Difference between revisions of "Starting with Teltonika Telematics"

From Wiki Knowledge Base | Teltonika GPS
Line 3: Line 3:
 
|<strong>Can we delete records from the device memory? </strong>
 
|<strong>Can we delete records from the device memory? </strong>
 
|-
 
|-
−
|You can clear devices memory by clicking "format" button in [Status] window. This will delete all stored records and start anew. You can also send SMS command "sdformat" to the device and it will do the same thing but remotely without the need to connect device 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 11: Line 11:
 
|No, but it is possible to retrieve the battery voltage and estimate the remaining battery life.
 
|No, but it is possible to retrieve the battery voltage and estimate the remaining battery life.
 
More information about it can be found here: [https://wiki.teltonika-gps.com/view/EYE_FAQ#How_does_the_battery_voltage_translate_into_the_percentage_of_the_battery.3F How does the battery voltage translate into the percentage of the battery?]
 
More information about it can be found here: [https://wiki.teltonika-gps.com/view/EYE_FAQ#How_does_the_battery_voltage_translate_into_the_percentage_of_the_battery.3F How does the battery voltage translate into the percentage of the battery?]
 +
 
Both EYE sensors and EYE Beacons can advertise their battery voltage
 
Both EYE sensors and EYE Beacons can advertise their battery voltage
 
|}
 
|}
Line 17: Line 18:
 
|<strong>What is Autoscan and with how many Teltonika device models is this possible? </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 has 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 30: Line 31:
 
|<strong>How to activate digital output with SMS command? What commands are available for FMB920? </strong>
 
|<strong>How to activate digital output with SMS command? What commands are available for FMB920? </strong>
 
|-
 
|-
−
| Supported commands can be found here: https://wiki.teltonika-gps.com/view/FMB920_SMS/GPRS_Commands
+
| Supported commands can be found here: [[FMB920_SMS/GPRS_Commands]]
−
To set digital output use the setdigout command. A description of this command can be found here: https://wiki.teltonika-gps.com/view/FMB_setdigout
+
To set digital output use the setdigout command. A description of this command can be found here: [https://wiki.teltonika-gps.com/view/FMB_setdigout FMB_setdigout]
 
|}
 
|}
  
Line 37: Line 38:
 
|<strong>What is the difference between Fuel consumed and Fuel consumed (Counted) or Total mileage and Total Mileage (Counted)? </strong>
 
|<strong>What is the difference between Fuel consumed and Fuel consumed (Counted) or Total mileage and Total Mileage (Counted)? </strong>
 
|-
 
|-
−
| Fuel consumed is the total fuel consumed by the vehicle since manufacturing while fuel consumed (counted) is the fuel consumed by the vehicle since the CAN device was installed.
+
| Fuel consumed is the total fuel consumed by the vehicle since it was manufactured, while fuel consumed (counted) is the fuel consumed by the vehicle since the CAN device was installed.
−
Total mileage is the total mileage of the vehicle as displayed in the dashboard since manufacture, while total mileage (counted) is the mileage of the vehicle from when the CAN device was installed.
+
Total mileage is the total mileage of the vehicle as displayed on the dashboard of the vehicle since it was manufactured, while total mileage (counted) is the mileage of the vehicle from when the CAN device was installed.
 
|}
 
|}
  
Line 45: Line 46:
 
|-
 
|-
 
| Yes, Iridium Edge does work with the FMC125 devices - the 03.28.06.Rev.323 firmware has to be used for this solution to work.
 
| Yes, Iridium Edge does work with the FMC125 devices - the 03.28.06.Rev.323 firmware has to be used for this solution to work.
−
More information about the Iridium Edge solution can be found here: https://wiki.teltonika-gps.com/view/Iridium_Edge
+
More information about the Iridium Edge solution can be found here: [[Iridium Edge]]
 
|}
 
|}
  
Line 52: Line 53:
 
|-
 
|-
 
| 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.
 
| 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
+
More information about TLS encryption can be found here: [https://wiki.teltonika-gps.com/view/FMB130_GPRS_settings#TLS.2FDTLS TLS settings]
 
|}
 
|}
  
Line 66: Line 67:
 
| There are 2 methods we can follow:
 
| There are 2 methods we can follow:
  
−
1. Digital Input: FMC920 device only has 1 Digital input which is mostly used to connect ignition cable, In this use case - Ignition source can be set to power voltage and seatbelt sensor can be connected to Digital input with priority - High and Operand "On change". If the voltage from seat belt sensor is negative, please use relay to convert to positive voltage. Please find screenshot below for reference.
+
1. Digital Input: The FMC920 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".
  
