Our workshop FR5 status read times out although ping sometimes succeeds, and another laptop has worked without complete network notes; what comparison would separate target, route and service at this sample-housing commissioning bench before we blame settings or code?
I cannot assign the FR5 timeout from intermittent ping alone
HazelBaker0484 · 28 Jul 2026, 16:15 UTC
1 reply
Replying to HazelBaker0484
Capture the exact documented request, target, selected network path and failure time on your laptop, then obtain the same record from a fresh successful session on the other one. Keep SDK identity with it. Ping and remembered success do not establish that the intended service was reached under equivalent conditions.
10pointsAdd to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.