Namespaces
Page
Discussion
Variants
Views
Read
View source
View history
PDF Export
More
Search
Changes
← Older edit
Newer edit →
Codec
(view source)
Revision as of 11:55, 2 November 2018
825 bytes added
,
11:55, 2 November 2018
→Codec 16 Nebaigta
Line 1,427:
Line 1,427:
Codec16 is supported from firmware – 00.03.xx and newer.
Codec16 is supported from firmware – 00.03.xx and newer.
ll AVL ID‘s which are higher then 255 will can be used only in CODEC16 protocol.
ll AVL ID‘s which are higher then 255 will can be used only in CODEC16 protocol.
+
+
+
<small>Generation type elements:</small>
+
{| class="wikitable"
+
|-
+
!style="background: black; color: white;"| Value !!style="background: black; color: white;"| Record created
+
|-
+
| 0 || On exit
+
|-
+
| 1 || On Entrance
+
|-
+
| 2 || On Both
+
|-
+
| 3 || Reserved
+
|-
+
| 4 || Hysterisis
+
|-
+
| 5 || On Change
+
|-
+
| 6 || Eventual
+
|-
+
| 7 || Periodcal
+
|}
+
+
+
<small>Codec16 TCP packet frame:</small>
+
{| class="wikitable"
+
|-
+
! Header !! Data length !! Codec ID !! NOD1 !! AVL DATA !! NOD2 !! CRC16
+
|-
+
| 4 bytes || 4 bytes || 0x10 || 1B || Variable || 1B || 4 Bytes
+
|}
+
+
NOD1, NOD2 – number of data (number of packed records)
+
+
Codec ID – constant 0x10.
+
+
Data length – the length of packet from CodecID to NOD2.
+
+
NOD2 should be equal to NOD1.
+
+
CRC16 is 4 bytes, but first two are zeroes and last two are CRC-16 calculated for CodecID to NOD2.
Mariusandruska
0
edits
Navigation menu
COMMUNITY
ABOUT
login
Personal tools
Log in
Create account
EN
EN
LT
DE
IT
ES
FR
RU
PL
PT
BR
JA
TR
NAVIGATION
Recent changes
Random page
What links here
Upload file
Help
Tools
Categories
Advanced Trackers
Professional Trackers
Accessories
General Information
Autonomous Trackers
Basic Trackers
CAN Trackers & Adapters
E-Mobility Trackers
EOL Products
Fast & Easy Trackers
Frequently Asked Questions - FAQ
OBD Trackers
Sensors
Software & Applications
Video Solutions
Mobility FAQ