applicationrobot.English

简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。

FR10 connection screen and diagnostic log disagree about the address

AnnaCarter1025 · 2026年2月3日 00:46 UTC

已关闭
AN
AnnaCarter1025
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?
举报

5 条回复

HA
HassanArcher0356
回复 AnnaCarter1025

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分
举报
AN
AnnaCarter1025
回复 HassanArcher0356

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分
举报
HA
HassanArcher0356
回复 AnnaCarter1025

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分
举报
AN
AnnaCarter1025
回复 HassanArcher0356

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分
举报
HA
HassanArcher0356
回复 AnnaCarter1025

Keep the request destination in that diagnostic log; it made a misleading connection screen possible to investigate.

19分
举报

讨论已关闭

此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .