Difference between revisions of "Starting with Teltonika Telematics"

From Wiki Knowledge Base | Teltonika GPS
(16 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
=='''Firmware'''==
 
=='''Firmware'''==
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<strong>How do I send SMS command to Teltonika Telematics device? </strong>
+
|<strong>How to send SMS command to Teltonika Telematics device? </strong>
 
|-
 
|-
|There is a certain structure that the command has to follow:
+
|There exists a specific structure that commands must adhere to. For instance, to send the SMS command "getinfo," the following guidelines should be observed:
  
For example, if we would want to send SMS command getinfo:
+
    If SMS login and password are set: login pass <strong>getinfo</strong>
 
+
    If SMS login and password are not set, leave two spaces before the command: <strong>getinfo</strong>
If you have set SMS login and password: <strong>login pass getinfo</strong>
 
 
 
If SMS login and password are not set leave two spaces before command:   <strong>getinfo</strong>
 
 
|}
 
|}
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<strong>Can we delete records from the device memory? </strong>
+
|<strong>Can records be deleted from the device memory? </strong>
 
|-
 
|-
|You can clear device's memory by clicking the "format" button in the [Status] window. This will delete all stored records from the device's memory. You can also send the SMS command "sdformat" to the device and it will do the same thing but remotely without the need to connect the device to a computer.
+
|Records stored in the device's memory can be cleared by clicking the "format" button in the [Status] window. Alternatively, sending the SMS command "sdformat" remotely accomplishes the same result without requiring a physical connection to a computer.
 
|}
 
|}
  
Line 205: Line 202:
 
|<strong>How many batteries does TAT1XY use? </strong>
 
|<strong>How many batteries does TAT1XY use? </strong>
 
|-
 
|-
| TAT1XY uses 1 battery, which consists of 2 (7.2V variant) or 3 (10.8V variant) cells. Difference between them - according to our testing the 3 cell battery can send 45% more records when compared to 2 cell battery.
+
| TAT1XY uses 1 battery, which consists of 2 (7.2V variant) or 3 (10.8V variant) cells. Currently, manufactured TAT devices use 3-cell batteries.
 
|}
 
|}
  
Line 271: Line 268:
 
| This usually occurs when the device tries making OBD requests while the vehicle has no ignition and is locked. This can happen due to improper configuration, so make sure that the OBD device properly detects the ignition of the vehicle, when the ignition is actually ON.
 
| This usually occurs when the device tries making OBD requests while the vehicle has no ignition and is locked. This can happen due to improper configuration, so make sure that the OBD device properly detects the ignition of the vehicle, when the ignition is actually ON.
 
More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
 
More information about the Ignition sources can be found here: [https://wiki.teltonika-gps.com/view/FMC130_System_settings#Ignition_Source Ignition source]
|}
 
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
|<strong>Why does my device keep sending the same coordinates even if the vehicle is moving? </strong>
 
|-
 
|This is usually caused by the Static Navigation feature being misconfigured in the [[FMB130 System settings|System settings]].
 
The static navigation feature allows us to filter out false GNSS position changes when the vehicle is stationary and show only the true location of the vehicle.
 
 
[[File:Static navigation off.png|frameless|339x339px]][[File:Static navigation on.png|frameless|344x344px]]
 
 
 
 
The filtering can be disabled by configured movement and/or ignition source - if they are configured incorrectly, the device will not only incorrectly detect vehicle movement state or ignition, but also will not disable the filtering, causing the records to be sent with the same coordinates.
 
 
To make sure that the Ignition is detected correctly, You can use the configurator Status I/O window or check the AVL ID 239 on Your server.
 
 
For movement detection, it can also be checked on the configurator Status I/O window or by checking AVL ID 240 on Your server.
 
 
 
|}
 
|}

Revision as of 13:39, 23 January 2024

Firmware

Software

Hardware

Protocols

Configuration