Connecting an ET-112 to Venus OS on a RP4b

Question

replit

This site is now in read-only archive mode. Please move all discussion, and create a new account at the new Victron Community site.

question

joseal asked Nov 5, '22

Connecting an ET-112 to Venus OS on a RP4b

Hi All,

I'm trying to get an ET-112 connected to a Venus OS running on a Raspberry PI 4b, but I cannot get the Venus OS detecting the energy meter.

I'm new to Victron ecosystem, but from what I've read, I believe that ET-112 should be detected by Venus OS.

I've the meter connected to a USB to RS485 adapter and the adapter connected to the RP4.

The adapter and the ET-112 seem to be ok, because if I use universal configuration tool (from Carlo Gavazzi) and I connect the adapter to my laptop, I can communicate with the energy meter.

What am I missing?

thank you very much in advance!

Venus OS

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Modifications Space

Node Red Space

Answer 1 · 2022-11-06T04:16:41Z

joseal answered · Nov 06, 2022 at 04:16 AM

ok after a bit more investigation... it seems that the dbus-modbus-client coming with the latest Venus OS release only supports EM24 energy meters:

https://github.com/.../dbus.../blob/master/carlo_gavazzi.py

Am I reading it right?

if so, is it different if I'm using a Cerbo GX instead of a RPI4 with Venus OS (because ESS documentation suggests an ET112 directly connected to Cerbo GX)?

Or, similar to what was done for the SDM630, did someone wrote new libs to add the ET112?

thanks in advance!

1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

pau1phi11ips commented · Nov 06, 2022 at 09:42 PM

The driver you linked to is just for Modbus over TCP and hence why only the EM24 is included in that one.

0 ·

Answer 2 · 2022-11-06T09:19:04Z

bathnm answered · Nov 06, 2022 at 09:19 AM

@joseal The VenusOS code is exactly the same. So if one dose not support it, neither will the other.

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Answer 3 · 2022-11-06T10:42:33Z

cbscpe answered · Nov 06, 2022 at 10:42 AM

Which brings me back to my original question. Which interface can I use on the Raspberry Pi to connect to the ET112. The ET112 is officially supported as Victron Energy Meter (there is even a victron energy label on the box where the ET112 came from). In other words:

Can I use the RS485 of the RS485/CAN-Bus Hat of Waveshare, can I use a generic USB->RS485 Adapter or do I have to use the Victron USB to RS485 cable.

1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

pau1phi11ips commented · Nov 06, 2022 at 09:36 PM

I've only ever used the Victron RS485 cable and never had a problem with connection with those.

0 ·

Answer 4 · 2022-11-06T10:54:11Z

bathnm answered · Nov 06, 2022 at 10:54 AM

@cbscpe any generic RS485 adapter should work. To debug this you are likely to need to get ssh console access to see what is happening.

When a serial interface is detected a service starts to run called serial starter. This will run through a number of possible services to identify what is on the end of the connection and start the correct service.

This is what my serial start log shows. Found through cat /var/log/serial-starter/current | tai64nlocal

2022-11-03 12:15:13.185419500 INFO: Start service dbus-modbus-client.serial.ttyUSB2 once
2022-11-03 12:15:20.569522500 INFO: Start service gps-dbus.ttyUSB2 once
2022-11-03 12:15:29.961157500 INFO: Start service vedirect-interface.ttyUSB2 once
2022-11-03 12:15:35.266304500 INFO: Start service dbus-cgwacs.ttyUSB2 once
2022-11-03 12:15:38.524557500 INFO: Start service dbus-fzsonick-48tl.ttyUSB2 once
2022-11-03 12:15:41.937204500 INFO: Start service dbus-imt-si-rs485tc.ttyUSB2 once

It cycled through and detected my RS485 device as an IMT.

I did have some issues with one or two of the USB <> RS485 converters in that they seemed to generate issues unless a terminating resistor was installed. Can only assume some either have them built in and others do not.

As long as the RS485 <> USB is using a standard generic chip it should work.

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Answer 5 · 2022-11-06T13:02:31Z

cbscpe answered · Nov 06, 2022 at 01:02 PM

Thanks for the debugging hint. That helped to find out my first USB->RS485 Adapter was not even detected by the Linux, although it worked with Windows and the Carlo Gavazzi UCS software. Fortunately I have some other brands at hand which seem to be recognised.

