robotology / icub-tech-support

Virtual repository that provides support requests for individual robots
GNU General Public License v2.0
20 stars 1 forks source link

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

Closed elandini84 closed 1 month ago

elandini84 commented 2 months ago

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.

valegagge commented 1 month ago

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

cc @Fabrizio69

AntonioAzocar commented 1 month ago

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

andresoll commented 1 month ago

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

AntonioConsilvio commented 1 month ago

Hi guys! Any feedback on this issue?

cc @AntonioAzocar @andresoll @ste93

ste93 commented 1 month ago

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.

AntonioConsilvio commented 1 month ago

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!