summaryrefslogtreecommitdiff
path: root/FCSoftwareRequirements.mdwn
authorPeter Welte <shark@centibyte.org>2007-03-25 04:30:07 (GMT)
committer Peter Welte <shark@centibyte.org>2007-03-25 04:30:07 (GMT)
commit84b19ae7f8667499da4b070cdc7a18fa6c2ff88f (patch) (side-by-side diff)
tree34a9a461eb4215add23aaa0e4d4f9da9bc0f2142 /FCSoftwareRequirements.mdwn
parent296d001c0aeb02d715a2907bd42949e3dcd923ed (diff)
downloadwiki-84b19ae7f8667499da4b070cdc7a18fa6c2ff88f.zip
wiki-84b19ae7f8667499da4b070cdc7a18fa6c2ff88f.tar.gz
FCSoftwareRequirements: cleanup
Diffstat (limited to 'FCSoftwareRequirements.mdwn') (more/less context) (ignore whitespace changes)
-rw-r--r--FCSoftwareRequirements.mdwn2
1 files changed, 1 insertions, 1 deletions
diff --git a/FCSoftwareRequirements.mdwn b/FCSoftwareRequirements.mdwn
index 609c94c..bf7b37f 100644
--- a/FCSoftwareRequirements.mdwn
+++ b/FCSoftwareRequirements.mdwn
@@ -162,7 +162,7 @@ The following are specific requirements, organized primarily by functionality. T
1. The software should have a method to configure whether or not antennas should be powered up.
2. The software must have a way for users to specify GPS position of the launch site, and starting barometric pressure at the launch site. [See setbase.sh and sequencer.c from old software; the software uses it to help detect liftoff].
3. The software should have a way for users to specify the Ameature radio callsign for the ATV node to use.
-2. Flight Sequencing: the software controls flight sequencing based on internal state machine, input from other subsystems and uplink data. The software will implement the state machine described in the [[FlightComputerStateFlowSep2003]] page. The highlights are described here:
+2. Flight Sequencing: the software controls flight sequencing based on internal state machine, input from other subsystems and uplink data. The software will implement the behavior described in each state in the [[FlightComputerStateFlowSep2003]] page. The highlights are described here:
1. The software will initialize with a "power on self test" that determines which nodes are currently active in the system, then enter a valid state in the state machine.
2. The software must set the recovery node timer to TIME\_TO\_APOGEE seconds before launch.
3. If an FC\_ABORT\_LAUNCH command is receieved from Launch Control the software enter the appropriate abort state if one is defined. If no abort state is defined (for example, once the motors ignite and launch is detect it is impossible to abort) the event will be logged and no state change will occur.