−
2. Analog Input: Seat belt sensor can be connected to Analog input 1 with priority - high and low level value (depending on the voltage from seatbelt, lets say 12 VDC) - 10 VDC and High level - 13 VDC. Idea is to make the voltage fall between low level and high level value and generate event when the voltage enters that range. If the voltage from seat belt sensor is negative, please use relay to convert to positive voltage. Please find screenshot below for reference.
+
2. Analog Input: The seat belt sensor can be connected to Analog input 1 with priority - high and low level values (depending on the voltage from the seatbelt, let's say 12 VDC) - 10 VDC and High level - 13 VDC. The idea is to make the voltage fall between low-level and high-level values and generate an event when the voltage enters that range.  
  
−
IO Priority guide: https://wiki.teltonika-gps.com/view/FMC920_I/O_settings#High_Priority
 
  
−
IO Operand: https://wiki.teltonika-gps.com/view/FMC920_I/O_settings#Operands
+
IO settings guide: [[FMC920 I/O settings]]
  
−
It is recommend to use FMX130 as the device has Ground sense option which will be easier to connect and also DIN1 can be used for Ignition which will be more accurate
+
It is recommended to use FMX130 as the device has a Ground sense option which will be easier to connect and DIN1 can be used for accurate Ignition detection.
 
|}
 
|}
  
Line 86: Line 86:
 
|<strong>Why does the TAT100 device appear offline on my server? </strong>
 
|<strong>Why does the TAT100 device appear offline on my server? </strong>
 
|-
 
|-
−
| The TAT works always in Deep-sleep mode, and the open link Timeout is 30sec maximum, so the device does not stay connected to the server. This is done to preserve the battery and allow the device to work longer.
+
| The TAT100 always works in Deep-sleep mode, and the open link Timeout is 30sec maximum, so the device does not stay connected to the server - this is done to preserve the battery life and allow the device to work longer.
 
|}
 
|}
  
Line 92: Line 92:
 
|<strong>Can I 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 receive 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 118: Line 118:
 
|<strong>When opening the configurator, a .NET error is shown. I tried installing .NET 7.0, but the error remained. How can this be solved?  </strong>
 
|<strong>When opening the configurator, a .NET error is shown. I tried installing .NET 7.0, but the error remained. How can this be solved?  </strong>
 
|-
 
|-
−
| New Configurators use the newer .NET version. Please make sure the correct version is installed. Please remove other (unused) .NET versions – more inforamtion can be found here:  Note #1: The Ways to determine the required version section is especially important here. It will help you decide which version you should choose. Note #2: x86 is recommended even with Microsoft Windows 64-bit Operating System.
+
| New Configurators use the newer .NET version - please make sure the correct version is installed and remove other (unused) .NET versions – more information can be found here:  [[.NET Runtime for Desktop installation]]
 +
Note #1: The Ways to determine the required version section is especially important here. It will help you decide which version you should choose.  
 +
 
 +
Note #2: x86 is recommended even with Microsoft Windows 64-bit Operating System.
 
|}
 
|}
  
Line 125: Line 128:
 
|-
 
|-
 
| FOTA Web is simply a device management platform that is used to assign files to the device remotely, such as firmware, configuration files, etc.
 
| FOTA Web is simply a device management platform that is used to assign files to the device remotely, such as firmware, configuration files, etc.
−
FOTA Web does not report the device's real-time location.
+
FOTA Web is '''not''' a tracking platform and does not report the device's real-time location.
 +
 
 +
 
 +
You can find more information about the FOTA Web tool here: [[FOTA WEB]]
 
|}
 
|}
  
Line 132: Line 138:
 
|-
 
|-
 
| Device transfer is a feature in FOTAWEB that allows clients to directly move devices amongst their accounts without the need to involve Teltonika.
 
| Device transfer is a feature in FOTAWEB that allows clients to directly move devices amongst their accounts without the need to involve Teltonika.
−
More information about this feature can be found here: https://wiki.teltonika-gps.com/view/FOTA_WEB_Devices#Device_transfer
+
More information about this feature can be found here: [https://wiki.teltonika-gps.com/view/FOTA_WEB_Devices#Device_transfer Device transfer]
 
|}
 
|}
  
Line 138: Line 144:
 
|<strong>How do I update configurations remotely via Teltonika FOTA Web? </strong>
 
|<strong>How do I update configurations remotely via Teltonika FOTA Web? </strong>
 
|-
 
|-
−
| Kindly use the FOTA Web to remotely update configurations to units as explained here: https://wiki.teltonika-gps.com/view/FOTA_WEB
+
| Kindly use the FOTA Web to remotely update configurations to units as explained here: [[FOTA WEB]]
  
 
Steps are:  
 
Steps are:  
Line 156: Line 162:
 
|<strong>What are the SIM card requirements for use with Teltonika Telematics devices? </strong>
 
|<strong>What are the SIM card requirements for use with Teltonika Telematics devices? </strong>
 
|-
 
