Mission File Options: Difference between revisions

From Project Apollo - NASSP
Jump to navigation Jump to search
(Create page)
 
(Add first few mission file parameters)
Line 1: Line 1:
NASSP uses a mission file to specify vehicle configuration and mission parameters.
NASSP uses a mission file to specify vehicle configuration and mission parameters.


{|class="wikitable"
!width="100"|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:
<code>
1    Block I and pre Apollo 13<BR>
2    Apollo 13 and later<BR>
</code>
||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:
<code>
0    No panel<BR>
1    J-type mission panel<BR>
2    Skylab missions panel<BR>
</code>
||0
|-
|}
TBD
TBD

Revision as of 13:00, 20 June 2026

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

TBD