...
- Ben Hyman (RIT Student)
- Billy Siegener (RIT Student) (bill)
- Dante Sivo (RIT Student)
- Yevgeniy Gorbachev (RIT Student) (gorb)
- Chloe Clark (RIT Student)
- Aaron Chan (RIT Student) - grafana expert
- Kenny Kim (RIT Student)
- Will Merges (RIT Student)
- James May (RIT Student)
- caw5317
- Alec Paul
- Jonathan Russo (RIT Student)
- Paige Elias (RIT Student)
- Adam Lehman
- @joe
- Joseph Even (RIT Student)
Goals
- Lay out high-level requirements
- The modules should be electrically independent
...
- need central shared bus
- any protocol with a master/slave structure is disadvantageous as it breaks "functional independence"
- speeeeeeedspeeeeeeeds
Board Separation
- 70cm RF is on the GPS board, not the telemetry board, because that's the only use case for 70cm RF
- Battery board is separate because it's a large failure point and should be very customizable
- Logging board should listen to literally every other board
...
- scope creep can get to us
- this could get very large and very complicated very quickly
- important to be diligent in designing for now, not digging ourselves into holes, not making unnecessary modules, etc.
Action items
...
Requirements
- High level for now - qualitative, not quantitative
Goals by start of AY 2022-23
- Connector(s) selected
- Protocol selected
- Voltages selected
- Good idea for sensors
- Good idea for module breakdown
- Microcontroller selected
- Requirements enumerated
Action items
- Sleep on the requirements
- Think about protocols
- Think about connectors