FMC800 System settings: Difference between revisions
no edit summary
(Created page with "{{Template:FMX0 System settings|model=FMC800 |analog_input = |txt_din3 = |input_mode = |txt_autocal = }} Category:FMC800 Configuration") |
No edit summary |
||
| Line 1: | Line 1: | ||
{{ | System settings have the following configurable parameters: | ||
| | ==System Settings== | ||
| | {{{movement|===Movement Source=== | ||
| | ------------------ | ||
| | Movement source will be used to determine when a vehicle is on stop or moving.<br> | ||
}} | Possible movement sources: | ||
[[ | {{{img_mov|[[Image:Movement_source.gif|right|300px]]}}} | ||
* '''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; | |||
* '''Accelerometer''' (movement) - if accelerometer detects movement, Vehicle MOVING mode is used; if there is no movement detected, Vehicle on STOP mode is used; | |||
* '''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; | |||
{{{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;}}} | |||
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=== | |||
------------------ | |||
[[Image:Led_indication.gif|right|300px]] | |||
This feature will be used to indicate device status and navigate them.<br></br> | |||
'''Note:''' If this feature is enabled, you can check LEDs behavior '''[[{{{model|FMC800}}} LED status|here]]'''. | |||
===GNSS Source=== | |||
------------------ | |||
In ''GNSS Source'' settings user can configure which GNSS system(s) to use.<br /> | |||
{{{GNSS|[[Image:GNSS_source.gif|right|300px]]}}} | |||
'''List of configurable GNSS sources:''' | |||
{{{txt_GNSS_enable|* GPS only | |||
* GPS + BeiDou | |||
* GPS + GLONASS | |||
* GPS + Galileo + GLONASS}}} | |||
{{{battery_charge|===Battery Charge Mode=== | |||
------------------ | |||
In ''Battery Charge Mode'' settings user can choose when battery will be charged.<br> | |||
[[Image:Battery_charge.gif|right|300px]] | |||
Possible options: | |||
* '''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; | |||
* '''Always''' - enables charging all the time (even if any sleep mode is active).}}} | |||
===Data Protocol=== | |||
------------------ | |||
[[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> | |||
==Static Navigation Settings== | |||
[[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== | |||
[[Image:Sleep_mode.gif|right|300px]] | |||
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|FMC800}}} Sleep modes#GPS Sleep mode|GPS Sleep]]''', '''[[{{{model|FMC800}}} Sleep modes#Deep Sleep mode|Deep Sleep]]''', '''[[{{{model|FMC800}}} Sleep modes#Online Deep Sleep mode|Online Deep Sleep]]''' and '''[[{{{model|FMC800}}} 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|FMC800}}} Sleep modes|'''here''']].<br></br> | |||
==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:FMX0_Ignition.gif|right|300px]]}}} | |||
{{{ignition_source|Possible ignition sources: | |||
* '''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></br> }}} | |||
Ignition status is used in power management and the following functionalities: [[{{{model|FMC800}}} Features settings#Eco/Green Driving|Eco/Green Driving]], [[{{{model|FMC800}}} Accelerometer Features settings#Excessive Idling|Excessive Idling]], Fuel Consumption, [[{{{model|FMC800}}} Features settings#Over Speeding|Over Speeding]], [[{{{model|FMC800}}} Accelerometer Features settings#Towing Detection|Towing Detection]] and [[{{{model|FMC800}}} Trip/Odometer settings|Trip]].<br> | |||
<!--'''Note:''' Object motion detection settings, where user can configure {{{txt_num|4}}} ways how {{{model|FMC800}}} 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=== | |||
------------------ | |||
[[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> | |||
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> | |||
==Accelerometer Auto Calibration== | |||
[[File:Autocalibration_new.gif|right|300px]] | |||
Users can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: | |||
* '''Once''' – calibrate one time only. | |||
* '''Continuous''' – continuously analyzes current data and re-calibrates if needed. | |||
<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. | |||