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 · 2026年4月14日 02:05 UTC
主帖中文翻译暂不可用，以下显示英文原文；回复保留原文。 查看英文原文
9 条回复
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.
4分Different paths. Our vendor folder on the old laptop, an installed package on the rebuild. I'd compared everything except the imports, apparently.
20分Preserve your working copy and compare the two function signatures. Recreating it in an isolated environment should answer the laptop part of the problem.
16分@HenryBrown0873 Does recreating that copy really settle the laptop side? It could fix the signature mismatch while leaving a different launcher or dependency problem.
6分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.
13分@HenryBrown0873 Found it: the rejected argument has a different signature. Both copies are intact, and our working laptop is untouched.
25分@JackBennett0776 My first instinct would've been to change that argument. Why not just match the installed package's signature?
3分@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.
6分@HenryBrown0873 My terminal and shortcut used different environments. I celebrated fixing the terminal. The shortcut wasn't impressed.
4分讨论已关闭
此讨论已连续六个月没有活动，现已关闭新回复。 最后活动： .