193
edits
Changes
no edit summary
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" 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.
|}
|}
== '''Hardware''' ==
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<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
|}
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<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.
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.
|}
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<strong>Where can we find the connection schemes for CAN-CONTROL adapter? </strong>
|-
| Please use the below drive to download the needed connection scheme.
Link: https://drive.teltonika.lt/d/31c32f08610044b699b3/
Password: wzh1XNp0
|}
{| 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>
|-
|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.
|}
{| 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.
|}
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<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
|}
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<strong>What is the battery life of TAT1XY? </strong>
|-
| TAT1XX can send approximately 1000 records, this may differ depending on the environment, coverage, Temperature, and device mounting,
|}
== '''Protocols''' ==
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<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:
https://wiki.teltonika-gps.com/view/Codec#Codec_8
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
|}
{| class="wikitable mw-collapsible mw-collapsed" role="presentation"
|<strong>In documentation it states that the Beacon data will be sent via AVL ID 385, but data from FMB140 is being sent with AVL ID:548. </strong>
|-
| When the simple mode is selected beacon parsing is done automatically so AVL ID:385 is used
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
|}
{| 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.
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>
|-
| It seems that You have enabled the Network Ping Timeout feature.
What Network Ping Timeout does is it sends an empty packet (0xFF) to the server to make sure that the operator does not close a link between the device and the server.
If you don't want to receive 0xFF packets anymore you can set Network Ping Timeout to 0 seconds.
|}
== '''Configuration''' ==
