EDVADO DOT · binary protocol

DOT parameter reference

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

264 · parameters

Open a row to see its values and example.

Format: TAG = uint8 + 4 B · little-endian

Power and main parameters1

TAG 0x01External voltage in mV Internal voltage (battery) in mVmV

The source is ambiguous here. Do not infer the missing layout, range or device support.

Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I16:N16

Values and interpretation

External supply and battery are separate unsigned 16-bit millivolt values. Divide a valid value by 1000 to obtain volts. Battery 0 means disconnected; 65535 means battery-management error.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

CAN measurements18

TAG 0x32CAN program and version—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I65:N65

Values and interpretation

Program number and CAN version are packed into 4 bytes: program, patch, minor version, major version.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x34Total engine operating timeh
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I67:N67

Values and interpretation

Raw engine operating time is stored in hundredths of an hour. Divide by 100; this is accumulated time, not clock time. max(raw) = 99999999

Interpretation example

2569835 / 100 = 25698.35 h → accumulated engine time

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x35Total mileagekm
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I68:N68

Values and interpretation

Raw accumulated distance is stored in hundredths of a kilometer. Divide by 100; this is total mileage, not trip distance. max(raw) = 999999999

Interpretation example

123456 / 100 = 1234.56 km → accumulated vehicle distance

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x36Total fuel consumedL
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I69:N69

Values and interpretation

Raw accumulated fuel consumption is stored in tenths of a liter. Divide by 10; this is consumption, not remaining fuel. max(raw) = 99999999

Interpretation example

1250 / 10 = 125 L → accumulated fuel consumption

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x37Fuel level%
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I70:N70

Values and interpretation

Raw fuel level is stored in tenths of a percent. Divide by 10. The documented maximum raw value is 1000, corresponding to 100%. max(raw) = 1000

Interpretation example

184 / 10 = 18.4% → fuel tank level 18.4%

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x38Fuel volumeL
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I71:N71

Values and interpretation

Raw fuel volume is stored in tenths of a liter. Divide by 10. Do not use a percentage calibration for this field. max(raw) = 1000

Interpretation example

425 / 10 = 42.5 L → fuel remaining

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x39Engine speedrpm
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I72:N72

Values and interpretation

Not specified in the source; do not assume a unit or range.

Interpretation example

1000 → 1000 rpm

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x3AEngine temperature°C
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I73:N73

Values and interpretation

raw ≤ 1000: T = raw °C raw > 1000: T = −(raw − 1000) °C

↳

raw = 1020 → −20 °C

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x3BVehicle speedkm/h
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I74:N74

Values and interpretation

Not specified in the source; do not assume a unit or range.

Interpretation example

50 → 50 km/h

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x3CAxle 1 loadkg
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I75:N75

Values and interpretation

CAN - pressure on the axle 1 (kg)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x3DAxle 2 loadkg
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I76:N76

Values and interpretation

CAN - pressure on the axle 2 (kg)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x3EAxle 3 loadkg
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I77:N77

Values and interpretation

CAN - pressure on the axle 3 (kg)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x43Exhaust fluid level%
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I82:N82

Values and interpretation

Raw exhaust-treatment fluid level is stored in tenths of a percent. Divide by 10; this is not a fuel measurement. max(raw) = 1000

Interpretation example

127 / 10 = 12.7% → exhaust-treatment fluid level

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x45Accelerator pedal position / Engine load%
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I84:N84

Values and interpretation

byte[0]: Accelerator pedal position (%) byte[1]: Engine load (%) cfm17 · cfm19 · cfm20 · cfm21 · cfm22 · cfm23 · cfm24 · cfm25 · cfm26 · cfm27 · cfm29 · cfm30

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x65Tachograph speedkm/h
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I117:N117

Values and interpretation

v = raw / 256 km/h

↳

0x0548 = 1352 → 5.28125 km/h

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x67Tachograph states—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I119:N119

Values and interpretation

0-2 bit - Driver Activity: 0-rest, 1-free, 2-work, 3-driving, 4-7 - Reserve 3-5 bits - the state of the driver card: 0-unknown, 1 - not authorized, 2 - authorized, 3 - failed to extract, 4-7 - Reserve 6-8 bits - partner Activity: 0-rest, 1-free, 2-work, 3-driving, 4-7 - Reserve 9-11 bits - the state of the card team-mate: 0-unknown, 1 - not authorized, 2 - authorized, 3 - failed to extract, 4-7 - Reserve Bit 16 - Ignition: 0 - off, 1 - on bit 17: The source is ambiguous here. Do not infer the missing layout, range or device support. 18 bit - mode "ferry / train": 0, not activated, 1 is activated 19 bit - mode "not applicable": 0, not activated, 1 is activated

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x69Card number: upper part—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I121:N121

Values and interpretation

24-31bit - country code. 0x2B - RU 21-23bit - Card Type: 0 = Driver (D), 1 = Master (M), 2 = Controller (K), 3 = Enterprise (P) 15-20bit - The index of the replacement card. Set to 0 to 9, then - from A to Z. 9-14bit - Index map updates. Set to 0 to 9, then - from A to Z. For card type 0: 0-8bit bits - Bits 32-41 card number For cards like 1,2,3: 3-8bit bit - index cards. Set to 0 to 9, then - from A to Z. 0-2bit bits - Bits 32-34 card number [bits 0:8 → 32:41] The source is ambiguous here. Do not infer the missing layout, range or device support.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x6BCard number: upper part—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I123:N123

Values and interpretation

24-31bit - country code. 0x2B - RU 21-23bit - Card Type: 0 = Driver (D), 1 = Master (M), 2 = Controller (K), 3 = Enterprise (P) 15-20bit - The index of the replacement card. Set to 0 to 9, then - from A to Z. 9-14bit - Index map updates. Set to 0 to 9, then - from A to Z. For card type 0: 0-8bit bits - Bits 32-41 card number For cards like 1,2,3: 3-8bit bit - index cards. Set to 0 to 9, then - from A to Z. 0-2bit bits - Bits 32-34 card number [bits 0:8 → 32:41] The source is ambiguous here. Do not infer the missing layout, range or device support.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

CAN signals50

cff0Remote locking event—
Format: TAG 0x33 · bit 0Link to parameterProtocol · sheet Tags · I66:N66

Event indication from the vehicle. Interpret it as a reported event, not as a persistent lock position.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Remote locking event

Interpretation example

cff0 = 1 → Remote locking event

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff1Remote unlocking event—
Format: TAG 0x33 · bit 1Link to parameterProtocol · sheet Tags · I66:N66

Event indication from the vehicle. Interpret it as a reported event, not as a persistent lock position.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Remote unlocking event

Interpretation example

cff1 = 1 → Remote unlocking event

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff2Remote trunk opening event—
Format: TAG 0x33 · bit 2Link to parameterProtocol · sheet Tags · I66:N66

Event indication from the vehicle. Interpret it as a reported event, not as a persistent lock position.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Remote trunk opening event

Interpretation example

cff2 = 1 → Remote trunk opening event

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff6CAN module sleep state—
Format: TAG 0x33 · bit 6Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. CAN module sleep state

Interpretation example

cff6 = 1 → CAN module sleep state

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff8Driver door open—
Format: TAG 0x33 · bit 8Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Driver door open

Interpretation example

cff8 = 1 → Driver door open

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff9Passenger door open—
Format: TAG 0x33 · bit 9Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Passenger door open

Interpretation example

cff9 = 1 → Passenger door open

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff10Trunk open—
Format: TAG 0x33 · bit 10Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Trunk open

Interpretation example

cff10 = 1 → Trunk open

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff11Engine hood open—
Format: TAG 0x33 · bit 11Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Engine hood open

Interpretation example

cff11 = 1 → Engine hood open

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff12Parking brake applied—
Format: TAG 0x33 · bit 12Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Parking brake applied

Interpretation example

