nuttx VS PX4-Autopilot

Hi Rust experts, we are willing to integrate rustix on NuttX RTOS, the initial effort was done by rustix author: https://github.com/bytecodealliance/rustix/tree/nuttx but it hit the wall since we don't know the right way to integrate cargo with the old-school NuttX's Makefiles. Any help or suggestion is welcome. More about NuttX here: https://nuttx.apache.org and here: https://nuttx.apache.org/docs/latest/

Open Source Autopilot for Drone Developers PX4 is an advanced and open source autopilot flight stack for drones. PX4 can flight completely autonomously for pre-programmed missions, or, obviously, it can help a pilot who remote-controls the drone. It runs on NuttX RTOS.

You should definitely have a look at NuttX.

https://gitlab.com/nuttx/NuttX/-/tree/master/drivers/sensors https://github.com/apache/incubator-nuttx/pull/2039

Maybe Nuttx can be an alternative. Have a look: https://nuttx.apache.org/

Zephyr, RIOT, NuttX are all open source RTOSes happy about contributions

Microcontrollers are a good start. Boards are cheap and sensors are plentiful. You could get a yet unsupported board and port RIOT, Zephyr or NuttX.

They are widely used in narrow circles :)

Two of (arguably the best) open source RC aircraft flight controllers (ArduPilot and PX4) are using extended Kalman filters in their state estimators (essentially sensor fusion that provides attitude/position estimate):

https://github.com/ArduPilot/ardupilot/tree/master/libraries...

https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/e...

I'm not that familiar with cleanflight/betaflight/inav scene to know what the FPV racer flight controllers use.

Actually, even the General Aviation pilots who actually manually manage their own load-shedding during a mission would quite like automated power distribution and management systems... and if you felt like taking on that sort of work as a hobby project to cut your teeth, I bet the guys at the (open-source) PX4 project would bite your hand off...

As a flight pilot engineer you have to find a sweet spot and balance logging too much and too little. Writing logs to an SD card has huge costs that come with it, that's why you don't want to log too much. Logging too little and you can't debug issues later on properly.

PX4 also has lots of "topics" logged at around 1/10, e.g. hover thrust estimate every 100ms:

https://github.com/PX4/PX4-Autopilot/blob/main/src/modules/l...

Okay, but nowadays most people talk about “Pixhawk” as an open-standard hardware platform and PX4 as the software. The source code is at https://github.com/PX4/PX4-Autopilot and they call themselves “PX4 Autopilot Software”.

As an example, PX4 is a popular open source drone autopilot software: https://github.com/PX4/PX4-Autopilot

I am working as a Remote Embedded Software developer for quite a while now and there is no obstacle in Remote work. If I am missing anything, parts are arriving in under the week. That said, I never had a better work-life balance in the last 10 years. Anyone who said Embedded is not possible to do remotely just check any open source flight controller project (in my case PX4).