Our rebuilt laptop rejects a status-call argument before contacting the FR5. Same script as the old laptop, allegedly the same setup. There are three SDK folders and the rebuild note helpfully says use the SDK.
I don't want to fix this by trying folders until one stops complaining. The old laptop is still available and runs the read-only check through its ordinary shortcut. What should I compare so the next person can reproduce the working setup?
Replying to BethBarnes0585
Compare what those actual shortcuts launch: Python executable, working directory, imported module path and the method signature from that loaded copy. Record the script and package versions beside them. Don't edit the argument just to please the rebuilt machine until you know which interface it has loaded; that can hide the mismatch and leave the original handover just as useless.
15 points