That’s good to hear! I only ask as we’ve been having a lot of trouble recently regarding some of the mavros implementation and timing issues (whether it’s px4 side or mavros side we are unsure of).
Would you see it better to target smaller scale projects? Or another way of putting it… Would it be easier and more reliable to implement a similar system to the px4 flight stack based targeting a single type of drone? Rather than have to aim for support across the multi-fixedwing-vtol codebase the px4 stack is currently aiming to achieve?
There are benefits to the unified codebase approach, but it seems like there is a lot of openings for potential issues.
Also (unless I missed it in the previously linked post) how do you plan on working around missing features in the flight stack? I am under the impression you will build directly off of the px4 source, so would you be planning on implementing all features as requested, and leaving any firmware incompleteness to on that side? Or would it be more aimed at supporting the currently available features, and keeping up to date with what is achievable with the firmware?