inav VS cleanflight

https://github.com/iNavFlight/inav/blob/master/docs/Failsafe.md Looks like something wrong with your failsafes

iNav is not hours of setup. Heck, if you are experienced with BF then it's barely an hour. Look at this guide. It is not 300 pages long. Basic setup you only need to do once (always save your CLI DIFF after setup in case you need to go back). One flight to run autotune. Then you are done.

https://github.com/iNavFlight/inav/wiki/Supported-boards (I feel like iNav can be installed on a lot more than those 5 mentioned on this page)

Take a look at the stick commands chart half way down this page.

Wheni first stumbled across https://github.com/jopohl/urh (universal radio hacker) i couldn’t believe my luck.

I’ve done stuff like this manually before (as in just collecting all the bits and then trying to ascribe meaning, e.g. https://github.com/cleanflight/cleanflight/issues/1125#issue... ) but i used URH to reverse my bbq temperature sensors.

I have an alexa skill that shows the last 20 readings for both probes on a graph. It is stupidly over the top (a Pi with a cheap sdr dongle listens for packets from the bbq down the garden, it parses out the measurements and fires them into a dynamodb which is absurd but it was quick to do, then the Alexa skill just pulls from there and sends to a chart api that draws my line graphs to show on alex’s screen - totally absurd but great fun to do)

This? https://github.com/cleanflight/cleanflight/releases/tag/v1.1.0

This made it really easy to figure out how to interpret the packets from my wireless barbeque thermometer. Previously i used some monstrous excel for this kind of pattern finding, e.g. https://github.com/cleanflight/cleanflight/issues/1125#issue...

In the end the bbq temp sensor turned out to be trivial, using rtl433 on a raspberry pi I just log the packets to a dynamo table and alexa (using google charts from a lambda) plots the last 20 points on screen.