Changes

*Server Response Timeout is used to set time period waiting for response from server side.  

*Server Response Timeout is used to set time period waiting for response from server side.  

*Ping mode, where user can enable and select how frequent device will send packets to inform server about active data link. It works when device did not send any records to server in defined time period.

*Ping mode, where user can enable and select how frequent device will send packets to inform server about active data link. It works when device did not send any records to server in defined time period.

*Static navigation settings, where user can turn static navigation on or off. Additional, user can chose from what source (movement or ignition) static navigation can be deactivated/activated;

*Static navigation settings, where user can turn static navigation on or off. Additional, user can chose from what source (movement or ignition) static navigation can be deactivated/activated. 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 on 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 (is 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 on 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 (is not moving) and GPS position is still traced.  

*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.