Closed onlykelvin closed 1 year ago
This article and the Wiki article in the Boards documentation section cover which MCUs and specifically which targets are available. https://github.com/iNavFlight/inav/wiki/Boards,-Targets-and-PWM-allocations Specifically covers the Signal outputs. Having 4 motors available is all that’s really required for it to be a “quad” flight controller.
BetaFlight targets, even the names, are not the same as INAV targets. Check the manufacturer’s web site for the INAV target name.
Supported FC for drones
I have found the boards list of what flight controllers are supported but it gives mixed signals.
Making it easier to comprehend what is supported for drones
Maybe I am still too new and just impotent regarding this firmware, but no matter how much I google I can't find any website for simple how-to. (as far as 'simple' can qualify for firm/software like INAV)
Suggested Solution
Who does this impact? Who is this for?
Everyone that flies FPV drones to make a migration, or just pure curiosity for what INAV is all about. Made easy.
Additional context with example
A simple example: The baby ape pro v2 has a STM32f411 FC MCU, it has the target MATEK F411 (it is noted by DarwinFPV that it's the target for Betaflight, to be fair). If I look at the supported boards list on it has the MATEK F411, and it does have this target in the INAV configurator, but it show a completely other FC when I click on full specifications than the baby ape pro v2 has. This is really confusing. Maybe it is because INAV is more limited regarding flashable FC's than Betaflight or me wanting something to be possible when it's not.
PS. I am not sure if this post is relevant here, but I will give it a shot since most whom will deal with this same issue I am dealing with right now will be looking at the INAV GitHub and wiki.
Hence I am placing this here. Otherwise I apologize.