Difference between revisions of "Starting with Teltonika Telematics"

From Wiki Knowledge Base | Teltonika GPS
 
(7 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 to send SMS command to Teltonika Telematics device? </strong>
+
|<strong>How do I send SMS command to Teltonika Telematics device? </strong>
 
|-
 
|-
−
|There exists a specific structure that commands must adhere to. For instance, to send the SMS command "getinfo," the following guidelines should be observed:
+
|There is a certain structure that the command has to follow:
−
    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>
+
For example, if we would want to send SMS command getinfo:
 +
 
 +
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>Is it possible to delete records from the device memory? </strong>
+
|<strong>Can we delete records from the device memory? </strong>
 
|-
 
|-
−
|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.
+
|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.
 
|}
 
|}
  
Line 24: Line 28:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>What is autoscan and which Teltonika device models support this feature?</strong>
+
|<strong>What is Autoscan and with how many Teltonika device models is this possible? </strong>
 
|-
 
|-
 
|Autoscan is the process of scanning for CANBUS program numbers in the vehicle CANBUS system. Currently, FMB140 and newest external CAN adapters have the Autoscan feature.
 
|Autoscan is the process of scanning for CANBUS program numbers in the vehicle CANBUS system. Currently, FMB140 and newest external CAN adapters have the Autoscan feature.
Line 59: Line 63:
 
|<strong>Is there a way to encrypt the data that is sent to the server? </strong>
 
|<strong>Is there a way to encrypt the data that is sent to the server? </strong>
 
|-
 
|-
−
| Yes, our devices have TLS encryption capability, which allows to secure the data using TLS certificates that are uploaded to the device and the server.
+
| Yes, our devices have TLS encryption capability, which allows us to secure the data using TLS certificates that are uploaded to the device and the server.
 
More information about TLS encryption can be found here: [https://wiki.teltonika-gps.com/view/FMB130_GPRS_settings#TLS.2FDTLS TLS settings]  
 
More information about TLS encryption can be found here: [https://wiki.teltonika-gps.com/view/FMB130_GPRS_settings#TLS.2FDTLS TLS settings]  
 
|}
 
|}
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>Is it possible to know how much data has been used with the current data plan? </strong>
+
|<strong>Can we check how much data has been used with the current data plan? </strong>
 
|-
 
|-
−
| In the configurator Status tab there is the GPRS traffic section, where data usage can be seen.
+
| In the configurator Status tab, we have the GPRS traffic section, where data usage can be seen.
 
Other than this, there is no way to get the data consumption from the device - this information will be available from the network provider.
 
Other than this, there is no way to get the data consumption from the device - this information will be available from the network provider.
 
|}
 
|}
Line 73: Line 77:
 
|<strong>Is there a way to implement seat belt detection with a device with only one digital input? </strong>
 
|<strong>Is there a way to implement seat belt detection with a device with only one digital input? </strong>
 
|-
 
|-
−
| There are 2 methods that can be followed:
+
| There are 2 methods we can follow:
  
 
1. Digital Input: if the device only has 1 Digital input which is mostly used to connect the ignition cable, In this use case - the ignition source can be set to power voltage and the seatbelt sensor can be connected to Digital input with priority - High and Operand "On change".
 
1. Digital Input: if the device only has 1 Digital input which is mostly used to connect the ignition cable, In this use case - the ignition source can be set to power voltage and the seatbelt sensor can be connected to Digital input with priority - High and Operand "On change".
Line 87: Line 91:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>How to get a SIM card IMSI number on my server? </strong>
+
|<strong>How do I get a SIM card IMSI number on my server? </strong>
 
|-
 
|-
 
| The IMSI is not available as an IO element, and it will not be sent to the server with records. However, it can be requested by a SMS/GPRS command "getimsi"
 
| The IMSI is not available as an IO element, and it will not be sent to the server with records. However, it can be requested by a SMS/GPRS command "getimsi"
Line 99: Line 103:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>Is it possible to send an SMS or command to the TAT100? </strong>
+
|<strong>Can I send an SMS or command to the TAT100? </strong>
 
|-
 
|-
 
| Yes, you can send a command to the TAT100 and it will execute this command once it wakes up.
 
| Yes, you can send a command to the TAT100 and it will execute this command once it wakes up.
Line 180: Line 184:
 
|<strong>How to connect the fuel gauge sensor to the Analog input of the FMx and calibrate for accurate results? </strong>
 
