Betaflight code modification for FPV QUAD Model aircraft

Betaflight and Butterflight Model Aircraft Flight controller firmware code is available on GitHub. I would like the following modifications done to the code with flight controller hardware targets of:

PyrodroneF4 (Betaflight)

OmnibusF4SD (Betaflight)

HelioRCSpring (Butterflight code)

The modifications are:

Flight Path Vector

The flight path vector will show the direction that the vehicle (quad)

is moving as a circle and crosshair symbol.

Examples:

1. When the quad is ascending the FPV will show a vertically displaced circle.

2. When the quad is turning right, the FPV will show a right displaced circle.

3. If the quad is flying level with no climbs, descents or turns, the FPV will be level.

4. If the quad has a left yaw but is flying straight ahead, the FPV will be level, but will be

displaced right in the field of view since first person video quad copters have a FIXED camera

that the pilot is viewing to fly the quad.

Note: Do not confuse First Person Video (FPV) which is the term used to describe using a quad copter, onboard camera and a onboard video transmitter, transmitting video to a display or goggles used by the pilot to fly the craft remotely. This is the intended application for this project.

Flight Path Vector is also abbreviated FPV.

The FPV (flight path vector) requires inputs from the gyros and accelerometers and the code computing the FPV will have to be updated at a fast enough rate to be usable, probably 50-100 HZ, depending on how much CPU load is taken up by the increased code.

This code is assumed to be hardwired into the firmware, however a OSD switch that is unused might be modified to allow turning on and off the FPV, for example, the horizon sidebars are not used and thus might be taken as a available switch.

Additional FPV modifications, like a flight path vector rate (first derivative) might also be needed at a later date. This would show a arrow around the flight path vector circle showing the magnitude of the change of the flight path vector. Additional work following flight tests will probably be needed.

All code, compilers and the procedure for the client to modify and compile code will be delivered.

References:

[login to view URL]

[login to view URL]

[login to view URL]

Ingeniería aeronáutica Desarrollo Desarrollo de software

Nº del proyecto: #16734949

Sobre el proyecto