Separating reachability from the controller service (controller identity retrieval)

The recorded endpoint agrees with our script. My failing laptop selects another active adapter; the working one selects the workshop interface.

Give that route difference to your network owner for a targeted correction. Repeating the documented read-only check should then settle the connection problem.

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

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.

Would a successful ping help at all, then? I've got a folder of ping screenshots feeling increasingly decorative.

@TobyBell0666 Limited reachability evidence. Ping doesn't exercise the documented SDK service, and a missing reply doesn't by itself prove the controller is offline.

My own diagnostic laptop changed its selected route when its active network connections changed between office and workshop use, even though the application endpoint stayed the same.

@AmaraBrooks0861 I'll retain the relevant adapter state alongside our selected-route information, making sure it describes the same laptop session in which the check fails.

@TobyBell0666 Would a check with only the workshop connection establish the required fix, or does the normal multiple-connection setup still need review?

Follow the documented connection setup with the network owner. Even a successful single-connection check wouldn't establish how the laptop should be configured during its normal combined use.

@LuisAli0260 And don't change the robot's address just to fit the laptop's route. You've identified a laptop difference, not an incorrect controller endpoint

Agreed. I've sent the route comparison to our network owner. The endpoint matches our installation record, so that's the reference I'm using.

@LuisAli0260 If the read-only request returns a service error after connection, what does that establish compared with a failure to connect?

@MeiAdams0168 It can establish that connection succeeded and an application response arrived. Then interpret that response using the matching SDK documentation, without calling the whole check successful.

On my installation, ping and the documented service were handled by different filtering rules. The network owner's logs established why ping replies coexisted with service failures.

@AmaraBrooks0861 If the route investigation leaves the service unavailable, I'll ask about filtering. I haven't established that your separate filtering example applies to our installation.

I still don't have a verified read-only connection from our diagnostic laptop. The route difference is a useful lead, but not a confirmed fix.

@TobyBell0666 That status fits the missing verification: an identified difference, with the actual connection result still unresolved.