Mission File Options

From Project Apollo - NASSP
Jump to navigation Jump to search

NASSP uses a mission file to specify vehicle configuration and mission parameters.

Option Function Default Value
SMJCVersion Service Module Jettison Controller version. A modification was used on Apollo 13 and later to prevent the Service Module from skipping out of the atmosphere on reentry. Valid values are:

1 Block I and pre Apollo 13
2 Apollo 13 and later

1
JMission If set to TRUE, the CSM will have the panels and systems that were flown on the J-type Apollo missions FALSE
Panel277Version Version of CSM panel 277. Valid values are:

0 No panel
1 J-type mission panel
2 Skylab missions panel

0
Panel278Version Version of CSM panel 278. Valid values are:

1 Pre Apollo 15
2 Apollo 15-16
3 Apollo 17
4 Skylab
5 ASTP

1
LMDSKYVersion Version of the LM DSKY. Valid values are:

1 Same as CM DSKY (Apollo 10 and before)
2 ALT and VEL lights (Apollo 11-14)
3 PRIO DISP and NO DAP lights (Apollo 15-17)

2
HasLMProgramer If set to TRUE the Lunar Module Programer for automatic flight and remote control is used (Apollo 5 only) FALSE
HasAEA If set to TRUE the Lunar Module has an Abort Electronics Assembly (computer of the AGS). Only Apollo 5 did not fly one. TRUE
LMHasAscEngArmAssy If set to TRUE the Ascent Engine Arming Assembly is used to remotely fire the APS engine in an unmanned configuration (flown on Apollo 9 and 10) FALSE

TBD

Retrieved from "http://nassp.space/index.php?title=Mission_File_Options&oldid=2395"