As I am still waiting for my parts to build my first quad I want to get your input on what you think would be the perfect Flightcontroller?

My suggestion would be that everybody tells me their favorite FC and what they would add/remove from it

Examples:
- Bigger solder pads
- Add onboard OSD
- Switch PINs XXX from the Left side to the right side
- PIN Compability with a fitting PDB
- Put some Flame stickers on it to make it go faster

I am really interested in your Input.

The reason for these questions is that I am thinking about designing my own Flight Controller board. But it's just a thought so far, but yes i can actually design something like this and have contacts for PCB manufacturing.

EDIT: Please only features for a Mini FPV Racequad!

Whats going on here man..! I thought there would be some response to this topic by now!?

I was thinking mainly of orientation of pads/plugs/sockets on the board. Pads for ESC's/motors at the corners to keep those 'noisy' wires clear of VTX cables. Pads for RX at the rear and FPV rig at the front. LED's and buzzer pads on one side, micro USB and boot pins (all easily accessible) on the other.

I was thinking of OSD... As I understand it, OSD adds a fraction of lag to FPV feed(?) but it's so useful as to make most people use it despite this, I thought if OSD could be actvated and de-activated via a switch on the TX this would allow pilots to check OSD info, only at optimum times and otherwise alleviate the lag?

All this thought of VTX interference and on board OSD led me to think of an onboard VTX, maybe even power switchable from the TX? With an on-board VTX and onboard RX, the aerials could possibly be placed at an optimum distance from each other to minimize interference?

As all the drone racing here goes on at least 100km from where I live, I don't know what the deal is with race control software but maybe an on-board RFID tag?
Apicalis, with your racing contacts maybe you know of some way to revolutionize timekeeping for Drone Racing!?

I started Hijacking your thread with my idea for a race control app but thought I would start a new thread...

point 1 and 2 are kind of contradictory when you have so much stuff on the board it's hard to have large solder pads.
For FC that has OSD features, i would recommend the OMNIBUS and Betaflight F3.. They have lots of features, but the pin layout is a mess... not user friendly at all...

For FC that has large pads to work with, maybe the LUX V2? great pin layout! But maybe too simple for some people that want more features.

I've been thinking about this...

I think focusing on the PDB as well as the FC might yield some worthwhile advancements. I'm not fond of AIO solutions that put too much on the FC. On the other hand, putting more on the PDB and streamlining connections between the two might be good. (I'm also a bit leary of 4-in-1 ESCs although I have a couple installed.)

I really like the QuadRevo OSD Pro and the DemonCore PDBs, but it would be nice to not have wires soldered from one component to both PDB and FC (like we do with ESCs). So here is my suggestion.

Create a PDB with 5V/12V filtered regulators (for Cam/VTx and power to FC), and built in OSD (like QuadRevo). In addition to pads for ESC power, add pads for ESC signal. Bring socket/pigtail from PDB containing 5V, Gnd, M1-M4 signal, Rx&Tx (for OSD). Then the FC only has UARTs, Radio Rx, maybe buzzer, maybe LED (or maybe put those on PDB). Upgrading the FC could be a lot easier.

Just thoughts...

- USB on VCP, not UART1
I would say the perfect one would be the BFF3 with F4 or F7