ergoCub 1.1 S/N:001 – head not reachable and torso slow

[mebbaid]

Robot Name 🤖

None

Request/Failure description

while doing some experiments on navigation with @SimoneMic we lost connection with the head (which is needed for the nav stack). We tried to ping the head but it is unreachable. In addition, pinging the torso takes on average 200 ms (which seems high)

Detailed context

while doing some experiments on navigation with @ we lost connection with the head (which is needed for the nav stack). We tried to ping the head but it is unreachable. In addition, pinging the torso takes on average 200 ms (which seems high)

Additional context

No response

How does it affect you?

This issue is blocking for running Navigation with the robot

[github-actions[bot]]

⚠️ Detected missing mandatory information

Hi @mebbaid 👋🏻

Some of the following points need your attention.

You are required to:

• [ ] enter the Robot Name, adjust the Issue Title and add the Robot Label.
• [ ] give the issue a meaningful Title.
• [x] provide a Detailed Context.

_{Please, mark the points above as solved once done.} [^1]: To get to know the allowed options for the dropdown fields, you may peruse the template.

[sgiraz]

Hi @mebbaid,

We can compare the ping time with other robots, but yep, 100+ ms seems high. Maybe the output of a traceroute command may help us to track the network traffic between the laptop and the torso.

cc @AntonioConsilvio @davidelasagna @Nicogene

[SimoneMic]

@GiulioRomualdi told me that after a complete reboot of the system (server, router and PCs) the ping has returned to acceptable levels. However we need the head PC to be working quite soon, due to a demo that has been anticipated on the 31st. We'd like to do some demo preparation tests on Monday (late) afternoon.

Thank you and sorry for the pressing

[GiulioRomualdi]

I @SimoneMic this morning, I checked the head and it was warking

[sgiraz]

We'd like to do some demo preparation tests on Monday (late) afternoon.

Ok guys,

Please keep the network traffic monitored to see if the problem happens again.

[steb6]

Today we had a similar issue about slow connection speed with the torso:

traceroute to 10.0.2.2 (10.0.2.2), 30 hops max, 60 byte packets
 1  * ergocub-torso (10.0.2.2)  170.508 ms *

cc @SimoneMic

[sgiraz]

Hi guys,

Thanks for keep monitoring this issue, we'll futher investigate on it.

In the meantime, next time it happens, I would ask you to provide as much context info as possible such as CPU workload (htop for the torso and jtop for the head) and the network traffic (vnStat)

@steb6 @GiulioRomualdi @SimoneMic @AntonioConsilvio

[sgiraz]

Hi guys,

Any news on this? Is still the problem occurring?

cc @steb6 @SimoneMic @mebbaid

[SimoneMic]

Actually it seems to be working fine. Haven't had this issue in a while now

[sgiraz]

Hi @SimoneMic, Thanks for your feedback! If you agree, I would proceed to close the issue right now.

[!Note] Please, keep in mind to check the CPU workload (w/ htop or jtop for example) in case it happens again.

cc @AntonioConsilvio @davidelasagna

[mebbaid]

If you agree, I would proceed to close the issue right now.

agreed. In case of things recurring down the line, we will open a separate issue and reference this one.

[sgiraz]

Hi @mebbaid

Ok thanks! Closing!