Our old laptop runs the read-only read-only connection verification script for Fairino FR10, but the rebuilt one rejects an argument without reaching the controller.
The script hasn't changed.
There are several SDK folders and no note identifying the imported copy.
We're in a workshop inspection station, using a sample bracket as a reference.
@TheoAbbott0062 Which module path does the script's own interpreter load on each laptop? I'd start there; the names on the SDK folders don't tell you what's running.
@HenryArcher0351 The paths differ: our vendor folder on the old laptop, an installed package on the rebuilt one. I'd compared the scripts and completely missed what they imported.
Preserve your working copy and compare the two function signatures. Recreating it in an isolated environment should answer the laptop part of the problem.
@AlexBennett0733 It could remove the local error. You'd still need matching SDK documentation and confirmation of the controller pairing; accepting the arguments doesn't establish the rest of the behaviour.
@LiamBaker0490 I've checked the launcher we actually use as well. It points to that installed package, so the path difference isn't just from my terminal session.
Treat them as separate identifiers unless the documentation says otherwise. Look for a stated pairing, or send both identifiers to support for confirmation.
Our maintenance record and the controller version screen agree. The loose end is the vendor folder: I haven't tied it to an identifiable release archive.