Our rebuilt training laptop rejects an argument before the FR5 status request leaves it, while the old laptop runs the unchanged script; with three SDK folders and no import note, how do I find which environment we are actually comparing?
We had a spare library folder that nobody thought was used until the import path showed otherwise. Ask the maintainer to capture the interpreter, imported module path and version on both laptops, using the same launch method as the failing script.
Maintainer found the rebuilt laptop imports from a user folder, while the old one uses the project environment; the folder labelled current is used by neither.
Compare the installed method signatures and their matching documentation next. Don't remove the rejected argument just to get past the exception; it may have meant something the selected version handles differently.
Has the maintainer identified a supported script and SDK pairing now? Keep the working laptop intact until the rebuilt setup passes the documented read-only check.
Also make the launch environment explicit in the handover, because a terminal test passing won't help if the desktop shortcut still imports that user copy
The supported pairing is identified and being installed in a dedicated environment, with the shortcut changed too, Amy; we have not altered the controller.
The documented status check now passes from the shortcut on the rebuilt laptop, and the handover records the imported path and version; thank you Alex for getting us to look at the actual import.