Template:FMB001/FMB010 System settings - Revision history

Justinas.strelciunas at 13:13, 10 October 2023

2023-10-10T13:13:27Z

@@ Line 74: / Line 74: @@
 This feature will be used to save power consumption of external battery (power supply). It let the user choose one of four power saving modes which he would prefer: '''[[{{{model|FMB1YX}}} Sleep modes#GPS Sleep mode|GPS Sleep]]''', '''[[{{{model|FMB1YX}}} Sleep modes#Deep Sleep mode|Deep Sleep]]''', '''[[{{{model|FMB1YX}}} Sleep modes#Online Deep Sleep mode|Online Deep Sleep]]''' and '''[[{{{model|FMB1YX}}} Sleep modes#Ultra Deep Sleep|Ultra Deep Sleep]]'''. Also, after the mentioned options you can find the Timeout (min) parameter which starts counting when the device is in STOP mode. After timeout is reached and all conditions for sleep mode are met, the device goes to sleep mode. <br></br>
 '''Note:''' Detail description and conditions about every mode you can find [[{{{model|FMB1YX}}} Sleep modes|'''here''']].<br></br><br></br>
 ==Ignition Source==

Justinas.strelciunas: /* Sleep Mode */

2023-10-10T13:09:03Z

Sleep Mode

← Older revision		Revision as of 16:09, 10 October 2023
Line 70:		Line 70:
	If the Static navigation filter is disabled, it will apply no changes to GPS data. If the Static navigation filter is enabled, it will filter changes in GPS position if no movement (configured movement source) or ignition (configured ignition source) is detected (depends on what static navigation settings are selected: movement, ignition or both sources). It allows filtering GPS jumps when an object is parked (is not moving) and GPS position is still traced.<br></br>		If the Static navigation filter is disabled, it will apply no changes to GPS data. If the Static navigation filter is enabled, it will filter changes in GPS position if no movement (configured movement source) or ignition (configured ignition source) is detected (depends on what static navigation settings are selected: movement, ignition or both sources). It allows filtering GPS jumps when an object is parked (is not moving) and GPS position is still traced.<br></br>
	==Sleep Mode==		==Sleep Mode==
	[[~~Image~~:~~Sleep_mode~~.~~gif~~\|right~~\|300px~~]]		[[File:NO 1 WIRE FINAL.png\|right]]<br>
			<br>
	This feature will be used to save power consumption of external battery (power supply). It let the user choose one of four power saving modes which he would prefer: '''[[{{{model\|FMB1YX}}} Sleep modes#GPS Sleep mode\|GPS Sleep]]''', '''[[{{{model\|FMB1YX}}} Sleep modes#Deep Sleep mode\|Deep Sleep]]''', '''[[{{{model\|FMB1YX}}} Sleep modes#Online Deep Sleep mode\|Online Deep Sleep]]''' and '''[[{{{model\|FMB1YX}}} Sleep modes#Ultra Deep Sleep\|Ultra Deep Sleep]]'''. Also, after the mentioned options you can find the Timeout (min) parameter which starts counting when the device is in STOP mode. After timeout is reached and all conditions for sleep mode are met, the device goes to sleep mode. <br></br>		This feature will be used to save power consumption of external battery (power supply). It let the user choose one of four power saving modes which he would prefer: '''[[{{{model\|FMB1YX}}} Sleep modes#GPS Sleep mode\|GPS Sleep]]''', '''[[{{{model\|FMB1YX}}} Sleep modes#Deep Sleep mode\|Deep Sleep]]''', '''[[{{{model\|FMB1YX}}} Sleep modes#Online Deep Sleep mode\|Online Deep Sleep]]''' and '''[[{{{model\|FMB1YX}}} Sleep modes#Ultra Deep Sleep\|Ultra Deep Sleep]]'''. Also, after the mentioned options you can find the Timeout (min) parameter which starts counting when the device is in STOP mode. After timeout is reached and all conditions for sleep mode are met, the device goes to sleep mode. <br></br>
	'''Note:''' Detail description and conditions about every mode you can find [[{{{model\|FMB1YX}}} Sleep modes\|'''here''']].<br></br><br></br>		'''Note:''' Detail description and conditions about every mode you can find [[{{{model\|FMB1YX}}} Sleep modes\|'''here''']].<br></br><br></br>

	==Ignition Source==		==Ignition Source==
	Ignition source will be used to determine ignition of vehicle. {{{voltage\|If voltage is between High Voltage Level and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON. If voltage is higher than High Voltage Level or lower than Low Voltage Level - ignition is OFF.}}}<br>		Ignition source will be used to determine ignition of vehicle. {{{voltage\|If voltage is between High Voltage Level and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON. If voltage is higher than High Voltage Level or lower than Low Voltage Level - ignition is OFF.}}}<br>

