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
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
Have the network owner assess and correct the identified route difference, then repeat the documented read-only check. That should settle the connection issue.