Hi Jan,

thank you for your feedback. Docker is not my preferred solution, but I would like to take a closer look at your setup.
Does your solution have limitations regarding supported RevPi gateways or revpimodio2 support? We use Profinet IRT Gateway, Profibus Gateway, RevPi Connect.

BR Markus

Debian Buster unterstützt Python in der Version 3.7. Der Security Support für Python 3.7 endet am 27.06.2023. Wir haben eine größere Anzahl RevPi Connect im Einsatz und benötigen eine stabile Lösung für ein Upgrade auf >= Python 3.8. Ideale Lösung wäre ein neue Image auf Basis Debian Bullseye. Welch...

Kann man ein "RevPi Gateway Profinet IRT" auch örtlich getrennt vom RevPi Connect (Verbindung über Patch-Kabel anstelle der Steckbrücke) betreiben? Wenn ja, was muss man bei der Einrichtung beachten?

What do you suggest as next steps?

The RevPi Connect+ consists of 3 circuit boards. Does it make sense to substitute one board after the other to find the problem? If yes, with which board should I start to prevent demaging other components?

LED A3 lights red, regardless if USB cable is plugged in or not.

Another RevPi which works ok, is always above 2.3W. But the 4 broken ones are 8GB devices and the other one is a 32GB device.

The RevPis consuming between 1.32 - 1.36W after power on.

It seems that USB disconnects right after the block device is created. Maybe this is an HW defect, but why 4 devices at the same time?

Here the log when I try it from a RaspberryPi 3: deviceadmin@HMI003:~/rpiboot/usbboot $ sudo ./rpiboot -v [sudo] password for deviceadmin: RPIBOOT: build-date Apr 21 2022 version 20220315~121405 445356e1 Waiting for BCM2835/6/7/2711... Loading embedded: bootcode.bin Device located successfully Initi...

No, the RevPi was directly connected to the Notebooks or RaspberryPi 3.