Ankündigung

Einklappen

PLUGINS

Bitte im Titel immer zuerst den Namen des Plugins hinschreiben
Mehr anzeigen
Weniger anzeigen

Modbus Gateway

Einklappen
X
 
  • Filter
  • Zeit
  • Anzeigen
Alles löschen
neue Beiträge

  • #61
    Hi,

    ich geh mal davon aus dass 192.168.1.77 dein Miniserver ist. Zumindest wird davon mal ein request entgegen genommen und an den modbus geschickt, allerdings gibt es keine Antwort von deinem Gerät, weswegen er nach nem Timeout, das ganze nochmal probiert (insgesamt 3 mal).

    Nach dem wirklich gar keine Antworten kommen, kann es entweder ein Problem mit der Verkabelung oder mit der Adresse vom Gerät sein.

    Ich hoffe das bringt dich weiter.

    Kommentar


    • #62
      also einfach mal die Adern vom Modbus tauschen? Welche adresse müsste denn eingestellt werden?

      Kommentar


      • #63
        Laut Loxone hat der Zähler Standard mäßig, die 1 , wenn du das nicht zufällig geändert hast... Das muss dann auch so in der loxone Config hinterlegt sein. Wenn das alles passt und man am Gerät nichts weiter einstellen kann, würde ich auf blöd wirklich mal die Adern tauschen


        Gesendet von iPhone mit Tapatalk

        Kommentar


        • #64
          Hello Together,

          after setup a new Loxberry v2, I switched from the "Modbus Powermeter" (EOL) to the "Modbus Gateway". Everything works fine so far after a manual start of the interface on the plugin page. But after a reboot I get the same error as user "Coolms" and I need to make a manual "start" again:

          Hab heute von User zmata das Modbus PRE-RELEASE Gateway Plugin für V1 in der Wiki entdeckt. Beschreibung vom Autor und Download: http://www.loxwiki.eu/display/LOX


          Unfortunately I installed a fresh version of loxberry and modbus plugin and after the first reboot ..."Active: failed (Result: exit-code) since Tue 12/24/2019 19:25:23 CET; 19s ago"
          If I press "start" manually everything is ok.
          Where can I find the requested "systemd log" to help solving that issue?

          Greetings Stephan

          @zmata: Thank you very much for the great plugin!

          Kommentar


          • #65
            heisly Are you using Pre-Release 0.0.9 ?

            The systemd unit is derived from the USB device name. In my case it is: usb-1a86_5523-if00-port0
            This name is also printend in the plugins overview page, just before the "Start/Stop" Button.

            Using ssh you can check whether the daemon is running by:

            systemctl status mbusd@usb-1a86_5523-if00-port0.service

            For getting the log and the reason what went wrong do the following:

            journalctl -u mbusd@usb-1a86_5523-if00-port0.service

            I guess i also need to check whether i can integrate the systemd log into the plugin if this issue persists

            Dominik

            Kommentar


            • ogrimo30
              ogrimo30 kommentierte
              Kommentar bearbeiten
              I have the same problem with the Pre-Release 0.0.9

          • #66
            Hello Dominik,

            thanks for your reply. I'm still using 0.0.8. Do you think 0.0.9 may fix the behavior?

            systemctl status after manual start:
            Code:
            loxberry@loxberry:~ $ systemctl status mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service
            ● mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service - Modbus TCP to Modbus RTU (RS-232/485) gateway.
            Loaded: loaded (/lib/systemd/system/mbusd@.service; enabled; vendor preset: enabled)
            Active: active (running) since Tue 2020-01-28 14:23:57 CET; 5h 19min ago
            Main PID: 1463 (mbusd)
            Tasks: 1 (limit: 2200)
            Memory: 156.0K
            CGroup: /system.slice/system-mbusd.slice/mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service
            └─1463 /usr/bin/mbusd -d -v2 -L /opt/loxberry/log/plugins/modbusgateway/mbusd-usb-FTDI_FT232R_USB_UART_AL0
            lines 1-8/8 (END)
            journalctl:
            (Failed startup after reboot, manual start at 14:21:52 succesfully)
            Code:
            [FONT=Calibri][FONT=Courier New]-- Logs begin at Tue 2020-01-28 14:19:41 CET, end at Tue 2020-01-28 19:53:14 CET. --[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:50 loxberry systemd[1]: Started Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:50 loxberry mbusd[176]: mbusd: can't open logfile '/opt/loxberry/log/plugins/modbusgateway/mbusd-usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.log' (No such file or directory), exiting...[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:50 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Main process exited, code=exited, status=255/EXCEPTION[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:50 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Failed with result 'exit-code'.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:51 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Service RestartSec=1s expired, scheduling restart.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:51 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Scheduled restart job, restart counter is at 1.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:51 loxberry systemd[1]: Stopped Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:51 loxberry systemd[1]: Started Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:51 loxberry mbusd[332]: mbusd: can't open logfile '/opt/loxberry/log/plugins/modbusgateway/mbusd-usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.log' (No such file or directory), exiting...[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:51 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Main process exited, code=exited, status=255/EXCEPTION[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:51 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Failed with result 'exit-code'.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:52 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Service RestartSec=1s expired, scheduling restart.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:52 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Scheduled restart job, restart counter is at 2.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:52 loxberry systemd[1]: Stopped Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:52 loxberry systemd[1]: Started Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:52 loxberry mbusd[495]: mbusd: can't open logfile '/opt/loxberry/log/plugins/modbusgateway/mbusd-usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.log' (No such file or directory), exiting...[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:52 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Main process exited, code=exited, status=255/EXCEPTION[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:52 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Failed with result 'exit-code'.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:54 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Service RestartSec=1s expired, scheduling restart.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:54 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Scheduled restart job, restart counter is at 3.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:54 loxberry systemd[1]: Stopped Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:54 loxberry systemd[1]: Started Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:54 loxberry mbusd[611]: mbusd: can't open logfile '/opt/loxberry/log/plugins/modbusgateway/mbusd-usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.log' (No such file or directory), exiting...[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:54 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Main process exited, code=exited, status=255/EXCEPTION[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:54 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Failed with result 'exit-code'.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:55 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Service RestartSec=1s expired, scheduling restart.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:55 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Scheduled restart job, restart counter is at 4.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:55 loxberry systemd[1]: Stopped Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:55 loxberry systemd[1]: Started Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:55 loxberry mbusd[612]: mbusd: can't open logfile '/opt/loxberry/log/plugins/modbusgateway/mbusd-usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.log' (No such file or directory), exiting...[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:55 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Main process exited, code=exited, status=255/EXCEPTION[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:55 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Failed with result 'exit-code'.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:56 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Service RestartSec=1s expired, scheduling restart.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:56 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Scheduled restart job, restart counter is at 5.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:56 loxberry systemd[1]: Stopped Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:56 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Start request repeated too quickly.[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:19:56 loxberry systemd[1]: mbusd@usb-FTDI_FT232R_USB_UART_AL036VXP-if00-port0.service: Failed with result 'exit-code'.[/FONT][/FONT]
            [FONT=Calibri][B][FONT=Courier New]Jan 28 14:19:56 loxberry systemd[1]: Failed to start Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/B][/FONT]
            [FONT=Calibri][B][FONT=Courier New]Jan 28 14:21:52 loxberry systemd[1]: Started Modbus TCP to Modbus RTU (RS-232/485) gateway..[/FONT][/B][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 mbusd-0.3.1 started...[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 tty: state now is TTY_PAUSE[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_loop(): select(): max_sd = 4, t_out = 000000:100000[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_loop(): select() returns 0[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 tty: state now is TTY_READY[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_loop(): select(): max_sd = 4, t_out = 000060:000000[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_loop(): select() returns 1[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_open(): accepting connection from 192.168.x.xxx[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 queue_new_elem(): length now is 1[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn[192.168.x.xxx]: state now is CONN_HEADER[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_loop(): select(): max_sd = 5, t_out = 000060:000000[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_loop(): select() returns 1[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn[192.168.x.xxx]: state now is CONN_RQST_FUNC[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn[192.168.x.xxx]: read request fc 4[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn[192.168.x.xxx]: state now is CONN_RQST_TAIL[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn[192.168.x.xxx]: request: [02][04][00][00][00][02][/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn[192.168.x.xxx]: state now is CONN_TTY[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 tty: state now is TTY_RQST[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_loop(): select(): max_sd = 4, t_out = 000060:000000[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 conn_loop(): select() returns 1[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 tty: written 8 bytes[/FONT][/FONT]
            [FONT=Calibri][FONT=Courier New]Jan 28 14:21:52 loxberry mbusd[1340]: 28 Jan 2020 14:21:52 tty: request written (total 8 bytes)[/FONT][/FONT]
            I hope the log is helpfull. Maybe the startup needs just a few seconds more...
            Would be great if you can fix this!
            Stephan

            Kommentar


            • #67
              Hey,

              I just pushed a new pre-release v0.0.10.

              This should fix the issue with creating the log file, as it now starts after after the loxberry.service is started.

              Kommentar


              • ogrimo30
                ogrimo30 kommentierte
                Kommentar bearbeiten
                Thank you @Gagi.

                The Pre-Release is working.

                One small bug, after installing v.0.0.10 Loxberry is still showing v.0.0.9.

              • heisly
                heisly kommentierte
                Kommentar bearbeiten
                Hello Dominik,
                it seems to work, thank you very much!
                But after installation it is still shown as v0.0.9
                Greetings, Stephan

              • Gagi
                Gagi kommentierte
                Kommentar bearbeiten
                ok, great, happy to hear that everything is working now.

                Regarding the version, i think i forgot to update it also in the plugin.cfg, but i can do that for the final release. I would appreciate if you could give some feedback after some time, whether everything is still working.

            • #68
              bei mir funktioniert die Abfrage leider auch nicht. Kann mir jemand helfen, sonst muss ich wohl doch die >200€ für die Modbus Extension investieren...
              Abfragen möchte ich einen Schneider Energiemeter (iEM3200)
              Adresse am Gerät ist 1. Verkabelung müsste auch passen (habs aber auch schon gedreht zum testen)

              Hier meine Einstellungen:
              Klicke auf die Grafik für eine vergrößerte Ansicht

Name: 2020-03-10 18_35_05-Window.png
Ansichten: 837
Größe: 68,7 KB
ID: 240064
              Klicke auf die Grafik für eine vergrößerte Ansicht

Name: 2020-03-10 18_34_42-Window.png
Ansichten: 827
Größe: 7,7 KB
ID: 240063
              Klicke auf die Grafik für eine vergrößerte Ansicht

Name: 2020-03-10 18_34_27-Window.png
Ansichten: 820
Größe: 9,1 KB
ID: 240062
              Klicke auf die Grafik für eine vergrößerte Ansicht

Name: 2020-03-10 18_34_12-Window.png
Ansichten: 905
Größe: 20,0 KB
ID: 240061

              Und die Log:
              10 Mar 2020 18:32:35 conn[192.168.1.110]: state now is CONN_RQST_FUNC
              10 Mar 2020 18:32:35 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              10 Mar 2020 18:32:35 conn_loop(): select() returns 1
              10 Mar 2020 18:32:35 conn[192.168.1.110]: read request fc 4
              10 Mar 2020 18:32:35 conn[192.168.1.110]: state now is CONN_RQST_TAIL
              10 Mar 2020 18:32:35 conn[192.168.1.110]: request: [01][04][07][e0][00][02]
              10 Mar 2020 18:32:35 conn[192.168.1.110]: state now is CONN_TTY
              10 Mar 2020 18:32:35 tty: state now is TTY_RQST
              10 Mar 2020 18:32:35 conn_loop(): select(): max_sd = 4, t_out = 000060:000000
              10 Mar 2020 18:32:35 conn_loop(): select() returns 1
              10 Mar 2020 18:32:35 tty: written 8 bytes
              10 Mar 2020 18:32:35 tty: request written (total 8 bytes)
              10 Mar 2020 18:32:35 tty: state now is TTY_RESP
              10 Mar 2020 18:32:35 tty: estimated 9 bytes, waiting 508853 usec
              10 Mar 2020 18:32:35 conn_loop(): select(): max_sd = 4, t_out = 000000:508853
              10 Mar 2020 18:32:35 conn_loop(): select() returns 0
              10 Mar 2020 18:32:35 tty: response timeout
              10 Mar 2020 18:32:35 tty: attempt to retry request (1 of 3)
              10 Mar 2020 18:32:35 tty: state now is TTY_RQST
              10 Mar 2020 18:32:35 tty: written 8 bytes
              10 Mar 2020 18:32:35 tty: request written (total 8 bytes)
              10 Mar 2020 18:32:35 tty: state now is TTY_RESP
              10 Mar 2020 18:32:35 tty: estimated 9 bytes, waiting 508853 usec
              10 Mar 2020 18:32:35 conn_loop(): select(): max_sd = 4, t_out = 000000:508853
              10 Mar 2020 18:32:36 conn_loop(): select() returns 0
              10 Mar 2020 18:32:36 tty: response timeout
              10 Mar 2020 18:32:36 tty: attempt to retry request (2 of 3)
              10 Mar 2020 18:32:36 tty: state now is TTY_RQST
              10 Mar 2020 18:32:36 tty: written 8 bytes
              10 Mar 2020 18:32:36 tty: request written (total 8 bytes)
              10 Mar 2020 18:32:36 tty: state now is TTY_RESP
              10 Mar 2020 18:32:36 tty: estimated 9 bytes, waiting 508853 usec
              10 Mar 2020 18:32:36 conn_loop(): select(): max_sd = 4, t_out = 000000:508853
              10 Mar 2020 18:32:36 conn_loop(): select() returns 0
              10 Mar 2020 18:32:36 tty: response timeout
              10 Mar 2020 18:32:36 tty: attempt to retry request (3 of 3)
              10 Mar 2020 18:32:36 tty: state now is TTY_RQST
              10 Mar 2020 18:32:36 tty: written 8 bytes
              10 Mar 2020 18:32:36 tty: request written (total 8 bytes)
              10 Mar 2020 18:32:36 tty: state now is TTY_RESP
              10 Mar 2020 18:32:36 tty: estimated 9 bytes, waiting 508853 usec
              10 Mar 2020 18:32:36 conn_loop(): select(): max_sd = 4, t_out = 000000:508853
              10 Mar 2020 18:32:37 conn_loop(): select() returns 0
              10 Mar 2020 18:32:37 tty: response timeout
              10 Mar 2020 18:32:37 conn[192.168.1.110]: state now is CONN_RESP
              10 Mar 2020 18:32:37 tty: state now is TTY_PAUSE
              10 Mar 2020 18:32:37 conn_loop(): select(): max_sd = 5, t_out = 000000:100000
              10 Mar 2020 18:32:37 conn_loop(): select() returns 1
              10 Mar 2020 18:32:37 conn[192.168.1.110]: state now is CONN_HEADER
              10 Mar 2020 18:32:37 conn_loop(): select(): max_sd = 5, t_out = 000000:099904
              10 Mar 2020 18:32:37 conn_loop(): select() returns 0
              10 Mar 2020 18:32:37 tty: state now is TTY_READY
              10 Mar 2020 18:32:37 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              10 Mar 2020 18:32:39 conn_loop(): select() returns 1
              10 Mar 2020 18:32:39 conn[192.168.1.110]: state now is CONN_RQST_FUNC
              10 Mar 2020 18:32:39 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              10 Mar 2020 18:32:39 conn_loop(): select() returns 1
              10 Mar 2020 18:32:39 conn[192.168.1.110]: read request fc 4
              10 Mar 2020 18:32:39 conn[192.168.1.110]: state now is CONN_RQST_TAIL
              10 Mar 2020 18:32:39 conn[192.168.1.110]: request: [01][04][0c][84][00][02]
              10 Mar 2020 18:32:39 conn[192.168.1.110]: state now is CONN_TTY

              Kommentar


              • streuber
                streuber kommentierte
                Kommentar bearbeiten
                Nachdem ich den seriellen Anschlußmodus auf „8o1“ verändert habe, hat es bei mir geklappt!

            • #69
              Hi All!
              I have an issue with the Modbus Gateway:

              I can read the device I'm connected to by the Modbus Poll (screen in attachment).
              But when I connect the Modbus Gateway I've got 0 in the Loxone config (and along the connection error).

              In the Modbus Gateway I'm using the standard settings - it corresponds with the device settings.

              Also I attach the fragment of log (level 9):

              Code:
              07 Jan 2021 13:08:18 mbusd-0.4.1 started...
              07 Jan 2021 13:08:18 tty: state now is TTY_PAUSE
              07 Jan 2021 13:08:18 conn_loop(): select(): max_sd = 4, t_out = 000000:100000
              07 Jan 2021 13:08:18 conn_loop(): select() returns 0
              07 Jan 2021 13:08:18 tty: state now is TTY_READY
              07 Jan 2021 13:08:18 conn_loop(): select(): max_sd = 4, t_out = 000060:000000
              07 Jan 2021 13:08:19 conn_loop(): select() returns 1
              07 Jan 2021 13:08:19 conn_open(): accepting connection from 192.168.0.10
              07 Jan 2021 13:08:19 queue_new_elem(): length now is 1
              07 Jan 2021 13:08:19 conn[192.168.0.10]: state now is CONN_HEADER
              07 Jan 2021 13:08:19 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              07 Jan 2021 13:08:19 conn_loop(): select() returns 1
              07 Jan 2021 13:08:19 conn[192.168.0.10]: state now is CONN_RQST_FUNC
              07 Jan 2021 13:08:19 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              07 Jan 2021 13:08:19 conn_loop(): select() returns 1
              07 Jan 2021 13:08:19 conn[192.168.0.10]: read request fc 3
              07 Jan 2021 13:08:19 conn[192.168.0.10]: state now is CONN_RQST_TAIL
              07 Jan 2021 13:08:19 conn[192.168.0.10]: request: [01][03][08][2d][00][01]
              07 Jan 2021 13:08:19 conn[192.168.0.10]: state now is CONN_TTY
              07 Jan 2021 13:08:19 tty: state now is TTY_RQST
              07 Jan 2021 13:08:19 conn_loop(): select(): max_sd = 4, t_out = 000060:000000
              07 Jan 2021 13:08:19 conn_loop(): select() returns 1
              07 Jan 2021 13:08:19 tty: written 8 bytes
              07 Jan 2021 13:08:19 tty: request written (total 8 bytes)
              07 Jan 2021 13:08:19 tty: state now is TTY_RESP
              07 Jan 2021 13:08:19 tty: estimated 7 bytes, waiting 515624 usec
              07 Jan 2021 13:08:19 conn_loop(): select(): max_sd = 4, t_out = 000000:515624
              07 Jan 2021 13:08:19 conn_loop(): select() returns 1
              07 Jan 2021 13:08:19 tty: read 5 bytes
              07 Jan 2021 13:08:19 tty: read 5 bytes of 7, offset 0
              07 Jan 2021 13:08:19 conn_loop(): select(): max_sd = 4, t_out = 000000:515187
              07 Jan 2021 13:08:20 conn_loop(): select() returns 0
              07 Jan 2021 13:08:20 tty: response read (total 5 bytes, offset 0 bytes)
              07 Jan 2021 13:08:20 tty: response is correct
              07 Jan 2021 13:08:20 tty: response: [01][83][02][c0][f1]
              07 Jan 2021 13:08:20 conn[192.168.0.10]: state now is CONN_RESP
              07 Jan 2021 13:08:20 tty: state now is TTY_PAUSE
              07 Jan 2021 13:08:20 conn_loop(): select(): max_sd = 5, t_out = 000000:100000
              07 Jan 2021 13:08:20 conn_loop(): select() returns 1
              07 Jan 2021 13:08:20 conn[192.168.0.10]: state now is CONN_HEADER
              07 Jan 2021 13:08:20 conn_loop(): select(): max_sd = 5, t_out = 000000:099500
              07 Jan 2021 13:08:20 conn_loop(): select() returns 0
              07 Jan 2021 13:08:20 tty: state now is TTY_READY
              07 Jan 2021 13:08:20 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              07 Jan 2021 13:09:19 conn_loop(): select() returns 1
              07 Jan 2021 13:09:19 conn[192.168.0.10]: state now is CONN_RQST_FUNC
              07 Jan 2021 13:09:19 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              07 Jan 2021 13:09:19 conn_loop(): select() returns 1
              07 Jan 2021 13:09:19 conn[192.168.0.10]: read request fc 3
              07 Jan 2021 13:09:19 conn[192.168.0.10]: state now is CONN_RQST_TAIL
              07 Jan 2021 13:09:19 conn[192.168.0.10]: request: [01][03][08][2d][00][01]
              07 Jan 2021 13:09:19 conn[192.168.0.10]: state now is CONN_TTY
              07 Jan 2021 13:09:19 tty: state now is TTY_RQST
              07 Jan 2021 13:09:19 conn_loop(): select(): max_sd = 4, t_out = 000060:000000
              07 Jan 2021 13:09:19 conn_loop(): select() returns 1
              07 Jan 2021 13:09:19 tty: written 8 bytes
              07 Jan 2021 13:09:19 tty: request written (total 8 bytes)
              07 Jan 2021 13:09:19 tty: state now is TTY_RESP
              07 Jan 2021 13:09:19 tty: estimated 7 bytes, waiting 515624 usec
              07 Jan 2021 13:09:19 conn_loop(): select(): max_sd = 4, t_out = 000000:515624
              07 Jan 2021 13:09:19 conn_loop(): select() returns 1
              07 Jan 2021 13:09:19 tty: read 5 bytes
              07 Jan 2021 13:09:19 tty: read 5 bytes of 7, offset 0
              07 Jan 2021 13:09:19 conn_loop(): select(): max_sd = 4, t_out = 000000:497731
              07 Jan 2021 13:09:20 conn_loop(): select() returns 0
              07 Jan 2021 13:09:20 tty: response read (total 5 bytes, offset 0 bytes)
              07 Jan 2021 13:09:20 tty: response is correct
              07 Jan 2021 13:09:20 tty: response: [01][83][02][c0][f1]
              07 Jan 2021 13:09:20 conn[192.168.0.10]: state now is CONN_RESP
              07 Jan 2021 13:09:20 tty: state now is TTY_PAUSE
              07 Jan 2021 13:09:20 conn_loop(): select(): max_sd = 5, t_out = 000000:100000
              07 Jan 2021 13:09:20 conn_loop(): select() returns 1
              07 Jan 2021 13:09:20 conn[192.168.0.10]: state now is CONN_HEADER
              07 Jan 2021 13:09:20 conn_loop(): select(): max_sd = 5, t_out = 000000:099342
              07 Jan 2021 13:09:20 conn_loop(): select() returns 0
              07 Jan 2021 13:09:20 tty: state now is TTY_READY
              07 Jan 2021 13:09:20 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              07 Jan 2021 13:10:19 conn_loop(): select() returns 1
              07 Jan 2021 13:10:19 conn[192.168.0.10]: timeout, closing connection
              07 Jan 2021 13:10:19 conn_close(): closing connection from 192.168.0.10
              07 Jan 2021 13:10:19 queue_delete_elem(): length now is 0
              07 Jan 2021 13:10:19 conn_loop(): select(): max_sd = 4, t_out = 000060:000000
              07 Jan 2021 13:11:19 conn_loop(): select() returns 0
              07 Jan 2021 13:11:19 conn_loop(): select(): max_sd = 4, t_out = 000060:000000
              07 Jan 2021 13:11:20 conn_loop(): select() returns 1
              07 Jan 2021 13:11:20 conn_open(): accepting connection from 192.168.0.10
              07 Jan 2021 13:11:20 queue_new_elem(): length now is 1
              07 Jan 2021 13:11:20 conn[192.168.0.10]: state now is CONN_HEADER
              07 Jan 2021 13:11:20 conn_loop(): select(): max_sd = 5, t_out = 000060:000000
              07 Jan 2021 13:12:19 conn_loop(): select() returns 1
              07 Jan 2021 13:12:19 conn[192.168.0.10]: timeout, closing connection
              Would be grateful if anybody can help..

              ----
              EDIT:
              I'm using the Pre release v0.0.10

              Greetings!
              NEON
              Zuletzt geändert von NEON_Rumia; 08.01.2021, 16:07.

              Kommentar


              • Gagi
                Gagi kommentierte
                Kommentar bearbeiten
                According to the logs, the device responses correctly and it's a matter of using the correct settings in Loxone to interpret them correctly. If you have a manual, you need to use the settings from there, if not, just try a few variations.

                Regarding the error you see in the logs, i don't think this is a problem, as it just states that the connection to Loxone has been closed, usually Loxone should reconnect for the next request.

              • NEON_Rumia
                NEON_Rumia kommentierte
                Kommentar bearbeiten
                Thanks Gagi!
                I'll try it on Monday...

                Greetings!
                NEON

            • #70
              Hi everybody,

              I do have some problems/questions, I realy don´t understand....

              I do use the ModbusGateway, connected to an Eastron SDM120 Modbus MID for 1 phase.

              Default settings of it: 2400 and 8n1 (as I know...)

              I did take the template for the Eastron SDM630 for my Miniserver and I do get some data. Thats nice, but:

              1) do I need to change it to 9600, I read it somewhere...?
              2) my log, why?

              Klicke auf die Grafik für eine vergrößerte Ansicht  Name: Lox-Log.JPG Ansichten: 0 Größe: 106,4 KB ID: 292499

              At the end: Perhaps I am blind, but where I can find "KW used at all"? I would like to see, how much was used. Not at this moment, at the end of day or month....

              Is it "total active energy"?

              Klicke auf die Grafik für eine vergrößerte Ansicht  Name: Modbus01.JPG Ansichten: 0 Größe: 86,6 KB ID: 292500
              How to set "hi byte" to 01?


              Sorry for it.

              Irgendwer eine Idee? AlexAn Du vielleicht?

              Some ideas?

              Greetings

              Mike
              Angehängte Dateien
              Zuletzt geändert von connor100; 22.02.2021, 09:52.

              Kommentar


              • #71
                Hi Mike,

                I just implemented the Modbus Plugin yesterday and first it also was not working (caused by the wrong settings). You need to set following settings:

                Bus velocity: 9600 (depends what you have set at the SDM120; by pressing the button you can have a look on the settings)

                Modus: 8n1

                TRX control: rts (this was the wrong setting for my implementation)

                All other settings can handover from the standard from the plugin.

                Regards

                Philipp
                Zuletzt geändert von phil84; 11.06.2021, 11:31.

                Kommentar


                • #72
                  Hi,
                  I want to use the plugin with a RS485 interface IC connected to the on-board UART interface (pin 8 and 10) instead of a USB dongle. How do I need to configure the RPi to make this work?
                  Thanks

                  Kommentar


                  • #73
                    Hallo zusammen

                    Vor längerer Zeit habe ich über das Plugin erfolgreich einen 3-Phasenzähler von Finder (7E.78.8.400.0212) eingebunden. Das hat nun über ein Jahr problemlos funktioniert. Seit einigen Tagen empfange ich nun aber keine Werte mehr. Ich habe dann festgestellt, das scheinbar der USB/RS485-Wandler defekt ist (rote LED hat durchgehend geleuchtet). Glücklicherweise hatte ich mir mal einen Ersatz bestellt und diesen fix eingebaut und konfiguriert, die Werte wurden gleich wieder übertragen. Leider war die Freude von kurzer Dauer, die Werte wurde genau ein Mal übertragen und dann nicht mehr.

                    Auch wenn ich das PlugIn oder den kompletten Loxberry neu starte, werden die Werte genau ein Mal übertragen.

                    ich steh grad ziemlich auf dem Schlauch, hat jemand eine Idee woran das liegen kann?

                    Kommentar


                    • #74

                      Hi,
                      after installing on a fresh Raspberry PI 3, I get the following error when installing the modbus gateway:​

                      8:03:08.904 OK: File ownership set successfully.
                      dpkg: error processing archive /opt/loxberry/data/system/tmp/uploads/QtjlrzCA72/LoxBerry-Plugin-ModbusGateway-0.0.12/dpkg/raspberry/mbusd-Linux_armv7l-v0.4.1.deb (--install):
                      package architecture (armhf) does not match system (arm64)
                      Errors were encountered while processing:
                      /opt/loxberry/data/system/tmp/uploads/QtjlrzCA72/LoxBerry-Plugin-ModbusGateway-0.0.12/dpkg/raspberry/mbusd-Linux_armv7l-v0.4.1.deb

                      18:03:09.175 ERROR: (Some) Packages could not be installed.

                      commad journalctl -u mbusd@usb-1a86_USB_Serial-if00-port0.service print this log


                      -- Journal begins at Wed 2023-12-27 18:04:16 CET, ends at Wed 2023-12-27 18:54:01 CET. --
                      Dec 27 18:05:54 loxberry systemd[1610]: mbusd@usb-1a86_USB_Serial-if00-port0.service: Failed to locate executable /usr/bin/mbusd: No such file or directory
                      Dec 27 18:05:54 loxberry systemd[1610]: mbusd@usb-1a86_USB_Serial-if00-port0.service: Failed at step EXEC spawning /usr/bin/mbusd: No such file or directory
                      Dec 27 18:05:54 loxberry systemd[1]: Started Modbus TCP to Modbus RTU (RS-232/485) gateway..
                      Dec 27 18:05:54 loxberry systemd[1]: mbusd@usb-1a86_USB_Serial-if00-port0.service: Main process exited, code=exited, status=203/EXEC
                      Dec 27 18:05:54 loxberry systemd[1]: mbusd@usb-1a86_USB_Serial-if00-port0.service: Failed with result 'exit-code'.
                      Dec 27 18:05:56 loxberry systemd[1]: mbusd@usb-1a86_USB_Serial-if00-port0.service: Scheduled restart job, restart counter is at 1.
                      Dec 27 18:05:56 loxberry systemd[1]: Stopped Modbus TCP to Modbus RTU (RS-232/485) gateway..
                      Dec 27 18:05:56 loxberry systemd[1631]: mbusd@usb-1a86_USB_Serial-if00-port0.service: Failed to locate executable /usr/bin/mbusd: No such file or directory
                      Dec 27 18:05:56 loxberry systemd[1631]: mbusd@usb-1a86_USB_Serial-if00-port0.service: Failed at step EXEC spawning /usr/bin/mbusd: No such file or directory​

                      can someone help here?​


                      Kommentar


                      • staly
                        staly kommentierte
                        Kommentar bearbeiten
                        Hello,
                        I have the same problem with Loxberry 3.0 on a Raspberry Pi 3 and 4.
                        On a VMware x64 VM the installation of ModbusGateway Plugin is working

                      • staly
                        staly kommentierte
                        Kommentar bearbeiten
                        I found a workarround, I installed Loxberry 3.0 on my Raspberry Pi3 with the following armv7 image.

                        On the armv7 installation there isn't this error. Modbus Gateway is working.
                    Lädt...
                    X