@400000006367a3b51af24ecc INFO: Create daemontools service dbus-cgwacs.ttyUSB0
@400000006367a3bb1f4a5e4c INFO: Start service dbus-cgwacs.ttyUSB0 once
@400000006367a3c22dd74c54 INFO: Create daemontools service dbus-fzsonick-48tl.ttyUSB0
@400000006367a3c8309dabcc INFO: Start service dbus-fzsonick-48tl.ttyUSB0 once
@400000006367a3cc040ae3a4 INFO: Create daemontools service dbus-imt-si-rs485tc.ttyUSB0
@400000006367a3d206c8138c INFO: Start service dbus-imt-si-rs485tc.ttyUSB0 once
@400000006367a3d515cfa41c INFO: Create daemontools service dbus-modbus-client.serial.ttyUSB0
@400000006367a3db1885560c INFO: Start service dbus-modbus-client.serial.ttyUSB0 once

And now Venus OS shows one Single Phase Energy Meter. So now I'm prepared for the next tests with my test system.

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Answer 6 · 2022-11-06T14:16:52Z

ok, my 3 different adapters show this, any idea?

2022-11-06 13:58:01.090593500 INFO: Create daemontools service vedirect-interface.ttyUSB0
2022-11-06 13:58:07.138210500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 13:58:12.801763500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 13:58:22.079060500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 13:58:27.305914500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 13:58:36.585147500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 13:58:41.813999500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 13:58:51.093316500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 13:58:56.318932500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 13:59:05.596410500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 13:59:11.216661500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 13:59:20.493536500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 13:59:25.716468500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 13:59:34.997289500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 13:59:40.225611500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 13:59:49.505347500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 13:59:54.734567500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:00:04.014318500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:00:09.245225500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:00:18.524370500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:00:23.750724500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:00:33.033191500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:00:38.276888500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:00:47.561100500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:00:52.782006500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:01:02.060616500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:01:07.289393500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:01:16.570678500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:01:21.796355500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:01:31.075393500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:01:36.305376500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:01:47.596917500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:01:52.826959500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:02:02.105946500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:02:07.333238500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:02:16.626555500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:02:21.847124500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:02:31.130050500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:02:36.362583500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:02:45.642845500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:02:50.866283500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:03:00.143062500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:03:07.388519500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:03:16.666446500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:03:21.892266500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:03:31.170208500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:03:36.396504500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:03:45.681707500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:03:50.912289500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:04:00.190965500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:04:05.417752500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:04:14.697207500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:04:20.319296500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:04:29.600457500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:04:34.827806500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:04:44.111991500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:04:49.343837500 INFO: Start service gps-dbus.ttyUSB0 once
2022-11-06 14:04:58.620727500 INFO: Start service vedirect-interface.ttyUSB0 once
2022-11-06 14:05:03.846060500 INFO: Start service gps-dbus.ttyUSB0 once

Answer 7 · 2022-11-06T14:58:32Z

Actually, I've two different scenarios:

1) the wave share usb to rs485 (b) adaptor, it gets detected as ttyACM0 and its udevadm info gives this:

root@raspberrypi4:/dev/serial-starter# udevadm info --query=property /dev/ttyACM0
DEVLINKS=/dev/serial-starter/ttyACM0 /dev/serial/by-id/usb-1a86_USB_Single_Serial_54D2060968-if00 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0
DEVNAME=/dev/ttyACM0
DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.0/tty/ttyACM0
ID_BUS=usb
ID_MODEL=USB_Single_Serial
ID_MODEL_ENC=USB\x20Single\x20Serial
ID_MODEL_FROM_DATABASE=VL805 USB 3.0 Host Controller
ID_MODEL_ID=55d3
ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0
ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_2_1_0
ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
ID_PCI_INTERFACE_FROM_DATABASE=XHCI
ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
ID_REVISION=0445
ID_SERIAL=1a86_USB_Single_Serial_54D2060968
ID_SERIAL_SHORT=54D2060968
ID_TYPE=generic
ID_USB_CLASS_FROM_DATABASE=Communications
ID_USB_DRIVER=cdc_acm
ID_USB_INTERFACES=:020201:0a0000:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=1a86
ID_VENDOR_ENC=1a86
ID_VENDOR_FROM_DATABASE=QinHeng Electronics
ID_VENDOR_ID=1a86
MAJOR=166
MINOR=0
SUBSYSTEM=tty
USEC_INITIALIZED=695220653

