Changes

Template:FMU System settings (view source)

Revision as of 14:47, 30 March 2020

3,095 bytes added ,  14:47, 30 March 2020
no edit summary
Line 1: Line 1: −
System settings have following configurable parameters:
+
System settings have the following configurable parameters:
−
* ''Sleep Settings'', where user can choose sleep mode;{{{txt_tmt_wipe|
+
===Sleep Settings===
−
* ''Ignition Source'', where 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 Ignition source. When the device detects movement, Ignition status will change to 1, regardless that DIN1 value is 0. User can select movement start and movement stop delay time - those parameters are used when 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;
+
Sleep Settings, where user can choose sleep mode;{{{txt_tmt_wipe|
 +
===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;
 
* 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;}}}
 
* 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;}}}
−
* ''Static Navigation Settings'', where user can turn static navigation on or off{{{txt_tmt_wipe|. Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation}}};
+
 
−
* Records settings, where user can enable or disable records when GPS is not available (no time synchronization);
+
===Static Navigation Settings===
−
* ''GNSS Source'' settings, where user can choose the necessary satellite system(s);
+
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}}};
 +
 
 +
*Records settings, where user can enable or disable records when GPS is not available (no time synchronization);
 +
 
 +
===GNSS Source===
 +
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;
 
* {{{txt_tmt_mod1|''LED Indication'', where user can turn on or off the indication LEDs;
−
* ''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|
+
===Battery Charge Mode===
−
* ''Data Protocol'', where user can choose which protocol version to use for data sending to server;
+
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);}}}
−
* ''Analog Input Value Range'', where user can choose analog input range of 10 V or 30 V;}}}
+
{{{txt_fmb0|{{{AIN_value_range|
−
* ''Time Synchronization'' settings, where 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). User can select which NTP server (it is possible to configure up to two servers) and what time period to use to resynchronize time.
+
===Analog Input Value Range===
−
* ''Accelerometer Auto Calibration'', where user can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <span style=color:#F6A83E>Disable</span> – do not use auto calibration feature (sends AXES raw data), <span style=color:#F6A83E>Once</span> – calibrate one time only, <span style=color:#F6A83E>Every Trip</span> – launch auto calibration every trip (note: trip function must be enabled! ). '''''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). Under Gravity Filter settings, user can choose: <span style=color:#F6A83E>Disabled</span> – do not remove GRAVITY component from AXL/Crash data, <span style=color:#F6A83E>Enabled</span> – remove GRAVITY component from AXL/Crash.
+
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%;">
 +
<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>
 
{{{txt_tmt_mod2|
 
{{{txt_tmt_mod2|
 
{{{template_link|}}}
 
{{{template_link|}}}
 
}}}
 
}}}
−
   
''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.
 
''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.
 +
{{{txt_mod_img|
 +
[[Image:FMB System settings.PNG|800px|none]]
 +
}}}
 +
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:
   −
{{{pic_system|[[Image:FMB GPRS-settings-{{{model|FMU1YX}}}.jpg|800px|none]]}}}
+
*GLONASS + BeiDou;
−
 
+
*Galileo + GLONASS + BeiDou;
−
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:
+
*GPS + GLONASS + BeiDou;
−
* GLONASS + BeiDou;
+
*GPS + Galileo + GLONASS + BeiDou.
−
* Galileo + GLONASS + BeiDou;
  −
* GPS + GLONASS + BeiDou;
  −
* GPS + Galileo + GLONASS + BeiDou.
      
List of configurable GNSS sources:
 
List of configurable GNSS sources:
Line 30: Line 92:  
{| class="wikitable"
 
{| class="wikitable"
 
|+
 
|+
−
! style="width: 250px; background: black; color: white;" | Selected source(s)
+
! style="width: 250px; background: black; color: white;" |Selected source(s)
−
! style="width: 100px; background: black; color: white;" | ID
+
! style="width: 100px; background: black; color: white;" |ID
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | BeiDou only
+
! style="text-align: left; vertical-align: top;" |BeiDou only
−
| style="text-align: left; vertical-align: top;" | 01
+
| style="text-align: left; vertical-align: top;" |01
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | GLONASS only
+
! style="text-align: left; vertical-align: top;" |GLONASS only
−
| style="text-align: left; vertical-align: top;" | 02
+
| style="text-align: left; vertical-align: top;" |02
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | Galileo only
+
! style="text-align: left; vertical-align: top;" |Galileo only
−
| style="text-align: left; vertical-align: top;" | 04
+
| style="text-align: left; vertical-align: top;" |04
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | Galileo + BeiDou
+
! style="text-align: left; vertical-align: top;" |Galileo + BeiDou
−
| style="text-align: left; vertical-align: top;" | 05
+
| style="text-align: left; vertical-align: top;" |05
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | Galileo + GLONASS
+
! style="text-align: left; vertical-align: top;" |Galileo + GLONASS
−
| style="text-align: left; vertical-align: top;" | 06
+
| style="text-align: left; vertical-align: top;" |06
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | GPS only
+
! style="text-align: left; vertical-align: top;" |GPS only
−
| style="text-align: left; vertical-align: top;" | 08
+
| style="text-align: left; vertical-align: top;" |08
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | GPS + BeiDou
+
! style="text-align: left; vertical-align: top;" |GPS + BeiDou
−
| style="text-align: left; vertical-align: top;" | 09
+
| style="text-align: left; vertical-align: top;" |09
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | GPS + GLONASS  
+
! style="text-align: left; vertical-align: top;" |GPS + GLONASS
−
| style="text-align: left; vertical-align: top;" | 10
+
| style="text-align: left; vertical-align: top;" |10
 
|-
 
|-
−
! style="text-align: left; vertical-align: top;" | GPS + Galileo
+
! style="text-align: left; vertical-align: top;" |GPS + Galileo
−
| style="text-align: left; vertical-align: top;" | 12
+
| 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;" |GPS + Galileo + BeiDou
−
| style="text-align: left; vertical-align: top;" | 13
+
| 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;" |GPS + Galileo + GLONASS
−
| style="text-align: left; vertical-align: top;" | 14
+
| style="text-align: left; vertical-align: top;" |14
 
|-
 
|-
 
|}
 
|}
Retrieved from "https://wiki.teltonika-gps.com/view/Special:MobileDiff/55953"

Navigation menu