I rebuilt our laptop, and the read-only script for controller identity recording on Fairino FR5 now rejects an argument before contacting the controller.
The old laptop still runs the same script.
I've found several SDK folders, but no record of which copy it uses.
Our setup is in a maintenance bench with controller access, with a fixture plate as the reference item.
Which SDK folder is my script actually using? (Fairino FR5)
JackBennett0776 · 14 Apr 2026, 02:05 UTC
9 replies
Replying to JackBennett0776
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.
4pointsReplying to HenryBrown0873
Different paths. Our vendor folder on the old laptop, an installed package on the rebuild. I'd compared everything except the imports, apparently.
20pointsReplying to JackBennett0776
Preserve your working copy and compare the two function signatures. Recreating it in an isolated environment should answer the laptop part of the problem.
16pointsReplying to HenryBrown0873
@HenryBrown0873 Does recreating that copy really settle the laptop side? It could fix the signature mismatch while leaving a different launcher or dependency problem.
6pointsReplying to PriyaBrown0916
You're right about my wording. Matching the SDK starts the comparison; it doesn't finish it. Include the interpreter, dependencies and launcher, then compare the documented read-only result.
13pointsReplying to HenryBrown0873
@HenryBrown0873 Found it: the rejected argument has a different signature. Both copies are intact, and our working laptop is untouched.
25pointsReplying to JackBennett0776
@JackBennett0776 My first instinct would've been to change that argument. Why not just match the installed package's signature?
3pointsReplying to LiamCarter1012
@LiamCarter1012 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.
6pointsReplying to HenryBrown0873
@HenryBrown0873 My terminal and shortcut used different environments. I celebrated fixing the terminal. The shortcut wasn't impressed.
4pointsDiscussion closed
This discussion is closed to new replies after six months without activity. Last activity: .