Welcome to the Luos community. I just reproduce your setup to get your bug.
I use a 0.0.2 USB shield on a 0.2.1 L0 board loaded with the 0.5.1 firmware revision and a potentiometer with a 0.2.0 L0 board with the 0.5.1 firmware revision. I run my test using pyluos 1.1.
The only error I have is the firmware revision number.
Another difference in my picture is the text after the robot object creation. We noticed that on some windows computers, it seems to be a Jupyter display bug. Don’t worry this display bug is just display.
For your knowledge, a module can be excluded if he don’t receive or take to many time to manage one of your command. Some specific variables read, such as firmware_revision, have to send a command to the module to get the value.
On the contrary, some others such as rot_position don’t have to send any command, pyluos receive automatically updates of this value.
So, looking at your rot_position value pyluos never receive any update from your potentiometer as if he crashed just after detection.
This is really strange. Do you have other modules working with your Usb module?
If yes, the problem probably come from your potentiometer, but I can’t say if its a software or an hardware problem for now.
@Didbo seems to have quite similar trouble using 0.02 USB shield on a 0.2.0 L0 board loaded with the 0.5.1 firmware revision and a Dynamixel V1 board loaded with 0.5.1 firmware revision linked with an AX-12 motor.
@Didbo do you have any insight about that?
I gona fix the 0.5.1 release today, I lets you know when it’s done.