LSIS XBE-DC08A, Руководство пользователя, Страница: 1067 / 1284

Chapter 2 Built-in Cnet communication
2-69
B
u
ilt
-in
C
omm
2.6 LS Bus Protocol
LS Bus Protocol communication is function executing communication between XGB Cnet and LS Inverter.User can
configure LS Bus communication system between our products without special setting by usingreading/writing data of
internal device area and monitoring function
2.6.1 LS Bus Protocol
LS Bus Protocol communication is function executing communication between XGB Cnet and LS Inverter.
User can configure LS Bus communication system between our products without special setting by using
reading/writing data of internal device area and monitoring function.
The function of LS Bus Protocol supported by XGB is as follows.

Device continuous reading

Device continuous writing
1) Frame structure
(1) Base format
(a) Request frame
(External communication → XGB)
Header
(ENQ) Station
number
Command Structurized data area
Frame check
(BCC) Tail
(EOT)
(b) ACK response frame
(XGB → External communication, when receiving data normally)
Header
(ACK) Station
number
Command Structurized data area
Frame check
(BCC) Tail
(EOT)
(c) NAK response frame
(XGB → External communication, when receiving data abnormally)
Header
(NAK) Station
number
Command Error code ( ASCII 4 Byte )
Frame check
(BCC) Tail
(EOT)
Note
1) The numerical data of all frames are ASCII codes equal to hexadecimal value, if there’s no clear statement.
The terms in hexadecimal are as follows.
•
Station No.
•
Command type is supported R (read) and W (write).
•
All contents of data
2) If it is hexadecimal, H is attached in front of the number of frames like H01, H12345, H34, H12, and H89AB.
3) Available frame length is maximum 256 bytes.
4) Used control codes are as follows.
Code Hex value Name Contents
ENQ H05 Enquire Request frame initial code
ACK H06 Acknowledge ACK response frame initial code
NAK H15 Not Acknowledge NAK response frame initial code
EOT H04 End of Text Request frame ending ASCII code