Project Apollo - NASSP - User contributions [en]

Flight Sequence Program

2025-04-17T15:50:48Z

Indy91: LOX NPV Vent

The flight sequence program is a series of scheduled commands that is being sent from the LVDC to the stages of the Saturn vehicle (S-IB/C, S-II, S-IVB and IU) during a mission. They are scheduled in various time bases. In NASSP the LVDC loads a flight sequence program file that is valid for a given mission. The file can be found under Config/Project Apollo.

TBD:

-Explain time bases

-Explain stage code

-List of all available Saturn IB and V commands

==Sequences==

'''Initiate LOX Dump (Saturn IB)'''

Prerequisites: Passivation Enable, Stage 3 (S-IVB), Channel 85

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|Aux Hydraulic Pump Flight Mode On||-22.0||3 (S-IVB)||28||The auxiliary hydraulic pump is turned on to center the J-2 engine for damping
|-
|Engine Mainstage Control Valve Open On||-0.2||3 (S-IVB)||30||Commands open main LOX valve
|-
|Engine He Control Valve Open||0.0||3 (S-IVB)||109||Provides pneumatics to open main LOX valve
|-
|LOX Tank NPV Valve Open On||10.0||3 (S-IVB)||42||The LOX NPV valve is latched open, if it is desired to do so
|-
|LOX Tank NPV Valve Open Off||12.0||3 (S-IVB)||37||Only if opened in the previous step
|}

'''Terminate LOX Dump (Saturn IB)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|Engine Mainstage Control Valve Open Off||-1.0||3 (S-IVB)||65||
|-
|Engine He Control Valve Open Off||0.0||3 (S-IVB)||110||
|-
|Aux Hydraulic Pump Flight Mode Off||2.0||3 (S-IVB)||29||
|}

'''Initiate LH2 Tank Blowdown Vent (Saturn IB)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LH2 Tank Vent Valve Open||0.0||3 (S-IVB)||38||
|}

'''Terminate LH2 Tank Blowdown Vent (Saturn IB)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LH2 Tank Vent Valve Close||-3.0||3 (S-IVB)||76||
|-
|LH2 Tank Vent Valve Boost Close On||0.0||3 (S-IVB)||77||
|-
|LH2 Tank Vent Valve Boost Close Off||2.0||3 (S-IVB)||78||
|}

'''Initiate S-IVB LH2 Continuous Vent System (Saturn V)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LH2 Tank Continuous Vent Orifice Shutoff Valve Open On||0.0||3 (S-IVB)||111||
|-
|LH2 Tank Continuous Vent Relief Override Shutoff Valve Open On||0.1||3 (S-IVB)||107||
|-
|LH2 Tank Continuous Vent Orifice Shutoff Valve Open Off||2.0||3 (S-IVB)||112||
|-
|LH2 Tank Continuous Vent Relief Override Shutoff Valve Open Off||2.1||3 (S-IVB)||108||
|}

'''Terminate S-IVB LH2 Continuous Vent System (Saturn V)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LH2 Tank Continuous Vent Valve Close On||0.0||3 (S-IVB)||84||
|-
|LH2 Tank Continuous Vent Valve Close Off||2.0||3 (S-IVB)||87||
|}

'''Open LOX Non-Propulsive Valves'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LOX Tank NPV Valve Open On||0.0||3 (S-IVB)||105||
|-
|LOX Tank NPV Valve Open Off||3.0||3 (S-IVB)||106||
|}

'''Close LOX Non-Propulsive Valves'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LOX Tank Vent and NPV Valves Boost Close On||0.0||3 (S-IVB)||95||
|-
|LOX Tank Vent and NPV Valves Boost Close Off||2.0||3 (S-IVB)||96||
|}

Flight Sequence Program

2025-04-16T20:25:40Z

Indy91:

Flight Sequence Program

2025-04-16T19:45:00Z

Indy91: Saturn V S-IVB continuous vent system procedures

The flight sequence program is a series of scheduled commands that is being sent from the LVDC to the stages of the Saturn vehicle (S-IB/C, S-II, S-IVB and IU) during a mission. They are scheduled in various time bases. In NASSP the LVDC loads a flight sequence program file that is valid for a given mission. The file can be found under Config/Project Apollo.

TBD:

-Explain time bases

-Explain stage code

-List of all available Saturn IB and V commands

==Sequences==

'''Initiate LOX Dump (Saturn IB)'''

Prerequisites: Passivation Enable, Stage 3 (S-IVB), Channel 85

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|Aux Hydraulic Pump Flight Mode On||-22.0||3 (S-IVB)||28||The auxiliary hydraulic pump is turned on to center the J-2 engine for damping
|-
|Engine Mainstage Control Valve Open On||-0.2||3 (S-IVB)||30||Commands open main LOX valve
|-
|Engine He Control Valve Open||0.0||3 (S-IVB)||109||Provides pneumatics to open main LOX valve
|-
|LOX Tank NPV Valve Open On||10.0||3 (S-IVB)||42||The LOX NPV valve is latched open, if it is desired to do so
|-
|LOX Tank NPV Valve Open Off||12.0||3 (S-IVB)||37||Only if opened in the previous step
|}

'''Terminate LOX Dump (Saturn IB)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|Engine Mainstage Control Valve Open Off||-1.0||3 (S-IVB)||65||
|-
|Engine He Control Valve Open Off||0.0||3 (S-IVB)||110||
|-
|Aux Hydraulic Pump Flight Mode Off||2.0||3 (S-IVB)||29||
|}