|-
−
| It is recommended to use any SIM card of choice, provided it can establish a GPRS connection to a remote server(bare minimum, should be able to connect to the internet
+
| Different Teltonika Telematics devices support Mini SIM, Micro SIM, and Nano SIM sized SIM cards. To know the exact SIM card supported by Your device, please check the General Description Wiki page for Your device.
 +
 
 +
 
 +
As for eSIMs, there are a couple of requirements for it to work with our devices - they can be found here: [[Requirements for eSIM]]
 
|}
 
|}
  
Line 162: Line 171:
 
|<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>
 
|-
 
|-
−
| Connect the analog input of the FMx to the vehicle fuel gauge data wire.
+
| 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]]
−
Connect the device to the PC and open the configurator under IO Locate the Analog input connected ie Analog input 1 or Analog input 2.
 
−
 
 
−
Turn on the ignition till the fuel gauge can show the fuel level on the dash.
 
−
 
 
−
Empty the tank.
 
−
 
 
−
Create a table of voltage against liters.
 
−
 
 
−
Add liters in batches of for instance 2 liters if the capacity is small like 40 liters or 5 litres if the capacity is above 80, while checking the voltage in the configurator.
 
−
 
 
−
After adding, give it a little time for the fuel gauge to read the voltage before adding a new batch.
 
−
 
 
−
Do this until the fuel tank is full.
 
−
 
 
−
Implement the table on the tracking platform using the AVL ID of the analog input connected.
 
 
|}
 
|}
  
Line 184: Line 178:
 
|<strong>Where can we find the connection schemes for CAN-CONTROL adapter? </strong>
 
|<strong>Where can we find the connection schemes for CAN-CONTROL adapter? </strong>
 
|-
 
|-
−
| Please use the below drive to download the needed connection scheme.
+
| Please use the link below to find and download the necessary connection scheme.
  
 
Link: https://drive.teltonika.lt/d/31c32f08610044b699b3/
 
Link: https://drive.teltonika.lt/d/31c32f08610044b699b3/
Line 192: Line 186:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>Does all RFIDs with 125 or 128kHz frequency will support 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, FMC 150 also supports a 1-wire protocol (DS1990A) RFID reader.
 
|Like other devices with a 1-Wire interface, FMC 150 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), we can integrate it into FMC150.
 
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.
−
|}
 
−
 
−
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
−
|<strong>Can ADAS be used on a motorcycle? </strong>
 
−
|-
 
−
| Teltonika ADAS is not intended to be used on motorcycles.
 
 
|}
 
|}
  
Line 207: Line 195:
 
|<strong>How many batteries does TAT use? </strong>
 
|<strong>How many batteries does TAT use? </strong>
 
|-
 
|-
−
| We are using a set of 2 batteries, and the nominal voltage is 7.2V. Additionally, there is a different TAT hardware version that works with 3 cell batteries, and the nominal voltage is 10.8V
+
| TAT 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 223: Line 211:
 
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:
 
| Teltonika data sending protocol Codec 8 and Codec 8Extended description with examples:
  
−
https://wiki.teltonika-gps.com/view/Codec#Codec_8
+
[[Codec|AVL data sending codecs]]
  
 
TCP/UDP listener and AVL parser with source code that could be used as a template for implementation of Teltonika protocols. The whole pack can be downloaded from here:
 
TCP/UDP listener and AVL parser with source code that could be used as a template for implementation of Teltonika protocols. The whole pack can be downloaded from here:
  
−
https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation
+
[https://wiki.teltonika-gps.com/view/Universal_Device_Test_Guide#Protocols_implementation Listener and AVL parser]
 
|}
 
|}
  
Line 237: Line 225:
 
When advanced beacon mode is selected, beacon data capturing can be configured manually and to distinguish simple and advanced functionalities a different ID is used - AVL ID 548.
 
When advanced beacon mode is selected, beacon data capturing can be configured manually and to distinguish simple and advanced functionalities a different ID is used - AVL ID 548.
  
−
For advanced beacon configuration documentation, you can find it here: https://wiki.teltonika-gps.com/view/Advanced_Beacon_Capturing_Configuration
+
For advanced beacon configuration documentation, you can find it here: [[Advanced Beacon Capturing Configuration]]
 
|}
 
|}
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>I have implemented Codec8 Extended protocol. Communication is working correctly, IMEI and AVL packets are working fine.
+
|<strong>I have implemented Codec8 Extended protocol. Communication is working correctly, IMEI and AVL packets are working fine,
−
But the unit sends 0xFF instead of AVL packets sometimes. It's not in the documentation.
+
But the unit sends 0xFF instead of AVL packets sometimes. It's not in the documentation.Is there any sense of this information and is it necessary to send some data as a response back? </strong>
−
 
 
−
Is there any sense of this information and is it necessary to send some data as a response back? </strong>
 
 
|-
 
|-
 
| It seems that You have enabled the Network Ping Timeout feature.
 
| It seems that You have enabled the Network Ping Timeout feature.

Revision as of 16:35, 15 January 2024

Firmware

Software

Hardware

Protocols

Configuration

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