ergoCub 1.0 S/N:000 – `left_leg-eb9-j4_5` and `right_leg-eb7-j4_5` not found at startup

[SimoneMic]

Robot Name 🤖

ergoCub 1.0 S/N:000

Request/Failure description

After the substitution of the legs the robot doesn't start anymore.

When launching the YRI these errors show up:

[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
[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

Seems like some boards are not found.

Detailed context

I am on the icub-tech/devel-ergoCubSN000 branch.
The firmware updater shows all the boards in application mode.

Here the full log of the errors that are occurring:

left leg:

[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
[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
[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
[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
[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
[ERROR] EthResource::verifyBoardPresence() DID NOT have replies from BOARD left_leg-eb9-j4_5 with IP 10.0.1.9 after 21.0024 seconds: CANNOT PROCEED ANY FURTHER
[ERROR] EthResource::verifyEPprotocol() cannot verify BOARD left_leg-eb9-j4_5 with IP 10.0.1.9 : cannot proceed any further
[ERROR] embObjMultipleFTsensors: BOARD left_leg-eb9-j4_5 (IP 10.0.1.9)   open() fails to verifyEPprotocol... cannot continue 
[ERROR] |yarp.dev.PolyDriver|left_leg-eb9-j4_5-strain| Driver <embObjMultipleFTsensors> was found but could not open
[WARNING] Cannot open device left_leg-eb9-j4_5-strain

right leg:

[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 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 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 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 right_leg-eb7-j4_5 IP 10.0.1.7 and nv ID32 = 0x00000002 -> IND = 0, TAG = eoprot_tag_mn_comm_status_managementprotocolversion
[ERROR] EthResource::verifyBoardPresence() DID NOT have replies from BOARD right_leg-eb7-j4_5 with IP 10.0.1.7 after 21.0028 seconds: CANNOT PROCEED ANY FURTHER
[ERROR] EthResource::verifyEPprotocol() cannot verify BOARD right_leg-eb7-j4_5 with IP 10.0.1.7 : cannot proceed any further
[ERROR] embObjMultipleFTsensors: BOARD right_leg-eb7-j4_5 (IP 10.0.1.7)   open() fails to verifyEPprotocol... cannot continue 
[ERROR] |yarp.dev.PolyDriver|right_leg-eb7-j4_5-strain| Driver <embObjMultipleFTsensors> was found but could not open
[WARNING] Cannot open device right_leg-eb7-j4_5-strain

Additional context

No response

How does it affect you?

No response

[AntonioConsilvio]

Hello! I have resolved this issue.

The error was caused by a problem with the ETH connection (E6 cable).

I have fixed the connection and it is now working properly! 🚀