I'm investigating a read-only diagnostic status collection timeout on our workshop laptop with Fairino FR5 in a workshop commissioning bench, using a fixture plate as a reference. Ping sometimes succeeds. Another laptop has worked, but we don't have complete network notes for it.
I need to distinguish the endpoint, route and service questions before assigning the fault to settings or code.
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.
@PavelArcher0353 Give that route difference to your network owner for a targeted correction. Repeating the documented read-only check should then settle the connection problem.
I've narrowed our connection investigation to a concrete route difference for the recorded endpoint. I'll close the fault only when the network owner's correction passes the documented read-only check in normal use.