Die Verbindung wurde nur einmal erfolgreich hergestellt.
Die folgenden Versuche schlugen fehl, allerdings ohne eine Fehlermeldung?
Code: Alles auswählen
29.03. 00:31:01 |---------------- Start sungrow.php --------------------------
29.03. 00:31:01 -Sungrow: localhost Port: 9000 GeräteID: 1
29.03. 00:31:01 + -Die Daten werden ausgelesen...
29.03. 00:31:01 -Firmware: ARM_SAPPHIRE-H_V11_V01_B
29.03. 00:31:01 -Seriennummer: ...
29.03. 00:31:02 -ModellGruppe: SH
29.03. 00:31:10 -Lesefehler => Ausgang.
29.03. 00:31:10 |---------------- Stop sungrow.php --------------------------
29.03. 00:32:02 |---------------- Start sungrow.php --------------------------
29.03. 00:32:02 -Sungrow: localhost Port: 9000 GeräteID: 1
29.03. 00:32:02 + -Die Daten werden ausgelesen...
29.03. 00:32:09 -Lesefehler => Ausgang.
29.03. 00:32:09 |---------------- Stop sungrow.php --------------------------
Code: Alles auswählen
sudo journalctl --unit mproxy
Code: Alles auswählen
Mar 29 00:25:00 pinas systemd[1]: Started mproxy.service - Modbus-Proxy.
Mar 29 00:25:00 pinas modbus-proxy[130681]: 2024-03-29 00:25:00,316 INFO modbus-proxy: Starting...
Mar 29 00:25:00 pinas modbus-proxy[130681]: 2024-03-29 00:25:00,323 INFO modbus-proxy.ModBus(192.168.178.45:502): Ready to accept requests on 0:9000
Mar 29 00:31:01 pinas modbus-proxy[130681]: 2024-03-29 00:31:01,256 INFO modbus-proxy.Client(127.0.0.1:57238): new client connection
Mar 29 00:31:01 pinas modbus-proxy[130681]: 2024-03-29 00:31:01,256 INFO modbus-proxy.ModBus(192.168.178.45:502): connecting to modbus...
Mar 29 00:31:01 pinas modbus-proxy[130681]: 2024-03-29 00:31:01,260 INFO modbus-proxy.ModBus(192.168.178.45:502): connected!
Mar 29 00:31:01 pinas modbus-proxy[130681]: 2024-03-29 00:31:01,260 INFO modbus-proxy.ModBus(192.168.178.45:502): delay after connect: 0.1
Mar 29 00:31:10 pinas modbus-proxy[130681]: 2024-03-29 00:31:10,837 INFO modbus-proxy.Client(127.0.0.1:57238): client closed connection
Mar 29 00:31:10 pinas modbus-proxy[130681]: 2024-03-29 00:31:10,837 INFO modbus-proxy.Client(127.0.0.1:57238): closing connection...
Mar 29 00:31:10 pinas modbus-proxy[130681]: 2024-03-29 00:31:10,838 INFO modbus-proxy.Client(127.0.0.1:57238): connection closed
Mar 29 00:32:02 pinas modbus-proxy[130681]: 2024-03-29 00:32:02,092 INFO modbus-proxy.Client(127.0.0.1:49480): new client connection
Mar 29 00:32:09 pinas modbus-proxy[130681]: 2024-03-29 00:32:09,337 INFO modbus-proxy.Client(127.0.0.1:49480): client closed connection
Mar 29 00:32:09 pinas modbus-proxy[130681]: 2024-03-29 00:32:09,338 INFO modbus-proxy.Client(127.0.0.1:49480): closing connection...
Mar 29 00:32:09 pinas modbus-proxy[130681]: 2024-03-29 00:32:09,338 INFO modbus-proxy.Client(127.0.0.1:49480): connection closed
Mar 29 00:33:01 pinas modbus-proxy[130681]: 2024-03-29 00:33:01,582 INFO modbus-proxy.Client(127.0.0.1:55966): new client connection
Mar 29 00:33:08 pinas modbus-proxy[130681]: 2024-03-29 00:33:08,827 INFO modbus-proxy.Client(127.0.0.1:55966): client closed connection
Mar 29 00:33:08 pinas modbus-proxy[130681]: 2024-03-29 00:33:08,828 INFO modbus-proxy.Client(127.0.0.1:55966): closing connection...
Mar 29 00:33:08 pinas modbus-proxy[130681]: 2024-03-29 00:33:08,829 INFO modbus-proxy.Client(127.0.0.1:55966): connection closed
Was kann das sein?
Ein Problem mit den Parametern in der yaml-Konfigurationsdatei?
Code: Alles auswählen
hru@pinas:~ $ cat /usr/lib/modbus-proxy/mproxy-conf.yaml
devices:
- modbus:
url: 192.168.178.45:502 # device url (mandatory): WLAN-Eingang SH10RT (Winet-S)
timeout: 10 # communication timeout (s) (optional, default: 10)
connection_time: 0.1 # delay after connection (s) (optional, default: 0)
listen:
bind: 0:9000 # listening address (mandatory)
Vielen Dank vorab für Eure Unterstützung
Gruß Hartmut