...

• Copy the Pixhawk’s functionality except:

  • a device with more compute for autonomy to do airside processing (an RPi 5)

  • support more CAN transceivers for our push to CAN infrastructure and remove all extra unneeded connectors

• Single Stack for the drone’s LV processing system to minimize assembly effort

  • flight controller would be a RPi hat

  • stack would be: RPI5 + LTE hat + anything we want + zp4

• Leave the HV stuff separate from this stack

  • this allows for us to do weight balance and wire length optimizations still and keeps our system somewhat flexible.

• This project is far out (as of May 2024)

  • We should wait for this to become more necessary as time keeps slipping into the future.

  • If EE has available to start now (or as soon as possible) we should because this is a large endeavor

  • As time goes forward we will get more new features and ideas so no point in the huge rush.

• Optimize for our platform

  • from a high level this has all been done before, we need to optimize for our platform once we define our system architecture

References

• Electrical S24

  • /wiki/spaces/AD/pages/2493087760

• 2024-05-07 EE Architecture

• https://bluerobotics.com/store/comm-control-power/control/navigator/

• very similar idea, this is meant for ROVs so we’d optimize ours for our platform of course

  https://docs.emlid.com/navio2/

Development

Implementation Details

...