JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.
-
@homoran sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
auch wenn (oder gerade weil) du nur ein Register haben willst, stell mal in den Grundeinstellungen die Anzahl gepollte Register auf einen niedrigen Wert.
Habe ich auch getestet habe die Werte auf die Hälfte eingestellt.
modbus.5 2025-03-07 10:01:01.501 debug Closing client on purpose. modbus.5 2025-03-07 10:01:00.499 debug Cleaning up request fifo. modbus.5 2025-03-07 10:01:00.499 debug Clearing timeout of the current request. modbus.5 2025-03-07 10:01:00.499 debug Socket closed with error modbus.5 2025-03-07 10:01:00.491 info Disconnected from slave 192.168.1.146 modbus.5 2025-03-07 10:01:00.491 debug Closing client on purpose. modbus.5 2025-03-07 10:01:00.441 warn [DevID_1] Poll error count: 6 code: "App Timeout" modbus.5 2025-03-07 10:00:55.314 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:00:55.241 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:00:55.241 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:00:54.189 warn [DevID_1] Poll error count: 5 code: "App Timeout" modbus.5 2025-03-07 10:00:49.053 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:00:48.988 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:00:48.988 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:00:47.938 warn [DevID_1] Poll error count: 4 code: "App Timeout" modbus.5 2025-03-07 10:00:42.840 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:00:42.737 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:00:42.737 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:00:41.686 warn [DevID_1] Poll error count: 3 code: "App Timeout" modbus.5 2025-03-07 10:00:36.577 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:00:36.485 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:00:36.485 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:00:35.434 warn [DevID_1] Poll error count: 2 code: "App Timeout" modbus.5 2025-03-07 10:00:30.313 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:00:30.233 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:00:30.233 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:00:29.182 warn [DevID_1] Poll error count: 1 code: "App Timeout" modbus.5 2025-03-07 10:00:24.100 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:00:23.981 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:00:23.981 debug Initialization of scale factors done! modbus.5 2025-03-07 10:00:23.981 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:00:23.980 info Connected to slave 192.168.1.146 modbus.5 2025-03-07 10:00:23.886 debug Add holdingRegisters.4752_Total_Battery_Voltage: {"_id":"holdingRegisters.4752_Total_Battery_Voltage","type":"state","common":{"name":"bat vol","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"mV"},"native":{"regType":"holdingRegs","address":4752,"deviceId":1,"type":"uint32be","len":2,"offset":0,"factor":1,"poll":true}} modbus.5 2025-03-07 10:00:23.885 debug Initialize Objects for holdingRegs: [{"_address":"4752","name":"Total Battery Voltage","description":"bat vol","unit":"mV","type":"uint32be","len":2,"factor":1,"offset":0,"formula":"","role":"value","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":1,"address":4752,"id":"holdingRegisters.4752_Total_Battery_Voltage"}] modbus.5 2025-03-07 10:00:23.885 debug Initialize Objects for inputRegs: [] modbus.5 2025-03-07 10:00:23.885 debug Initialize Objects for coils: [] modbus.5 2025-03-07 10:00:23.885 debug Initialize Objects for disInputs: [] modbus.5 2025-03-07 10:00:23.828 info starting. Version 6.3.2 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.18.3, js-controller: 7.0.6 modbus.5 2025-03-07 10:00:23.711 debug Plugin sentry Initialize Plugin (enabled=true) modbus.5 2025-03-07 10:00:19.818 info terminating modbus.5 2025-03-07 10:00:19.332 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason modbus.5 2025-03-07 10:00:19.332 debug Plugin sentry destroyed modbus.5 2025-03-07 10:00:19.332 info terminating modbus.5 2025-03-07 10:00:19.317 debug Closing client on purpose. modbus.5 2025-03-07 10:00:19.316 info Got terminate signal TERMINATE_YOURSELF modbus.5 2025-03-07 10:00:12.413 debug Closing client on purpose. modbus.5 2025-03-07 10:00:11.412 debug Cleaning up request fifo. modbus.5 2025-03-07 10:00:11.412 debug Clearing timeout of the current request. modbus.5 2025-03-07 10:00:11.412 debug Socket closed with error modbus.5 2025-03-07 10:00:11.404 info Disconnected from slave 192.168.1.146 modbus.5 2025-03-07 10:00:11.404 debug Closing client on purpose. modbus.5 2025-03-07 10:00:11.353 warn [DevID_1] Poll error count: 10 code: "App Timeout" modbus.5 2025-03-07 10:00:06.266 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:00:06.153 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:00:06.153 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:00:06.153 info Connected to slave 192.168.1.146 modbus.5 2025-03-07 09:59:07.158 debug Closing client on purpose. modbus.5 2025-03-07 09:59:06.158 debug Cleaning up request fifo. modbus.5 2025-03-07 09:59:06.158 debug Clearing timeout of the current request. modbus.5 2025-03-07 09:59:06.158 debug Socket closed with error modbus.5 2025-03-07 09:59:06.151 info Disconnected from slave 192.168.1.146 modbus.5 2025-03-07 09:59:06.151 debug Closing client on purpose. modbus.5 2025-03-07 09:59:06.100 warn [DevID_1] Poll error count: 9 code: "App Timeout" modbus.5 2025-03-07 09:59:00.997 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 09:59:00.901 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 09:59:00.900 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 09:59:00.900 info Connected to slave 192.168.1.146 -
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
auf die Hälfte eingestellt.
bitte auf 1 oder 2 stellen
es gibt Geräte die sich sonst aufhängen.Muss nicht die Ursache sein, würde ich gerne ausschließen
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4
wo steht der Parameter denn?
Hier
steht 0, nicht 4 -
modbus.5 2025-03-07 10:16:18.537 debug Closing client on purpose. modbus.5 2025-03-07 10:16:17.536 debug Cleaning up request fifo. modbus.5 2025-03-07 10:16:17.536 debug Clearing timeout of the current request. modbus.5 2025-03-07 10:16:17.536 debug Socket closed with error modbus.5 2025-03-07 10:16:17.531 info Disconnected from slave 192.168.1.146 modbus.5 2025-03-07 10:16:17.531 debug Closing client on purpose. modbus.5 2025-03-07 10:16:17.480 warn [DevID_1] Poll error count: 6 code: "App Timeout" modbus.5 2025-03-07 10:16:12.369 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:16:12.279 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:16:12.279 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:16:11.228 warn [DevID_1] Poll error count: 5 code: "App Timeout" modbus.5 2025-03-07 10:16:06.105 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:16:06.027 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:16:06.027 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:16:04.975 warn [DevID_1] Poll error count: 4 code: "App Timeout" modbus.5 2025-03-07 10:15:59.843 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:15:59.775 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:15:59.775 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:15:58.724 warn [DevID_1] Poll error count: 3 code: "App Timeout" modbus.5 2025-03-07 10:15:53.629 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:15:53.523 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:15:53.523 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:15:52.471 warn [DevID_1] Poll error count: 2 code: "App Timeout" modbus.5 2025-03-07 10:15:47.365 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:15:47.270 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:15:47.270 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:15:46.219 warn [DevID_1] Poll error count: 1 code: "App Timeout" modbus.5 2025-03-07 10:15:41.103 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4 modbus.5 2025-03-07 10:15:41.019 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:15:41.019 debug Initialization of scale factors done! modbus.5 2025-03-07 10:15:41.018 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:15:41.018 info Connected to slave 192.168.1.146 modbus.5 2025-03-07 10:15:40.927 debug Add holdingRegisters.4752_Total_Battery_Voltage: {"_id":"holdingRegisters.4752_Total_Battery_Voltage","type":"state","common":{"name":"bat vol","role":"value","type":"number","read":true,"write":true,"def":0,"unit":"mV"},"native":{"regType":"holdingRegs","address":4752,"deviceId":1,"type":"uint32be","len":2,"offset":4,"factor":1,"poll":true}} modbus.5 2025-03-07 10:15:40.927 debug Initialize Objects for holdingRegs: [{"_address":"4752","name":"Total Battery Voltage","description":"bat vol","unit":"mV","type":"uint32be","len":2,"factor":1,"offset":4,"formula":"","role":"value","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":1,"address":4752,"id":"holdingRegisters.4752_Total_Battery_Voltage"}] modbus.5 2025-03-07 10:15:40.927 debug Initialize Objects for inputRegs: [] modbus.5 2025-03-07 10:15:40.927 debug Initialize Objects for coils: [] modbus.5 2025-03-07 10:15:40.927 debug Initialize Objects for disInputs: [] modbus.5 2025-03-07 10:15:40.874 info starting. Version 6.3.2 in /opt/iobroker/node_modules/iobroker.modbus, node: v20.18.3, js-controller: 7.0.6 modbus.5 2025-03-07 10:15:40.764 debug Plugin sentry Initialize Plugin (enabled=true) modbus.5 2025-03-07 10:15:36.922 info terminating modbus.5 2025-03-07 10:15:36.437 info Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason modbus.5 2025-03-07 10:15:36.437 debug Plugin sentry destroyed modbus.5 2025-03-07 10:15:36.437 info terminating modbus.5 2025-03-07 10:15:36.422 debug Closing client on purpose. modbus.5 2025-03-07 10:15:36.422 info Got terminate signal TERMINATE_YOURSELFSehr komisch alles, habe mit Modbus noch nie Probleme gehabt. Habe alle SMA Wechselrichter drin plus Energiezähler von EASTRoN und Heidelberg Ladestation die funktionieren super.
-
Ich habe zum Test jetzt auch mal noch ein ELFIN RS485 Adapter probiert aber auch hier das selbe
-
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
2025-03-07 10:15:40.927 debug Initialize Objects for holdingRegs: [{"_address":"4752","name":"Total Battery Voltage","description":"bat vol","unit":"mV","type":"uint32be","len":2,"factor":1,"offset":4,"formula":"","role":"value","room":"","poll":true,"wp":false,"cw":false,"isScale":false,"deviceId":1,"address":4752,"id":"holdingRegisters.4752_Total_Battery_Voltage"}]wo kommt der offset 4 her?
edit!
hast du den in der Zwischenzeit eingestellt?
Warum?Das ist im Moment der einzige Fehler
-
@homoran sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
Hier
steht 0, nicht 4
Ich habe es so verstanden das ich den so einstellen soll
Sorry -
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
das ich den so einstellen soll
nein!
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
2025-03-07 10:00:55.314 warn Error in handler for 3: RangeError [ERR_OUT_OF_RANGE]: The value of "offset" is out of range. It must be >= 0 and <= 3. Received 4
-
Ich habe den ZLAN wieder angeschlossen und offset auf 0
modbus.5 2025-03-07 10:47:53.458 info Disconnected from slave 192.168.1.123 modbus.5 2025-03-07 10:47:53.458 debug Closing client on purpose. modbus.5 2025-03-07 10:47:52.457 debug Cleaning up request fifo. modbus.5 2025-03-07 10:47:52.457 debug Clearing timeout of the current request. modbus.5 2025-03-07 10:47:52.457 debug Socket closed with error modbus.5 2025-03-07 10:47:52.457 warn [DevID_1] Poll error count: 7 code: {"err":"timeout","timeout":5000} modbus.5 2025-03-07 10:47:52.456 error Client in error state. modbus.5 2025-03-07 10:47:52.456 error Request timed out. modbus.5 2025-03-07 10:47:52.456 warn Error: undefined modbus.5 2025-03-07 10:47:47.456 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 10:47:47.456 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 10:47:47.456 info Connected to slave 192.168.1.123 -
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
2025-03-07 10:47:52.456 warn Error: undefinedmacht keinen Spaß
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
den ZLAN
ist was?
gibt es da was einzustellen, was nicht zu den Adapter Einstellungen oder WR Einstellungen passt? -
@wendy2702 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
RMMS (Radzio Modbus Master Simulator
Den habe ich mal runtergeladen, aber da passiert überhaupt nichts habe die verbindung über den usb und den tcp Adapter probiert unten bei TX RX passiert nichts.
Mit dem Programm vom JK BMS klappt die Verbindung mit dem usb Adapter einwandfrei.
-
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
mit dem usb Adapter
den sollte man immer nehmen, wenn möglich.
Einen TCP2RS485 Konverter zwischenzuschalten bringt immer weitere Fehlermöglichkeiten mit sich -
@homoran sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
den ZLAN
Das ist der ZLAN RS485 Adapter hier im Screenshot alle Einstellungen.
-
@homoran sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
Einen TCP2RS485 Konverter zwischenzuschalten bringt immer weitere Fehlermöglichkeiten mit sich
Ja, habe aber keine andere Möglichkeit da die Technik der PV Batterie in der Garage ist
-
Kann es sein das etwas mit der Adresse nicht stimmt ? Sollte man mal eine andere her nehmen?
Habe auch nicht verstanden warum wir jetzt die Adresse um die Spannung abzufragen in holding eingetragen haben, dachte holding ist nur um Werte zu setzen? -
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
@homoran sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
den ZLAN
Das ist der ZLAN RS485 Adapter hier im Screenshot alle Einstellungen.
Damit kenne ich ich gar nicht aus, aber
-
@homoran sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
Damit kenne ich ich gar nicht aus, aber
Ich habe das als DNS interpretiert falls man den Adapter von aussen erreichen möchte? Habe allerdings auch schon die IP vom ioBroker eingetragen gehabt.
Konnte kein unterschied feststellen...
-
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
warum wir jetzt die Adresse um die Spannung abzufragen in holding eingetragen haben
weil es so in deiner Anleitung steht.
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
dachte holding ist nur um Werte zu setzen?
da halten sich aber leider viele Hersteller nicht dran
-
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
Habe allerdings auch schon die IP vom ioBroker eingetragen gehabt.
was stand dann im log?
-
@homoran sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
dachte holding ist nur um Werte zu setzen?
Alles klar, verstanden
hier nochmal der log mit eingetragener io ip bei destination:
modbus.5 2025-03-07 11:06:47.158 info Disconnected from slave 192.168.1.123 modbus.5 2025-03-07 11:06:47.157 debug Closing client on purpose. modbus.5 2025-03-07 11:06:46.157 debug Cleaning up request fifo. modbus.5 2025-03-07 11:06:46.157 debug Clearing timeout of the current request. modbus.5 2025-03-07 11:06:46.157 debug Socket closed with error modbus.5 2025-03-07 11:06:46.156 warn [DevID_1] Poll error count: 2 code: {"err":"timeout","timeout":5000} modbus.5 2025-03-07 11:06:46.156 error Client in error state. modbus.5 2025-03-07 11:06:46.156 error Request timed out. modbus.5 2025-03-07 11:06:46.156 warn Error: undefined modbus.5 2025-03-07 11:06:41.156 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 11:06:41.155 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 11:06:40.327 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.327 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.104 warn [DevID_1] Poll error count: 1 code: "ReadHoldingRegisters: Invalid FC 13" modbus.5 2025-03-07 11:06:40.104 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.104 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.104 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.104 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.104 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.103 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.103 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.103 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:40.103 warn Error in handler for 3: RangeError [ERR_BUFFER_OUT_OF_BOUNDS]: Attempt to access memory outside buffer bounds modbus.5 2025-03-07 11:06:39.740 debug [DevID_1/holdingRegs] Poll address 4752 - 2 registers modbus.5 2025-03-07 11:06:39.740 debug Initialization of scale factors done! modbus.5 2025-03-07 11:06:39.739 debug [DevID_1] Poll start --------------------- modbus.5 2025-03-07 11:06:39.739 info Connected to slave 192.168.1.123 -
@elektroniker86 sagte in JK BMS mit Modbus Adapter über RS485 zu TCP einbinden.:
Invalid FC 13
ich hab keine Ahnung wo der herkommt
es gibt anscheinend wirklich keinen FC13auch der buffer error ist wieder da
