Show HN: µFSM – A state chart library for embedded applications
11–20 of 35 posts
Re: Show HN: µFSM – A state chart library for embedded applications
#12Very nice! Anything that allows something more sophisticated than switch:case in embedded systems are welcome! Also, state machines are way too often overlooked as a proper model for embedded systems architecture. My guess is that proper implementation may become hard (specially if you want to nest them), and there are lots of hardware engineers doing firmware. In my case, when I want to use a state machine for a pro…
Re: Show HN: µFSM – A state chart library for embedded applications
#13Thanks for sharing! I'm working on a device and I've been searching for a good FSM library in C with no dynamic allocation :)
Re: Show HN: µFSM – A state chart library for embedded applications
#14Re: Show HN: µFSM – A state chart library for embedded applications
#15Very nice! Anything that allows something more sophisticated than switch:case in embedded systems are welcome! Also, state machines are way too often overlooked as a proper model for embedded systems architecture. My guess is that proper implementation may become hard (specially if you want to nest them), and there are lots of hardware engineers doing firmware. In my case, when I want to use a state machine for a pro…
They’re particularly ideal for embedded systems. The limited ram in many embedded systems makes a full dynamic language difficult to fit but a state chart interpreter can be very minimal while production runs can be compiled directly to code. Memory management in state charts can often be much easier to handle.
There’s also a lot of benefit to describing valid states for your system both in terms of correctness and the ability of algorithmically finding an optimal reduced state machine.
Personally I am fond of SCXML as it’s fairly concise, can include code snippets, and has a relatively well documented standard easy to display by converting to Vue/React/WebComponents. XMI with its connection to UML didn’t seem appealing to me, but this project seems pretty robust!
Re: Show HN: µFSM – A state chart library for embedded applications
#16Very nice! Anything that allows something more sophisticated than switch:case in embedded systems are welcome! Also, state machines are way too often overlooked as a proper model for embedded systems architecture. My guess is that proper implementation may become hard (specially if you want to nest them), and there are lots of hardware engineers doing firmware. In my case, when I want to use a state machine for a pro…
I second the use of statemachine for embedded systems. They’re particularly ideal for embedded systems. The limited ram in many embedded systems makes a full dynamic language difficult to fit but a state chart interpreter can be very minimal while production runs can be compiled directly to code. Memory management in state charts can often be much easier to handle. There’s also a lot of benefit to describing valid st…
Re: Show HN: µFSM – A state chart library for embedded applications
#17Re: Show HN: µFSM – A state chart library for embedded applications
#18What do you recommend as editor? Does Papyrus work?
Re: Show HN: µFSM – A state chart library for embedded applications
#19It requires a paid tool (Staruml) to extract a fsm from a state chart? Regardless, this looks very cool I will dive in later.
Re: Show HN: µFSM – A state chart library for embedded applications
#20Very nice! Anything that allows something more sophisticated than switch:case in embedded systems are welcome! Also, state machines are way too often overlooked as a proper model for embedded systems architecture. My guess is that proper implementation may become hard (specially if you want to nest them), and there are lots of hardware engineers doing firmware. In my case, when I want to use a state machine for a pro…
I went to the Quantum Leaps site to check out their run-to-completion scheduler(s), one of the rare RTOS alternatives out there. They seem to have an incredible vision, yet, unfortunately, the site and the books make you want to stop reading and go alone.
At the time, I actually bought the book and I liked it. It was a bit dense in the beginning, and I skipped the example, but I had some good takeaways, specially on the implementation of the system, which is described in the book.