wiki/ SoftwareRequirementsJune2003

Software Requirements, June 2003 Launch

  1. Flight Computer
  2. will initialize with a "power on self test" that determines which CAN nodes are currently active in the system, then enter a valid state in the state machine
  3. will have a manual override to exit the launch-ready state
  4. will accept all CAN packets with < 5% dropped
  5. each CAN packet will take <1 millisecond from receipt at the CAN chip, dispatch by muxer, to signal of action thread
  6. Logger
  7. will have no discernable impact on other processing
  8. will guarantee 100% logging of all packets, including those with failed header checksum, up to the limit of the log buffer
  9. will deal gracefully with log buffer overflow; if necessary, will discard oldest data first
  10. 2.4 Ghz downlink
  11. software will tolerate 100% failure of link
  12. when resuming from a failure, will process most recent data first
  13. will process 10 ping packets per second from the ground to Flight Computer
  14. Assumptions
  15. maximum of 128K bytes/sec received on CAN bus
  16. lots of spare cycles in the Flight Computer
  17. limiting factor will be bandwidth on the 2.4 Ghz link, which is expected to be 1 Mbit/sec in each direction