LOS Link

Rough Notes:

• LOS Link is to handle the interface between (likely) attitude manager and the driver for what ever protocol between the receiver and flight controller (protocols may include PPM, SBus, and Crossfire)

  • A PPM driver has already been implemented

  • SBus: https://reefwing.medium.com/how-to-write-your-own-flight-controller-software-part-2-bc7f27214bb2#:~:text=Remote%20Control%20Receiver.-,The%20SBUS%20Protocol,-In%20the%20old

  • CrossFire: uses UART

• There must be a method to know which protocol your using. Since ZP software should care about which protocol we are using, this should be handled within LOS.

  • There will be an accessible .h file that will have a bunch of defines letting us know which driver to use (all these drivers should output the exact same thing so they can be easily swapped in and out by LOS interface).

  • The defines can be used with ifdef preprocessor directives to determine which part of the code should be compiled to allow the use of the proper driver.

• ZP software shouldn’t even care about which peripherals are being used or the pinout. That should all be handled by the interface/driver.

  • This will also be found in the same accessible .h file and will hold all the configuration data such as which pins and peripherals are being used for each driver.

• Inputs:

  • Initialization of the LOS Link would require no inputs from AM. LOS link will look into the plane config file to determine the number of channels being used.

  • LOS Link would not require any inputs when using the interface

• Outputs:

  • The channel percentages

• Public functions: