Source cells

Description [EN]

Description of work [RU]

Bi-directional communication protocol: device -> server, server -> device.

Each parcel (PACKAGE) from the device requires confirmation from the server (SERVER_COM)

If there is no confirmation from the server, the device will duplicate packet until confirmation.

Data transmission to the server is in continuous TCP session (GPRS).

Data are transmitted in binary form, byte order little-endian.

The structure and procedure packs

ORDER OF TRANSMISSION

DEVICE >>

<< SERVER

first connection with the server transmitted HEADER - in response to confirmation HEADER further PACKAGE + SERVER_COM (confirmation)

HEADER

Heading

SERVER_COM

Server command

PACKAGE

Package

PACKET_0

Package_0

......

......

PACKET_N

Package_N

SERVER_COM

Server command

subsequent packets PACKAGE + SERVER_COM (confirmation)

PACKAGE

Package

PACKET_0

Package_0

.....

.....

PACKET_N

Package_N

SERVER_COM

Server command

asynchronous command Only a command (between packages PACKAGE)

SERVER_COM

Server command

HEADER - the structure of the title and description

order in byte

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

size bytes

example

FF

23

[ID BYTE]

[ID BYTE]

[ID BYTE]

[ID BYTE]

[ID BYTE]

[ID BYTE]

[ID BYTE]

[ID BYTE]

10-18

description fields

HEADER identificator

1

protocol version 0x22 - HEADER1 - don't support 0x23 - HEADER2 (GSM/GPRS) 0x24 - HEADER3 (EXT ID) 0x25 - HEADER2 (WIFI)

1

uniq ID (IMEI) ([IDENTIFIER] = [IDENTIFIER])

8

extended WIFI identifier, only for HEADER3 additional WIFI device identifier, only for Header3

8

description of work

transmitted once at each new initialization (connection) with the server, in response, the server should transmit an acknowledgment (cm. SERVER_COM)

job description

transmitted once for each new initialization (connection) with the server; in response, the server must send an acknowledgment (see Server commands)

PACKAGE - structure and description of the packages on the device

order in byte

0

1

N

2+N

size bytes

example

5B

01

01010101010101010101011

5D

3 + N

description fields

start sign PACKAGE

1

PACKAGE number from 0x01 to 0xFB

1

PACKET (one or more)

N

end sign PACKAGE

1.0

description of work

PACKET wrapper for transmission (1 or more). PACKAGE from 0x01 to 0xFB requires confirmation from the server (see. SERVER_COM)

job description

order in byte

0

1

2

3

Size bytes

example

5B

FD

00

5D

4

description fields

start sign PACKAGE

1

number is 0xFD

1

Answer code: 0x00 - OK, !0x00 - ERROR

1

end sign PACKAGE

1.0

description of work

PACKAGE 0xFD is an answer to server command type 0xFD (file transfer from server to device)

job description

PACKET - the structure and description of the packages on the device

order in byte

0

1

2

3

4

5

6

N=20

7+N

size bytes

example

01

14

00

E3

F1

6B

50

03298B5E4204CBD514420500191000080400FF02

1B

8 + N

description fields

type of content (0x01-DATA)

1

packet data length (length DATA)

2

unixtime 0x506BF1E3= 1349251555(unix time) = Wed, 03 Oct 2012 08:05:55 GMT

4

TAGs (DATA)

N

0x1B - checksum is calculated for all fields except the type and length of the packet.

1

description of work

PACKET DATA is a set of tags (Tags) (one or more) having the same time

job description

order in byte

0

1

2

3

4

5

6

N=4

7+N

size bytes

example

03

14

00

E3

F1

6B

50

text

C8

8 + N

description fields

type of content (0x03 - TEXT)

1

packet data length (length TEXT)

2

unixtime 0x506BF1E3= 1349251555(unix time) = Wed, 03 Oct 2012 08:05:55 GMT

4

TEXT

N

0xC8 - checksum it is sum of all bytes except the fields of type and length of the packet

1

description of work

PACKET TEXT is a text message, like answer to text command (message to driver)

job description

order in byte

0

1

2

3

4

5

6

7

8

9

10

N

7+N

size bytes

example

04

14

00

E3

F1

6B

50

00

02

00

00

34FA76EBB2AB434BABACE9015 ... .4034

C8

12 + N

description fields

type of content (0x04 - FILE)

1.0

packet data length (length DATA)

2.0

unixtime 0x506BF1E3= 1349251555(unix time) = Wed, 03 Oct 2012 08:05:55 GMT

4.0

The offset from the beginning of the file

4.0

FILE DATA

N

0xC8 - checksum it is sum of all bytes except the fields of type and length of the packet

1.0

description of work

If the offset = 0xFFFFFFFF, then the field FILE DATA contains the attributes of the file size, name and extension (type). Transfer of each new file starts at offset 0xFFFFFFFF

If the offset! = 0xFFFFFFFF, the FILE DATA field contains data to be written to the file at offset obtained in this variable

All packages FILE, belonging to the same file have the same time of the formation (unixtime)

FILE DATA field structure of the transmission attributes of a file:

job description

order in byte

t

is

s

t

d

d

d

example

0.0

7A

0.0

0.0

04

74

65

73

74

03

64

