DONE :=M51.7
BUSY :=M51.0
ERROR :=M51.6
STATUS :=MD92
RECORD :=P#DB80.DBX0.0 BYTE 11
U M 51.0
SPB m2
BE
Block status or error information
Source area in DB80
Table A-35 DB80: Transparent message format
Byte Initial value (hex) Comment (Hex)
0 00 Req_Control
(00 = Transparent message format.
40 = Transparent message format with SHC sequence)
1 05 Number of preamble bytes (05-14)
2 82 Start character
(02 = Short Frame with command 0)
(82 = Long Frame with other commands)
3 98 Address
(with command 0, the address is exactly 1 byte long and has
the value 0.)
4 CF
5 38
6 84
7 F0
8 01 Command (CMD)
9 00 Length in bytes
10 98 Checksum (CHK)
(calculated as EXOR addition starting from byte 2 "Start
character" up to the last byte of the command. The check‐
sum must not be sent with the job.)
A HART command can also be sent in compact message format. In this case, the data transferred
via DB80 is reduced to 4 bytes.
Table A-36 DB80: Compact message format
Byte Initial value (hex) Comment (Hex)
0 20 Req_Control
(20 = Compact message format
60 = Compact message format with SHC string)
1 05 Number of preamble bytes (5…20, 255)
2 01 Command (CMD)
3 00 Length in bytes
Appendix
A.6 HART operating data records
ET 200iSP
Operating Instructions, 11/2022, A5E00247483-AK 457
To Next Page
Loading...
Need help?
General