2) the other two chinese adaptors, get detected as ttyUSB0 and its udevadm info gives this:

root@raspberrypi4:/dev/serial-starter# udevadm info --query=property /dev/ttyUSB0
DEVLINKS=/dev/serial-starter/ttyUSB0 /dev/serial/by-id/usb-Silicon_Labs_CP2104_USB_to_UART_Bridge_Controller_00FDA2E5-if00-port0 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0-port0
DEVNAME=/dev/ttyUSB0
DEVPATH=/devices/platform/scb/fd500000.pcie/pci0000:00/0000:00:00.0/0000:01:00.0/usb1/1-1/1-1.2/1-1.2:1.0/ttyUSB0/tty/ttyUSB0
ID_BUS=usb
ID_MODEL=CP2104_USB_to_UART_Bridge_Controller
ID_MODEL_ENC=CP2104\x20USB\x20to\x20UART\x20Bridge\x20Controller
ID_MODEL_FROM_DATABASE=CP2102/CP2109 UART Bridge Controller [CP210x family]
ID_MODEL_ID=ea60
ID_PATH=platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0
ID_PATH_TAG=platform-fd500000_pcie-pci-0000_01_00_0-usb-0_1_2_1_0
ID_PCI_CLASS_FROM_DATABASE=Serial bus controller
ID_PCI_INTERFACE_FROM_DATABASE=XHCI
ID_PCI_SUBCLASS_FROM_DATABASE=USB controller
ID_REVISION=0100
ID_SERIAL=Silicon_Labs_CP2104_USB_to_UART_Bridge_Controller_00FDA2E5
ID_SERIAL_SHORT=00FDA2E5
ID_TYPE=generic
ID_USB_DRIVER=cp210x
ID_USB_INTERFACES=:ff0000:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=Silicon_Labs
ID_VENDOR_ENC=Silicon\x20Labs
ID_VENDOR_FROM_DATABASE=Cygnal Integrated Products, Inc.
ID_VENDOR_ID=10c4
MAJOR=188
MINOR=0
SUBSYSTEM=tty
USEC_INITIALIZED=2544117312

Where can I change the ID to force one of these adaptors to be recognized?

Answer 8 · 2022-11-06T15:22:42Z

joseal answered · Nov 06, 2022 at 03:22 PM

@cbscpe could you please share some info about the adapter that works?

thank you

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Answer 9 · 2022-11-06T16:22:53Z

cbscpe answered · Nov 06, 2022 at 04:22 PM

This is the one I was successfully using: USB to RS485 Adapter

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Answer 10 · 2022-11-06T16:23:22Z

cbscpe answered · Nov 06, 2022 at 04:23 PM

https://www.reichelt.de/ch/de/raspberry-pi-usb-rs485-schnittstelle-ch340c-rpi-usb-rs485-p242783.html?&nbc=1

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

Answer 11 · 2022-11-06T16:28:33Z

cbscpe answered · Nov 06, 2022 at 04:28 PM

If my investigations are correct, then you need to make sure that the Adapter uses the FT232R USB to Serial Chip, and it has to be a genuine one and not a fake copy. Use lsusb -v to show the vendor and device information

root@raspberrypi2:~# lsusb -v

Bus 001 Device 011: ID 0403:6001 Future Technology Devices International, Ltd FT232 Serial (UART) IC
Device Descriptor:
  bLength                18
  bDescriptorType         1
  bcdUSB               2.00
  bDeviceClass            0 
  bDeviceSubClass         0 
  bDeviceProtocol         0 
  bMaxPacketSize0         8
  idVendor           0x0403 Future Technology Devices International, Ltd
  idProduct          0x6001 FT232 Serial (UART) IC
  bcdDevice            6.00
  iManufacturer           1 FTDI
  iProduct                2 FT232R USB UART
  iSerial                 3 A50285BI
  bNumConfigurations      1
  Configuration Descriptor:
    bLength                 9
    bDescriptorType         2
    wTotalLength       0x0020
    bNumInterfaces          1
    bConfigurationValue     1
    iConfiguration          0 
    bmAttributes         0xa0
      (Bus Powered)
      Remote Wakeup
    MaxPower               90mA
    Interface Descriptor:
      bLength                 9
      bDescriptorType         4
      bInterfaceNumber        0
      bAlternateSetting       0
      bNumEndpoints           2
      bInterfaceClass       255 Vendor Specific Class
      bInterfaceSubClass    255 Vendor Specific Subclass
      bInterfaceProtocol    255 Vendor Specific Protocol
      iInterface              2 FT232R USB UART
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x81  EP 1 IN
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
      Endpoint Descriptor:
        bLength                 7
        bDescriptorType         5
        bEndpointAddress     0x02  EP 2 OUT
        bmAttributes            2
          Transfer Type            Bulk
          Synch Type               None
          Usage Type               Data
        wMaxPacketSize     0x0040  1x 64 bytes
        bInterval               0