64

64

Size of file in bytes

The length of the file name

The file name to ASCII

The length of the file extension

The file extension to ASCII

order in byte

0

1

2

3

4

5

6

N=32

7+N

Size bytes

example

06

20

00

E3

F1

6B

50

03298B5E4204CBD514420500191000080400FF02

C8

8 + N

description fields

type of content (0x06 - DATA_BINARY)

1

packet data length (length DATA)

2

unixtime 0x506BF1E3= 1349251555(unix time) = Wed, 03 Oct 2012 08:05:55 GMT

4

DATA_BINARY

N

0xC8 - checksum it is sum of all bytes except the fields of type and length of the packet

1

description of work

PACKET DATA_BINARY is a binary data to be transmitted to server

job description

order in byte

0

1

2

3

4

5

6

N=32

7+N

Size bytes

example

08

20

00

E3

F1

6B

50

00

C8

8 + N

description fields

type of content (0x08 - CONFIRM_THE_COMMAND)

1

packet data length (length DATA)

2

unixtime 0x506BF1E3= 1349251555(unix time) = Wed, 03 Oct 2012 08:05:55 GMT

4

error code: 0 - no error

N

confirmed command

0xC8 - checksum it is sum of all bytes except the fields of type and length of the packet

1

description of work

CONFIRM_THE_COMMAND2 is used to inform server the command is received by device

job description

order in byte

0

1

2

3

4

5

6

7

8 9 10 11

12

Size bytes

example

09

05

00

E3

F1

6B

50

00

11 22 33 44

1B

13

description fields

type of content (0x09 - CONFIRM_THE_COMMAND BY TOKEN)

1

packet data length (length DATA)

2

unixtime 0x506BF1E3= 1349251555(unix time) = Wed, 03 Oct 2012 08:05:55 GMT

4

error code: 0 - no error 1 - unknown command 2 - too few arguments 3 - too many arguments 4 - invalid argument value 5 - command execution error 6 - command accepted but need time to execute (ACK) 7 - command queue overflow 8 - slave device not available 9 - slave device not responded after all trys

1

0x44332211 - token of confirmed command

4

0xC8 - checksum it is sum of all bytes except the fields of type and length of the packet

1

description of work

CONFIRM_THE_COMMAND is used to inform server the command is received by device

job description

order in byte

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

Size bytes

example

13

14

00

E3

F1

6B

50

E3

F1

6B

50

1B

00

SERVICE TEXT

1B

14 + N

description fields

type of content (0x13 - SERVICE TEXT)

1

packet data length (length TEXT)

2

unixtime 0x506BF1E3= 1349251555(unix time) = Wed, 03 Oct 2012 08:05:55 GMT

4

ID session time of the first PACKAGE

4

PACKAGE number

2

SERVICE TEXT

N

0x1B - checksum is calculated for all fields except the type and length of the packet.

1

description of work

SERVICE TEXT — debug information for transmission to WEB

job description

[EN]

Example (N VALUE)

TAG - structure and description of the packages on the device

order in byte

0

1

2

3

4

size bytes

example

01

0D

0D

0D

0D

5

description fields

variable number

1

variable

4

Each TAG has a fixed size of 5 bytes, of which the first byte indicates the number of variable (a total of 256 variables), the remaining 4 bytes - this variable (see. Table. 1). variable structure may be different, and the description of the method of packing is given for each variable

Table 1. Description 4-byte variable

Tag number

Title

Description

Example (N VALUE)

1.0

External voltage in mV Internal voltage (battery) in mV

the 2 bytes = external voltage 0x3054 = 12372 mV or second example 0x6B67 =27495 mV next 2 bytes = internal battery voltage 0x106E = 4206 mV or second example 0x0F80 = 3968 mV if value 0x00 - battery not connected if value 0xFFFF (65535) - error battery managment

01 6E 10 54 30 01 80 0F 67 6B (second example)

2.0

ID key

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

02 12 34 56 AB

3.0

Latitude

0x425E8B82 = 55,636238 latitude in IEEE 754 format (the floor. If the number N North, Neg. number, if S South) If coordinate is not valid - do not send them

03 82 8B 5E 42

4.0

Longitude

0x42167875 = 37,617633 longitude in IEEE 754 format (the floor If the number of E East, Neg. number, if W West) If coordinate is not valid - do not send them

04 75 78 16 42

5.0

speed (high byte) satellites altitude course (least significant byte)

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

05 11 19 E7 08

6.0

PINx - number of digital input, its mode value (NAME BEFORE THE VALUE IN DISPLAY ACCORDING TO INPUT MODE!)

06 06 01 12 01 => IMPS_1=274 [IMPS_x] 06 07 02 12 11 => FREQ_2=4370 [FREQ_x] 06 08 03 55 21 => VOLT_3=8533 [VOLT_x] 06 01 00 12 11 => PIN=0x1112. [PIN]

7.0

SIM CARD 1 LAC CID

Local Area Code - (first 2 B) 0xFF01 Cell ID - (next. 2 B) 0x1417

07 17 14 01 FF

8.0

SIM CARD 1 Signal level GSM (old. Byte) MCC (2 bytes) MNC (low byte)

