old laptop works, new one dislikes an argument

VictorChen1142 · 1 Jun 2025, 14:41 UTC

Closed
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 replies

MA
MayaChen1171
Replying to VictorChen1142

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

25 points
VI
VictorChen1142
Replying to 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 points
MA
MayaChen1171
Replying to VictorChen1142

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

10 points
RA
RaviBarnes0563
Replying to VictorChen1142

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 points
MA
MayaChen1171
Replying to VictorChen1142

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 points
VI
VictorChen1142
Replying to 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 points

Discussion closed

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