can't get device qualifier: Resource temporarily unavailable
can't get debug descriptor: Resource temporarily unavailable
Device Status:     0x0000
  (Bus Powered)

2

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

joseal commented · Nov 06, 2022 at 05:36 PM

Thank you very much!

In the meantime, I did some more investigation, I've figured out how this works and I was able to all my adaptors to work...

Basically, the /etc/udev/rules.d/serial-starter.rules file is where the service routing is defined based on the respective Model ID.

So, if we edit the file and add a new line with the model ID of your adaptor (pointing to Carlo Gavazzi VE service), it will make the trick.

Now, this will require a manual step on every update... so, I'm now trying to flash my adaptor's eeprom with the same model ID as the Victron hardware (this way it will be the same as use their cable)...

I will share more details, if I'm able to change its ID.

My file:

ACTION=="add", SUBSYSTEM=="tty", SUBSYSTEMS=="platform|usb-serial", SYMLINK+="serial-starter/%k"
ACTION=="remove", SUBSYSTEM=="tty", SUBSYSTEMS=="platform|usb-serial", RUN+="/opt/victronenergy/serial-starter/cleanup.sh %k"

# The VE USB RS485 has a FT232R, but that chip can also rs232 etc, so also check default
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="FT232R_USB_UART",            ENV{VE_SERVICE}="rs485:default"
# Older versions have specific id_model so that is rs485 for sure
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="USB-RS485_Cable",            ENV{VE_SERVICE}="rs485"
# Isolated rs485
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="USB485_Iso_stick",           ENV{VE_SERVICE}="rs485"
# The Zigbee USB to rs485 show up as Serial_Controller_D, so check cgwacs as well
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="USB-Serial_Controller_D",    ENV{VE_SERVICE}="cgwacs:default"
# 2nd generation Zigbee converter - DRF2658C (USB)
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="CP2102_USB_to_UART_Bridge_Controller", ENV{VE_SERVICE}="cgwacs:default"
# DRF2658C Zigbee converter with CH340 chip
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="USB2.0-Serial", ENV{VE_SERVICE}="cgwacs:default"

# VE.Direct cable should have a specific model-id, if not set it is a FT232EX.
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="VE_Direct_cable",            ENV{VE_SERVICE}="vedirect"
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="FT232EX",                    ENV{VE_SERVICE}="vedirect:default"

ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="MK3-USB_Interface",          ENV{VE_SERVICE}="mkx"

### New Line for my chinese adaptor ###
ACTION=="add", ENV{ID_BUS}=="usb", ENV{ID_MODEL}=="CP2104_USB_to_UART_Bridge_Controller", ENV{VE_SERVICE}="cgwacs:default"

0 ·

joseal commented · Nov 07, 2022 at 01:56 AM

Hi again,

after a few more hours investigating this topic, I was finally able to understand how this is handled under Venus OS and make it work with my chinese adaptors.

Basically, the reason why only victron adaptors and a few other adaptors work, it has to be with product description text (product ID model) provided by the non-vitron adaptors.

For example, one of my chinese adaptors by default presents himself as "CP2104_USB_to_UART_Bridge_Controller":

root@raspberrypi4:~# lsusb -s 001:005 -v Bus 001 Device 005: ID 10c4:ea60 Cygnal Integrated Products, Inc. CP2102/CP2109 UART Bridge Controller [CP210x family] Device Descriptor: ... idVendor 0x10c4 Cygnal Integrated Products, Inc. idProduct 0xea60 CP2102/CP2109 UART Bridge Controller [CP210x family] bcdDevice 1.00 iManufacturer 1 Silicon Labs iProduct 2 CP2104_USB_to_UART_Bridge_Controller iSerial 3 00FDA2E5 ....

But looking at /etc/udev/rules.d/serial-starter.rules, we can see all recognized IDs and we can also add our adapter's ID:

Edited the file and rebooted the OS, the ET112 is now detected:

The problem of this approach is that requires a manual step on each OS update!

However, instead of add the adaptor's ID to the rules file, we can update the adaptor's description using its customization tool:

And Venus OS will detect it as a vitron adaptor, without require us to change anything on the OS!

Hope this post helps others save some time, in case they need an USB to RS485 adaptor and they don't have access to the orginal victron cable (always prefered).

0 ·

1667786187557.png (70.8 KiB)

1667786348504.png (13.8 KiB)

1667786436400.png (37.3 KiB)

Answer 12 · 2022-11-07T08:46:48Z

@joseal Do any of your adapters get identified?

Take a look at the serial-starter.rules on udev on the RPI and Cerbo. There is a chance that the serial-starter is not being triggered for the RS485, as it is not being detected.

In your udevadm info --query=property /dev/tty.... output I did not see any of these lines. These are controlled by that udev file.

VE_SERVICE=rs485:default

However you do have these lines in the udev output..

DEVLINKS=/dev/serial-starter/ttyACM0 /dev/serial/by-id/usb-1a86_USB_Single_Serial_54D2060968-if00 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0

AND

DEVLINKS=/dev/serial-starter/ttyUSB0 /dev/serial/by-id/usb-Silicon_Labs_CP2104_USB_to_UART_Bridge_Controller_00FDA2E5-if00-port0 /dev/serial/by-path/platform-fd500000.pcie-pci-0000:01:00.0-usb-0:1.2:1.0-port0

Therefore I suspect without the VE_SERVICE it is to trying to start these as RS485 devices and that is why your logs are only showing gps-dbus.ttyUSB0 and vedirect-interface.ttyUSB0 for the SUB0 and nothing or the ACM0

I suspect this is as simple as the devices you have are not being detected and initialised. This will be down to using non tested adapters, or adapters not based on chipsets that have been tested. With some patience I am sure you an get them working with modifications to udev rules files.. Just record the changes to various files so you can populate them following an upgrade when these files will be replaced.

For reference my RS485 which works without an issues gives this output....

udevadm info --query=property /dev/ttyUSB2
DEVLINKS=/dev/serial-starter/ttyUSB2 /dev/serial/by-id/usb-FTDI_FT232R_USB_UART_AB0MFQYI-if00-port0 /dev/serial/by-path/platform-1c14000.usb-usb-0:1.4:1.0-port0
DEVNAME=/dev/ttyUSB2
DEVPATH=/devices/platform/soc/1c14000.usb/usb1/1-1/1-1.4/1-1.4:1.0/ttyUSB2/tty/ttyUSB2
ID_BUS=usb
ID_MODEL=FT232R_USB_UART
ID_MODEL_ENC=FT232R\x20USB\x20UART
ID_MODEL_FROM_DATABASE=FT232 Serial (UART) IC
ID_MODEL_ID=6001
ID_PATH=platform-1c14000.usb-usb-0:1.4:1.0
ID_PATH_TAG=platform-1c14000_usb-usb-0_1_4_1_0
ID_REVISION=0600
ID_SERIAL=FTDI_FT232R_USB_UART_AB0MFQYI
ID_SERIAL_SHORT=AB0MFQYI
ID_TYPE=generic
ID_USB_DRIVER=ftdi_sio
ID_USB_INTERFACES=:ffffff:
ID_USB_INTERFACE_NUM=00
ID_VENDOR=FTDI
ID_VENDOR_ENC=FTDI
ID_VENDOR_FROM_DATABASE=Future Technology Devices International, Ltd
ID_VENDOR_ID=0403
MAJOR=188
MINOR=2
SUBSYSTEM=tty
USEC_INITIALIZED=6596800
VE_SERVICE=rs485:default

Answer 13 · 2023-05-19T07:30:20Z

frank-online answered · May 19, 2023 at 07:30 AM

I do have a similar problem with the CP2102.

Could you please tell me, where I can download (link?) the CP21xx Customization Utility? Or perhaps you upload the file to filetransfer / dropbox / google / or any other cloud?

2 |3000

Attachments: Up to 8 attachments (including images) can be used with a maximum of 190.8 MiB each and 286.6 MiB total.

question

Connecting an ET-112 to Venus OS on a RP4b

Related Resources

question details

Modifications Space

Node Red Space

question

Connecting an ET-112 to Venus OS on a RP4b

Related Resources

question details

Related Questions

Modifications Space

Node Red Space