Demo Mode: Difference between revisions
(Created page with "<i>Are you using Robopad with a large group of people who've never come across it before?<br> Want to make sure that they can have fun with the circuit but not accidentally ch...") |
m (Updates the demo URL to be the full IP address) |
||
| Line 2: | Line 2: | ||
Want to make sure that they can have fun with the circuit but not accidentally change the wifi settings so that it's locked out of use?</i> | Want to make sure that they can have fun with the circuit but not accidentally change the wifi settings so that it's locked out of use?</i> | ||
RoboPad has a simple solution to these situations: <strong>Demo mode</strong> - once connected to the RoboPad simply navigate to <strong> | RoboPad has a simple solution to these situations: <strong>Demo mode</strong> - once connected to the RoboPad simply navigate to <strong>192.168.4.1/demo</strong> and press the button to enable demo mode. This will disable all hardware configuration settings in the RoboPad's hardware configuration manager but still allow for NodeGraph changes (often very important if you're building robots rapidly, as it lets users do things like invert drive controls and swap connections which will let them account for ambiguously-wired drive motors). | ||
<strong>Note</strong> that this is not a bullet-proof defence against unwanted tinkering. Anybody with a connection to the RoboPad can also go to the <strong>/demo</strong> page and simply disable the mode - on top of that, while the mode hides the <i>user interface</i> to update the RoboPad's settings, it does not stop the <i>core functionality</i>. Users could still circumvent the mode by manually configuring POST requests to the device or simply editing the HTML served to them client-side on the management page to re-enable the management buttons. However, demo mode <i>is</i> effective at stopping new users from innocently changing device settings by accident, and may deter any would-be troublemakers in your group. | <strong>Note</strong> that this is not a bullet-proof defence against unwanted tinkering. Anybody with a connection to the RoboPad can also go to the <strong>/demo</strong> page and simply disable the mode - on top of that, while the mode hides the <i>user interface</i> to update the RoboPad's settings, it does not stop the <i>core functionality</i>. Users could still circumvent the mode by manually configuring POST requests to the device or simply editing the HTML served to them client-side on the management page to re-enable the management buttons. However, demo mode <i>is</i> effective at stopping new users from innocently changing device settings by accident, and may deter any would-be troublemakers in your group. | ||
If someone does manage to change a setting that you wanted to keep control over, you may have to resort to putting the RoboPad into [https://wiki.robopad.co.uk/index.php/Safeboot Safeboot mode]. | If someone does manage to change a setting that you wanted to keep control over, you may have to resort to putting the RoboPad into [https://wiki.robopad.co.uk/index.php/Safeboot Safeboot mode]. | ||
Latest revision as of 14:05, 9 May 2024
Are you using Robopad with a large group of people who've never come across it before?
Want to make sure that they can have fun with the circuit but not accidentally change the wifi settings so that it's locked out of use?
RoboPad has a simple solution to these situations: Demo mode - once connected to the RoboPad simply navigate to 192.168.4.1/demo and press the button to enable demo mode. This will disable all hardware configuration settings in the RoboPad's hardware configuration manager but still allow for NodeGraph changes (often very important if you're building robots rapidly, as it lets users do things like invert drive controls and swap connections which will let them account for ambiguously-wired drive motors).
Note that this is not a bullet-proof defence against unwanted tinkering. Anybody with a connection to the RoboPad can also go to the /demo page and simply disable the mode - on top of that, while the mode hides the user interface to update the RoboPad's settings, it does not stop the core functionality. Users could still circumvent the mode by manually configuring POST requests to the device or simply editing the HTML served to them client-side on the management page to re-enable the management buttons. However, demo mode is effective at stopping new users from innocently changing device settings by accident, and may deter any would-be troublemakers in your group.
If someone does manage to change a setting that you wanted to keep control over, you may have to resort to putting the RoboPad into Safeboot mode.