Workshop laptop sometimes pings FR5, documented read times out. Another laptop worked. What should we compare before changing controller settings?
Confirm the intended target and actual read on both laptops. Ping isn't that check.
8分简体中文界面。帖子、指南及政策正文保留原文；未对原文作自动翻译。
Which target does our failing FR5 read actually contact?
GraceAbbott0059 · 2026年6月29日 20:06 UTC
19 条回复
Was the other laptop's success recorded with the controller identity, Grace? I've seen a saved screenshot become evidence that everything matched when nobody had kept the launch settings beside it.
9分Record the selected destination from the running program, not only the address in someone's setup note. Those can differ without anyone deliberately changing the script.
8分Reece, do shortcuts commonly select different files, even with the same script?
7分They can. Compare the actual working directory and loaded configuration rather than assuming the nearby file is the one used
23分Pavel, saved output identifies our controller. Reece and Lin, actual launch settings weren't recorded on either laptop.
8分Then preserve the current failing setup before the paired comparison. The working result is useful evidence of one success, but it does not yet establish that the endpoint, route or software environment matches now.
14分Who owns that comparison, Grace? Controller owner for intended target, network owner for permitted route and service, maintainer for the saved launch. Keep their answers together.
8分Our maintainer is coordinating all three. The failing shortcut loads a personal training profile, not the documented cell profile.
-1分Does that profile actually name a different destination? I'd write down the loaded values before calling the profile the cause. A wrong-looking file name can still contain the right address, which would leave the timeout unexplained.
14分回复 Olivia_Carr
Different destination confirmed. Network owner verified the intended cell route; maintainer is correcting the profile selection, not changing controller settings.
20分回复 LinChan1053
That answers my shortcut question too, thank you Lin. The values mattered, not the file's reassuring name.
19分Has the intended read succeeded after that correction, Grace? I would keep target mismatch found and service check passed as two results until the second actually happens.
17分And repeat from the ordinary shortcut, not only the maintainer's terminal.
2分Sarah's launch point belongs in the rebuild instructions too. If the fix depends on knowing which menu choice not to use, the next shift may reproduce the failure quite faithfully.
12分Normal shortcut now returns the intended FR5 identity. Reopening also passes. Both sessions retain target, route and SDK details.
10分Keep the old profile identified as training-only or remove it from the operational choices under your configuration process. It remains useful evidence of the fault, not a second equally valid launch option.
5分回复 Marcus_Bowen
Operational shortcut fixed and training profile separated. Maintainer updated the rebuild note. This timeout is closed without a controller change.
-1分Give the covering maintainer that note too. The paired evidence is more useful now than the earlier claim that another laptop worked.
17分