Skip to content

ergoCub 1.3 S/N:002 – Intermittent issues with head board head-eb21-j3Β #2230

@SimoneMic

Description

@SimoneMic

Robot Name πŸ€–

ergoCub 1.3 S/N:002

Request/Failure description

After several attempts the robot started correctly, but many times the following error happened at startup:

[ERROR] theNVmanager::Impl::ask() had a timeout for BOARD head-eb21-j3 IP 10.0.1.21 and nv ID32 = 0x00000002 -> IND = 0, TAG = eoprot_tag_mn_comm_status_managementprotocolversion

Blocking thus the calibration.
The solution was to restart the motors each time and re-launching the calibration.

Detailed context

At first the robot wasn't starting with errors in the like:

[ERROR] theNVmanager::Impl::ask() had a timeout for BOARD head-eb21-j3 IP 10.0.1.21 and nv ID32 = 0x00000002 -> IND = 0, TAG = eoprot_tag_mn_comm_status_managementprotocolversion

and

[ERROR] theNVmanager::Impl::wait() had a timeout for BOARD head-eb21-j3 IP 10.0.1.21 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.21 for nv ID32 = 0x00030001 -> IND = 0, TAG = eoprot_tag_mn_service_status_commandresult
[ERROR] EthResource::serviceCommand() failed an acked activation request to BOARD head-eb21-j3 with IP 10.0.1.21 after 3 attempts each with waiting timeout of 0.5 seconds

After several attempts, and trying to disable the head, the robot started "normally" with the head in the following state:

Image

The pitch joint is in: No fault detected fault state

Finally the robot started normally, at the 5th attempt.

Additional context

Probably it's a wiring issue (intermittent contact)

How does it affect you?

No response

Metadata

Metadata

Type

No type

Projects

Status

Triage

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions