Alain Capt

Apollo 8

This was the first mission to fly to the Moon. This mission didn't carry a LM. It was replaced by a "mass compensation structure". This is simulated in AMSO. Obviously, you won't be able to dock with this structure. The 3rd stage, at 8 minutes after separation, will maneuver and perform a main engine burn.
REMARK: You can fly the Apollo 7 mission with the same configuration. To do so, you just need to create the launch scenario.

Apollo 9

This mission tested the LM in Earth orbit. A space EVA was also performed. In AMSO, the CSM commands menu will allow you to start a space EVA, as soon as you have extracted the LM from the 3rd stage. The Commands menu will never display the autopilot commands in this mission. To understand the details regarding space EVA, please read the chapter, “SIM BAY INSTRUMENTS AND ACTIVITIES.” The difference here between the scenario and the space EVA described in this chapter is obviously that you won't have any film cassettes to retrieve. You can just enjoy the spectacle of the Earth under you. At the 3rd stage, 8 minutes after LM extraction, will maneuver and perform a main engine burn. You are not supposed to go to the Moon in this mission. In case you do it anyway, AMSO will configure itself for the Tranquility landing base, but your LM commands menu won't allow any PDI commands and you won't be able to perform a lunar EVA in the case of your landing in manual configuration.

Apollo 10

Apollo 10 was the general repetition of the historical following mission, Apollo 11. So it is very similar to it. The 3rd stage, 8 minutes after LM extraction, will maneuver and perform a main engine burn. AMSO will be configured for the Tranquility landing base, but your LM command menu won't allow any PDI commands and you won't be able to perform a lunar surface EVA in the event that you land in manual.

TIME ACCELERATION MANAGEMENT

The autopilot for both LM and CSM vessels manage time acceleration. It will not allow time acceleration, which is not suitable in the present phase. It will also automatically reset the time acceleration to 1x before the RCS attitude maneuvers and trajectory burns. Note that after this automatic reset to normal time, you may accelerate again if you wish, even during attitude maneuvers and trajectory control burns.

ATC sound engines also reset automatically time acceleration to 1x, 2 seconds before the next ATC sound will be played. If you re-accelerate the time while an ATC sound is playing, the play of this sound will be immediately aborted and the ATC engine will load the next sound to play. Of course, if this next sound is to be played in less than 2 seconds, the time acceleration will be again reset to 1x.
If the feature "Damage and Failure" is activated into the parameters section of the Orbiter "Launchpad" and such an event occur, time acceleration will be immediately reset to 1x. This let you the time to react to the event.
Be aware that you can have another vessel than the one you are actually controlling, who may limit the time acceleration for a certain period of time. It is the case, for example, when the 3^rd stage execute its burn after the separation from Apollo vessel, or when this same 3^rd stage try to intercept the Moon. This can also happen if both vessels you control (Apollo and LM) run an autopilot program in the same time.

AUTOPILOTS

The autopilot for Earth orbit insertion will bring you to a perfect circular orbit at the nominal altitude of 101.4 nm (187.7 km), for missions up to Apollo 14 and 90.0 nm (166,7 km) since Apollo 15. A small white label - "AP " - will appear on the left-bottom corner of the screen, when the autopilot is active. When this autopilots is engaged, any manual control commands, throttle change, engagement of any navigation modes like KILLROT, PROGRADE, etc…, will immediately disable the autopilot. It may also self-disable if it detects an anomaly in the trajectory. The autopilot, when it has been disabled, cannot be reactivated. This autopilot support 10x accelerated time, but it is not recommended.

REMARKS: ATTENTION!!! In Orbiter, a vessel’s attitude stability is sensitive to the frame rate you get. This is why, during flight phase under LM or CSM autopilot control, that the time acceleration control feature will NOT ALLOW time acceleration over 10x, IF YOUR FRAME RATE IS BELOW 40 FPS. Also be very careful when the vessel does attitude maneuvers or trajectory correction burns to not reaccelerate the time more than 10x. It’s better to wait until the maneuver has ended to try accelerating time if the higher ratio is allowed by this feature.

ATTENTION!!! In the case of both LM and CSM vessels running an autopilot program, you must NOT FORGET that you have two vessels managing the unique simulation time acceleration. So don't be surprised if suddenly the acceleration is reset to 1x or you cannot increase more than 10x. The other vessel is responsible for this! Also be very cautious with the 100x rate (see previous remark).

Note that ANY of the LM or CSM autopilot programs can be disengaged AT ANY TIME with the "K" Action key (the program is immediately stopped, and all thrusters cut). You will have to confirm the disengagement with the "Up" arrow key. Note that this action will be irreversible in many cases. So use it with caution.

CSM autopilot computer functions

