The commissioning laptop gets a ping reply from the FR5, then its documented identity request times out. A borrowed laptop worked once, with no useful setup notes. What would you capture before we blame the controller or change its settings?
Our FR5 laptop ping works while the identity request waits
DavidBrown0954 · 2025年10月17日 22:09 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
7 条回复
Capture the actual destination, adapter and selected route for both laptops, with the request version and complete read result; the old successful attempt needs reproducing under known conditions before it becomes a reliable comparison.
24分回复 TheoAli0236
The borrowed machine is available again. Both used the same bench connection, but one has a USB network adapter. We haven't recorded the route or actual destination used by the application.
19分Then same socket is only one shared detail (the software may still be taking another route).
10分回复 AnnaAli0242
Yes, Anna; I would have IT compare the service connection and local policy once those destinations and routes are known, with the SDK and configuration differences retained for software to review.
17分回复 TheoAli0236
IT is collecting that comparison. I found two settings files on ours, so I've asked software which one the running process actually loads. No controller changes made.
21分Two files are a clue, not a diagnosis; get the loaded path before deleting either.
5分David, did the paired check reproduce the success and timeout, or is that still being arranged?
19分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .