search

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

ergoCub 1.1 S/N:002 – Torso Board not starting when launching YRI #1798

Closed SimoneMic closed 1 month ago

SimoneMic commented 2 months ago

Robot Name 🤖

ergoCub 1.1 S/N:002

Request/Failure description

While launching the YRI with ergocub_all_ros2.xml from the robot torso, a lot of errors tied to unreachable boards occur. Even after several startup of the same YRI I have noticed that the torso wasn't opening correctly its rpc port, since many times it wasn't appearing in yarp name list No errors, nor HW fault, in the motor gui.

Detailed context

Here the error message:

[ERROR] theNVmanager::Impl::ask() had a timeout for BOARD torso-eb5-j0_2 IP 10.0.1.5 and nv ID32 = 0x0100010c -> IND = 1, TAG = eoprot_tag_mc_joint_status_core_modes_controlmodestatus
[WARNING] EthResource::getRemoteValue() cannot have a reply from BOARD torso-eb5-j0_2 with IP 10.0.1.5 at attempt # 1 w/ timeout of 0.2 seconds
[ERROR]   FATAL: EthResource::getRemoteValue() DID NOT have replies from BOARD torso-eb5-j0_2 with IP 10.0.1.5  even after 0.200059 seconds: CANNOT PROCEED ANY FURTHER
[ERROR] Failure of askRemoteValue() inside embObjMotionControl::doneRaw(axis= 1 ) for  BOARD torso-eb5-j0_2 (IP 10.0.1.5)

Additional context

No response

How does it affect you?

No response

AntonioConsilvio commented 1 month ago

Hi! the ethernet problem was caused by the nearness of the 2FOC board to the EMS EB5. Once the two boards were separated, the problem did not reappear! Closing!