Changes

Teltonika Data Sending Protocols (view source)

Revision as of 12:20, 29 November 2022

827 bytes added , 12:20, 29 November 2022

m

no edit summary

Line 1: Line 1:

='''<big>Introduction</big>'''=

A codec is a device or computer program for encoding or decoding a digital data stream or signal. Codec is a portmanteau of coder-decoder. A codec encodes a data stream or a signal for transmission and storage, possibly in encrypted form, and the decoder function reverses the encoding for playback or editing.

−

Below you will see a table of all Codec types with ~~ID’s~~:

+

Below you will see a table of all Codec types with IDs:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 22: Line 22:

='''<big>Codec for device data sending</big>'''=

−

In this chapter, you will find information about every Codec protocol which are ~~using~~ for device data sending and differences between them.

+

In this chapter, you will find information about every Codec protocol which are used for device data sending and the differences between them.

=='''<big>Codec 8</big>'''==

Line 36: Line 36:

*'''AVL Data Packet'''

−

~~Below~~ table represents AVL Data Packet structure:

+

The below table represents the AVL Data Packet structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 61: Line 61:

'''Data Field Length''' – size is calculated starting from Codec ID to Number of Data 2.

'''Codec ID''' – in Codec8 it is always <code>0x08</code>.

−

'''Number of Data 1''' – a number ~~which~~ defines how many records are in the packet.

+

'''Number of Data 1''' – a number that defines how many records are in the packet.

'''AVL Data''' – actual data in the packet (more information below).

−

'''Number of Data 2''' – a number ~~which~~ defines how many records are in the packet. This number must be the same as “Number of Data 1”.

+

'''Number of Data 2''' – a number that defines how many records are in the packet. This number must be the same as “Number of Data 1”.

−

'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code ~~using for~~ detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

+

'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

−

'''Note:''' for [[FMB640]], [[FMB641]], [[FMC640]], and [[FMM640]], minimum AVL record size is 45 bytes (all IO elements disabled). ~~Maximum~~ AVL record size is 255 bytes. Maximum AVL packet size is 512 bytes. For other devices, the minimum AVL record size is 45 bytes (all IO elements disabled). Maximum AVL packet size is 1280 bytes.

+

'''Note:''' for [[FMB640]], [[FMB641]], [[FMC640]], and [[FMM640]], minimum AVL record size is 45 bytes (all IO elements disabled). The maximum AVL record size is 255 bytes. Maximum AVL packet size is 512 bytes. For other devices, the minimum AVL record size is 45 bytes (all IO elements disabled). Maximum AVL packet size is 1280 bytes.

*AVL Data

Line 85: Line 85: −

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January, 1970 UTC (UNIX time).

+

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January 1970 UTC (UNIX time).

−

'''Priority''' – field ~~which define~~ AVL data priority (more information below).

+

'''Priority''' – a field that defines AVL data priority (more information below).

'''GPS Element''' – location information of the AVL data (more information below).

−

'''IO Element''' – additional configurable information from device (more information below).

+

'''IO Element''' – additional configurable information from the device (more information below).

*Priority

Line 109: Line 109:

*GPS element

−

~~Below~~ table represents GPS Element structure:

+

The below table represents the GPS Element structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 129: Line 129: −

'''Longitude''' – east – west position.

+

'''Longitude''' – east-west position.

−

'''Latitude''' – north – south position.

+

'''Latitude''' – north-south position.

'''Altitude''' – meters above sea level.

'''Angle''' – degrees from north pole.

Line 136: Line 136:

'''Speed''' – speed calculated from satellites.

'''Note:''' Speed will be <code>0x0000</code> if GPS data is invalid.

−

Longitude and latitude are integer values built from degrees, minutes, seconds and milliseconds by formula:

+

Longitude and latitude are integer values built from degrees, minutes, seconds, and milliseconds by the formula:

[[Image:GPS.png]]

Where:

d – Degrees; m – Minutes; s – Seconds; ms – Milliseconds; p – Precision (10000000)

−

If longitude is in west or latitude in south, multiply result by –1.

+

If the longitude is in the west or latitude in the south, multiply the result by –1.

Note:

−

To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is 0, coordinate is positive~~, if~~ it is 1, coordinate is negative.

+

To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is 0, the coordinate is positive. If it is 1, the coordinate is negative.

Example:

Received value: <code>20 9C CA 80</code> converted to BIN: <code>00100000 10011100 11001010 10000000</code> first bit is 0, which means coordinate is positive converted to DEC: <code>547146368</code>. For more information see two‘s complement arithmetic.

Line 154: Line 154:

| style="vertical-align: middle; text-align: center;" |1 byte

| rowspan="26" style=" width:5%; vertical-align: middle; text-align: left;" |

−

| rowspan="26" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on event – this field defines which IO property has changed and generated an event. For example, when if Ignition state ~~changed~~ and it ~~generate~~ event, Event IO ID will be <code>0xEF</code> (AVL ID: 239). If it’s not eventual record – the value is 0.

+

| rowspan="26" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on the event – this field defines which IO property has changed and generated an event. For example, when if the Ignition state changes and it generates an event, the Event IO ID will be <code>0xEF</code> (AVL ID: 239). If it’s not an eventual record – the value is 0.

'''N''' – a total number of properties coming with record (N = N1 + N2 + N4 + N8).

'''N1''' – number of properties, which length is 1 byte.

Line 240: Line 240:

First, when the module connects to the server, the module sends its IMEI. First comes a short identifying the number of bytes written and then goes IMEI as text (bytes).

For example, IMEI <code>356307042441013</code> would be sent as <code>000F333536333037303432343431303133</code>.

−

~~First~~ two bytes denote IMEI length. In this case <code>0x000F</code> means, that IMEI is 15 bytes long.

+

The first two bytes denote IMEI length. In this case <code>0x000F</code> means, that IMEI is 15 bytes long.

−

After receiving IMEI, server should determine if it would accept data from this module. If yes, server will reply to module <code>01</code>, if not - <code>00</code>. Note that confirmation should be sent as binary packet. I.e. 1 byte <code>0x01</code> or <code>0x00</code>.

+

After receiving IMEI, the server should determine if it would accept data from this module. If yes, server will reply to module <code>01</code>, if not - <code>00</code>. Note that confirmation should be sent as a binary packet. I.e. 1 byte <code>0x01</code> or <code>0x00</code>.

−

