Reachy 2 core won't start after Bedrock IPC reassembly (Logs included)

Core.txt (189.3 KB)

grippers.txt (351.4 KB)

Hi everyone,

I’m currently working with a Reachy 2 and could use some help troubleshooting a startup issue.

We recently had to replace the main IPC (Bedrock V3000) due to a hardware failure. We went through the whole software setup process (udev rules, EtherCAT checks, etc.) and tested the robot with the infinite_grooving.py script while the new Bedrock was still unmounted. Everything worked perfectly and the robot moved without issues.

The problem started right after we physically installed the Bedrock inside the torso and put the shell back together. Now, the reachy2-core fails to start.

Our main suspect is that a cable might have been accidentally disconnected, pinched, or loosened during the reassembly process. Since taking the whole torso apart again is quite tedious, we pulled the startup logs to see if we can pinpoint exactly which component is missing.

Has anyone experienced a similar issue or can spot in the logs which specific connection (EtherCAT node, camera, USB device…) is causing the core to crash? Any pointers on which specific cable to check would save us a lot of time!

Thanks in advance for the help.

Hello,

It seems like the grippers and/or antennas are not detected correctly.

You could try to start the core with the antennas and grippers in fake mode to see if this is the problem! To do so:

  1. Access the page <your-robot-ip>:5000, and click on Fake Articulation.

  1. Select the grippers and antennas, then Save Configuration.

  1. Eventually restart reachy2-core.

If the core starts while the grippers and antennas are in fake mode, then you should check the connections to these elements in the torso (blue lights when it is correctly initialized, remains red if not):

If everything seems to be correctly plugged, maybe you could try to apply the udev rules again.

Hi @Gaelle,

Thank you for the tip! We just tested the “Fake Articulation” mode as you suggested, and you were right.

When we set both the antennas and the grippers to fake mode, the core starts perfectly. We also tried alternating them (one in fake mode, the other in normal mode) to see if only one was causing the issue, but the core failed to start in both scenarios. This confirms that both the grippers and the antennas are failing to connect.

Additionally, while the core is running in fake mode, we checked the LEDs and they remain solid red.

Since both are failing at the same time and showing red LEDs, is there a common cable, hub, or power connection shared by both the grippers and the antennas that we might have accidentally loosened during the Bedrock installation?

Could you please point us to the specific cables or connectors we should check inside the torso? We are ready to open it up again and waiting for your instructions.

Best regards,

Álvaro Solana



Hi,

Just a gentle bump on this thread to see if you have any updates.

We are still stuck with the grippers and antennas showing solid red LEDs, and we are ready to open the torso again to check the wiring.

However, I noticed something else on the dashboard that might help pinpoint the exact issue: the standard cameras are working perfectly and showing the video feed, but the depth camera is not outputting anything at all.

Could this be related? Since the depth camera, grippers, and antennas are all failing simultaneously, is there a specific USB hub, shared cable, or power line connecting these components that we might have accidentally loosened during the Bedrock replacement?

A picture or a quick description of the layout would be incredibly helpful so we know exactly where to look inside the shell.

Thanks in advance, Álvaro

Hi @alvaro_solana,

Thanks for those details. For the dashboard, this is not related, it’s a known issue of the dashboard, you should be able to see the stream from the torso camera with the SDK Client.

You should check the cables of the antennas and the grippers. Each one starts from a U2D2, and is connected to the torso USB hub, then the hub is connected to the third USB port of the bedrock. (see the attached photos)

USB of the grippers to the hub:


USB of the antennas to the hub:

Hub to the bedrock:

There you can see a photo of the structure alone :

After verifying that all these cables are properly connected, if it still doesn’t work, we can try reconfiguring the udev rules. To do this, you can stop the core and WebRTC services (in the dashboard, under the “Services” section, click “Stop” for the reachy2-core and WebRTC services) and then run:

ssh bedrock@reachy2-pvt03.local
cd reachy2_pc_install
./udev.sh ## copy/paste the output on the topic if you can
udevadm control --reload-rules && udevadm trigger
sudo reboot

We hope this will solve your issue !

Claire

Hi Claire,

Great news! The issue is completely resolved now.

We ran the commands with sudo permissions and, after the reboot, the LEDs turned blue immediately. We have tested the robot and everything is working beautifully: the grippers open and close perfectly, and the antennas are moving flawlessly as well.

Thank you so much for your incredible support and patience throughout this whole process! We really appreciate your help.

Best regards,

Álvaro Solana

Logs_udev.txt (118.9 KB)

1 Like