6,023
edits
Changes
mLine 30:
Line 30: − + + Line 114:
Line 115: − Line 132:
Line 132: + − + + + + + + + Line 146:
Line 153: − Protocol version for data sending to server.+ − Codec 8 supports up to 255 AVL ID.+ − Codec 8 Extended supports up and above 255 AVL ID. − + + + + + + + Line 158:
Line 170: − + − 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>.+ + + Line 345:
Line 359: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + Line 363:
Line 418: + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + + +
no edit summary
Available speed source: GNSS or CAN.
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.
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]]
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]
}}
}}
* 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.
* 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]]
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]
}}
}}
Lowest voltage to enabled DIN for 150V range - 9V
Lowest voltage to enabled DIN for 150V range - 9V
}}
}}
|}
|}
===DOUT Overcurrent protection===
{|
{{#if:{{{TFT_DOUT_Overcurrent_protection|}}}
|
|===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.
}}
|}
{|
{|
*Codec 8 Extended supports up and above 255 AVL ID.
*Codec 8 Extended supports up and above 255 AVL ID.
}}
|}
[[Image:Screenshot 2024-03-01 at 14-16-56 5.2. System - Mobility documentation.png]]
{|
{{#if:{{{PT_Power_on|}}}
|
|===Power On By USB/Charger===
[[Image:PT Power on by usb.png|200px|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|}}}
{{#if:{{{PT_Power_on|}}}
|
|
|===Power On By USB/Charger===
|===Continuous Charging Mode===
[[Image:PT continuous charging.png|200px|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%.
}}
}}
|}
|}
|[[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.
{| class="wikitable" style="width: 80%;"
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours)
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org
|}
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]]
|}
|}
*<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:
{| class="wikitable" style="width: 80%;"
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request calibration info (time, ground vector, side vector)
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request calibration clear from flash and stop calibration task
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request calibration status and calibration task status
|}
Accelerometer Auto Calibration parameter has 3 options:
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.
* Once - when this option is selected, the device only tries once to do calibrating. When calibration is done, the device will not try to recalibrate, even if the calibration is not correct. Calibration will be left as it is.
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.
Gravity filter subtracts gravity from the vector when the device is calibrated or when auto calibration is disabled (default values). Parameter functionality is the same in all versions. This also influences the ECO/Green driving scenario algorithm.
* Disable - do NOT remove gravity component from AXL/Crash data.
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]
'''Important''':If Auto Calibration is disabled, in order for the Eco/Green Driving to work propertly, the device must be mounted according to the TFT100 Mounting Guidelines
}}
|}
{|
{{#if:{{{TFT_Mounting_Guidelines|}}}
|
|=== Mounting Guidelines ===
The device should be mounted according to the picture below. Logo/Antenna must be facing up.
[[File:Screenshot 2024-03-04 at 09-01-13 tft100-mounting-guidelines.jpg (JPEG Image 900 × 600 pixels).png|thumb]]
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
<br>
}}
|}
{|
{{#if:{{{TFT_Accelerometer_delay|}}}
|
|===Accelerometer delay===
Configurable movement start/stop delay settings.
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]
{| class="wikitable" style="width: 80%;"
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1
|-
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60
|}
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.
}}
}}
|}
|}
