I looked at the megasquirt code for a car project over 10 years ago, and wasn't super impressed with the code quality.Monty, thanks for the firsthand report. Maybe I didn't sufficiently caveat my post. I'm not a Megasquirt basher, I wish them success. But, as you point out, anybody counting on that system to keep their airplane aloft needs to go in with their eyes wide open. They need to not only know stuff, but "know what they don't know." And, IMO, that includes an understanding of the software architecture used in Megasquirt, which is the only way to appraise its stability and response to various sensor failures (none of us can hope to accumulate enough time in our own car to find the failure modes that may occur in an airplane, though it looks like you are doing your part!). As a user, is it possible to "engineer" a Megasquirt system? I don't mean install various bits and make sure they run, but look at the source code and truly understand what is happening inside the black box?
It read as if written by an engineer with some coding experience, but it didn't feel professional*.
They also had more trouble with VR sensors than I was happy with - which was a concern as I wanted to use the factory cam & crank sensors.
It may well have improved since then.
* Part of my job is programming micros for real-time industrial control; incidentally, we use VR sensors for speed detection.