icub-tech-support icon indicating copy to clipboard operation
icub-tech-support copied to clipboard

R1 S/N:003 – Wireless fault not working properly

Open elandini84 opened this issue 1 year ago • 1 comments

Robot Name 🤖

R1 S/N:003

Request/Failure description

The wireless external fault button does not work. If the receiver board is connected, the robot is always in a fault state

Detailed context

The robot cannot work with the external fault button connected to the robot. Yarprobotinterface log shows for all the joints the "External fault button pressed" error message even if the wireless button is not pressed.

Additional context

No response

How does it affect you?

This situation does not allow us to use the external fault which is a valuable tool for our tests in Turin next week.

elandini84 avatar Apr 30 '24 14:04 elandini84

Hi @AntonioConsilvio, me and @andresoll we are aligned on this issue. Please contact us when you start working on it.

cc @Fabrizio69

valegagge avatar May 06 '24 07:05 valegagge

Hi! This morning, I and @andresoll did the work on the robot and on disassembling the wiring we found this connector slightly detached from the fault board and that is why the fault was giving problems. In fact, once it was reconnected properly, it no longer gave any problems and to prevent it from coming loose again I put a drop of glue on it. Maybe Andrea will give more information

connettore fault R1

cc @Fabrizio69 @valegagge

AntonioAzocar avatar May 21 '24 12:05 AntonioAzocar

thank you @AntonioAzocar, I asked @ste93 to prove that everything is working properly. This morning I will go to the robot arena to verify that everything is working.

cc @valegagge

andresoll avatar May 22 '24 06:05 andresoll

Hi guys! Any feedback on this issue?

cc @AntonioAzocar @andresoll @ste93

AntonioConsilvio avatar May 23 '24 07:05 AntonioConsilvio

Yes sorry, yesterday we did a test together with @andresoll @sofiafaraci and @elandini84 and it worked well for 6h and 30 min, we suppose that the old problems were caused by the faulty connector and probably the charger of the button.

ste93 avatar May 23 '24 09:05 ste93

Great @ste93, thank you for the feedback.

Good job @AntonioAzocar @andresoll! 🚀

@ste93 @elandini84 feel free to open a new issue if the problem reoccurs.

Closing!

AntonioConsilvio avatar May 23 '24 09:05 AntonioConsilvio