First Steps and Failures: Difference between pages

From Project Apollo - NASSP
(Difference between pages)
Jump to navigation Jump to search
m (Reverted edits by [[Special:Contributions/imported>Indy91|imported>Indy91]] ([[User talk:imported>Indy91|talk]]) to last revision by [[User:imported>Thymo|imported>Thymo]])
Tag: Rollback
 
(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...")
 
Line 1: Line 1:
{{Infobox | caption=Realism Levels | text = ''Quickstart Mode''
'''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.
* For beginners
* Orbiter-like control of the spacecraft
* Almost no panel usage necessary


''Virtual AGC Mode''
=Specific Failures=
* For advanced users
* Realistic behavior of the spacecraft
* Utilizes Virtual AGC }}


After you finished the [[Installation|Installation]] of the latest beta version the Project Apollo scenarios are in the '''"Project Apollo - NASSP" scenario folder''' and subfolders. Because of the ongoing development many of the scenarios and missions are not working yet, they are in the "Broken Scenarios" folder.
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.


Project Apollo - NASSP supports different levels of complexity or '''realism modes''', so you can adjust the difficulty level you want to use. You choose the desired mode by choosing the  appropriate scenario. At the moment ''Quickstart Mode'' is available for beginners, while ''Virtual AGC Mode'' is intended for the advanced user.
==CSM Failures==


== Quickstart Mode ==
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.
{{ Attention | message=Quickstart missions are no longer supported. Consider using the Virtual AGC scenarios. }}
[[Image:Saturn1b_on_pad.jpg|thumb|right|The Apollo 7 Saturn 1b on pad]]


The Quickstart mode is intended for beginners, who are already familiar with Orbiter in general, but don't have much particular knowledge about Apollo and the historic spacecraft. If you aren't familiar with Orbiter yet, we suggest to try the built-in Deltaglider at first.
The additional failure conditions for the CSM are:


In Quickstart mode as much as possible is done automatically and the spacecraft behave as much as possible like standard Orbiter spacecrafts. It's only very rarely necessary to use the panel. All (or almost all) critical maneuvers are done by autopilot and you can also fly the spacecraft more "Orbiter like" than the real Apollo spacecraft. The [[Simple AGC]] is used as [[w:Apollo_Guidance_Computer|Apollo Guidance Computer (AGC)]].
*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


This mode is currently the only mode that can effectively fly a complete moon landing mission.  There is a (in progress) tutorial and checklist page [[Quickstart to the Moon]].
==LM Failures==


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


The following missions and scenarios are available for Quickstart mode:
=Switch Failures=


* [[Apollo 7#Quickstart mode|Apollo 7]]
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


== Virtual AGC Mode ==
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.


[[Image:SaturnV_on_pad.jpg|thumb|right|The Apollo 11 Saturn V on pad]]
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.
 
The Virtual AGC mode is intended for the advanced users, who already have some basic knowledge about the [[w:Project_Apollo|Apollo missions]], are familiar with Orbiter and now want to do it like the real astronauts did.
 
In Virtual AGC mode everything is as authentic as possible and you have to fly the mission (almost) like the real thing. You have to do long checklists and control the internal systems manually. The spacecrafts behave more like the real ones, the S-IVB is restartable only once for example.
 
A very important device of the Apollo spacecraft is the [[w:Apollo_Guidance_Computer|Apollo Guidance Computer (AGC)]], which normally does the guidance, navigation and control tasks. In this mode, the [http://www.ibiblio.org/apollo/ Virtual AGC], an Apollo Guidance Computer emulator running the original, authentic Apollo flight software (at the moment '''Colossus 1A''', build 249 from October 28, 1968, flown with Apollo 9) is used. With the [[Virtual AGC]] you can do all procedures exactly as described in the original documentation.
 
{{ Attention | message=Because of the AGC hardware emulation time acceleration higher than about 10x is not recommended as long as the guidance computer is turned on.}} 
 
On real Apollo missions, many things went wrong, mostly minor. In Virtual AGC mode, some of these failures are simulated at the appropriate time in the mission. So be sure to perform your control panel checks and work around any failures which do occur.
 
=== Missions ===
 
The following missions and scenarios are available for Virtual AGC mode:
 
* [[Apollo 7#Virtual AGC mode|Apollo 7]]
 
=== Checklists ===
 
The following checklists are available for Virtual AGC mode:
 
==== Annotated checklists in Word file format ====
 
are in the Doc\Project Apollo - NASSP\Checklists folder of your installation.
 
==== Project Apollo Checklist MFD ====
 
For Virtual AGC Mode Project Apollo Checklist MFD provides in-game checklists. It can execute checklists automatically, so to watch the show do the following:
 
* Start Orbiter, go to the "Extras" tab of the Orbiter launchpad, double-click Vessel configuration and then double-click Project Apollo Configuration.
* Go to the "Virtual AGC Mode" tab and activate both the "Enable automatic checklist execution" and the "Slow automatic checklist execution (e.g. for demonstrations)" option.
* Start the "Project Apollo - NASSP/Apollo 7 Virtual AGC - Launch" scenario. Choose "Start paused" if you don't want to miss the first steps.
* Press F1, F4, choose "Custom, then "External MFD".
* Select the "Project Apollo Checklist" MFD.
* Press FLSH to highlight the switch of the current step (if applicable)
* Unpause Orbiter and enjoy the show!
 
== Unmanned Missions ==
 
A few unmanned Apollo missions are supported. The missions run automatically, simply activate time acceleration and wait for the next event. time acceleration will be deactivated a few minutes beforehand.
 
* [[Apollo 4|Apollo 4]]
* [[Apollo 5|Apollo 5]]
* [[Apollo 6|Apollo 6]]
 
 
== Fictional Missions ==
 
Scenarios in Fictional missions directory:
 
* [[Random failures scenario | Random failures]]
* [[Saturn 5 INT 20 scenario | Saturn 5 INT 20]]
* [[Apollo to Venus Phase A scenario | Apollo to Venus]]
* [[Saturn 1b Skylab scenario | Saturn 1b Skylab]]
* [[Apollo 2 scenario | Apollo 2 launch]]
 
 
== Documentation ==
 
As always, be sure to review documentation relevant to your mission. The [[:Category:Missions|Missions]] and [[:Category:Spacecraft|Spacecraft]] pages are good places to begin (work in progress).

Revision as of 14:50, 15 May 2024

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

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.

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.