Hi,
Does anyone here know if F.Port (FrSky) is supported/developed on the Holybro Pixhawk 4 FMUv5 F7?
Thx,
Yuri
Hi
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/rc
Then 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.
1 Like
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: PX4 Architectural Overview · PX4 Developer Guide
Has the status of F-Port support changed? It would be nice to have one less cable to worry about 
1 Like
I’m also looking forward to this!
IO failsafe is a very rare situation, I think support f.port first on a uart on FMU is enough for most of users.
Resurrecting this thread. Has the status of this changed?
Do we have any news on this topic? For Arducopter it´s working for quite a while 
1 Like
Hi, I wanted to extend PX4 support for this protocol. But I came across an error that I was not able to connect the receiver to the FMU. More information about this issue is here:
Would also love to see support for F.Port! 
yep, F.PORT would be awesome since it supports bidirectional communication (telemetry feedback as well)