level signal from 0 to 31, 0x14 = 20 Mobile Country Code - code of the country in which the BS (Russia it is 250, Ukraine - 255, Belarus - 257) 0x00FA = 250 Mobile Network Code - code for your network 0x01 = 1 (MTS - 01, MegaFon - 02, SMARTS - 07, Beeline - 99)

08 01 FA 00 14

9.0

Device status (DS)

see Table. 2

09 0C F0 84 63

10.0

IMPS_0

Number of pulses per IN_0

11.0

IMPS_1

Number of pulses per IN_1

12.0

IMPS_2

Number of pulses per IN_2

13.0

IMPS_3

Number of pulses per IN_3

14.0

IMPS_4

Number of pulses per IN_4

15.0

IMPS_5

Number of pulses per IN_5

16.0

IMPS_6

Number of pulses per IN_6

17.0

IMPS_7

Number of pulses per IN_7

18.0

reserve

reserve

19.0

reserve

reserve

20.0

FREQ_0

Frequency on IN_0

21.0

FREQ_1

Frequency on IN_1

22.0

FREQ_2

Frequency on IN_2

23.0

FREQ_3

Frequency on IN_3

24.0

FREQ_4

Frequency on IN_4

25.0

FREQ_5

Frequency on IN_5

26.0

FREQ_6

Frequency on IN_6

27.0

FREQ_7

Frequency on IN_7

28.0

reserve

reserve

29.0

reserve

reserve

30.0

VOLT_0

The analog sensor (messages Wialon adc1) in mV

31.0

VOLT_1

The analog sensor (messages Wialon adc2)

32.0

VOLT_2

The analog sensor (messages Wialon adc3)

33.0

VOLT_3

The analog sensor (messages Wialon adc4)

34.0

VOLT_4

The analog sensor (messages Wialon adc5)

35.0

VOLT_5

The analog sensor (messages Wialon adc6)

36.0

VOLT_6

The analog sensor (messages Wialon adc7)

37.0

VOLT_7

The analog sensor (messages Wialon adc8)

38.0

reserve

reserve

39.0

reserve

reserve

40.0

TEMP_0

The temperature sensor (1-wire) T_0 (formula for Wialon \ const100-const500)

temperature range is from -500.00 to +500.00 C temperature is transmitted to the server multiplied by 100 (to convert the decimal value into an integer), for example 28.33 to 2833. For the 0 (zero) degree takes a value of 50,000, but when unpacking the values ​​from the device you need to take 50,000, for example: 1. convert -26.33 -2633, add 50000 = 47367 pass on the server subtract 50000, and again obtain -2633 2. 16.55 transform 1655, we add the 50,000 = 51655 pass on the server subtract 50000, and again obtain 1655 Ie Range of temperature should be from 0 to 100,000. Meaning 111111 - says an incorrect calculation of the temperature

41.0

TEMP_1

The temperature sensor (1-wire) T_1

42.0

TEMP_2

The temperature sensor (1-wire) T_2

43.0

TEMP_3

The temperature sensor (1-wire) T_3

44.0

TEMP_4

The temperature sensor (1-wire) T_4

45.0

TEMP_5

The temperature sensor (1-wire) T_5

46.0

TEMP_6

The temperature sensor (1-wire) T_6

47.0

TEMP_7

The temperature sensor (1-wire) T_7

48.0

TEMP_8

The temperature sensor (1-wire) T_8

49.0

TEMP_9

The temperature sensor (1-wire) T_9

50.0

can_log_number - program number CAN

B1 - Number installed program CAN module (CAN) B2 - patch software version B3 - minor software version B4 - major software version

can_log_number Example: 32 BC 05 02 01 program = 188, FW = 5.1.2

51.0

CAN - can_security_state Flags Security Status - Bit-transmitted, for example: cff0..cff31

cff0- car factory was closed with the remote control cff1 - car factory was opened with a remote control cff2- trunk was opened with a remote control factory cff3 - module sent a signal to the protection of restatement cff4-5 - reserve cff6 - CAN-module entered the mode «sleep» cff7 - reserve cff8 - the driver's door is open cff9 - passenger door is open cff10 - trunk is open cff11 - engine cover is open cff12 - tightened handbrake lever cff13 - the foot brake is depressed cff14 - the engine is running cff15 - webasto cff16 - ignition is on cff17 - alarm mode - standard protection cff18 - closed regular remote control cff19 - key in the ignition cff20 - dynamic lighting cff21 - opened the front passenger door cff22 - open rear doors cff23-31 - reserve

can_sequrity_state Example: 33 22 33 44 55 the value is 0x55443322, or bitwise 100010000101000001001000001001 cff0 cf3

52.0

CAN - total engine operating time (hours), multiplied. 100 / DES_schetchik hours

Example: actual 25698.35 - pass 2569835, max 99999999

can_eng_full_time

53.0

CAN - full run (km), multiplied by 100 / DES_ power

Example: actual 25698.35 - pass 2569835, 999999999 max

can_full_mileage

54.0

CAN - full fuel consumption (l), multiplied by 10 / DES_davlenie oil

Example: actual 25698.3 - pass 256983, max 99999999

can_fuel_level_cons

55.0

CAN - the fuel level in the tank (%) / DES_uroven

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

can_fuel_level

56.0

CAN - the fuel level in the tank (l)

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

can_fuel_liters

57.0

CAN - engine speed (rpm) / DES_rpm

can_rpm

58.0

CAN - engine temperature (C) / DES_temperatura

if more than in 1000 - a negative temperature (for example, 1008 means it is minus 8), everything else is considered positive temperature

can_eng_temp

59.0

CAN - Vehicle speed (km / h) / DES_voltage

can_speed

60.0

CAN - pressure on the axle 1 (kg) / kW DES_vyrabotano

CAN - pressure on the axle 1 (kg)

can_axle_load1

61.0

CAN - pressure on the axle 2 (kg) / launches DES_neudachnye

CAN - pressure on the axle 2 (kg)

can_axle_load2

62.0

CAN - pressure on the axle 3 (kg) / DES_nalichie error

CAN - pressure on the axle 3 (kg)

can_axle_load3

63.0

CAN - pressure on the axle 4 (kg) / DES_preduprezhdeniya

CAN - pressure on the axle 4 (kg) / Haldex Trailer voltage (mV)

can_axle_load4

64.0

CAN - pressure on the axle 5 (kg)

CAN - pressure on the axle 5 (kg) / Haldex Axle load (multiplied by 10 bar pressure)

can_axle_load5

65.0

CAN - can_accident Flags state control Bit-transmitted, for example: cfa0..cfa31

cfa0-5 - reserve cfa6 - Passenger Seat Belt cfa7 - Driver Seat Belt cfa8 - ESP (electronic stability control) cfa9 - Indicator glow plug cfa10 - FAP (particulate filter) cfa11 - Electric pressure adjustment cfa12 - Parking lights cfa13 - Dipped headlights cfa14 - Main beam headlights cfa15 - reserve cfa16 - Check the motor (cfa8) cfa17 - fault coverage cfa18 - Low tire pressure cfa19 - Worn brake pads cfa20 - Warning cfa21 - ABS (anti-lock) cfa22 - Low fuel level cfa23 - reserve cfa24 - STOP cfa25 - pressure / oil level cfa26 - temperature / coolant level cfa27 - brake system cfa28 - Charging the battery cfa29 - AIRBAG (airbag) cfa30-31 - reserve

Example: 41 10 20 40 80 the value is 0x80402010, or bitwise 10000000010000000010000000010000

66.0

CAN - Status Flags agricultural equipment CAN_Agro Bit-transmitted, for example: cfs0..cfs31

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

Example: 42 09 12 14 22 the value is 0x22141209, or bitwise 100010000101000001001000001001 cfs0 - Threshing drum included cfs3 - including power PTO cfs9 - Open the entrance to the grain tank cfs12 - Clogged filter hydraulic oil cfs18 - Clogged air filter cfs20 - Emergency oil temperature in the hydraulic rams cfs25 - no operator cfs29- drum speed

67.0

CAN - The fluid level AdBLUE (%)

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

68.0

CAN - The fluid level AdBLUE (L)

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

69.0

CAN - driving_state position of the gas pedal \ engine load \ characteristic of a movement transmitted Bit-motion characteristic (feature motion), for example: cfm16..cfm31

1st byte position of the gas pedal 0x44 = 68% (CAP) 2nd byte engine load 0x33 = 51% (CLE) cfm16 - reserve cfm17 - Low levels of water in the tank in the tank cfm18 - Turning back hydraulics cfm19 - Standalone engine is started cfm20 - Joystick to the right cfm21 - Joystick left cfm22 - Joystick forward cfm23 - Joystick ago cfm24 - brush included cfm25 - The water supply is turned on cfm26 - Vacuums cfm27 - Unloading of the hopper cfm28 - High-pressure washers (Kerher) cfm29 - Dispersion salt (sand) inclusive cfm30 - Low salt (sand) in the tank cfm31 - reserve

Example: 45 44 33 22 11 1 byte 0x44 position of the gas pedal 68% 2-byte 0x33 the engine load of 51% 3 bytes and 4 bytes (16-31 bits) 0x1122 or bitwise 1000100100010 cfm17 - Low levels of water in the tank in the tank cfm21 - Joystick left cfm24 - brush included cfm28 - High-pressure washers (Kerher)

70.0

LLS_0

The value of the relative level and temperature DUT protocol LLS the first 2 bytes - level value 0x3111 = 12561 (LLS) or open sensor for TEMP (0-close, 1-open) or illumination level 3rd byte - temperature 0xA0 = - 96 or 0x50 = 80 4th 0x00 - voltage battery for BLE sensors (LLS, TEMP) multiplied by 10 (for example, actually 3.6 - 36 pass)

46 11 31 A0 00

71.0

LLS_1

The value of the relative level and temperature DUT protocol LLS

72.0

LLS_2

The value of the relative level and temperature DUT protocol LLS

73.0

LLS_3

The value of the relative level and temperature DUT protocol LLS

74.0

LLS_4

The value of the relative level and temperature DUT protocol LLS

75.0

LLS_5

The value of the relative level and temperature DUT protocol LLS

76.0

LLS_6

The value of the relative level and temperature DUT protocol LLS

77.0

LLS_7

The value of the relative level and temperature DUT protocol LLS

78.0

LLS_8

