ardupilot/libraries/AP_HAL_F4Light/hardware/osd
2018-02-22 08:10:32 +11:00
..
osd_core HAL_F4Light: new hal for F4 boards, close to bare-metal 2018-02-10 09:14:41 +11:00
osd_eeprom.cpp HAL_F4Light: new hal for F4 boards, close to bare-metal 2018-02-10 09:14:41 +11:00
osd_eeprom.h HAL_F4Light: new hal for F4 boards, close to bare-metal 2018-02-10 09:14:41 +11:00
osd_namespace.h HAL_F4Light: new hal for F4 boards, close to bare-metal 2018-02-10 09:14:41 +11:00
osd.cpp AP_HAL_F4light: fixed compilation for boards AirbotF4, AirbotV2 and CL_Racing_F4. Corrected prefix for binaries 2018-02-22 08:10:32 +11:00
osd.h AP_HAL_F4light: fixed compilation for boards AirbotF4, AirbotV2 and CL_Racing_F4. Corrected prefix for binaries 2018-02-22 08:10:32 +11:00
ReadMe.md HAL_F4Light: new hal for F4 boards, close to bare-metal 2018-02-10 09:14:41 +11:00
rules.mk HAL_F4Light: new hal for F4 boards, close to bare-metal 2018-02-10 09:14:41 +11:00

Support for built-in MAX7456 for FCs. Uses files from MinimOSD-Extra project (https://github.com/night-ghost/minimosd-extra) which used as module in AP_HAL_F4Light/support folder

Because Ardupolot is written on C++ and consists of objects with a hidden internal structure, it is impossible to get the state of the flight controller from OSD driver. Therefore, the OSD works completely independently in its own process, and communicates with the controller via emulated UART using the Mavlink protocol - as well as external OSD does.

So there can't be a cool config menu like Betaflight has, but can be support for parameters changing, like in MP.