0
edits
Changes
no edit summary
{{#if:{{{MM_Movement_source|}}}
{{#if:{{{MM_Movement_source|}}}
|
|
|====Movement Source====
|===Movement Source===
User can select which source will be used to determine when vehicle is on stop or moving. When multiple are selected, if any of selected are active, Vehicle MOVING mode is used.
User can select which source will be used to determine when vehicle is on stop or moving. When multiple are selected, if any of selected are active, Vehicle MOVING mode is used.
}}
}}
{{#if:{{{TFT_can|}}}
{{#if:{{{TFT_can|}}}
|
|
|====Speed source====
|===Speed source===
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.
If TFT100 is used with CAN modification extra settings option will we available for choosing Speed source.
[[Image:speed_source.PNG]]
[[Image:speed_source.PNG]]
{{#if:{{{TAT100_no_show|}}}
{{#if:{{{TAT100_no_show|}}}
|
|
|====Records settings====
|===Records settings===
Here user can enable or disable records when GPS is not available (no GPS fix). <br>
Here user can enable or disable records when GPS is not available (no GPS fix). <br>
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br>
* <b>After Position Fix</b> - Device must have GPS fix and time to save/send records. <br>
{{#if:{{{TFT_system_settings|}}}
{{#if:{{{TFT_system_settings|}}}
|
|
|====PDOP filter====
|===PDOP filter===
User can choose to enable or disable the PDOP filter. This feature allows to discard GNSS module output data if PDOP (Position Dilution of Precision) value is above selected threshold.
User can choose to enable or disable the PDOP filter. This feature allows to discard GNSS module output data if PDOP (Position Dilution of Precision) value is above selected threshold.
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.
* <b>PDOP filter threshold</b> - PDOP filter threshold value can be entered from which the parameters will be filtered.
{{#if:{{{TFT_system_settings|}}}
{{#if:{{{TFT_system_settings|}}}
|
|
|====Input/Output Mode====
|===Input/Output Mode===
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:
User can choose specific external pins to work as an input or as output. Possible valid input/output configurations:
*Digital input 3 and Digital input 4 (value:5),
*Digital input 3 and Digital input 4 (value:5),
{{#if:{{{MM_LED_indication|}}}
{{#if:{{{MM_LED_indication|}}}
|
|
|====LED Indication====
|===LED Indication===
User can turn on or off the indication LEDs.
User can turn on or off the indication LEDs.
}}
}}
|}
|}
{|
{{#if:{{{AT_no_show|}}}
|===GNSS Source settings===
User can configure which GNSS system(s) to use.<br />
User can configure which GNSS system(s) to use.<br />
User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together.
User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together.
*GPS + GLONASS;
*GPS + GLONASS;
*GPS + GLONASS + Galileo.
*GPS + GLONASS + Galileo.
}}
|}
{|
{|
{{#if:{{{TST_battery_charge_mode|}}}
{{#if:{{{TST_battery_charge_mode|}}}
|
|
|====Battery Charge Mode====
|===Battery Charge Mode===
Here user can change battery charger settings, where charging is allowed.
Here user can change battery charger settings, where charging is allowed.
Battery will be charged: '''''On Need''''' (battery will be charged anytime when it needs to be charged) and '''''After Ignition ON''''' (battery will be charged only when ignition is on).
Battery will be charged: '''''On Need''''' (battery will be charged anytime when it needs to be charged) and '''''After Ignition ON''''' (battery will be charged only when ignition is on).
{{#if:{{{TFT_system_settings|}}}
{{#if:{{{TFT_system_settings|}}}
|
|
|====Analog Input Value Range====
|===Analog Input Value Range===
User can choose analog input range of 15 V or 150 V.
User can choose analog input range of 15 V or 150 V.
}}
}}
{{#if:{{{Data_protocol|}}}
{{#if:{{{Data_protocol|}}}
|
|
|====Data Protocol====
|===Data Protocol===
User can choose which protocol version to use for data sending to server.
User can choose which protocol version to use for data sending to server.
*Codec 8 supports up to 255 AVL ID;
*Codec 8 supports up to 255 AVL ID;
{{#if:{{{PT_Power_on|}}}
{{#if:{{{PT_Power_on|}}}
|
|
|====Power On By USB/Charger====
|===Power On By USB/Charger===
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>.
Device supports two working modes: normal mode, where the device works as usual, and charging mode, which is entered when ''Power On By USB/Charger'' parameter is <b>disabled</b>. To enter normal mode, device can be turned on by power button or by USB charger, if ''Power On By USB/Charger'' parameter is set to <b>Enable</b>.
}}
}}
|}
|}
{|
{|
{{#if:{{{LBS_tracking|}}}
{{#if:{{{Location_settings|}}}
|
|
|==Tracking with LBS==
|==Location Settings==
[[Image:Location_settings{{{model|X}}}.png|right|]]
}}
|}
{|
{{#if:{{{LBS_tracking|}}}
|
|===Location Source===
[[Image:LBS1.jpg|right]]
[[Image:LBS1.jpg|right]]
*If <b>GNSS or LBS</b> is selected, device will use GNSS if the satellites are visible, if not - it will start sending cell towers information to the server, which will be able to calculate the approximate location using LBS.
*If <b>GNSS or LBS</b> is selected, device will use GNSS if the satellites are visible, if not - it will start sending cell towers information to the server, which will be able to calculate the approximate location using LBS.
Also, <b>GSM Cell ID</b> and <b>Active GSM Operator</b> should have at least Low priority in I/O settings.
Also, <b>GSM Cell ID</b> and <b>Active GSM Operator</b> should have at least Low priority in I/O settings.[[Image:LBS IO.jpg|right]]
[[Image:LBS IO.jpg|left]]
<br><br><br>
<br>
}}
<br>
|}
<br>
<br>
===GNSS Source settings===
User can configure which GNSS system(s) to use.<br />
User has a choice to use only one system between GPS, GLONASS, Galileo or Beidou and it is possible to choose two or three systems together. One exception is that you cannot combine BeiDou and GLONASS systems together.
Examples of non-configurable GNSS source combinations are:
*GLONASS + BeiDou;
*Galileo + GLONASS + BeiDou;
*GPS + GLONASS + BeiDou;
*GPS + Galileo + GLONASS + BeiDou.
List of configurable GNSS sources:
*GPS only;
*GPS + BeiDou;
*GPS + GLONASS;
*GPS + GLONASS + Galileo.
}}
}}
|}
|}
{|
{|
{{#if:{{{TAT100_show|}}}
{{#if:{{{AT_show|}}}
|
|
|==GNSS control==
|===GNSS control===
User can manually turn ON/OFF the GNSS module. For example, if button 'Turn off GNSS' is pressed and device is trying to acquire GNSS fix for a record, it will turn GNSS back on. If GNSS module is turned ON using 'Turn on GNSS' button, it will be active for undefined period of time until USB is disconnected and device is going to sleep, record sending is finished or the 'Turn off GNSS' button is pressed again.
User can manually turn ON/OFF the GNSS module. For example, if button 'Turn off GNSS' is pressed and device is trying to acquire GNSS fix for a record, it will turn GNSS back on. If GNSS module is turned ON using 'Turn on GNSS' button, it will be active for undefined period of time until USB is disconnected and device is going to sleep, record sending is finished or the 'Turn off GNSS' button is pressed again.
<br><br><br><br><br><br><br><br><br>
<br><br><br><br><br><br><br><br><br>
{|
{|
{{#if:{{{TAT100_show|}}}
{{#if:{{{AT_show|}}}
|
|
|==Coordinate acquisition timeout==
|===Coordinate acquisition timeout===
The configured time adds a delay when the coordinates of the device are taken to stabilize and ensure accuracy. Important thing to note that TAT100 can take up to 180 seconds to get the GPS fix and the configured timeout would only go after the GPS fix timeout has finished or the coordinates were received.
The configured time adds a delay when the coordinates of the device are taken to stabilize and ensure accuracy. Important thing to note that TAT100 can take up to 180 seconds to get the GPS fix and the configured timeout would only go after the GPS fix timeout has finished or the coordinates were received.
{|
{|
{{#if:{{{TAT100_show|}}}
{{#if:{{{AT_show|}}}
|
|
|==Static Navigation Settings==
|===Static Navigation Settings===
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.
Static navigation helps to save power by not enabling the GPS module and instantly generating a record if movement was not detected.
When enabled the device monitors the accelerometer and registers movement events by configured movement sensitivity. When the device wakes up to save and send a periodic record, and movement was not registered, the device will use the last known coordinates and will generate a record without turning ON the GPS module. However, if there are no last known coordinates, then the device will enable the GPS module and will try to get a new GPS fix.<br />
When enabled the device monitors the accelerometer and registers movement events by configured movement sensitivity. When the device wakes up to save and send a periodic record, and movement was not registered, the device will use the last known coordinates and will generate a record without turning ON the GPS module. However, if there are no last known coordinates, then the device will enable the GPS module and will try to get a new GPS fix.<br />
The functionality is illustrated in the flowchart below:
The functionality is illustrated in the flowchart below:
[[File:Staticnavflowchart.png]]
[[File:Staticnavflowchart.png]]
}}
|}
{|
{{#if:{{{AT_show|}}}
|
|==Movement sensitivity==
This feature sets the sensitivity threshold levels for movement event registration. Higher configured level makes the device “less sensitive” and vice versa. Currently, there are 10 configurable Movement Sensitivity levels. Levels are measured in mG - thousandth parts of the gravitational force equivalent or gravitational acceleration of Earth (9.8 m/s). It means that if Movement Sensitivity is set to 1000 mG, the device has to be free falling, experience fierce stops/accelerations or vibrations to detect movement.<br />
}}
}}
|}
|}
Here the user can set the movement start/stop delays. <br/>
Here the user can set the movement start/stop delays. <br/>
''For example'', if the '''''Movement Start Delay''''' is set to 1s and '''''Movement Stop Delay''''' to 60s, the movement will be detected after 1s of moving and defined as stopped after 60s when device stopped moving.
''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.
}}
}}
|}
|}
