EM24 lost after update to Venus 3.55 RasPi

Modifications
, , ,
1

Hi,
I am running Venus on a Raspi controlling one MP2 500 and a Fronius Symo. The Gavazzi EM24 RS485 smartmeter worked fine on Venus 2.92, all data were display correctly.
Since update to 3.55 Venus doesn’t read anymore data from the Smartmeter.

EM24 offline
EM24 offline1579×641 141 KB

Swiching back to 2.92 brings back the EM24. So it seem to be not a hardware issue.

I wonder if it could be a matter of RS485 speed. EM24 is limited to 9600 Baud.
Is there a config file in Venus to alter the communication speed?

Thank you

2

moved to modifications as that is where you may get more help on RasPi installs

3

You appear to be running GuiMods.

Please isolate the issue to stock Victron code by uninstalling GuiMods and any other third party modifications. If the problem persists, please reply to this topic.

If you determine the problem is with GuiMods or other package, please close this topic and start an issue at GitHub.

For GuiMods:

If you determine the problem is related to another package, please open an issue in the appropriate GitHub repo.

Thanks.

4

thank you very much. I did as adviced, but situation didn’t change. Still no AC loads nor SmartMeter data displayed.

5

What USB -RS485 converter are you using?

I don’t think the baudrate is the issue; more likely that the USB/RS485 converter is no longer recognised as such; or something like that.

See also here: Lost connection to smart meters after upgrade to venus 3.55.

The log files to check once logged in are /data/logs/dbus-cgwacs and perhaps some related to serial starter.

Info on how to check logs is here: commandline operational · victronenergy/venus Wiki · GitHub

6

The issue seems to be a matter of RS485.
I am using a USB_to_RS485 stick at USB0 that worked like a charm with Venus 2.92.

Here are some of the log files I found:

dbus.modbus-client.ttyUSB1
dbus.modbus-client.ttyUSB11995×310 110 KB

dbus-imt-si-rs485tc.ttyUSB0
dbus-imt-si-rs485tc.ttyUSB01635×223 75.9 KB

dbus-modbus-client.ttyUSB0
dbus-modbus-client.ttyUSB01768×221 86 KB

I couldnt see much difference in the logs between 2.92 and 3.55

7

Hi @Lichtbogen , it looks as if the USB cable is detected, since /dev/ttyUSB0 does show up, but communication is not succeeding?

You can try running the driver directly, by first telling serial-starter to leave it alone:

/opt/victronenergy/serial-starter/stop-tty.sh /dev/ttyUSB0

And then try running the driver directly:

/opt/victronenergy/dbus-cgwacs/dbus-cgwacs --verbose /dev/ttyUSB0

The output should tell us what is going wrong.