Mark van Renswoude
5d013b4273
Refactored settings and global state to reduce overhead Consolidated configuration into class constants (I really didn't like all the shouting in the code :-))
21 lines
836 B
Markdown
21 lines
836 B
Markdown
# Testscript
|
|
As I really do not want to explain to my employer how I broke my desk, this document describes the intended behaviour of the software in various scenarios, focusing on the safety guards.
|
|
|
|
## Startup
|
|
|
|
1. Height sensor must report at least 3 values within 5mm of each other in 500 ms intervals to be considered stable.
|
|
1. If the EEPROM has not been initialized yet, the height offset setup screen must be displayed.
|
|
1. Otherwise, the home screen must be displayed.
|
|
|
|
|
|
## Home
|
|
|
|
|
|
## Moving
|
|
|
|
1. If the height sensor does not report a valid value for 100ms the move must be aborted and the move error screen shown.
|
|
|
|
### Move error screen
|
|
|
|
1. This screen can only be closed if the height sensor is considered stable, as described in the startup sequence.
|
|
1. Pressing any button will close this screen and return to the Home screen. |