Then the module starts to send the first AVL data packet. After the server receives a packet and parses it, the server must report to the module number of data received as integer (four bytes).

+

Then the module starts to send the first AVL data packet. After the server receives a packet and parses it, the server must report to the module number of data received as an integer (four bytes).

−

If sent data number and reported by the server ~~doesn’t~~ match module resends sent data.

+

If the sent data number and the reported by the server don’t match module resends the sent data.

*Example:

−

~~Module~~ connects to server and sends IMEI:

+

The module connects to the server and sends IMEI:

−

~~Server~~ accepts the module:

+

The server accepts the module:

01

−

~~Module~~ sends data packet:

+

The module sends data packet:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 262: Line 262:

| style="vertical-align: middle; text-align: center;" |Codec ID – 0x08,

Number of Data – '''0x02'''

−

(Encoded using continuous bit stream. ~~Last~~ byte padded to align to byte boundary)

+

(Encoded using continuous bit stream. The last byte is padded to align to the byte boundary)

| style="vertical-align: middle; text-align: center;" |CRC of “AVL Data Array”

|-

Line 276: Line 276:

*'''Examples'''

−

~~Hexadecimal~~ stream of AVL Data Packet receiving and response in these examples are given in hexadecimal form. The different fields of packets are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of AVL Data Packet receiving and response in these examples are given in the hexadecimal form. The different fields of packets are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

'''1'st example'''

−

Receiving one data record with each element property (1 byte, 2 bytes, 4 ~~byte~~ and 8 ~~byte~~).

+

Receiving one data record with each element property (1 byte, 2 bytes, 4 bytes, and 8 bytes).

−

Received data in hexadecimal stream:

+

Received data in the hexadecimal stream:

Parsed:

Line 305: Line 305:

| rowspan="24" style="vertical-align: middle; text-align: center;" |AVL Data

| style="vertical-align: middle; text-align: center;" |Timestamp

−

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D8 EA 30 (GMT: Monday, June 10, 2019 10:04:46 AM)

+

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D8 EA 30 (GMT: Monday, June 10, 2019, 10:04:46 AM)

|-

| style="vertical-align: middle; text-align: center;" |Priority

Line 389: Line 389:

'''2'nd example'''

−

Receiving one data record with one or two different element properties (1 byte, 2 ~~byte~~).

+

Receiving one data record with one or two different element properties (1 byte, 2 bytes).

−

Received data in hexadecimal stream:

+

Received data in the hexadecimal stream:

Parsed:

Line 415: Line 415:

| rowspan="20" style="vertical-align: middle; text-align: center;" |AVL Data

| style="vertical-align: middle; text-align: center;" |Timestamp

−

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D9 AD 80 (GMT: Monday, June 10, 2019 10:05:36 AM)

+

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D9 AD 80 (GMT: Monday, June 10, 2019, 10:05:36 AM)

|-

| style="vertical-align: middle; text-align: center;" |Priority

Line 488: Line 488:

'''3'rd example'''

Receiving two or more data records with one or more different element properties.

−

Received data in hexadecimal stream:

+

Received data in the hexadecimal stream:

<code>000000000000004308020000016B40D57B480100000000000000000000000000000001010101000000000000016B40D5C198010000000000000000000000000000000

101010101000000020000252C</code>

Line 515: Line 515:

