You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I maintain RLSOK. You can try the local example without a robot, ROS installation or cloud account.
Use an Ubuntu 22.04 or 24.04 x64 computer with curl and tar. Start in a new directory and follow the download page's matching download and checksum commands:
The sample uses deliberate configuration changes. The original should return WOULD_ALLOW; the changed calibration should return WOULD_BLOCK. Open the reports and read the reason. No robot commands are sent.
Updated September 15: if you would rather try a file comparison, there is now a step-by-step Pure Pursuit exercise. It uses the public Pioneer-X source, changes a saved lookahead value from 0.6 to 0.7 and compares it with the same original baseline. You need Linux x64, Python 3 and Git. The guide uses RLSOK Local Check 1.5.0; its example values come from source defaults, not a robot owner's current settings.
That file report uses UNCHANGED, REVIEW_REQUIRED and NEEDS_MATERIAL. Those labels describe saved files, not the sample's Shadow authorization decisions. A matching file report does not prove what is running on a robot or how well it drives.
If you try either path, reply with which one you used and the first result or step that failed. Your OS version and a short error with private details removed are enough. Please do not upload firmware containing WiFi settings or private configuration files.
On Windows or macOS, you can watch the existing offline demonstration on the download page first.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I maintain RLSOK. You can try the local example without a robot, ROS installation or cloud account.
Use an Ubuntu 22.04 or 24.04 x64 computer with curl and tar. Start in a new directory and follow the download page's matching download and checksum commands:
Run the local example
The sample uses deliberate configuration changes. The original should return
WOULD_ALLOW; the changed calibration should returnWOULD_BLOCK. Open the reports and read the reason. No robot commands are sent.Updated September 15: if you would rather try a file comparison, there is now a step-by-step Pure Pursuit exercise. It uses the public Pioneer-X source, changes a saved lookahead value from 0.6 to 0.7 and compares it with the same original baseline. You need Linux x64, Python 3 and Git. The guide uses RLSOK Local Check 1.5.0; its example values come from source defaults, not a robot owner's current settings.
That file report uses
UNCHANGED,REVIEW_REQUIREDandNEEDS_MATERIAL. Those labels describe saved files, not the sample's Shadow authorization decisions. A matching file report does not prove what is running on a robot or how well it drives.If you try either path, reply with which one you used and the first result or step that failed. Your OS version and a short error with private details removed are enough. Please do not upload firmware containing WiFi settings or private configuration files.
On Windows or macOS, you can watch the existing offline demonstration on the download page first.
All reactions