These 3 programs are fictitious, but will really simplify your mission. They allow you to do orbital maneuvers which would otherwise be quite difficult to accomplish with standard Orbiter instruments. You can also use the “Check orbit>base alignment” query function, which will tell you the actual cross range with the landing site allowing you to decide if it is necessary to perform an orbit>base alignment.

P17 -> DOI insertion:

This program allows you to insert the full stack or even the CSM alone (which does not really make sense, but you can do it if you want to) on DOI elliptical orbit for lunar landing. Please note that this program DOES NOT align the orbit plane with the landing site.

P18 -> Orbit>base plane alignment:

This program allows you to align the orbit plane of the full stack or the CSM alone in order to make the orbit plane pass just over the landing site. If both planes are highly misaligned, this program will proceed in several steps, one at each of the orbit nodes. So you’ll get 2 corrections per orbit. ATTENTION!!! In the case of the orbit being totally wrong for the landing site, it may create a situation totally out of the vessel’s capacities, in particular for fuel requirements.

P19 -> Parking orbit circularization:

This program allows you to circularize orbit of the full stack or the CSM alone for the optimal Moon parking orbit altitude of 110 km for the rendezvous operation. This operation may require two distinct burns.

LM autopilot computer functions

An important preliminary remark is to mention that ASCENT of any kind (normal ascent or any ABORT ascent) and RENDEZVOUS operations rely ON A PASSIVE CSM target. Passive means that the CSM should avoid any LINEAR movements with attitude thrusters and obviously DO NOT modify its orbit with the main engine thruster, while the LM is doing ascent and rendezvous maneuvers. Rotation is allowed and will be useful late in the RENDEZVOUS stage, when you point your CSM noise in the direction of the incoming LM.

If the CSM breaks this rule while the LM is flying an ASCENT of any kind, the LM autopilot will finish creating a safe orbit and then stop.
If the CSM breaks this rule while the LM is flying a RENDEZVOUS, the LM autopilot will immediately abort the RENDEZVOUS operation.
--------------- PDI operation (Moon landing):
With the commands menu (“K” Action key), you can check for the validity of the PDI operation. The function "Check PDI conditions" will tell you if you are go for PDI. If you are not ‘go’, this function will tell you what is incorrect so you can use another program to make the necessary corrections. The function "Time to PDI," if you are go for PDI, will tell you the time remaining before the end of optimal time to engage PDI. Finally the PDI is activated with the "Engage PDI" function. Use the left/right arrow keys to select the desired function and the "up" arrow key to activate it.
This operation involves the following programs which very accurately simulate a real PDI.
P63 -> braking phase:

This is the start point of the PDI. Normally you should be already oriented more or less retrograde and looking down at the Moon’s surface. After about 3 minutes of braking, the program will automatically yaw the LM so that the windows look upward into space.

P64 -> Approach phase:

During this phase, the LM will first pitch down toward the Moon and then enter into the "CHANGE TARGET" mode. In virtual cockpit only, the view camera will lock on the planned landing site coordinates. A small green blinking dot can be seen in the center of the screen, which indicates the actual landing location. When you are in this mode, you can use the 4 arrows keys to choose another landing location. The blinking dot will immediately reflect the new position and stay locked on it. This "CHANGE TARGET" feature is real, but in reality the pilot used the graduations on the LM window to read the position of the landing site. You can change the landing location rather late in this phase. But at a certain point you will not see the indicator "CHANGE TARGET" anymore, which means you no longer can change the landing target, other than to switch to the manual landing program (see the following P66 section).

P65 -> landing phase:

When this program starts, the camera is automatically reset to the usual visual references. You also regain the control of the camera with the mouse, so have a look around if you wish. During this phase, the LM will finish aligning over the landing site and cautiously close the ground distance. At 1.70 meters altitude, the hovering engine will be cut off automatically and you will be landed on the Moon.

P66 -> Manual landing:

At any time during execution of P64 or P65, you can press either "Insert" or "Delete" to take the control of the LM. The camera will be immediately reset to the usual visual references. You also regain control of the camera with the mouse so you look around if you wish . The main task of P66 is to make the vertical speed independent of the LM attitude and keep it to the assigned value you can control with "Insert" (incr +1 ft/s), "Delete" (decr -1 ft/s) or "End" to set to zero. You control both lateral and longitudinal speeds, with pitch and bank commands (joystick recommended). Except if you apply your command while pressing the "Ctrl" key, when you cease to apply the command, the autopilot will automatically kill all the rotations. You can read on the screen "FwdV:" for the forward speed and "LatV:" for the lateral speed. A negative value means you’re moving backward, and laterally to the "port" side (left). The actual vertical speed & altitude is also displayed. Naturally, the automatic hovering engine is cut at about 1 meter altitude. Concerning the vertical axis, you just have to control the autopilot vertical speed setup and NEVER use direct engine thrust control commands. This is the program Neil Armstrong used to land the Eagle.

