Introduction

• Lighting Boards outlines general hardware development information for hardware.

• Fixed Wing 2025 is intended to leverage Single Servo Driver & LED Board Rev 2 for lighting.

• Big Quad 2025 is intended to leverage LED Board Rev 3 for lighting.

Development Plan

• Single Servo Driver , LED Board Rev 3 , & LED Board Rev 2 all feature Neopixels controlled by an STM32 with a CAN transceiver.

• Initially boards will be assembled and programmed to command a constant color for validation.

• Boards can then be mounted into the target system with final wiring configuration and be leveraged for media photography.

• Eventually boards should be able to communicate with each other over CAN to be able to produce synchronized hardcoded lighting patterns (in which all boards match timings).

• Next boards should support firmware flashing over CAN using a development board to program them one at a time. This will require bootloader support.

  • See come context in this convo.

• Then boards should support flashing firmware from the Pixhawk via mission planner the same way normal DroneCAN peripherals function. This may require using AP_Periph or other COTS software to integrate.

  • Highly consider use of ardupilot/Tools/AP_Periph at master · ArduPilot/ardupilot

• Lighting boards should support easily scriptable lighting patterns being commanded by flight controller events or pilot input. Consider lua scripting or other “low priority” scripting methods that do not require modifications to ardupilot firmware to function.