Teltonika Codec14 communication protocol

Supported device types and versions
Communication line configuration
Communication station configuration
I/O tag configuration
Literature
Changes and modifications
Document revisions

Supported device types and versions

The communication protocol Teltonika Codec14 supports a data acquisition from the devices "Fleet Management Systems Unit" Teltonika of type FM4200 with firmware Movys.
The protocol represents TCP server to which the units are being connected online. The data come into system via configuration of so-called "master" station and I/O tags. I.e. whatever number of connected units send data to system via one sample configuration of the unit. A unique IMEI code of the unit identifies data from single units.

Communication line configuration

• Communication line category: TCP/IP TCP.
• Server host: all (TCP server), server port: well-known port according to the setting of the device.

Communication station configuration

Communication protocol: Teltonika Codec14.
Recommended setting of the station time intervals: delay 1 sec.

Station protocol parameters

Following station protocol parameters can be configured:

Table 1

Full name	Meaning	Unit	Default value
Clients per Thread	Number of the connected units handled by one thread. It is used for balancing the power and the response of communication process in dependence on the number of connected units.	1 up-to 200	50
Send Async Message Request After Connect	KOM process will send 'Asynchronous Message Request' after a unit is connected. The unit will answer by 'Asynchronous Message Response' which contains the data (AVL record).	YES/NO	YES
Debug Packet Analyse	Activation of debug information about the received and sent datagrams.	YES/NO	YES
Debug Values	Activation of debug information about received values.	YES/NO	NO
Debug Packet Queue Flow	Activation of debug information about the state of received data processing by D2000 System.	YES/NO	NO
Debug Packet Binary Contents	Permission of debug lists containing the received/sent datagrams in binary form.	YES/NO	YES
Unit Debug File	Permission of special form of tracing the units when the debug information is saved into special file. The name of this file is derived from IP address of unit (IP1_IP2_IP3_IP4.log) in subdirectory "trace" of application directory. It makes easier the identification of debug lists from the unit. Meaning of parameters: Not_Allowed - the file will not be created Both Line & Station - the file will be created in parallel with standard .log file which traces the communication line Station Only - only special log files are allowed Warning! This setting overrides the level setting of communication tracing in the line configuration (see also the information in document Communication lines - configuration dialog box, section Communication tracing).	Not Allowed Both Line & Station Station Only	Not Allowed
Unit Debug File Size	Maximal size of the special debug file of unit tracing. After the file reaches this size it will be renamed and saved alike the file of communication line tracing.	1 up-to 50 MBytes	10

I/O tag configuration

Possible value types of I/O tags: Ai, Ao, Ci, Co, Di, Dout, TiA, ToA, TxtI, TxtO.

List of I/O tag addresses

Table 2

Parameter writing

The following rules hold:

1. The values of parameters can be only written, not read.
2. The check, if the writing was all right, is made through the so-called Configuration Timestamp (I/O tag with address UNIT_STAT.ST_CONFIG_TIMESTAMP). The value "Config Timestamp" must be set during the parameters writing - it is the parameter with ID = 0 (Profile Timestamp). The value should be the unique absolute time (the best is the time of the configuration begin).
   After the parameters was written the value UNIT_STAT.ST_CONFIG_TIMESTAMP must be set on the value of parameter with ID=0 sent by user.
3. Process of writing:
   • Set IMEI to I/O tag UNIT_PARAMS_OUT.IMEI, if it ends with error (on an action WAIT) the KOM process does not recognize the unit with this IMEI or it is not online.
   • Set the value type of parameter to UNIT_PARAMS_OUT.VALUE_TYPE (see the Table 3).
   • Set UNIT_PARAMS_OUT.VALUE with the value of parameter (as text).
   • Set UNIT_PARAMS_OUT.ADDR with the parameter ID. The parameter ID=0 "Profile Timestamp" should be the first.
   • Set UNIT_PARAMS_OUT.VALUE_TYPE of next parameter.
   • Set UNIT_PARAMS_OUT.VALUE with the value of next parameter.
   • Set UNIT_PARAMS_OUT.ADDR with the parameter ID of next parameter.
     
     .... repeat so many times how much parameters you are writing. You need not to write all the parameter but only those changed.....
   • Set UNIT_PARAMS_OUT.VALUE_TYPE on value 1 to finish the configuration.
   • Set UNIT_PARAMS_OUT.VALUE - empty text to finish the configuration.
   • Set UNIT_PARAMS_OUT.ADDR on value 0. It is a signal to send parameters into unit physically.

Table 3

Literature

• Teltonika Codec.14 Communication Protocol Description, Rev.11.

Changes and modifications

• Sept. 2009 - Document creation

Document revisions

• Ver. 1.0 – September 30th, 2009