Donatas.Kondratokas: /* New Time Synchronization method implementation */

2022-09-15T04:50:19Z

New Time Synchronization method implementation

← Older revision		Revision as of 07:50, 15 September 2022
Line 111:		Line 111:
	From 03.25.14 firmware the new time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. <br> This state checks the difference between RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a re-synchronization procedure by GNSS. <br> After that, the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time re-synchronization.<br>		From 03.25.14 firmware the new time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. <br> This state checks the difference between RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a re-synchronization procedure by GNSS. <br> After that, the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time re-synchronization.<br>
	In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to the state of syncing by NTP. Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP re-synchronization time is reached (if the re-synchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.		In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to the state of syncing by NTP. Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP re-synchronization time is reached (if the re-synchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.
	[[image:Lentele.png\|left\|~~500px~~]]		[[image:Lentele.png\|left\|520px]]
	[[image:Lenta.png\|middle\|~~560px~~]]		[[image:Lenta.png\|middle\|580px]]
	<br></br>		<br></br>

Donatas.Kondratokas: /* New Time Synchronization method implementation */

2022-09-15T04:42:04Z

New Time Synchronization method implementation

← Older revision		Revision as of 07:42, 15 September 2022
Line 113:		Line 113:
	[[image:Lentele.png\|left\|500px]]		[[image:Lentele.png\|left\|500px]]
	[[image:Lenta.png\|middle\|560px]]		[[image:Lenta.png\|middle\|560px]]
	~~<br></br>~~<br></br>		<br></br>

	==Accelerometer Auto Calibration==		==Accelerometer Auto Calibration==

Donatas.Kondratokas: /* New Time Synchronization method implementation */

2022-09-15T04:41:30Z

New Time Synchronization method implementation

← Older revision		Revision as of 07:41, 15 September 2022
Line 113:		Line 113:
	[[image:Lentele.png\|left\|500px]]		[[image:Lentele.png\|left\|500px]]
	[[image:Lenta.png\|middle\|560px]]		[[image:Lenta.png\|middle\|560px]]
	~~<br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br>~~<br></br><br></br>		<br></br><br></br>

	==Accelerometer Auto Calibration==		==Accelerometer Auto Calibration==

Donatas.Kondratokas: /* New Time Synchronization method implementation */

2022-09-14T13:17:02Z

New Time Synchronization method implementation

← Older revision		Revision as of 16:17, 14 September 2022
Line 108:		Line 108:
	===New Time Synchronization method implementation===		===New Time Synchronization method implementation===
	------------------		------------------
	~~[[image:Timesyncflowchart.png\|right\|600px]]~~
	From 03.25.14 firmware the new time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. <br> This state checks the difference between RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a re-synchronization procedure by GNSS. <br> After that, the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time re-synchronization.<br>		From 03.25.14 firmware the new time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. <br> This state checks the difference between RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a re-synchronization procedure by GNSS. <br> After that, the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time re-synchronization.<br>
	In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to the state of syncing by NTP. Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP re-synchronization time is reached (if the re-synchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.		In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to the state of syncing by NTP. Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP re-synchronization time is reached (if the re-synchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.
			[[image:Lentele.png\|left\|500px]]
			[[image:Lenta.png\|middle\|560px]]
	<br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br>		<br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br>

	==Accelerometer Auto Calibration==		==Accelerometer Auto Calibration==
	[[File:Accelerometer_auto.gif\|right\|300px]]		[[File:Accelerometer_auto.gif\|right\|300px]]

Mantas.Kraujelis at 07:16, 11 August 2021

2021-08-11T07:16:19Z

← Older revision		Revision as of 10:16, 11 August 2021
Line 60:		Line 60:
	* '''After Ignition ON''' - charger can be enabled after ignition is turned on, except if battery is fully charged or 10 minute timeout has not passed since device was turned on for faster FIX receiving;		* '''After Ignition ON''' - charger can be enabled after ignition is turned on, except if battery is fully charged or 10 minute timeout has not passed since device was turned on for faster FIX receiving;
	* '''Always''' - enables charging all the time (even if any sleep mode is active).}}}		* '''Always''' - enables charging all the time (even if any sleep mode is active).}}}
	~~{{{analog_input\|===Analog Input Value Range===~~
	~~------------------~~
	~~[[Image:Analog_input.gif\|right\|300px]]~~
	~~In ''Analog Input Value Range'' settings user can choose an analog input range of 10 V or 30 V.<br></br><br></br>}}}~~

	===Data Protocol===		===Data Protocol===
	------------------		------------------
	[[Image:Data_protocol.gif\|right\|300px]]		[[Image:Data_protocol.gif\|right\|300px]]
	In ''Data Protocol'' settings user can choose which protocol version ('''[[Codec#Codec 8\|Codec 8]]''' or '''[[Codec#Codec 8 Extended\|Codec 8 Extended]]''') will use for data sending to the server.<br></br>		In ''Data Protocol'' settings user can choose which protocol version ('''[[Codec#Codec 8\|Codec 8]]''' or '''[[Codec#Codec 8 Extended\|Codec 8 Extended]]''') will use for data sending to the server.<br></br>
	~~{{{input_mode\|===Input Mode===~~
	~~------------------~~
	~~[[Image:Input_mode.gif\|right\|300px]]~~
	~~In ''Input Mode'' settings user can choose which configurable input will be use: ''DIN2/AIN1'' or ''[[FMB130_Negative_Input_Usage_Scenario\|Ground Sense]]''.<br/>~~
	If Ground Sense is selected, the input will act as an inverse Digital Input, where a low voltage level will output "1" using the Ground Sense I/O element, and a high voltage level will output "0".<br></br><br></br>}}}

	==Static Navigation Settings==		==Static Navigation Settings==
