Line 1: |
Line 1: |
| System settings have the following configurable parameters: | | System settings have the following configurable parameters: |
− | ===Sleep Settings=== | + | ==System Settings== |
− | Sleep Settings, where user can choose sleep mode;{{{txt_tmt_wipe|
| + | ===Movement Source=== |
− | ===Ignition Source=== | + | ------------------ |
− | Ignition Source, where the user can choose an ignition source from digital input 1, power voltage{{{txt_fmb0|, engine RPM}}} and accelerometer. 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. Example: DIN1 and Accelerometer are selected as the Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. Users can select movement start and movement stop delay time - those parameters are used when the accelerometer is selected as an ignition source. Ignition status is used in power management and the following functionalities: eco-driving, excessive idling, fuel consumption, over speeding, towing and trip;
| + | Movement source will be used to determine when a vehicle is on stop or moving.<br> |
− | * Object motion detection settings, where user can configure {{{txt_num|4}}} ways how {{{model|FMU1YX}}} 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;}}} | + | Possible movement sources: |
− | | + | [[Image:Movement source.png|right|300px]] |
− | ===Static Navigation Settings===
| + | * '''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; |
− | Static Navigation Settings, where users can turn static navigation on or off{{{txt_tmt_wipe|. Additionally, the user can choose which source (movement or ignition) is used to activate/deactivate static navigation}}};
| + | * '''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; |
− | *Records settings, where user can enable or disable records when GPS is not available (no time synchronization);
| + | {{{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> |
− | ===GNSS Source===
| + | '''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: |
− | GNSS Source settings, where user can choose the necessary satellite system(s);
| |
− | | |
− | * {{{txt_tmt_mod1|''LED Indication'', where user can turn on or off the indication LEDs; | |
− | ===Battery Charge Mode===
| |
− | Battery Charge Mode, where user can choose when battery will be charged: <span style=color:#F6A83E>On Need</span> (battery will be charged anytime when it needs to be charged) and <span style=color:#F6A83E>After Ignition ON</span> (battery will be charged only when ignition is on);}}}
| |
− | {{{txt_fmb0|{{{AIN_value_range|
| |
− | ===Analog Input Value Range===
| |
− | Analog Input Value Range where user can choose analog input range of 10 V or 30 V;}}}
| |
− | {{{Input_mode|===Input Mode===
| |
− | Input Mode lets user to choose if configurable connector will work as digital/analog input or as ground sense.}}}
| |
− | <br>}}}
| |
− | ===Data Protocol===
| |
− | Data Protocol where user can choose which protocol version to use for data sending to the server;
| |
− | ===Time Synchronization{{{txt_hide_tmt250|*}}}===
| |
− | Time Synchronization settings, where the user can choose which source(s) to use for {{{model|FMU1YX}}} 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). Users can select which NTP server (it is possible to configure up to two servers) and what time period to use to resynchronize time. <br>
| |
− | {{{txt_hide_tmt250|
| |
− | *using 03.25.13 or older firmware
| |
− | }}} | |
− | ===New time synchronization method implementation{{{txt_hide_tmt250|*}}}===
| |
− | 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 resynchronization 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 resynchronization.<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 resynchronization time is reached (if the resynchronization time is set to 0 – no NTP sync is performed at all). Time synchronization by NITZ can occur at any time.
| |
− | {{{txt_hide_tmt250|
| |
− | * using 03.25.14 or newer firmware<br>
| |
− | }}}
| |
− | [[image:Timesyncflowchart.png|center]]
| |
− | | |
− | | |
− | === Accelerometer Auto Calibration === | |
− |
| |
− | [[File:Accelerometer auto calibration.PNG|thumb|right]]
| |
− | <br>
| |
− | User 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:
| |
− | | |
− | <br> * <span style="color:#F6A83E">Disable</span> – do not use auto calibration feature (sends AXES raw data).
| |
− | <br> * <span style="color:#F6A83E">Once</span> – calibrate one time only.
| |
− | <br> * <span style="color:#F6A83E">Continuous</span> – continuously analyzes current data and re-calibrates if needed.
| |
− | | |
− | <br> '''''Important!''''' If Auto calibration is disabled, device should be mounted according User manual for EcoDriving feature to work properly. If enabled, AXES will be reoriented to VEHICLE axes according User manual (+X – Forward, +Y – Left, +Z – Down).
| |
− | | |
− | <br> Gravity filter substracts gravity from vector when devices is calibrated or if auto-calibration is disabled (default values). Gravity is only removed when gravity filter is enabled.
| |
− | <br> | |
− | Filter settings, user can choose:
| |
− | | |
− | <br> * <span style="color:#F6A83E">Disabled</span> – do not remove GRAVITY component from AXL/Crash data. | |
− | <br> * <span style="color:#F6A83E">Enabled</span> – remove GRAVITY component from AXL/Crash.
| |
− | <br>
| |
− | <br>
| |
− | '''Note:''' In FM*0YX devices autocalibration is set by default and it is not configurable via configurator. Device connected to OBD port is not positioned accoring to the vehicle axis and in this case autocalibration is must. | |
− | | |
− | ===Multiple Movement Sources===
| |
− | 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%;"> | | <table class="nd-othertables_2" style="width: 68%;"> |
| <tr> | | <tr> |
Line 74: |
Line 22: |
| </tr> | | </tr> |
| </table> | | </table> |
− | {{{txt_tmt_mod2| | + | ===Speed Source=== |
− | {{{template_link|}}} | + | ------------------ |
− | }}} | + | [[Image:Speed source.png|right|300px]] |
− | ''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. | + | Speed source will be used to determine which speed source to use.<br></br> |
− | {{{txt_mod_img| | + | '''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. |
− | [[Image:FMB System settings.PNG|800px|none]] | + | ===Records Saving/Sending Without TS=== |
− | }}} | + | ------------------ |
− | 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:
| + | This feature will be used to save and dend records to server without time sinchronization.<br> |
| + | [[Image:Records saving sending without TS.png|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. |
| + | ===LED Indication=== |
| + | ------------------ |
| + | [[Image:LED Indication.png|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|FMU1YX}}} LED status|here]]'''. |
| + | ===GNSS Source=== |
| + | ------------------ |
| + | In ''GNSS Source'' settings user can configure which GNSS system(s) to use.<br />User has a choice to use only one system GPS 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: |
| + | {{{fmb208|[[Image:GNSS source.png|right|300px]]}}} |
| + | * GLONASS + BeiDou; |
| + | * Galileo + BeiDou; |
| + | * Galileo + GLONASS; |
| + | * Galileo + GLONASS + BeiDou; |
| + | * GPS + Galileo; |
| + | * GPS + GLONASS + BeiDou; |
| + | * GPS + Galileo + BeiDou; |
| + | * GPS + Galileo + GLONASS + BeiDou.<br></br> |
| + | '''List of configurable GNSS sources:''' |
| + | * GPS only; |
| + | * GPS + BeiDou; |
| + | * GPS + GLONASS; |
| + | * GPS + Galileo + GLONASS. |
| + | ===Battery Charge Mode=== |
| + | ------------------ |
| + | In ''Battery Charge Mode'' settings user can choose when battery will be charged.<br> |
| + | [[Image:Battery Charge Mode.png|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). |
| + | {{{analog_input|===Analog Input Value Range=== |
| + | ------------------ |
| + | [[Image:Analog input value range.png|right|300px]] |
| + | In ''Analog Input Value Range'' settings user can choose an analog input range of 10 V or 30 V.<br></br><br></br>}}} |
| + | ===Data Protocol=== |
| + | ------------------ |
| + | [[Image:Data Protocol.png|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> |
| + | {{{input_mode|===Input Mode=== |
| + | ------------------ |
| + | [[Image:Input mode.png|right|300px]] |
| + | In ''Data Protocol'' settings user can choose which configurable input will be use: ''DIN2/AIN1'' or ''[[FMB130_Negative_Input_Usage_Scenario|Ground Sense]]''.<br></br><br></br>}}} |
| + | ==Static Navigation Settings== |
| + | [[Image:Static Navigation Settings.png|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.png|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|FMU1YX}}} Sleep modes#GPS Sleep mode|GPS Sleep]]''', '''[[{{{model|FMU1YX}}} Sleep modes#Deep Sleep mode|Deep Sleep]]''', '''[[{{{model|FMU1YX}}} Sleep modes#Online Deep Sleep mode|Online Deep Sleep]]''' and '''[[{{{model|FMU1YX}}} 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|FMU1YX}}} Sleep modes|'''here''']].<br></br><br></br> |
| + | ==Ignition Source== |
| + | Ignition source will be used to determine ignition of vehicle.<br> |
| + | {{{img_ignition|[[Image:Ignition source.png|right|300px]]}}} |
| + | Possible ignition sources: |
| + | * '''DIN 1''' (Digital Input 1) - if ''DIN1'' is 1 - ignition is ON; if ''DIN1'' value is 0 - ignition is OFF;}}} |
| + | * '''Power Voltage''' - if voltage is between High Voltage Lever and Low Voltage Level (below ''Ignition Settings'' options) - ignition is ON; if voltage is higher than High Voltage Lever 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> |
| + | {{{txt_din3|* '''DIN 3''' (Digital Input 3) - if ''DIN3'' is 1 - ignition is ON; if ''DIN3'' value is 0 - ignition is OFF;}}} |
| + | '''Example:''' DIN1 and Accelerometer are selected as the Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. Users can select movement start and movement stop delay time - those parameters are used when the accelerometer is selected as an ignition source.<br> |
| + | Ignition status is used in power management and the following functionalities: [[{{{model|FMU1YX}}} Features settings#Eco/Green Driving|Eco/Green Driving]], [[{{{model|FMU1YX}}} Accelerometer Features settings#Excessive Idling|Excessive Idling]], Fuel Consumption, [[{{{model|FMU1YX}}} Features settings#Over Speeding|Over Speeding]], [[{{{model|FMU1YX}}} Accelerometer Features settings#Towing Detection|Towing Detection]] and [[{{{model|FMU1YX}}} Trip/Odometer settings|Trip]].<br> |
| + | <!--'''Note:''' Object motion detection settings, where user can configure {{{txt_num|4}}} ways how {{{model|FMU1YX}}} 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 settings.png|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 older.png|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> |
| + | {{{txt_autocal|==Accelerometer Auto Calibration== |
| + | [[File:Accelerometer auto calibration.PNG|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. |
| | | |
− | *GLONASS + BeiDou;
| + | <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). |
− | *Galileo + GLONASS + BeiDou;
| |
− | *GPS + GLONASS + BeiDou;
| |
− | *GPS + Galileo + GLONASS + BeiDou.
| |
| | | |
− | List of configurable GNSS sources:
| + | <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> |
− | {| class="wikitable"
| + | Filter settings, user can choose: |
− | |+
| + | * '''Disabled''' – do not remove GRAVITY component from AXL/Crash data. |
− | ! style="width: 250px; background: black; color: white;" |Selected source(s)
| + | * '''Enabled''' – remove GRAVITY component from AXL/Crash. |
− | ! style="width: 100px; background: black; color: white;" |ID
| + | <br> |
− | |-
| + | '''Note:''' In [[{{{model|FMU1YX}}}]] 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. |
− | ! 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
| |
− | |-
| |
− | |}
| |