Our old laptop runs the read-only controller status collection script for Fairino FR5, 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 maintenance bench with controller access, using an inspection fixture as a reference.
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.
@HanaBrooks0796 Preserve your working copy and compare the two function signatures. Recreating it in an isolated environment should answer the laptop part of the problem.
@IsabelChen1170 I've found a signature difference exactly where the argument is rejected. Both SDK copies are preserved, and our working laptop is still untouched.
@FarahBrooks0852 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.
@CarlaChan1097 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.
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.
You can compare checksums to establish that copies match. Just don't let that stand in for knowing the publisher, release or supported controller pairing.
There's no history with that folder, and I can't tell whether it's been edited. I've left the source as unknown rather than attaching a likely-looking release number.
@HanaBrooks0796 Send support the known identifiers, signature difference and sanitized traceback. Say the vendor copy is untraced; don't present it as a known release.