Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  • Should support rangefinders, optical flow sensor, lidars, barometers, GPS etc..

  • Our solution should be incredibly adaptable to multiple airframes and can be optimized for such

  • Our board should follow Mounting Hole Specifications for easier mounting into our system

...

  • PoC or PoE Custom board

    • Power and Data on one protocol

    • lots of EE complexity

    • would reduce wiring

    • PoE

      • Overkill for our application

      • Lots of implementation details

  • Monster Mount/Board

    • One CAN Node

    • multiple connections to lots of onboard sensors

  • Integration of an individual sensor and CAN node onto a single PCBA

    • no separate translational board (it’s all integrated in one board)

    • Bus based differential wiring scheme that only requires one set of wires to stack of sensors

    • Start with doing this?

    • Small boards with a single sensor and CAN node

    • Start with LiDars and Optical flow sensors because they’re high priority for Pegasus 2024 System Architecture

Final Implementation:

  • Lidar CAN PCBA

    • EFS and EE pick chips and sensors

    • Useful for lots of comp cycles

    • Will save lots of monies in future

    • EFS figure out CAN comms to ardu

Timeline

  • How many people are available to allocate towards this?

    • EE has a lot of bootcampers who are slowly working on it

  • Lidar CAN PCBA

    • hopefully done by end of april

    • then few months of testing

    • fly in comp 2025