VTS VENTUS PRO PVS PO 50 EC [15/16] Description of errors

VTS VENTUS PRO PVS PO 50 EC [15/16] Description of errors
VTS reserves the right to implement changes without prior notice.
www.vtsgroup.com Page 15 of 16 ver. 2.0 (11.2021)
Error format:
Description
Size [Bytes]
Values
Notes
Address
1
1 247
Function code
1
0x90
Error code
1
1 4
See section 4.2.4
CRC check sum
0x0000 0xFFFF
See section 4.4
4.2.4. Description of errors
CODE
Name
0x01
Invalid function
0x02
Invalid data range / address
0x03
Invalid data value
0x04
SLAVE device error
4.3. Data format
4.3.1. Character / byte format
The following figure shows the format of a byte transmitted in the MODBUS
RTU protocol. Each transmitted character has 10 or 11 bits, which are sent in
order from the least significant to the most significant.
With even / odd parity check
START
1
2
3
4
5
6
7
8
PAR
STOP
Without parity check (1 or 2 stop bits):
START
1
2
3
4
5
6
7
8
STOP
(STOP)
4.3.2. Order of bytes in 16-bit data fields in a transmission frame
The following figure shows the byte order of the 16-bit data fields. For 16-bit
data fields, the correct byte order is that the older byte is transmitted first,
then the younger byte (HI→LO - BIG ENDIAN), while for the CRC field the
younger byte is transmitted first, then the older byte (LO→ HI - LITTLE
ENDIAN).
DATA
CHECK SUM
REG-0 (16bit)
REG-1 (16 bit)
...
REG-N (16bit)
CRC (16bit)
HI
LO
HI
LO
HI
LO
LO
HI

Содержание

Скачать