--------------- ABORT / ABORT-STAGE:
During all the PDI flight operations (when under control of the autopilot), you can press the "J" Action key to obtain a menu where using the left/right arrow key you may choose between:
P70 -> ABORTS:

This program will immediately stop the landing attempt and use the remaining descent stage fuel to try to rebuild an orbit suitable for a future emergency rendezvous with the CSM. In an early ABORT, the LM will probably be able to rebuild an orbit without exhausting all the descent stage fuel. In this case, when the orbit is built but before starting the "rendezvous" sequence of programs, the descent stage will be automatically jettisoned. In the case of exhausting the fuel supply before the end of the orbit injection, P71 will be immediately executed.

P71 -> ABORT-STAGE:

This program will immediately jettison the descent stage, and then with the ascent stage try to do the same as P70. Notice that at any time during the PDI operation if you run out of fuel with the descent stage, this program will be immediately executed.

Both P70 and P71 after having rebuilt an orbit will normally link automatically to the appropriate "rendezvous" sequence of programs (see following). But if the rendezvous is not possible the program will stop. If this happens, it means that you should correct some of the orbit parameters of the LM or the CSM in order to be able to engage the "rendezvous" operation (See following: POST-ABORTS auxiliary functions).
--------------- ASCENT operation (rendezvous):
With the commands menu, you should first check for the validity of the ASCENT operation. The function, "Check ASCENT conditions", will tell you if you are go for ASCENT. In case not, this function will tell you what is incorrect so you can switch to the CSM and use the appropriate program to correct the problem. The function "Time to ASCENT" (if you are go for ASCENT), will tell you the time remaining before the end of optimal time to engage ASCENT. Finally, engage the ASCENT with the "Engage ASCENT" function. Use left/right arrow keys to select the desired function and the "up" arrow key to activate it for all ASCENT operations.
P12 -> orbit insertion program:

This program will do the lift off countdown. Soon before launch, you will hear the historical Apollo 11 check list spoken by Neil Armstrong. Finally, you will hear Neil saying the last 9 seconds of the countdown and the ascent stage will lift off.

P3X + P4X -> rendezvous programs:

After the ascent stage reaches an orbit of approximately 20 km, two different sequences of programs may run, depending on whether you’re flying an Apollo mission previous to Number 14.

The sequences for Apollo 11 & 12 (or an imaginary successful 13) will reach the CSM during the second orbit of the ascent stage. The sequence for Apollo 14 and later missions flew direct rendezvous during the first ascent stage orbits.
The early flights sequences involve programs P32, P33, P34, P35 and P40
The later "direct" sequences involve P33 P34, P35 and P41.
There is not much to say about these programs, or to do while they run, except that you may decide to abort the sequence at any time with "K" Action key. The P32, P33, P34, P35 are all target-tracking programs. Your LM always aims right at your target, the CSM. If it has beacon lights ON, you should see the CSM from quite a distance. The P40 and P41 are programs that perform all trajectory corrections burns.
P36 -> fictitious approach/station/pre-docking program:

This program didn't exist in the reality of the Apollo program. The crew executed these tasks manually. So, if you want to respect reality, just use "K" key to abort P36 when it is activated. The pre-docking program handles the final approach of the rendezvous, then brakes toward the CSM, and finally turns the ascent stage so the docking port is aligned with the center of gravity of the CSM.

It is nice to let this program run, if you want to have the "show". You can switch from the LM to the CSM with the "M" key in order to appreciate the closing of both vessels. If it is night, you should see the beacon lights, if you switched them ON with “Ctrl-L”. The first time you switch to CSM, you will probably need to align the CSM with attitude rotations in order to point your windows in the direction of incoming ascent stage. Use the docking HUD to help you in this task.
Soon after reaching the "station", the LM will rotate and align its axis with the CSM. It will keep control of the axis for about 2 min, so you have enough time to align the CSM manually. When you are aligned, just wait until the end of P36, or abort it with the "K" Action key and do the docking manually with the CSM.

--------------- Pre-landing auxiliary functions:
These 3 programs are fictitious, but will really simplify your mission. They allow you to do orbital maneuver which would otherwise be quite difficult to accomplish with standard Orbiter instruments.
P17 -> DOI insertion:

This program allows you to insert the full stack, or the LM alone, on a DOI elliptical orbit for lunar landing. Please note that this program DOES NOT align the orbit plane (see P18 below).

P18 -> Orbit>base plane alignment:

This program allows you to align the orbital plane of the full stack, or the LM alone, to make the orbit plane pass directly over the landing site. If both planes are highly misaligned, this program will proceed in several steps at each of the orbit nodes. There will be 2 corrections per orbit during alignment. ATTENTION!!! Be warned of the possibility that the orbit may be totally wrong for the landing site, in which the mission may move outside of the vessel capacities, particularly for fuel requirements.

