Update README.md
added disclaimer bit
This commit is contained in:
parent
3e7e50c307
commit
74a2936c1c
@ -7,6 +7,7 @@ Add a big ugly emergency stop to your sidebar. It's big, it's yellow, it's red,
|
||||
That's the point of an EMERGENCY stop!
|
||||
|
||||
![](/extras/assets/img/plugins/estop/enabled.PNG) vs ![](/extras/assets/img/plugins/estop/disabled.PNG)
|
||||
|
||||
## Setup
|
||||
|
||||
Install via the bundled [Plugin Manager](https://github.com/foosel/OctoPrint/wiki/Plugin:-Plugin-Manager)
|
||||
@ -28,3 +29,7 @@ Find the "appearance" section, and add the plugin to the top of the sidebar orde
|
||||
- plugin_estop
|
||||
|
||||
Please note: White spaces are critical inside the config.yaml file, special care must be taken when adding or removing entries that the correct layout is maintained. For more information on config.yaml and its appearance section, see here: http://docs.octoprint.org/en/master/configuration/config_yaml.html#appearance
|
||||
|
||||
#### Disclaimer
|
||||
|
||||
This is not a magical button, it can't perform miracles, all it does is send the standard `M112` emergency stop gcode to your printer, how it responds to that is largely up to the firmware. Depending on the control board and firmware, a reset may be required to regain control, or a simple disconnect and reconnect may also work. So called 'blocking' gcodes (such as the heat-and-wait commands) may render this button ineffective (again, largely up to how the firmware handles incoming commands) and so a software solution should never be relied upon to overcome a hardware issue such as a fire or other critical event. There is no substitute for physical human intervention in case of an emergency, and a _pysical_ emergency stop button capable of cutting the incoming power.
|
||||
|
Loading…
Reference in New Issue
Block a user