TheoAllen0323 · 11 Feb 2026, 18:22 UTC
Have IT identify both responders first. Same destination address doesn't guarantee the same device answered.
11 pointsIT has the two captured hardware addresses and the actual controller label. One responder is still unidentified. We've kept the failed identity queries with their captures instead of calling each ping a successful controller connection.
10 pointsOur old bench PC kept an address somebody had reassigned. Worth checking the nearby equipment too.
21 pointsAnd verify the identity reply afterwards, not only that ping becomes reliable.
4 pointsIT found a spare inspection PC using the same address and corrected the allocation under the workshop network plan. That explains the changing responder. We haven't changed the SDK or controller settings to chase it.
13 pointsDoes the actual identity query work now?
15 pointsYes, from our normal workshop shortcut, including after restarting the laptop. Returned identity matches the intended controller and IT has kept the route and allocation notes. Thanks Ada, the spare PC was sitting there looking completely unrelated to the robot problem.
13 pointsThis discussion is closed to new replies after six months without activity. Last activity: .