Changes

no edit summary
Line 79: Line 79:  
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><br>
 +
 
 +
 
 +
===BT/BLE module OFF during Sleep modes===
 +
------------------
 +
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.
 +
<br>
 +
 
 +
From the version, 03.28.XX this new functionality includes new parameters:
 +
 
 +
*'''Periodic Wakeup''' – if value is greater than zero, device while being in Deep Sleep or Online Deep Sleep, will wake up after defined period for beacon collection. This is mainly should be used when Bluetooth® is disabled in sleep.
 +
*'''Bluetooth® On While In Sleep'''- by default this parameter value is set to Enable and BT will work as in base functionality. If this value is set to Disable, Bluetooth® will be turned off when device goes to Deep Sleep or Online Deep Sleep and will be turned on during Periodic Wakeup or if device enters normal state.
 +
[[Image:PWU.jpg|right|300px]]
 +
</br></br>
 +
 
 +
Note: In case when during scan after wakeup no BLE devices will be found FMB will be active for configured scan duration time in Bluetooth® 4.0 tab. After that timeout FMB will go to sleep state.
 +
<br>
 +
 
 +
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state and can only wake up if one of the conditions is true:
 +
 
 +
*Movement is detected by accelerometer (not by the configured movement source);
 +
*External power is applied;
 +
*It is the time to make a new periodic record (new feature);
 +
<br>
 +
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.
 +
 
 
==Ignition Source==
 
==Ignition Source==
Ignition source will be used to determine ignition of vehicle. {{{voltage|If voltage is between High Voltage Lever and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON. If voltage is higher than High Voltage Lever 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:Ignition_settings.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;}}}
* '''Power Voltage''' - if voltage is between High Voltage Lever and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON; if voltage is higher than High Voltage Lever or lower than Low Voltage Level - ignition is OFF.
+
* '''Power 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.
 
{{{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;
Line 95: Line 121:  
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>
 
<!--'''Note:''' Object motion detection settings, where user can configure {{{txt_num|4}}} ways how {{{model|FMB1YX}}} detects movement and change its working mode (for more information refer to section {{{ctrDaq|[[{{{model|Template:}}} Data acquisition settings]]}}}). Other functionalities that depend on movement source are: power manager, fuel consumption and trip;}}}-->
 
<!--'''Note:''' Object motion detection settings, where user can configure {{{txt_num|4}}} ways how {{{model|FMB1YX}}} detects movement and change its working mode (for more information refer to section {{{ctrDaq|[[{{{model|Template:}}} Data acquisition settings]]}}}). Other functionalities that depend on movement source are: power manager, fuel consumption and trip;}}}-->
 +
 
==Accelerometer Delay Settings==
 
==Accelerometer Delay Settings==
 
[[Image:Accelerometer_delay.gif|right|300px]]
 
[[Image:Accelerometer_delay.gif|right|300px]]
Line 117: Line 144:  
===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.  
<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>
+
[[image:Lentele.png|left|520px]]
 +
[[image:Lenta.png|middle|580px]]
 +
<br></br>
 
{{{txt_autocal|==Accelerometer Auto Calibration==
 
{{{txt_autocal|==Accelerometer Auto Calibration==
 
[[File:Accelerometer_auto.gif|right|300px]]
 
[[File:Accelerometer_auto.gif|right|300px]]
Line 138: Line 166:  
'''Note:''' In [[{{{model|FMB1YX}}}]] devices autocalibration is set by default and it is not configurable via configurator. Device connected to OBD port is not positioned according to the vehicle axis and in this case autocalibration is a must.
 
'''Note:''' In [[{{{model|FMB1YX}}}]] devices autocalibration is set by default and it is not configurable via configurator. Device connected to OBD port is not positioned according to the vehicle axis and in this case autocalibration is a must.
 
}}}
 
}}}
 +
 +
==Assisted GPS Settings==
 +
[[Image:FMX_8_Assisted_GPS_Settings.gif|right|300px]]
 +
Assisted GPS is a feature that significantly improves the time to first fix. It works by providing the necessary data to the device via the cellular network instead of the slow satellite link, essentially "warming up" the receiver for a fix.<br></br>
 +
The user can '''Enable''' or '''Disable''' the AGPS in '''Home''', '''Roaming''' or '''Unknown''' Network.<br></br>
 +
By default, functionality will only work if device is connected to Home Network.<br></br>
 +
AGPS File Duration determines the duration of the downloaded AGPS file. The longer the duration, the more data is downloaded periodically.
 +
The user can choose:
 +
* '''3 days''' – 3 days duration.
 +
* '''6 hours''' – 6 hours duration.
 +
 +
==Low Power Mode==
 +
[[File:Low_power_mode.gif|right|400px]]
 +
Low Power mode functionality was implemented to firmware from FMB.03.28.02.Rev.00. This functionality only works on devices that supports battery. It can only be active if device sleep mode is configured as Deep Sleep or Online Sleep. In other cases, low power mode is not allowed.
 +
* '''Min Period''' – is timer after which device has to wake up (exit Deep or Online sleep state)
 +
* '''GPS Search Period''' – is period in which device tries to acquire GPS fix after waking up
 +
* '''GPS Accuracy''' – is value of minimum requirements of HDOP/PDOP/VDOP to renew GPS data after fix was acquired.
 +
* '''GPS Satellites Quantity''' – is value of minimum visible satellites available to device to renew GPS data after fix was acquired.
 +
* '''Hold GPS Fix Timeout''' – is timer in which device tries to hold GPS fix for better GPS data accuracy.
 +
<br>
 +
<br>
 +
As mentioned before, this functionality only works if Deep sleep or Online sleep is configured. Device will enter Low Power mode if external power source is lost, but battery is connected. Device immediately will switch to it’s configured sleeping mode without checking any conditions for sleeping mode. Only conditions for device to go to sleep are: is Low Power mode enabled, is external voltage missing, is there a battery connected.
 +
<br>
 +
<br>
 +
'''Note:''' When device is in Low Power mode, device will not generate any records except for one periodic record after every '''Min Period'''.

Navigation menu