-
Notifications
You must be signed in to change notification settings - Fork 21
OSError initialize robot #6
Comments
Hi @Net-Mist! This issue can come from a few different issues:
|
Hi ! The file /dev/ttyACM0 exists. I tried to use the low level communication to ping the motor but it failed. import pypot
import pypot.dynamixel.protocol.v1 as protocol
from pypot.dynamixel import DxlIO
io = DxlIO(port='/dev/ttyACM0', baudrate=1000000)
ids = io.scan() It raises an error : pypot.dynamixel.io.abstract_io.DxlCommunicationError: could not parse received data bytearray(b'\x00') after sending DxlPingPacket(id=0) After searching on google it seems it means:
Do you think of other reasons why this is happening ? Thank you for your help |
Yes it's usually one of:
If you see the led turn red on the last motor of your chain when the power supply is plugged it should not be the issue. Are you using a 12V power supply? To check the id you can use pypot with the scan function. The only option to debug the duplicate id is to connect the motor one by one. |
This cut wired is indeed intentional. It lets the communication through and not the power. We used it to have two power supply on the robot: one for the first motor (the one using most torque) and the rest of the robot. I'll post the wiring diagram soon. |
Hello,
I tried to connect to a new Reachy robot, but after installing the python module I get this error :
File "
/reachy/software/build/lib/reachy/reachy.py", line 79, in new/.local/lib/python3.6/site-packages/pypot/creatures/abstractcreature.py", line 128, in newrobot = AbstractPoppyCreature.new(cls, *args, **kwargs)
File "
raise OSError('Could not initalize robot: {} '.format(exc_inst))
OSError: Could not initalize robot: Could not find the motors (16, 10, 11, 12, 13, 14, 15) on bus /dev/ttyACM0.
So it seems Linux (Ubuntu 18.04 LTS) can see the robot, connect to it but can't find the motors.
Do you know why this error is happening ?
The text was updated successfully, but these errors were encountered: