Difference between revisions of "Starting with Teltonika Telematics"

From Wiki Knowledge Base | Teltonika GPS
 
(22 intermediate revisions by 4 users not shown)
Line 1: Line 1:
 
=='''Firmware'''==
 
=='''Firmware'''==
 +
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 +
|<strong>How do I send SMS command to Teltonika Telematics device? </strong>
 +
|-
 +
|There is a certain structure that the command has to follow:
 +
 +
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>Can we delete records from the device memory? </strong>
 
|<strong>Can we delete records from the device memory? </strong>
Line 29: Line 41:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<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? </strong>
 
|-
 
|-
−
| 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 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 59: Line 70:
 
|<strong>Can we check 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 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.
+
| 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.
 
|}
 
|}
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>Is there a way to implement seat belt detection with FMC920 device? </strong>
+
|<strong>Is there a way to implement seat belt detection with a device with only one digital input? </strong>
 
|-
 
|-
 
| There are 2 methods we can follow:
 
| There are 2 methods we can follow:
  
−
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".
+
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".
 +
 
 +
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.  
  
−
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.
 
  
  
Line 135: Line 148:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>How to use the device transfer feature in FOTAWEB? </strong>
+
|<strong>How to use the device transfer feature in FOTA Web? </strong>
 
|-
 
|-
−
| 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 FOTA Web 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 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 144: Line 157:
 
|<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: [[FOTA WEB]]
+
| Kindly use the FOTA Web to remotely update configurations to units as explained here: [[FOTA WEB|FOTA Web]]
  
 
Steps are:  
 
Steps are:  
  
−
1. Upload the configuration file in FOTA WEB under the files tab.  
+
1. Upload the configuration file in FOTA Web under the files tab.  
  
 
2. Head over to the devices tab then select the devices to receive the configuration.  
 
2. Head over to the devices tab then select the devices to receive the configuration.  
Line 154: Line 167:
 
3. Click on Create Task and choose Update Configuration on the drop-down then below it, choose the uploaded file, then click on Create Task.  
 
3. Click on Create Task and choose Update Configuration on the drop-down then below it, choose the uploaded file, then click on Create Task.  
  
−
The task will be executed the next time the device connects to FOTA WEB or you can force it to connect immediately by sending a command "  web_connect" with two spaces before the command and no quotes, or hard restart the unit by unplugging the power and the internal battery then plugging it back on then the task will be executed immediately.
+
The task will be executed the next time the device connects to FOTA Web or you can force it to connect immediately by sending a command '''''web_connect''''', or by forcing a hard restart of the unit by unplugging the power and the internal battery then plugging it back on - then the task will be executed immediately.
 
|}
 
|}
  
Line 178: Line 191:
 
|<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 link below to find and download the necessary connection scheme.
+
| Please create a Helpdesk ticket for our support team and specify the vehicle that the connection scheme is needed for.
−
 
+
The whole supported vehicle list for CAN-CONTROL adapter can be found here: [[CAN adapter supported vehicles]]
−
Link: https://drive.teltonika.lt/d/31c32f08610044b699b3/
 
−
 
 
−
Password: wzh1XNp0
 
 
|}
 
|}
  
Line 188: Line 198:
 
|<strong>Does 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, FMC 150 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), 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"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>How many batteries does TAT use? </strong>
+
|<strong>How many batteries does TAT1XY use? </strong>
 
|-
 
|-
−
| 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.
+
| 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 241: Line 251:
  
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
 
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
−
|<strong>I have successfully paired the Teltonika Eye sensor to the FMB130 and I can see the data on the I/O tab but the data is not sent to my platform, what could be the issue? </strong>
+
|<strong>I have successfully paired the Teltonika Eye sensor to the fleet management device and I can see the data on the I/O tab but the data is not sent to my platform, what could be the issue? </strong>
 
|-
 
|-
 
| For the data to be sent to the platform, the I/O needs to have a priority of ‘Low’, ‘High’, or ‘Panic’ so that the data can be sent with periodical data to the platform.
 
| For the data to be sent to the platform, the I/O needs to have a priority of ‘Low’, ‘High’, or ‘Panic’ so that the data can be sent with periodical data to the platform.
Line 261: Line 271:
 
| 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.
 +
 
|}
 
|}

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"