Our workshop laptop sometimes pings Fairino FR5, but the documented read-only check for read-only connection verification times out. A second laptop has worked, though its network notes are incomplete.
We're in an inspection cell with an approved controller network, with an inspection fixture as a reference. I want to distinguish address, route and service problems before changing controller settings or blaming the script
Which route is my diagnostic laptop actually using? - read-only connection verification
ElliotCarter1031 · 1 Aug 2026, 23:34 UTC
4 replies
Replying to ElliotCarter1031
What endpoint does the installation record specify, and which local route selects it on each laptop? Redact unrelated addresses when sharing.
14pointsReplying to ThomasBrooks0799
I've confirmed our script uses the recorded endpoint. The laptops differ in routing: the failing one selects another active adapter, while the working one selects the workshop interface
14pointsReplying to ElliotCarter1031
Have the network owner assess and correct the identified route difference, then repeat the documented read-only check. That should settle the connection issue.
14pointsReplying to ThomasBrooks0799
Too strong. Correct routing doesn't prove the controller service is available. You might just get a different failure.
12pointsAdd to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.