|
Trying to get my foot in the door with Modbus, and not having much luck. I need to access Modbus RTU data from Huawei SUN2000-10KTL-M0 inverter (which I think shares same registers as many SUN2000 models). Not sure which piece of my puzzle is in the wrong place, but I have tried communicating with Modbus Bridge and SML script and Serial TCP and haven't seen any two-way communication happening. So my error could be in a number of places. Looking for suggestions to move forward. My setup: Mini D1 attached to RS485 converter board fed with 5v/Gnd/GPIO1(Tx)/GPIO3(Rx) which is in turn connected to the inverter via pins 1/3 on the com port. Have built my binary with the following #defines: Modbus doc for Huawei shows all registers available, here is a sample of two that I want to start with to understand the syntax: For scripting, I've tried adapting a script from someone on Discord, but it crashes. So clearly something is wrong. Do I define all the required registers on the first line? And then subsequent lines are mapping those into variables? If so, how do i specify which bytes I want for each variable? Lots and lots of xxxxxxxxxxxxx? If I wanted to see communication happen with ModbusBridge, I've tried |
Replies: 9 comments 37 replies
|
OK, trying to connect with modbus TCP in script. How do I define the port? When I try: I get |
|
your descriptor is wrong. the port has to be given instead of baud rate |
|
Was missing a m. And I see that the baud rate is replaced by the port. But when I do: I get: |
|
still the wrong meter number not 2 but 1 |
|
Ah got it. The meter number in the line below was wrong. Now it's working. |
|
I had the RS485 connected to 3/5 instead of 1/3. Now I am receiving data from the SUN2000 when I define ModBrTx and ModBrRx and do for example So now i just need some guidance on the syntax of the SML script/meter definition... |
|
@jeroenst I'm trying to read a string (register 30000), but unclear what Function Code and Type I should use. Everything I've tried so far has returned error 1 or 2. |
|
See https://tasmota.github.io/docs/Modbus-Bridge/ for examples. 30000 (0) is probably a holding register containing an integer. |
|
@pkkrusty I suspect you don't have it on Ethernet or Wifi, right? I'd be careful in messing with the Modbus on the SUN2000 if it is connected to the cloud, also if you want to add a backup box (not the one that is from Huawei) because of warranty issues. I think it calls home to the EMEA servers occasionally. I ended up using the TCP protocol and the modbus package to pipe things into node-red. If you are familiar with that, in node-red it works somewhat like this: [
{
"id": "b88b6574d56ef461",
"type": "modbus-getter",
"z": "43643082ec7e300c",
"name": "32080",
"showStatusActivities": false,
"showErrors": false,
"logIOActivities": false,
"unitid": "1",
"dataType": "HoldingRegister",
"adr": "32080",
"quantity": "2",
"server": "70220ecd.1ca1e",
"useIOFile": false,
"ioFile": "",
"useIOForPayload": false,
"emptyMsgOnFail": false,
"keepMsgProperties": false,
"x": 290,
"y": 2500,
"wires": [
[
"6cd123d226deaa96"
],
[
"c6ae93e907d20880"
]
]
},
{
"id": "6cd123d226deaa96",
"type": "buffer-parser",
"z": "43643082ec7e300c",
"name": "",
"data": "payload",
"dataType": "msg",
"specification": "spec",
"specificationType": "ui",
"items": [
{
"type": "int32be",
"name": "Active Power",
"offset": 0,
"length": 1,
"offsetbit": 0,
"scale": "1",
"mask": ""
}
],
"swap1": "",
"swap2": "",
"swap3": "",
"swap1Type": "swap",
"swap2Type": "swap",
"swap3Type": "swap",
"msgProperty": "payload",
"msgPropertyType": "str",
"resultType": "value",
"resultTypeType": "output",
"multipleResult": false,
"fanOutMultipleResult": false,
"setTopic": true,
"outputs": 1,
"x": 470,
"y": 2500,
"wires": [
[
"9efb69d6834bfe6e"
]
]
},
{
"id": "9efb69d6834bfe6e",
"type": "calculator",
"z": "43643082ec7e300c",
"name": "",
"inputMsgField": "payload",
"outputMsgField": "payload",
"operation": "div",
"constant": "1",
"round": true,
"decimals": "0",
"x": 630,
"y": 2500,
"wires": [
[
"f2c43b3f9855a2d2",
"908ab92b8223d602",
"9fae2ace5a750514"
]
]
},
{
"id": "fe721ef316ce2431",
"type": "calculator",
"z": "43643082ec7e300c",
"name": "",
"inputMsgField": "payload",
"outputMsgField": "payload",
"operation": "div",
"constant": "1",
"round": true,
"decimals": "0",
"x": 630,
"y": 2280,
"wires": [
[
"107145cec1d3e177",
"bd8b3801a4dd4f35",
"cbf7131f2ab87a6b"
]
]
},
{
"id": "eafde78ee735f583",
"type": "buffer-parser",
"z": "43643082ec7e300c",
"name": "",
"data": "payload",
"dataType": "msg",
"specification": "spec",
"specificationType": "ui",
"items": [
{
"type": "int32be",
"name": "Meter Power",
"offset": 0,
"length": 1,
"offsetbit": 0,
"scale": "1",
"mask": ""
}
],
"swap1": "",
"swap2": "",
"swap3": "",
"swap1Type": "swap",
"swap2Type": "swap",
"swap3Type": "swap",
"msgProperty": "payload",
"msgPropertyType": "str",
"resultType": "value",
"resultTypeType": "output",
"multipleResult": false,
"fanOutMultipleResult": false,
"setTopic": true,
"outputs": 1,
"x": 470,
"y": 2280,
"wires": [
[
"fe721ef316ce2431"
]
]
},
{
"id": "4273b3319d082ee0",
"type": "modbus-getter",
"z": "43643082ec7e300c",
"name": "37113",
"showStatusActivities": false,
"showErrors": false,
"logIOActivities": false,
"unitid": "1",
"dataType": "HoldingRegister",
"adr": "37113",
"quantity": "2",
"server": "70220ecd.1ca1e",
"useIOFile": false,
"ioFile": "",
"useIOForPayload": false,
"emptyMsgOnFail": false,
"keepMsgProperties": false,
"x": 290,
"y": 2280,
"wires": [
[
"eafde78ee735f583"
],
[
"01d1b3c7dc289c7f"
]
]
},
{
"id": "01d1b3c7dc289c7f",
"type": "modbus-getter",
"z": "43643082ec7e300c",
"name": "37001",
"showStatusActivities": false,
"showErrors": false,
"logIOActivities": false,
"unitid": "1",
"dataType": "HoldingRegister",
"adr": "37001",
"quantity": "2",
"server": "70220ecd.1ca1e",
"useIOFile": false,
"ioFile": "",
"useIOForPayload": false,
"emptyMsgOnFail": false,
"keepMsgProperties": false,
"x": 290,
"y": 2360,
"wires": [
[
"ceb2f6cd6d3e1f74"
],
[
"fefb6e6db0337e66"
]
]
},
{
"id": "ceb2f6cd6d3e1f74",
"type": "buffer-parser",
"z": "43643082ec7e300c",
"name": "",
"data": "payload",
"dataType": "msg",
"specification": "spec",
"specificationType": "ui",
"items": [
{
"type": "int32be",
"name": "Battery Charging",
"offset": 0,
"length": 1,
"offsetbit": 0,
"scale": "1",
"mask": ""
}
],
"swap1": "",
"swap2": "",
"swap3": "",
"swap1Type": "swap",
"swap2Type": "swap",
"swap3Type": "swap",
"msgProperty": "payload",
"msgPropertyType": "str",
"resultType": "value",
"resultTypeType": "output",
"multipleResult": false,
"fanOutMultipleResult": false,
"setTopic": true,
"outputs": 1,
"x": 470,
"y": 2360,
"wires": [
[
"d2bf14d65d271a2b"
]
]
},
{
"id": "d2bf14d65d271a2b",
"type": "calculator",
"z": "43643082ec7e300c",
"name": "",
"inputMsgField": "payload",
"outputMsgField": "payload",
"operation": "div",
"constant": "1",
"round": true,
"decimals": "0",
"x": 630,
"y": 2360,
"wires": [
[
"16e34fcea77299b7",
"d04dfd81845f0670",
"edcc896017129dd7"
]
]
},
{
"id": "fefb6e6db0337e66",
"type": "modbus-getter",
"z": "43643082ec7e300c",
"name": "37004",
"showStatusActivities": false,
"showErrors": false,
"logIOActivities": false,
"unitid": "1",
"dataType": "HoldingRegister",
"adr": "37004",
"quantity": "1",
"server": "70220ecd.1ca1e",
"useIOFile": false,
"ioFile": "",
"useIOForPayload": false,
"emptyMsgOnFail": false,
"keepMsgProperties": false,
"x": 290,
"y": 2420,
"wires": [
[
"4de4701af5175cc7"
],
[
"b88b6574d56ef461"
]
]
},
{
"id": "4de4701af5175cc7",
"type": "buffer-parser",
"z": "43643082ec7e300c",
"name": "",
"data": "payload",
"dataType": "msg",
"specification": "spec",
"specificationType": "ui",
"items": [
{
"type": "uint16be",
"name": "Battery SOC",
"offset": 0,
"length": 1,
"offsetbit": 0,
"scale": "1",
"mask": ""
}
],
"swap1": "",
"swap2": "",
"swap3": "",
"swap1Type": "swap",
"swap2Type": "swap",
"swap3Type": "swap",
"msgProperty": "payload",
"msgPropertyType": "str",
"resultType": "value",
"resultTypeType": "output",
"multipleResult": false,
"fanOutMultipleResult": false,
"setTopic": true,
"outputs": 1,
"x": 470,
"y": 2420,
"wires": [
[
"6a965186ad6d3025"
]
]
},
{
"id": "6a965186ad6d3025",
"type": "calculator",
"z": "43643082ec7e300c",
"name": "",
"inputMsgField": "payload",
"outputMsgField": "payload",
"operation": "div",
"constant": "10",
"round": true,
"decimals": "1",
"x": 630,
"y": 2420,
"wires": [
[
"570deb8c6dd59d98",
"3ce3a1626ffcad72",
"2764b5e90fe10f8f"
]
]
},
{
"id": "bf0919fb75e9424d",
"type": "comment",
"z": "43643082ec7e300c",
"name": "Battery",
"info": "",
"x": 110,
"y": 2380,
"wires": []
},
{
"id": "107145cec1d3e177",
"type": "debug",
"z": "43643082ec7e300c",
"name": "meter power",
"active": false,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "true",
"targetType": "full",
"statusVal": "",
"statusType": "auto",
"x": 810,
"y": 2280,
"wires": []
},
{
"id": "3e9af4313968d8e7",
"type": "inject",
"z": "43643082ec7e300c",
"name": "",
"props": [
{
"p": "payload"
},
{
"p": "topic",
"vt": "str"
}
],
"repeat": "30",
"crontab": "",
"once": true,
"onceDelay": "10",
"topic": "",
"payloadType": "date",
"x": 170,
"y": 2220,
"wires": [
[
"4273b3319d082ee0"
]
]
},
{
"id": "f2c43b3f9855a2d2",
"type": "debug",
"z": "43643082ec7e300c",
"name": "active power",
"active": false,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "true",
"targetType": "full",
"statusVal": "",
"statusType": "auto",
"x": 810,
"y": 2480,
"wires": []
},
{
"id": "16e34fcea77299b7",
"type": "debug",
"z": "43643082ec7e300c",
"name": "battery flow",
"active": false,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "true",
"targetType": "full",
"statusVal": "",
"statusType": "auto",
"x": 810,
"y": 2360,
"wires": []
},
{
"id": "570deb8c6dd59d98",
"type": "debug",
"z": "43643082ec7e300c",
"name": "battery state",
"active": false,
"tosidebar": true,
"console": false,
"tostatus": false,
"complete": "true",
"targetType": "full",
"statusVal": "",
"statusType": "auto",
"x": 810,
"y": 2420,
"wires": []
},
{
"id": "70220ecd.1ca1e",
"type": "modbus-client",
"name": "WLAN-FE",
"clienttype": "tcp",
"bufferCommands": true,
"stateLogEnabled": false,
"queueLogEnabled": false,
"tcpHost": "192.168.0.34",
"tcpPort": "502",
"tcpType": "DEFAULT",
"serialPort": "/dev/ttyUSB",
"serialType": "RTU-BUFFERD",
"serialBaudrate": "9600",
"serialDatabits": "8",
"serialStopbits": "1",
"serialParity": "none",
"serialConnectionDelay": "100",
"serialAsciiResponseStartDelimiter": "",
"unit_id": 1,
"commandDelay": 1,
"clientTimeout": 5000,
"reconnectOnTimeout": false,
"reconnectTimeout": 2000,
"parallelUnitIdsAllowed": true
}
] |
|
I have an old SDongle-A01 that apparently can't do Modbus TCP. I'm not using the cloud anyway. |
|
"I think it calls home to the EMEA servers occasionally." The SUN2000 backup box is really dumb. At best it closes a relay that shorts two of the modbus lines. |
|
Here's my script using modbus bridge to get values into MQTT and InfluxDB. Text values are commented out because I'm decoding in Grafana, which saves memory on ESP8266. Note this uses gemu's ScriptEditor. 
Note that this is different from the first pic I posted. Tx goes to Tx and Rx goes to Rx.
|
|
Thank you for the fast reply. The code would be helpfull thank you. Now waiting for the connector to arrive. |
|
Its not yet working for me. Can you help me ? The picture of the sun2000 connection is that looking up at the inverter. |
|
Sorry, you should be using pin 1 and 2 for your connector. Here is a script i use with a 33ktl to write a register that derates power to a specific register: Key section is here: A sml scripting function that lets you write a register. I have it in the >S section so each second it checks if I've changed the http://192.168.3.8/cm?cmnd=script%20%3Ederateto=200 
So in essence I schedule the system to push 20% of rated power starting at 8am, and then switch to 100% (1000) at 2pm. For battery control, you just need to find which registers control the battery settings and write to those. What battery do you have? |
|
I am using an ESP32. The console mentions that it is using uart 2. I will try connecting to pins 16 and 17. |
|
I mean pin 1 and 2 on the Huawei connector. For the ESP32 yes you would connect the RS485 adapter to 16 and 17, and then declare that correctly in your SML script. i.e. change the meter description line to: |
|
Smart meter script for Huawei SUN2000-10KTL is as follows. Not all registers are read, just the important ones: |
|
Can you please post the fully working solution? I am also interested in
that… thx
pkkrusty ***@***.***> schrieb am Mi. 28. Juni 2023 um 18:30:
… Ah got it. The meter number in the line below was wrong. Now it's working.
—
Reply to this email directly, view it on GitHub
<#18917 (reply in thread)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAA3R4GG5N2XKAKGOSCV4LTXNRL35ANCNFSM6AAAAAAZM6DQX4>
.
You are receiving this because you commented.Message ID:
***@***.***>
|
|
Not sure what you mean. Post above yours has the >M section of the script that works correctly. All you need to add is above it in the script window. |
|
@pkkrusty thanks for your Work! With great help, I am on the way to evaluating the Huawei system with Tasmota via Modbus TCP. I already get the default values. ,502,HUAWEI,0,10,r01037D100004,01037D00,01037D08,01037D40,r01037D450003,r01037D48000A,01037D55,01037D57,01037D59,01037D6A,01037D72 1,010308SSss@i0:10,PV1 Voltage,V,PV1_Voltage,1 Since I still can't understand the Huawei numbers via the app, I now want to bring together as many values as possible from the inverter and the battery. How do I get the other report sizes? Sorry for my bad English, I'm from Germany. |
|
Which model inverter do you have? Usually the Modbus registers are published in the manual, and it is simple to add more lines to get battery data. |
|
thanks for the very fast answer! SUN2000-10KTL-M1 (10 kwp) with LUNA2000 (5kwh) I admit that I didn't understand the first line or how to complete the list. https://support.huawei.com/enterprise/en/doc/EDOC1100050690 (only info: That's exactly my problem and I would like to help make the Huawei numbers easier to coordinate and explain: |
|
This document looks like the latest modbus info for the inverter. I haven't seen anything online about communicating with the battery module. It will take some time to look at and understand the code for new lines. If for example, you want to read register 184 (Total DC Input Power), you would add 0103 (modbus device 01, read a register is code 03, then the hex representation of register 32108 which is 7D6C, so you would add 01037D6C and then add a line below to parse it. So... ,502,HUAWEI,0,10,r01037D100004,01037D00,01037D08,01037D40,r01037D450003,r01037D48000A,01037D55,01037D57,01037D59,01037D6A,01037D72 ,01037D6C (Note you could also write r01037D6C0002, which would be the same thing. Default is 2 16-bit registers) 1,010308SSss@i0:10,PV1 Voltage,V,PV1_Voltage,1 |
|
Looks like battery info is in the 37000 registers... From this document: Huawei documents are not very consistent. |
|
This example helped me a lot in understanding! |
|
Hi @pkkrusty , I'm making little good steps in my Tasmota project. However, I was told that you shouldn't overload the modbus. I get the values into Tasmota via “M” and not under “S”. Can I have any influence at all? How stable is the Modbus and do I have to be careful? |
|
I think using the smart meter approach (>M section) is better. If you can consolidate the register reads, that saves some bandwidth/time also. i.e. reading 10 registers at once, then breaking them out line by line like my example, then you only have one header and one crc for all 10 registers. In the example, I read about 600 bits of data, which at 9600bps, only takes 62 milliseconds. That should leave plenty of time for other operations inside the Huawei. I don't think it will get overloaded before the ESP device does. Where is your reference to not overload the modbus? Maybe people smarter than me know a limit. |
|
Hi - I am in contact with 2000ede and reported about my solution to read SUN-Modbus data with an ESP32, programmed in C++ and showing results on a 1.8' LDC display. I always send 6 read commands, with different tokens and of different parameter area lengths (4, 2, 8, 2, 7, 10 words of data). Then I wait for the 6 responses - that I identify by the tokens. This takes from my experience 2...4 sec. I assume this mainly caused by processing the data from the sun inverter. I assume that this is not limited by the modbus-load, but I have no measurement results of the modbus load, as I use Modbus TCP and do not measure the modbus directly. |
|
one question: what is the difference between "M" and "S" section? |
|
Ah ok, there's a big difference between direct Modbus and Modbus TCP. The latter is dealing with extra network layers and network latency. However, I have used the Modbus TCP feature in scripting with some fronius inverters and can read quite a bit before it gets unstable. ">M section is specific to smart meters. >S loops once per second and can include any code. I used Modbus bridge driver initially to pull one register per second, then I figured out the smart meter section and switched to that. |
|
Now I got the info, so the interval is also possible under M: In the first line there is the parameter transmission interval (here 10) +1,....,m,0,502,mod1,1,10,r01039C870015 |
|
Hello,
|
|
Are you reading from the Huawei via Modbus TCP? Or regular Modbus via RS485 adapter? I have never seen wrong readings with regular Modbus. |
|
Modbus TCP
1,010308SSss@i0:10,PV1 DC Spannung,V,PV1_Voltage,1 |
Here's my script using modbus bridge to get values into MQTT and InfluxDB. Text values are commented out because I'm decoding in Grafana, which saves memory on ESP8266. Note this uses gemu's ScriptEditor.
In userconfig_override, I have the following defines: