Does anyone here know if F.Port (FrSky) is supported/developed on the Holybro Pixhawk 4 FMUv5 F7?
It's not in development but would be nice to have.
I'm willing to have a look at it, but I'm new to px4 so would need quite some pointers from experienced devs...
Great!Here some initial pointers:- FrSky telemetry is implemented here: https://github.com/PX4/Firmware/blob/master/src/drivers/telemetry/frsky_telemetry/frsky_telemetry.cpp- RC parsing library is here: https://github.com/PX4/Firmware/tree/master/src/lib/rcThen it gets a bit complicated because of the IO chip: RC goes through the IO e.g. on Pixhawk 4. This is simpler for example on the Pixracer, where RC is directly parsed in the fmu driver: https://github.com/PX4/Firmware/blob/master/src/drivers/px4fmu/fmu.cpp#L1551
I'm not sure if it's worth adding F.Port support for boards with an IO due to the required amount of changes (though we could work around it by using another UART for RC).
Feel free to ask me further questions.
Ok, I only have a pixhawk 4 (holybro) to test on so it would be nice to get it working through io...I hope to find some time next week to look into the rc code.Why does it go through IO? Is there a guide/blog that explains px4 on a medium level?
Because of failsafe: if the main FMU fails, the IO can still operate on its own (though this is only for fixed-wing to fly fully manual).
The best reference is probably this: https://dev.px4.io/en/concept/architecture.html