简体中文界面。帖子、指南及政策正文保留原文;未对原文作自动翻译。

old laptop works, new one dislikes an argument

VictorChen1142 · 2025年6月1日 14:41 UTC

已关闭
VI
VictorChen1142
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?

6 条回复

MA
MayaChen1171

What file path does the imported module report on the working laptop? Start with the copy Python actually loaded.

25
VI
VictorChen1142

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
MA
MayaChen1171

Now compare the documented arguments for that call in those two versions. Don't edit the controller to fix a local argument error.

10
RA
RaviBarnes0563

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
MA
MayaChen1171

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
VI
VictorChen1142

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

讨论已关闭

此讨论已连续六个月没有活动,现已关闭新回复。 最后活动: .