ttyRS485 used for communication between Connect+ and AIO

[mats-olov_rustad]

We have a cabinet with one Connect+ module connected on its left side through a PiBridge to a AIO module. If our logger application opens and uses the ttyRS485 device the Power LED of the AIO module is steadily red. If our logger application is configured not to open and use the ttyRS485 device the AIO Power led is stedaily green.

We interpret this behaviour to mean that there are software in the Connect+ module that uses the ttyRS485 device to communicate between the Connect+ and AIO modules. Is this a correct assumption?

With regards,

[dirk]

Hi mats-olov_rustad,

We have a cabinet with one Connect+ module connected on its left side through a PiBridge to a AIO module. If our logger application opens and uses the ttyRS485 device the Power LED of the AIO module is steadily red. If our logger application is configured not to open and use the ttyRS485 device the AIO Power led is stedaily green.

The RED Power LED indicates that the AIO module is in safe state because the watchdog timeout has been triggered. This could be caused by a communication failure on the PiBridge.

We interpret this behaviour to mean that there are software in the Connect+ module that uses the ttyRS485 device to communicate between the Connect+ and AIO modules. Is this a correct assumption?

Maybe this is a correct assumption to your device althouth it is NOT a usual behavior.

Could you please verify if the output of your device is similar to this:

Code: Select all

pi@RevPi40302:~ $ ll /dev/ttyRS485
lrwxrwxrwx 1 root root 7 Feb  3 08:49 /dev/ttyRS485 -> ttyUSB0