ergoCub 1.3 S/N:002 – Robot doesn't start due to `left_arm-eb31-j4_6` IP 10.0.1.31 not found

[SimoneMic]

Robot Name 🤖

ergoCub 1.3 S/N:002

Request/Failure description

Starting the robot with: yarprobotinterface --config ergocub.xml --enable_tags "(enable_ros2)" --disable_tags "(disable_left_hand)"
On the branch 'icub-tech/devel-ergoCubSN002'.

The following error occurs:

[ERROR] theNVmanager::Impl::wait() had a timeout for BOARD left_arm-eb31-j4_6 IP 10.0.1.31 and nv ID32 = 0x00030001 -> IND = 0, TAG = eoprot_tag_mn_service_status_commandresult
[ERROR] theNVmanager::Impl::command() fails a wait() from IP 10.0.1.31 for nv ID32 = 0x00030001 -> IND = 0, TAG = eoprot_tag_mn_service_status_commandresult
[ERROR] embObjMotionControl::open() has an error in call of ethResources::serviceVerifyActivate() for BOARD left_arm-eb31-j4_6 (IP 10.0.1.31) 
[ERROR] |yarp.dev.PolyDriver|left_arm-eb31-j4_6-mc| Driver <embObjMotionControl> was found but could not open

Detailed context

The robot doesn't start even the calibration phase, but the YRI closes.
Disabling the left arm the calibration starts correctly.

The firmware situation of the boards is as in picture:

Additional context

No response

How does it affect you?

No response

[aazocar7]

Hi,
I forgot to update this issue, but the problem has been solved by replacing the AMC_BLDC board (the 31B0) because, as you can clearly see in the photo, the connector where the power supply comes in has burned out and possibly due to a piece of debris falling from the forearm mechanism (see second photo).
Another cause of the problem was that a component on the board, circled in red, had been damaged and had practically come off.

However, the problem was solved and the robot was working properly again.

cc @Fabrizio69 @SimoneMic

[Fabrizio69]

Thanks @aazocar7... at this point we close this issue