GraceAbbott0059 · 29 Jun 2026, 20:06 UTC
Confirm the intended target and actual read on both laptops. Ping isn't that check.
8 pointsWas 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 pointsRecord 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 pointsReece, do shortcuts commonly select different files, even with the same script?
7 pointsThey can. Compare the actual working directory and loaded configuration rather than assuming the nearby file is the one used
23 pointsPavel, saved output identifies our controller. Reece and Lin, actual launch settings weren't recorded on either laptop.
8 pointsThen 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 pointsWho 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 pointsOur maintainer is coordinating all three. The failing shortcut loads a personal training profile, not the documented cell profile.
-1 pointsDoes 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 pointsDifferent destination confirmed. Network owner verified the intended cell route; maintainer is correcting the profile selection, not changing controller settings.
20 pointsThat answers my shortcut question too, thank you Lin. The values mattered, not the file's reassuring name.
19 pointsHas 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 pointsAnd repeat from the ordinary shortcut, not only the maintainer's terminal.
2 pointsSarah'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 pointsNormal shortcut now returns the intended FR5 identity. Reopening also passes. Both sessions retain target, route and SDK details.
10 pointsKeep 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 pointsOperational shortcut fixed and training profile separated. Maintainer updated the rebuild note. This timeout is closed without a controller change.
-1 pointsGive the covering maintainer that note too. The paired evidence is more useful now than the earlier claim that another laptop worked.
17 pointsBy creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.