SmartLogger ModBus Interface Definitions
SmartLogger ModBus Interface Definitions
SmartLogger ModBus Interface Definitions
Issue 35
Date 2020-02-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://e.huawei.com
Change History
Contents
5 Reference Documents................................................................................................................. 42
1 Introduction
Name Description
Name Description
I64 Signed integer (64 bits)
STR String
MLD Multiple bytes
N/A Not applicable
2 Register Definitions
RW signals are permanently valid, will be retained until updated the next time, and support
0X03, 0X06, and 0X10 instructions.
WO signals do not support the 0X03 query instruction, but support the 0X06 and 0X10
instructions.
RO signals support only the 0X03 instruction.
2.1 Register Definitions for the SmartLogger
2.2 Alarm Definitions for the SmartLogger
2.3 Register Definitions for the Environmental Monitor Instrument
2.4 Register Definitions for the Power Meter
2.5 Register Definitions for the SUN2000
2.6 Public Register Definitions
2.7 Remapped Modbus definitions
In the following table, the operation object of the register is the SmartLogger or all inverters accessed by
the SmartLogger. In the Modbus-TCP communications protocol, the logic device ID is fixed to 0.
In the following table, the operating object of the register is an environmental monitor instrument. In the
Modbus-TCP communications protocol, the logic device ID is set to the RS485 address of the
environmental monitor instrument.
In the following table, the operating object of the register is a power meter. In the Modbus-TCP
communications protocol, the logic device ID is set to the RS485 address of the power meter.
SN16 ~ SN25 registers are supported only by DL/T 645 power meters.
The operating object of the register is an SUN2000 inverter. In the Modbus-TCP communications
protocol, the logic device ID is set to the RS485 address of the inverter.
For the detailed register definitions, see the SUN2000VXXXRXXXCXX MODBUS Protocol.
A device name consists of a maximum of 20 bytes (excluding the terminator), and can contain only
visible characters whose ASCII codes are in the range from 0x20 to 0x7e, including letters (a–z, A–Z),
digits (0–9), and single-byte punctuation (excluding '\").
The mapped registers are accessed by the SmartLogger address. By default, each device takes up 25
registers, the register address is derived from the initial register address, offset address, and device
address translation. Device address for Modbus physical address. Supported devices: inverter,
environmental monitor instrument.
9 Cabinet RO I16 ℃ 10 11 1
temperature
10 Major Fault Code RO U32 N/A N/A 12 2 Alarm
ID(Bit31~16) +
Cause ID(Bit15~0)
11 Minor Fault Code RO U32 N/A N/A 14 2 Alarm
ID(Bit31~16) +
Cause ID(Bit15~0)
12 Warning Code RO U32 N/A N/A 16 2 Alarm
ID(Bit31~16) +
Cause ID(Bit15~0)
13 Spare1 RO U16 N/A N/A 18 1
14 Spare2 RO U16 N/A N/A 19 1
15 Spare3 RO U16 N/A N/A 20 1
16 Spare4 RO U16 N/A N/A 21 1
17 Spare5 RO U16 N/A N/A 22 1
18 Spare6 RO U16 N/A N/A 23 1
19 Spare7 RO U16 N/A N/A 24 1
The MODBUS-TCP interface provided by the SmartLogger can directly access the inverter.
The built-in power interface of the SmartLogger can be used for array-level power adjustment.
If the power interface is used, the power adjustment instruction is first processed by the
SmartLogger and then forwarded to the inverter.
Related interfaces are as follows.
The address of an access device is an RS485 address which can be read on the LCD or built-in WebUI of
the SmartLogger.
0 1–247 248–255
Table 4-3 Table of exception codes returned by an NE (0x00–0x8F are for common exception
codes)
4.3.3.4 Example
A master node sends a request to a slave node (logic device ID: 01) to query register whose
address is 32306/0X7E32. The request frame format is as follows:
Data 00 01 00 00 00 06 00 03 7E 32 00 02
frame
Data 00 01 00 00 00 07 00 03 04 00 00 00 01
frame
Data 00 01 00 00 00 03 00 83 03
frame
4.3.4.4 Example
A master node sends a Power-On instruction(register address: 40200/0X9D08) to a slave node
whose address is 01. The request frame format is as follows:
Data 00 01 00 00 00 06 00 06 9D 08 00 00
frame
Data 00 01 00 00 00 06 00 06 9D 08 00 00
frame
Data frame 00 01 00 00 00 03 00 86 04
4.3.5.4 Example
A master node sends an instruction to a slave node whose address is 01 to set the active power
control mode (register address: 40118/0X9CB6) to 2, and set the active power deration
(register address: 40119/0X9CB7) to 50%. The request frame format is as follows:
Dat 00 01 00 00 00 0B 00 10 9C B 00 02 04 00 02 00 32
a 6
fra
me
Datafr 00 01 00 00 00 06 00 10 9C B6 00 02
ame
Basic device identifier: All objects of this type are mandatory, such as the manufacturer
name, product code, and revision version.
Normal device identifier:Except the basic data objects, the device provides additional
and optional identifiers and data object description. Normal device identifiers define all
types of objects according to standard definitions, but the execution of this type of
objects is optional.
Extensive device identifier:Except the basic data objects, the device provides additional
and optional identifiers and special data object description. All these data objects are
related to the device.
5 Reference Documents
Modbus_Application_Protocol_V1_1b3
Modbus over serial line specification and implementation guide V1.02
Modbus_Messaging_Implementation_Guide_V1_0b