Our workshop laptop sometimes pings Fairino FR10, but the documented read-only check for controller availability checking 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 a fixture plate 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.
A route correction addresses the identified difference but doesn't guarantee service availability. The next check could establish connection and then fail at the application stage.
@CalebBaker0493 Fair. I should've said it tests the routing lead. Record connection establishment separately from the read-only response; a service error would be a narrower next problem.