简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

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

MiaCarter0992 · 2026年5月8日 00:15 UTC

回复讨论
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 条回复

JO
JoAli0244

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

12
MI
MiaCarter0992
回复 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
JO
JoAli0244

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
MI
MiaCarter0992
回复 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
JO
JoAli0244

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

9

参与讨论

欢迎来到 Application Robot

所有人都可以阅读论坛。登录或注册后即可发起讨论、回复或上传照片。

忘记密码?

注册账号即表示你同意我们的 使用条款 社区准则。请阅读我们的 隐私政策 ,了解我们如何处理你的信息。