ergoCub 1.1 S/N:001 – yarprobotinterface unable to connect to leg boards eb6, eb7, eb8, eb9

[G-Cervettini]

Robot Name 🤖

ergoCub 1.1 S/N:001

Request/Failure description

The yarprobotinterface has been restarted after a minor fall while walking through the WalkingModule to ensure that the calibration was still correct. After restarting this module we were no longer able to connect to some of the control boards in the legs:

[ERROR] theNVmanager::Impl::ask() had a timeout for BOARD right_leg-eb6-j0_3 IP 10.0.1.6 and nv ID32 = 0x00000002 -> IND = 0, TAG = eoprot_tag_mn_comm_status_managementprotocolversion
[ERROR] theNVmanager::Impl::ask() had a timeout for BOARD right_leg-eb7-j4_5 IP 10.0.1.7 and nv ID32 = 0x00000002 -> IND = 0, TAG = eoprot_tag_mn_comm_status_managementprotocolversion
[ERROR] theNVmanager::Impl::ask() had a timeout for BOARD left_leg-eb8-j0_3 IP 10.0.1.8 and nv ID32 = 0x00000002 -> IND = 0, TAG = eoprot_tag_mn_comm_status_managementprotocolversion
[ERROR] theNVmanager::Impl::ask() had a timeout for BOARD left_leg-eb9-j4_5 IP 10.0.1.9 and nv ID32 = 0x00000002 -> IND = 0, TAG = eoprot_tag_mn_comm_status_managementprotocolversion

Detailed context

Most likely the E5 cable got damaged/detached during the fall.

I tried to run the FirmwareUpdater and run a discover, this confirmed that the boards from 10.0.1.6 to 10.0.1.9 are not reachable:

Additional context

log_ergocub-torso_yarprobotinterface_1251.zip

How does it affect you?

I wasn't able to finish my walking experiments.

[AntonioConsilvio]

Hi @G-Cervettini, the problem was caused by the E5 cable on the side connected to the EB6 board (Right_leg). The crimps were coming out of the connector:

I reinserted the crimps and fixed the connector so that the crimps would not come out, and then I put glue so that the crimps would stay in place.

The robot was tested together with @GiulioRomualdi and it works properly!

Closing!✅