Sigenstor Modbus
-
Moin,
habe seit heute die PV in Betrieb und verzweifel ein wenig an Modbus ( mal wieder ).
Modbus im Inverter ist aktiv und eigentlich ist alles Dokumentiert, bekomme aber nur:2025-05-20 17:27:52.763 warn [DevID_1] Poll error count: 2 code: {"errorCode":132,"exceptionCode":2,"message":"ILLEGAL DATA ADDRESS"}MOD-EDIT: Code in code-tags gesetzt!
Vielleicht mag mir ja jemand auf die Sprünge helfen.
Doku ->
Meine Settings ->
Ich könnte mir zwar hintenrum die Daten über HA holen, das würde ich mir aber gerne ersparen.
Matze -
@matzebhv sagte in Sigenstor Modbus:
bekomme aber nur
bitte debug log!
@matzebhv sagte in Sigenstor Modbus:
Meine Settings ->
Master wäre mMn falsch.
ich hab da gar nicht stehen
Geräte ID ist wirklich
1?keine ALIASES benutzen, wenn du schon 30003 nutzst!
-
2 62 Log-Größe: 3.3 MB 1 Zeit debug Nachricht alexa2.0 2025-05-20 18:23:51.731 info Alexa-Push-Connection (macDms = true) established. Disable Polling alexa2.0 2025-05-20 18:23:50.440 info Alexa-Push-Connection disconnected - retry: Retry Connection in 1s modbus.0 2025-05-20 18:23:42.875 debug Closing client on purpose. modbus.0 2025-05-20 18:23:41.874 debug Cleaning up request fifo. modbus.0 2025-05-20 18:23:41.874 debug Socket closed with error modbus.0 2025-05-20 18:23:41.855 info Disconnected from slave 192.168.178.39 modbus.0 2025-05-20 18:23:41.855 debug Closing client on purpose. modbus.0 2025-05-20 18:23:41.804 warn [DevID_1] Poll error count: 6 code: {"errorCode":132,"exceptionCode":2,"message":"ILLEGAL DATA ADDRESS"} modbus.0 2025-05-20 18:23:41.804 debug Received pdu describes an error. modbus.0 2025-05-20 18:23:41.668 debug [DevID_1/inputRegs] Poll address 30003 - 1 registers modbus.0 2025-05-20 18:23:41.668 debug [DevID_1] Poll start --------------------- modbus.0 2025-05-20 18:23:40.617 warn [DevID_1] Poll error count: 5 code: {"errorCode":132,"exceptionCode":2,"message":"ILLEGAL DATA ADDRESS"} modbus.0 2025-05-20 18:23:40.617 debug Received pdu describes an error. modbus.0 2025-05-20 18:23:40.508 debug [DevID_1/inputRegs] Poll address 30003 - 1 registers modbus.0 2025-05-20 18:23:40.507 debug [DevID_1] Poll start --------------------- modbus.0 2025-05-20 18:23:39.456 warn [DevID_1] Poll error count: 4 code: {"errorCode":132,"exceptionCode":2,"message":"ILLEGAL DATA ADDRESS"} modbus.0 2025-05-20 18:23:39.456 debug Received pdu describes an error. modbus.0 2025-05-20 18:23:39.372 debug [DevID_1/inputRegs] Poll address 30003 - 1 registers modbus.0 2025-05-20 18:23:39.372 debug [DevID_1] Poll start --------------------- modbus.0 2025-05-20 18:23:38.320 warn [DevID_1] Poll error count: 3 code: {"errorCode":132,"exceptionCode":2,"message":"ILLEGAL DATA ADDRESS"} modbus.0 2025-05-20 18:23:38.320 debug Received pdu describes an error. modbus.0 2025-05-20 18:23:38.199 debug [DevID_1/inputRegs] Poll address 30003 - 1 registers modbus.0 2025-05-20 18:23:38.198 debug [DevID_1] Poll start --------------------- modbus.0 2025-05-20 18:23:37.148 warn [DevID_1] Poll error count: 2 code: {"errorCode":132,"exceptionCode":2,"message":"ILLEGAL DATA ADDRESS"} modbus.0 2025-05-20 18:23:37.148 debug Received pdu describes an error. modbus.0 2025-05-20 18:23:37.125 debug [DevID_1/inputRegs] Poll address 30003 - 1 registers modbus.0 2025-05-20 18:23:37.125 debug [DevID_1] Poll start --------------------- modbus.0 2025-05-20 18:23:36.074 warn [DevID_1] Poll error count: 1 code: {"errorCode":132,"exceptionCode":2,"message":"ILLEGAL DATA ADDRESS"} modbus.0 2025-05-20 18:23:36.073 debug Received pdu describes an error. modbus.0 2025-05-20 18:23:36.057 debug [DevID_1/inputRegs] Poll address 30003 - 1 registers modbus.0 2025-05-20 18:23:36.057 debug Initialization of scale factors done! modbus.0 2025-05-20 18:23:36.056 debug [DevID_1] Poll start --------------------- modbus.0 2025-05-20 18:23:36.055 info Connected to slave 192.168.178.39 modbus.0 2025-05-20 18:23:35.721 debug Initialize Objects for holdingRegs: [] modbus.0 2025-05-20 18:23:35.720 debug Add inputRegisters.30003_EMS_work_mode: {"_id":"inputRegisters.30003_EMS_work_mode","type":"state","common":{"name":"","role":"value","type":"number","read":true,"write":false,"def":0,"unit":""},"native":{"regType":"inputRegs","address":30003,"deviceId":1,"type":"uint16le","len":1,"offset":0,"factor":1}} modbus.0 2025-05-20 18:23:35.720 debug Initialize Objects for inputRegs: [{"_address":"30003","deviceId":1,"name":"EMS work mode","description":"","unit":"","type":"uint16le","len":1,"factor":1,"offset":0,"formula":"","role":"value","room":"","cw":"","isScale":"","address":30003,"id":"inputRegisters.30003_EMS_work_mode"}] modbus.0 2025-05-20 18:23:35.720 debug Initialize Objects for coils: [] modbus.0 2025-05-20 18:23:35.719 debug Initialize Objects for disInputs: [] modbus.0 2025-05-20 18:23:35.535 debug Schedule restart: 0 9 * * * modbus.0 2025-05-20 18:23:35.505 info starting. Version 6.4.0 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.19.2, js-controller: 7.0.7 modbus.0 2025-05-20 18:23:34.391 debug Plugin sentry Initialize Plugin (enabled=true) host.iOBroker 2025-05-20 18:23:33.286 info instance system.adapter.modbus.0 in version "6.4.0" started with pid 16220Der Inverter ist Slave, iobroker Master. Das sollte schon so passen.
ID ist 1 laut den Einstellungen im Inverter.
Alias aus hat leider keinen Unterschied gemacht. -
@matzebhv sagte in Sigenstor Modbus:
type":"uint16le
hat das e7nen Grund warum du little Endian nimmst?
hab ich auf dem Microfilm
leider vorher nicht erkannt -
@homoran
Oh man, jetzt gehts.
Außerdem muss für die Adressen im niedrigen Bereich die Slave-ID 247 eingestellt werden.
Für alle Sigenstor-User:
_address deviceId name description unit type len factor offset formula role room cw isScale 30554 1 Daily export energy kWh uint32be 2 0.01 0 level 30556 1 Accumulated export energy Total Energy produced kWh uint64be 4 0.01 0 level 30560 1 Daily import energy kWh uint32be 2 0.01 0 level 30566 1 Battery daily charge energy kWh uint32be 2 0.01 0 level 30568 1 Battery accumulated charge energy kWh uint64be 4 0.01 0 level 30572 1 Battery daily discharge energy kWh uint32be 2 0.01 0 level 30574 1 Battery accumulated discharge energy kWh uint64be 4 0.01 0 level 30587 1 Active power W int32be 2 0 0 level 30602 1 Battery State of Health Battery SOH % uint16be 1 0.1 0 level 31027 1 PV1 voltage String Nord Voltage V int16be 1 0.1 0 level 31028 1 PV1 current String Nord Current A int16be 1 0.01 0 level 31029 1 PV2 voltage String Sued Voltage V int16be 1 0.1 0 level 31030 1 PV2 current String Sued Current A int16be 1 0.01 0 level 31035 1 PV Power W int32be 2 0 0 level 30003 247 EMS work mode 0: max self consumption; 1:Sigen AI; 2:TOU, 7: Remote EMS uint16be 1 0 0 level 30005 247 Grid Active Power >0 buy from grid; <0 sell to grid W int32be 2 0.1 0 level 30009 247 On/Off Grid status 0: on grid; 1: off grid (auto); 2: off grid (manual) uint16be 1 0.1 0 level 30014 247 SOC Soc of system % uint16be 1 0.1 0 level 30015 247 L1 power Phase 1 power W int32be 2 0.1 0 level 30017 247 L2 power Phase 2 power W int32be 2 0.1 0 level 30019 247 L3 power Phase 3 power W int32be 2 0.1 0 level 30027 247 Alarm (General) If hybrid inverter has alaarm, this will be set int32be 2 0 0 level 30031 247 Plant active power W int32be 2 0 0 level 30033 247 Plant reactive power W int32be 2 0 0 level 30035 247 PV power PV Power from Roof kW int32be 2 0.001 0 level 30037 247 Battery Power <0: discharging; >0: charging W int32be 2 0 0 level 30052 247 Grid sensor L1 active power W int32be 2 0 0 level 30054 247 Grid sensor L2 active power W int32be 2 0 0 level 30056 247 Grid sensor L3 active power W int32be 2 0 0 level 30064 247 Max charging capacity kWh int32be 2 0.01 0 level 30066 247 Max discharging capacity kWh int32be 2 0.01 0 level 30068 247 ESS charging power kW int32be 2 0.001 0 level 30070 247 ESS discharging power kW int32be 2 0.001 0 level -
@matzebhv sagte in Sigenstor Modbus:
Oh man, jetzt gehts.
hast du nur den Haken gesetzt, oder uf das üblicherweise verwendete bigEndian umgestellt?
-
@homoran Erst auf Big Endian, das alleine hat nicht geholfen. Die Checkbox hat es dann zum fliegen gebracht.
