Modbus Gateway

[Gast]

Gagi I've just added you as collaborator.

[ROLE]

Gagi ogrimo30Gast


I've just installed the plugin from Gagi without any problems. Now I've to try whether the plugin runs now or not. But for that I've to adjust my laboratory environment. That takes time. I will give reply!

[Gagi]

I'm also just setting up a new pi, just to give it a try and see whether i can replicate the service start/stop problem here.

[Gagi]

Ok, i think i know found the problem. First my last raspberry packages was using a too recent rasbian, so it wasn't working with the standard raspbian stretch installations. This is now fixed. The other problem was the custom systemd service file which was part of the old mbusd package, while my new one, was a vanilla build from the repository.
I now also tested the plugin and it works fine on my local installation. Please give it a try:

https://github.com/Gagi2k/LoxBerry-Plugin-ModbusGateway/releases/tag/v0.0.9-2

As mbusd updated their repository to make packaging easy, it might happen that mbusd will be part of a standard raspbian release, because of that, i will try to see how we can get it working with a vanilla mbusd without a custom systemd service.

[ogrimo30]

Sound good!
Thank you. I will test it tomorrow when I'm at home.

[ROLE]

Gagi
Anbei meine Logs aus der Loxone Config und vom Modbus Plugin.

Leider kommen keine Werte an.

Enclosed Logs from Modbus Plugin and Loxone Config.

No data received by Loxone.

[Gagi]

Mhh, the log file looks good to me. I guess 192.168.0.145 is your miniserver and mbusd gets requests and sends valid response, so from that point it should work fine.

[ROLE]

I found the problem. It was in Loxone Config. Different from configuration of meters connected via Modbus Extension I had to select 2 register for 32 bit and registersequence. Now I get all data and I am happy.

[ogrimo30]

Hello,
i just made a fresh Loxberry installation and installed the plugin version 0.0.9-2.
The start error is gone.

But i don't received data and get a new error during the installation:
15.10.2019 09:23:48 WARNING: HARDCODED PATH'S: Das Plugin nutzt einen hardkodierten Pfad zu /opt/loxberry. Dies könnte zu Problemen führen und sollte vom Plugin-Author behoben werden:xxxx@xxxx.cz

No data received by Loxone.

Enclosed Logs from Modbus Plugin.

Thank you!!!

[Christian Fenzl]

