55
edits
Changes
no edit summary
==System Settings==
==System Settings==
{{#if:{{{MM_Movement_source|}}}
{{#if:{{{MM_Movement_source|}}}
|
|
|====Movement Source====
|===Movement Source===
User can select which source will be used to determine when vehicle is on stop or moving. When multiple are selected, if any of selected are active, Vehicle MOVING mode is used.
User can select which source will be used to determine when vehicle is on stop or moving. When multiple are selected, if any of selected are active, Vehicle MOVING mode is used.
Available movement source:
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right]]
* Ignition: checks ignition settings which depends on Ignition Source settings;
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;
* Accelerometer: movement detection depends on Accelerometer Delay Settings;
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.
When multiple source are selected, if any of selected are active, Movement is detected.
}}
}}
{{#if:{{{TFT_can|}}}
{{#if:{{{TFT_can|}}}
|
|
|====Speed source====
|===Speed source===
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.
[[Image:speed_source.PNG]]
Available speed source: GNSS or CAN.
If CAN Speed source enabled, it will retrieve speed from CAN data, but if the speed value from CAN data is 0, speed will be retrieved from GNSS data if Position Fix acquired, even though it is not configured.<br>
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]
}}
}}
{{#if:{{{AT_no_show|}}}
{{#if:{{{TAT100_no_show|}}}
|
|
|====Records settings====
|===Records settings===
Here user can enable or disable records when GPS is not available (no GPS fix). <br>
Here user can enable or disable records when GPS is not available (no GPS fix). <br>
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br>
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br>
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.
}}
}}
{{#if:{{{TFT_show|}}}
{{#if:{{{TFT_system_settings|}}}
|
|
|====PDOP filter====
|===PDOP filter===
User can choose to enable or disable the PDOP filter. This feature allows to discard GNSS module output data if PDOP (Position Dilution of Precision) value is above selected threshold.
User can choose to enable or disable the PDOP filter. This feature allows to discard GNSS module output data if PDOP (Position Dilution of Precision) value is above selected threshold.
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.
}}
}}
{{#if:{{{TFT_show|}}}
{{#if:{{{TFT_system_settings|}}}
|
|
|====Input/Output Mode====
|===Input/Output Mode===
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:
*Digital input 3 and Digital input 4 (value:5),
*Digital input 3 and Digital input 4 (value:5),
*Digital output 1 and Digital output 2 (value:10).
*Digital output 1 and Digital output 2 (value:10).
}}
}}
{{#if:{{{MM_LED_indication|}}}
{{#if:{{{MM_LED_indication|}}}
|
|
|====LED Indication====
|===LED Indication===
User can turn on or off the indication LEDs.
User can turn on or off the indication LEDs.
}}
}}
{{#if:{{{AT_no_show|}}}
|
|===GNSS Source settings===
User can configure which GNSS system(s) to use.<br />
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.
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.
*GPS + GLONASS + Galileo.
*GPS + GLONASS + Galileo.
}}
{{#if:{{{TST_battery_charge_mode|}}}
{{#if:{{{TST_battery_charge_mode|}}}
|
|
|====Battery Charge Mode====
|===Battery Charge Mode===
Here user can change battery charger settings, where charging is allowed.
Here user can change battery charger settings, where charging is allowed.
Battery will be charged: '''''On Need''''' (battery will be charged anytime when it needs to be charged) and '''''After Ignition ON''''' (battery will be charged only when ignition is on).
Battery will be charged: '''''On Need''''' (battery will be charged anytime when it needs to be charged) and '''''After Ignition ON''''' (battery will be charged only when ignition is on).
Three charging modes is available:
* On neeed: charger enabled if external voltage is higher than 5.05 voltage and Battery Voltage is below 3.90V. Charging is disabled if device enters any sleep mode.
* After Ignition On: charger enabled after ignition is turned on, except if the battery is fully charged or 10-minute timeout has not passed since the device was turned on for faster FIX receiving.
* Always: charger is always enabled, except if the battery is fully charged or 10-minute timeout has not passed since the device was turned on for faster FIX receiving.
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]
}}
}}
{{#if:{{{TFT_show|}}}
{{#if:{{{TFT_system_settings|}}}
|
|
|====Analog Input Value Range====
|===Analog Input Value Range===
User can choose analog input range of 15 V or 150 V.
User can choose analog input range of 15 V or 150 V.
Input range used to determine lowest voltage for DIN1 and DIN2 activation.
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]
Lowest voltage to enabled DIN for 15V range - 2.5V
Lowest voltage to enabled DIN for 150V range - 9V
}}
{{#if:{{{TFT_show|}}}
|
|===DOUT Overcurrent protection===
DOUTs have overcurrent protection that triggers after the current exceeds 300 mA. This protection works by generating pulses on the hardware. When the firmware detects at least 20 impulses on a DOUT it turns off that DOUT for 5 minutes. During this time all scenarios that try to turn this DOUT on will fail.
}}
}}
{{#if:{{{Data_protocol|}}}
{{#if:{{{Data_protocol|}}}
|
|
|====Data Protocol====
|===Data Protocol===
User can choose which protocol version to use for data sending to server.
User can choose which protocol version to use for data sending to server.
*Codec 8 supports up to 255 AVL ID;
*Codec 8 supports up to 255 AVL ID;
*Codec 8 Extended supports up and above 255 AVL ID.
*Codec 8 Extended supports up and above 255 AVL ID.
}}
{{#if:{{{PT_Power_on|}}}
|
|===Power On By USB/Charger===
[[Image:PT Power on by usb.png|right]]
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br>
Device supports two working modes: normal mode, where the device works as usual, and charging mode, which is entered when ''Power On By USB/Charger'' parameter is <b>disabled</b>. To enter normal mode, device can be turned on by power button or by USB charger, if ''Power On By USB/Charger'' parameter is set to <b>Enable</b>.
}}
}}
|}
{{#if:{{{PT_Power_on|}}}
|
|===Continuous Charging Mode===
[[Image:PT continuous charging.png|right]]
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br>
Battery protection mode to extend battery life. Should only be used when device is permanently connected to external charger. When enabled charge current is reduced preventing charging to maximum voltage. This results in lower battery temperature and extended battery lifetime. Please note, this also increases battery charge time and reduces overall charge to around 85%.
}}
{|
{|
{{#if:{{{PT_Power_on|}}}
{{#if:{{{Location_settings|}}}
|
|
|====Power On By USB/Charger====
|==Location Settings==
[[Image:Location_settings_{{{model|X}}}.png|right]]
}}
}}
|}
|}
{|
{|
{{#if:{{{LBS_tracking|}}}
{{#if:{{{LBS_tracking|}}}
|
|
|==Tracking with LBS==
|===Location Source===
<b>LBS</b> - location based services. It helps us to find the approximate location without using a GNSS, but using cell towers information instead. Device cannot find the location using LBS by itself, approximate location is calculated on the server side according to the information provided by the device. Therefore, to locate a unit by LBS the device should send at least 4 parameters: mcc, mnc, lac, cell ID.
<b>LBS</b> - location based services. It helps us to find the approximate location without using a GNSS, but using cell towers information instead. Device cannot find the location using LBS by itself, approximate location is calculated on the server side according to the information provided by the device. Therefore, to locate a unit by LBS the device should send at least 4 parameters: mcc, mnc, lac, cell ID.
*If <b>LBS</b> is selected as a location source, the device will send information about the cell towers to the server and <b>will not use GNSS</b>.
*If <b>LBS</b> is selected as a location source, the device will send information about the cell towers to the server and <b>will not use GNSS</b>.
*If <b>GNSS or LBS</b> is selected, device will use GNSS if the satellites are visible, if not - it will start sending cell towers information to the server, which will be able to calculate the approximate location using LBS.
*If <b>GNSS or LBS</b> is selected, device will use GNSS if the satellites are visible, if not - it will start sending cell towers information to the server, which will be able to calculate the approximate location using LBS.
Also, <b>GSM Cell ID</b> and <b>Active GSM Operator</b> should have at least Low priority in I/O settings.
Also, <b>GSM Cell ID</b> and <b>Active GSM Operator</b> should have at least Low priority in I/O settings.<br>[[Image:LBS IO.jpg|left]]
[[Image:LBS IO.jpg|left]]
<br><br><br><br>
<br>
}}
<br>
|}
<br>
<br>
{|
{{#if:{{{Location_settings|}}}
|
|===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.
List of configurable GNSS sources:
*GPS only;
*GPS + BeiDou;
*GPS + GLONASS;
*GPS + GLONASS + Galileo.
}}
}}
|}
|}
{|
{|
{{#if:{{{TAT100_show|}}}
{{#if:{{{AT_show|}}}
|
|
|==GNSS control==
|===GNSS control===
User can manually turn ON/OFF the GNSS module. For example, if button 'Turn off GNSS' is pressed and device is trying to acquire GNSS fix for a record, it will turn GNSS back on. If GNSS module is turned ON using 'Turn on GNSS' button, it will be active for undefined period of time until USB is disconnected and device is going to sleep, record sending is finished or the 'Turn off GNSS' button is pressed again.
User can manually turn ON/OFF the GNSS module. For example, if button 'Turn off GNSS' is pressed and device is trying to acquire GNSS fix for a record, it will turn GNSS back on. If GNSS module is turned ON using 'Turn on GNSS' button, it will be active for undefined period of time until USB is disconnected and device is going to sleep, record sending is finished or the 'Turn off GNSS' button is pressed again.
}}
}}
|}
|}
{|
{|
{{#if:{{{TAT100_show|}}}
{{#if:{{{AT_show|}}}
|
|
|==Coordinate acquisition timeout==
|===Coordinate acquisition timeout===
The configured time adds a delay when the coordinates of the device are taken to stabilize and ensure accuracy. Important thing to note that TAT100 can take up to 180 seconds to get the GPS fix and the configured timeout would only go after the GPS fix timeout has finished or the coordinates were received.
The configured time adds a delay when the coordinates of the device are taken to stabilize and ensure accuracy. Important thing to note that TAT100 can take up to 180 seconds to get the GPS fix and the configured timeout would only go after the GPS fix timeout has finished or the coordinates were received.
{|
{|
{{#if:{{{TAT100_show|}}}
{{#if:{{{AT_show|}}}
|
|
|==Static Navigation Settings==
|===Static Navigation Settings===
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.
When enabled the device monitors the accelerometer and registers movement events by configured movement sensitivity. When the device wakes up to save and send a periodic record, and movement was not registered, the device will use the last known coordinates and will generate a record without turning ON the GPS module. However, if there are no last known coordinates, then the device will enable the GPS module and will try to get a new GPS fix.<br />
When enabled the device monitors the accelerometer and registers movement events by configured movement sensitivity. When the device wakes up to save and send a periodic record, and movement was not registered, the device will use the last known coordinates and will generate a record without turning ON the GPS module. However, if there are no last known coordinates, then the device will enable the GPS module and will try to get a new GPS fix.<br />
The functionality is illustrated in the flowchart below:
The functionality is illustrated in the flowchart below:
{|
{|
{{#if:{{{TAT100_no_show|}}}
{{#if:{{{AT_show|}}}
|
|===Movement sensitivity===
This feature sets the sensitivity threshold levels for movement event registration. Higher configured level makes the device “less sensitive” and vice versa. Currently, there are 10 configurable Movement Sensitivity levels. Levels are measured in mG - thousandth parts of the gravitational force equivalent or gravitational acceleration of Earth (9.8 m/s). It means that if Movement Sensitivity is set to 1000 mG, the device has to be free falling, experience fierce stops/accelerations or vibrations to detect movement.<br />
}}
|}
{|
{{#if:{{{TFT_Static_Navigation|}}}
|
|
|==Static Navigation Settings==
|==Static Navigation Settings==
[[Image:Static_navigation_PT.png|right]]
[[Image:Static_navigation_TFT.png|right]]
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. <br />
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. <br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.
<br>
<br>
}}
|}
{|
{{#if:{{{PT_show|}}}
|
|==Static Navigation Settings==
[[Image:Static_navigation_PT.png|right]]
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 is detected. It allows filtering GPS jumps when the object is not moving and GPS position is still traced. <br />
}}
}}
|}
|}
{|
{|
{{#if:{{{TAT100_no_show|}}}
{{#if:{{{GH_section|}}}
|
|==Call Duration Limits==
[[Image:Call duration limits.png|right]]
These is two places for these settings. First one can be found in the SMS \ Calls Settings section. This setting applies to incoming and outgoing calls, except for the keyboard “Call” action and the Amber Alert feature.
[[Image:Cal duration limit2.png|right]]
Second one can be found in the Keyboard section. These settings are only visible when the button action is Call. There is only one parameter per button, so the same parameter applies to all button presses.
}}
|}
{|
{{#if:{{{AT_no_show|}}}
|
|
|==Sleep Mode==
|==Sleep Mode==
<tr style="vertical-align: top; text-align: left;">
<tr style="vertical-align: top; text-align: left;">
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br>
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br>
{{{PT_movement_source|If any of selected movement sources are active, movement mode will be activated. If all selected sources are inactive STOP mode will be enabled. [[Image: PT Sleep exit Source.png]]}}}
{{{PT_movement_source|If any of selected movement sources are active, movement mode will be activated. If all selected sources are inactive STOP mode will be enabled.}}}
</td>
</td>
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td>
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td>
{|
{|
{{#if:{{{TFT_ignition_source|}}}
{{#if:{{{BT/BLE_no_show|}}}
|
|
===BT/BLE module OFF during Sleep modes===
------------------
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.
<br>
From the version, 03.28.XX this new functionality includes new parameters:
*'''Periodic Wakeup''' – if value is greater than zero, device while being in Deep Sleep or Online Deep Sleep, will wake up after defined period for beacon collection. This is mainly should be used when Bluetooth is disabled in sleep.
*'''Bluetooth On While In Sleep'''- by default this parameter value is set to Enable and BT will work as in base functionality. If this value is set to Disable, Bluetooth will be turned off when device goes to Deep Sleep or Online Deep Sleep and will be turned on during Periodic Wakeup or if device enters normal state.
[[Image:PWU.jpg|right|300px]]
</br></br>
Note: In case when during scan after wakeup no BLE devices will be found FMB will be active for configured scan duration time in Bluetooth 4.0 tab. After that timeout FMB will go to sleep state.
<br>
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state and can only wake up if one of the conditions is true:
*Movement is detected by accelerometer (not by the configured movement source);
*External power is applied;
*It is the time to make a new periodic record (new feature);
<br>
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.
}}
}}
|}
|}
{|
{|
{{#if:{{{TAT100_no_show|}}}
{{#if:{{{TFT_show|}}}
|
|
|==Movement Settings==
|==Ignition Source==
[[Image:Accelerometer_delay.PNG|right]]
[[Image:Mob_Ignition_source.png|right]]
User can choose an ignition source from digital input (1, 2 or 3), power voltage, CAN 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. <br>
''For example'', if the '''''Movement Start Delay''''' is set to 1s and '''''Movement Stop Delay''''' to 60s, the movement will be detected after 1s of moving and defined as stopped after 60s when device stopped moving.
''For 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. <br>
Ignition status is used in power management and the following functionalities: Eco/Green driving, Excessive idling, Over speeding, Towing detection and trip.
<br><br><br>
}}
}}
|}
|}
{|
{|
{{#if:{{{TAT100_show|}}}
{{#if:{{{TFT_Accelerometer_Delay|}}}
|
|
|==Movement sensitivity==
|==Accelerometer Delay Settings==
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]
Here the user can set the movement start/stop delays. <br>
''For example'', if the '''''Movement Start Delay''''' is set to 1s and '''''Movement Stop Delay''''' to 60s, the movement will be detected after 1s of moving and defined as stopped after 60s when device stopped moving.
<br>
<table style="border-collapse: collapse; width:50%;" border="1;">
<tr style="text-align: center; background:black; color:white>
<th width="20%">Parameter ID</th>
<th width="30%">Name</th>
<th width="15%">Min Value</th>
<th width="15%">Max Value</th>
<th width="20%">Default Value</th>
</tr>
<tr style="text-align: center;">
<td>19001</td>
<td>Movement Start Delay</td>
<td>1</td>
<td>60</td>
<td>5</td>
</tr>
<tr style="text-align: center;">
<td>19002</td>
<td>Movement Stop Delay</td>
<td>5</td>
<td>300</td>
<td>60</td>
</tr>
</table>
}}
}}
|}
|}
|[[Image:Time_synchronization.PNG|right]]
|[[Image:Time_synchronization.PNG|right]]
User can select which NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.
User can select which NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.
<table style="border-collapse: collapse; width:60%;" border="1;">
<tr style="text-align: center; background:black; color:white>
<th width="15%">Parameter ID</th>
<th width="20%">Name</th>
<th width="15%">Value/Type</th>
<th width="15%">Min Value</th>
<th width="15%">Max Value</th>
<th width="20%">Default Value</th>
</tr>
<tr style="text-align: center;">
<td>901</td>
<td>NTP Resync (hours)</td>
<td>uint8</td>
<td>0</td>
<td>24</td>
<td>3</td>
</tr>
<tr style="text-align: center;">
<td>902</td>
<td>NTP Server 1</td>
<td>char</td>
<td>0</td>
<td>55</td>
<td>avl1.teltonika.lt</td>
</tr>
<tr style="text-align: center;">
<td>903</td>
<td>NTP Server 2</td>
<td>char</td>
<td>0</td>
<td>55</td>
<td>pool.ntp.org</td>
</tr>
</table>
Time synchronization works by waiting a minute on startup to acquire fix and consequently synchronizes the time via GNSS. If the firmware acquires the fix, it starts working in the syncing by GNSS state. This state checks the difference of RTC and GNSS times every second. If the difference of at least 3 seconds persists to be for 5 seconds, the firmware triggers a procedure by GNSS.
After that, the the time difference is still calculated, but the difference is expected to persist for at least 5 minutes to trigger a GNSS time resynchronization. This is done to prevent false GNSS timestamps (such as year 2080 and etc.). If there’s no time difference found, the difference is expected to persist again for a period of 5 seconds later on when calculating. In the case that there is no fix or it is lost during the syncing by GNSS state, the firmware goes to 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 NTP resynchronization time is set to 0, no periodical resynchronization is done in this state. Time synchronization by NITZ can occur any time.
[[File:Time sync chart.png|thumb]]
|}
|}
{|
{|
{{#if:{{{TFT_accelerometer_calibration|}}}
{{#if:{{{GH_TMT_section|}}}
|
|
|==Accelerometer auto calibration==
|==Movement Settings==
[[Image:Accelerometer settings.png|right]]
Here the user can set the movement start/stop delays. <br/>
''For example'', if the '''''Movement Start Delay''''' is set to 1s and '''''Movement Stop Delay''''' to 60s, the movement will be detected after 1s of moving and defined as stopped after 60s when device stopped moving. Accelerometer Sensitivity in Sleep parameter defines how much movement device needs to experience to exit sleep mode. The lower the sensitivity - the more movement is required.
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal
*<code>Normal</code> – recommended value for most users
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal
Changing Accelerometer Sensitivity in Sleep parameter might result in fake movement record or skipped movement events! Only change that if you experience problems with movement detection!
}}
|}
{|
{{#if:{{{TFT_show|}}}
|
|==Accelerometer Auto Calibration==
[[Image:Accelerometer_auto_calibration.PNG|right]]
[[Image:Accelerometer_auto_calibration.PNG|right]]
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/>
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/>
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),
*<code>Disable</code> – do not use Auto Calibration feature (sends AXES raw data),
*<code>Once</code> – calibrate one time only,
*<code>Once</code> – calibrate one time only,
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br />
*<code>Continuous</code> – launch Auto Calibration every trip (note: trip function must be enabled! ). <br />
'''Important!''': If Auto Calibration is disabled, device should be mounted according User manual for Eco/Green driving feature to work properly. If enabled, AXES will be reoriented to VEHICLE axes according User manual (+X – Forward, +Y – Left, +Z – Down). <br />
Under Gravity Filter settings, user can choose:
Under Gravity Filter settings, user can choose:
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.
(An in-depth explanation for the Auto Calibration can be found here)
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:
* X is front.
* Y is left.
* Z is down.
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]
Once vehicle’s axes are calculated, device is considered calibrated.
'''Note''': Moving forward along any axis will generate negative values. This means acceleration will generate -X values, accordingly braking will generate X values. Same goes for other axes.
Commands that can be used during calibration:
<table style="border-collapse: collapse; width:65%;" border="1;">
<tr style="text-align: center; background:black; color:white>
<th width="25%">Command</th>
<th width="15%">Response</th>
<th width="60%">Description</th>
</tr>
<tr style="text-align: center;">
<td>auto_calibrate:set</td>
<td>Yes</td>
<td>Request Auto Calibration task start</td>
</tr>
<tr style="text-align: center;">
<td>auto_calibrate:get</td>
<td>Yes</td>
<td>Request calibration info (time, ground vector, side vector)</td>
</tr>
<tr style="text-align: center;">
<td>auto_calibrate:clear</td>
<td>Yes</td>
<td>Request calibration clear from flash and stop calibration task</td>
</tr>
<tr style="text-align: center;">
<td>auto_calibrate:status</td>
<td>Yes</td>
<td>Request calibration status and calibration task status</td>
</tr>
</table>
}}
|}
{|
{{#if:{{{TFT_show|}}}
|
|=== Mounting Guidelines ===
[[File:Screenshot 2024-03-04 at 09-01-13 tft100-mounting-guidelines.jpg (JPEG Image 900 × 600 pixels).png|thumb]]
The device should be mounted according to the picture below. Logo/Antenna must be facing up.
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
}}
}}
|}
|}
|==Tracking Mode==
|==Tracking Mode==
[[Image:Tracking_mode.png|right]]
[[Image:Tracking_mode.png|right]]
<b>Power Saving Mode</b> <br>
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br>
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br>
The purpose of this feature is to reduce power consumption and its main function is to turn off the GPS module when the device is stationary. For power saving functionality to run several conditions need to be met, one of them: ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds. In device cold start state the GPS module is turned on for 180 sec. If GPS fix is obtained before this timeout elapses, GPS module turns off and a record is saved, and if not, no record will be saved. Before each new record saving period is expired the device is constantly checking for movement and if no motion has been detected, the GPS module does not turn on and the device waits for a periodic record to be eventually saved. If motion is detected at least 45 seconds before the record saving action, the GPS module will be turned on. If ''Records Saving/Sending Without TS'' configuration is set <span style=color:#F6A83E>Always</span> or <span style=color:#F6A83E>After Time Sync</span> a periodic record is saved and GPS is turned off again. Alternatively, if configuration is set to <span style=color:#F6A83E>After Position Fix</span>, the device will try to obtain GPS fix before record saving takes place and then allow extra ''GPS search period'' to obtain fix. Failing to do so within ''GPS search period'', GPS module will be turned back off and the record will be not saved at all. While this mode is enabled the data acquisition parameters min. distance, min. angle, min. speed delta, are disabled.
The purpose of this feature is to reduce power consumption and its main function is to turn off the GPS module when the device is stationary. For power saving functionality to run several conditions need to be met, one of them: ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds. In device cold start state the GPS module is turned on for 180 sec. If GPS fix is obtained before this timeout elapses, GPS module turns off and a record is saved, and if not, no record will be saved. Before each new record saving period is expired the device is constantly checking for movement and if no motion has been detected, the GPS module does not turn on and the device waits for a periodic record to be eventually saved. If motion is detected at least 45 seconds before the record saving action, the GPS module will be turned on. If ''Records Saving/Sending Without TS'' configuration is set <span style=color:#F6A83E>Always</span> or <span style=color:#F6A83E>After Time Sync</span> a periodic record is saved and GPS is turned off again. Alternatively, if configuration is set to <span style=color:#F6A83E>After Position Fix</span>, the device will try to obtain GPS fix before record saving takes place and then allow extra ''GPS search period'' to obtain fix. Failing to do so within ''GPS search period'', GPS module will be turned back off and the record will be not saved at all. While this mode is enabled the data acquisition parameters min. distance, min. angle, min. speed delta, are disabled.
Requirements:
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;
* Tracking mode selected to “Low Power”.
* Tracking mode selected to “Low Power”.
{|
{|
{{#if:{{{TFT_system_settings|}}}
{{#if:{{{TFT_show|}}}
|
|
|==Timestamp Backup==
|==Timestamp Backup==
|==GNSS Fix Holdout==
|==GNSS Fix Holdout==
[[Image:Gnssfixholdout.jpg.jpg|right]]
[[Image:Gnssfixholdout.jpg|right]]
If this parameter is ‘Enable’, then for the first 30s of GNSS fix, coordinates are not considered valid. ‘Disable’ means that from the start of the fix coordinates are considered valid.
If this parameter is ‘Enable’, then for the first 30s of GNSS fix, coordinates are not considered valid. ‘Disable’ means that from the start of the fix coordinates are considered valid.
}}
}}
|}
|}