OBDH Team Members
David Marshall ku.ca.el|91mad#ku.ca.el|91mad
Gareth Douglas ku.ca.el|87dg#ku.ca.el|87dg
James Forster ku.ca.el|01fhj#ku.ca.el|01fhj
Tom Hands ku.ca.el|1hot#ku.ca.el|1hot
Dominic Hilliard ku.ca.el|241hd#ku.ca.el|241hd
Andy West ku.ca.el|291wa#ku.ca.el|291wa
Robert Garner ku.ca.el|751gr#ku.ca.el|751gr
Peter Adams ku.ca.el|1alsp#ku.ca.el|1alsp
Gareth Gould ku.ca.el|7gjg#ku.ca.el|7gjg
Ian Griffiths ku.ca.el|04gi#ku.ca.el|04gi
Peter Hague ku.ca.el|91hrp#ku.ca.el|91hrp
Greg Smith ku.ca.el|41spg#ku.ca.el|41spg
All our code can be found on our Google Code project.
- Subsystem integration
- Interface overview
- ADCS Interface
- COMS Interface
- Payload Interface
- PSU Interface
- ADIL Determines Image Lightness
- Data Budget
- I2C Command Bus
- Power up procedures
- SD card specification and testing
- SD Implementation
- Main Program Loop
A list of work packages for the OBDH subsystem, and their descriptions, can be found on the management pages.
Before ANY work is attempted on the work packages, team members should read the OBDH operations manual PLM-OBDH-Operations-215. There are important instructions there for handling the equipment and avoiding ESD (Electro-Static Discharge).
All work done on these packages must be documented whilst it is underway.
A work package will only be considered complete when that documentation is submitted and specified outputs are generated. This is to ensure that the completion of each work package can be independently verified, and the work checked.