cff12 = 1 → Parking brake applied

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff13Brake pedal pressed—
Format: TAG 0x33 · bit 13Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Brake pedal pressed

Interpretation example

cff13 = 1 → Brake pedal pressed

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff14Engine running—
Format: TAG 0x33 · bit 14Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Engine running

Interpretation example

cff14 = 1 → Engine running

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff16Ignition on—
Format: TAG 0x33 · bit 16Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Ignition on

Interpretation example

cff16 = 1 → Ignition on

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff17Factory alarm state—
Format: TAG 0x33 · bit 17Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Factory alarm state

Interpretation example

cff17 = 1 → Factory alarm state

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff19Key in ignition—
Format: TAG 0x33 · bit 19Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Key in ignition

Interpretation example

cff19 = 1 → Key in ignition

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff20Dynamic lighting signal—
Format: TAG 0x33 · bit 20Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Dynamic lighting signal

Interpretation example

cff20 = 1 → Dynamic lighting signal

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff21Front passenger door open—
Format: TAG 0x33 · bit 21Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Front passenger door open

Interpretation example

cff21 = 1 → Front passenger door open

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cff22Rear doors open—
Format: TAG 0x33 · bit 22Link to parameterProtocol · sheet Tags · I66:N66

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Rear doors open

Interpretation example

cff22 = 1 → Rear doors open

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa6Passenger seat belt indicator—
Format: TAG 0x41 · bit 6Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Passenger seat belt indicator

Interpretation example

cfa6 = 1 → Passenger seat belt indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa7Driver seat belt indicator—
Format: TAG 0x41 · bit 7Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Driver seat belt indicator

Interpretation example

cfa7 = 1 → Driver seat belt indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa8Electronic stability indicator—
Format: TAG 0x41 · bit 8Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Electronic stability indicator

Interpretation example

cfa8 = 1 → Electronic stability indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa9Glow plug indicator—
Format: TAG 0x41 · bit 9Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Glow plug indicator

Interpretation example

cfa9 = 1 → Glow plug indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa10Particulate filter indicator—
Format: TAG 0x41 · bit 10Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Particulate filter indicator

Interpretation example

cfa10 = 1 → Particulate filter indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa11Electronic pressure regulation indicator—
Format: TAG 0x41 · bit 11Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Electronic pressure regulation indicator

Interpretation example

cfa11 = 1 → Electronic pressure regulation indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa12Position lights indicator—
Format: TAG 0x41 · bit 12Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Position lights indicator

Interpretation example

cfa12 = 1 → Position lights indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa13Low beam indicator—
Format: TAG 0x41 · bit 13Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Low beam indicator

Interpretation example

cfa13 = 1 → Low beam indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa14High beam indicator—
Format: TAG 0x41 · bit 14Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. High beam indicator

Interpretation example

cfa14 = 1 → High beam indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa18Low tire pressure indicator—
Format: TAG 0x41 · bit 18Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Low tire pressure indicator

Interpretation example

cfa18 = 1 → Low tire pressure indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa19Brake pad wear indicator—
Format: TAG 0x41 · bit 19Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Brake pad wear indicator

Interpretation example

cfa19 = 1 → Brake pad wear indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa20Warning indicator—
Format: TAG 0x41 · bit 20Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Warning indicator

Interpretation example

cfa20 = 1 → Warning indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa21Anti-lock braking indicator—
Format: TAG 0x41 · bit 21Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Anti-lock braking indicator

Interpretation example

cfa21 = 1 → Anti-lock braking indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa22Low fuel indicator—
Format: TAG 0x41 · bit 22Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Low fuel indicator

Interpretation example

cfa22 = 1 → Low fuel indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa24STOP indicator—
Format: TAG 0x41 · bit 24Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. STOP indicator

Interpretation example

cfa24 = 1 → STOP indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa25Oil pressure or level indicator—
Format: TAG 0x41 · bit 25Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Oil pressure or level indicator

Interpretation example

cfa25 = 1 → Oil pressure or level indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa26Coolant temperature or level indicator—
Format: TAG 0x41 · bit 26Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Coolant temperature or level indicator

Interpretation example

cfa26 = 1 → Coolant temperature or level indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa27Brake system indicator—
Format: TAG 0x41 · bit 27Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Brake system indicator

Interpretation example

cfa27 = 1 → Brake system indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa28Battery charging indicator—
Format: TAG 0x41 · bit 28Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Battery charging indicator

Interpretation example

cfa28 = 1 → Battery charging indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfa29Airbag indicator—
Format: TAG 0x41 · bit 29Link to parameterProtocol · sheet Tags · I80:N80

Indicator reported by the vehicle controller. A set bit identifies the named indication; it is not an independent diagnosis.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Airbag indicator

Interpretation example

cfa29 = 1 → Airbag indicator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm17Low water level—
Format: TAG 0x45 · bit 17Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Low water level

Interpretation example

cfm17 = 1 → Low water level

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm19Auxiliary engine running—
Format: TAG 0x45 · bit 19Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Auxiliary engine running

Interpretation example

cfm19 = 1 → Auxiliary engine running

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm20Joystick right—
Format: TAG 0x45 · bit 20Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Joystick right

Interpretation example

cfm20 = 1 → Joystick right

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm21Joystick left—
Format: TAG 0x45 · bit 21Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Joystick left

Interpretation example

cfm21 = 1 → Joystick left

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm22Joystick forward—
Format: TAG 0x45 · bit 22Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Joystick forward

Interpretation example

cfm22 = 1 → Joystick forward

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm23Joystick backward—
Format: TAG 0x45 · bit 23Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Joystick backward

Interpretation example

cfm23 = 1 → Joystick backward

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm24Brush enabled—
Format: TAG 0x45 · bit 24Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Brush enabled

Interpretation example

cfm24 = 1 → Brush enabled

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm25Water supply enabled—
Format: TAG 0x45 · bit 25Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Water supply enabled

Interpretation example

cfm25 = 1 → Water supply enabled

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm26Vacuum system signal—
Format: TAG 0x45 · bit 26Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Vacuum system signal

Interpretation example

cfm26 = 1 → Vacuum system signal

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm27Hopper unloading—
Format: TAG 0x45 · bit 27Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Hopper unloading

Interpretation example

cfm27 = 1 → Hopper unloading

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm29Salt or sand spreading enabled—
Format: TAG 0x45 · bit 29Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Salt or sand spreading enabled

Interpretation example

cfm29 = 1 → Salt or sand spreading enabled

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfm30Low salt or sand level—
Format: TAG 0x45 · bit 30Link to parameterProtocol · sheet Tags · I84:N84

Equipment state reported by the CAN controller. Availability depends on the installed equipment and CAN program.

Values and interpretation

  • 0named signal is not asserted.
  • 1named signal is asserted. Low salt or sand level

Interpretation example

cfm30 = 1 → Low salt or sand level

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x41CAN · cfa—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I80:N80

Values and interpretation

cfa6 · cfa7 · cfa8 · cfa9 · cfa10 · cfa11 · cfa12 · cfa13 · cfa14 · cfa18 · cfa19 · cfa20 · cfa21 · cfa22 · cfa24 · cfa25 · cfa26 · cfa27 · cfa28 · cfa29

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

Module states32

DS2[28:30]Wi-Fi module and network state—
Format: TAG 0x63 · 3 bitLink to parameterProtocol · sheet Tags · I262:N262

Wi-Fi state in DOT DS2, bits 28–30. Extract the three-bit field from the status word before using the enumerated values.

Values and interpretation

  • 0module not found
  • 1module found
  • 2network not found
  • 3searching for network
  • 4network found
  • 5connecting
  • 6connected.

Interpretation example

DS2 [28–30] = 6

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

nav_stDS2 · nav_st—
Format: TAG 0x63 · bits 0:1Link to parameterProtocol · sheet Tags · I233:N233

Values and interpretation