'''Initiate LH2 Tank Blowdown Vent (Saturn IB)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LH2 Tank Vent Valve Open||0.0||3 (S-IVB)||38||
|}

'''Terminate LH2 Tank Blowdown Vent (Saturn IB)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LH2 Tank Vent Valve Close||-3.0||3 (S-IVB)||76||
|-
|LH2 Tank Vent Valve Boost Close On||0.0||3 (S-IVB)||77||
|-
|LH2 Tank Vent Valve Boost Close Off||2.0||3 (S-IVB)||78||
|}

'''Initiate S-IVB LH2 Continuous Vent System (Saturn V)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LH2 Tank Continuous Vent Orifice Shutoff Valve Open On||0.0||3 (S-IVB)||111||
|-
|LH2 Tank Continuous Vent Relief Override Shutoff Valve Open On||0.1||3 (S-IVB)||107||
|}

'''Terminate S-IVB LH2 Continuous Vent System (Saturn V)'''

Prerequisites: -

{|class="wikitable"
!Event||Time from Event||Stage||Channel||Remarks
|-
|LH2 Tank Continuous Vent Valve Close On||0.0||3 (S-IVB)||84||
|-
|LH2 Tank Continuous Vent Valve Close Off||2.0||3 (S-IVB)||87||
|-
|LH2 Tank Vent and Latching Relief Valves Boost Close On||3.2||3 (S-IVB)||77||
|-
|LH2 Tank Vent and Latching Relief Valves Boost Close Off||5.2||3 (S-IVB)||78||
|}

Flight Sequence Program

2025-02-05T20:23:42Z

Indy91:

Flight Sequence Program

2025-02-05T20:22:38Z

Indy91:

Flight Sequence Program

2025-02-05T19:59:50Z

Indy91: Add more sequences

Flight Sequence Program

2025-02-05T19:56:56Z

Indy91: Initial page

Scenario File Options

2024-09-05T15:07:40Z

Indy91: Explain APOLLONO vs MISSION parameter

The '''Project Apollo''' scenarios have a vast number of options that you can specify. Some of the more useful are:

==General options==

These are options specifying things such as the CSM and LM call signs, various masses, fuel masses and other parameters.

{|class="wikitable"
!width="100"|Option || Function
|-
|TCP||Specifies the height of the rocket above the ground in meters prior to launch. This can be adjusted if the mission is flown from a different launch pad to the default for the spacecraft (e.g. the Skylab 'milk stool' for the Saturn 1b).
|-
|APOLLONO||Apollo mission number. This is used to provide mission-specific systems and events such as mission audio or system failures. This has to be a numeric value and it will load the mission file from the Missions/ProjectApollo/ folder with the name "Apollo X.cfg", with X standing for the number after APOLLONO. If a non-numeric mission file is desired, use the MISSION parameter instead.
|-
|MISSION||See APOLLONO. This parameter will load the mission file from the folder Missions/ProjectApollo with the name "X.cfg", with X standing for the file name specified after MISSION.
|-
|VECHNO||The Saturn vehicle number: typically this will be in the 200s for a Saturn 1b, and 500s for a Saturn V. This is used to name the separated stages and components of the spacecraft.
|-
|REALISM||Sets the realism level from 0 (lowest) to 10 (highest). Lower realism level missions will be easier to fly. ''Quickstart mode'' is level 0, ''Virtual AGC mode'' is level 5.
|-
|DLS||Set to 1 to delete the launch site when the spacecraft passes out of visible range. This can give a significant performance boost on slow machines.
|-
|FDAIDISABLED||Set to 1 to disable the OpenGL FDAI rendering. This can give a significant performance boost on slow machines.
|-
|MISSNTIME||Current mission time in seconds since launch.
|-
|IGMST||Inertial Guidance Mode start: set to the time in seconds after launch at which the autopilot switches to inertial guidance mode and starts trying to hit the target orbit rather than follow the pre-planned pitch program.
|-
|SIFUELMASS||
Specifies the mass in kilograms of the fuel in the first stage (S-IC or S-IB).
|-
|SIEMPTYMASS||
Specifies the empty mass in kilograms of the first stage (S-IC or S-IB).
|-
|SICSHUT||
Specifies the mission time of center engine shutdown of the first stage (S-IC or S-IB).
|-
|SISHUT||
Specifies the mission time of shutdown of the remaining engines of the first stage (S-IC or S-IB).
|-
|SIIFUELMASS||
Specifies the mass in kilograms of the fuel in the second stage (S-IVB for Saturn 1B or S-II for Saturn V). This is not used for the INT-20.
|-
|SIIEMPTYMASS||
Specifies the empty mass in kilograms of the second stage (S-IVB for Saturn 1B or S-II for Saturn V). This is not used for the INT-20.
|-
|SIICSHUT
||
Specifies the mission time of the center engine shutdown of the S-II stage of Saturn V and derivatives.
|-
|SIIPUT||
Specifies the mission time of the PU-shift (change of mixture ratio) the second stage (S-IVB for Saturn 1B or S-II for Saturn V).
|-
|SIISHUT||
Specifies the mission time of shutdown of the remaining engines of the S-II stage of Saturn V and derivatives.
|-
|S4FUELMASS||
Specifies the mass in kilograms of the fuel in the S-IVB stage of Saturn V and derivatives.
|-
|LMASCFUEL||
Specifies the mass in kilograms of the fuel in the LEM ascent stage, if appropriate.
|-
|LMDSCFUEL||
Specifies the mass in kilograms of the fuel in the LEM descent stage, if appropriate.
|-
|SMMASS||Empty mass of the Service Module, in kilograms.
|-
|CMMASS||Empty mass of the Command Module, in kilograms.
|-
|S4PL||
Specifies the payload of the SIVb stage. Current values are:

<code>
0 Standard LEM 
1 ASTP 
2 LTA LEM test article 
3 LM1 test LEM 
4 LTA8 LEM test article 
5 Docking target 
6 LTA6 LEM test article 
7 Empty 
8 Docking adapter for an SIVb 'wet workshop' 
</code>
|-
|AUTOSLOW||Set to 1 to slow to 1x time acceleration when 'something important' happens. For manned flights, this is typically when a piece of mission audio is played, for unmanned flights it is typically a stage separation, engine burn, etc.
|-
|LANDFAIL||Landing failures. Set to 1 to disable all random landing failures in your scenario, or 0 to create a random set of failures.
|-
|LAUNCHFAIL||Launch failures. Set to 1 to disable all random launch failures in your scenario, or 0 to create a random set of failures.
|-
|SWITCHFAIL||Switch failures. Set to 1 to disable all random switch failures in your scenario, or 0 to create a random set of failures.
|-
|UNMANNED||Set to 1 for an unmanned mission.
|-
|ATTACHSTATE||Specifies which 'things' are attached to the spacecraft. This is a bit-field, created by combining the following values as appropriate.

<code>
1 The interstage is attached. 
2 The LES is attached. 
4 There is a docking probe. 
8 The Apex Cover is attached. 
16 The parachutes are attached. 
32 There is a CSM on the launcher. 
64 If there is no CSM, there is a nosecap on the SLA panels.
</code>

Defaults are generally safe to use, but you may need to specify the value in the scenario for unusual missions (e.g. Apollo 5 with no LES or CSM and a nosecap uses 93).
|-
|HASPROBE||Allows you to override the default docking probe state. Set to 1 if the spacecraft has a docking probe, or 0 if it doesn't.

This value is not saved in scenarios written out by orbiter, it is purely intended to allow you to set the docking probe state in initial scenarios without having to specify the full value for ATTACHSTATE. If you specify both HASPROBE and ATTACHSTATE in the same scenario, then whichever value comes second will be used for the docking probe state.
|-
|SLASTATE||Specifies the state of the SLA panels on the SIVB. Bit 8 should be set to 1 if the panels are hinged, or 0 if they separate from the SIVB. Bits 0-7 specify the angle to which they will open if hinged, defaulting to 45 degrees with an upper limit of 150 degrees; if they're not hinged, they currently always separate at 45 degrees.

In most cases the default will work fine (hinged to 45 degrees on Saturn 1b, not hinged on Saturn V), but special missions may require manually setting this state. For example for hinged panels opening to 150 degrees use "SLASTATE 150" in the scenario.
|-
|PAYN||Sets the payload vessel name (e.g. Eagle for the Apollo 11 LEM). This is the name the SIVB payload will be given when it is created; LEMN can be used as a synonym.
|-
|MCC_MT_Enabled||Set to 1 to enable the ground and mission tracking of the [[Mission Control Center]]. This parameter is only used for initializing the MCC before launch and is not saved again in a scenario.
|}

==Mission parameter options==

These are options specifying things such as the earth parking orbit parameters, lunar landing site, various mission time parameters etc.

{|class="wikitable"
!width="100"|Option || Function
|-
|TOAPO||Specifies the desired launch apogee altitude in kilometers.
|-
|TOPER||Specifies the desired launch perigee altitude in kilometers.
|-
|TOHDG||Specifies the desired launch azimuth in degrees.
|-
|TLIMJD||Specifies the desired MJD of the TLI burn.<cite>I</cite>
|-
|LOIMJD||Specifies the desired MJD of the first LOI burn.<cite>I</cite>
|-
|FREERETURNPECMJD||Specifies the desired MJD of the free return pericynthion.<cite>I</cite> (currently unused)
|-
|FREERETURNPECALT||Specifies the desired altitude (in meters) of the free return pericynthion.<cite>I</cite> (currently unused)
|-
|TLIOFFSETLON||Specifies the longitude of desired target offset (in radian) of the TLI burn.<cite>I</cite>
|-
|TLIOFFSETLAT||Specifies the latitude of desired target offset (in radian) of the TLI burn.<cite>I</cite>
|-
|TLIOFFSETRAD||Specifies the radius of the desired target offset (in meters) of the TLI burn.<cite>I</cite>
|-
|MOONMJD||Specifies the desired MJD of the lunar landing.<cite>I</cite>
|-
|MOONBASE||Orbiter base name of the planned landing site on the Moon, if any.<cite>I</cite>
|-
|MOONLAT||Latitude (in degrees) of the planned landing point on the Moon, if any.
|-
|MOONLONG||Longitude (in degrees) of the planned landing point on the Moon, if any.
|-
|MOONALT||Altitude (in meters) of the planned landing point on the Moon, if any.
|-
|EARTHEIMJD||Specifies the desired MJD of the Earth landing entry interface, if any.<cite>I</cite>
|-
|SPLASHLAT||Latitude (in degrees) of the planned splashdown site on the Earth, if any.<cite>I</cite>
|-
|SPLASHLONG||Longitude (in degrees) of the planned splashdown site on the Earth, if any.<cite>I</cite>
|}

==Audio options==

{|class="wikitable"
!width="100"|Option || Function
|-
|LANG||Set to the appropriate string for the audio language you want to use. Currently we only ship English audio, but if, say, you downloaded a French audio add-on you could set this to French instead and the French files would take precedence.
|}

==AGC options==

AGC options are specified between AGC_BEGIN and AGC_END. Options outside those lines will be ignored.

{|class="wikitable"
!width="100"|Option || Function
|-
|EMEM||Set an AGC erasable memory location to a specified value. Addresses and values are both specified in octal (base-8), so to set address 10 (decimal) to 17 (decimal) you would specify <code>EMEM0012 21</code>. LMPAD and CMPAD should be used in prelaunch scenarios.
|-
|}

==Virtual AGC options==

These options are set in the standard CSM configuration, not between the AGC_BEGIN and AGC_END lines. If you try to set them inside the AGC configuration they will be ignored.

{|class="wikitable"
!width="100"|Option || Function
|-
|CMPAD||Set a Virtual AGC erasable memory location in the CM AGC to a specified value. Addresses and values are both specified in octal (base-8), so to set address 10 (decimal) to 17 (decimal) you would specify <code>EMEM0012 21</code>. If the scenario uses the C++ AGC rather than Virtual AGC, these values are ignored.

CMPAD entries are used once to set up the values in the AGC when the scenario is loaded, then thrown away. So they will not be saved to a scenario file when you exit Orbiter.
|-
|LMPAD||Set a Virtual AGC erasable memory location in the LM AGC to a specified value. Addresses and values are both specified in octal (base-8), so to set address 10 (decimal) to 17 (decimal) you would specify <code>EMEM0012 21</code>. If the scenario uses the C++ AGC rather than Virtual AGC, these values are ignored.

Note that the LEM PAD is loaded when the LEM is created, so setting these values when the LEM already exists in the scenario will have no effect.
|-
|LMPADCNT||Sets the number of LEM PAD entries. The LEM PAD is saved in a table until the LEM is created, so the DLL needs to know how large a table to create. Any values beyond this count will be ignored.
|}

==LVDC options==

LVDC options are specified between LVDC_BEGIN and LVDC_END. Options outside those lines will be ignored.

====Guidance Presettings For Boost to Earth Parking Orbit====

{|class="wikitable"
!width="100"|Option || Function
|-
|LVDC_dV_B||Cutoff velocity bias for S-IVB first burn. Velocity in meters per second.
|-
|LVDC_eps_2||Constant time for selection of guidance option that enforces only terminal velocity. Time in seconds.
|-
|LVDC_fx[0]||Coefficients of parking orbit inclination polynomial. Values as degrees in <code>LVDC_fx[0]</code> to <code>LVDC_fx[6]</code>.
|-
|LVDC_gx[0]||Coefficients of parking orbit descending nodal angle polynomial. Values as degrees in <code>LVDC_gx[0]</code> to <code>LVDC_gx[6]</code>.
|-
|LVDC_H||Third zonal harmonic coefficient in gravitational potential model.
|-
|LVDC_J||Second zonal harmonic coefficient in gravitational potential model.
|-
|LVDC_Fx[1][0]||Coefficients for the four-segment first-stage tilt polynomial. <code>LVDC_Fx[1][0]</code> to <code>LVDC_Fx[1][4]</code> for the first segment, <code>LVDC_Fx[2][0]</code> to <code>LVDC_Fx[2][4]</code> for the second segment etc.
|-
|LVDC_Rho[0]||Atmospheric density mode polynomial coefficients.
|-
|LVDC_ROV||Constant for biasing terminal range-angle prediction in first S-IVB burn.
|-
|LVDC_T_ar||Time from Timebase 1 when tilt arrest occurs.
|-
|LVDC_tau2||Estimated time to burn up vehicle completely, from a selected time between T1I=0 and the end of the artificial tau mode.
|-
|LVDC_tau2N||Nominal tau, used in the S-IVB first-burn artificial tau mode.
|-
|LVDC_tau3||Estimated time to burn up S-IVB completely, constant during first and second stages of IGM.
|-
|LVDC_T_S1||Segment switch times for four-segment first-stage tilt polynomial reference to Timebase 1.<code>LVDC_T_S1</code> to <code>LVDC_T_S3</code>.
|-
|LVDC_Tt_3||Estimated third-stage burn time.
|-
|}

====Guidance Presettings for Translunar Injection Boost====

{|class="wikitable"
!width="100"|Option || Function
|-
|LVDC_eps_2R||Constant time for selection of guidance option that enforces only terminal velocity end-conditions during S-IVB second burn.
|-
|LVDC_eps_3R||Constant time for selection of guidance option that freezes the terminal conditions during the second S-IVB burn.
|-
|LVDC_T_4N||Nominal time from TB4 to first GCS.
|-
|}

====Targeting Presettings for Daily Launch Window====

{|class="wikitable"
!width="100"|Option || Function
|-
|LVDC_ALFTSA||Desired angle between the S Vector (Nodal crossing of target ellipse and Earth Parking Orbit) and T (Unit Target) vector at restart preparation for first opportunity. (constant across daily launch window.)
|-
||LVDC_ALFTSB||Desired angle between the S Vector (Nodal crossing of target ellipse and Earth Parking Orbit) and T (Unit Target) vector at restart preparation for second opportunity. (constant across daily launch window.)
|-
|LVDC_BETAA||Angle between S Vector and Radius Vector at initiation of S-IVB restart preparations for first opportunity. (constant across launch window.)
|-
|LVDC_BETAB||Angle between S Vector and Radius Vector at initiation of S-IVB restart preparations for second opportunity. (constant across launch window.)
|-
|LVDC_CCSA0||<code>LVDC_CCSA0</code> through <code>LVDC_CCSA14</code> are values of a 15-point table of the cosine of the true anomaly of the target vector as a function of time into the launch window for first opportunity.
|-
|LVDC_CCSB0||<code>LVDC_CCSB0</code> through <code>LVDC_CCSB14</code> are values of a 15-point table of the cosine of the true anomaly of the target vector as a function of time into the launch window for second opportunity.
|-
|LVDC_C3A0||<code>LVDC_C3A0</code> through <code>LVDC_C3A14</code> are values of a 15-point table of twice the specific energy of the target ellipse as a function of time into the launch window for first opportunity.
|-
|LVDC_C3B0||<code>LVDC_C3B0</code> through <code>LVDC_C3B14</code> are values of a 15-point table of twice the specific energy of the target ellipse as a function of time into the launch window for second opportunity.
|-
|LVDC_DECA0||<code>LVDC_DECA0</code> through <code>LVDC_DECA14</code> are values of a 15-point table of target vector declination as a function of time into the launch window for first opportunity.
|-
|LVDC_DECB0||<code>LVDC_DECB0</code> through <code>LVDC_DECB14</code> are values of a 15-point table of target vector declination as a function of time into the launch window for second opportunity.
|-
|LVDC_dV_BR|| Cutoff velocity bias for translunar injection (constant across daily launch window.)
|-
|LVDC_ENA0||<code>LVDC_ENA0</code> through <code>LVDC_ENA14</code> are values of a 15-point table of target ellipse eccentricity as a function of time into the launch window for first opportunity.
|-
|LVDC_ENB0||<code>LVDC_ENB0</code> through <code>LVDC_ENB14</code> are values of a 15-point table of target ellipse eccentricity as a function of time into the launch window for second opportunity.
|-
|LVDC_FA||True anomaly of the predicted cutoff radius vector for first opportunity (constant across daily launch window).
|-
|LVDC_FB||True anomaly of the predicted cutoff radius vector for second opportunity (constant across daily launch window).
|-
|LVDC_hx[0][0]||<code>LVDC_hx[0][0]</code> through <code>LVDC_hx[0][4]</code> are coefficients of the first-segment polynomial of launch azimuth versus time.
|-
|LVDC_hx[1][0]||<code>LVDC_hx[1][0]</code> through <code>LVDC_hx[1][4]</code> are coefficients of the second-segment polynomial of launch azimuth versus time.
|-
|LVDC_hx[2][0]||<code>LVDC_hx[2][0]</code> through <code>LVDC_hx[2][4]</code> are coefficients of the third-segment polynomial of launch azimuth versus time.
|-
|LVDC_hx[3][0]||<code>LVDC_hx[3][0]</code> through <code>LVDC_hx[3][4]</code> are coefficients of the fourth-segment polynomial of launch azimuth versus time.
|-
|LVDC_RASA0||<code>LVDC_RASA0</code> through <code>LVDC_RASA14</code> are values of a 15-point table of target vector right ascension as a function of time into the launch window for first opportunity.
|-
||LVDC_RASB0||<code>LVDC_RASB0</code> through <code>LVDC_RASB14</code> are values of a 15-point table of target vector right ascension as a function of time into the launch window for second opportunity.
|-
|LVDC_RNA||Predicted radius at reignition for first opportunity (constant across daily launch window).
|-
|LVDC_RNB||Predicted radius at reignition for second opportunity (constant across daily launch window).
|-
|LVDC_t_DS0||<code>LVDC_t_DS0</code> through <code>LVDC_t_DS3</code> are the partition times for launch azimuth polynomial segments.
|-
|LVDC_t_D1||<code>LVDC_t_D1</code> through <code>LVDC_t_DS3</code> are the initial times for the azimuth polynomial segments.
|-
|LVDC_TETEO||Angle between the inertial meridian of the vernal equinox and the Pad 39A meridian at Guidance Reference Release.
|-
|LVDC_T_LO||Time from midnight Greenwich Mean Time to GRR on day of launch.
|-
||LVDC_TPA0||<code>LVDC_TPA0</code> through <code>LVDC_TPA14</code> are values of a 15-point table of time since launch window opening. These time are values of all out-of-orbit targeting tables for first opportunity.
|-
||LVDC_TPB0||<code>LVDC_TPB0</code> through <code>LVDC_TPB14</code> are values of a 15-point table of time since launch window opening. These time are values of all out-of-orbit targeting tables for second opportunity.
|-
|LVDC_t_SD1||<code>LVDC_t_SD1</code> through <code>LVDC_t_SD3</code> are azimuth polynomial normalizing coefficients.
|-
|LVDC_TSTA||Time to begin testing for restart preparations referenced to Timebase 5 for first opportunity.
|-
|LVDC_TSTB||Time to begin testing for restart preparations referenced to Timebase 5 for second opportunity.
|-
|LVDC_XLunarAttitude||Roll, pitch and yaw attitude required for S/C separation maneuver.
|-
|}

==Checklist Information==

These values are defined between the lines <checklist> and </checklist>

{|class="wikitable"
!width = "100"|Option || Function
|-
|FILE || This is the file name of the checklist file to use.
|-
|AUTO || This defines whether to automatically execute the checklists.
|}

Additionally there are two items to define in the launch vehicle before the scenario starts. These are NOT defined between <checklist> and </checklist>

{|class = "wikitable"
!width = "100"|Option || Function
|-
|LEMCHECK || This is the file name of the checklist the LEM should use.
|-
|LEMCHECKAUTO || This defines whether the LEM should automatically execute the checklists.
|}

==Scenario information==
{|class="wikitable"
!width="100"|Option || Function
|-
|NASSPVER|| The version of the current scenario file. The first two digits are reserved to indicate the current NASSP version. The remaining 3 digit number is incremented each time a breaking change is made to a scenario parameter.
|}

==See Also==

* [[Config File Options]]

[[Category:Scenario configuration]]

Failures

2024-05-15T14:53:04Z

Indy91:

'''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.

