our FR5 status timeout lacks a useful laptop comparison

AaronChan1045 · 12 Nov 2025, 21:15 UTC

Closed
AA
AaronChan1045
Our FR5 diagnostic read times out on the workshop laptop, while another laptop reportedly worked; I want to repeat the same documented read on both and capture the endpoint, selected route and service result before anyone changes controller settings to fit an incomplete story.

3 replies

GR
GraceBennett0755
Replying to AaronChan1045

Capture the effective destination from the application on each machine, not only its settings file, and keep the interpreter and SDK versions with the results. Then compare the selected network paths without treating ping as a service test.

7 points
AA
AaronChan1045
Replying to GraceBennett0755

Both applications target the same recorded endpoint, but the failing laptop selects a different adapter; IT is checking that route and the permitted service access, with the SDK versions retained for comparison and no controller change made.

12 points
GR
GraceBennett0755
Replying to AaronChan1045

Has the read succeeded after an authorised network correction, or is the adapter difference still a finding under investigation? That result will tell you whether there is another problem to pursue.

4 points

Discussion closed

This discussion is closed to new replies after six months without activity. Last activity: .