| Line 127: |
Line 127: |
| | ==Time Synchronization== | | ==Time Synchronization== |
| | ''Time Synchronization settings'' will be use to set how device time will be re-synchronize. | | ''Time Synchronization settings'' will be use to set how device time will be re-synchronize. |
| − | ===Old Time Synchronization Settings*=== | + | |
| | + | === Time Synchronization Settings*=== |
| | ------------------ | | ------------------ |
| | [[Image:Time_synchronization.gif|right|300px]] | | [[Image:Time_synchronization.gif|right|300px]] |
| Line 138: |
Line 139: |
| | ''NTP server 1'' and ''NTP Server 2'' let the user select which NTP server (s) will be used to re-synchronize time.<br></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 | | '''*''' 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>
| |
| − | {{{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.
| |
| − | }}}
| |