The value of the relative level and temperature DUT protocol LLS

79.0

LLS_9

The value of the relative level and temperature DUT protocol LLS

80.0

The value of the relative level and temperature DUT protocol LLS

The value of the relative level and temperature DUT protocol LLS the first 2 bytes - level value 0x3111 = 12561 the third byte - temperature 0xA0 = - 96 or 0x50 = 80 Temperature in degrees Celsius (-128 ... 127) fourth byte - the number of sensor 0x03 - sensor №3

50 11 31 A0 03

80.0

MicroLink - Return Temp (messages Wialon ml_ret)

0xC1DF6A76 = -27.9269828 With the temperature in the IEEE 754 format

50 76 6A DF C1

81.0

MicroLink - Supply Temp (messages Wialon ml_sup)

0xC1DF6A76 = -27.9269828 With the temperature in the IEEE 754 format

51 76 6A DF C1

82.0

MicroLink - Setpoint Temp (messages Wialon ml_sp)

0xC1DF6A76 = -27.9269828 With the temperature in the IEEE 754 format

52 76 6A DF C1

83.0

MicroLink - Container ID (letter) (in messages Wialon ml_cid)

0x43484C55 = "the ear"

4C 53 55 48 43

84.0

MicroLink - Container ID (number) (messages Wialon ml_cid)

0x0001E240 = 123456

E2 54 40 01 00

85.0

MicroLink - serial number comp + SW Rev

E2 55 40 01 00

86.0

MicroLink - Return Temp (messages Wialon ml_ret)

0xC1DF6A76 = -27.9269828 With the temperature in the IEEE 754 format

87.0

MicroLink - reserve

88.0

MicroLink - reserve

89.0

MicroLink - reserve

90.0

The display driver DV-01

Posts in Wialon driver_status = name, driver_status_id = number

91.0

Data on the maneuver / accident

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)

for EcoDriving (always with 91, 92 and 93 tags) Example: 5B 01 11 02 22 value is set to 0x22021101 axis value X+ = 4353 (0x1101) axis value X- = 8706 (0x2202) Example: 5C 00 00 03 33 value is set to 0x33030000 axis value Y = 13059 (0x3303)

92.0

Data on the maneuver / accident

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

93.0

Data on the maneuver / accident

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)

94.0

balance of SIM1

signed int

95.0

balance of SIM2

signed int

96.0

OBD Diagnostic Trouble Code (DTC)

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

Example: 60 AB D3 7A 00 DTC_00_Value = U13AB, DTC_00_Src = 0x7EF, DTC_00_Type = A 60 7A 80 27 01 DTC_01_Value = B007A, DTC_01_Src = 0x7EA, DTC_01_Type = 7 60 06 07 03 02 DTC_02_Value = P0706, DTC_02_Src = 0x7E8, DTC_02_Type = 3

97.0

SIM1 Cell ID extended

98.0

SIM2 Cell ID extended

99.0

DS2 for A5, I4, L1, A series

see Table 6

100.0

Mileage Tachograph

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

101.0

Speed ​​Tachograph

Tachograph vehicle speed multiplied by 256 (eg, 0x0548 = 5.28125 km / h)

102.0

Voltage Tachograph

System voltage Tachograph in millivolts

103.0

Discopathy tachograph

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 17 bits - weight: 1 disabled, 0-enabled 18 bit - mode "ferry / train": 0, not activated, 1 is activated 19 bit - mode "not applicable": 0, not activated, 1 is activated

104.0

Number of cards in a card reader driver (junior section)

Bits 0-31 of the card number

68 40 1C BC DF -> 0xDFDC1C40 69 02 A0 01 2B -> 0x2B01A002: 0x02DFDC1C40 = [CARD ID] - card number 0x10 = 16 = 'G' - the index map update 0x03 = 3 = '3' - an index card replacement 0x00 = 0 = 'D' - type card 0x2B = 'RU' - the country code We get the RU D [CARD ID] 3 G

105.0

Number of cards in a card reader driver (older part)

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

106.0

Number of cards in a card reader mate (junior section)

Bits 0-31 of the card number

6A FF E3 0B 54 -> 0x540BE3FF 6B EA 12 22 2B -> 0x2B2212EA:   0x2540BE3FF = 9999999999 - card number   0x0F = 15 = 'F' - an index card   0x09 = 9 = '9' - an index map update   0x04 = 4 = "4" - the index card replacement   0x01 = 1 = 'M' - type card   0x2B = 'RU' - the country code We get the RU M F 9999999999 F 4 9

107.0

Number of cards in a card reader partner (principal part)

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

108.0

Tachograph serial number (part 1)

109.0

Tachograph serial number (part 2)

110.0

Condition sensor G-Sensor

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

111.0

Data on the maneuver

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

When maneuvering in a Packet of device tags peredayustsya 111,112,113

112.0

Data on the maneuver / accident

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)

If the tag contains Packet 111 - data tags are the parameters of the maneuver. If the tag contains Packet 114 - data tags are the parameters of the accident. In one Packet can not otdnovremenno transmitted data and maneuver of an accident

113.0

Data on the maneuver / accident

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

114.0

The data on road accidents

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

When maneuvering in a Packet of device tags peredayustsya 114,112,113, 115, 116, 117, 118

