subscribe to our Youtube


4167 questions

4739 answers


0 members

We are migrating to our new platform at Moving forward, you can continue discussions on this new platform. This current platform will be temporarily maintained for reference purposes.
0 votes
in Vehicle tracking by anonymous
In Codec protocol, an short example is given for event record of ignition. However, I could not find a detailed explanation about Event IO ID and AVL ID. Why 0xEF correspond to Ignition event, what ID corresponds to ignition on and off... etc

Can you please let me know where I can find these information?

1 Answer

0 votes
by anonymous

Hello REE,

Thank you for reaching out to us.

Our trackers sent AVL packets to servers in Hexadecimal format, 0xEF converted to decimal is 239, which represents the AVL ID for Ignition. You can verify all the AVL ID lists of each tracker on our wiki page, selecting the tracker model and then selecting the Teltonika Data Sending Parameters ID section.

For example, AVL IDs of FMB920 can be found here:

In the list, you can find as well the values that the AVL ID can take. For ignition:

  • 0 = Ignition OFF
  • 1 = Ignition ON

Regarding the Event IO ID, all the I/Os can be configured on four priority options:

  1. None: The module doesn't generate an additional record. If Ignition is set to this priority, it will never be sent on the AVL packet. 
  2. Low: The module makes an additional record with an indication that the event was caused by an I/O element change (Depending on Operands configuration). If Ignition is set to this priority, it will be sent in each AVL packet and if a change occurs (change from 0 to 1 or vice-versa) the AVL ID will be set on the Event IO ID of the record.
  3. High: The module makes an additional record with a High Priority flag on the record and sends Event IO ID packet immediately to the server. If Ignition is set to this priority, it will be sent in each AVL packet and if a change occurs (change from 0 to 1 or vice-versa) the AVL ID will be set on the Event IO ID of the record with High Priority (01) and send inmediately.
  4. Panic: Same as High Priority, but if GPRS fails, it sned an AVL packet using SMS data if SMS data sending is enabled and the number is provided in SMS/Call Settings.
You can refer to the following links for further details:
Kind regards. 
by anonymous

Many thanks. Can I ask more questions? For ignition, 

  • 0 = Ignition OFF
  • 1 = Ignition ON

Where can I check the Ignition status in the Codec 8 protocol? is it in one_byte_io_value?  

by anonymous


Please refer to the following raw data, this is the typical data sent by the tracker to the server under TCP protocol:

1. Ignition OFF: 


  1. Preamble: 000000
  2. AVL Data Length: 00000023
  3. Codec ID & AVL Data count: 08 01
  4. Time Stamp: 00000180D83F3658
  5. Priority: 00
  6. Longitude & Latitude: D0E26154 FB29B46C
  7. Altitude, Angle & Satellites & Speed: 0000 0000 00 0000
  8. Event ID: 00
  9. Element Count: 01
  10. 1 Byte Element Count: 01
  11. 1 Byte ID: EF (Ignition)
  12. ID Value: 00 (OFF)
  13. 2, 4 & 8 Byte Count: 00 00 00
  14. AVL Data Count: 01
  15. CRC: 00009939

2. Ignition ON with High Priority: 


  1. Priority: 01 (High)
  2. Event ID: EF (Event which generates the record)   
  3. 1 Byte ID: EF (Ignition)
  4. ID Value: 01 (ON)

For further explanation about parsing this data, check:

Best regards.