Michal
/
Prusa-Firmware-MMU
mirror of https://github.com/prusa3d/Prusa-Firmware-MMU
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity
Prusa-Firmware-MMU/tests/unit/logic
History
D.R.racer 6dd5057b67 Separate NoCommand and StartUp (new state machine) 
The reasons for this change are:
- NoCommand is used during the lifetime of the firmware as a fallback in case an unknown command is received (simplifies command handling code). It must remain not doing anything.
- StartUp became a complex infrastructure which needs to "live" until an error is fixed (if any). That requires a "standard" StateInner() function which waits for the user to resolve the error.

Unit tests renamed as well.
 		2022-12-20 15:53:05 +01:00
..
cut_filament Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
eject_filament Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
failing_tmc Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
feed_to_bondtech Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
feed_to_finda Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
helpers Improve logging in unit tests' helpers.ipp 2022-12-20 10:35:59 +01:00
homing Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
load_filament Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
start_up Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
stubs Distinguish among different error states when recovering ToolChange 2022-11-18 22:42:05 +01:00
tool_change Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
unload_filament Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
unload_to_finda Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00
CMakeLists.txt Separate NoCommand and StartUp (new state machine) 2022-12-20 15:53:05 +01:00