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.
our FR5 status timeout lacks a useful laptop comparison
AaronChan1045 · 12 Nov 2025, 21:15 UTC
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
Discussion closed
This discussion is closed to new replies after six months without activity. Last activity: .