https://wiki.teltonika-gps.com/api.php?action=feedcontributions&feedformat=atom&user=Jonas.sterbaviciusTeltonika Telematics Wiki - User contributions [en]2026-04-15T18:18:29ZUser contributionsMediaWiki 1.43.5https://wiki.teltonika-gps.com/index.php?title=TAT100_System_settings&diff=97321TAT100 System settings2024-04-12T09:26:45Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:System settings<br />
|model=TAT100<br />
|device_group=AT <br />
<br />
|TFT_DOUT_Overcurrent_protection=false<br />
|MM_Movement_source=false<br />
|TFT_can=false<br />
|MM_LED_indication= false<br />
|TST_battery_charge_mode= false;<br />
|TFT_system_settings= false<br />
|PT_Power_on= false<br />
|PT_movement_source= false<br />
|TFT_ignition_source= false<br />
|TFT_accelerometer_calibration= false<br />
|PT_Tracking_mode=false<br />
|TAT100_show=false<br />
|GNSS_Fix_Holdout=false<br />
|LBS_tracking=false<br />
|AT_no_show=false<br />
|GH_TMT_section=false<br />
|GH_section=false<br />
|TFT_Accelerometer_delay=false<br />
|TFT_Mounting_Guidelines=false<br />
<br />
}}<br />
<br />
[[Category:TAT100 Configuration]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT141_System_settings&diff=97320TAT141 System settings2024-04-12T09:26:14Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:System settings<br />
|model=TAT141<br />
|device_group=AT <br />
<br />
|TFT_DOUT_Overcurrent_protection=false<br />
|MM_Movement_source=false<br />
|TFT_can=false<br />
|MM_LED_indication= false<br />
|TST_battery_charge_mode= false;<br />
|TFT_system_settings= false<br />
|PT_Power_on= false<br />
|PT_movement_source= false<br />
|TFT_ignition_source= false<br />
|TFT_accelerometer_calibration= false<br />
|PT_Tracking_mode=false<br />
|TAT100_show=false<br />
|GNSS_Fix_Holdout=false<br />
|LBS_tracking=false<br />
|AT_no_show=false<br />
|GH_TMT_section=false<br />
|GH_section=false<br />
|TFT_Accelerometer_delay=false<br />
|TFT_Mounting_Guidelines=false<br />
<br />
}}<br />
<br />
[[Category:TAT141 Configuration]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT140_System_settings&diff=97319TAT140 System settings2024-04-12T09:24:36Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:System settings<br />
|model=TAT140<br />
|device_group=AT <br />
<br />
|MM_Movement_source=false<br />
|TFT_DOUT_Overcurrent_protection=false<br />
|TFT_can=false<br />
|MM_LED_indication= false<br />
|TST_battery_charge_mode= false;<br />
|TFT_system_settings= false<br />
|PT_Power_on= false<br />
|PT_movement_source= false<br />
|TFT_ignition_source= false<br />
|TFT_accelerometer_calibration= false<br />
|PT_Tracking_mode=false<br />
|TAT100_show=false<br />
|GNSS_Fix_Holdout=false<br />
|LBS_tracking=false<br />
|AT_no_show=false<br />
|GH_section=false<br />
|GH_TMT_section=false<br />
|TFT_Mounting_Guidelines=false<br />
|TFT_Accelerometer_delay=false<br />
<br />
}}<br />
<br />
[[Category:TAT140 Configuration]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97318Template:System settings2024-04-12T09:23:33Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_DOUT_Overcurrent_protection|}}}<br />
|<br />
|===DOUT Overcurrent protection===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_Mounting_Guidelines|}}}<br />
|<br />
|=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_Accelerometer_delay|}}}<br />
|<br />
|===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97317Template:System settings2024-04-12T09:19:17Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_DOUT_Overcurrent_protection|}}}<br />
|<br />
|===DOUT Overcurrent protection===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97316Template:System settings2024-04-12T09:17:26Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_DOUT_Overcurrent_protection|}}}<br />
|<br />
|===DOUT Overcurrent protection===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97315Template:System settings2024-04-12T09:16:00Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_DOUT Overcurrent protection|}}}<br />
|<br />
|===DOUT Overcurrent protection===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97314Template:System settings2024-04-12T09:07:27Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_DOUT_Overcurrent_protection|}}}<br />
|<br />
===DOUT Overcurrent protection===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97313Template:System settings2024-04-12T09:04:57Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_DOUT Overcurrent protection|}}}<br />
|<br />
<br />
===DOUT Overcurrent protection===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97310Template:System settings2024-04-12T06:12:17Z<p>Jonas.sterbavicius: Reverted edits by Jonas.sterbavicius (talk) to last revision by Karolis.C</p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
}}<br />
|}<br />
===DOUT Overcurrent protection===<br />
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.<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97309Template:System settings2024-04-12T06:11:42Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
}}<br />
|}<br />
===DOUT Overcurrent protection===<br />
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.<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_Mounting_Guidelines|}}}<br />
<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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 />
{{#if:{{{TFT_Accelerometer_delay|}}}<br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97308Template:System settings2024-04-12T06:10:10Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
}}<br />
|}<br />
===DOUT Overcurrent protection===<br />
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.<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Mounting_Guidelines|}}}<br />
<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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 />
{{#if:{{{Accelerometer_delay|}}}<br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97307Template:System settings2024-04-12T06:03:17Z<p>Jonas.sterbavicius: Reverted edits by Jonas.sterbavicius (talk) to last revision by Karolis.C</p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
}}<br />
|}<br />
===DOUT Overcurrent protection===<br />
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.<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT140_System_settings&diff=97306TAT140 System settings2024-04-12T06:01:26Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:System settings<br />
|model=TAT140<br />
|device_group=AT <br />
<br />
|DOUT_Overcurrent_protectio=false<br />
|MM_Movement_source=false<br />
|TFT_can=false<br />
|MM_LED_indication= false<br />
|TST_battery_charge_mode= false;<br />
|TFT_system_settings= false<br />
|PT_Power_on= false<br />
|PT_movement_source= false<br />
|TFT_ignition_source= false<br />
|TFT_accelerometer_calibration= false<br />
|PT_Tracking_mode=false<br />
|TAT100_show=false<br />
|GNSS_Fix_Holdout=false<br />
|LBS_tracking=false<br />
|AT_no_show=false<br />
|GH_section=false<br />
|GH_TMT_section=false<br />
|Mounting_Guidelines=false<br />
|Accelerometer_delay=false<br />
}}<br />
<br />
[[Category:TAT140 Configuration]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97305Template:System settings2024-04-12T06:00:45Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{DOUT_Overcurrent_protection|}}}<br />
===DOUT Overcurrent protection===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
<br />
{|<br />
{{#if:{{{Mounting_Guidelines|}}}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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 />
{{#if:{{{Accelerometer_delay|}}}<br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
}}<br />
|}<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT140_System_settings&diff=97304TAT140 System settings2024-04-12T05:49:24Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:System settings<br />
|model=TAT140<br />
|device_group=AT <br />
<br />
|DOUT_Overcurrent_protectio=false<br />
|MM_Movement_source=false<br />
|TFT_can=false<br />
|MM_LED_indication= false<br />
|TST_battery_charge_mode= false;<br />
|TFT_system_settings= false<br />
|PT_Power_on= false<br />
|PT_movement_source= false<br />
|TFT_ignition_source= false<br />
|TFT_accelerometer_calibration= false<br />
|PT_Tracking_mode=false<br />
|TAT100_show=false<br />
|GNSS_Fix_Holdout=false<br />
|LBS_tracking=false<br />
|AT_no_show=false<br />
|GH_section=false<br />
|GH_TMT_section=false<br />
}}<br />
<br />
[[Category:TAT140 Configuration]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97303Template:System settings2024-04-12T05:47:42Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
}}<br />
|}<br />
{|<br />
{{#if:{{{DOUT_Overcurrent_protection|}}}<br />
===DOUT Overcurrent protection===<br />
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.<br />
}}<br />
|}<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:System_settings&diff=97302Template:System settings2024-04-12T05:46:50Z<p>Jonas.sterbavicius: </p>
<hr />
<div>==System Settings==<br />
{|<br />
{{#if:{{{MM_Movement_source|}}}<br />
|<br />
|===Movement Source===<br />
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.<br />
Available movement source:<br />
[[Image:Screenshot 2024-03-01 at 14-04-10 5.2. System - Mobility documentation.png|right|300px]]<br />
* Ignition: checks ignition settings which depends on Ignition Source settings;<br />
<br />
* GNSS: movement detected if Fix position available and speed is bigger or equal to 5km/h;<br />
<br />
* Accelerometer: movement detection depends on Accelerometer Delay Settings;<br />
<br />
* CAN Speed: movement is detected if CAN speed retrieved from specific CAN protocol.<br />
<br />
When multiple source are selected, if any of selected are active, Movemenet is detected.<br />
<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_can|}}}<br />
|<br />
|===Speed source===<br />
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.<br />
<br />
Available speed source: GNSS or CAN.<br />
<br />
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><br />
<br />
[[Image:Screenshot 2024-03-01 at 14-09-53 5.2. System - Mobility documentation.png]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===Records settings===<br />
Here user can enable or disable records when GPS is not available (no GPS fix). <br><br />
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br><br />
* <b>After Time Sync</b> - Device must have correct time to save/send records. Allows record sending with no coordinates. <br><br />
* <b>Always</b> - Always save/send records. Allows record sending with no coordinates and no correct time.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===PDOP filter===<br />
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.<br />
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Input/Output Mode===<br />
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:<br />
*Digital input 3 and Digital input 4 (value:5),<br />
*Digital output 1 and Digital input 4 (value:6),<br />
*Digital input 3 and Digital output 2 (value:9),<br />
*Digital output 1 and Digital output 2 (value:10).<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{MM_LED_indication|}}}<br />
|<br />
|===LED Indication===<br />
User can turn on or off the indication LEDs.<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TST_battery_charge_mode|}}}<br />
|<br />
|===Battery Charge Mode===<br />
Here user can change battery charger settings, where charging is allowed.<br />
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).<br />
<br />
Three charging modes is available:<br />
<br />
* 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.<br />
<br />
* 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.<br />
<br />
* 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.<br />
[[Image:Screenshot 2024-03-01 at 14-11-41 5.2. System - Mobility documentation.png]]<br />
<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|===Analog Input Value Range===<br />
User can choose analog input range of 15 V or 150 V.<br />
<br />
Input range used to determine lowest voltage for DIN1 and DIN2 activation.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-13-04 5.2. System - Mobility documentation.png]]<br />
<br />
Lowest voltage to enabled DIN for 15V range - 2.5V<br />
<br />
Lowest voltage to enabled DIN for 150V range - 9V<br />
}}<br />
|}<br />
{|<br />
{{#if:{{{DOUT Overcurrent protection|}}}<br />
===DOUT Overcurrent protection===<br />
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.<br />
}}<br />
|}<br />
{|<br />
{{#if:{{{Data_protocol|}}}<br />
|<br />
|===Data Protocol===<br />
User can choose which protocol version to use for data sending to server.<br />
*Codec 8 supports up to 255 AVL ID;<br />
*Codec 8 Extended supports up and above 255 AVL ID.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Power On By USB/Charger===<br />
[[Image:PT Power on by usb.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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>.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{PT_Power_on|}}}<br />
|<br />
|===Continuous Charging Mode===<br />
[[Image:PT continuous charging.png|200px|right]]<br />
'''Note''': This feature is available forwards from FW version 55.02.03.Rev.05<br><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%.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|==Location Settings==<br />
[[Image:Location_settings_{{{model|X}}}.png|right|300px]]<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{LBS_tracking|}}} <br />
|<br />
|===Location Source===<br />
<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. <br />
<br />
*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>.<br />
<br />
*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.<br />
<br />
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]]<br />
<br><br><br><br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{Location_settings|}}}<br />
|<br />
|===GNSS Source settings===<br />
User can configure which GNSS system(s) to use.<br /><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. <br />
<br />
Examples of non-configurable GNSS source combinations are:<br />
*GLONASS + BeiDou;<br />
*Galileo + GLONASS + BeiDou;<br />
*GPS + GLONASS + BeiDou;<br />
*GPS + Galileo + GLONASS + BeiDou.<br />
<br />
List of configurable GNSS sources:<br />
<br />
*GPS only;<br />
*GPS + BeiDou;<br />
*GPS + GLONASS;<br />
*GPS + GLONASS + Galileo.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===GNSS control===<br />
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.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Coordinate acquisition timeout===<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Static Navigation Settings===<br />
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.<br />
<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 /><br />
<br />
The functionality is illustrated in the flowchart below:<br />
<br />
[[File:Staticnavflowchart.png]]<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_show|}}}<br />
|<br />
|===Movement sensitivity===<br />
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 /><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Static Navigation Settings==<br />
[[Image:Static_navigation_PT.png|right]]<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 /><br />
Additionally, user can choose which source (movement or ignition) is used to activate/deactivate static navigation.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_section|}}}<br />
|<br />
|==Call Duration Limits==<br />
[[Image:Call duration limits.png|right]]<br />
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.<br />
[[Image:Cal duration limit2.png|right]]<br />
<br />
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.<br />
<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{AT_no_show|}}}<br />
|<br />
|==Sleep Mode==<br />
<table style="width:100%"><br />
<tr style="vertical-align: top; text-align: left;"><br />
<td style="width:75%">User can choose sleep mode. More about sleep modes can be found {{{ctrSleepModes|[[{{{model|X}}} Sleep modes|here]]}}}. <br><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]]}}}<br />
</td><br />
<td>[[Image:Sleep_mode_{{{model|X}}}.png|right]]</td><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{BT/BLE_no_show|}}}<br />
|<br />
===BT/BLE module OFF during Sleep modes===<br />
------------------<br />
Power off sleep mode can be described as the lowest possible power consumption mode where the device can go into power off state.<br />
<br><br />
<br />
From the version, 03.28.XX this new functionality includes new parameters:<br />
<br />
*'''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.<br />
*'''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.<br />
[[Image:PWU.jpg|right|300px]]<br />
</br></br><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 />
<br><br />
<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:<br />
<br />
*Movement is detected by accelerometer (not by the configured movement source);<br />
*External power is applied;<br />
*It is the time to make a new periodic record (new feature);<br />
<br><br />
Please keep a note that Power OFF Sleep will not work if any USB cable is connected to the device.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_ignition_source|}}}<br />
|<br />
|==Ignition Source==<br />
[[Image:Mob_Ignition_source.png|right]]<br />
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. 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/Green driving, Excessive idling, Over speeding, Towing detection and trip.<br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{GH_TMT_section|}}}<br />
|<br />
|==Movement Settings==<br />
[[Image:Accelerometer settings.png|right]]<br />
Here the user can set the movement start/stop delays. <br/><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.<br />
*<code>Minimal</code> – approximately 40% higher movement threshold comparing to Normal<br />
*<code>Reduced</code> – approximately 20% higher movement threshold comparing to Normal<br />
*<code>Normal</code> – recommended value for most users<br />
*<code>Increased</code> – approximately 20% lower movement threshold comparing to Normal<br />
*<code>Maximum</code> – approximately 40% lower movement threshold comparing to Normal<br />
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!<br />
}}<br />
|}<br />
<br />
==Time Synchronization==<br />
{| style="width: 100%;"<br />
<br />
|[[Image:Time_synchronization.PNG|right]]<br />
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.<br />
<br />
Configurable NTP server (it is possible to configure up to two servers) and what time period to use to re-synchronize time.<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Value/Type'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 901<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Resync (hours) <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | uint8<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 24<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 902<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | avl1.teltonika.lt<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 903<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | NTP Server 2<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | char<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 0<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 55<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | pool.ntp.org<br />
|}<br />
<br />
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.<br />
<br />
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.<br />
<br />
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.<br />
<br />
[[File:Time sync chart.png|thumb]]<br />
<br />
<br />
<br />
<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_accelerometer_calibration|}}}<br />
|<br />
|==Accelerometer auto calibration==<br />
[[Image:Accelerometer_auto_calibration.PNG|right]]<br />
User can disable or enable Accelerometer Auto Calibration and Gravity Filter features. Under Accelerometer Auto Calibration settings, user can choose: <br/><br />
<br />
*<code>Disable</code> – do not use auto calibration feature (sends AXES raw data),<br />
*<code>Once</code> – calibrate one time only,<br />
*<code>Continuous</code> – launch auto calibration every trip (note: trip function must be enabled! ). <br /><br />
<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 /> <br />
Under Gravity Filter settings, user can choose: <br />
<br />
*<code>Disabled</code> – do not remove GRAVITY component from AXL/Crash data,<br />
*<code>Enabled</code> – remove GRAVITY component from AXL/Crash.<br />
<br />
(An in-depth explanation for the auto calibration can be found here)<br />
<br />
Calibration algorithm is used to recalculate accelerometer axes to represent vehicle’s axes (see Picture below). Vehicles axes are as follows:<br />
<br />
* X is front.<br />
* Y is left.<br />
* Z is down.<br />
<br />
[[File:Screenshot 2024-03-01 at 14-34-37 vehicleaxes.png (PNG Image 1186 × 596 pixels).png|thumb]]<br />
Once vehicle’s axes are calculated, device is considered calibrated.<br />
'''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.<br />
<br />
Commands that can be used during calibration:<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Command'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Response'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Description'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:set<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Request auto calibration task start<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:get<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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)<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:clear<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | auto_calibrate:status<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Yes<br />
| 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<br />
|}<br />
Accelerometer Auto Calibration parameter has 3 options:<br />
<br />
* Disabled - when this option is selected the device will be calibrated accordingly to its mounted position.<br />
<br />
* 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.<br />
<br />
* Continuous - calibration process is going on continuously and is always updated, no matter if it is correct or not.<br />
<br />
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.<br />
<br />
* Disable - do NOT remove gravity component from AXL/Crash data.<br />
<br />
* Enable - remove gravity component from AXL/Crash. Meaning that in calculations ground vector is subtracted from vehicle projection.<br />
<br />
[[Image:Screenshot 2024-03-01 at 14-38-59 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
'''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<br />
<br />
}}<br />
|}<br />
=== Mounting Guidelines ===<br />
The device should be mounted according to the picture below. Logo/Antenna must be facing up.<br />
[[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><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br><br />
<br />
===Accelerometer delay===<br />
Configurable movement start/stop delay settings.<br />
[[Image:Screenshot 2024-03-01 at 14-40-45 5.2. System - Mobility documentation.png|thumb]]<br />
<br />
{| class="wikitable" style="width: 80%;"<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Parameter ID'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Name'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Min'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Max'''<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |'''Default'''<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19001<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Start delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 1<br />
|-<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 19002<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | Movement Stop Delay<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 300<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: center; background: white;" | 60<br />
|}<br />
<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 />
<br />
{|<br />
{{#if:{{{PT_Tracking_mode|}}}<br />
|<br />
|==Tracking Mode==<br />
[[Image:Tracking_mode.png|right]]<br />
<br><b>Power Saving Mode</b> <br><br />
<br />
* <b>Performance</b> - In this mode GNSS module is constantly awake for maximum track quality.<br><br />
* <b>Low power</b> - Battery saving mode, where GNSS is woken up only when it is time to acquire Position. Standard Sleep modes are not available in this mode.<br />
<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.<br />
<br />
Requerements:<br />
* ''Min Period'' value in ''Data Acquisition'' is more than or equal to 60 seconds;<br />
* Tracking mode selected to “Low Power”.<br />
<br><br />
GNSS module will be turned OFF:<br />
* Fix was not caught in 45 seconds;<br />
* Fix was stable for 30 seconds.<br />
<br><br />
<i>Power Saving Mode</i> Values:<br />
<br />
<table style="border-collapse: collapse; width:50%;" border="1;"><br />
<tr style="text-align: center; background:black; color:white><br />
<th width="20%">Parameter ID</th><br />
<th width="40%">Name</th><br />
<th width="20%">Min Value</th><br />
<th width="20%">Max Value</th><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>909</td><br />
<td>Power Saving Mode</td><br />
<td>0 - Performance</td><br />
<td>1 - Low Power</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>905</td><br />
<td>GPS accuracy</td><br />
<td>0.1</td><br />
<td>20</td><br />
</tr><br />
<tr style="text-align: center;"><br />
<td>906</td><br />
<td>GPS Satellites Quantity</td><br />
<td>4</td><br />
<td>20</td><br />
</tr><br />
</table><br />
}}<br />
|}<br />
<br />
{|<br />
{{#if:{{{TFT_system_settings|}}}<br />
|<br />
|==Timestamp Backup==<br />
[[Image:Timestamp Backup.png|right]]<br />
Enables or disables the Timestamp Backup synchronization. <br />
<br />
This feature, if enabled, every minute saves current timestamp to non-volatile memory (persist after power cutoff). If device was restarted for some reason and was unable to synchronize time, device will use the last saved timestamp as current time.<br />
<br />
}}<br />
|}<br />
<br />
<br />
{|<br />
{{#if:{{{GNSS_Fix_Holdout|}}}<br />
|<br />
|==GNSS Fix Holdout==<br />
<br />
[[Image:Gnssfixholdout.jpg|right]]<br />
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.<br />
<br />
}}<br />
|}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Promotional_Material&diff=97297Promotional Material2024-04-11T09:49:32Z<p>Jonas.sterbavicius: </p>
<hr />
<div>*'''[[General Teltonika Design Material]]'''<br />
*'''[[General Fleet Management Design Material]]'''<br />
*'''[[Media:Telematics-product-catalog-february-2024.pdf|Telematics Product Catalog, February 2024]]'''<br />
*'''[[Media:Telematics-journal-2023-december.pdf.pdf|Telematics Journal December 2023, Vol. 5]]''', '''[https://teltonika-gps.com/cdn/pdfs/2023/telematics-journal-2023-june.pdf Vol. 4], [https://teltonika-gps.com/cdn/pdfs/2023/telematics-journal-vol3.pdf Vol. 3], [https://teltonika-gps.com/cdn/pdfs/2024/telematics-journal-vol2.pdf Vol. 2], [https://teltonika-gps.com/cdn/pdfs/2024/telematics-journal-vol1.pdf Vol. 1]'''<br />
*'''Product Design Material'''<br />
**FMB0<br />
***[[FMB001 Promotional Material|FMB001]]<br />
***[[FMB010 Promotional Material|FMB010]]<br />
**FMB1<br />
***[[FMB110 Promotional Material|FMB110]]<br />
***[[FMB120 Promotional Material|FMB120]]<br />
***[[FMB122 Promotional Material|FMB122]]<br />
***[[FMB125 Promotional Material|FMB125]]<br />
***[[FMB130 Promotional Material|FMB130]]<br />
***[[FMB140 Promotional Material|FMB140]]<br />
**FMU1<br />
***[[FMU125 Promotional Material|FMU125]]<br />
***[[FMU130 Promotional Material|FMU130]]<br />
**FMB2<br />
***[[FMB202 Promotional Material|FMB202]]<br />
***[[FMB204 Promotional Material|FMB204]]<br />
**FM30<br />
***[[FM3001 Promotional Material|FM3001]]<br />
**FM36<br />
***[[FM36M1 Promotional Material|FM36M1]]<br />
**FMB6<br />
***[[FMB630 Promotional Material|FMB630]]<br />
***[[FMB640 Promotional Material|FMB640]]<br />
**FMB9<br />
***[[FMB900 Promotional Material|FMB900]]<br />
***[[FMB920 Promotional Material|FMB920]]<br />
**FMB96<br />
***[[FMB964 Promotional Material|FMB964]]<br />
**FM63<br />
***[[FM6300 design material|FM6300]]<br />
**FMC1<br />
***[[FMC125 Promotional Material|FMC125]]<br />
***[[FMC130 Promotional Material|FMC130]]<br />
** FMM<br />
***[[FMM125 Promotional Material|FMM125]]<br />
***[[FMM130 Promotional Material|FMM130]]<br />
**FML<br />
***[[FML001 design material|FML001]]<br />
**FMT1<br />
***[[FMT100 Promotional Material|FMT100]]<br />
**MTB1<br />
***[[MTB100 Promotional Material|MTB100]]<br />
**Solutions<br />
***[[FMBT design material|FMBT]]<br />
**CAN Adapters<br />
***[[LV-CAN200 design material|LV-CAN200]]<br />
***[[ALL-CAN300 design material|ALL-CAN300]]<br />
***[[CAN-CONTROL design material|CAN-CONTROL]]<br />
***[[MINI-CAN design material|MINI-CAN]]<br />
***[[ECAN01_design_material|ECAN01]]<br />
<br />
[[Category:General Information|40]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TMT250_Short-term_firmware&diff=97014TMT250 Short-term firmware2024-03-25T14:38:42Z<p>Jonas.sterbavicius: </p>
<hr />
<div>__TOC__<br />
<br />
==Short-Term firmware==<br />
{{Template:Firmware_template<br />
<br />
|fw_head=SHORT-TERM FIRMWARE <!---Top header ---><br />
|firmware_ver= 55.01.11.Rev.00 <!---Firmware version ---><br />
|BlueNRG_txt= <!---For TAT100, if BlueNRG not included, then leave as is ---><br />
|configurator_ver= 1.6.11_R.41 <!--- Configurator version ---><br />
|Bluenrg_ver= <!---For TAT100, BlueNRG version ---><br />
|Release_date= 2022.09.16 <!---Firmware release date ---><br />
<br />
<!--- |DLTAB=<br />
|DLTAB2=<br />
|DLTAB3= ---><br />
|TAT_BL_ST1=<br />
|TAT_BL_ST2=<br />
|TAT_BL_ST3=<br />
|DL_FMB1=<br />
|DL_FMB2=<br />
|DL_FMB3=<br />
<br />
|BLNRG1=<br />
|BLNRG2=<br />
|BLNRG3=<br />
<br />
|DL_ALL31=<br />
|DL_ALL31_BL=<br />
|DL_ALL3=<br />
|DL_ALL31_BL1=<br />
<br />
|DL_ALL62=<br />
|DL_ALL62_BL=<br />
|DL_ALL6=<br />
|DL_ALL62_BL1=<br />
<br />
|DL_ALL62_1=<br />
|DL_ALL4_FMB=<br />
|DL_ALL4=<br />
|DL_ALL4_FMB1=<br />
|TAT_HW6=display:none;<br />
|TAT_BL2=<br />
|TAT_BL= <!---BlueNRG download link ---><br />
<br />
|BlueNrgb= <!---BlueNRG download tab ---><br />
|BlueNrgb2= <!---BlueNRG download tab ---><br />
|BlueNrga2=<br />
|BlueNrga=<br />
<br />
|FW_DL=FMB.Ver.55.01.11.Rev.00.e.zip <!---Firmware download file ---><br />
|CF_DL=Teltonika.Configurator_1.6.11_R.41.zip <!---Configurator download file ---><br />
|DL_FOR_ALL=Teltonika.Configurator_1.6.11_R.41_and_FMB.Ver.55.01.11.Rev.00.e.zip <!---All files download ---><br />
}}<br />
<br />
<br />
{| class="wikitable" style="width: 100%; valign="top"; align="center";|"<br />
|+<br />
!colspan="5" style="width:100%; border: 1px solid #0054A6;border-bottom: 1px solid #0054A6; background: #0054A6; color: white; text-align: center;" |<font size="3"><b>CHANGELOG</b></font><br />
|-<br />
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION<br />
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE<br />
! style="width: 35%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES<br />
! style="width: 40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES<br />
! style="width: 30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |KNOWN ISSUES<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" | 55.01.11.Rev.00<br>1.6.11_R.41 <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.09.16<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
*[CHN] Changed minimum BLE scan start period configuration value.<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
*[CHN] Changed minimum BLE scan start period configuration value.<br />
*[FIX] Fixed Beacon record saving on Disabled discovery parameter. <br />
*[FIX] Fixed time synchronization issues.<br />
*[FIX] Implemented accelerometer changes to prevent unwanted wake-up and fake movement in Low Power. <br />
*[ADD] Added GPS Track data renewing immediately after difference detected.<br />
*[FIX] Fixed beacons buffer cleanup after the end of BLE scanning or periodic beacon record creation.<br />
*[FIX] Fixed GSM Established LED Indication turning off after configuration change.<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
*If the BLE record period is configured to 60sec, every second record is without the date, if it is configures every 5sec period, quantity of records without the date increases. If the eventual records is configured, issue does not reoccur.<br />
|}<br />
<br />
<!--<br />
{| class="wikitable" style="border-style: solid; border-width: 0px;"<br />
|+ <br />
|-<br />
| style="width: auto; text-align: left; background: #F6F6FB;" | '''NOTE!'''<br />
| style="width: auto; text-align: left; background: #F6F6FB;" | THERE IS NO SHORT TERM FIRMWARE AVAILABLE. PLEASE USE THE [[TMT250 Stable firmware|STABLE]] VERSION.<br />
|}<br />
<div class="mw-collapsible mw-collapsed" data-expandtext="Older changelogs can be seen by expanding this section" data-collapsetext="Close this section" style="width:100%;"><br />
<div class="mw-collapsible-content" ><br />
{| class="wikitable" style="width: 100%; valign="top"; align="center";|"<br />
<br />
--><br />
<div class="mw-collapsible mw-collapsed" data-expandtext="View changelog history" data-collapsetext="Close this section" style="width:100%;"><br />
{| class="wikitable" style="width: 100%; valign="top"; align="center";|"<br />
<br />
|-<br />
! style="width: 10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION<br />
! style="width: 10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE<br />
! style="width: 25%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES<br />
! style="width: 30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES <br />
|-<br />
<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |55.01.10.Rev.00<br>1.6.11 R.39<br />
<i>*was approved as STABLE<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.09.14<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* [CHN] Renamed Universal Beacons feature to BLE Devices<br />
* [CHN] Changed TMT250 default configuration<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* [FIX]: Fixed BLE Sensor Custom IO SMS sending with value NaN and displaying as ASCII in Configurator.<br />
* [FIX]: Fixed device constantly opening and closing GPRS with permanent link if APN is empty in configurator.<br />
* [FIX]: Fixed permanent link not changing protocol after reconfiguration.<br />
* [CHN]: Updated FOTA WEB protocol ID 0x04 => 0x05 <br />
* [FIX]: Increased connection interval in order to speed up connection through BLE terminal. <br />
* [FIX]: Fixed POSI command skipping. <br />
* [FIX]: Fixing network stability issues. <br />
* [FIX]: Fixed timestamp not renewing for Eddystone beacons.<br />
* [FIX]: Added condition to prevent closing socket, if GPRS command is received and response was not sent yet.<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |55.01.09.Rev.01<br>1.6.11_R.38<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.04.29<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Removed POSI command from base. This will solve internal memory fills and not records send issue.<br />
* Increased external queue size to prevent abnormal restarts and prevent from records sending stops. This issue repeats during Non Stop BLE during BLE scan.<br />
* Fixed device saving periodic records while in charging mode<br />
* Removed unused BT User ID<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |55.01.06.Rev.01<br>1.6.11_R.35<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.03.03<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Handheld: Added Universal Beacon value for Beacon Detection parameter.<br />
* Removed Continuous battery charging mode.<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Fixed a broken GSM connection due to incorrect SIM card error.<br />
* Added AVL IDs reservation and changed AVL ID enum size from 14b to 16b. New AVL ID will be from 20000 to 29999. <br />
* Fixed FOTA WEB fail when the DUMB files requested for download do not exist.<br />
* Added variable temperature corrections according to laboratory results for battery critical limits calculation<br />
* Added auto reset after out of normal working range temperature. <br />
* Increased accelerometer sensitivity in ultra deep sleep mode<br />
|-<br />
|}<br />
</div><div><br />
<br></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=GH5200_Short-term_firmware&diff=97013GH5200 Short-term firmware2024-03-25T14:37:35Z<p>Jonas.sterbavicius: </p>
<hr />
<div>__TOC__<br />
<br />
==Short-Term firmware==<br />
<br />
{{Template:Firmware_template<br />
<br />
|fw_head=SHORT-TERM FIRMWARE <!---Top header ---><br />
|firmware_ver= 55.01.11.Rev.00 <!---Firmware version ---><br />
|BlueNRG_txt= <!---For TAT100, if BlueNRG not included, then leave as is ---><br />
|configurator_ver= 1.6.11_R.41 <!--- Configurator version ---><br />
|Bluenrg_ver= <!---For TAT100, BlueNRG version ---><br />
|Release_date= 2022.09.16 <!---Firmware release date ---><br />
<br />
<!--- |DLTAB=<br />
|DLTAB2=<br />
|DLTAB3= ---><br />
|TAT_BL_ST1=<br />
|TAT_BL_ST2=<br />
|TAT_BL_ST3=<br />
|DL_FMB1=<br />
|DL_FMB2=<br />
|DL_FMB3=<br />
<br />
|BLNRG1=<br />
|BLNRG2=<br />
|BLNRG3=<br />
<br />
|DL_ALL31=<br />
|DL_ALL31_BL=<br />
|DL_ALL3=<br />
|DL_ALL31_BL1=<br />
<br />
|DL_ALL62=<br />
|DL_ALL62_BL=<br />
|DL_ALL6=<br />
|DL_ALL62_BL1=<br />
<br />
|DL_ALL62_1=<br />
|DL_ALL4_FMB=<br />
|DL_ALL4=<br />
|DL_ALL4_FMB1=<br />
|TAT_HW6=display:none;<br />
|TAT_BL2=<br />
|TAT_BL= <!---BlueNRG download link ---><br />
<br />
|BlueNrgb= <!---BlueNRG download tab ---><br />
|BlueNrgb2= <!---BlueNRG download tab ---><br />
|BlueNrga2=<br />
|BlueNrga=<br />
<br />
|FW_DL=FMB.Ver.55.01.11.Rev.00.e.zip <!---Firmware download file ---><br />
|CF_DL=Teltonika.Configurator_1.6.11_R.41.zip <!---Configurator download file ---><br />
|DL_FOR_ALL=Teltonika.Configurator_1.6.11_R.41_and_FMB.Ver.55.01.11.Rev.00.e.zip <!---All files download ---><br />
}}<br />
<br />
<br />
{| class="wikitable" style="width: 100%; valign="top"; align="center";|"<br />
|+<br />
!colspan="5" style="width:100%; border: 1px solid #0054A6;border-bottom: 1px solid #0054A6; background: #0054A6; color: white; text-align: center;" |<font size="3"><b>CHANGELOG</b></font><br />
|-<br />
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION<br />
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE<br />
! style="width: 35%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES<br />
! style="width: 40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES<br />
! style="width: 30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |KNOWN ISSUES<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" | 55.01.11.Rev.00<br>1.6.11_R.41 <br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.09.16<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
*[CHN] Changed minimum BLE scan start period configuration value.<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
*[CHN] Changed minimum BLE scan start period configuration value.<br />
*[FIX] Fixed Beacon record saving on Disabled discovery parameter. <br />
*[FIX] Fixed time synchronization issues.<br />
*[FIX] Implemented accelerometer changes to prevent unwanted wake-up and fake movement in Low Power. <br />
*[ADD] Added GPS Track data renewing immediately after difference detected.<br />
*[FIX] Fixed beacons buffer cleanup after the end of BLE scanning or periodic beacon record creation.<br />
*[FIX] Fixed GSM Established LED Indication turning off after configuration change.<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
*If the BLE record period is configured to 60sec, every second record is without the date, if it is configures every 5sec period, quantity of records without the date increases. If the eventual records is configured, issue does not reoccur.<br />
|}<br />
<br />
<!--<br />
{| class="wikitable" style="border-style: solid; border-width: 0px;"<br />
|+ <br />
|-<br />
| style="width: auto; text-align: left; background: #F6F6FB;" | '''NOTE!'''<br />
| style="width: auto; text-align: left; background: #F6F6FB;" | THERE IS NO SHORT TERM FIRMWARE AVAILABLE. PLEASE USE THE [[GH5200 Stable firmware|STABLE]] VERSION.<br />
|}<br />
--><br />
<div class="mw-collapsible mw-collapsed" data-expandtext="View changelog history" data-collapsetext="Close this section" style="width:100%;"><br />
{| class="wikitable" style="width: 100%; valign="top"; align="center";|"<br />
<br />
|-<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION<br />
! style="width: 10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE<br />
! style="width: 35%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES<br />
! style="width: 40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |55.01.10.Rev.00<br>1.6.11 R.39 <br><i>*was approved as STABLE<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.09.14<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* [CHN] Renamed Universal Beacons feature to BLE Devices<br />
* [CHN] Changed GH5200 default configuration<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* [FIX]: Fixed BLE Sensor Custom IO SMS sending with value NaN and displaying as ASCII in Configurator.<br />
* [FIX]: Fixed device constantly opening and closing GPRS with permanent link if APN is empty in configurator.<br />
* [FIX]: Fixed permanent link not changing protocol after reconfiguration.<br />
* [CHN]: Updated FOTA WEB protocol ID 0x04 => 0x05 <br />
* [FIX]: Increased connection interval in order to speed up connection through BLE terminal. <br />
* [FIX]: Fixed POSI command skipping. <br />
* [FIX]: Fixing network stability issues. <br />
* [FIX]: Fixed timestamp not renewing for Eddystone beacons.<br />
* [FIX]: Added condition to prevent closing socket, if GPRS command is received and response was not sent yet.<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |55.01.09.Rev.01<br>1.6.11_R.38<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.04.29<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Removed POSI command from base. This will solve internal memory fills and not records send issue.<br />
* Increased external queue size to prevent abnormal restarts and prevent from records sending stops. This issue repeats during Non Stop BLE during BLE scan.<br />
* Fixed device saving periodic records while in charging mode<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |55.01.08.Rev.00<br>1.6.11_R.37<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.03.22<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Added ManDown and NoMovement Pre-alarm cancelation via keyboard button.<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
|-<br />
|}<br />
</div><div><br />
<br></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT140_Short-term_firmware&diff=97012TAT140 Short-term firmware2024-03-25T14:36:51Z<p>Jonas.sterbavicius: </p>
<hr />
<div>__TOC__<br />
<br><br />
{| style="width: 100%; text-align: left; border-bottom: 1px solid #FFCC33; border-left: 1px solid #FFCC33;border-top: 1px solid #FFCC33;border-right: 1px solid #FFCC33; background: #FEF6E7; padding: 10px;"<br />
| style="padding: 10px;"| [[File:Warning.png|30px]]<br />
|<b>CAUTION!</b> <br> Both firmwares (Modem and BlueNRG) must be flashed into device. Failing so can lead to unexpected device behavior and rapid battery discharge.<br />
|}<br />
<br />
<div class="mw-collapsible mw-collapsed tlt-border" style="background: #FAFAFA;""><br />
<div style="font-weight:bold; color: black;"><font size="3"><b>TAT140 BlueNRG & Modem FIRMWARE UPDATE GUIDE</b></font></font></div><br />
----<br />
<div class="mw-collapsible-content" ><br />
{{Template: TAT FW update guide}}<br />
</div></div><br />
<br />
==TAT140 Stable Firmware and Software==<br />
{{Template:TAT-series Firmware and Software<br />
|model=TAT140<br />
|TAT100_only=false<br />
|only_TAT100=display:none;<br />
<br />
|fw_head= SHORT-TERM FIRMWARE<br />
|firmware_ver= N/A<br />
|configurator_ver= N/A<br />
|Bluenrg_ver= N/A<br />
|Release_date= N/A<br />
|FW_DL<br />
|CF_DL=<br />
|DL_ALL<br />
}}<br />
<br />
{| class="wikitable" style="border-style: solid; border-width: 0px; margin-left: auto; margin-right: auto;"<br />
|+ <br />
|-<br />
| style="width: auto; text-align: left; background: #F6F6FB;" | '''NOTE!'''<br />
| style="width: auto; text-align: left; background: #F6F6FB;" | THERE IS NO SHORT TERM FIRMWARE AVAILABLE. PLEASE USE THE [[TAT100 Stable firmware|STABLE]] VERSION.<br />
|}<br />
<br />
<h2 style="width:100%; border: 1px solid #0054A6;border-bottom: 1px solid #0054A6; background: #0054A6; color: white; text-align: center;">CHANGELOG</h2><br />
<!--CHANGELOG NAUJINTI TEMPLATE VIDUJE--><br />
<br />
{| class="wikitable" style="width: 100%; valign="top"; align="center";|"<br />
|+<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION<br />
! style="width: 10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE<br />
! style="width: 35%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES<br />
! style="width: 40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES<br />
! style="width: 30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |KNOWN ISSUES<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* N/A<br />
|}<br />
<br />
<div class="mw-collapsible mw-collapsed" data-expandtext="View changelog history" data-collapsetext="Close this section" style="width:100%;"><br />
<div class="mw-collapsible-content" ><br />
{| class="wikitable" style="width: 100%;"<br />
|+<br />
! style="width: 15%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION<br />
! style="width: 10%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE<br />
! style="width: 35%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES<br />
! style="width: 40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES<br />
! style="width: 30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |KNOWN ISSUES<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* N/A<br />
|}<br />
</div></div></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT100_Short-term_firmware&diff=97011TAT100 Short-term firmware2024-03-25T14:36:16Z<p>Jonas.sterbavicius: </p>
<hr />
<div>__TOC__<br />
<br><br />
{| style="width: 100%; text-align: left; border-bottom: 1px solid #FFCC33; border-left: 1px solid #FFCC33;border-top: 1px solid #FFCC33;border-right: 1px solid #FFCC33; background: #FEF6E7; padding: 10px;"<br />
| style="padding: 10px;"| [[File:Warning.png|30px]]<br />
|<b>CAUTION!</b> <br> Both firmwares (Modem and BlueNRG) must be flashed into device. Failing so can lead to unexpected device behavior and rapid battery discharge.<br />
|}<br />
<br />
<div class="mw-collapsible mw-collapsed tlt-border" style="background: #FAFAFA;""><br />
<div style="font-weight:bold; color: black;"><font size="3"><b>TAT100 BlueNRG & Modem FIRMWARE UPDATE GUIDE</b></font></font></div><br />
----<br />
<div class="mw-collapsible-content" ><br />
{{Template: TAT FW update guide}}<br />
</div></div><br />
<br />
==Backup/BLE support Feature Firmware==<br />
{{Template:TAT-series Firmware and Software<br />
|fw_head=SHORT-TERM FIRMWARE<br />
|firmware_ver=Not Available<br />
|configurator_ver=Not Available<br />
|Bluenrg_ver= Not Available<br />
|Release_date=Not Available<br />
|FW_DL_HW31=<br />
|FW_DL_HW62=<br />
|CF_DL=<br />
|ALL_HW31=<br />
|ALL_HW62=<br />
|DL_ALL31=<br />
|DL_ALL62=<br />
|ALL_FMB=<br />
|DL_ALL_FMB=<br />
}}<br />
<br />
<br />
{| class="wikitable" style="border-style: solid; border-width: 0px; margin-left: auto; margin-right: auto;"<br />
|+ <br />
|-<br />
| style="width: auto; text-align: left; background: #F6F6FB;" | '''NOTE!'''<br />
| style="width: auto; text-align: left; background: #F6F6FB;" | THERE IS NO SHORT TERM FIRMWARE AVAILABLE. PLEASE USE THE [[TAT100 Stable firmware|STABLE]] VERSION.<br />
|}<br />
<br />
<br />
<h2 style="width:100%; border: 1px solid #0054A6;border-bottom: 1px solid #0054A6; background: #0054A6; color: white; text-align: center;">CHANGELOG</h2><br />
{| class="wikitable" style="width: 100%;"<br />
|+<br />
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION<br />
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE<br />
! style="width: 35%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES<br />
! style="width: 40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES<br />
! style="width: 30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |KNOWN ISSUES<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |N/A<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |N/A<br />
|}<br />
<br />
<br />
<div class="mw-collapsible mw-collapsed" data-expandtext="View changelog history" data-collapsetext="Close this section" style="width:100%;"><br />
<div class="mw-collapsible-content" ><br />
{| class="wikitable" style="width: 100%;"<br />
|+<br />
{| class="wikitable" style="width: 100%; valign="top"; align="center";|"<br />
|+<br />
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |VERSION<br />
! style="width: 5%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |RELEASE DATE<br />
! style="width: 35%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |CONFIGURATOR CHANGES<br />
! style="width: 40%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |FIRMWARE CHANGES<br />
! style="width: 30%; border: 1px solid white; border-bottom: 2px solid #0054A6; background: white; color: #0054A6; text-align: center;" |KNOWN ISSUES<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.16.Rev.543*<br>BlueNRG version: 10.3.12 for TAT100 HW ver.: 31<br> <br />
0.3.12 for TAT100 HW ver.: 62<br>Configurator version: 1.7.16_E.TAT100.R23 RELEASE<br><i>*was approved as STABLE</i><br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.08.08<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
*Updated Teltonika Configurator version to set Central device default IMEI to 300000000000000<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
*SMS command created for getting device statistics<br />
*Protection from writing other devices FW<br />
*Added condition to prevent modem waking up at midnight if scheduler is configured<br />
*Added reconfiguration mechanism that lets FW work with / without SMPS filterMissing<br />
*Fixed issue of missing 4th sensor's data with Monitoring operand<br />
*Fixed too frequent / unnecessary scans with all sensors configured as monitoring<br />
*Fixed sensors scan starting with monitoring operand when Backup tracker is configured<br />
*Backup tracker scan not starting right after<br />
*Time synchronization every 24 hours<br />
*Fixed LBS data sending issue<br />
*New AVL ID 20015 for Modem UpTime (in seconds)<br />
*Added response sending if recovery command is sent through GPRS<br />
*The next periodic record after Recovery mode deactivation being sent with AVL ID 20012 - fixed<br />
*Reduced EQ Core update frequency<br />
*Fixed battery consumption issue when GSM is jammed.<br />
*LED status changed from constant on to blinking mode to save the battery<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.16.Rev.531<br>BlueNRG version: 10.3.6 for TAT100 HW ver.: 31<br> <br />
0.3.6 for TAT100 HW ver.: 62<br>Configurator version: 1.7.16_R.TAT100.R5<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2022.04.14<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Added Recovery mode option<br />
* Added I/O element of Recovery Mode<br />
* Added more options of movement sensitivity threshold [50-1000mG]<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Added Recovery mode feature<br />
* Implemented Recovery mode activation from the Backup tracking alarm<br />
* Added EYE sensors support<br />
* Fixed Minor bugs regarding the sensors<br />
* Fixed Short period Recovery Mode records<br />
* Extended Backup Tracker: Central device IMEI range<br />
* Backup tracker: Scanning logic has been changed, scan duration is not configurable anymore, it is up to 60 seconds by default now.<br />
* Implemented Record timestamp shift feature<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Sometimes sensor records are randomly generated when using Backup Tracking with the USB cable plugged in.<br />
* Only 2 sensors are working correctly with Monitoring Operand, values from the 3rd and 4th sensor may not be received.<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.16.Rev.522<br>BlueNRG version: 10.2.21.Rev.01<br>Configurator version: 1.7.16_R.TAT100.R2-BACKUP<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2021.12.21<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
'''Backup firmware:'''<br />
* Changed required packets amount in backup tracker scenario and minimal scan duration<br />
* Fixed backup tracker alarm not triggering just before wakeup<br />
* Fixed backup tracker not detecting enough packets during BLE scan<br />
* Periodic records do not affect backup tracker alarm record generation<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Sometimes <code>Periodic</code>/<code>Schedule</code> record overwrites backup alarm record if both records are created at a same time.<br />
* Possible workaround would be to '''disable''' periodical records:<br />
<b>Tracking</b> → <b>Tracking Mode:</b> <code>None</code><br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.16.Rev.522<br>BlueNRG version: 10.2.21.Rev.01<br>Configurator version:<br>1.7.16_R.TAT100.R2-BLE<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2021.12.21<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
'''BLE firmware:'''<br />
* Fixed BLE sensor records with wrong event ID being sent<br />
* Fixed BLE sensor record duplicates with <code>On change</code> operand<br />
* Fixed BLE sensor <code>On Exit</code> record not generating when switching to sleep mode<br />
* Fixed <code>Custom1</code> sensor data in SMS being sent as NaN ''(empty)''<br />
* Fixed duplicate BLE sensor data after waking up<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
|-<br />
! style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |Firmware version: 55.00.15.Rev.519<br>BlueNRG version: 10.2.14<br>Configurator version: 1.7.16_R.TAT100.R2-BACKUP<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: center; vertical-align: top; background: white;" |2021.10.19<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
* Fixed fake movement detection on startup<br />
* Fixed problem when the device is stuck in <b>On Stop</b> tracking mode after reconfiguration<br />
* Added Power-On reason data and fixed version changes to device statistics<br />
* Fixed Backup tracker issue where the alarm mode is not immediately activated when the central device disappears<br />
* Fixed empty GSM I/O elements<br />
* Fixed an issue where UTC is added after each reconfiguration<br />
* Added record printing to <code>Dump log</code><br />
* LBS data is not included in records if GNSS fix was caught<br />
* Fixed NTP timesync failure if offset is zero<br />
* Improved record creation (wake up from sleep) during <b>Backup tracker</b> alarms<br />
<br><br />
<hr><br />
<div class="mw-collapsible mw-collapsed" data-expandtext="Expand changelog" data-collapsetext="Close this section" style="width:100%;"><br />
<br><br />
<div class="mw-collapsible-content" ><br />
<hr><br />
* Improved GNSS module control with <code>Static Navigation</code> and <code>LBS</code><br />
* Added prevention from inappropriate record generation if the battery is low (HW watchdog)<br />
* Added statistic element for USB connected uptime<br />
* Added timestamp to BlueNRG serial prints<br />
* Minor improvement for BlueNRG firmware update via configurator<br />
* Added filter for <code>LBS</code> cell_id duplicates<br />
* Improved Bluetooth® sensor record creation with <code>'On Change'</code> operand<br />
* Added Bluetooth® sensor support<br />
* Added condition to skip LBS data update if location source is only GNSS<br />
* Increased retries of AT+# command in order to avoid empty LBS data from modem<br />
* Changed <code>Open link timeout</code> to 15s<br />
* Fixed an issue where the tracking mode would change from the scheduler to periodic<br />
* Improved logic for multiple <code>FOTA Web</code> tasks update in the same connection<br />
* Implemented rule for additional connection to <code>FOTA Web</code> after baseband firmware update<br />
* Added accelerometer version information inside '.info' serial command<br />
* Fixed an issue with battery voltage <code>I/O element</code> when record saving is overlapping with a firmware update<br />
* Fixed <code>Scheduler</code> record sending at midnight<br />
* Fixed missed LBS values inside <code>I/O elements</code><br />
* Fixed an issue when GNSS speed is not zero while the device is in a stationary position<br />
* General minor improvements<br />
</div></div><br />
| style="border: 1px solid white; border-bottom: 2px solid #E8E8E8; text-align: left; vertical-align: top; background: white;" |<br />
|-<br />
|}<br />
<br />
</div></div><br />
<br></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT240&diff=97008TAT2402024-03-25T08:32:05Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:FM Home<br />
|model=TAT240<br />
|description=TAT240 is a tamper-proof, 4G LTE (CAT1), 3G/2G fallback, GNSS, Bluetooth® device for asset tracking and maximum protection against thefts of containers, and trailers, as well as it could be used in a wide range of applications from valuable goods to tools tracking. The tamper detection feature of TAT240 ensures significantly improved protection of the assets.<br />
|image=TAT240 BT SIG.jpg<br />
|link=https://teltonika-gps.com/products/trackers/assets-workforce/tat240<br />
|FW&SW=[[TAT240 Firmware and configurator|Firmware and configurator]]<br />
|errata=*[[TAT240 Firmware errata|Firmware errata]]<br />
|AVLID=*[[TAT240 AVL ID List| AVL ID List]]<br />
|Safety Instructions=[[TAT240 Safety Instructions|Safety Instructions]]<br />
|FAQ=[[TAT240 FAQ|FAQ]]<br />
<br />
|datasheet_date=2024-03-25<br />
|quick_manual_date=2024-03-25<br />
|Wiring_scheme_icon=<br />
|Wiring_scheme=<br />
}}<br />
<br />
[[Category: Autonomous Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT141&diff=97007TAT1412024-03-25T08:31:47Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:FM Home<br />
|model=TAT141<br />
|description=TAT141 is a 4G LTE (CAT M1/NB2), 3G/2G fallback, GNSS, Bluetooth® device for asset tracking and additional protection against thefts of valuable goods, as well as it could be used in wide range of applications from tools tracking to container tracking<br />
|image=TAT141 BT SIG.jpg<br />
|link=https://teltonika-gps.com/products/trackers/assets-workforce/tat141<br />
|FW&SW=[[TAT141 Firmware and configurator|Firmware and configurator]]<br />
|errata=*[[TAT141 Firmware errata|Firmware errata]]<br />
|AVLID=*[[TAT141 AVL ID List| AVL ID List]]<br />
|Safety Instructions=[[TAT141 Safety Instructions|Safety Instructions]]<br />
|FAQ=[[TAT141 FAQ|FAQ]]<br />
<br />
|datasheet_date=2024-03-25<br />
|quick_manual_date=2024-03-25<br />
|Wiring_scheme_icon=<br />
|Wiring_scheme=<br />
<br />
}}<br />
<br />
[[Category: Autonomous Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT140&diff=97006TAT1402024-03-25T08:31:30Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:FM Home<br />
|model=TAT140<br />
|description=TAT140 is a 4G LTE (CAT1), 3G/2G fallback, GNSS, Bluetooth® device for asset tracking and additional protection against thefts of valuable goods, as well as it could be used in wide range of applications from tools tracking to container tracking.<br />
|image=TAT140_BT_SIG.jpg<br />
|link=https://teltonika-gps.com/products/trackers/assets-workforce/tat140<br />
|FW&SW=[[TAT140 Firmware and configurator|Firmware and configurator]]<br />
|errata=*[[TAT140 Firmware errata|Firmware errata]]<br />
|AVLID=*[[TAT140 AVL ID List| AVL ID List]]<br />
|Safety Instructions=[[TAT140 Safety Instructions|Safety Instructions]]<br />
|FAQ=[[TAT140 FAQ|FAQ]]<br />
<br />
|datasheet_date=2024-03-25<br />
|quick_manual_date=2024-03-25<br />
|Wiring_scheme_icon=<br />
|Wiring_scheme=<br />
<br />
}}<br />
<br />
<br />
[[Category:Autonomous Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TAT100&diff=97005TAT1002024-03-25T08:30:59Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:FM Home<br />
|model=TAT100<br />
|description=TAT100 is a device for asset tracking and additional protection against thefts of valuable goods, as well as it could be used in wide range of applications from tools tracking to container tracking <br />
|image=TAT100 BT SIG.jpg<br />
|link=https://teltonika-gps.com/products/trackers/assets-workforce/tat100<br />
|FW&SW=[[TAT100 Firmware and configurator|Firmware and configurator]]<br />
|errata=*[[TAT100 Firmware errata|Firmware errata]]<br />
|AVLID=*[[TAT100 AVL ID List| AVL ID List]]<br />
|Safety Instructions=[[TAT100 Safety Instructions|Safety Instructions]]<br />
|FAQ=[[TAT100 FAQ|FAQ]]<br />
<br />
|datasheet_date=2024-03-25<br />
|quick_manual_date=2024-03-25<br />
|Wiring_scheme_icon=<br />
|Wiring_scheme=<br />
<br />
}}<br />
<br />
<br />
[[Category:Autonomous Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-TAT100.pdf&diff=97004File:DS-TAT100.pdf2024-03-25T08:27:53Z<p>Jonas.sterbavicius: v1.4</p>
<hr />
<div>== Summary ==<br />
v1.4</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-TAT141.pdf&diff=97002File:DS-TAT141.pdf2024-03-25T08:26:28Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:DS-TAT141.pdf</p>
<hr />
<div>== Summary ==<br />
v2.1</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:QM-TAT141.pdf&diff=97001File:QM-TAT141.pdf2024-03-25T08:25:41Z<p>Jonas.sterbavicius: v1.4</p>
<hr />
<div>== Summary ==<br />
v1.4</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:QM-TAT240.pdf&diff=96999File:QM-TAT240.pdf2024-03-25T08:23:28Z<p>Jonas.sterbavicius: v1.1</p>
<hr />
<div>== Summary ==<br />
v1.1</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:QM-TAT100.pdf&diff=96996File:QM-TAT100.pdf2024-03-25T08:20:01Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:QM-TAT100.pdf</p>
<hr />
<div></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:QM-TAT140.pdf&diff=96995File:QM-TAT140.pdf2024-03-25T08:19:18Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:QM-TAT140.pdf</p>
<hr />
<div></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-TAT140.pdf&diff=96994File:DS-TAT140.pdf2024-03-25T08:17:54Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:DS-TAT140.pdf</p>
<hr />
<div></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-TAT140.pdf&diff=96992File:DS-TAT140.pdf2024-03-25T08:14:05Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:DS-TAT140.pdf</p>
<hr />
<div></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-TAT240.pdf&diff=96991File:DS-TAT240.pdf2024-03-25T08:13:26Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:DS-TAT240.pdf</p>
<hr />
<div></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-TMT250.pdf&diff=96814File:DS-TMT250.pdf2024-03-19T14:42:59Z<p>Jonas.sterbavicius: v1.3</p>
<hr />
<div>== Summary ==<br />
v1.3</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=TMT250&diff=96813TMT2502024-03-19T14:22:28Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:FM Home<br />
|model=TMT250<br />
|description=TMT250 is an autonomous personal tracker with GNSS, GSM and Blue-tooth connectivity<br />
|image=TMT250_small_t.png<br />
|link=https://teltonika-gps.com/products/trackers/assets-workforce/tmt250<br />
|FW&SW=[[TMT250 Firmware and configurator|Firmware and configurator]]<br />
|errata=*[[TMT250 Firmware errata|Firmware errata]]<br />
|AVLID=*[[TMT250 AVL ID List| AVL ID List]]<br />
|Safety Instructions=[[TMT250 Safety Instructions|Safety Instructions]]<br />
|FAQ=[[TMT250 FAQ|FAQ]]<br />
<br />
|datasheet_date=2024-03-19<br />
|quick_manual_date=2024-01-10<br />
|Wiring_scheme_icon=<br />
|Wiring_scheme=<br />
<br />
}}<br />
<br />
<br />
[[Category:Autonomous Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=DSM&diff=96652DSM2024-03-14T09:26:37Z<p>Jonas.sterbavicius: </p>
<hr />
<div>'''DSM (D'''river '''S'''afety and '''M'''onitoring solution). This product with Deep-Learning technology can support drowsiness, distraction and yawning attention warnings as well as periodic event data and picture footage transfer. <br />
<br />
'''We would like to introduce our new solution, allowing the possibility to connect two cameras, DSM and DashCam or DualCam, to one device, FMC650'''. By utilizing the two RS232 ports on the FMC650, you can connect the DSM camera for driver status monitoring to one port and the DualCam or DashCam camera for road and cargo monitoring to the second port. '''[https://wiki.teltonika-gps.com/view/DSM_Configuration#Connecting_two_cameras_simultaneously_for_FMx650 Configuration]''' <br />
<br />
[[File:Mdsm22 106.png|370x320px|right]]<br />
<br />
*[[DSM_First_Start | First Start]]<br />
*[[DSM_Camera_Manual | Camera Manual]]<br />
*[[DSM Calibration]]<br />
*[[DSM Configuration]]<br />
*[[DSM Communication Protocol]]<br />
*[[DSM Data Sending Parameters ID]]<br />
*[[DSM SMS commands]]<br />
*[[DSM Certifications & Approvals]]<br />
*[[DSM Firmware errata]]<br />
*[[DSM Firmware and Drivers update]]<br />
*[[DSM FAQ]]<br />
*[[DSM EAN]]<br />
*[[DSM Testing Guide]]<br />
*[[DSM Integration on platfroms]]<br />
*[[CloudView Platform]]<br />
==Downloads==<br />
'''Manual & Documentation'''<br><br />
<br />
[[File:pdf_icon.png|32px|link=]]<br />
[[Media:Datasheet TELTONIKA DSM V1.2.pdf|DSM Datasheet (EN)]]<br />
<small>(Updated on: 2023-07-17)</small><br />
<br />
==External links==<br />
[https://teltonika-gps.com/products/accessories/video-telematics/teltonika-dsm Teltonika DSM]<br />
<br />
[[Category: Video Solutions]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=FMC125_TRA&diff=96535FMC125 TRA2024-03-06T09:23:15Z<p>Jonas.sterbavicius: /* Attachments */</p>
<hr />
<div>{{TRA UAE Certificate<br />
|model=FMC125<br />
|model1=FMC125<br />
|manufacturer=TELTONIKA UAB<br />
|apprnumber=ER94582/21<br />
}}<br />
<br />
<br />
==Attachments==<br />
{| style="margin: 0 auto;valign="center""<br />
|[[File:FMC125_1_TRA.png|thumb|center|150px|FMC125 TRA Jordan Certificate, page 1/3]]<br />
|[[File:FMC125_2_TRA.png|thumb|center|150px|FMC125 TRA Jordan Certificate, page 2/3]]<br />
|[[File:FMC125_3_TRA.png|thumb|center|150px|FMC125 TRA Jordan Certificate, page 3/3]]<br />
|}<br />
To download a PDF version of the declaration, [[Media:FMC125 TRA Certificate.pdf|here]].</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=FMC230&diff=96450FMC2302024-03-05T12:04:47Z<p>Jonas.sterbavicius: </p>
<hr />
<div>[[File:FMC230-MCIBO-datasheet-2023-12-28.png|thumb|400x300px|right|upright=0.35|FMC230]]<br />
Advanced LTE terminal with flexible inputs configuration and IP67 protection<br />
<br />
*[[FMC230 First Start|First Start]]<br />
*[[FMC230 Manual|Manual]]<br />
*[[FMC230 Configuration|Configuration]]<br />
*{{{certification|[[FMC230 Certification & Approvals|Certifications & Approvals]]}}}<br />
*{{{memberships|[[FMC230 Memberships|Memberships]]}}}<br />
*{{{Nomenclature_classification_codes|[[FMC230 Nomenclature, classification codes|Nomenclature, Classification codes]]}}}<br />
<!--*{{{usage_scenarios|[[FMC230 Usage Scenarios|Usage Scenarios]]}}}--><br />
*{{{product_change_notifications|[[FMC230 Product Change Notifications|Product Change Notifications]]}}}<br />
*{{{FW&SW|}}}<br />
*{{{errata|[[FMC230 firmware_errata|Firmware errata]]}}}<br />
*{{{AVLID|[[FMC230 Teltonika Data Sending Parameters ID|Teltonika Data Sending Parameters ID]]}}}<br />
*{{{promotional_material|[[FMC230 Promotional Material|Promotional Material]]}}}<br />
*{{{Safety Instructions|}}}<br />
*{{{FAQ|}}}<br />
<br />
==Downloads==<br />
<br />
<big>'''Manual & Documentation'''</big><br><br />
{|<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:DS-FMC230.pdf|FMC230 Datasheet (EN)]]<br />
|<small>(Updated on: {{{datasheet_date|2024-03-05}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:QM-FMC230.pdf|FMC230 Quick Manual (EN)]]<br />
|<small>(Updated on: {{{quick_manual_date|2023-02-07}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-EN.pdf|FMx2 IP67 Flyer (EN)]]<br />
|<small>(Updated on: {{{FMx2-IP67-flyer_date|2023-06-21}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-RU.pdf|FMx2 IP67 Flyer (RU)]]<br />
|<small>(Updated on: {{{FMx2-IP67-flyer_date|2023-06-21}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-ES.pdf|FMx2 IP67 Flyer (ES)]]<br />
|<small>(Updated on: {{{FMx2-IP67-flyer_date|2023-06-21}}})</small><br />
|}<br />
<br />
<big>'''Driver & Utility'''</big><br><br />
{|<br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Media:TeltonikaCOMDriver.zip|PC drivers]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Firmware versions|Firmware]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Teltonika Configurator versions|Configurator]]<br />
|}<br />
<ul></ul><br />
{{{suppress_link|<br />
==External links==<br />
{{{link|https://teltonika-gps.com/products/trackers/FMC230/}}}}}}<br />
<br />
[[Category:Advanced Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=FMC234&diff=96449FMC2342024-03-05T12:04:19Z<p>Jonas.sterbavicius: </p>
<hr />
<div>[[Image:FMC234 MBIBO-side-2024-02-26.png |thumb|400x300px|right|upright=0.35|FMC234]]<br />
Advanced LTE terminal with flexible inputs configuration and IP67 protection<br />
<br />
*[[FMC234 First Start|First Start]]<br />
*[[FMC234 Manual|Manual]]<br />
*[[FMC234 Configuration|Configuration]]<br />
*{{{certification|[[FMC234 Certification & Approvals|Certifications & Approvals]]}}}<br />
*{{{memberships|[[FMC234 Memberships|Memberships]]}}}<br />
*{{{Nomenclature_classification_codes|[[FMC234 Nomenclature, classification codes|Nomenclature, Classification codes]]}}}<br />
<!--*{{{usage_scenarios|[[FMC234 Usage Scenarios|Usage Scenarios]]}}}--><br />
*{{{product_change_notifications|[[FMC234 Product Change Notifications|Product Change Notifications]]}}}<br />
*{{{FW&SW|}}}<br />
*{{{errata|[[FMC234 firmware_errata|Firmware errata]]}}}<br />
*{{{AVLID|[[FMC234 Teltonika Data Sending Parameters ID|Teltonika Data Sending Parameters ID]]}}}<br />
*{{{promotional_material|[[FMC234 Promotional Material|Promotional Material]]}}}<br />
*{{{Safety Instructions|}}}<br />
*{{{FAQ|}}}<br />
<br />
==Downloads==<br />
<br />
<big>'''Manual & Documentation'''</big><br><br />
{|<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:DS-FMC234.pdf|FMC234 Datasheet (EN)]]<br />
|<small>(Updated on: {{{datasheet_date|2024-03-05}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:QM-FMC234.pdf|FMC234 Quick Manual (EN)]]<br />
|<small>(Updated on: {{{quick_manual_date|2023-12-04}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-EN.pdf|FMx2 IP67 Flyer (EN)]]<br />
|<small>(Updated on: {{{datasheet_date|2023-06-21}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-RU.pdf|FMx2 IP67 Flyer (RU)]]<br />
|<small>(Updated on: {{{quick_manual_date|2023-06-21}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-ES.pdf|FMx2 IP67 Flyer (ES)]]<br />
|<small>(Updated on: {{{quick_manual_date|2023-06-21}}})</small><br />
|}<br />
<br />
<big>'''Driver & Utility'''</big><br><br />
{|<br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Media:TeltonikaCOMDriver.zip|PC drivers]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Firmware versions|Firmware]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Teltonika Configurator versions|Configurator]]<br />
|}<br />
<ul></ul><br />
{{{suppress_link|<br />
==External links==<br />
{{{link|https://teltonika-gps.com/products/trackers/FMC234/}}}}}}<br />
<br />
[[Category:Advanced Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=FMC225&diff=96448FMC2252024-03-05T12:03:40Z<p>Jonas.sterbavicius: </p>
<hr />
<div>[[Image:FMC225-MCIBO 4000x4000 8.png|thumb|400x300px|right|upright=0.35|FMC225]]<br />
Professional LTE terminal with GNSS and LTE/3G/GSM connectivity, RS485/RS232 interfaces and backup battery<br />
<br />
*[[FMC225 First Start|First Start]]<br />
*[[FMC225 Manual|Manual]]<br />
*[[FMC225 Configuration|Configuration]]<br />
*{{{certification|[[FMC225 Certification & Approvals|Certifications & Approvals]]}}}<br />
*{{{Memberships|[[FMC225 Memberships|Memberships]]}}}<br />
*{{{Nomenclature_classification_codes|[[FMC225 Nomenclature, classification codes|Nomenclature, Classification codes]]}}}<br />
<!--*{{{usage_scenarios|[[FMC225 Usage Scenarios|Usage Scenarios]]}}}--><br />
*{{{product_change_notifications|[[FMC225 Product Change Notifications|Product Change Notifications]]}}}<br />
*{{{FW&SW|}}}<br />
*{{{errata|[[FMC225 firmware_errata|Firmware errata]]}}}<br />
*{{{AVLID|[[FMC225 Teltonika Data Sending Parameters ID|Teltonika Data Sending Parameters ID]]}}}<br />
*{{{promotional_material|[[FMC225 Promotional Material|Promotional Material]]}}}<br />
*{{{Safety Instructions|}}}<br />
*{{{FAQ|}}}<br />
<br />
==Downloads==<br />
<br />
<big>'''Manual & Documentation'''</big><br><br />
{|<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:DS-FMC225.pdf|FMC225 Datasheet (EN)]]<br />
|<small>(Updated on: {{{datasheet_date|2024-03-05}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:QM-FMC225.pdf|FMC225 Quick Manual (EN)]]<br />
|<small>(Updated on: {{{quick_manual_date|2023-02-07}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-EN.pdf|FMx2 IP67 Flyer (EN)]]<br />
|<small>(Updated on: {{{FMx2-IP67-flyer_date|2023-06-21}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-RU.pdf|FMx2 IP67 Flyer (RU)]]<br />
|<small>(Updated on: {{{FMx2-IP67-flyer_date|2023-06-21}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:FMx2-IP67-Flyer-ES.pdf|FMx2 IP67 Flyer (ES)]]<br />
|<small>(Updated on: {{{FMx2-IP67-flyer_date|2023-06-21}}})</small><br />
|}<br />
<br />
<big>'''Driver & Utility'''</big><br><br />
{|<br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Media:TeltonikaCOMDriver.zip|PC drivers]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Firmware versions|Firmware]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Teltonika Configurator versions|Configurator]]<br />
|}<br />
<ul></ul><br />
{{{suppress_link|<br />
==External links==<br />
{{{link|https://teltonika-gps.com/products/trackers/FMC225/}}}}}}<br />
<br />
[[Category:Professional Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=FMC13A&diff=96447FMC13A2024-03-05T12:00:44Z<p>Jonas.sterbavicius: </p>
<hr />
<div>[[Image:FMC13A-side-2023-12-29.png|thumb|400x300px|right|upright=0.35|FMC13A]]<br />
Advanced LTE terminal with flexible inputs configuration<br />
<br />
*[[FMC13A First Start|First Start]]<br />
*[[FMC13A Manual|Manual]]<br />
*[[FMC13A Configuration|Configuration]]<br />
*{{{certification|[[FMC13A Certification & Approvals|Certifications & Approvals]]}}}<br />
*{{{memberships|[[FMC13A Memberships|Memberships]]}}}<br />
*{{{Nomenclature_classification_codes|[[FMC13A Nomenclature, classification codes|Nomenclature, Classification codes]]}}}<br />
<!--*{{{usage_scenarios|[[FMC13A Usage Scenarios|Usage Scenarios]]}}}--><br />
*{{{product_change_notifications|[[FMC13A Product Change Notifications|Product Change Notifications]]}}}<br />
*{{{FW&SW|}}}<br />
*{{{errata|[[FMC13A firmware_errata|Firmware errata]]}}}<br />
*{{{AVLID|[[FMC13A Teltonika Data Sending Parameters ID|Teltonika Data Sending Parameters ID]]}}}<br />
*{{{promotional_material|[[FMC13A Promotional Material|Promotional Material]]}}}<br />
*{{{Safety Instructions|}}}<br />
*{{{FAQ|}}}<br />
<br />
==Downloads==<br />
<br />
<big>'''Manual & Documentation'''</big><br><br />
{|<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:DS-FMC13A.pdf|FMC13A Datasheet (EN)]]<br />
|<small>(Updated on: {{{datasheet_date|2024-03-05}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:QM-FMC13A.pdf|FMC13A Quick Manual (EN)]]<br />
|<small>(Updated on: {{{quick_manual_date|2023-02-07}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:North-America-flyer.pdf|North America Flyer (EN)]]<br />
|<small>(Updated on: {{{North_America_flyer_date|2023-06-21}}})</small><br />
|}<br />
<br />
<big>'''Driver & Utility'''</big><br><br />
{|<br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Media:TeltonikaCOMDriver.zip|PC drivers]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Firmware versions|Firmware]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Teltonika Configurator versions|Configurator]]<br />
|}<br />
<ul></ul><br />
{{{suppress_link|<br />
==External links==<br />
{{{link|https://teltonika-gps.com/products/trackers/fmc13a}}}}}}<br />
<br />
[[Category:Advanced Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=FMC130&diff=96446FMC1302024-03-05T11:52:54Z<p>Jonas.sterbavicius: </p>
<hr />
<div>{{Template:FM Home<br />
|model=FMC130<br />
|description=Advanced LTE terminal with flexible inputs configuration|image=Screenshot 2023-12-18 090141.png<br />
|link=https://teltonika-gps.com/product/fmc130/}}<br />
|datasheet_date=2024-03-05<br />
<br />
[[Category:Advanced Trackers]]</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=Template:FM_Home&diff=96445Template:FM Home2024-03-05T11:51:38Z<p>Jonas.sterbavicius: /* Downloads */</p>
<hr />
<div>[[Image:{{{image}}}|thumb|400x300px|right|upright=0.35|{{{model|FM device}}}]]<br />
{{{description|FM device}}}<br />
<br />
*[[{{{model}}} First Start|First Start]]<br />
*[[{{{model}}} Manual|Manual]]<br />
*[[{{{model}}} Configuration|Configuration]]<br />
*{{{certification|[[{{{model}}} Certification & Approvals|Certifications & Approvals]]}}}<br />
*{{{membership|[[{{{model}}} Memberships|Memberships]]}}}<br />
*{{{Nomenclature_classification_codes|[[{{{model}}} Nomenclature, classification codes|Nomenclature, Classification codes]]}}}<br />
<!--*{{{usage_scenarios|[[{{{model}}} Usage Scenarios|Usage Scenarios]]}}}--><br />
*{{{product_change_notifications|[[{{{model}}} Product Change Notifications|Product Change Notifications]]}}}<br />
*{{{FW&SW|}}}<br />
*{{{errata|[[{{{model}}} firmware_errata|Firmware errata]]}}}<br />
*{{{AVLID|[[{{{model}}} Teltonika Data Sending Parameters ID|Teltonika Data Sending Parameters ID]]}}}<br />
*{{{promotional_material|[[{{{model}}} Promotional Material|Promotional Material]]}}}<br />
*{{{Safety Instructions|}}}<br />
*{{{FAQ|}}}<br />
<br />
==Downloads==<br />
<br />
<big>'''Manual & Documentation'''</big><br><br />
{|<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:DS-{{{model}}}.pdf|{{{model}}} Datasheet (EN)]]<br />
|<small>(Updated on: {{{datasheet_date|2024-03-05}}})</small><br />
|-<br />
|[[File:pdf_icon.png|32px|link=]]<br />
|[[Media:QM-{{{model}}}.pdf|{{{model}}} Quick Manual (EN)]]<br />
|<small>(Updated on: {{{quick_manual_date|2023-08-29}}})</small><br />
|-<br />
|{{{Wiring_scheme_icon|[[File:image_icon.png|32px|link=]]}}}<br />
|{{{Wiring_scheme|[[Media:Wiring-scheme-{{{model}}}.jpg|{{{model}}} Wiring scheme (EN)]]}}}<br />
|<br />
|}<br />
<br />
<big>'''Driver & Utility'''</big><br><br />
{|<br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Media:TeltonikaCOMDriver.zip|PC drivers]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Firmware versions|Firmware]] <br><br />
|[[File:zip_icon.png|32px|link=]]<br />
|[[Teltonika Configurator versions|Configurator]]<br />
|}<br />
<ul></ul><br />
{{{suppress_link|<br />
==External links==<br />
{{{link|https://teltonika-gps.com/products/vehicle-tracking/}}}}}}</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-FMC234.pdf&diff=96444File:DS-FMC234.pdf2024-03-05T11:50:07Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:DS-FMC234.pdf</p>
<hr />
<div>== Summary ==<br />
v1.0.6</div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-FMC225.pdf&diff=96443File:DS-FMC225.pdf2024-03-05T11:49:35Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:DS-FMC225.pdf</p>
<hr />
<div></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-FMC130.pdf&diff=96442File:DS-FMC130.pdf2024-03-05T11:49:08Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:DS-FMC130.pdf</p>
<hr />
<div></div>Jonas.sterbaviciushttps://wiki.teltonika-gps.com/index.php?title=File:DS-FMC13A.pdf&diff=96441File:DS-FMC13A.pdf2024-03-05T11:48:31Z<p>Jonas.sterbavicius: Jonas.sterbavicius uploaded a new version of File:DS-FMC13A.pdf</p>
<hr />
<div></div>Jonas.sterbavicius