View source for Which data protocol to choose Codec 8 or Codec 8 Extended

==Recommendation==
We strongly recommend all clients to use Codec 8 Extended protocol, in order to be able to use all device features.

===Reason to choose Codec 8 Extended===

*'''Codec 8''' supports max I/O elements up to 255 [[Full AVL ID List (Mobility)|AVL ID]]. Although this standard is older, it was left as an option for clients that have already integrated this protocol into their platforms.
*'''Codec 8 Extended''' supports 2 bytes, 65 535 AVLs.

''For example'', '''Codec 8''' does not support [[Full AVL ID List (Mobility)|AVL ID]] 385, which is an ID for '''Beacon ID''', while '''Codec 8 Extended''' supports all ID's that are listed on [[Full AVL ID List (Mobility)|AVL ID]] page.

For more information about Codec 8 Extended protocol visit: [[Teltonika_Data_Sending_Protocols#Codec_8_Extended| Codec 8 Extended]]
===Differences between Codec 8 and Codec 8 Extended===

----
{| class="nd-othertables_2" style="width:100%;"
|+
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec8
! rowspan="1" style="width:10%; border-bottom: 2px solid #0054A6; vertical-align: middle; text-align: center;" |Codec8 Extended
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Codec ID
| style="vertical-align: middle; text-align: center;" |0x08
| style="vertical-align: middle; text-align: center;" |0x8E
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element total IO count length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element IO count length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |AVL Data IO element AVL ID length
| style="vertical-align: middle; text-align: center;" |1 byte
| style="vertical-align: middle; text-align: center;" |2 bytes
|-
! rowspan="1" style="width:10%; vertical-align: middle; text-align: center;" |Variable size IO elements
| style="vertical-align: middle; text-align: center;" |Does not include
| style="vertical-align: middle; text-align: center;" |Includes variable size elements
|-
|} <br />

''Note: Both Codec 8 and Codec 8 Extended are transferring periodic data.''

==Setting up your configuration to use Codec 8 Extended protocol==

===System panel===

*Set '''Data Protocol''' to '''Codec 8 Extended'''. This way, the device will be able to include 2 byte length AVL IO elements instead of 1 byte, so more parameters whose AVL ID is higher than 255 could be included to the packet.
*Save the changes to the device.

[[File:Codec8E.png|thumb|System panel]]<br />
More information about ''System'' panel and it's parameters for each device can be found here: 

[[TST100 System settings|TST100]] | [[TFT100 System settings|TFT100]] | [[GH5200 System settings|GH5200]] | [[TMT250 System settings|TMT250]]

[[Category: General Technical Questions]]