embedded-systems
Designing a finite state machine with states, events and transitions, and coding it table-driven
taught
Taught in
-
Finite state machines
Embedded Systems and the Internet of Things
Requires
- software-debouncing required
Required by
- Building a room controller around a table-driven state machine with persistent modes required
- Naming the ways a device's connection fails (access point, DHCP lease, broker restart, weak signal) and how each is noticed required
- Recognizing which embedded-systems skills (non-blocking loops, state machines, NVS, Serial) connected firmware leans on required
- Running several timers and state machines in one loop as a tiny cooperative scheduler required
Local knowledge map
Local knowledge map
Click to expand
Solid arrows are required prerequisites; dashed are recommended or helpful. Lower rows are more foundational. Click any box to jump to that concept.