View source for FMB640 System settings

System settings have following configurable parameters:
System settings have 14 configurable parameters: 
*Sleep settings, where user can choose sleep mode; 
*GNSS Source, where user can pick any or all satellite systems to use. More selections might improve tracking quality
*Analog Input value range, where user can choose analog input range 10 V or 30 V (10 V range for now works same as 30 V range). 
*AIN4/DOUT4 Mode, user can select on of 2 options to define which way 18th pin (from Figure 5) will work. 
*J1708 settings used to enable/disable following vehicle bus standard used for communication.
*Odometer Source settings, where user can select one of the options for odometer counting. There are 5 possible options: GNSS, LVCAN, ALLCAN, FMS and KLINE.
*Speed source settings are used to declare what technology will be used for vehicle speed measurement
*Records Settings, where user can enable or disable records when GPS is not available (no time synchronization). There are additional parameters for records saving: memory selection and sorting option to define where records will be saved and in what order they will be sent.
*Open Link Timeout is used to set timeout of link between FMB640 and AVL application termination. If FMB640 has already sent all records it waits for new records before closing link (except Deep Sleep mode, more information in Deep Sleep mode chapter). If new records are generated in the period of this timeout, and minimum count of timer to send is reached, they are sent to AVL application. This option is useful when GSM operator charge money for link activation.
*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.
•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. 
*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. 



* Object motion detection settings, where user can configure {{{txt_num|4}}} ways how {{{model|FMB640}}} detects movement and change its working mode (for more information refer to section [[FMB640 Data acquisition settings|Data acquisition settings]]). Other functionalities that depend on movement source are: power manager, fuel consumption and trip;
* ''Static Navigation Settings'', where user can turn static navigation on or off. Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation;
* Records settings (no time synchronization), where user can enable or disable records when GPS is not available;
* ''GNSS Source'' settings, where user can choose the necessary satellite system(s);
* ''LED Indication'', where user can turn on or off the indication LEDs;
* ''Analog Input Value Range'', where user can choose analog input range of 10 V or 30 V;}}}
* ''Time Synchronization'' settings, where user can choose which source(s) to use for {{{model|FMB640}}} 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.

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

{{{pic_system|[[Image:FMB640_System.png|800px|center]]}}}

In ''GNSS Source'' settings user can configure which GNSS system(s) to use.<br/>User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together. Examples of non-configurable GNSS source combinations are:
* GLONASS + BeiDou;
* Galileo + GLONASS + BeiDou;
* GPS + GLONASS + BeiDou;
* GPS + Galileo + GLONASS + BeiDou.

{| 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
|-
|}