Line 15: |
Line 15: |
| *Ignition source, where user can choose between power voltage, digital input 1, digital input 2, digital input 3, digital input 4 and accelerometer 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 (in seconds): those parameters are used when ignition source is accelerometer. | | *Ignition source, where user can choose between power voltage, digital input 1, digital input 2, digital input 3, digital input 4 and accelerometer 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 (in seconds): those parameters are used when ignition source is accelerometer. |
| *Time synchronization settings, where user can choose from what source (or sources) FMB640 time will be synchronized. User has choice to use only one synchronization source by GNSS. When selected synchronization from NTP, time will be synchronized from NTP server and from GNSS. When selected synchronization from NITZ, time will be synchronized from GSM operator and GNSS. When selected synchronization from NITZ+NTP, time will be synchronized from all three sources (if it is necessary). Every time GNSS fix will be acquired time will be synchronized (if needed). User can select from what NTP server (possible to configure two servers) time will be synchronized, as well as delay after which time synchronization from non-GNSS source will begin. | | *Time synchronization settings, where user can choose from what source (or sources) FMB640 time will be synchronized. User has choice to use only one synchronization source by GNSS. When selected synchronization from NTP, time will be synchronized from NTP server and from GNSS. When selected synchronization from NITZ, time will be synchronized from GSM operator and GNSS. When selected synchronization from NITZ+NTP, time will be synchronized from all three sources (if it is necessary). Every time GNSS fix will be acquired time will be synchronized (if needed). User can select from what NTP server (possible to configure two servers) time will be synchronized, as well as delay after which time synchronization from non-GNSS source will begin. |
− | {| class="wikitable"
| |
− | |+
| |
− | ! style="width: 150px; background: black; color: white;" | Movement source
| |
− | ! style="width: 300px; background: black; color: white;" | Vehicle on Stop mode
| |
− | ! style="width: 300px; background: black; color: white;" | Vehicle Moving mode
| |
− | |-
| |
− | ! style="text-align: left; vertical-align: top;" | Ignition (recommended)
| |
− | | style="text-align: left; vertical-align: top;" | If ignition (ignition source) is logic low.
| |
− | | style="text-align: left; vertical-align: top;" | If ignition (ignition source) is logic high.
| |
− | |-
| |
− | ! style="text-align: left; vertical-align: top;" | Movement (movement sensor)
| |
− | | style="text-align: left; vertical-align: top;" | Internal movement sensor does not detect movement.
| |
− | | style="text-align: left; vertical-align: top;" | Internal movement sensor detects movement.
| |
− | |-
| |
− | ! 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.
| |
− | | style="text-align: left; vertical-align: top;" | GPS fix is available and vehicle speed is higher than 5 km/h.
| |
− | |-
| |
− | | style="text-align: left; vertical-align: top;" colspan=2 | While GPS fix is unavailable, Object Motion Detection Settings are working like in Msensor mode.
| |
− | |-
| |
− | ! style="text-align: left; vertical-align: top;" | CAN speed
| |
− | | style="text-align: left; vertical-align: top;" | If speed {{{txt_obd2|from BT OBDII dongle }}}is equal to 0 km/h.
| |
− | | style="text-align: left; vertical-align: top;" | If speed {{{txt_obd2|from BT OBDII dongle }}}from BT OBDII dongle is higher than 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 (as defined by configured movement source) or ignition (as defined by configured ignition source) is detected. It allows filtering GPS jumps when the object is parked (not moving) and GPS position is still traced. | | ''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 (as defined by configured movement source) or ignition (as defined by configured ignition source) is detected. It allows filtering GPS jumps when the object is parked (not moving) and GPS position is still traced. |