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?
FR5 status shortcut loading an unrecorded SDK copy
BethBarnes0585 · 8 May 2026, 18:33 UTC
1 reply
Add to the discussion
Welcome to Application Robot
By creating an account, you agree to our Terms and Conditions and community guidelines. Read our Privacy Policy for how your information is handled.