|<strong>How to connect the fuel gauge sensor to the Analog input of the FMx and calibrate for accurate results? </strong>
 
|-
 
|-
−
| Device can measure the fuel level using analog input by matching the voltage coming from the fuel level sensor already mounted in the car, with the fuel level in the tank.
+
| We can measure the fuel level using analog input by matching the voltage coming from the fuel level sensor already mounted in the car, with the fuel level in the tank.
 
More information on how the AIN has to be connected and calibrated can be found here: [[Analog Fuel Sensor]]
 
More information on how the AIN has to be connected and calibrated can be found here: [[Analog Fuel Sensor]]
 
|}
 
|}
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>Where the connection schemes for CAN-CONTROL adapter can be found? </strong>
+
|<strong>Where can we find the connection schemes for CAN-CONTROL adapter? </strong>
 
|-
 
|-
 
| Please create a Helpdesk ticket for our support team and specify the vehicle that the connection scheme is needed for.
 
| Please create a Helpdesk ticket for our support team and specify the vehicle that the connection scheme is needed for.
Line 192: Line 196:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>Do all RFID cards with 125 or 128kHz frequency work with FMC150 ? What about a 13.56 MHz NFC or RFID device? </strong>
+
|<strong>Does all RFID cards with 125 or 128kHz frequency work with FMC150 ? What about a 13.56 MHz NFC or RFID device? </strong>
 
|-
 
|-
 
|Like other devices with a 1-Wire interface, FMC150 also supports a 1-wire protocol (DS1990A) RFID reader.
 
|Like other devices with a 1-Wire interface, FMC150 also supports a 1-wire protocol (DS1990A) RFID reader.
−
If the reader reads cards with 125 or 128 kHz and transmits this data through 1 wire protocol (DS1990A), an integration can be done for FMX150 devices.
+
If the reader reads cards with 125 or 128 kHz and transmits this data through 1 wire protocol (DS1990A), we can integrate it into FMC150.
 
|}
 
|}
  
Line 201: Line 205:
 
|<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. Currently, manufactured TAT devices use 3-cell batteries.
+
| 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.
 
|}
 
|}
  
Line 213: Line 217:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>Where information on how to parse messages from Teltonika Telematics devices can be found?</strong>
+
|<strong>Where can I find how to parse the message from the device in the backend? </strong>
 
|-
 
|-
 
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:
 
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:
Line 255: Line 259:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>Why device does not detect the ignition? </strong>
+
|<strong>Why device doesn't detect the ignition? </strong>
 
|-
 
|-
 
|Please check which ignition source have you chosen and configure the device according to Your use case.  
 
|Please check which ignition source have you chosen and configure the device according to Your use case.  
Line 263: Line 267:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>When testing an OBD device, alarm of the vehicle is triggered when it is parked. What could cause this? </strong>
+
|<strong>When testing the OBD device alarm of the vehicle is triggered when it is parked. What could cause this? </strong>
 
|-
 
|-
 
| 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.
Line 270: Line 274:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>How to calculate how much data device is going to consume according to configuration?</strong>
+
|<strong>Why does my device keep sending the same coordinates even if the vehicle is moving? </strong>
 
|-
 
|-
−
|The total number of data consumption bytes depends on parameters, features and also the frequency of data sending configured in Data Acquisition.  
+
|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.
  
−
By counting the bytes of each enabled parameter, the size of one packet can be calculated. Once the frequency or amount of packets sent is known only multiplication needs to be done:
+
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.
−
Packet Size X Amount of packets
 
  
−
Important note: Network operators round the packets into larger chunks, e.g.: if device sends 800 Bytes of data, operators can round it to 1 kB (1024 Bytes).  
+
For movement detection, it can also be checked on the configurator Status I/O window or by checking AVL ID 240 on Your server.
  
−
You can find the size of each IO in the below link:</br>
 
−
[https://wiki.teltonika-gps.com/view/FMC130_Teltonika_Data_Sending_Parameters_ID#Permanent_I.2FO_elements Teltonika Data Sending parameters]
 
 
|}
 
|}

Latest revision as of 15:45, 26 March 2024

Firmware

Software

Hardware

Protocols

Configuration

Retrieved from "https://wiki.teltonika-gps.com/index.php?title=Starting_with_Teltonika_Telematics&oldid=97077"