Our FR5 read-only check works on the old laptop and fails before connection on the rebuilt one. Same script. Several SDK copies, no note of which is loaded.
How can I identify the working copy so the next maintainer does not repeat this search?
old laptop works, new one dislikes an argument
VictorChen1142 · 2025年6月1日 14:41 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
6 条回复
What file path does the imported module report on the working laptop? Start with the copy Python actually loaded.
25分回复 MayaChen1171
It loads from the application's local SDK folder. The rebuilt laptop loads from its installed package directory. We were comparing the wrong folders by hand.
13分Now compare the documented arguments for that call in those two versions. Don't edit the controller to fix a local argument error.
10分Can you include the interpreter and normal launch shortcut in the notes as well, so the working copy can be found from the operator's usual login?
15分And get support to confirm the version you intend to keep. Working once and being the agreed setup aren't necessarily the same thing.
15分回复 MayaChen1171
The signatures differ. Support confirmed which release belongs with our setup, and we are restoring that documented environment. Shortcut and interpreter paths are in the handover now; final read-only check still pending.
11分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .