[niekas]

We have 2 KUKA robots and both have had same IP addresses for a very long time even though their IPs are set to be assigned dynamically.

A couple days ago, we were not able to connect to one of the robots. RoboDK connection was giving error but ping was successful. We thought of many things that could be causing the problem ever since RoboDK showed ping as successful. Never gave possibility that the IP had changed. (We also didn't try to ping from Terminal and that's on us.)

TL;DR: RoboDK ping was successful even though it shouldn't have been.

[Jeremy]

Just to make sure that I understand well.

The IP address of the robot changed, but when pinging with the old IP address with RDK the ping test was successful.

Jeremy

[niekas]

Just to make sure that I understand well.

The IP address of the robot changed, but when pinging with the old IP address with RDK the ping test was successful.

Jeremy

Yes Jeremy, that is exactly what has happened.