Our workshop laptop sometimes pings the FR10, but its read-only availability check times out. I noticed the connection screen shows our controller address while an older address appears in the diagnostic log. Another laptop has worked, though we haven't retained its setup. Could the two checks be using different destinations?
FR10 connection screen and diagnostic log disagree about the address
AnnaCarter1025 · 2026年2月3日 00:46 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
5 条回复
Trace the address actually passed to the availability request, not just the displayed selection; ping and the application may be reading different saved values.
21分Maintainer traced it. Ping reads the selected address, but the availability helper retains the address loaded at startup. Changing the selection updates the screen without rebuilding that helper. The old destination in the log was real, not an old log entry.
16分Test startup and a subsequent selection change separately after the repair, since a correct fresh launch would not expose the stale helper you found.
9分Maintainer fixed the helper update. Tests now check the destination after startup and after changing the selection, and our workshop laptop reads the expected controller identity through the normal launcher. Thanks for pointing at the actual request; I was about to chase SDK versions on the other laptop.
22分Keep the request destination in that diagnostic log; it made a misleading connection screen possible to investigate.
19分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .