summaryrefslogtreecommitdiff
path: root/FCSoftwareRequirements.mdwn
authorPeter Welte <shark@centibyte.org>2007-02-26 03:52:23 (GMT)
committer Peter Welte <shark@centibyte.org>2007-02-26 03:52:23 (GMT)
commitafdaeb5225fd73c2a0224573f5d0bbf3d5d03539 (patch) (side-by-side diff)
treea0661e035dd28fb454e10e37eb93394369856db4 /FCSoftwareRequirements.mdwn
parent99f3e28d044b1658e67ca301d430e0d67fbb348f (diff)
downloadwiki-afdaeb5225fd73c2a0224573f5d0bbf3d5d03539.zip
wiki-afdaeb5225fd73c2a0224573f5d0bbf3d5d03539.tar.gz
FCSoftwareRequirements
Diffstat (limited to 'FCSoftwareRequirements.mdwn') (more/less context) (ignore whitespace changes)
-rw-r--r--FCSoftwareRequirements.mdwn18
1 files changed, 15 insertions, 3 deletions
diff --git a/FCSoftwareRequirements.mdwn b/FCSoftwareRequirements.mdwn
index 64376df..76193aa 100644
--- a/FCSoftwareRequirements.mdwn
+++ b/FCSoftwareRequirements.mdwn
@@ -1,4 +1,16 @@
-This document describes the requirements for the PSAS flight computer software. This will be a fairly detailed and technical requirements document because the "customers" are also the developers.
+## Introduction
+
+This document describes the requirements for the PSAS flight computer software. This will be a fairly detailed and technical requirements document because the "customers" are also the developers. The software described in this document is targeting the AV2b avioncs hardware package which will be running in the LV2c rocket in late 2007.
+
+### Purpose
+
+The purpose of this document is to describe in detail the requirements of the flight computer software. By carefully detailing the requirements of the software, all PSAS members and specifically avionics and software members can review them for accuracy, and ultimately we can produce software that is both complete and correct. Because a detailed list of requirements helps us get the software correct the first time, without redesign, recoding, and retesting, we will be able to launch smarter rockets, faster.
+
+This document should also help new PSAS members and other interested people understand our software's capabilities and operation.
+
+The intended audience of this document is primarily PSAS developers, but the document will be available for review to anyone on the Internet.
+
+### Scope
Feel free to review and add input. --Peter
@@ -28,8 +40,6 @@ The onboard computer is the TQM5200. We're using a TBD GB flash disk. TODO
Sensors (need list) Comm Bus Wireless comm info More hw info OS: Linux 2.6 (Probably &gt; 2.6.20 w/ Sarah's USBFS patches) memory - how much?
-Simulation: code must be designed with unit and integration testing (simulation) in mind
-
Recovery Node: FC sets timer to N seconds (TBD) before it is launched. FC s/ make state of rec. node timer available to GC. If FC detects timer has &lt;= 1 second but FC doesn't think we're at apogee, set timer to 4 seconds.
The FC must detect apogee based on sensor data.
@@ -38,6 +48,8 @@ The FC must send signal to hardware to deploy drogue at apogee.
The FC must record sensor data. -&gt; using flash drive -&gt; using wireless link
+Simulation: code must be designed with unit and integration testing (simulation) in mind
+
The software must not be designed in some crazy way that makes adding active guidance to hard.
The firmware software runs on the control devices. As much of the firmware code as possible must be written in ANSI C so it can be tested with the FC software using the simulator.