Show HN: I made an app for designing Embedded Systems and code generation
fsmpro.io
fsmpro.io
They used State Machine design regressively for business logic implementation across all their products. Embedded system code is meant for deploying on Microcontrollers and usually written in a low level language like C. The dependency on state machine was excessive to a point that they made a tool for designing state machines which perfectly made business sense.
As a engineer, I liked the uselfulness and lightweight nature of the tool but it crashed often and was not maintained. After sometime they discontiued the tool and purchased Enterprise Architect which helps in designing state machines but originally meant for doing other things. Unlike the previous tool, the code generated by Enterprise Architect was not clean enough and not used.
I researched and picked up the core idea of the tool created a better version of it with FsmPro. I made sure it is cross-platform so that it could reach most users. It is available as a free download and comes with all the features to support development and codification of state machines.
Please try and let me know what you think.
QM again does a host of other things apart from state machine design. You have to work with their framework to get the work done and also getting the license is expensive.
You can design however you want in FsmPro. There is no model to adhere to. You can design state machines, talk to other state machines and just inlcude them in your projects with a single header file inclusion.
I make my argument clear in this piece: https://medium.com/@FsmPro/introducing-fsmpro-a-tool-built-w...:
A few points: The post title should mention finite state machines, I think.
In the page you say « FsmPro is xml based which reduces the possiblity of data loss »: How and compared to what?
Losing work is expensive.
A project file could get corrupted for a myriad of reasons. If the format of the file is proprietary or could not be deciphered easily, you would lose your data. This is a very common problem with Microsoft and Adobe files to name a few.
Having a standard xml format makes it easy to repair had the file get corrupted by accident. Also, it makes it easier for anyone to run scripts to get the data out of the files. Ex: Custom code generate with a script that scrapes the xml file.
On installing the tool, you would have an example project open by itself which should help. There are multiple examples in the installation directory of your computer. I hope I answered your query.