115.0

Time of the accident (EGTS)

116.0

Breadth DTP (EGCS)

117.0

Longitude accident (EGTS)

118.0

The data on road accidents

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

119.0

BMS - bluetooth tag (iBeacon)

the 2 bytes = 0x3054 = 12372 - MAJOR next 2 bytes = 0x106E = 4206 - MINOR

77 6E 10 54 30 - 12372 -major, 4206-minor bms=12372:4206

120-129

MODBUS mbus

4 bytes

130.0

The data from the meter

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)

always sent two tags 130 and 131 - can transmit the values ​​of multiple sensors. Sensors are separated by number 131 tag bits 24-31 Transfer sequence: 130 TAG followed by 131 - it's importamt Example: 82 22 11 00 00 82 - tag number (130) the value is 0x00001122, or 4386 - the amount of fuel Example: 83 04 03 02 01 83 - tag number (131) the value is 0x01020304, or bitwise 1000000100000001100000100 flow rate = 772 sensor status = nominal mode number of sensor = 1

131.0

The data from the meter

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)

150.0

Odometr calculated. full mileage of vehicle (km) over satellite, multiplied by 100

Example: actual 25698.35 - pass 2569835, 999999999 max

gps_full_mileage

151.0

Dilution of Precision

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

Example: 97 C3 05 00 00 97 - tag number (151) hdop = 0x05C3 / 100 = 14.75

152.0

153.0

device status

154.0

balance SIM1 and SIM2

155.0

155.0

Refill capacity in ml

KUSS_L

156.0

Filling number and filling duration

KUSS_N, KUSS_T

0xNNTTTTTT

157.0

160.0

MODBUS

SDV pressure address 1

161.0

MODBUS

SDV pressure address 2

162.0

MODBUS

SDV pressure address 3

163.0

MODBUS

SDV pressure address 4

164.0

MODBUS

SDV pressure address 5

165.0

MODBUS

SDV pressure address 6

166.0

MODBUS

SDV pressure address 7

167.0

MODBUS

SDV pressure address 8

168.0

MODBUS

169.0

MODBUS

170.0

ATOM video_id / abt_value

171.0

ATOM state of cameras

172.0

full active energy, multiplied by 100 / ATOM unique_label

173.0

full reactive energy, multiplied by 100 / ATOM video_start_time

174.0

175.0

ATOM ERROR CODES

190.0

Virtual Sensors (designation wialon VS_n) see Table 5

1st byte 0x22 = 34 - the number of virtual sensor (n) 2,3,4 bytes - the sensor value 0x554433 = 5,588,019

BE 22 33 44 55

200.0

SIM card 2 LAC CID

Local Area Code - (first 2 B) 0xFF01 Cell ID - (next. 2 B) 0x1417

C8 17 14 01 FF

201.0

SIM card 2 Signal level GSM (old. Byte) MCC (2 bytes) MNC (low byte)

level signal from 0 to 31, 0x14 = 20 Mobile Country Code - code of the country in which the BS (Russia it is 250, Ukraine - 255, Belarus - 257) 0x00FA = 250 Mobile Network Code - code for your network 0x01 = 1 (MTS - 01, MegaFon - 02, SMARTS - 07, Beeline - 99)

C9 01 FA 00 14

202.0

ICCID sim card 2 [3 to 11 digits]

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]

203.0

ICCID sim card 2 [from 12 to 20 digits]

204.0

MAC BLE

205.0

MAC BLE

206.0

207.0

.....

210-229

VAL_x

4 bytes parametrs for additional services (210-219 used for special CAN data)

DC 0C F0 84 63

4 bytes parametrs for additional services (220-229 used for universal BLE integration)

230-239

.....

250.0

Informational messages (for tracker)

cm. Table. 3 information messages (error status, etc.)

Next contact time in unixtime format (for beacon)

251.0

Hard & Soft versions

fb 08 02 01 2d

252.0

Hardware status (HS)

cm. Table. 4 module status device (HS)

253.0

ICCID sim card 1 [3 to 11 digits] - iccid1p1

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

fd e2 e1 2c 16

254.0

ICCID sim card 1 [from 12 to 20 digits] - iccid1p2

fe cc 6a 91 05

255.0

Device ID

unique device identifier (ID) in the WEB configurator

Table 2. Description of the device status (DS)

Number bits

Title

Description

Example

0.0

Input IN0 - in Wialon in1

messages Wialon I / 0

09 0C F0 84 63                      31 Bit 0 0x6384f00c = 0110 0011 1000 0100 1111 0000 0000 1100 0 - IN0 = 0 1 - IN1 = 1 2 - IN2 = 1 3 - IN3 = 1 4 - IN4 = 0 5 - IN5 = 0 6 - IN6 = 0 7 - IN7 = 0 8 - OUT0 = 0 9 - OUT1 = 0 10 - OUT2 = 0 11 - OUT3 = 0 12,13 - GSM = 3 14,15 - GPS / Glonass = 3 16 - MOVE_SENS = 0 17 - SIM = 0 18 - 1 = SIM_INSERT 19 - ST0 = 0 20 - ST1 = 0 21 - ST2 = 0 22.23 - Bat status 1 = 24-31 - VOLT = 99 (99 * 150 = 14850 mV)