Failures

2024-05-15T14:50:21Z

Indy91: Created page with "'''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..."

ProjectApolloMFD

2022-03-05T15:57:07Z

Indy91:

[[Image:ProjectApolloMFD.jpg|thumb|right|ProjectApolloMFD ECS screen.]]

The '''ProjectApolloMFD''' provides users with important mission information, which cannot otherwise be accessed from within the simulation. Mission time, guidance parameters, environmental variables, and a TLI program are included. To access ProjectApolloMFD, activate it from the Modules tab of Orbiter's launchpad.

== Mission Time ==

Current mission time is always displayed in the upper portion of the MFD.

All other information can be accessed on the various sub-screens, which are selectable from the main menu.

== Guidance, Navigation & Control (GNC) ==

This screen displays relevant flight information:

* Velocity (ft/s)
* Vertical Velocity (ft/s)
* Altitude (nm)
* Apoapsis Altitude (nm)
* Periapsis Altitude (nm)
* Inclination (deg)
* Latitude (deg)
* Longitude (deg)

Pressing the '''EMS''' button will save a bitmap of the current [[Entry Monitoring System]] scroll.

Pressing the '''DMP''' button creates a [[Virtual AGC]] core memory dump file in the Orbiter directory. The file is named ''ProjectApollo CMC.core'' for the CMC or ''ProjectApollo LGC.core'' for the LGC. If the file already exists it will be overwritten. The core dump file can be used with the [http://www.ibiblio.org/apollo/yaAGC.html yaAGC] in order to debug the AGC flight software for example.

To access, press '''GNC''' on the main menu.

== Environmental Control System (ECS) ==

For the CSM this screen contains two parameters:

*Crew Status
*Glycol Cooling Loops
*Status of CSM O2 Hose

The crew status parameter displays the number and status of the crew. Although basic, the simulation does take into account such variables as temperature, CO2 levels, and cabin/suit pressurization. Exposing the crew to inhospitable conditions will
affect their life functions, and result in an appropriate warning displayed in the Crew Status field. The number of crew members can be changed by pressing '''CRW''' and a number from 0 (no crew) to 3.

The second parameter allows testing of the glycol coolant loops. These loops provide vital cooling to certain spacecraft systems, as well as to the cabin and the crew's suits. Using the '''PRIM''' and '''SEC''' buttons, one can input power output values from -3000W to 3000W for either or both loops. The simulation of these systems is accurate, and effects of various power outputs on spacecraft systems can be observed. See [[Environmental Control System (CSM)]] for more informations.

The CSM O2 Hose can be connected when the LM is docked using the '''HOS''' button. A hose connected to the suit loop in the CSM pushes air to the LM cabin, which overpressurizes it, leading to an air circulation back to the CSM cabin. In reality and in the simulation this can be used to prevent CO2 building up in the LM without getting scrubbed, during times when the LM is still inactive.

In the LM the additional parameters displayed are the specific status of the Commander (CDR) and Lunar Module Pilot (LMP). They can be in the cabin, suits or the PLSS. The '''CRW''' button only changes the number of crew in the cabin, so to move CDR and/or LMP into or out of the LM they first have to be moved to the cabin and then further moved into the suits or out of the LM.

The '''EVA''' button can be used to start an EVA, provided the forward hatch is open. Due to some current limitations only one astronaut can be send outside.

To access, press '''ECS''' on the main menu.

== Instrument Unit (IU) ==

The IU screen can be used to send various commands to the Instrument Unit. Before this can be done, select the vessel with the IU using the '''SRC''' button. The uplink options are:

*Switch Selector. This option sends specific discrete signals to any of the Saturn stages. This can be anything from starting or stopping engines to setting or resetting single relays. A full list of available commands will be provided on the [Launch Vehicle Digital Computer] page. Use the '''STA''' button to select the stage for the command and the '''CHA''' button for the specific command identification.
*Timebase Update. Many of the events on the Saturn stages are following a precise schedule, relative to time bases (e.g. time base 7, time since TLI cutoff). It can be necessary to postpone future events. This can be done by sending a time base update. The time increment is equal to the change in event times after the update. Input a delta time with the '''TIM''' button.
*LM Abort (Apollo 5). This Apollo 5 only commands starts the sequence of events to jettison the Lunar Module in case of an abort (e.g. S-IVB engine failure).
*TD&E Enable. On a lunar mission this command enables the sequence of events for performing Transposition, Docking and Extraction in Earth orbit, following a decision to not go ahead with the TLI maneuver. The S-IVB will go into attitude hold at a preprogrammed time. This command permamently disables the TLI maneuver.
*Restart Maneuver Enable. This command enables the Apollo 9 restart maneuver, following the separation of the CSM and LM from the S-IVB.
*Timebase 8 Enable. For Apollo 10 and later the sequence of events in the S-IVB following TD&E is not enabled until this ground command is send. During Apollo 10 and 11 this command should be send shortly after LM ejection (MCC scenarios send it automatically). Timebase 8 is then started automatically 2 hours after TLI. On Apollo 12 and later sending this command immediately starts the S-IVB APS Evasive Maneuver.
*Evasive Yaw Maneuver Enable. On Apollo 12 and later the S-IVB perform a yaw maneuver to get into an attitude pointing away from the CSM+LM stack for the evasive burn. This command should be send shortly after LM ejection, or as scheduled in the flight plan.
*Execute Comm Maneuver. After the S-IVB has performed all its maneuvers for lunar slingshot or impact it can be desirable to get into an attitude that is optimal for communication with Earth. Sending this command will start an attitude maneuver to that preprogrammed attitude.
*S-IVB/IU Lunar Impact. This type of uplink is used to schedule a burn for a course correction for lunar impact of the S-IVB. The calculation for this burn can be found in the RTCC MFD under Utilities. After the burn parameters have been calculated input them with the '''TIG''', '''BT''', '''PIT''' and '''YAW''' buttons and uplink the maneuver.
*Remove Inhibit Maneuver No. 4. This Apollo 9 only command allows the S-IVB to maneuver back to orb rate tracking after having been in attitude hold for TD&E.

To access, press '''IU''' on the main menu.

== Telemetry (TELE) ==

The telemetry page can be used for uplinking data to the Apollo Guidance Computer. The available options are:

*State vector update. First select the source vessel using the '''SRC''' button and the reference body (Earth or Moon) using the '''REF''' button. Also choose in which state vector slot in the AGC the uplink will occur, using the '''SLT''' button. Then press the '''SV''' button twice to start the uplink.
*Clock update. To update the clock in either AGC use the '''CLK''' button to start the uplink.
*Ascent Engine Arming. This LM only can be used to remotely arm of the Ascent Propulsion System. Press the '''AEAA''' button and choose the relays to set or reset.
*Apollo 5 abort. Two buttons are included to start two abort sequences in the Apollo 5 LGC software. The first, for a suborbital abort, is started with the '''SAB'''. For a late ascent abort, following an attempt by the LM to reach orbit, use the '''COI''' button for Contingency Orbit Insertion.

== Lunar Guidance Computer (LGC) ==

The LGC screen contains a number of helpful tools for LM activation. In the upper half of the screen it shows the TEPHEM (launch time) from the CMC. Below that are IMU attitudes of the CSM and the corresponding required docked alignment of the LM.

After the docked coarse alignment using the display attitude a fine alignment for Verb 42 can be calculated using the '''V42''' button. In almost all the cases the attitude reference (REFSMMAT) will be the same for CSM and LM. Only during Apollo 9 for the rendezvous day were local vertical, local horizontal attitude references used, which has a different definition for CSM versus LM. In this case only use the '''REF''' button and set the alignment reference to LVLH.

Two buttons for clock initialization are included on the screen. To initialize the AGS clock using the backup method start Verb 47 on the DSKY and enter 377+00000 on the DEDA without pressing ENTRS. The '''V47''' button then causes an simultaneous ENTR press on both DSKY and DEDA. In the LGC this stores the current time as a AGS time reference. In the AGS this sets the clock time to zero.

The second clock procedure is for comparing CMC and LGC clock. Enter Verb 06 Noun 65 on both the CSM and the LM DSKYs. The '''ENT''' button then presses ENTR on both DSKYs at the same time. The difference between the CMC and LGC clock times can then be used to enter a time increment (Verb 55) for the LGC.

== Failure Simulation (FAIL) ==

A number of system failures are supported in NASSP, mainly concerning the [SECS] in the CSM and engine or guidance failures in the Saturn vehicle. There are two pages with the status of the failure simulation which can be cycled with the '''PAG''' button. Using the '''RAN''' a random selection of failures can be generated.

The first page contains the SECS failures Enter the corresponding number of the failure using the '''SEQ''' button. The second page shows the engine failures on the S-IB/S-IC and S-II stages. Also supported are a IU reference failure and a failure of the S-II interstage to separate.

ProjectApolloMFD

2022-03-05T15:56:56Z

Indy91: Add failure section

ProjectApolloMFD

2022-03-05T15:51:06Z

Indy91: Add LGC section

ProjectApolloMFD

2022-03-05T15:08:14Z

Indy91: Update TELE section

ProjectApolloMFD

2022-03-05T14:57:00Z

Indy91: Update IU section

ProjectApolloMFD

2022-03-05T14:28:56Z

Indy91: Update ECS section

ProjectApolloMFD

2022-03-05T14:18:53Z

Indy91: Update GNC section

ProjectApolloMFD

2022-03-05T14:15:03Z

Indy91: Add new PAMFD pages