Eastron SDM72 not showing up in Device List (automatically)

[rpsmonkey]

Hi,

connected a Eastron SDM72V2 device and installed your script. The meters doesn't show up under devices automatically. But if I do a
/opt/victronenergy/serial-starter/stop-tty.sh ttyUSB0
/opt/victronenergy/dbus-modbus-client/dbus-modbus-client.py -x -s ttyUSB0
the device is found and all values are displayed correctly under Device List.

I've tried with Cerbo GX and a freshly installed Raspi with Venus OS for testing, both with newest firmware v.3.53. Both show the same behavior.

It seems that the RS485toUSB device is found, but somehow the dbus-modbus-client.py script is not executed with serial parameter and therefore the meter isn't found. Any ideas?

Kind Regards
Robert

[Telekatz]

Looks like Serial-Starter is not checking ttyUSB0. Try adding this in /etc/udev/rules.d/serial-starter.rules:
ACTION=="add", KERNEL=="ttyUSB0", ENV{VE_SERVICE}="modbus"

[rpsmonkey]

Awesome. That is working! At least for my test-setup with only 1 energy meter. Thanks a lot for the help.

For my productive system I have a EM540 meter connected with a RS485toUSB device and that is working out of the box. Trying to put that SDM72 on the same bus/USB device was not working. I therefore tested with a second RS485toUSB device. Now with each reboot the devices get randomly the ttyUSB0 (or ttyUSB1) link.

Can I also add the Lin with ttyUSB1 or do I get side effect when already the EM540 is running on the one device?
And any explanation why EM540 with RS485-modbus is working but no serial-starter is started for other RS485-modbus meters?

[Telekatz]

Are the two RS485toUSB devices of the same type?

You can try adding the interface by its ID instead of the device name. This should work similarly to what is described in the Venus OS Wiki, except that instead of "ignore" you enter "modbus" as VE_SERVICE.