1.0

Input IN1 - in Wialon in2

messages Wialon I / 0

2.0

Input IN2 - in Wialon in3

messages Wialon I / 0

3.0

Input IN3 - in Wialon in4

messages Wialon I / 0

4.0

Input IN4 - in Wialon in5

messages Wialon I / 0

5.0

Input IN5 - in Wialon in6

messages Wialon I / 0

6.0

Input IN6 - in Wialon in7

messages Wialon I / 0

7.0

Input IN7 - in Wialon in8

messages Wialon I / 0

8.0

Output OUT0 - in Wialon out1

messages Wialon I / 0

9.0

Output OUT1 - in Wialon out2

messages Wialon I / 0

10.0

Output OUT2 - in Wialon out3

messages Wialon I / 0

11.0

Output OUT3 - in Wialon out4

messages Wialon I / 0

12.0

the state of the GSM modem (messages Wialon gsm_st)

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

13.0

14.0

the state of GPS / Glonass module (messages Wialon nav_st)

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

15.0

16.0

Motion Sensor (messages Wialon mw)

1 - motion is 0 - no movement

17.0

SIM card / SIM-chip (messages Wialon sim_t)

1 - sim-chip 0 - sim-card

18.0

the presence of a SIM card / SIM-chip (messages Wialon sim_in)

1 - insert, 0 - no

19.0

st0 - mode service / sensor opening

mode (0 - monitoring, 1 - protection)

20.0

st1 - SOS mode monitor / alarm mode protection / 1-wire discrete mode

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

21.0

st2 - Status of plugs

ignition or ignition of the CAN virtual

22.0

Backup battery status (in messages Wialon pwr_in)

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)

23.0

24.0

external voltage (messages Wialon pwr_ext)

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

25.0

26.0

27.0

28.0

29.0

...

31.0

Table 6 . Description of the device status 2 (DS2)

Number bits

Title

Description

Example

0.0

GPS / GLONASS status [nav_st]

1.0

2.0

GSM status [gsm_st]

3.0

4.0

5.0

Active SIM [sim_t]

0 - SIM1, 1 - SIM2

6.0

status SIM card 1 GSM [sim1_st]

7.0

8.0

9.0

status SIM card 2 GSM [sim2_st]

10.0

11.0

12.0

Server Status 0 [S0_st] - service or monitoring server 4

13.0

14.0

Status of Server 1 [S1_st] - monitoring server 1

15.0

16.0

Server 2 status [S2_st] - monitoring server 2

17.0

18.0

Server 3 status [S3_st] - monitoring server 3

19.0

20.0

Accelerometer [mw]

21.0

22.0

Tamper sensor [os] / BLE Tag (L, A seies)

23.0

MicroSD card [msd]

24.0

25.0

Bluetooth [BT]

26.0

gyroscope [gyro]

27.0

28-30

WIFI module status

0 - MODULE_NOT_FOUND 1 - MODULE_FOUND 2 - NETWORK_NOT_FOUND 3 - NETWORK_FINDING 4 - NETWORK_FOUND 5 - NETWORK_CONNECTING 6 - NETWORK_CONNECTED

31.0

Table 3. Description of messages from the device

room

Title

Description

Example

0.0

...

5.0

registration request unit

request sent

6.0

registration request unit

request has been successfully worked out

7.0

registration request unit

Error in query

8.0

registration request unit

Error in query

9.0

registration request unit

10.0

query device settings

request sent

11.0

query device settings

request has been successfully worked out

12.0

query device settings

Error in query

13.0

query device settings

Error in query (the same settings)

14.0

query device settings

15.0

request the current version

request sent

16.0

request the current version

request has been successfully worked out

17.0

request the current version

Error in query

18.0

request the current version

Error in query

19.0

request the current version

20.0

request for a piece of firmware

request sent

21.0

request for a piece of firmware

request has been successfully worked out

22.0

request for a piece of firmware

Error in query (Bad SW version for HW)

23.0

request for a piece of firmware

Error in query

24.0

request for a piece of firmware

firmware is loaded successfully

25.0

transfer request settings

request sent

26.0

transfer request settings

request has been successfully worked out

27.0

transfer request settings

Error in query

28.0

transfer request settings

Error in query

29.0

transfer request settings

30.0

confirmation

request sent

31.0

confirmation

request has been successfully worked out

32.0

confirmation

Error in query

33.0

confirmation

Error in query

34.0

confirmation

35.0

querying the server

request sent

36.0

querying the server

request has been successfully worked out

37.0

querying the server

Error in query

38.0

querying the server

Error in query

39.0

querying the server

...

60.0

Team registration

internal command

61.0

Team registration

a team from the server

62.0

Team registration

command via SMS

63.0

Team registration

team through the Viewer

64.0

Team registration

team call

65.0

Team registration

reserve

66.0

Team registration

reserve

67.0

Team registration

reserve

68.0

Team registration

reserve

69.0

Team registration

reserve

70.0

command to update the device settings

internal command

71.0

command to update the device settings

a team from the server

72.0

command to update the device settings

command via SMS

73.0

command to update the device settings

team through the Viewer

74.0

command to update the device settings

team call

75.0

