Difference between revisions of "Template:FMB System settings"

From Wiki Knowledge Base | Teltonika GPS
m
(112 intermediate revisions by 22 users not shown)
Line 1: Line 1:
System settings have the following configurable parameters:
+
System settings have 9 configurable parameters:
==System Settings==
+
* ''Sleep Settings'', where user can choose sleep mode;
{{{movement|===Movement Source===
+
* ''Ignition Source'', where user can choose between power voltage, digital input 1, accelerometer and engine RPM as ignition sources. More than one ignition source can be selected at the same moment. User can select movement start and movement stop delay time - those parameters are used when accelerometer is selected as ignition source. Ignition status is used in power management and the following functionalities: eco driving, excessive idling, fuel consumption, over speeding, towing and trip functionalities.
------------------
+
* Object Motion Detection Settings, where user can configure 4 ways how {{{model|FMB1YX}}} detects movement, and change its working mode (for working modes, read section [[{{Template:FMB Data acquisition settings|{{{model}}}}}|Data acquisition settings]]). Other functionalities that depend from movement source: power manager, fuel consumption and trip.
Movement source will be used to determine when a vehicle is on stop or moving.<br>
+
* ''Static Navigation Settings'', where user can turn static navigation on or off. Additionally, user can choose what source is used (movement or ignition) to activate/deactivate static navigation.
Possible movement sources:
+
* Records Settings, where user can enable or disable records when GPS is not available (no time synchronization).
{{{img_mov|[[Image:Movement_source.gif|right|300px]]}}}
+
* ''GNSS Source'' settings, where user can choose the necessary satellite system.
* '''Ignition''' - if ignition (based on ignition source) is ON, Vehicle MOVING mode is used; if the ignition is OFF, Vehicle on STOP mode is used;
+
* ''LED Indication'', where user can turn on or off the indication LEDs.
* '''Accelerometer''' (movement) - if accelerometer detects movement, Vehicle MOVING mode is used; if there is no movement detected, Vehicle on STOP mode is used;
+
* ''Battery Charge Mode'', where user can choose when battery will be charged: <span style=color:#F6A83E>On Need</span> (battery will be charged anytime when it needs to be charged) and <span style=color:#F6A83E>After Ignition ON</span> (battery will be charged only when ignition is on).
* '''GNSS''' - if GPS fix is acquired and speed >= 5 km/h vehicle MOVING mode is used; if GPS speed <5 km/h, Vehicle on STOP mode is used;
+
* ''Analog Input Value Range'', where user can choose analog input range of 10 V or 30 V (currently 10 V is in fact a 30 V range).
{{{txt_can_speed|* '''CAN speed''' - If speed from BT OBDII dongle is higher than 0 km/h, Vehicle MOVING mode is used; If speed from BT OBDII dongle is equal 0 km/h, Vehicle on STOP mode is used;}}}
+
* ''Time Synchronization'' settings, where user can choose which source(s) to use for {{{model|FMB1YX}}} time synchronization. User has a choice to use only one synchronization source (<span style=color:#F6A83E>Disable (GPS only)</span>), allow synchronization from both the GNSS and NTP server (<span style=color:#F6A83E>NTP</span>), select synchronization through GNSS and GSM operator (<span style=color:#F6A83E>NITZ</span>) or from all three sources (when <span style=color:#F6A83E>NITZ+NTP</span> is selected). User can select which NTP server (it is possible to configure up to two servers) and what time period to use to resynchronize time.
If there is no GNSS fix, the accelerometer determines profile change. If there is no OBDII dongle active (or speed reported by dongle == 0 km/h) accelerometer determines profile change.<br></br>
 
'''Note:''' From new firmware version '''03.25.14.Rev.03''' added new '''multiple movement sources selection''' at once. If any of selected movement sources are active, movement mode will be activated. If all selected sources are inactive STOP mode will be enabled. Configurable movement parameter ID has been changed. Information regarding configurable parameter ID could be found in the table below:
 
<table class="nd-othertables_2" style="width: 68%;">
 
<tr>
 
        <th style="width: 10%; text-align:left; vertical-align:middle; color:black">Firmware version until 03.25.14.rev.03</th>
 
        <th style="width: 20%; text-align:center; vertical-align:middle; color:black">Firmware version from 03.25.14.rev.03</th>
 
    </tr>
 
<tr>
 
        <td style="width: 8%; text-align:center;">100 - Parameter ID</td>
 
        <td style="width: 8%; text-align:center">138 - Parameter ID</td>
 
    </tr>
 
</table>}}}
 
{{{speed_source|===Speed Source===
 
------------------
 
[[Image:Speed.gif|right|300px]]
 
Speed source will be used to determine which speed source to use.<br></br>
 
'''Note:''' If the speed source is configured as OBD / CAN, the device will try to take speed from OBD first. If the speed value read is 0, then it tries to take speed from CAN. If the speed value is also 0, the firmware takes the speed from GNSS, even though it is not configured.}}}
 
===Records Saving/Sending Without TS===
 
------------------
 
This feature will be used to save and send records to server without time sinchronization.<br>
 
[[Image:Records_saving.gif|right|300px]]
 
Possible options:
 
* '''After Position Fix''' - records will be saved and send only after position fix;
 
* '''After Time Sync''' - records will be saved and send only after time synchronization;
 
* '''Always''' - records will be always saved and send even if will not be time synchronization.
 
'''Note:''' ''If record is without valid coordinates – (there were no GPS fix in the moment of data acquisition) – Longitude, Latitude and Altitude values are last valid fix, and Angle, Satellites and Speed are 0. After a reboot, it will send zero coordinates.''
 
  
===LED Indication===
+
{| class="wikitable"
------------------
+
|+
[[Image:Led_indication.gif|right|300px]]
+
! style="width: 150px; background: black; color: white;"  | Movement source
This feature will be used to indicate device status and navigate them.<br></br>
+
! style="width: 300px; background: black; color: white;" | Vehicle on Stop mode
'''Note:''' If this feature is enabled, you can check LEDs behavior '''[[{{{model|FMB1YX}}} LED status|here]]'''.
+
! style="width: 300px; background: black; color: white;" | Vehicle Moving mode
===GNSS Source===
+
|-
------------------
+
! style="text-align: left; vertical-align: top;" | Ignition (recommmended)
In ''GNSS Source'' settings user can configure which GNSS system(s) to use.<br />
+
| style="text-align: left; vertical-align: top;" | If ignition (ignition source) is logic low
{{{fmb208|[[Image:GNSS_source.gif|right|300px]]}}}
+
| style="text-align: left; vertical-align: top;" | If ignition (ignition source) is logic high
'''List of configurable GNSS sources:'''
+
|-
{{{txt_fmb208_enable|* GPS only
+
! style="text-align: left; vertical-align: top;" | Movement (movement sensor)
* IRNSS only
+
| style="text-align: left; vertical-align: top;" | Internal movement sensor does not detect movement.
* GPS + Galileo + IRNSS
+
| style="text-align: left; vertical-align: top;" | Internal movement sensor detects movement.
* GPS + Galileo + GLONASS + BeiDou + IRNSS.}}}
+
|-
{{{battery_charge|===Battery Charge Mode===
+
! style="text-align: left; vertical-align: top;" rowspan=2 | GPS
------------------
+
| style="text-align: left; vertical-align: top;" | GPS fix is available and vehicle speed is lower than 5 km/h.
In ''Battery Charge Mode'' settings user can choose when battery will be charged.<br>
+
| style="text-align: left; vertical-align: top;" | GPS fix is available and vehicle speed is higher than 5 km/h.
[[Image:Battery_charge.gif|right|300px]]
+
|-
Possible options:
+
| style="text-align: left; vertical-align: top;" colspan=2 | While GPS fix is unavailable, Object Motion Detection Settings are working like in Msensor mode.
* '''On Need''' - enable battery charger any time when needed;
+
|-
* '''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;
+
! style="text-align: left; vertical-align: top;" | CAN speed
* '''Always''' - enables charging all the time (even if any sleep mode is active).}}}
+
| style="text-align: left; vertical-align: top;" | If speed from BT OBDII dongle is equal 0 km/h.
{{{analog_input|===Analog Input Value Range===
+
| style="text-align: left; vertical-align: top;" | If speed from BT OBDII dongle is higher that 0 km/h.
------------------
+
|-
[[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===
+
''Static Navigation'' mode is a filter, which filters out track jumps when the object is stationary. If static navigation filter is disabled, it will apply no changes to GPS data. If 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 is selected: movement, ignition or both sources). It allows filtering GPS jumps when object is parked (not moving) and GPS position is still traced.
------------------
 
[[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>
 
{{{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==
+
[[Image:fmb120_system.png|800px|center]]
[[Image:Static_navigation.gif|right|300px]]
 
''Static Navigation Mode'' is a filter, which filters out track jumps when the object is stationary.<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==
 
[[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>
 
'''Note:''' Detail description and conditions about every mode you can find [[{{{model|FMB1YX}}} Sleep modes|'''here''']].<br></br><br></br><br>
 
  
 +
In GNSS source Settings user can configure which GNSS system(s) to use.<br/>User has a choice to use only one system of GPS, Glonass, Galileo or Beidou. Also it is possible to choose two or three systems together. One exception is that you cannot combine Beidou and Glonass systems together.
  
===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:
+
{| class="wikitable"
 +
|+
 +
! style="width: 250px; background: black; color: white;" | Selected source(s)
 +
! style="width: 100px; background: black; color: white;" | ID
 +
|-
 +
! style="text-align: left; vertical-align: top;" | BeiDou only
 +
| style="text-align: left; vertical-align: top;" | 01
 +
|-
 +
! style="text-align: left; vertical-align: top;" | GLONASS only
 +
| style="text-align: left; vertical-align: top;" | 02
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Galileo only
 +
| style="text-align: left; vertical-align: top;" | 04
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Galileo + Beidou
 +
| style="text-align: left; vertical-align: top;" | 05
 +
|-
 +
! style="text-align: left; vertical-align: top;" | Galileo + Glonass
 +
| style="text-align: left; vertical-align: top;" | 06
 +
|-
 +
! style="text-align: left; vertical-align: top;" | GPS only
 +
| style="text-align: left; vertical-align: top;" | 08
 +
|-
 +
! style="text-align: left; vertical-align: top;" | GPS + BeiDou
 +
| style="text-align: left; vertical-align: top;" | 09
 +
|-
 +
! style="text-align: left; vertical-align: top;" | GPS + GLONASS
 +
| style="text-align: left; vertical-align: top;" | 10
 +
|-
 +
! style="text-align: left; vertical-align: top;" | GPS + Galileo
 +
| style="text-align: left; vertical-align: top;" | 12
 +
|-
 +
! style="text-align: left; vertical-align: top;" | GPS + Galileo + BeiDou
 +
| style="text-align: left; vertical-align: top;" | 13
 +
|-
 +
! style="text-align: left; vertical-align: top;" | GPS + Galileo + GLONASS
 +
| style="text-align: left; vertical-align: top;" | 14
 +
|-
 +
|}
  
*'''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.
+
Examples of NON-configurable GNSS sources:
*'''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.
+
* GLONASS + BeiDou;
[[Image:PWU.jpg|right|300px]]
+
* Galileo + GLONASS + BeiDou;
</br></br>
+
* GPS + GLONASS + BeiDou;
 
+
* GPS + Galileo + GLONASS + BeiDou.
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 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]]}}}
 
{{{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;}}}
 
* '''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;}}}
 
* '''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>
 
{{{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. }}}}}}
 
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;}}}-->
 
 
 
==Accelerometer Delay Settings==
 
[[Image:Accelerometer_delay.gif|right|300px]]
 
''Accelerometer Delay Settings'' will be use to set timeout of delay when will be detected accelerometer status changes.<br></br>
 
'''Note:''' these settings impact ignition/movement sources.<br>
 
The user can set:
 
* '''Movement Start Delay (s)''' - movement start delay in seconds;
 
* '''Movement Stop Delay (s)''' - movement stop delay in seconds;
 
==Time Synchronization==
 
''Time Synchronization settings'' will be use to set how device time will be re-synchronize.
 
===Old Time Synchronization Settings*===
 
------------------
 
[[Image:Time_synchronization.gif|right|300px]]
 
''Synchronization settings'' is used for choosing the device’s internal time synchronization source. Possible options are:
 
* '''GPS Only''' - time synchronization by GPS;
 
* '''NITZ and NTP''' - time synchronization from GSM operators (NITZ) and/or web server (NTP);
 
* '''NTP''' - time synchronization from NTP server only;
 
* '''NITZ''' - time synchronization from GSM operators (NITZ).
 
''NTP Resync'' parameter determines how often a device should resynchronize its time. If the set value is not equal to zero, time resynchronization will occur periodically at time intervals to which this parameter is set.<br>
 
''NTP server 1'' and ''NTP Server 2'' let the user select which NTP server (s) will be used to re-synchronize time.<br></br>
 
'''*''' using 03.25.13 or older firmware
 
===New Time Synchronization method implementation===
 
------------------
 
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.
 
[[image:Lentele.png|left|520px]]
 
[[image:Lenta.png|middle|580px]]
 
<br></br>
 
{{{txt_autocal|==Accelerometer Auto Calibration==
 
[[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:
 
* '''Disable''' – do not use auto-calibration feature (sends AXES raw data).
 
* '''Once''' – calibrate one time only.
 
* '''Continuous''' – continuously analyzes current data and re-calibrates if needed.
 
 
 
<br> '''''Important!''''' If Auto calibration is disabled, the device should be mounted according to the User manual for EcoDriving feature to work properly. If enabled, AXES will be reoriented to VEHICLE axes according to the User manual (+X – Forward, +Y – Left, +Z – Down).
 
 
 
<br> Gravity filter subtracts gravity from vector when devices are calibrated or if auto-calibration is disabled (default values). Gravity is only removed when gravity filter is enabled.
 
<br>
 
Filter settings, user can choose:
 
* '''Disabled''' – do not remove GRAVITY component from AXL/Crash data.
 
* '''Enabled''' – remove GRAVITY component from AXL/Crash.
 
<br>
 
'''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'''.
 

Revision as of 07:54, 26 April 2018

System settings have 9 configurable parameters:

  • Sleep Settings, where user can choose sleep mode;
  • Ignition Source, where user can choose between power voltage, digital input 1, accelerometer and engine RPM as ignition sources. More than one ignition source can be selected at the same moment. User can select movement start and movement stop delay time - those parameters are used when accelerometer is selected as ignition source. Ignition status is used in power management and the following functionalities: eco driving, excessive idling, fuel consumption, over speeding, towing and trip functionalities.
  • Object Motion Detection Settings, where user can configure 4 ways how FMB1YX detects movement, and change its working mode (for working modes, read section [[

Data Acquisition

Data Acquisition modes are an essential part of FMB1YX device, they are also highly configurable.
Through configuration user defines how records will be saved and sent. There are three different modes: Home, Roaming, and Unknown. All these modes with configured data acquisition and report frequencies depend on the current GSM Operator defined in the Operator list (see section Template:FMB GSM Operators settings) and are switched when GSM operator changes (e.g. vehicle passes through a country border).
If current GSM operator is defined as Home Operator, the device will work in Home Data Acquisition mode, if the current operator is defined as Roaming Operator, the device will work in Roaming Data Acquisition mode, and if the current operator code is not written in the Roaming Operator list, the device will work in Unknown mode.
This functionality allows having different AVL records to acquire and send parameter values when the object is moving or standing still. Vehicle moving or stop state is defined by the Stop Detection Source parameter. There are 4 ways for FMB1YX to switch between Vehicle on Stop and Vehicle Moving modes, please refer to the first table in Template:FMB System settings.
FMB1YX has 6 different modes. Operational logic is shown in the figure below.

Bw nb.png If home operator is written to roaming operator list, it will still be detected as home operator.
Fmb120 daq mode logic.png


The operator search is performed every 15 minutes. Depending on the current GSM operator Home, Roaming or Unknown mode can be changed faster than every 15 minutes. This process is separate from the operator search. Movement criteria are checked every second.

Fmb120 data acquisition config+.gif


Record Saving settings

Min Saved Records defines the minimum number of coordinates and I/O data that should be transferred within a single connection to the server. If FMB1YX does not have enough coordinates to send to the server, it will check again after a time interval defined in Send Period field.
Send period controls the frequency of data being sent to the server over GPRS. The module makes attempts to send collected data to the server every defined period of time. If it does not have enough records (depends on the parameter Min. Saved Records described above), it tries again after the defined time interval.

Bw nb.png Keep in mind that FMB1YX operates in GMT:0 time zone, without daylight saving.

FMB1YX is able to collect records using four methods at the same time: time, distance, angle, and speed-based data acquisition:

  • Time based data acquisition (Min Period) – records are acquired every time when a defined interval of time passes. Entering zero disables data acquisition based on time.
  • Distance-based data acquisition (Min Distance) – records are acquired when the distance between the previous coordinate and current position is greater than a defined parameter value. Entering zero disables data acquisition based on distance.
  • Angle based data acquisition (Min Angle) – records are acquired when the angle difference between the last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on the angle.
  • Speed based data acquisition (Min Speed Delta) – records are acquired when the speed difference between the last recorded coordinate and current position is greater than a defined value. Entering zero disables data acquisition based on speed.
Fmb120 daq mode basis.png

On Demand Tracking

This functionality was made global (for all FMB devices) from 03.25.06.Rev.00. Tracking on Demand can be activated using commands. After device receives SMS/GPRS command " on_demand_trackingX" where X is a number from 0 to 2.

Possible X values are:

  • X = 0 – Stops Tracking on Demand functionality.
  • X = 1 – Starts Tracking on Demand functionality.
  • X = 2 – Generates one high priority record and initiates data sending to the server.

After that, the device starts to generate high priority records and initiate data sending to the server. This feature is configurable via SMS/GPRS commands only.

From version 03.25.11.Rev.00 tracking on demand can be triggered by multiple IO Events. To enable functionality at least one activation source must be selected and an appropriate IO Event (in I/O tab) should be enabled (Low/High/Panic priority, the operand must NOT be “Monitoring”). When IO Event is generated and if the event is enabled in activation sources, tracking on demand will be started. THE new IO event will not interrupt or restart tracking on-demand until the Duration period has expired. If tracking on demand is already running, SMS/GPRS command will restart tracking on demand. If tracking the on-demand period is lower than the normal record acquisition period, only high priority records will be created. If tracking the on-demand period is larger than the normal record acquisition period, low priority records will be created according to data acquisition configuration and high priority records will be created after configured tracking on-demand period. Some new Tracking on Demand parameters are introduced in devices.

On demand Tracking.gif

There are three available options for the activation source of tracking on demand - DIN/AIN or both (devices that support multiple DINs/AINs allow choosing which DINs/AINs to use). Note that, these inputs will work as buttons, rather than switches, and are used to trigger the functionality, the duration of tracking on demand will not be extended if the activation source status is high for a period of time.|Data acquisition settings]]). Other functionalities that depend from movement source: power manager, fuel consumption and trip.

  • Static Navigation Settings, where user can turn static navigation on or off. Additionally, user can choose what source is used (movement or ignition) to activate/deactivate static navigation.
  • Records Settings, where user can enable or disable records when GPS is not available (no time synchronization).
  • GNSS Source settings, where user can choose the necessary satellite system.
  • LED Indication, where user can turn on or off the indication LEDs.
  • Battery Charge Mode, where user can choose when battery will be charged: On Need (battery will be charged anytime when it needs to be charged) and After Ignition ON (battery will be charged only when ignition is on).
  • Analog Input Value Range, where user can choose analog input range of 10 V or 30 V (currently 10 V is in fact a 30 V range).
  • Time Synchronization settings, where user can choose which source(s) to use for FMB1YX time synchronization. User has a choice to use only one synchronization source (Disable (GPS only)), allow synchronization from both the GNSS and NTP server (NTP), select synchronization through GNSS and GSM operator (NITZ) or from all three sources (when NITZ+NTP is selected). User can select which NTP server (it is possible to configure up to two servers) and what time period to use to resynchronize time.
Movement source Vehicle on Stop mode Vehicle Moving mode
Ignition (recommmended) If ignition (ignition source) is logic low If ignition (ignition source) is logic high
Movement (movement sensor) Internal movement sensor does not detect movement. Internal movement sensor detects movement.
GPS GPS fix is available and vehicle speed is lower than 5 km/h. GPS fix is available and vehicle speed is higher than 5 km/h.
While GPS fix is unavailable, Object Motion Detection Settings are working like in Msensor mode.
CAN speed If speed from BT OBDII dongle is equal 0 km/h. If speed from BT OBDII dongle is higher that 0 km/h.

Static Navigation mode is a filter, which filters out track jumps when the object is stationary. If static navigation filter is disabled, it will apply no changes to GPS data. If 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 is selected: movement, ignition or both sources). It allows filtering GPS jumps when object is parked (not moving) and GPS position is still traced.

Fmb120 system.png

In GNSS source Settings user can configure which GNSS system(s) to use.
User has a choice to use only one system of GPS, Glonass, Galileo or Beidou. Also it is possible to choose two or three systems together. One exception is that you cannot combine Beidou and Glonass systems together.


Selected source(s) ID
BeiDou only 01
GLONASS only 02
Galileo only 04
Galileo + Beidou 05
Galileo + Glonass 06
GPS only 08
GPS + BeiDou 09
GPS + GLONASS 10
GPS + Galileo 12
GPS + Galileo + BeiDou 13
GPS + Galileo + GLONASS 14

Examples of NON-configurable GNSS sources:

  • GLONASS + BeiDou;
  • Galileo + GLONASS + BeiDou;
  • GPS + GLONASS + BeiDou;
  • GPS + Galileo + GLONASS + BeiDou.