SUN2000!3!10KTL-M0 MODBUS Interface Definitions
SUN2000!3!10KTL-M0 MODBUS Interface Definitions
V100R001
MODBUS Interface Definitions
Issue 01
Date 2019-01-02
and other Huawei trademarks are trademarks of Huawei Technologies C o., 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 stipulat ed by the contract made bet ween 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. E very 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: http://e.huawei.com
Change History
Contents
1 Introduction
This document describes the Modbus protocol used by Huawei inverters and provides
standards and constraints for future third-party integration, development, and customization.
Huawei inverters comply with the standard Modbus protocol, and this document describes
only the information special for Huawei inverters. For other information about Modbus, see
the documents about the standard Modbus protocol.
1.1 Terms and Abbreviations
1.2 System Requirements
1.3 Inverter Models and Rated Power
STR String
Name Description
400 SUN2000-5KTL-M0
401 SUN2000-5KTL-M0
402 SUN2000-6KTL-M0
403 SUN2000-6KTL-M0
404 SUN2000-8KTL-M0
405 SUN2000-8KTL-M0
406 SUN2000-10KTL-M0
407 SUN2000-10KTL-M0
408 SUN2000-12KTL-M0
410 SUN2000-3KTL-M0
411 SUN2000-4KTL-M0
The maximum active power (Pmax), maximum reactive power (Qmax), and rated power (Pn)
corresponding to each model can be obtained through the register interface.
2 Register Definitions
3 Alarms
16 bits 0x1234
A slave node returns one response for each request from the master node. If the master node
does not receive any response from the slave node in 5s, the communication process is
regarded as timed out.
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: 00) to query register whose
address is 32306/0X7E32. The request frame format is as follows:
01
Protocol Type 00
00
Data Length 00
06
Logic Device ID 00
Function Code 03
Number of Registers 00
02
01
Protocol Type 00
00
Data Length 00
07
Logic Device ID 00
Function Code 03
Data Number of bytes 04
RegisterValue 00
00
00
01
01
Protocol Type 00
00
Data Length 00
03
Logic Device ID 00
Function Code 83
Data Error Code 03
4.3.4.4 Example
A master node sends instruction(register address: 40200/0X9D08) to a slave node whose
address is 00. The request frame format is as follows:
01
Protocol Type 00
00
Data Length 00
06
Logic Device ID 00
Function Code 06
08
Register Value 00
00
01
Protocol Type 00
00
Data Length 00
06
Logic Device ID 00
Function Code 06
08
Register Value 00
00
Protocol Type 00
00
Data Length 00
03
Logic Device ID 00
Function Code 86
4.3.5.4 Example
A master node sends an instruction to a slave node whose address is 00 to set (register address:
40118/0X9CB6) to 2, and set (register address: 40119/0X9CB7) to 50. The request frame
format is as follows:
01
Protocol Type 00
00
Data Length 00
0B
Logic device ID 00
Function Code 10
Number of Registers 00
02
Number of Bytes 04
Register Value 00
02
00
32
01
Protocol Type 00
00
Data Length 00
06
Logic device ID 00
Function Code 10
Data Register Address 9C
B6
Number of Registers 00
02
01
Protocol Type 00
00
Data Length 00
03
Logic Device ID 00
Function Code 90
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.
Object ID 1 0x00
Consistency level 1 01
More 1 N/A
Object length 1 N
Object value N N/A
ReadDeviId code 1 03
Object ID 1 0x87
ReadDeviId code 1 03
Consistency level 1 03
More 1 N/A
Object length 1 N
Object value N N/A
0x88 Information about the ASCII character string Returns information only
first device See the device for the first device if a
description definitions network element allows
below. only one device to be
connected to each RS485
For
example:1=SUN2000L-XXKTL;2=V100R001C00SPC100;3=P1.0-D5.0;4=123232323;5=1;6
=1.1
3 Version of the ASCII character See the interface protocol version definitions.
communications string
protocol