P19 -> Parking orbit circularization:

This program allows you to circularize the orbit of the full stack, or the LM alone, to the optimal Moon parking orbit altitude of 110 km for the rendezvous operation. This operation may require two distinct burns.

--------------- ABORT LUNAR OPERATIONS:
During your stay on the Moon, you may elect at any time to use the numeric keypad "ENTER" key to initiate an immediate ABORT MISSION lift off. The only prerequisite condition is obviously that both astronauts need to be on board! In this emergency procedure, the CSM’s position relative to the Moon base is ignored and the autopilot will engage the "ABORT-STAGE" program P71. Please refer to previous sections describing aborts during PDI operations to learn what will happen in this case.
--------------- POST-ABORTS auxiliary functions:
This menu is accessible only when the LM is operating in the ascent stage. You may need to use this menu in the event that an ABORT command wasn't able to perform a direct rendezvous sequence of programs. In this case, the abort program will stop when the orbit is built. These functions are also potentially life saving if you have disengaged the autopilot during any ABORTS or even during a normal ASCENT/RENDEZVOUS. It allows you to perform the following functions:
P16 -> engage orbit>orbit alignment:

This program allows aligning the LM’s orbital plane with the CSM’s orbit. You must have already built an orbit to be able to engage this program. If both planes are highly misaligned this program will proceed in several steps, at each node with the CSM’s orbit. There are 2 corrections per orbit.

P34 -> Engage RENDEZVOUS:

When both the LM’s and the CSM’s orbital planes are aligned you can engage this program. It will build a sequence of programs which will allow synchronizing the phase of both vessels and perform the rendezvous.

--------------- FULL STACK MANOEUVER auxiliary function:
P13 -> LM main engine delta-V burn:

The purpose of this program is to allow delta-V stabilized thrusts with the LM, without having to worry about the thrust axis translation.

This program is only available if you had the "PRESSURE NULL IN CRYO-TANK #2" malfunction event. When you press on the "K" key, you will be prompted to set a desired delta-V in meters per second for the burn. You can specify a negative delta-V to obtain a burn in the opposite direction. Increment/decrement the delta-V value with the "left/right" arrow keys. With the "Down" arrow key, you can toggle the incremental value between 0.5 or 10 m/s. The "Up" arrow key engages the burn program.
In Orbiter it is difficult to perform orbital maneuvers with a hovering vessel like the LM. This is because your main engine is not thrusting in the same Orbiter axis as conventional vessels. For example, this means that you cannot directly use the instruments’ indications to perform a prograde thrust. You will have to first orient the vessel prograde and then rotate 90 degrees to put your hovering engine on the prograde axis. If you consider this in conjunction with the fact that thrusting the full stack in this way is incredibly unstable, you begin to appreciate the help of this P13 program.
This is how to use this program. First orient the LM vessel as you would a standard vessel. This orientation will be the reference for the subsequent burn. Keep in mind that the burn will occur 180 seconds after you have engaged the program. As soon as engaged, the program will perform a precise axis translation to orient the hovering engine in the right direction, and will do the burn required to obtain the given delta-V while keeping LM’s orientation stable. The program may not run and return with the "Not enough fuel" error, in the event of insufficient fuel left to obtain the desired delta-V. At any time during the burn you may press the "K" Action key to disengage the program.
--------------- ERRORS MESSAGES:
This is the summary of the errors which can be produced by a running program. Most of them will probably occur as soon as you attempt to run a program in an inadequate situation. But it is also possible that a sequence of a program will terminate due to one or more of these abnormal situations.
- Unnecessary action

- Not enough fuel

- Target orbit off plane

- Vessel too far off plane

- Out of fuel

- Vessel not in orbit

- Target not in orbit

- CSM has broken rendezvous

You can find very interesting technical information about the LM & the CSM autopilots in the document written by the author "LazyD" included with the documentation.

SIM BAY INSTRUMENTS AND ACTIVITIES

Since the Apollo 15 mission, AMSO simulates the SIM bay compartment of the CSM.

Features of this simulation are:
- Jettison of the SIM bay panel

- The deployment of a sub-satellite

- The deployment or the stowing of magnetometer antennas

- Space EVA to retrieve film cassettes

The commands to activate these features can be found in the commands menu. These commands are managed dynamically. This mean commands are only seen when they can be used. For example, before you have jettisoned the SIM bay panel, you won't have any of the other mentioned commands. Note that this management wasn't done in a too restrictive of a way. For example, you will be able to start a space EVA as soon as the SIM bay is open and not only after you performed the TEI, as it was in reality. Refer to the "USAGE" chapter, to understand how to work the commands menu with the arrow keys.
Jettison of the SIM bay panel

This will simply detach the SIM bay panel from the side of the SM. The panel is slowly propelled away from the vessel, revealing the SIM bay with all its instruments represented in 3d.