HARDCODED PATHS is shown if in any file the /opt/loxberry/* path is used.
This is no problem for the plugin as long as LoxBerry's home directory is in here (and currently, no image or vm uses another path).

Gagi Just to give you direct links :-)

We provide environment variables ($LBHOMEDIR - https://www.loxwiki.eu/display/LOXBE...nmentvariablen)

If - for any reason - environment variables do not work (in a systemd service file, this pretty sure will not work) you may use the replacement variables (https://www.loxwiki.eu/pages/viewpag...ageId=28803623). During plugin installation, all non-binary files of the plugin package are parsed for the variables and these got replaced with path's in the installed files. This is very handy, as you don't need to care about it, it simply is done automatically.

[svethi]

and I have to say, that you can use directives to specify environments in your service file for your daemon. Just like the service file for the ssdpd of the Loxberry.

https://github.com/mschlenstedt/Loxberry/blob/4c5fb752ed66100e5d81f0373aa7b8ba400acfce/system/systemd/ssdpd.service#L9

[Gagi]

Christian Fenzl @svethi: Thx, i was thinking about 'sed' and installing it, but env variables makes the even easier and maintainable.

@ogrimo30: From the logs also writing to it, doesn't work correctly as you don't get any response (even though your AC might accept the command). Do you have any way to check that modbus still works correctly for your AC ? E.g. by reading the values directly using your modbus USB dongle ?

[ogrimo30]

Hallo,
bitte entschuldigt meine spätet Antwort - ich habe auf das Ersatzteil gewartet....
Das Plugin arbeitet jeztz wieder perfekt. Das Problem war ein defekter Modbus - USB - Dongle.
Danke für eure Hilfe

The Plugin works finde, it was a problem with the Modbus - USB - Dongle.
Thank you!!

PS: Ist es möglich das auch das Restart-Problem gelöst wurde?

[Gagi]

Great, then i can start the work to do a proper update of the plugin and fix the hardcoded path of the systemd service.

ogrimo30 What do you mean with Restart-Problem ? If you mean that the service did not start from the Loxberry UI, then yes, the service was fixed to start properly, but no additional changes in the plugin were made.

[Gast]

hi,
za każdym razem, gdy Loxberry jest restartowany, wtyczka Modbus nie uruchamia się automatycznie. Mam komunikat „Aktywny: nieudany (Wynik: kod wyjścia) od ......”. Muszę ręcznie rozpocząć od przycisku „start”. Wtyczka Modbus 0.0.9-2
Loxberry 2.0.0.4
Raspbian - 10 (buster)

Czy możesz pomóc?

[ROLE]

Google Translator:

Bei jedem Neustart von Loxberry wird das Modbus-Plug-In nicht automatisch gestartet. Ich habe die Meldung "Aktiv: fehlgeschlagen (Ergebnis: Beendigungscode) von ......". Ich muss manuell über die Schaltfläche "Start" starten. Modbus-Stecker 0.0.9-2
Loxberry 2.0.0.4
Raspbian - 10 (Buster)

Kannst du mir helfen?

[Gagi]

Hi,

i pushed all my fixes to the official repository now and did a fresh Pre-Release of 0.0.9 there.
This also includes a fix for the hardcoded paths and a way to update the systemd service from the plugin without repackaging mbusd all the time and i hope with this we can switch to a apt source in the future.

You should get the update using the Pre-Release channel. Let me know how it works for you, so i can du a full update soon.

[Gast]

Thanks for the quick reply.
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.

M.S.

[Gagi]

Could you check the log file of the modbus plugin after the reboot ? It hopefully provides some more information why it failed to start.

[Gast]

There is no log file after reboot.
It creates after manual start only.



.

[Gagi]

Hi, could you check the systemd log for any errors?


Gesendet von iPhone mit Tapatalk

[janralf]

Hallo in die Runde ich habe gerade einen Hänger und hoffe ihr habt eine idee ich habe jetzt endlich mal wieder ein bisschen Zeit gehabt und mein Energymeter eingebaut und das Modbus Plugin auf dem Loxberry installiert aber ich bekomme auf teufel komm raus keine Daten in den Miniserver


17 Jan 2020 22:34:20 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:20 tty: response timeout
17 Jan 2020 22:34:20 tty: attempt to retry request (3 of 3)
17 Jan 2020 22:34:20 tty: state now is TTY_RQST
17 Jan 2020 22:34:20 tty: state now is TTY_RESP
17 Jan 2020 22:34:20 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:21 tty: response timeout
17 Jan 2020 22:34:21 conn[192.168.1.77]: state now is CONN_RESP
17 Jan 2020 22:34:21 tty: state now is TTY_PAUSE
17 Jan 2020 22:34:21 conn[192.168.1.77]: state now is CONN_HEADER
17 Jan 2020 22:34:21 tty: state now is TTY_READY
17 Jan 2020 22:34:26 conn[192.168.1.77]: state now is CONN_RQST_FUNC
17 Jan 2020 22:34:26 conn[192.168.1.77]: state now is CONN_RQST_TAIL
17 Jan 2020 22:34:26 conn[192.168.1.77]: request: [01][03][00][32][00][01]
17 Jan 2020 22:34:26 conn[192.168.1.77]: state now is CONN_TTY
17 Jan 2020 22:34:26 tty: state now is TTY_RQST
17 Jan 2020 22:34:27 tty: state now is TTY_RESP
17 Jan 2020 22:34:27 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:27 tty: response timeout
17 Jan 2020 22:34:27 tty: attempt to retry request (1 of 3)
17 Jan 2020 22:34:27 tty: state now is TTY_RQST
17 Jan 2020 22:34:27 tty: state now is TTY_RESP
17 Jan 2020 22:34:27 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:28 tty: response timeout
17 Jan 2020 22:34:28 tty: attempt to retry request (2 of 3)
17 Jan 2020 22:34:28 tty: state now is TTY_RQST
17 Jan 2020 22:34:28 tty: state now is TTY_RESP
17 Jan 2020 22:34:28 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:28 tty: response timeout
17 Jan 2020 22:34:28 tty: attempt to retry request (3 of 3)
17 Jan 2020 22:34:28 tty: state now is TTY_RQST
17 Jan 2020 22:34:28 tty: state now is TTY_RESP
17 Jan 2020 22:34:28 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:29 tty: response timeout
17 Jan 2020 22:34:29 conn[192.168.1.77]: state now is CONN_RESP
17 Jan 2020 22:34:29 tty: state now is TTY_PAUSE
17 Jan 2020 22:34:29 conn[192.168.1.77]: state now is CONN_HEADER
17 Jan 2020 22:34:29 conn[192.168.1.77]: state now is CONN_RQST_FUNC
17 Jan 2020 22:34:29 conn[192.168.1.77]: state now is CONN_RQST_TAIL
17 Jan 2020 22:34:29 conn[192.168.1.77]: request: [01][03][00][1b][00][02][01][71][00][00][00][06][01][03][00][1f][00][02]
17 Jan 2020 22:34:29 conn[192.168.1.77]: state now is CONN_TTY
17 Jan 2020 22:34:29 tty: state now is TTY_RQST
17 Jan 2020 22:34:29 tty: state now is TTY_RESP
17 Jan 2020 22:34:29 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:29 tty: response timeout
17 Jan 2020 22:34:29 tty: attempt to retry request (1 of 3)
17 Jan 2020 22:34:29 tty: state now is TTY_RQST
17 Jan 2020 22:34:29 tty: state now is TTY_RESP
17 Jan 2020 22:34:29 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:30 tty: response timeout
17 Jan 2020 22:34:30 tty: attempt to retry request (2 of 3)
17 Jan 2020 22:34:30 tty: state now is TTY_RQST
17 Jan 2020 22:34:30 tty: state now is TTY_RESP
17 Jan 2020 22:34:30 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:30 tty: response timeout
17 Jan 2020 22:34:30 tty: attempt to retry request (3 of 3)
17 Jan 2020 22:34:30 tty: state now is TTY_RQST
17 Jan 2020 22:34:30 tty: state now is TTY_RESP
17 Jan 2020 22:34:30 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:31 tty: response timeout
17 Jan 2020 22:34:31 conn[192.168.1.77]: state now is CONN_RESP
17 Jan 2020 22:34:31 tty: state now is TTY_PAUSE
17 Jan 2020 22:34:31 conn[192.168.1.77]: state now is CONN_HEADER
17 Jan 2020 22:34:31 tty: state now is TTY_READY
17 Jan 2020 22:34:36 conn[192.168.1.77]: state now is CONN_RQST_FUNC
17 Jan 2020 22:34:36 conn[192.168.1.77]: state now is CONN_RQST_TAIL
17 Jan 2020 22:34:36 conn[192.168.1.77]: request: [01][03][00][32][00][01]
17 Jan 2020 22:34:36 conn[192.168.1.77]: state now is CONN_TTY
17 Jan 2020 22:34:36 tty: state now is TTY_RQST
17 Jan 2020 22:34:37 tty: state now is TTY_RESP
17 Jan 2020 22:34:37 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:37 tty: response timeout
17 Jan 2020 22:34:37 tty: attempt to retry request (1 of 3)
17 Jan 2020 22:34:37 tty: state now is TTY_RQST
17 Jan 2020 22:34:37 tty: state now is TTY_RESP
17 Jan 2020 22:34:37 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:38 tty: response timeout
17 Jan 2020 22:34:38 tty: attempt to retry request (2 of 3)
17 Jan 2020 22:34:38 tty: state now is TTY_RQST
17 Jan 2020 22:34:38 tty: state now is TTY_RESP
17 Jan 2020 22:34:38 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:38 tty: response timeout
17 Jan 2020 22:34:38 tty: attempt to retry request (3 of 3)
17 Jan 2020 22:34:38 tty: state now is TTY_RQST
17 Jan 2020 22:34:38 tty: state now is TTY_RESP
17 Jan 2020 22:34:38 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:39 tty: response timeout
17 Jan 2020 22:34:39 conn[192.168.1.77]: state now is CONN_RESP
17 Jan 2020 22:34:39 tty: state now is TTY_PAUSE
17 Jan 2020 22:34:39 conn[192.168.1.77]: state now is CONN_HEADER
17 Jan 2020 22:34:39 conn[192.168.1.77]: state now is CONN_RQST_FUNC
17 Jan 2020 22:34:39 conn[192.168.1.77]: state now is CONN_RQST_TAIL
17 Jan 2020 22:34:39 conn[192.168.1.77]: request: [01][03][00][1b][00][02][01][74][00][00][00][06][01][03][00][1f][00][02]
17 Jan 2020 22:34:39 conn[192.168.1.77]: state now is CONN_TTY
17 Jan 2020 22:34:39 tty: state now is TTY_RQST
17 Jan 2020 22:34:39 tty: state now is TTY_RESP
17 Jan 2020 22:34:39 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:39 tty: response timeout
17 Jan 2020 22:34:39 tty: attempt to retry request (1 of 3)
17 Jan 2020 22:34:39 tty: state now is TTY_RQST
17 Jan 2020 22:34:39 tty: state now is TTY_RESP
17 Jan 2020 22:34:39 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:40 tty: response timeout
17 Jan 2020 22:34:40 tty: attempt to retry request (2 of 3)
17 Jan 2020 22:34:40 tty: state now is TTY_RQST
17 Jan 2020 22:34:40 tty: state now is TTY_RESP
17 Jan 2020 22:34:40 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:40 tty: response timeout
17 Jan 2020 22:34:40 tty: attempt to retry request (3 of 3)
17 Jan 2020 22:34:40 tty: state now is TTY_RQST
17 Jan 2020 22:34:40 tty: state now is TTY_RESP
17 Jan 2020 22:34:40 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:41 tty: response timeout
17 Jan 2020 22:34:41 conn[192.168.1.77]: state now is CONN_RESP
17 Jan 2020 22:34:41 tty: state now is TTY_PAUSE
17 Jan 2020 22:34:41 conn[192.168.1.77]: state now is CONN_HEADER
17 Jan 2020 22:34:41 tty: state now is TTY_READY
17 Jan 2020 22:34:46 conn[192.168.1.77]: state now is CONN_RQST_FUNC
17 Jan 2020 22:34:46 conn[192.168.1.77]: state now is CONN_RQST_TAIL
17 Jan 2020 22:34:46 conn[192.168.1.77]: request: [01][03][00][32][00][01]
17 Jan 2020 22:34:46 conn[192.168.1.77]: state now is CONN_TTY
17 Jan 2020 22:34:46 tty: state now is TTY_RQST
17 Jan 2020 22:34:47 tty: state now is TTY_RESP
17 Jan 2020 22:34:47 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:47 tty: response timeout
17 Jan 2020 22:34:47 tty: attempt to retry request (1 of 3)
17 Jan 2020 22:34:47 tty: state now is TTY_RQST
17 Jan 2020 22:34:47 tty: state now is TTY_RESP
17 Jan 2020 22:34:47 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:48 tty: response timeout
17 Jan 2020 22:34:48 tty: attempt to retry request (2 of 3)
17 Jan 2020 22:34:48 tty: state now is TTY_RQST
17 Jan 2020 22:34:48 tty: state now is TTY_RESP
17 Jan 2020 22:34:48 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:48 tty: response timeout
17 Jan 2020 22:34:48 tty: attempt to retry request (3 of 3)
17 Jan 2020 22:34:48 tty: state now is TTY_RQST
17 Jan 2020 22:34:48 tty: state now is TTY_RESP
17 Jan 2020 22:34:48 tty: estimated 7 bytes, waiting 515624 usec
17 Jan 2020 22:34:49 tty: response timeout
17 Jan 2020 22:34:49 conn[192.168.1.77]: state now is CONN_RESP
17 Jan 2020 22:34:49 tty: state now is TTY_PAUSE
17 Jan 2020 22:34:49 conn[192.168.1.77]: state now is CONN_HEADER
17 Jan 2020 22:34:49 conn[192.168.1.77]: state now is CONN_RQST_FUNC
17 Jan 2020 22:34:49 conn[192.168.1.77]: state now is CONN_RQST_TAIL
17 Jan 2020 22:34:49 conn[192.168.1.77]: request: [01][03][00][1b][00][02][01][77][00][00][00][06][01][03][00][1f][00][02]
17 Jan 2020 22:34:49 conn[192.168.1.77]: state now is CONN_TTY
17 Jan 2020 22:34:49 tty: state now is TTY_RQST
17 Jan 2020 22:34:49 tty: state now is TTY_RESP
17 Jan 2020 22:34:49 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:49 tty: response timeout
17 Jan 2020 22:34:49 tty: attempt to retry request (1 of 3)
17 Jan 2020 22:34:49 tty: state now is TTY_RQST
17 Jan 2020 22:34:49 tty: state now is TTY_RESP
17 Jan 2020 22:34:49 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:50 tty: response timeout
17 Jan 2020 22:34:50 tty: attempt to retry request (2 of 3)
17 Jan 2020 22:34:50 tty: state now is TTY_RQST
17 Jan 2020 22:34:50 tty: state now is TTY_RESP
17 Jan 2020 22:34:50 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:50 tty: response timeout
17 Jan 2020 22:34:50 tty: attempt to retry request (3 of 3)
17 Jan 2020 22:34:50 tty: state now is TTY_RQST
17 Jan 2020 22:34:50 tty: state now is TTY_RESP
17 Jan 2020 22:34:50 tty: estimated 9 bytes, waiting 517708 usec
17 Jan 2020 22:34:51 tty: response timeout
17 Jan 2020 22:34:51 conn[192.168.1.77]: state now is CONN_RESP
17 Jan 2020 22:34:51 tty: state now is TTY_PAUSE
17 Jan 2020 22:34:51 conn[192.168.1.77]: state now is CONN_HEADER
17 Jan 2020 22:34:51 tty: state now is TTY_READY
17 Jan 2020 22:34:52 Terminated by signal: SIGTERM
17 Jan 2020 22:35:20 mbusd-0.3.1 started...
17 Jan 2020 22:35:20 conn_open(): accepting connection from 192.168.1.77

habe das Original Loxone Energymeter 3 Phasig