Hallo,
ich versuche eine Ochsner Air Hawk 518 WP in ioBroker über modbus TCP einzubinden.
Das ist mein erster Versuch mit Modbus. Hoffe jemand von Euch kann mir hier weiterhelfen.
Ich hatte bereits Kontakt mit dem Ochsner Support, die haben das dann auch auf der WP eingeschaltet und jetzt wird zumindest der Adapter in der ioBroker GUI grün. Allerdings kommen keine Werte von der WP am ioBroker an.
2023-11-17 12:28:54.295 - info: host.iobroker.home.local "system.adapter.modbus.0" enabled
2023-11-17 12:28:54.329 - info: host.iobroker.home.local instance system.adapter.modbus.0 started with pid 12626
2023-11-17 12:28:54.980 - debug: modbus.0 (12626) Redis Objects: Use Redis connection: 127.0.0.1:9001
2023-11-17 12:28:54.994 - debug: modbus.0 (12626) Objects client ready ... initialize now
2023-11-17 12:28:55.036 - debug: modbus.0 (12626) Objects create System PubSub Client
2023-11-17 12:28:55.037 - debug: modbus.0 (12626) Objects create User PubSub Client
2023-11-17 12:28:55.051 - debug: modbus.0 (12626) Objects client initialize lua scripts
2023-11-17 12:28:55.054 - debug: modbus.0 (12626) Objects connected to redis: 127.0.0.1:9001
2023-11-17 12:28:55.055 - silly: modbus.0 (12626) redis psubscribe cfg.o.system.user.*
2023-11-17 12:28:55.064 - silly: modbus.0 (12626) redis psubscribe cfg.o.enum.*
2023-11-17 12:28:55.064 - silly: modbus.0 (12626) objectDB connected
2023-11-17 12:28:55.066 - debug: modbus.0 (12626) Redis States: Use Redis connection: 127.0.0.1:9000
2023-11-17 12:28:55.112 - debug: modbus.0 (12626) States create System PubSub Client
2023-11-17 12:28:55.113 - debug: modbus.0 (12626) States create User PubSub Client
2023-11-17 12:28:55.161 - debug: modbus.0 (12626) States connected to redis: 127.0.0.1:9000
2023-11-17 12:28:55.161 - silly: modbus.0 (12626) statesDB connected
2023-11-17 12:28:55.175 - debug: modbus.0 (12626) Plugin sentry Initialize Plugin (enabled=true)
2023-11-17 12:28:55.352 - info: modbus.0 (12626) starting. Version 5.0.11 in /opt/iobroker/node_modules/iobroker.modbus, node: v16.20.2, js-controller: 5.0.16
2023-11-17 12:28:55.401 - silly: modbus.0 (12626) States system redis pmessage system.adapter.modbus.0.logLevel/system.adapter.modbus.0.logLevel:{"val":"silly","ack":true,"ts":1700220535395,"q":0,"from":"system.adapter.modbus.0","lc":1700065052244}
2023-11-17 12:28:55.416 - debug: modbus.0 (12626) Initialize Objects for disInputs: []
2023-11-17 12:28:55.417 - debug: modbus.0 (12626) Initialize Objects for coils: []
2023-11-17 12:28:55.417 - debug: modbus.0 (12626) Initialize Objects for inputRegs: [{"_address":"79","name":"","description":"","unit":"","type":"uint32be","len":2,"factor":1,"offset":0,"formula":"","role":"level","room":"","cw":false,"isScale":"","deviceId":1,"address":79,"id":"inputRegisters.79"}]
2023-11-17 12:28:55.417 - debug: modbus.0 (12626) Add inputRegisters.79: {"_id":"inputRegisters.79","type":"state","common":{"name":"","role":"level","type":"number","read":true,"write":false,"def":0,"unit":""},"native":{"regType":"inputRegs","address":79,"deviceId":1,"type":"uint32be","len":2,"offset":0,"factor":1}}
2023-11-17 12:28:55.417 - debug: modbus.0 (12626) Initialize Objects for holdingRegs: []
2023-11-17 12:28:55.536 - info: modbus.0 (12626) Connected to slave 192.168.0.213
2023-11-17 12:28:55.537 - debug: modbus.0 (12626) [DevID_1] Poll start ---------------------
2023-11-17 12:28:55.537 - debug: modbus.0 (12626) Initialization of scale factors done!
2023-11-17 12:28:55.537 - debug: modbus.0 (12626) [DevID_1/inputRegs] Poll address 79 - 2 registers
2023-11-17 12:28:55.541 - silly: modbus.0 (12626) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":false,"ack":true,"ts":1700220535535,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1700220528805}
2023-11-17 12:28:55.545 - debug: modbus.0 (12626) [DevID_1/inputRegs] Poll address 79 DONE
2023-11-17 12:28:55.550 - silly: modbus.0 (12626) States user redis pmessage modbus.0.*/modbus.0.info.connection:{"val":true,"ack":true,"ts":1700220535548,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1700220535548}
2023-11-17 12:28:55.552 - silly: modbus.0 (12626) States user redis pmessage modbus.0.*/modbus.0.inputRegisters.79:{"val":0,"ack":true,"ts":1700220535550,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1700220519087}
2023-11-17 12:28:55.631 - silly: modbus.0 (12626) States user redis pmessage modbus.0.*/modbus.0.info.pollTime:{"val":9,"ack":true,"ts":1700220535630,"q":0,"from":"system.adapter.modbus.0","user":"system.user.admin","lc":1700220535630}
2023-11-17 12:29:05.595 - debug: modbus.0 (12626) [DevID_1] Poll start ---------------------
2023-11-17 12:29:05.596 - debug: modbus.0 (12626) [DevID_1/inputRegs] Poll address 79 - 2 registers
2023-11-17 12:29:05.600 - debug: modbus.0 (12626) [DevID_1/inputRegs] Poll address 79 DONE
2023-11-17 12:29:15.652 - debug: modbus.0 (12626) [DevID_1] Poll start ---------------------
2023-11-17 12:29:15.653 - debug: modbus.0 (12626) [DevID_1/inputRegs] Poll address 79 - 2 registers
2023-11-17 12:29:15.657 - debug: modbus.0 (12626) [DevID_1/inputRegs] Poll address 79 DONE
Der Ochsner Support hat mir auch noch das angehängte Dokument geschickt. Da stehen die richtigen Register / Adressen drinnen die man verwenden sollte.
ZBH-Modbus OTS-DE02_20220725_Archiv.pdf
Wenn ich das richtig lese müßte Adresse 79 die Betriebsstunden der Verdichter anzeigen. Da bekomm ich aber immer 0 zurück. Ich hab das nat. auch schon mit so ziemlich allen anderen Adressen auch ausprobiert. Kommt immer 0 zurück.
Danke schonmal im vorhinein für jede Hilfe.
