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.
our FR5 status timeout lacks a useful laptop comparison
AaronChan1045 · 2025年11月12日 21:15 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
3 条回复
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分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分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分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .