
UPS2000-(6 kVA-20 kVA)
Modbus Protocol Development Guide
1 Communication Protocol
Issue 02 (2016-03-10)
Huawei Proprietary and Confidential
Copyright © Huawei Technologies Co., Ltd.
11
Object ID
Object Name
or
Description
Type
Mandatory or
Optional
(M/O)
Category
0x80-0xFF
N/A
N/A
N/A
Extension
Request PDU:
Function Code
1 byte
0x2B
MEI Type
1 byte
0x0E
ReadDevID Code
1 byte
0x01/0x02/0x03/0x04
Object ID
1 byte
0x00 to 0xFF
Request parameter description:
Function code: 43 (decimal), 0x2B (hexadecimal).
MEI type: The MEI type of 14 (0x0E) assigned to the device identifier port.
The ReadDevID has four access types:
−
0x01: request to obtain the basic device identifier (stream access)
−
0x02: request to obtain the normal device identifier (stream access)
−
0x03: request to obtain the extension device identifier (stream access)
−
0x04: request to obtain the special device identifier (special access)
If the identifier data is not suitable for individual responses, you can require several request
and response transactions. The object ID byte provides the first identifier code obtained. For
the first transaction, the client must set the object ID to 0x00 to obtain the start of the device
identifier data. For the subsequent transactions, the client must set the object ID to the value
returned by the previous responded server.
If the object ID does not match any known object, the server points to the object numbered
0x00 (from the start).
For single access, the ReadDevID code is 0x04. The object ID in the requesting process
provides the obtained object identifier code.
If the object ID does not match any known object, the server returns an abnormal code
numbered 0x02 (invalid data address).
Response PDU:
Function Code
1 byte
0x2B
MEI Type
1 byte
0x0E
ReadDevID Code
1 byte
0x01/0x02/0x03/0x04
Consistency Level
1 byte
N/A
More
1 byte
0x00/0xFF