command to update the device settings

reserve

76.0

command to update the device settings

reserve

77.0

command to update the device settings

reserve

78.0

command to update the device settings

reserve

79.0

command to update the device settings

reserve

80.0

command to update the device software

internal command

81.0

command to update the device software

a team from the server

82.0

command to update the device software

command via SMS

83.0

command to update the device software

team through the Viewer

84.0

command to update the device software

team call

85.0

command to update the device software

reserve

86.0

command to update the device software

reserve

87.0

command to update the device software

reserve

88.0

command to update the device software

reserve

89.0

command to update the device software

reserve

90.0

command to update the device software

100.0

Device startup

before restart

199.0

GeoZones

200.0

MORE_LOADER_ERRORs

cancel update

201.0

MORE_WR / RD_ERRORs

cancel update

202.0

CRC_32 ERROR

cancel update

203.0

UpSetSt

update the configuration at each start

204.0

UpSetTime

re-set the interval

250.0

Error external navigation module

restart module

251.0

No NMEA

restart device

300.0

Time synchronization of GPS / Glonass

301.0

synchronization of time through the configurator

302.0

time synchronization with server monitoring

303.0

load filter: Duplicate Time

304.0

send a first valid position

305.0

send last valid point

306.0

By time interval in parking state

event 1

307.0

worked condition of the distance

308.0

The first point is valid after the start of the device

309.0

NMEA packet loss from the module

310.0

Error NMEA

restart device

311.0

The first coordinate is valid

312.0

the latter is valid coordinate

313.0

worked condition speed

314.0

worked condition of the distance

315.0

worked condition at a corner

event 4

316.0

worked condition at zero speed

317.0

Discrete input triggering

318.0

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

319.0

Reset filters coordinate when sending to the server

320.0

First message info

321.0

GPS / GLONASS power short circuit detect

322.0

On command 0101

323.0

On command 010B

324.0

325.0

Alternative positioning

326.0

BLE sensor event

327.0

The positioning source has changed

400.0

Switching to parking mode

event 2

401.0

Switching to sleep mode

402.0

came out of sleep by the movement

403.0

came out of sleep by the Timer

404.0

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

405.0

came out of sleep by the triggered input

406.0

came out of sleep by the GPS / Glonass

407.0

Start movenent

event 3

408.0

409.0

Shock detected

410.0

Tilt detected

500.0

No response from the server

501.0

No response from the server when you try again

502.0

Error while sending data from the memory

503.0

Error sending current data

504.0

ER_HEADER

505.0

ER_SERVER_ANS (0xFE)

510.0

error in ADC

restart devices

511.0

error in the GSM

restart devices

512.0

error transmission data to the server

restart devices

513.0

inc_nmea

514.0

write tempory settings

515.0

Checksum error when sending packets

516.0

switching between SIM cards

517.0

RTC fail

520.0

external power changed

530.0

Cover Sensor Activated

531.0

Successful command delivery to the device

600.0

switched mode DEEP SLEEP

Deep Sleep mode (consumption 4-5 mA)

601.0

I emerged from DEEP SLEEP timer

signal transmission life

602.0

I emerged from DEEP SLEEP to change the inlet

transfer of disturbing messages

603.0

It emerged from DEEP SLEEP motion detected

604.0

It emerged from DEEP SLEEP to change the input voltage

610.0

MODBUS_RTU PACKET

618.0

620.0

621.0

666.0

On command

restart devices

667.0

system error

restart devices

700.0

a request to upload a file from the tachograph .ddd

701.0

.ddd start automatically upload the file over the interval

702.0

.ddd file successfully vygruzhen around tachograph

703.0

705.0

Invalid password authorization canister in the tachograph

706.0

An error occurred when unloading from the tachograph

707.0

card is removed during a file upload .ddd

708.0

No card in the card reader or card is not authorized

709.0

tachograph stopped responding (perhaps asleep)

710.0

Driver Activity has changed

800.0

G-sensor command response calibration

850.0

External device firmware has been downloaded

851.0

External device firmware has been updated

852.0

An error occurred while external device updating

853.0

An error occurred while downloading the external device firmware

860.0

CAN sniffer started

861.0

CAN autobaudrate ready

862.0

log collect finished, file is full

863.0

log collect finished, timeout

865.0

CAN sniffer start fail

866.0

CAN autobaudrate fail

867.0

create CAN file fail

868.0

save CAN file fail

860-1116

Exceptions of the G-Sensor

888.0

locator error

restart devices

1200.0

Change state of IN0

...

...

1207.0

Change state of IN7

1208.0

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

1209.0

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

1210.0

Ignition is ON

1211.0

Ignition is OFF

1212.0

Engine is ON

1213.0

Engine is OFF

1250 + x

Change state of extended INx, x = 0...9

1300 - 1315

start of exceed of acceleration threshold

1320 - 1335

end of exceed of acceleration threshold

1340 - 1345

start of exceed of speed threshold

1350 - 1355

end of exceed of speed threshold

Table 4. Description Module status device (HS)

the status of the modules devices

number bits

status

a value of 0

to 1

0.0

Inner memory

No settings

Settings OK

1.0

External Memory

issue

OK

2.0

Real Time Clock

issue

OK

3.0