0: Disabled 1: Enabled 2: Enabled, NMEA OK, searching for satellites 3: 3D fix

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

gsm_stDS2 · gsm_st—
Format: TAG 0x63 · bits 2:4Link to parameterProtocol · sheet Tags · I235:N235

Values and interpretation

0: Disabled 1: Enabled 2: AT OK 3: GPRS activation 4: GPRS OK on the active SIM 5: Reserved 6: Reserved 7: Reserved

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

sim_tDS2 · sim_t—
Format: TAG 0x63 · bits 5:5Link to parameterProtocol · sheet Tags · I238:N238

Values and interpretation

0: SIM1 1: SIM2

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

sim1_stDS2 · sim1_st—
Format: TAG 0x63 · bits 6:8Link to parameterProtocol · sheet Tags · I239:N239

Values and interpretation

0: No SIM card 1: Registering to home network 2: Searching for network 3: Registration rejected 4: Reserved 5: Roaming registration 6: PIN ERROR 7: Reserved

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

sim2_stDS2 · sim2_st—
Format: TAG 0x63 · bits 9:11Link to parameterProtocol · sheet Tags · I242:N242

Values and interpretation

0: No SIM card 1: Registering to home network 2: Searching for network 3: Registration rejected 4: Reserved 5: Roaming registration 6: PIN ERROR 7: Reserved

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

S0_stDS2 · S0_st—
Format: TAG 0x63 · bits 12:13Link to parameterProtocol · sheet Tags · I245:N245

Values and interpretation

0: Not used / CLOSED 1: CONNECTING 2: Connection established / CONNECT OK 3: Logged in to the server

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

S1_stDS2 · S1_st—
Format: TAG 0x63 · bits 14:15Link to parameterProtocol · sheet Tags · I247:N247

Values and interpretation

0: Not used / CLOSED 1: CONNECTING 2: Connection established / CONNECT OK 3: Logged in to the server

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

S2_stDS2 · S2_st—
Format: TAG 0x63 · bits 16:17Link to parameterProtocol · sheet Tags · I249:N249

Values and interpretation

0: Not used / CLOSED 1: CONNECTING 2: Connection established / CONNECT OK 3: Logged in to the server

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

S3_stDS2 · S3_st—
Format: TAG 0x63 · bits 18:19Link to parameterProtocol · sheet Tags · I251:N251

Values and interpretation

0: Not used / CLOSED 1: CONNECTING 2: Connection established / CONNECT OK 3: Logged in to the server

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

mwDS2 · mw—
Format: TAG 0x63 · bits 20:21Link to parameterProtocol · sheet Tags · I254:N254

Values and interpretation

0: Parked 1: Driving 2: Error 3: Self-test error

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

osDS2 · os—
Format: TAG 0x63 · bits 22:22Link to parameterProtocol · sheet Tags · I256:N256

Values and interpretation

Tamper sensor / BLE tag: 0 closed / absent; 1 open / present. Meaning depends on device configuration.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

msdDS2 · msd—
Format: TAG 0x63 · bits 23:24Link to parameterProtocol · sheet Tags · I257:N257

Values and interpretation

0: Absent 1: Present 2: Error 3: Reserved

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

BTDS2 · BT—
Format: TAG 0x63 · bits 25:25Link to parameterProtocol · sheet Tags · I259:N259

Values and interpretation

0: Disabled 1: Enabled

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

gyroDS2 · gyro—
Format: TAG 0x63 · bits 26:27Link to parameterProtocol · sheet Tags · I260:N260

Values and interpretation

0: Disabled 1: Enabled 2: Error 3: Not specified in the protocol

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[0]Inner memory—
Format: bit fieldLink to parameterProtocol · sheet Tags · I494:N494

Values and interpretation

0 = No settings; 1 = Settings OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[1]External Memory—
Format: bit fieldLink to parameterProtocol · sheet Tags · I495:N495

Values and interpretation

0 = issue; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[2]Real Time Clock—
Format: bit fieldLink to parameterProtocol · sheet Tags · I496:N496

Values and interpretation

0 = issue; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[3]powered modem—
Format: bit fieldLink to parameterProtocol · sheet Tags · I497:N497

Values and interpretation

0 = off; 1 = included

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[4]modem status—
Format: bit fieldLink to parameterProtocol · sheet Tags · I498:N498

Values and interpretation

0 = no; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[5]GSM AT command—
Format: bit fieldLink to parameterProtocol · sheet Tags · I499:N499

Values and interpretation

0 = not responding; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[6]SIM card—
Format: bit fieldLink to parameterProtocol · sheet Tags · I500:N500

Values and interpretation

0 = not inserted; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[7]SIM PIN—
Format: bit fieldLink to parameterProtocol · sheet Tags · I501:N501

Values and interpretation

0 = activated; 1 = not activated

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[8]PIN check—
Format: bit fieldLink to parameterProtocol · sheet Tags · I502:N502

Values and interpretation

0 = issue; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[9]power module GPS / Glonass—
Format: bit fieldLink to parameterProtocol · sheet Tags · I503:N503

Values and interpretation

0 = off; 1 = included

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[10]Module GPS / Glonass—
Format: bit fieldLink to parameterProtocol · sheet Tags · I504:N504

Values and interpretation

0 = NO_NMEA; 1 = NMEA OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[11]Motion Sensor—
Format: bit fieldLink to parameterProtocol · sheet Tags · I505:N505

Values and interpretation

0 = not fixed; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[12]speed NMEA—
Format: bit fieldLink to parameterProtocol · sheet Tags · I506:N506

Values and interpretation

0: 9600 baud 1: 115200 baud

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[13]Number current SIM Card—
Format: bit fieldLink to parameterProtocol · sheet Tags · I507:N507

Values and interpretation

0- primary, 1 - secondary

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[16]SIM card 2—
Format: bit fieldLink to parameterProtocol · sheet Tags · I510:N510

Values and interpretation

0 = not inserted; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[17]SIM PIN 2—
Format: bit fieldLink to parameterProtocol · sheet Tags · I511:N511

Values and interpretation

0 = activated; 1 = not activated

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

module-status[18]PIN Check 2—
Format: bit fieldLink to parameterProtocol · sheet Tags · I512:N512

Values and interpretation

0 = issue; 1 = OK

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

Fuel and sensors10

TAG 0x47LLS_1—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I86:N86

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x48LLS_2—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I87:N87

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x49LLS_3—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I88:N88

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x4ALLS_4—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I89:N89

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x4BLLS_5—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I90:N90

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x4CLLS_6—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I91:N91

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x4DLLS_7—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I92:N92

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x4ELLS_8—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I93:N93

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x4FLLS_9—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I94:N94

Values and interpretation

Relative fuel level and temperature. The source does not specify the byte layout for this channel; do not infer the LLS_0 battery field.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x46 · LLS_0Relative level, temperature and battery°C · V
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I85:N85

Values and interpretation

Bytes 0–1: relative level; for a temperature sensor, circuit state (0 closed, 1 open), or illumination level. Byte 2: signed temperature. Byte 3: BLE sensor battery voltage × 10. A relative level is not a volume in liters.

↳

byte[2] = 0xA0 → −96 °C byte[3] = 36 → 3.6 V

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

Navigation4

TAG 0x03Latitude°
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I18:N18

Values and interpretation

IEEE 754 float32, degrees. Positive: north; negative: south. Invalid coordinates are not transmitted.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x04Longitude°
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I19:N19

Values and interpretation

IEEE 754 float32, degrees. Positive: east; negative: west. Invalid coordinates are not transmitted.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x05speed (high byte) satellites altitude course (least significant byte)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I20:N20

Values and interpretation

0x08 = 8 * 1.852 = 14.81 km / h above the speed in knots 0xE7 = 0-3 bits - the number of GPS (0-15) 7 (0x07) satellites 4-7 bits - the number of Glonass (0-15) 14 (0x0E) satellites, the total number of satellites 21 (0xFE - LBS position, 0xFF - WiFi position) 0x19 = 25 * 10 = 250 m altitude in meters / 10 0x11 = 17 * 2 = azimuth multiplied by 2

Interpretation example

05 11 19 E7 08

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x97Dilution of Precision1
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I143:N143

Values and interpretation

Bit 0-15 - hdop, multiplied by 100 Bit 16-31 - reserved

Interpretation example

97 C3 05 00 00

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

Inputs and outputs25

TAG 0x06PIN · IMPS_x · FREQ_x · VOLT_x—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I21:N21

Values and interpretation

byte[0]: 0x06 IMPS · 0x07 FREQ (Hz) · 0x08 VOLT (mV) · 0x01 PIN byte[1]: PIN n byte[2:3]: uint16 0x01: byte[1].bit0 → Ignition; byte[1].bit1 → Call button Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x0AIMPS_0—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I25:N25

Values and interpretation

Number of pulses per IN_0

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x0BIMPS_1—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I26:N26

Values and interpretation

Number of pulses per IN_1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x0CIMPS_2—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I27:N27

Values and interpretation

Number of pulses per IN_2

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x0DIMPS_3—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I28:N28

Values and interpretation

Number of pulses per IN_3

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x0EIMPS_4—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I29:N29

Values and interpretation

Number of pulses per IN_4

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x0FIMPS_5—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I30:N30

Values and interpretation

Number of pulses per IN_5

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x10IMPS_6—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I31:N31

Values and interpretation

Number of pulses per IN_6

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x11IMPS_7—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I32:N32

Values and interpretation

Number of pulses per IN_7

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x14FREQ_0Hz
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I35:N35

Values and interpretation

Frequency on IN_0

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x15FREQ_1Hz
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I36:N36

Values and interpretation

Frequency on IN_1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x16FREQ_2Hz
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I37:N37

Values and interpretation

Frequency on IN_2

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x17FREQ_3Hz
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I38:N38

Values and interpretation

Frequency on IN_3

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x18FREQ_4Hz
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I39:N39

Values and interpretation

Frequency on IN_4

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x19FREQ_5Hz
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I40:N40

Values and interpretation

Frequency on IN_5

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x1AFREQ_6Hz
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I41:N41

Values and interpretation

Frequency on IN_6

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x1BFREQ_7Hz
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I42:N42

Values and interpretation

Frequency on IN_7

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x1EVOLT_0mV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I45:N45

Values and interpretation

VOLT_0 · mV V = raw / 1000

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x1FVOLT_1mV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I46:N46

Values and interpretation

VOLT_1 · mV V = raw / 1000

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x20VOLT_2mV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I47:N47

Values and interpretation

VOLT_2 · mV V = raw / 1000

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x21VOLT_3mV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I48:N48

Values and interpretation

VOLT_3 · mV V = raw / 1000

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x22VOLT_4mV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I49:N49

Values and interpretation

VOLT_4 · mV V = raw / 1000

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x23VOLT_5mV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I50:N50

Values and interpretation

VOLT_5 · mV V = raw / 1000

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x24VOLT_6mV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I51:N51

Values and interpretation

VOLT_6 · mV V = raw / 1000

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x25VOLT_7mV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I52:N52

Values and interpretation

VOLT_7 · mV V = raw / 1000

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

Virtual and additional sensors24

TAG 0xBEVirtual and additional sensors—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I171:N171

Values and interpretation

uint8 n + uint24 value Not specified in the protocol

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_12EcoDrive (only for L, A series)—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I557:N557

Values and interpretation

acceleration thresholds and events bit 6 - Navigation Antenna Orientation Error bit 5 - Exceeding the permissible deviation of the tracker axes bit 4 - Exceeding the threshold of permissible speed bit 3 - Exceeding the threshold of vertical accelerations bit 2 - Exceeding the threshold of lateral accelerations bit 1 - Exceeding the threshold during deceleration bit 0 - Exceeding the threshold during acceleration

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_13Visibility status of BLE sensors (only for L, A series)—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I558:N558

Values and interpretation

bit 7 - mac 4 bit 6 - mac 3 bit 5 - mac 2 bit 4 - mac 1 1 - online, 0 - offline

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_14wireless relays state bits—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I559:N559

Values and interpretation

1 - activated, 0 - deactivated

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_19Positioning information—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I561:N561

Values and interpretation

byte 0 - coordinate source: 0 - no coordinate 1 - satts 2 - locator 3 - geotag

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_49Service flags—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I581:N581

Values and interpretation

Black box status: 0 - space available, 1 - overflow bit 0 - Monitoring server 1 ... bit 3 - Monitoring server 4

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_52Immo bypass system status—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I584:N584

Values and interpretation

52[0] - Vehicle status 0 bits 0.1 Central lock status (00 - no information; 01 - closed; 10 - open; 11 - closed and armed) bit 2 left front door open (1 - open, 0 - closed) bit 3 right front door open (1 - open, 0 - closed) bit 4 left rear door open (1 - open, 0 - closed) bit 5 right rear door open (1 - open, 0 - closed) bit 6 trunk open (1 - open, 0 - closed) bit 7 hood open (1 - open, 0 - closed) 52[1] - Vehicle status 1 bit 0 dimensions are enabled (1 - enabled, 0 - disabled). The status is transmitted with the support of the autorun module firmware bit 1 ignition on (key or autostart system) bit 2 engine running (1 - running, 0 - stopped) bit 3 transmission type (1 - automatic transmission/robot, 0 - manual transmission) bit 4 the transmission is not ready for autostart (1 - yes, 0 - no). Depending on the type of transmission: • Automatic transmission - the transmission is not parked; • robot—the transmission is not parked; • Manual transmission - logical neutral is not passed bit 5 the handbrake is not ready for autostart (1 - lowered - not ready, 0 - raised - ready). Depending on the type of transmission: • Automatic transmission—handbrake not raised; • robot—the handbrake is not raised; • Manual transmission - the handbrake is not raised when passing logical neutral bit 6 DRLs are enabled (1 - yes, 0 - no). The status is transmitted with the support of the autorun module firmware bit 7 Low beam is on (1 - yes, 0 - no). The status is transmitted with the support of the autorun module firmware 52[2] - Vehicle status 2 bit 0 engine immobilization active (1 - active, 0 - inactive) bit 1 Valet mode is enabled (1 - enabled, 0 - disabled) bit 2 seat belts are not fastened (1 - yes, 0 - no). Status transmitted with the support of the autorun module firmware bit 3 windows down (1 - yes, 0 - no). Status is transferred with support autorun module firmware bit 4 the interior light is on (1 - yes, 0 - no). The status is transferred when firmware support for autorun module bit 5 there is not enough washer fluid (1 - yes, 0 - no). The status is transferred when firmware support for autorun module bit 6 control output 1 (1 - enabled, 0 - disabled) bit 7 control output 2 (1 - enabled, 0 - disabled)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_54Immobilizer bypass system status—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I586:N586

Values and interpretation

54[0] - Status of the immo bypass system in normal message operation mode Data is buffered to avoid losses during active state changes 0x00 autostart disabled (impossible) 0x01 autostart enabled, engine not running 0x02 autostart process in progress 0x03 engine started as a result of autostart 0x04 the engine did not start after all attempts 0x05 autostart process stops engine stopped 0x06 autostart error, the engine was started but stopped 0x07 passing through the logical neutral 0xFF bootloader mode 54[1] - Cause of alarm message Installed when occurrence of an alarming event. Resets after end of the vehicle alarm. bit 0 accelerometer (1 - triggered, 0 - no triggered) [54.1 · bit 1] The source is ambiguous here. Do not infer the missing layout, range or device support. bit 2 left front door open (1 - open, 0 - closed) bit 3 right front door open (1 - open, 0 - closed) bit 4 left rear door open (1 - open, 0 - closed) bit 5 right rear door open (1 - open, 0 - closed) bit 6 trunk open (1 - open, 0 - closed) bit 7 hood open (1 - open, 0 - closed)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_55Immo bypass system status—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I587:N587

