Failures

From Project Apollo - NASSP
Jump to navigation Jump to search

NASSP simulates various failures for the CSM, LM and Saturn rockets. To enable them select "Damage and Failure Simulation" under Realism in the Parameters tab of the Orbiter launchpad. Failures can be scheduled or randomized. Aside from specific failures in the simulation, generic switch failures are supported where systems see the state of a switch in a failed switch position, different from the actual position. The specific failures can be scheduled or randomized in the Project Apollo MFD, switch failures are currently only available through editing scenarios.

Specific Failures

For failures to occur they have to be "armed" and a failure condition has to be added to them. These conditions are currently all time based. For both CSM and LM the mission time since launch (failure condition 0) can be used as well as the simulation time (failure condition 1) since the start of the simulation. Only the CSM currently supports more failure conditions.

CSM Failures

Failure Types

The list of available failures that are simulation can be viewed directly in the PAMFD page for failures. The majority of them are still launch or reentry related.

Launch Failures

The center engine on the SIb, SIC and SII stages may randomly shut down early. This may or may not require a launch abort or a different mission profile depending on when in the launch it occurs: with a Saturn 1b this may not leave enough fuel to reach orbit, and with a Saturn V it may not leave enough fuel to reach the Moon.

The LET auto jettison may fail, requiring you to jettison the tower manually. The LET jettison motor may fail, requiring you to jettison the tower manually with the abort motor. Automatic separation of the SII stage from the SIC may fail, requiring you to separate manually.

Display Failures

Random lights on the Caution and Warning System will fail.

Switch Failures

Any of the TWR JETT and SM JETT switches may fail, though only one of each type will fail at any time as having both fail would be fatal. If one of the two redundant switches doesn't function, use the other.

Landing Failures

The apex cover deploy, drogue deploy and main chute deploy may fail randomly. You will have to deploy them manually.

Failure Conditions

The additional failure conditions for the CSM are:

  • 2 = time since S-I/S-II (or S-IVB) staging
  • 3 = time since S-II/S-IVB staging
  • 4 = time since Earth Orbit Insertion
  • 5 = time since TLI preparations start (Timebase 6)
  • 6 = time since TLI cutoff

LM Failures

No specific failures are currently supported for the LM, but switch failures can be scheduled on mission or simulation time.

Switch Failures

Switch malfunctions have to be added to scenarios. For this, a failure section in the scenario has to be added that starts with line FAILURES_BEGIN and ends with FAILURES_END. In between, the following format is used.

SWITCHMALFUNCTION GNComputerMnACircuitBraker 0 0 100.0

1st parameter: name of failed panel element 2nd parameter: failure state of panel element 3rd parameter: The condition type for the failure. See above. 4th parameter: The time value associated with the condition type.

There is no list of switches, but the names can be derived from the saturnpanel.cpp and lempanel.com files where the names are used in the Register function for each switch.