Line 85:		Line 75:
	==Ignition Source==		==Ignition Source==
	Ignition source will be used to determine ignition of vehicle. {{{voltage\|If voltage is between High Voltage Level and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON. If voltage is higher than High Voltage Level or lower than Low Voltage Level - ignition is OFF.}}}<br>		Ignition source will be used to determine ignition of vehicle. {{{voltage\|If voltage is between High Voltage Level and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON. If voltage is higher than High Voltage Level or lower than Low Voltage Level - ignition is OFF.}}}<br>
	{{{img_ignition\|[[Image:~~Ignition_settings~~.gif\|right\|300px]]}}}		{{{img_ignition\|[[Image:FMB001_Ignition.gif\|right\|300px]]}}}
	{{{ignition_source\|Possible ignition sources:		{{{ignition_source\|Possible ignition sources:
	{{{txt_din1\|* '''DIN 1''' (Digital Input 1) - if ''DIN1'' is 1 - ignition is ON; if ''DIN1'' value is 0 - ignition is OFF;}}}		{{{txt_din1\|* '''DIN 1''' (Digital Input 1) - if ''DIN1'' is 1 - ignition is ON; if ''DIN1'' value is 0 - ignition is OFF;}}}

Mantas.Kraujelis at 13:56, 10 August 2021

2021-08-10T13:56:05Z

← Older revision		Revision as of 16:56, 10 August 2021
Line 91:		Line 91:
	{{{txt_engine_rpm\|* '''Engine RPM''' - if ''RPM'' from OBD II or CAN is higher than 0 - ignition is ON; if ''RPM'' from OBD II or CAN is equal to 0 - ignition is OFF;}}}		{{{txt_engine_rpm\|* '''Engine RPM''' - if ''RPM'' from OBD II or CAN is higher than 0 - ignition is ON; if ''RPM'' from OBD II or CAN is equal to 0 - ignition is OFF;}}}
	* '''Accelerometer''' - if movement sensor detects movement - ignition is ON; if movement is not detected - ignition is OFF;		* '''Accelerometer''' - if movement sensor detects movement - ignition is ON; if movement is not detected - ignition is OFF;
	More than one ignition source can be selected at the same moment. When there are 2 or more sources selected, at least one condition has to be met to change Ignition status.<br>		More than one ignition source can be selected at the same moment. When there are 2 or more sources selected, at least one condition has to be met to change Ignition status.<br></br>
	{{{txt_example\|'''Example:''' DIN1 and Accelerometer are selected as the Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. Users can select movement start and movement stop delay time - those parameters are used when the accelerometer is selected as an ignition source. }}}}}}		{{{txt_example\|'''Example:''' DIN1 and Accelerometer are selected as the Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. Users can select movement start and movement stop delay time - those parameters are used when the accelerometer is selected as an ignition source. }}}}}}
	Ignition status is used in power management and the following functionalities: [[{{{model\|FMB1YX}}} Features settings#Eco/Green Driving\|Eco/Green Driving]], [[{{{model\|FMB1YX}}} Accelerometer Features settings#Excessive Idling\|Excessive Idling]], Fuel Consumption, [[{{{model\|FMB1YX}}} Features settings#Over Speeding\|Over Speeding]], [[{{{model\|FMB1YX}}} Accelerometer Features settings#Towing Detection\|Towing Detection]] and [[{{{model\|FMB1YX}}} Trip/Odometer settings\|Trip]].<br>		Ignition status is used in power management and the following functionalities: [[{{{model\|FMB1YX}}} Features settings#Eco/Green Driving\|Eco/Green Driving]], [[{{{model\|FMB1YX}}} Accelerometer Features settings#Excessive Idling\|Excessive Idling]], Fuel Consumption, [[{{{model\|FMB1YX}}} Features settings#Over Speeding\|Over Speeding]], [[{{{model\|FMB1YX}}} Accelerometer Features settings#Towing Detection\|Towing Detection]] and [[{{{model\|FMB1YX}}} Trip/Odometer settings\|Trip]].<br>

Mantas.Kraujelis at 13:54, 10 August 2021

2021-08-10T13:54:48Z

← Older revision		Revision as of 16:54, 10 August 2021
Line 92:		Line 92:
	* '''Accelerometer''' - if movement sensor detects movement - ignition is ON; if movement is not detected - ignition is OFF;		* '''Accelerometer''' - if movement sensor detects movement - ignition is ON; if movement is not detected - ignition is OFF;
	More than one ignition source can be selected at the same moment. When there are 2 or more sources selected, at least one condition has to be met to change Ignition status.<br>		More than one ignition source can be selected at the same moment. When there are 2 or more sources selected, at least one condition has to be met to change Ignition status.<br>
	~~{{{txt_din3\|* '''DIN 3''' (Digital Input 3) - if ''DIN3'' is 1 - ignition is ON; if ''DIN3'' value is 0 - ignition is OFF;}}}~~
	{{{txt_example\|'''Example:''' DIN1 and Accelerometer are selected as the Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. Users can select movement start and movement stop delay time - those parameters are used when the accelerometer is selected as an ignition source. }}}}}}		{{{txt_example\|'''Example:''' DIN1 and Accelerometer are selected as the Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. Users can select movement start and movement stop delay time - those parameters are used when the accelerometer is selected as an ignition source. }}}}}}
	Ignition status is used in power management and the following functionalities: [[{{{model\|FMB1YX}}} Features settings#Eco/Green Driving\|Eco/Green Driving]], [[{{{model\|FMB1YX}}} Accelerometer Features settings#Excessive Idling\|Excessive Idling]], Fuel Consumption, [[{{{model\|FMB1YX}}} Features settings#Over Speeding\|Over Speeding]], [[{{{model\|FMB1YX}}} Accelerometer Features settings#Towing Detection\|Towing Detection]] and [[{{{model\|FMB1YX}}} Trip/Odometer settings\|Trip]].<br>		Ignition status is used in power management and the following functionalities: [[{{{model\|FMB1YX}}} Features settings#Eco/Green Driving\|Eco/Green Driving]], [[{{{model\|FMB1YX}}} Accelerometer Features settings#Excessive Idling\|Excessive Idling]], Fuel Consumption, [[{{{model\|FMB1YX}}} Features settings#Over Speeding\|Over Speeding]], [[{{{model\|FMB1YX}}} Accelerometer Features settings#Towing Detection\|Towing Detection]] and [[{{{model\|FMB1YX}}} Trip/Odometer settings\|Trip]].<br>

Mantas.Kraujelis at 13:53, 10 August 2021

2021-08-10T13:53:39Z

← Older revision		Revision as of 16:53, 10 August 2021
Line 123:		Line 123:
	In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to the state of syncing by NTP. Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP re-synchronization time is reached (if the re-synchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.		In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to the state of syncing by NTP. Entering the state of NTP syncing, the firmware immediately attempts to synchronize the time by triggering NTP and later on, does this periodically every time the configured NTP re-synchronization time is reached (if the re-synchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.
	<br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br>		<br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br><br></br>
	~~{{{txt_autocal\|~~==Accelerometer Auto Calibration==		==Accelerometer Auto Calibration==
	[[File:Accelerometer_auto.gif\|right\|300px]]		[[File:Accelerometer_auto.gif\|right\|300px]]
	Users can disable or enable Accelerometer Auto Calibration and Gravity Filter features. This feature is available from firmware version 03.25.07.Rev.00. Under Accelerometer Auto Calibration settings, user can choose:		Users can disable or enable Accelerometer Auto Calibration and Gravity Filter features. This feature is available from firmware version 03.25.07.Rev.00. Under Accelerometer Auto Calibration settings, user can choose: