Workshop laptop sometimes gets a ping reply from the FR10 address, then the read-only identity query times out. Another laptop worked previously, with no useful notes left behind. IT noticed the responding hardware address changes between captures. What should we establish before this becomes another argument about the robot SDK?
Our FR10 address answers ping and still won't identify itself
TheoAllen0323 · 2026年2月11日 18:22 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
Have IT identify both responders first. Same destination address doesn't guarantee the same device answered.
11分IT 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分Our old bench PC kept an address somebody had reassigned. Worth checking the nearby equipment too.
21分And verify the identity reply afterwards, not only that ping becomes reliable.
4分回复 AdaBrown0912
IT 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分Does the actual identity query work now?
15分回复 AdaBrown0912
Yes, 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分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .