Separating reachability from the controller service (Fairino FR5, diagnostic status collection)

MiaCarter0992 · 8 May 2026, 00:15 UTC

Reply to discussion
MI
MiaCarter0992
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.

5 replies

JO
JoAli0244
Replying to MiaCarter0992

What endpoint does the installation record specify, and which local route selects it on each laptop? Redact unrelated addresses when sharing

12 points
MI
MiaCarter0992
Replying to JoAli0244

@JoAli0244 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.

18 points
JO
JoAli0244
Replying to MiaCarter0992

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

13 points
MI
MiaCarter0992
Replying to JoAli0244

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.

7 points
JO
JoAli0244
Replying to MiaCarter0992

That keeps the route finding and the final connection result in proportion. The repeat check is a clear condition for closing the fault

9 points

Add to the discussion

Welcome to Application Robot

Everyone can read the forum. Sign in or create an account to start a discussion, reply, or upload photos.

Forgot your password?

By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.