Values and interpretation

55[0] - 55[1] - Low-Endian format. Remaining engine operating time according to the autostart timer. Data is sent when the autorun procedure is started, repeated sending is carried out with a sampling rate of 8 seconds. If the engine starts without a timer, the value is 0xFFFF.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_56Immo bypass system status—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I588:N588

Values and interpretation

Econometric value (can bus)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_66Tachograph TCO1 FMS—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I596:N596

Values and interpretation

In example received value is 0x332211 LSByte 0x11 is Data Byte1, 0x22 - Data Byte2 and 0x33 (MSByte) - Data Byte 3 Data Byte 1: bits[6:7] - Vehicle motion (00 = Vehicle motion not detected, 01 = vehicle motion detected) bits[3:5] - Driv. 2 working state (000 = Rest, 001 = Driver available, 010 = Work, 011 = Drive, 110 = Error, 111 = not available bits[0:2] - Driv. 1 working state (000 = Rest, 001 = Driver available, 010 = Work, 011 = Drive, 110 = Error, 111 = not available Data Byte 2: bits[6:7] - Vehicle Overspeed (00 = No overspeed, 01 = Overspeed) bits[4:5] - Driver 1 card (00 = Card not present, 01= Card present) bits[0:3] - Driv. 1 time rel states (0000 = normal, 0001 = 15 min bef. 4 ½ h, 0010 = 4 ½ h reached, 0011 = 15 min bef. 9 h, 0100 = 9 h reached, 0101 = 15 min bef. 16 h, 0110 = 16h reached, 1110 = Error, 1111 = not available) Data Byte 3: bits[6:7] - don`t care bits[4:5] - Driver 2 card (00 = Card not present, 01= Card present) bits[0:3] - Driv. 2 time rel states (0000 = normal, 0001 = 15 min bef. 4 ½ h, 0010 = 4 ½ h reached, 0011 = 15 min bef. 9 h, 0100 = 9 h reached, 0101 = 15 min bef. 16 h, 0110 = 16h reached, 1110 = Error, 1111 = not available)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_67Tachograph DRIVER1_DRIVE_TIME—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I597:N597

Values and interpretation

minutes

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_68Tachograph DRIVER2_DRIVE_TIME—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I598:N598

Values and interpretation

minutes

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_69Tachograph DRIVER1_TOTAL_DRIVE_TIME—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I599:N599

Values and interpretation

minutes

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_70Tachograph DRIVER2_TOTAL_DRIVE_TIME—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I600:N600

Values and interpretation

minutes

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_71Tachograph DRIVER1_REST_TIME—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I601:N601

Values and interpretation

minutes

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_72Tachograph DRIVER2_REST_TIME—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I602:N602

Values and interpretation

minutes

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_73Tachograph DRIVER1_ACT_TIME—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I603:N603

Values and interpretation

minutes

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_74Tachograph DRIVER2_ACT_TIME—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I604:N604

Values and interpretation

minutes

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_86SPN100_ENGINE_OIL_PRESSURE—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I609:N609

Values and interpretation

kPa

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_91Accelerometer X-Axis (for A, L, A4, A4MAX, C4 series)—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I612:N612

Values and interpretation

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_92Accelerometer Y-Axis (for A, L, A4, A4MAX, C4 series)—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I613:N613

Values and interpretation

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VS_93Accelerometer Z-Axis (for A, L, A4, A4MAX, C4 series)—
Format: TAG 0xBE · uint8 + uint24Link to parameterProtocol · sheet Tags · I614:N614

Values and interpretation

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

VAL_xVirtual and additional sensors—
Format: bit fieldLink to parameterProtocol · sheet Tags · I182:N183

Four-byte additional fields: tags 210–219 carry special CAN data; tags 220–229 carry universal Bluetooth integration data. Units, scaling and meaning are defined by the selected function, not by the VAL_x code alone.

Values and interpretation

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

Protocol reference · 100
TAG 0x02ID key—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I17:N17

Values and interpretation

key i-Button (for example key number 0xAB563412)

Interpretation example

02 12 34 56 AB

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x07SIM CARD 1 LAC CID—

The source is ambiguous here. Do not infer the missing layout, range or device support.

Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I22:N22

Values and interpretation

LAC · CID · 2 × uint16 The source is ambiguous here. Do not infer the missing layout, range or device support.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x08SIM CARD 1 Signal level GSM (old. Byte) MCC (2 bytes) MNC (low byte)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I23:N23

Values and interpretation

Signal level: 0–31 (0x14 = 20). MCC is the country code of the base station: Russia 250, Ukraine 255, Belarus 257 (0x00FA = 250). MNC is the mobile network code (0x01 = 1).

Interpretation example

08 01 FA 00 14

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x09Device status (DS)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I24:N24

Values and interpretation

see Table. 2

Interpretation example

09 0C F0 84 63

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x29TEMP_1—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I56:N56

Values and interpretation

The temperature sensor (1-wire) T_1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x2ATEMP_2—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I57:N57

Values and interpretation

The temperature sensor (1-wire) T_2

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x2BTEMP_3—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I58:N58

Values and interpretation

The temperature sensor (1-wire) T_3

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x2CTEMP_4—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I59:N59

Values and interpretation

The temperature sensor (1-wire) T_4

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x2DTEMP_5—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I60:N60

Values and interpretation

The temperature sensor (1-wire) T_5

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x2ETEMP_6—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I61:N61

Values and interpretation

The temperature sensor (1-wire) T_6

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x2FTEMP_7—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I62:N62

Values and interpretation

The temperature sensor (1-wire) T_7

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x30TEMP_8—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I63:N63

Values and interpretation

The temperature sensor (1-wire) T_8

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x31TEMP_9—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I64:N64

Values and interpretation

The temperature sensor (1-wire) T_9

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x33CAN - can_security_state Flags Security Status - Bit-transmitted, for example: cff0..cff31—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I66:N66

Values and interpretation

cff0 · cff1 · cff2 · cff6 · cff8 · cff9 · cff10 · cff11 · cff12 · cff13 · cff14 · cff16 · cff17 · cff19 · cff20 · cff21 · cff22

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x42CAN - Status Flags agricultural equipment CAN_Agro Bit-transmitted, for example: cfs0..cfs31—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I81:N81

Values and interpretation

cfs0 - Threshing drum included (cfs0) cfs1 - Included unloading pipe cfs2 - Includes hydraulics cfs3 - including power PTO cfs4-7 reserve cfs8 - Excessive play under the threshing drum (cfs8) cfs9 - Open the entrance to the grain tank cfs10 - Grain Hopper 100% cfs11 - Grain Silo 70% cfs12 - Clogged filter hydraulic oil cfs13 - Low oil pressure of the hydraulic system cfs14 - Low hydraulic oil level cfs15 - Clogged filter hydraulic brakes cfs16 - Clogged engine oil filter (cfs16) cfs17 - Clogged fuel filter cfs18 - Clogged air filter cfs19 - Emergency oil temperature in the hydraulic suspension cfs20 - Emergency oil temperature in the hydraulic rams cfs21 - Emergency engine oil pressure cfs22 - Emergency coolant level cfs23 - overflow section of the hydraulic unit cfs24 - On unloading auger drive when folded. unloading. pipe (cfs24) cfs25 - no operator cfs26 - Clogging straw cfs27 - Presence of water in fuel cfs28 - Fan speed cleaning cfs29 - drum speed cfs30-31 - reserve

Interpretation example

42 09 12 14 22

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

cfs28 / cfs29: The source is ambiguous here. Do not infer the missing layout, range or device support.

TAG 0x44Exhaust fluid levelL
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I83:N83

Values and interpretation

multiplied by 10 (for example, actually 55.3 - 553 pass), the maximum value of 1000 max(raw) = 1000

Interpretation example

553 / 10 = 55.3 L

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x5BData on the maneuver / accident—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I107:N107

Values and interpretation

0-15 Bit - Maximum positive acceleration along the X axis for the period from the previous message in mg (int 16) Bits 16-31 - Maximum negative acceleration along the X axis for the period from the previous message in mg (int 16)

Interpretation example

5B 01 11 02 22

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x5CData on the maneuver / accident—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I108:N108

Values and interpretation

0-15 Bit - Reserved Bits 16-31 - Maximum angle acceleration value for the period from the previous message in mg (int 16)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x5DData on the maneuver / accident—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I109:N109

Values and interpretation

0-15 Bit - Maximum positive acceleration along the Z axis for the period from the previous message in mg (int 16) Bits 16-31 - Maximum negative acceleration along the Z axis for the period from the previous message in mg (int 16)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x5Ebalance of SIM1—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I110:N110

Values and interpretation

signed int

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x5Fbalance of SIM2—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I111:N111

Values and interpretation

signed int

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x60OBD Diagnostic Trouble Code (DTC)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I112:N112

Values and interpretation

0-3 Bit - fifth DTC character (0 - F) 4-7 Bit - fourth DTC character (0 - F) 8-11 Bit - third DTC character (0 - F) 12-13 Bit - second DTC character (0 - 3) 14-15 Bit - first DTC character (0 = P, 1 = C, 2 = B, 3 = U) 16-19 Bit - DTC type (3 = Stored, 7 = Pending, A = Permanent) 20-23 Bit - DTC source (0 = 7E8, 1 = 7E9, 2 = 7EA etc) 24-31 Bit - DTC id in tracker's table

Interpretation example

60 AB D3 7A 00

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x63DOT · DS2—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I115:N115

Values and interpretation

bits 0:1 · nav_st bits 2:4 · gsm_st bits 5:5 · sim_t bits 6:8 · sim1_st bits 9:11 · sim2_st bits 12:13 · S0_st bits 14:15 · S1_st bits 16:17 · S2_st bits 18:19 · S3_st bits 20:21 · mw bits 22:22 · os bits 23:24 · msd bits 25:25 · BT bits 26:27 · gyro bits 28:30 · Wi-Fi

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x64Mileage Tachographkm
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I116:N116

Values and interpretation

Mileage in kilometers multiplied by 100. (such as real 123.45 km - pass 12345)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x66Voltage TachographmV
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I118:N118

Values and interpretation

System voltage Tachograph in millivolts

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x68Number of cards in a card reader driver (junior section)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I120:N120

Values and interpretation

Bits 0-31 of the card number

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x6ANumber of cards in a card reader mate (junior section)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I122:N122

Values and interpretation

Bits 0-31 of the card number

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x6ECondition sensor G-Sensor—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I127:N127

Values and interpretation

Bit 0 - All the fields with information about the terminal and the vehicle properly filled Bit 1 - Status of self Bit 2 - Calibration Status Bit 3 - Reported maneuver the vehicle Bit 4 - Fixed an accident short Bit 5 - Fixed long road accidents Bit 6-7 Data bits Bit 8-15 Reserved Bit 16 - Sensor is determined, responding Bit 17-30 Reserved

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x6FData on the maneuver—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I128:N128

Values and interpretation

Bit 0-7 - type of maneuver: 1 - Accelerating 2 - Braking 3 - Left Turn 4 - The left turn with acceleration 5 - Left turn braking 6 - Left turn Wide 7 - Left wide turn with acceleration 8 - Left turn with wide braking 9 - Right turn 10 - Right turn acceleration 11 - Right turn braking 12 - Wide Right turn 13 - Right wide turn with acceleration 14 - Right turn with wide braking 15 - The circular movement 16 - Rebuilding 17 - Overtaking 18 - Bumps narrow 19 - Bumps wide Bit 8-15 - Degree field: 1 - Low 2 - Medium 3 - High Bit 16-31 - Time to maneuver in milliseconds

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x70Data on the maneuver / accident—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I129:N129

Values and interpretation

Bit 0-15 - The value of the X axis is transmitted in mg (int 16) Bits 16-31 of the Y-axis value is transmitted in mg (int 16)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x71Data on the maneuver / accident—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I130:N130

Values and interpretation

Bit 0-15 - The Z-value is transferred in mg (int 16) Bit 16-31 Reserved

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x72The data on road accidents—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I131:N131

Values and interpretation

Bit 0-15 - number of accidents Bit 16-23 - The direction of impact 1 Front 2 Rear 3 Side Bit 24-31 - The severity of the accident

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x76The data on road accidents—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I135:N135

Values and interpretation

Bit 0-7 - speed (EGTS) Bit 8-15 - course (EGTS) Bit 16-23 - Condition Vehicle during the accident: - 16-bit - state ignition - 17-bit - Driver Seat Belt Status - 18-bit - the state of the passenger belt - 19 bits - are valid coordinates of the accident - Bit 20 - speed above 255 km / h

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x82The data from the meter—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I139:N139

Values and interpretation

The volume of fuel in 0.01 liters, flowed through the flowmeter since the formation of the previous message (signed integer variable is 32 bits)

Interpretation example

82 22 11 00 00

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x83The data from the meter—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I140:N140

Values and interpretation

Bit 0-15 - The flow rate of 0.1 l / h. (symbolic variable short 16-bit) Bit 16-23 - the status of the sensor: -bit 16 Current mode: idle. -bit 17 Current mode: the nominal mode. -bit 18 current mode: Overload. -bit 19 Current mode: cheat. -bit 20 Current mode: negative. 21 -bit intervention. -bit 22 - 23 Not used. Bit 24-31 - number of sensor(0..255)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x96Odometr calculated. full mileage of vehicle (km) over satellite, multiplied by 100km
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I142:N142

Values and interpretation

Example: actual 25698.35 - pass 2569835, 999999999 max

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xC8SIM card 2 LAC CID—

The source is ambiguous here. Do not infer the missing layout, range or device support.

Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I172:N172

Values and interpretation

LAC · CID · 2 × uint16 The source is ambiguous here. Do not infer the missing layout, range or device support.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xC9SIM card 2 Signal level GSM (old. Byte) MCC (2 bytes) MNC (low byte)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I173:N173

Values and interpretation

Signal level: 0–31 (0x14 = 20). MCC is the country code of the base station: Russia 250, Ukraine 255, Belarus 257 (0x00FA = 250). MNC is the mobile network code (0x01 = 1).

Interpretation example

C9 01 FA 00 14

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xCAICCID sim card 2 [3 to 11 digits]—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I174:N174

Values and interpretation

ICCID (Integrated Circuit Card Id), the length of the ICCID - 20 digits the first 2 digits for SIM-cards are always 89 (not passed), unused last digits are filled by 0 ca e2 e1 2c 16 = 202 tag (iccid2p1) 0x162ce1e2 = 372040162 CB CC 6A 91 05 = 203 tag (iccid2p2) 0x05916acc = 093416140 89 + iccid2p1 + iccid2p2 = [IDENTIFIER]

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xFAInformational messages (for tracker)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I186:N186

Values and interpretation

TAG 0xFA

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

5 registration request unit

request sent

6 registration request unit

request has been successfully worked out

7 registration request unit

Error in query

8 registration request unit

Error in query

9 registration request unit

Not specified in the source; do not assume a unit or range.

10 query device settings

request sent

11 query device settings

request has been successfully worked out

12 query device settings

Error in query

13 query device settings

Error in query (the same settings)

14 query device settings

Not specified in the source; do not assume a unit or range.

15 request the current version

request sent

16 request the current version

request has been successfully worked out

17 request the current version

Error in query

18 request the current version

Error in query

19 request the current version

Not specified in the source; do not assume a unit or range.

20 request for a piece of firmware

request sent

21 request for a piece of firmware

request has been successfully worked out

22 request for a piece of firmware

Error in query (Bad SW version for HW)

23 request for a piece of firmware

Error in query

24 request for a piece of firmware

firmware is loaded successfully

25 transfer request settings

request sent

26 transfer request settings

request has been successfully worked out

27 transfer request settings

Error in query

28 transfer request settings

Error in query

29 transfer request settings

Not specified in the source; do not assume a unit or range.

30 confirmation

request sent

31 confirmation

request has been successfully worked out

32 confirmation

Error in query

33 confirmation

Error in query

34 confirmation

Not specified in the source; do not assume a unit or range.

35 querying the server

request sent

36 querying the server

request has been successfully worked out

37 querying the server

Error in query

38 querying the server

Error in query

39 querying the server

Not specified in the source; do not assume a unit or range.

60 Team registration

internal command

61 Team registration

a team from the server

62 Team registration

command via SMS

63 Team registration

team through the Viewer

64 Team registration

team call

70 command to update the device settings

internal command

71 command to update the device settings

a team from the server

72 command to update the device settings

command via SMS

73 command to update the device settings

team through the Viewer

74 command to update the device settings

team call

80 command to update the device software

internal command

81 command to update the device software

a team from the server

82 command to update the device software

command via SMS

83 command to update the device software

team through the Viewer

84 command to update the device software

team call

90 command to update the device software

Not specified in the source; do not assume a unit or range.

100 Device startup

Not specified in the source; do not assume a unit or range.

199 GeoZones

Not specified in the source; do not assume a unit or range.

200 MORE_LOADER_ERRORs

cancel update

201 MORE_WR / RD_ERRORs

cancel update

202 CRC_32 ERROR

cancel update

203 UpSetSt

update the configuration at each start

204 UpSetTime

re-set the interval

250 Error external navigation module

restart module

251 No NMEA

restart device

300 Time synchronization of GPS / Glonass

Not specified in the source; do not assume a unit or range.

301 synchronization of time through the configurator

Not specified in the source; do not assume a unit or range.

302 time synchronization with server monitoring

Not specified in the source; do not assume a unit or range.

303 load filter: Duplicate Time

Not specified in the source; do not assume a unit or range.

304 send a first valid position

Not specified in the source; do not assume a unit or range.

305 send last valid point

Not specified in the source; do not assume a unit or range.

306 By time interval in parking state

Not specified in the source; do not assume a unit or range.

307 worked condition of the distance

Not specified in the source; do not assume a unit or range.

308 The first point is valid after the start of the device

Not specified in the source; do not assume a unit or range.

309 NMEA packet loss from the module

Not specified in the source; do not assume a unit or range.

310 Error NMEA

restart device

311 The first coordinate is valid

Not specified in the source; do not assume a unit or range.

312 the latter is valid coordinate

Not specified in the source; do not assume a unit or range.

313 worked condition speed

Not specified in the source; do not assume a unit or range.

314 worked condition of the distance

Not specified in the source; do not assume a unit or range.

315 worked condition at a corner

Not specified in the source; do not assume a unit or range.

316 worked condition at zero speed

Not specified in the source; do not assume a unit or range.

317 Discrete input triggering

Not specified in the source; do not assume a unit or range.

318 Manifestation of parameter vs_12 (only for L and A-Series)

Not specified in the source; do not assume a unit or range.

319 Reset filters coordinate when sending to the server

Not specified in the source; do not assume a unit or range.

320 First message info

Not specified in the source; do not assume a unit or range.

321 GPS / GLONASS power short circuit detect

Not specified in the source; do not assume a unit or range.

322 On command 0101

Not specified in the source; do not assume a unit or range.

323 On command 010B

Not specified in the source; do not assume a unit or range.

325 Alternative positioning

Not specified in the source; do not assume a unit or range.

326 BLE sensor event

Not specified in the source; do not assume a unit or range.

327 The positioning source has changed

Not specified in the source; do not assume a unit or range.

400 Switching to parking mode

Not specified in the source; do not assume a unit or range.

401 Switching to sleep mode

Not specified in the source; do not assume a unit or range.

402 came out of sleep by the movement

Not specified in the source; do not assume a unit or range.

403 came out of sleep by the Timer

Not specified in the source; do not assume a unit or range.

404 came out of sleep when the external power was turned on. Voltage

Not specified in the source; do not assume a unit or range.

405 came out of sleep by the triggered input

Not specified in the source; do not assume a unit or range.

406 came out of sleep by the GPS / Glonass

Not specified in the source; do not assume a unit or range.

407 Start movenent

Not specified in the source; do not assume a unit or range.

409 Shock detected

Not specified in the source; do not assume a unit or range.

410 Tilt detected

Not specified in the source; do not assume a unit or range.

500 No response from the server

Not specified in the source; do not assume a unit or range.

501 No response from the server when you try again

Not specified in the source; do not assume a unit or range.

502 Error while sending data from the memory

Not specified in the source; do not assume a unit or range.

503 Error sending current data

Not specified in the source; do not assume a unit or range.

504 ER_HEADER

Not specified in the source; do not assume a unit or range.

505 ER_SERVER_ANS (0xFE)

Not specified in the source; do not assume a unit or range.

510 error in ADC

restart devices

511 error in the GSM

restart devices

512 error transmission data to the server

restart devices

513 inc_nmea

Not specified in the source; do not assume a unit or range.

514 write tempory settings

Not specified in the source; do not assume a unit or range.

515 Checksum error when sending packets

Not specified in the source; do not assume a unit or range.

516 switching between SIM cards

Not specified in the source; do not assume a unit or range.

517 RTC fail

Not specified in the source; do not assume a unit or range.

520 external power changed

Not specified in the source; do not assume a unit or range.

530 Cover Sensor Activated

Not specified in the source; do not assume a unit or range.

531 Successful command delivery to the device

Not specified in the source; do not assume a unit or range.

600 switched mode DEEP SLEEP

Deep Sleep mode (consumption 4-5 mA)

601 I emerged from DEEP SLEEP timer

signal transmission life

602 I emerged from DEEP SLEEP to change the inlet

transfer of disturbing messages

603 It emerged from DEEP SLEEP motion detected

Not specified in the source; do not assume a unit or range.

604 It emerged from DEEP SLEEP to change the input voltage

Not specified in the source; do not assume a unit or range.

610 MODBUS_RTU PACKET

Not specified in the source; do not assume a unit or range.

666 On command

restart devices

667 system error

restart devices

700 a request to upload a file from the tachograph .ddd

Not specified in the source; do not assume a unit or range.

701 .ddd start automatically upload the file over the interval

Not specified in the source; do not assume a unit or range.

702 .ddd file successfully vygruzhen around tachograph

Not specified in the source; do not assume a unit or range.

705 Invalid password authorization canister in the tachograph

Not specified in the source; do not assume a unit or range.

706 An error occurred when unloading from the tachograph

Not specified in the source; do not assume a unit or range.

707 card is removed during a file upload .ddd

Not specified in the source; do not assume a unit or range.

708 No card in the card reader or card is not authorized

Not specified in the source; do not assume a unit or range.

709 tachograph stopped responding (perhaps asleep)

Not specified in the source; do not assume a unit or range.

710 Driver Activity has changed

Not specified in the source; do not assume a unit or range.

800 G-sensor command response calibration

Not specified in the source; do not assume a unit or range.

850 External device firmware has been downloaded

Not specified in the source; do not assume a unit or range.

851 External device firmware has been updated

Not specified in the source; do not assume a unit or range.

852 An error occurred while external device updating

Not specified in the source; do not assume a unit or range.

853 An error occurred while downloading the external device firmware

Not specified in the source; do not assume a unit or range.

860 CAN sniffer started

Not specified in the source; do not assume a unit or range.

861 CAN autobaudrate ready

Not specified in the source; do not assume a unit or range.

862 log collect finished, file is full

Not specified in the source; do not assume a unit or range.

863 log collect finished, timeout

Not specified in the source; do not assume a unit or range.

865 CAN sniffer start fail

Not specified in the source; do not assume a unit or range.

866 CAN autobaudrate fail

Not specified in the source; do not assume a unit or range.

867 create CAN file fail

Not specified in the source; do not assume a unit or range.

868 save CAN file fail

Not specified in the source; do not assume a unit or range.

888 locator error

restart devices

1200 Change state of IN0

Not specified in the source; do not assume a unit or range.

1207 Change state of IN7

Not specified in the source; do not assume a unit or range.

1208 Change state of IN8 - 1-WIRE discrete mode (IN8 for A5)

Not specified in the source; do not assume a unit or range.

1209 Change state of IN9 - Sensor opening (IN9 for A5)

Not specified in the source; do not assume a unit or range.

1210 Ignition is ON

Not specified in the source; do not assume a unit or range.

1211 Ignition is OFF

Not specified in the source; do not assume a unit or range.

1212 Engine is ON

Not specified in the source; do not assume a unit or range.

1213 Engine is OFF

Not specified in the source; do not assume a unit or range.

TAG 0xFBDOT · HW / SW—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I188:N188

Values and interpretation

byte[0] = HW major byte[1] = HW minor byte[2] = SW major byte[3] = SW minor

↳

FB 08 02 01 2D → HW 8.2 · SW 1.45

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xFCDOT · HS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I189:N189

Values and interpretation

module-status[0] module-status[1] module-status[2] module-status[3] module-status[4] module-status[5] module-status[6] module-status[7] module-status[8] module-status[9] module-status[10] module-status[11] module-status[12] module-status[13] module-status[16] module-status[17] module-status[18]

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xFDICCID sim card 1 [3 to 11 digits] - iccid1p1—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I190:N190

Values and interpretation

ICCID (Integrated Circuit Card Id), the length of the ICCID - 20 digits the first 2 digits for SIM-cards are always 89 (not passed) [IDENTIFIER] printf(“ICCID1=89%09d%09d”, iccid1p1, iccid1p2) fd e2 e1 2c 16 (iccid1p1) 162ce1e2 = 372040162 fe cc 6a 91 05 (iccid1p2) 05916acc = 93416140

Interpretation example

fd e2 e1 2c 16

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xFFDevice ID—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I192:N192

Values and interpretation

unique device identifier (ID) in the WEB configurator

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[0]IN0—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I198:N198

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[1]IN1—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I199:N199

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[2]IN2—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I200:N200

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[3]IN3—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I201:N201

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[4]IN4—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I202:N202

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[5]IN5—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I203:N203

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[6]IN6—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I204:N204

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[7]IN7—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I205:N205

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[8]OUT0—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I206:N206

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[9]OUT1—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I207:N207

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[10]OUT2—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I208:N208

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[11]OUT3—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I209:N209

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[12:13]the state of the GSM modem—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I210:N210

Values and interpretation

0 - off, 1 - Registration in network 2 - comp. 3 server - replies from the server (standard)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[14:15]the state of GPS / Glonass module—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I212:N212

Values and interpretation

0 - off 1 - search for satellites, 2 - <8 satellites, 3 - more than 8 satellites (normal)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[16]Motion Sensor—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I214:N214

Values and interpretation

1 - motion is 0 - no movement

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[17]SIM card / SIM-chip—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I215:N215

Values and interpretation

1 - sim-chip 0 - sim-card

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[18]the presence of a SIM card / SIM-chip—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I216:N216

Values and interpretation

1 - insert, 0 - no

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[19]st0 - mode service / sensor opening—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I217:N217

Values and interpretation

mode (0 - monitoring, 1 - protection)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[20]st1 - SOS mode monitor / alarm mode protection / 1-wire discrete mode—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I218:N218

Values and interpretation

status of the alarm button (SOS) / alarm in the armed mode

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[21]st2 - Status of plugs—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I219:N219

Values and interpretation

ignition or ignition of the CAN virtual

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[22:23]Backup battery status—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I220:N220

Values and interpretation

00 - less than 3V or not connected, 01 - from 3V to 3.8 V, 10 - from 3.8V to 4.1V, 11 - more than 4.1V (normal)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS A[24:31]external voltage—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I222:N222

Values and interpretation

External voltage divided by 150 example: 0x54 = 84 * 150 = 12600 mV max. 38400 mV

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

The source is ambiguous here. Do not infer the missing layout, range or device support.

DS B[0]IN0 (−) / OUT0 (−)—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I641:N641

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS B[1]IN1 (+) · Ignition—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I642:N642

Values and interpretation

0 / 1

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS B[12:13]the state of the GSM modem—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I653:N653

Values and interpretation

0 - off, 1 - Registration in network 2 - comp. 3 server - replies from the server (standard)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS B[14:15]the state of GPS / Glonass module—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I655:N655

Values and interpretation

0 - off 1 - search for satellites, 2 - <8 satellites, 3 - more than 8 satellites (normal)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS B[16]Motion Sensor—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I657:N657

Values and interpretation

1 - motion is 0 - no movement

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS B[17]SIM card / SIM-chip—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I658:N658

Values and interpretation

1 - sim-chip 0 - sim-card

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS B[18]the presence of a SIM card / SIM-chip—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I659:N659

Values and interpretation

1 - insert, 0 - no

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

DS B[19:23]Backup battery voltage—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I660:N660

Values and interpretation

Internal voltage divided by 150 example: 0x1B = 27 * 150 = 4050 mV max. 4800 mV

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

The source is ambiguous here. Do not infer the missing layout, range or device support.

DS B[24]External voltage—

The protocol contains two DS layouts but does not specify a reliable selection rule. Decode only after the applicable layout is confirmed for the device.

Format: bit fieldLink to parameterProtocol · sheet Tags · I665:N665

Values and interpretation

External voltage divided by 150 example: 0x54 = 84 * 150 = 12600 mV max. 38400 mV

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x61SIM1 · Cell ID—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I113:N113

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x62SIM2 · Cell ID—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I114:N114

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x6CSerial number · 1/2—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I124:N124

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x6DSerial number · 2/2—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I125:N125

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x73Time of the accident (EGTS)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I132:N132

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x74Breadth DTP (EGCS)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I133:N133

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x75Longitude accident (EGTS)—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I134:N134

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x99device status—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I145:N145

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x9Abalance SIM1 and SIM2—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I146:N146

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA0MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I154:N154

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA1MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I155:N155

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA2MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I156:N156

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA3MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I157:N157

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA4MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I158:N158

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA5MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I159:N159

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA6MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I160:N160

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA7MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I161:N161

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA8MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I162:N162

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xA9MODBUS—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I163:N163

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xCCMAC BLE · TAG 204—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I176:N176

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xCDMAC BLE · TAG 205—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I177:N177

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xCFWi-Fi · A—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I179:N179

Values and interpretation

The purpose is named in the protocol, but the internal format, units or combination rule are not specified. Do not infer them from similar fields.

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0x28TEMP_0 · Temperature sensor°C
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I55:N55

Values and interpretation

T = (raw − 50000) / 100 °C raw: 0…100000 → −500…+500 °C raw = 111111 → Error

↳

47367 → −26.33 °C; 51655 → 16.55 °C

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xCBICCID · SIM2 · [12:20]—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I175:N175

Values and interpretation

uint32 · decimal[9] ICCID = 89 + decimal9(TAG 202) + decimal9(TAG 203)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.

TAG 0xFEICCID · SIM1 · [12:20]—
Format: 4 B · little-endianLink to parameterProtocol · sheet Tags · I191:N191

Values and interpretation

uint32 · decimal[9] ICCID = 89 + decimal9(TAG 253) + decimal9(TAG 254)

Definitions describe protocol fields, not universal device support. Availability depends on the DOT model, firmware and configuration.