(1'st record)

| style="vertical-align: middle; text-align: center;" |Timestamp

−

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D5 7B 48 (GMT: Monday, June 10, 2019 10:01:01 AM)

+

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 40 D5 7B 48 (GMT: Monday, June 10, 2019, 10:01:01 AM)

|-

| style="vertical-align: middle; text-align: center;" |Priority

Line 657: Line 657:

*Acknowledgment packet

−

~~Acknowledgment~~ packet should have the same Packet ID as an acknowledged data packet and empty Data Payload. Acknowledgment should be sent in binary format.

+

The acknowledgment packet should have the same Packet ID as an acknowledged data packet and empty Data Payload. Acknowledgment should be sent in binary format.

{| class="nd-othertables_2" style="width:100%;"

|+

Line 698: Line 698:

'''IMEI Length''' – always will be <code>0x000F</code>.

'''Module IMEI''' – IMEI of a sending module encoded the same as with TCP.

−

'''AVL Data Array''' – array of encoded AVL data (same as TCP AVL Data Array).

+

'''AVL Data Array''' – an array of encoded AVL data (same as TCP AVL Data Array).

*Server response Packet Payload using UDP channel

Line 717: Line 717:

*'''Communication with server'''

−

The module sends the UDP channel packet with an encapsulated AVL data packet. The server sends the UDP channel packet with an encapsulated response module that validates AVL Packet ID and the Number of accepted AVL elements. If server response with valid AVL Packet ID ~~is not received~~ within configured timeout, the module can retry sending.

+

The module sends the UDP channel packet with an encapsulated AVL data packet. The server sends the UDP channel packet with an encapsulated response module that validates the AVL Packet ID and the Number of accepted AVL elements. If the server response is not received with a valid AVL Packet ID within configured timeout, the module can retry sending.

*Example:

−

~~Module~~ sends the data:

+

The module sends the data:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 734: Line 734:

IMEI Length – 0x000F

IMEI – 0x313233343536373839303132333435

−

(Encoded using continuous bit stream. ~~Last~~ byte padded to align to byte boundary)

+

(Encoded using continuous bit stream. The last byte is padded to align to the byte boundary)

| style="vertical-align: middle; text-align: center;" |Codec ID – 0x08,

Number of Data – 0x02

Line 746: Line 746: −

~~Server~~ must respond with acknowledgment:

+

The server must respond with an acknowledgment:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 765: Line 765:

*'''Example'''

−

~~Hexadecimal~~ stream of AVL Data Packet receiving and response in this example ~~are~~ given in hexadecimal form. The different fields of packet are ~~separate~~ into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of AVL Data Packet receiving and response in this example is given in the hexadecimal form. The different fields of the packet are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

−

Received data in hexadecimal stream:

+

Received data in the hexadecimal stream:

<code>003DCAFE0105000F33353230393330383634303336353508010000016B4F815B30010000000000000000000000000000000103021503010101425DBC000001</code>

Parsed:

Line 804: Line 804:

|-

| style="vertical-align: middle; text-align: center;" |Timestamp

−

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 4F 81 5B 30 (GMT: Thursday, June 13, 2019 6:23:26 AM)

+

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 4F 81 5B 30 (GMT: Thursday, June 13, 2019, 6:23:26 AM)

|-

| style="vertical-align: middle; text-align: center;" |Priority

Line 869: Line 869: −

~~Server~~ response in hexadecimal stream:

+

The server response in the hexadecimal stream:

Parsed:

Line 902: Line 902:

*'''<big>Protocols overview</big>'''

−

Codec8 Extended is used for FMBXXX family devices. This protocol looks familiar to Codec8 but they have some differences. ~~Main~~ differences between are shown in below table:

+

Codec8 Extended is used for FMBXXX family devices. This protocol looks familiar to Codec8 but they have some differences. The main differences between them are shown in below table:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 939: Line 939:

*'''AVL data packet'''

−

~~Below~~ table represents AVL data packet structure:

+

The below table represents the AVL data packet structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 964: Line 964:

'''Data Field Length''' – size is calculated starting from Codec ID to Number of Data 2.

'''Codec ID''' – in Codec8 Extended it is always <code>0x8E</code>.

−

'''Number of Data 1''' – a number ~~which~~ defines how many records are in the packet.

+

'''Number of Data 1''' – a number that defines how many records are in the packet.

'''AVL Data''' – actual data in the packet (more information below).

−

'''Number of Data 2''' – a number ~~which~~ defines how many records are in the packet. This number must be the same as “Number of Data 1”.

+

'''Number of Data 2''' – a number that defines how many records are in the packet. This number must be the same as “Number of Data 1”.

−

'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code ~~using for~~ detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

+

'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

−

'''Note:''' for [[FMB640]], [[FMB641]], [[FMC640]], and [[FMM640]], minimum AVL record size is 45 bytes (all IO elements disabled). ~~Maximum~~ AVL record size is 255 bytes. For other devices, the minimum AVL record size is 45 bytes (all IO elements disabled). Maximum AVL packet size is 1280 bytes.

+

'''Note:''' for [[FMB640]], [[FMB641]], [[FMC640]], and [[FMM640]], minimum AVL record size is 45 bytes (all IO elements disabled). The maximum AVL record size is 255 bytes. For other devices, the minimum AVL record size is 45 bytes (all IO elements disabled). Maximum AVL packet size is 1280 bytes.

*AVL Data

−

~~Below~~ table represents AVL Data structure:

+

The below table represents the AVL Data structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 989: Line 989:

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January 1970 UTC (UNIX time).

−

'''Priority''' – field ~~which define~~ AVL data priority (more information below).

+

'''Priority''' – a field that defines AVL data priority (more information below).

'''GPS Element''' – locational information of the AVL data (more information below).

−

'''IO Element''' – additional configurable information from device (more information below).

+

'''IO Element''' – additional configurable information from the device (more information below).

*Priority

Line 1,012: Line 1,012:

*GPS element

−

~~Below~~ table represents GPS Element structure:

+

The below table represents the GPS Element structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,032: Line 1,032: −

'''Longitude''' – east – west position.

+

'''Longitude''' – east-west position.

−

'''Latitude''' – north – south position.

+

'''Latitude''' – north-south position.

'''Altitude''' – meters above sea level.

'''Angle''' – degrees from north pole.

Line 1,039: Line 1,039:

'''Speed''' – speed calculated from satellites.

'''Note:''' Speed will be <code>0x0000</code> if GPS data is invalid.

−

Longitude and latitude are integer values built from degrees, minutes, seconds and milliseconds by formula:

+

Longitude and latitude are integer values built from degrees, minutes, seconds, and milliseconds by the formula:

[[Image:GPS.png]]

Where:

d – Degrees; m – Minutes; s – Seconds; ms – Milliseconds; p – Precision (10000000)

−

If longitude is in west or latitude in south, multiply result by –1.

+

If the longitude is in the west or latitude in the south, multiply the result by –1.

Note:

−

To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is <code>0</code>, coordinate is positive, if it is <code>1</code>, coordinate is negative.

+

To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is <code>0</code>, the coordinate is positive, if it is <code>1</code>, the coordinate is negative.

Example:

Received value: <code>20 9C CA 80</code> converted to BIN: <code>00100000 10011100 11001010 10000000</code> first bit is 0, which means coordinate is positive converted to DEC: <code>547146368</code>. For more information see two‘s complement arithmetic.

Line 1,057: Line 1,057:

| style="vertical-align: middle; text-align: center;" |2 bytes

| rowspan="33" style=" width:5%; vertical-align: middle; text-align: left;" |

−

| rowspan="33" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on event – this field defines which IO property has changed and generated an event. For example, when if Ignition state ~~changed~~ and it ~~generate~~ event, Event IO ID will be 0xEF (AVL ID: 239). If it’s not eventual record – the value is 0.

+

| rowspan="33" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on the event – this field defines which IO property has changed and generated an event. For example, when if the Ignition state changes and it generates an event, the Event IO ID will be 0xEF (AVL ID: 239). If it’s not an eventual record – the value is 0.

'''N''' – a total number of properties coming with record (N = N1 + N2 + N4 + N8).

'''N1''' – number of properties, which length is 1 byte.

Line 1,063: Line 1,063:

'''N4''' – number of properties, which length is 4 bytes.

'''N8''' – number of properties, which length is 8 bytes.

−

'''NX''' – a number of properties, which length is defined by length element.

+

'''NX''' – a number of properties, which length is defined by the length element.

'''N’th IO ID''' - AVL ID.

'''N'th Lenght''' - AVL ID value lenght.

Line 1,149: Line 1,149:

|-

! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |1’st IO Value

−

| style="vertical-align: middle; text-align: center;" |Defined by ~~lenght~~

+

| style="vertical-align: middle; text-align: center;" |Defined by length

|-

| colspan="2" style="vertical-align: middle; text-align: center;" |...

Line 1,160: Line 1,160:

|-

! rowspan="1" style="width:15%; vertical-align: middle; text-align: center;" |NX’th Value

−

| style="vertical-align: middle; text-align: center;" |Defined by ~~lenght~~

+

| style="vertical-align: middle; text-align: center;" |Defined by length

|-

|}

Line 1,170: Line 1,170:

*Example:

−

~~Module~~ connects to server and sends IMEI:

+

The module connects to the server and sends IMEI:

−

~~Server~~ accepts the module:

+

The server accepts the module:

−

~~Module~~ sends data packet:

+

The module sends data packet:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,185: Line 1,185:

| style="vertical-align: middle; text-align: center;" |Codec ID – 0x8E,

Number of Data – '''0x02'''

−

(Encoded using continuous bit stream. ~~Last~~ byte padded to align to byte boundary)

+

(Encoded using continuous bit stream. The last byte is padded to align to the byte boundary)

| style="vertical-align: middle; text-align: center;" |CRC of “AVL Data Array”

|-

Line 1,199: Line 1,199:

*'''Example'''

−

~~Hexadecimal~~ stream of AVL Data Packet receiving and response in this example ~~are~~ given in hexadecimal form. The different fields of packet are ~~separate~~ into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of AVL Data Packet receiving and response in this example is given in the hexadecimal form. The different fields of the packet are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

−

Received data in hexadecimal stream:

+

Received data in the hexadecimal stream:

<code>000000000000004A8E010000016B412CEE000100000000000000000000000000000000010005000100010100010011001D00010010015E2C880002000B000000003544C87

A000E000000001DD7E06A00000100002994</code>

Line 1,226: Line 1,226:

| rowspan="25" style="vertical-align: middle; text-align: center;" |AVL Data

| style="vertical-align: middle; text-align: center;" |Timestamp

−

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 41 2C EE 00 (GMT: Monday, June 10, 2019 11:36:32 AM)

+

| style="vertical-align: middle; text-align: center;" |00 00 01 6B 41 2C EE 00 (GMT: Monday, June 10, 2019, 11:36:32 AM)

|-

| style="vertical-align: middle; text-align: center;" |Priority

Line 1,320: Line 1,320:

*'''Communication with server'''

−

The module sends the UDP channel packet with an encapsulated AVL data packet. The server sends the UDP channel packet with an encapsulated response module that validates AVL Packet ID and the Number of accepted AVL elements. If server response with valid AVL Packet ID ~~is not received~~ within configured timeout, the module can retry sending.

+

The module sends the UDP channel packet with an encapsulated AVL data packet. The server sends the UDP channel packet with an encapsulated response module that validates the AVL Packet ID and the Number of accepted AVL elements. If the server response is not received with a valid AVL Packet ID within configured timeout, the module can retry sending.

*Example:

−

~~Module~~ sends the data:

+

The module sends the data:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,337: Line 1,337:

IMEI Length – 0x000F

IMEI – 0x313233343536373839303132333435

−

(Encoded using continuous bit stream. ~~Last~~ byte padded to align to byte boundary)

+

(Encoded using continuous bit stream. The last byte is padded to align to the byte boundary)

| style="vertical-align: middle; text-align: center;" |Codec ID – 0x8E,

Number of Data – 0x02

Line 1,349: Line 1,349: −

~~Server~~ must respond with acknowledgment:

+

The server must respond with an acknowledgment:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,368: Line 1,368:

*'''Example'''

−

~~Hexadecimal~~ stream of AVL Data Packet receiving and response in this example ~~are~~ given in hexadecimal form. The different fields of packet are ~~separate~~ into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of AVL Data Packet receiving and response in this example is given in the hexadecimal form. The different fields of the packet are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

−

Received data in hexadecimal stream:

+

Received data in the hexadecimal stream:

<code>005FCAFE0107000F3335323039333038363430333635358E010000016B4F831C680100000000000000000000000000000000010005000100010100010011009D000100</code>

Line 1,485: Line 1,485: −

~~Server~~ response in hexadecimal stream:

+

The server response in the hexadecimal stream:

Parsed:

Line 1,518: Line 1,518:

*'''<big>Protocol overview</big>'''

−

Codec16 is using for [[FMB630]]/FM63XY series devices. This protocol looks familiar like Codec8 but they have some differences. ~~Main~~ differences between are shown in table below:

+

Codec16 is using for [[FMB630]]/FM63XY series devices. This protocol looks familiar like Codec8 but they have some differences. The main differences between them are shown in the table below:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,544: Line 1,544: −

'''Note:''' Codec16 is supported from firmware – 00.03.xx and newer. ([[FMB630]]/FM63XY) || AVL ~~ID‘s which~~ are higher than 255 will can be used only in Codec16 protocol.

+

'''Note:''' Codec16 is supported from firmware – 00.03.xx and newer. ([[FMB630]]/FM63XY) || AVL IDs that are higher than 255 will can be used only in the Codec16 protocol.

*'''<big>Codec 16 protocol sending over TCP</big>'''

Line 1,550: Line 1,550:

*'''AVL data packet'''

−

~~Below~~ table represents AVL data packet structure:

+

The below table represents the AVL data packet structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,575: Line 1,575:

'''Data Field Length''' – size is calculated starting from Codec ID to Number of Data 2.

'''Codec ID''' – in Codec16 it is always 0x10.

−

'''Number of Data 1''' – a number ~~which~~ defines how many records are in the packet.

+

'''Number of Data 1''' – a number that defines how many records are in the packet.

'''AVL Data''' – actual data in the packet (more information below).

−

'''Number of Data 2''' – a number ~~which~~ defines how many records are in the packet. This number must be the same as “Number of Data 1”.

+

'''Number of Data 2''' – a number that defines how many records are in the packet. This number must be the same as “Number of Data 1”.

−

'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code ~~using for~~ detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

+

'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

−

'''Note:''' for [[FMB630]] and FM63XY, minimum AVL record size is 45 bytes (all IO elements disabled). ~~Maximum~~ AVL record size is 255 bytes.

+

'''Note:''' for [[FMB630]] and FM63XY, the minimum AVL record size is 45 bytes (all IO elements disabled). The maximum AVL record size is 255 bytes.

*AVL Data

−

~~Below~~ table represents AVL Data structure:

+

The below table represents the AVL Data structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,600: Line 1,600:

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January 1970 UTC (UNIX time).

−

'''Priority''' – field ~~which define~~ AVL data priority (more information below).

+

'''Priority''' – a field that defines AVL data priority (more information below).

'''GPS Element''' – location information of the AVL data (more information below).

−

'''IO Element''' – additional configurable information from device (more information below).

+

'''IO Element''' – additional configurable information from the device (more information below).

*Priority

Line 1,623: Line 1,623:

*GPS element

−

~~Below~~ table represents GPS Element structure:

+

The below table represents the GPS Element structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,643: Line 1,643: −

'''Longitude''' – east – west position.

+

'''Longitude''' – east-west position.

−

'''Latitude''' – north – south position.

+

'''Latitude''' – north-south position.

'''Altitude''' – meters above sea level.

'''Angle''' – degrees from north pole.

Line 1,650: Line 1,650:

'''Speed''' – speed calculated from satellites.

'''Note:''' Speed will be <code>0x0000</code> if GPS data is invalid.

−

Longitude and latitude are integer values built from degrees, minutes, seconds and milliseconds by formula:

+

Longitude and latitude are integer values built from degrees, minutes, seconds, and milliseconds by the formula:

[[Image:GPS.png]]

Where:

d – Degrees; m – Minutes; s – Seconds; ms – Milliseconds; p – Precision (10000000)

−

If longitude is in west or latitude in south, multiply result by –1.

+

If the longitude is in the west or latitude in the south, multiply the result by –1.

Note:

−

To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is <code>0</code>, coordinate is positive, if it is <code>1</code>, coordinate is negative.

+

To determine if the coordinate is negative, convert it to binary format and check the very first bit. If it is <code>0</code>, the coordinate is positive, if it is <code>1</code>, the coordinate is negative.

Example:

Received value: <code>20 9C CA 80</code> converted to BIN: <code>00100000 10011100 11001010 10000000</code> first bit is 0, which means coordinate is positive converted to DEC: <code>547146368</code>. For more information see two‘s complement arithmetic.

Line 1,668: Line 1,668:

| style="vertical-align: middle; text-align: center;" |2 bytes

| rowspan="27" style=" width:5%; vertical-align: middle; text-align: left;" |

−

| rowspan="27" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on event – this field defines which IO property has changed and generated an event. For example, when if Ignition state ~~changed~~ and it ~~generate~~ event, Event IO ID will be 0xEF (AVL ID: 239). If it’s not eventual record – the value is 0.

+

| rowspan="27" style=" width:65%; vertical-align: middle; text-align: left;" |'''Event IO ID''' – if data is acquired on the event – this field defines which IO property has changed and generated an event. For example, when if the Ignition state changes and it generates an event, the Event IO ID will be 0xEF (AVL ID: 239). If it’s not an eventual record – the value is 0.

'''Generation type''' - data event generation type. More information about it you can find here.

'''N''' – a total number of properties coming with record (N = N1 + N2 + N4 + N8).

Line 1,789: Line 1,789:

*'''Communication with server'''

−

Communication with server is the same as with Codec8 protocol, except in Codec16 protocol Codec ID is <code>0x10</code> and has generation type.

+

Communication with the server is the same as with Codec8 protocol, except in Codec16 protocol Codec ID is <code>0x10</code> and has generation type.

*Example:

−

~~Module~~ connects to server and sends IMEI:

+

The module connects to the server and sends IMEI:

−

~~Server~~ accepts the module:

+

The server accepts the module:

−

~~Module~~ sends data packet:

+

The module sends data packet:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 1,808: Line 1,808:

| style="vertical-align: middle; text-align: center;" |Codec ID – 0x10,

Number of Data – '''0x02'''

−

(Encoded using continuous bit stream. The last byte padded to align to byte boundary)

+

(Encoded using continuous bit stream. The last byte is padded to align to the byte boundary)

| style="vertical-align: middle; text-align: center;" |CRC of “AVL Data Array”

|-

Line 1,822: Line 1,822:

*'''Example'''

−

~~Hexadecimal~~ stream of AVL Data Packet receiving and response in this example ~~are~~ given in hexadecimal form. The different fields of packet are ~~separate~~ into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of AVL Data Packet receiving and response in this example is given in the hexadecimal form. The different fields of the packet are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

−

Received data in hexadecimal stream:

+

Received data in the hexadecimal stream:

Line 1,850: Line 1,850:

(1'st record)

| style="vertical-align: middle; text-align: center;" |Timestamp

−

| style="vertical-align: middle; text-align: center;" |00 00 01 6B DB C7 83 30 (GMT: Wednesday, July 10, 2019 12:06:54 PM)

+

| style="vertical-align: middle; text-align: center;" |00 00 01 6B DB C7 83 30 (GMT: Wednesday, July 10, 2019, 12:06:54 PM)

|-

| style="vertical-align: middle; text-align: center;" |Priority

Line 1,921: Line 1,921:

(2'nd record)

| style="vertical-align: middle; text-align: center;" |Timestamp

−

| style="vertical-align: middle; text-align: center;" |00 00 01 6B DB C7 87 18 (GMT: Wednesday, July 10, 2019 12:06:55 PM)

+

| style="vertical-align: middle; text-align: center;" |00 00 01 6B DB C7 87 18 (GMT: Wednesday, July 10, 2019, 12:06:55 PM)

|-

| style="vertical-align: middle; text-align: center;" |Priority

Line 2,004: Line 2,004:

*'''UDP channel protocol'''

−

AVL data packet is the same as with Codec8, except Codec ID is changed to <code>0x10</code>. AVL Data encoding performed according to Codec16 protocol.

+

AVL data packet is the same as with Codec8, except Codec ID is changed to <code>0x10</code>. AVL Data encoding is performed according to the Codec16 protocol.

*'''Communication with server'''

−

The module sends the UDP channel packet with an encapsulated AVL data packet. The server sends the UDP channel packet with an encapsulated response module validates AVL Packet ID and the Number of accepted AVL elements. If server ~~response~~ with valid AVL Packet ID is not received within configured timeout, the module can retry sending.

+

The module sends the UDP channel packet with an encapsulated AVL data packet. The server sends the UDP channel packet with an encapsulated response module that validates the AVL Packet ID and the Number of accepted AVL elements. If the server responds with a valid AVL Packet ID that is not received within configured timeout, the module can retry sending.

*Example:

−

~~Module~~ sends the data:

+

The module sends the data:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 2,025: Line 2,025:

IMEI Length – 0x000F

IMEI – 0x313233343536373839303132333435

−

(Encoded using continuous bit stream. ~~Last~~ byte padded to align to byte boundary)

+

(Encoded using continuous bit stream. The last byte is padded to align to the byte boundary)

| style="vertical-align: middle; text-align: center;" |Codec ID – 0x10,

Number of Data – 0x02

Line 2,037: Line 2,037: −

~~Server~~ must respond with acknowledgment:

+

The server must respond with an acknowledgment:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 2,056: Line 2,056:

*'''Example'''

−

~~Hexadecimal~~ stream of AVL Data Packet receiving and response in this example ~~are~~ given in hexadecimal form. The different fields of packet are ~~separate~~ into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of AVL Data Packet receiving and response in this example is given in the hexadecimal form. The different fields of the packet are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

−

Received data in hexadecimal stream:

+

Received data in the hexadecimal stream:

<code>015BCAFE0101000F33353230393430383532333135393210070000015117E40FE80000000000000000000000000000000000EF05050400010000030000B4000</code>

Line 2,096: Line 2,096:

|-

| style="vertical-align: middle; text-align: center;" |Timestamp

−

| style="vertical-align: middle; text-align: center;" |00 00 01 51 17 E4 0F E8 (GMT: Wednesday, November 18, 2015 12:00:01 AM)

+

| style="vertical-align: middle; text-align: center;" |00 00 01 51 17 E4 0F E8 (GMT: Wednesday, November 18, 2015, 12:00:01 AM)

|-

| style="vertical-align: middle; text-align: center;" |Priority

Line 2,176: Line 2,176: −

~~Server~~ response in hexadecimal stream:

+

The server response in the hexadecimal stream:

Parsed:

Line 2,252: Line 2,252:

='''<big>Codec for communication over GPRS messages</big>'''=

−

In this chapter, you will find information about every Codec protocol which are ~~using~~ for communication over GPRS messages and differences between them.

+

In this chapter, you will find information about every Codec protocol which are used for communication over GPRS messages and the differences between them.

=='''<big>Codec 12</big>'''==

Line 2,258: Line 2,258:

*'''<big>About Codec12</big>'''

−

Codec12 is the original and main Teltonika protocol for device-server communication over GPRS messages. Codec12 GPRS commands can be used for sending configuration, debug, digital outputs control commands, or other (special purpose ~~command~~ on special firmware versions). This protocol is also necessary for using [[FMB630]]/[[FM6300]]/FM5300/FM5500/FM4200 features like: Garmin, LCD communication, COM TCP Link Mode.

+

Codec12 is the original and main Teltonika protocol for device-server communication over GPRS messages. Codec12 GPRS commands can be used for sending configuration, debug, digital outputs control commands, or other (special purpose commands on special firmware versions). This protocol is also necessary for using [[FMB630]]/[[FM6300]]/FM5300/FM5500/FM4200 features like Garmin, LCD communication, and COM TCP Link Mode.

*'''<big>GPRS command session</big>'''

Line 2,264: Line 2,264:

The following figure shows how the GRPS command session is started over TCP.

[[File:Codec12.png|1150px]]

−

First, the Teltonika device opens the GPRS session and sends AVL data to the server (refer device protocols). Once all records are sent and correct sent data array acknowledgment is received by device then GPRS commands in Hex can be sent to the device.

+

First, the Teltonika device opens the GPRS session and sends AVL data to the server (refer to device protocols). Once all records are sent and the correct sent data array acknowledgment is received by the device then GPRS commands in Hex can be sent to the device.

−

The ACK (~~acknowledge~~ of IMEI from server) is a one-byte constant 0x01. The acknowledgment of each data array send from the device is four bytes integer – a number of received records.

+

The ACK (acknowledgment of IMEI from server) is a one-byte constant 0x01. The acknowledgment of each data array send from the device is four bytes integer – a number of received records.

−

Note, that the GPRS session should remain active between device and server, while GPRS commands are sent. For this reason, active datalink timeout (global parameters in device configuration) is recommended to be set to 259200 (maximum value).

+

Note, that the GPRS session should remain active between the device and server, while GPRS commands are sent. For this reason, active datalink timeout (global parameters in device configuration) is recommended to be set to 259200 (maximum value).

*'''<big>General Codec12 message structure</big>'''

−

The following diagram shows basic structure of Codec12 messages.

+

The following diagram shows the basic structure of Codec12 messages.

'''Command message structure:'''

{| class="nd-othertables_2" style="width:100%;"

Line 2,330: Line 2,330:

'''Command/Response Size''' – command or response length.

'''Command/Response''' – command or response in HEX.

−

'''Command/Response Quantity 2''' - a byte ~~which~~ defines how many records (commands or responses) are in the packet. This byte will not be parsed but it’s recommended that it should contain the same value as Command/Response Quantity 1.

+

'''Command/Response Quantity 2''' - a byte that defines how many records (commands or responses) are in the packet. This byte will not be parsed but it’s recommended that it should contain the same value as Command/Response Quantity 1.

−

'''CRC-16''' – calculated from Codec ID to the Command Quantity 2. CRC (Cyclic Redundancy Check) is an error-detecting code ~~using for~~ detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

+

'''CRC-16''' – calculated from Codec ID to the Command Quantity 2. CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

−

Note that difference between commands and responses is message type field: <code>0x05</code> means command and <code>0x06</code> means response.

+

Note that the difference between commands and responses is the message type field: <code>0x05</code> means command and <code>0x06</code> means response.

*'''<big>Command coding table</big>'''

Line 2,341: Line 2,341:

*'''<big>Command parsing example</big>'''

−

~~Hexadecimal~~ stream of command and answer in this example is given in hexadecimal form. The different fields of the message are separated into different table columns for better readability and understanding.

+

The hexadecimal stream of command and answer in this example is given in the hexadecimal form. The different fields of the message are separated into different table columns for better readability and understanding.

*'''<big>GPRS commands examples</big>'''

−

~~Hexadecimal~~ stream of GPRS command and answer in these examples are given in hexadecimal form. The different fields of messages are ~~separate~~ into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of GPRS command and answer in these examples are given in the hexadecimal form. The different fields of messages are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

'''1'st example:''' Sending ''[[FMB getinfo|getinfo]]'' SMS command via GPRS Codec12

−

Server request in hexadecimal stream:

+

Server request in the hexadecimal stream:

Parsed:

Line 2,388: Line 2,388:

Note that Server Command converted from HEX to ASCII means ''[[FMB getinfo|getinfo]]''

−

Device response in hexadecimal stream:

+

Device response in the hexadecimal stream:

Line 2,432: Line 2,432:

'''2'nd example:''' Sending ''[[FMB getio|getio]]'' SMS command via GPRS Codec12

−

Server request in hexadecimal stream:

+

Server request in the hexadecimal stream:

Parsed:

Line 2,473: Line 2,473:

Note that Server Command converted from HEX to ASCII means ''[[FMB getio|getio]]''

−

Device response in hexadecimal stream:

+

Device response in the hexadecimal stream:

Parsed:

Line 2,518: Line 2,518:

*'''<big>Communication with server</big>'''

−

The GSM/GPRS commands can be sent from a terminal program. We recommend ~~to use~~ Hercules (in TCP server mode). Simply write command into Hercules Send field, check HEX box and click Send button. Note that the TCP server must be listening on a specified port (see Port field and Listen button below).

+

The GSM/GPRS commands can be sent from a terminal program. We recommend using Hercules (in TCP server mode). Simply write the command into the Hercules Send field, check the HEX box and click Send button. Note that the TCP server must be listening on a specified port (see Port field and Listen button below).

[[File:Hercules.jpeg]]

Line 2,536: Line 2,536:

*'''<big>About Codec13</big>'''

−

Codec13 is the original Teltonika protocol for device-server communication over GPRS messages and it is based on Codec12 protocol. The main differences of Codec13 are that timestamp is ~~using~~ in messages and communication is one way only (Codec13 is used for Device -> Server sending).

+

Codec13 is the original Teltonika protocol for device-server communication over GPRS messages and it is based on the Codec12 protocol. The main differences of Codec13 are that timestamp is used in messages and communication is one way only (Codec13 is used for Device -> Server sending).

*'''<big>General Codec13 message structure</big>'''

−

The following diagram shows basic structure of Codec 13 messages:

+

The following diagram shows the basic structure of Codec 13 messages:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 2,568: Line 2,568: −

'''Preamble''' – the packet starts with preamble field (four zero bytes).

+

'''Preamble''' – the packet starts with a preamble field (four zero bytes).

'''Data Size''' – size is calculated from the Codec ID field to the second Command Quantity field.

'''Codec ID''' – in Codec13 it is always <code>0x0D</code>.

'''Command Quantity 1''' – <code>0x01</code>, it is ignored when parsing the message.

'''Command Type''' – it is always <code>0x06</code> since the packet is direction is FM->Server.

−

'''Command Size''' – command size field includes size of timestamp too, so it is equal to the size of payload + size of timestamp.

+

'''Command Size''' – command size field includes the size of the timestamp too, so it is equal to the size of the payload + the size of the timestamp.

−

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January, 1970 UTC (UNIX time).

+

'''Timestamp''' – a difference, in milliseconds, between the current time and midnight, January 1970 UTC (UNIX time).

'''Command''' – actual received data.

−

'''Command Quantity 2''' – a byte ~~which~~ defines how many records (commands) are in the packet. This byte will not be parsed but it’s recommended that it should contain the same value as Command/Response Quantity 1.

+

'''Command Quantity 2''' – a byte that defines how many records (commands) are in the packet. This byte will not be parsed but it’s recommended that it should contain the same value as Command/Response Quantity 1.

−

'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code ~~using for~~ detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

+

'''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

−

'''Note:''' Codec13 packets are used only when “Message Timestamp” parameter in RS232 settings is enabled.

+

'''Note:''' Codec13 packets are used only when the “Message Timestamp” parameter in RS232 settings is enabled.

*'''<big>Command parsing example</big>'''

−

~~Hexadecimal~~ stream of GPRS command in this example is given in hexadecimal form. The different fields of message are ~~separate~~ into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of the GPRS command in this example is given in the hexadecimal form. The different fields of the message are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

Sending ''[[FMB getinfo|getinfo]]'' SMS command via GPRS Codec13.

Hexadecimal stream:

Line 2,633: Line 2,633:

*'''<big>About Codec14</big>'''

−

Codec14 is the original Teltonika protocol for device-server communication over GPRS messages and it is based on Codec12 protocol.

+

Codec14 is the original Teltonika protocol for device-server communication over GPRS messages and it is based on the Codec12 protocol.

−

The main difference of Codec14 is that device will answer to GPRS command if the device physical IMEI number matches specified IMEI number in GPRS command.

+

The main difference of Codec14 is that the device will answer the GPRS command if the device's physical IMEI number matches the specified IMEI number in the GPRS command.

−

Codec14 GPRS commands can be used for sending configuration, debug, digital outputs control commands, or other (special purpose ~~command~~ on special firmware versions).

+

Codec14 GPRS commands can be used for sending configuration, debug, digital outputs control commands, or other (special purpose commands on special firmware versions).

*'''<big>FMB firmware requirements</big>'''

Line 2,706: Line 2,706:

'''Codec ID''' – in Codec14 it is always <code>0x0E</code>.

'''Command/Response Quantity 1''' – it is ignored when parsing the message.

−

'''Type''' – if it is request command from server it has to contain 0x05. The response type field will contain <code>0x06</code> if it’s ACK or <code>0x11</code> if it’s nACK.

+

'''Type''' – if it is a request command from the server it has to contain 0x05. The response type field will contain <code>0x06</code> if it’s ACK or <code>0x11</code> if it’s nACK.

−

''Explanation:'' If command message IMEI is equal to actual device IMEI, received command will be executed and response will be sent with ACK (<code>0x06</code>) message type field value. If command message IMEI doesn’t match actual device IMEI, received command won’t be executed and response to the server will be sent with nACK (<code>0x11</code>) message type field value.

+

''Explanation:'' If command message IMEI is equal to actual device IMEI, received command will be executed and response will be sent with ACK (<code>0x06</code>) message type field value. If the command message IMEI doesn’t match the actual device IMEI, the received command won’t be executed and a response to the server will be sent with nACK (<code>0x11</code>) message type field value.

'''Command/Response Size''' – command or response length.

−

''Note:'' make sure that size is IMEI size 8 + actual command size. ~~Minimal~~ value is 8 because Codec14 always contains IMEI and it’s 8 bytes.

+

''Note:'' make sure that size is IMEI size 8 + actual command size. The minimal value is 8 because Codec14 always contains IMEI and it’s 8 bytes.

−

'''IMEI (HEX)''' – it is send as HEX value. ~~Example~~ if device IMEI is 123456789123456 then IMEI data field will contain <code>0x0123456789123456</code> value.

+

'''IMEI (HEX)''' – it is send as HEX value. For example, if the device IMEI is 123456789123456 then the IMEI data field will contain <code>0x0123456789123456</code> value.

'''Command/Response''' – command or response in HEX.

−

'''Command/Response Quantity 2''' - a byte ~~which~~ defines how many records (commands or responses) are in the packet. This byte will not be parsed but it’s recommended that it should contain the same value as Command/Response Quantity 1. '''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code ~~using~~ to detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

+

'''Command/Response Quantity 2''' - a byte that defines how many records (commands or responses) are in the packet. This byte will not be parsed but it’s recommended that it should contain the same value as Command/Response Quantity 1. '''CRC-16''' – calculated from Codec ID to the Second Number of Data. CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data. For calculation we are using [[Codec#CRC-16|CRC-16/IBM]].

*'''<big>GPRS in Codec14 examples</big>'''

−

~~Hexadecimal~~ stream of GPRS command and answer in this example ~~are~~ given in hexadecimal form. The different fields of message are ~~separate~~ into different table columns for better readability and some of them are converted to ASCII values for better understanding.

+

The hexadecimal stream of the GPRS command and answer in this example is given in the hexadecimal form. The different fields of the message are separated into different table columns for better readability and some of them are converted to ASCII values for better understanding.

Sending ''[[FMB getver|getver]]'' SMS command via GPRS Codec14:

Server requests in Hexadecimal stream:

Line 2,762: Line 2,762:

Note that Server Command converted from HEX to ASCII means ''[[FMB getver|getver]]''

−

Device ACK response in hexadecimal stream:

+

Device ACK response in the hexadecimal stream:

Line 2,809: Line 2,809:

Note that Device Response converted from HEX to ASCII means:

''Ver:03.18.14_04 GPS:AXN_5.10_3333 Hw:FMB120 Mod:15 IMEI:352093081452251 Init:2018-11-22 7:13 Uptime:17234 MAC:60BDD0016261 SPC:1(0) AXL:0 OBD:0 BL:1.6 BT:4''

−

Device nACK response in hexadecimal stream:

+

Device nACK response in the hexadecimal stream:

Parsed:

Line 2,849: Line 2,849:

=='''<big>Differences between Codec 12, Codec 13 and Codec 14</big>'''==

−

In the table below you will see differences between Codec12, Codec13 and Codec14.

+

In the table below you will see differences between Codec12, Codec13, and Codec14.

{| class="nd-othertables_2" style="width:100%;"

|+

Line 2,891: Line 2,891:

='''<big>24 Position SMS Data Protocol</big>'''=

−

24-hour SMS is usually sent once every day and contains GPS data for the last 24 hours. TP-DCS field of this SMS should indicate that message contains 8-bit data (i.e. TP-DCS can be <code>0x04</code>).

+

24-hour SMS is usually sent once every day and contains GPS data for the last 24 hours. The TP-DCS field of this SMS should indicate that message contains 8-bit data (i.e. TP-DCS can be <code>0x04</code>).

Note, that 24 position data protocol is used only with subscribed SMS. Event SMS uses standard AVL data protocol.

*'''<big>Encoding</big>'''

−

To be able to compress 24 GPS data entries into one SMS (140 octets), the data is encoded extensively using bit fields. ~~Data~~ packet can be interpreted as a bitstream, where all bits are numbered as follows:

+

To be able to compress 24 GPS data entries into one SMS (140 octets), the data is encoded extensively using bit fields. The data packet can be interpreted as a bitstream, where all bits are numbered as follows:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 2,912: Line 2,912: −

Bits in a byte are numbered starting from the least significant bit. A field of 25 bits would consist of bits 0 to 24 where 0 is the least significant bit and bit 24 – most significant bit.

+

Bits in a byte are numbered starting from the least significant bit. A field of 25 bits would consist of bits 0 to 24 where 0 is the least significant bit and bit 24 – is the most significant bit.

*'''<big>Structure</big>'''

−

Below in the tables you will see SMS Data Structure:

+

Below in the tables, you will see the SMS Data Structure:

{| class="nd-othertables_2" style="width:100%;"

|+

Line 2,955: Line 2,955: −

The time of only the first GPS data element is specified in Timestamp field. ~~Time~~ corresponding to each further element can be computed as elementTime = Timestamp + (1 hour * elementNumber).

+

The time of only the first GPS data element is specified in the Timestamp field. The time corresponding to each further element can be computed as elementTime = Timestamp + (1 hour * elementNumber).

{| class="nd-othertables_2" style="width:100%;"

|+

Line 3,025: Line 3,025:

*'''<big>SMS Events</big>'''

−

When ~~Configured~~ to generate SMS event user will get this SMS upon event:

+

When configured to generate an SMS event user will get this SMS upon event:

''<Year/Month/Day> <Hour:Minute:Second> P:<profile_nr> <SMS Text> Val:<Event Value> Lon:<longitude> Lat:<latitude> Q:<HDOP>''

Example:

Line 3,031: Line 3,031:

='''<big>Sending data using SMS</big>'''=

−

This type data ~~sending~~ is ~~using~~ for FMBXXX devices which can be configured in [[FMB120 SMS/Call settings#SMS Data Sending|SMS Data Sending settings]].

+

This type of data sent is used for FMBXXX devices which can be configured in [[FMB120 SMS/Call settings#SMS Data Sending|SMS Data Sending settings]].

*'''<big>Data sending via SMS</big>'''

−

AVL data or events can be sent encapsulated in binary SMS. TP-DCS field of these SMS should indicate that message contains 8-bit data (for example: TP-DCS can be <code>0x04</code>).

+

AVL data or events can be sent encapsulated in binary SMS. The TP-DCS field of these SMS should indicate that message contains 8-bit data (for example TP-DCS can be <code>0x04</code>).

{| class="nd-othertables_2" style="width:100%;"

|+

Line 3,053: Line 3,053:

='''<big>CRC-16</big>'''=

−

CRC (Cyclic Redundancy Check) is an error-detecting code ~~using~~ to detect accidental changes to RAW data. The algorithm on how to calculate CRC-16 (also known as CRC-16/IBM) you will find below.

+

CRC (Cyclic Redundancy Check) is an error-detecting code used to detect accidental changes to RAW data. The algorithm on how to calculate CRC-16 (also known as CRC-16/IBM) you will find below.

[[File:CRC16.png]]

[[Category:General Information|50]]

SandraG

Administrators

2,544

edits

Namespaces

Variants

Views

More

Search

Changes

Teltonika Data Sending Protocols (view source)

Revision as of 12:20, 29 November 2022

Navigation menu

Personal tools

NAVIGATION

Tools

Categories