Tracker configuration

Teltonika Tracker configuration

Teltonika codec support

	TCP	UDP
Codec 8	❌	❌
Codec 8 Extended	✔️	✔️
Codec 16	❌	❌
Codec 12	✔️	❌
Codec 13	❌	❌
Codec 14	❌	❌

Note

Even if both TCP and UDP are available, it is reccomended to configure the device via TCP as it ensures, that packets are delivered from the device to server. Users may expect some dataloss if using UDP configuration as it lacks additional data packet delivery validation.

Teltonika device configuration

In order to successfully connect Teltonika devices to Fliteca systems, users can follow this simple guide. First and most important task is to register device in Fliteca, but that step requires knowing devices IMEI. Users can look up their device IMEi on the device itself, on the box or view it in the configurator as shown below.

Note

You can find and download The latest configurator version based on your Teltonika device in the Teltonika Wiki page.

Next up, users must point the tracker to send all data to Teltonika receivers. For concrete receiver address and port information, users should look in the Data acquisition section of this doccumentation. Once users know correct ip/domain and port combination, they can enter it in the main server config as shown below.

Teltonika trackers support a multitude of different IO elements that can be received by fliteca. Once connected to the vehicle, Teltonika configurator shows which OBD elements are supported. Users should mark “Low” priority near the fields that they wish to send to fliteca. Example configuration is shown in the image below.

Lastly, users might want to modify data rate, that the device generates and sends data. Fliteca team has found, that default settings work pretty well, unless the users want to see better precision on vehicle tracks.

Warning

Extremely high rate of packet generation will lead to higher usage of mobile data.

Warning

This guide is just reccomendation, though advanced users may configure devices to better suit their needs.