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?
Trace the address actually passed to the availability request, not just the displayed selection; ping and the application may be reading different saved values.
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.
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.