[NASSP 8][Apollo 8] Realtime simulation Debriefing

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
As done with Apollo 7, in this thread I will do a debrief of the various Flight Days of Apollo 8, as flown on my recent real time simulation. I believe that this debriefs help users and provide feedback to the NASSP Team.

I considered the flight days as follows, on a different manner as on Apollo 7, and one that I believe is simpler:
  • FD1 (18/05/2022) GET -04:30:00 to GET 24:00:00
  • FD2 (19/05/2022) GET 24:00:00 to GET 48:00:00
  • FD3 (20/05/2022) GET 48:00:00 to GET 72:00:00
  • FD4 (21/05/2022) GET 72:00:00 to GET 96:00:00
  • FD5 (22/05/2022) GET 96:00:00 to GET 120:00:00
  • FD6 (23/05/2022) GET 120:00:00 to GET 144:00:00
  • FD7 (24/05/2022) GET 144:00:00 to GET 148:15:26
Flight day 1:
For the first 24 hours of mission, the following activities were scheduled:
  1. Backup Crew Prelaunch Procedure
  2. Prime Crew Prelaunch Procedure
  3. Saturn V Boost Procedure
  4. Post insertion checks and config
  5. TLI
  6. Transposition demo and S-IVB photography
  7. Evasive maneuver from S-IVB
  8. P23 runs with Earth Horizons
  9. MCC-1
  10. P23 runs with Earth Landmarks
  11. P23 runs with Earth Horizons
Backup crew prelaunch:
This procedure was, as always, started at T-4 hours. Word Checklist was followed, and a V35 was added after computer power up. Procedure was completed in 56 minutes and 6 seconds.

Prime crew prelaunch:
Procedure was started at T-2 hours and 40 minutes, following the Word Checklist. At T-1 hour, 39 minutes and 26 seconds, the hatch was closed, from the VC, by using the following clickspot:
giphy.gif


Saturn V Boost procedure:
First Saturn V to fly with a crew lifted off at 07:51:00 local time, and the boost procedure was done by following the Word Checklist. Cabin pressure decreased during first stage climbout. Tower jettison was a few seconds late. At 00:06:13 GET an RCS was fired by mistake, when performing the GPI test. SECO occured at 00:11:13 GET. Insertion data was as follows:
N62 VI +25558
N62 H DOT +00008
N62 H PAD +01036
N44 HA +01039
N44 HP +00998
N44 TFF -59 59

Post insertion checks and config:
Steps for post insertion were performed in the following order: Step 1, Step 5, Step 2, Step 3, Step 16, Step 4, Step 12 (just GDC Align to IMU), Step 7, Step 8, Step 9, step 11.
Steps 9, 10 and 11 were performed as able, while step 8 was completing. COAS was then installed, and then continued with step 6 and 12 (IMU realign, P52 option 3, stars 6 and 17). Checklist was continued at GET 01:31:45, with Step 13, after AOS and completed by 01:37:30 by performing step 17 and 15.
Data for step 13 was as follows (SCS ATT reference comparison check):
DSKY: +18009 +00047 +00052
ATT Set dials: 180.3 001 000.5

TLI:
PAD for TLI was received at 01:47:25 GET and was as follows:
TLI
02:40:44 TB6p
179 R
045 P
001 Y
5:17 BT
10499.0 DVC
35569 VI
357 R SEP
081 P SEP
002 Y SEP
TLI preparation checklist was started at 02:15:30 GET, by following the Checklist MFD.
S-IVB Ullage begun (reported) at 02:49:10 GET
S-IVB Restarted for TLI at 02:50:23 GET and burnt for 5 minutes and 17 seconds.
TLI Data is as follows:
N62 VI +35568
N62 H DOT +04749
N62 H PAD +01775

Transposition demo and S-IVB photography:
Preparation for S-IVB sep was started at 03:15:48 GET.
Separation from the S-IVB ocurred at 03:21:00 GET and the THC was used to command the separation. As on Apollo 7, a pitch up was obtained. Transposition was performed in AUTO mode and photos were taken from the S-IVB.

2022_s-ivb-1.png


2022_s-ivb-2.png


Evasive maneuver from S-IVB:
Maneuver around the S-IVB, in preparation for evasive maneuver started at 03:36:00 GET.

2022_s-ivb-3.png


Evasive maneuver was performed at 03:43:58 GET, applying -1.5 fps in the X axis.

2022_s-ivb-4.png


P23 runs with Earth Horizons:
The following P23´s were run starting at 04:20:00 GET.
Star 14 ENH, Star 15 EFH and Star 16 EFH.
Results are as follows
+00047
+00142
---------
+00003
+00009
+00014
+00037
---------
+00010
+00024
+00024
+00052
MCC-1:
MCC-1 was scrubbed, maybe because of the RCS hotfire at 00:06:13 GET, or the sneeze at 04:51:12 GET.
Crew took a power NAP from 08:07:00 GET to 08:33:00 GET.

P23 runs with Earth Landmarks:
The following P23´s were run starting at GET 09:11:00
Star 15 and 16, Earth Landmark 10 (Punta Yoyameko)
Landmarks could not be seen on Earth, despite being enabled. Maybe because of the distance from Earth Surface?
Results are as follows:
+00326
+00108
---------
+00626 (bad)
+00202 (bad)
---------
+00184
+00058
+00333
+00095
---------
+00353
+00099

Trajectory de-correction:
It was determined that as MCC-1 was scrubbed, because trajectory was very nice, if MCC-2 got also scrubbed a bug may occur and MCC would "break", so a decorrection was needed to force MCC-2.
At GET 17:00:44 a +X burn with translation was performed at 0,0,0 attitude, and 1 fps Delta V

Rest periods:
The first sleep period of the mission was started at 13:30:00 GET and finished at 16:15:00
Next "sleep" period started at 18:30:00 GET and finished at 20:40:00 GET.
Next "sleep" period started at 21:10:00 GET.

P23 runs with Earth Horizons:
To conclude FD1, the following P23´s were run starting at GET 17:20:00:
Star 22 EFH and Star 16 EFH.
Results are as follows
+00779 (Bad)
+00107 (Bad)
-----------
+01180 (Bad)
+00161 (Bad)
-----------
+00922 (Bad)
+00126 (Bad)
-----------
+00834 (Bad)
+00113 (Bad)

P23 run discarded (Star 22 EFH)
+02612 (Bad)
+00426 (Bad)
------------
+01032 (Bad)
+00167 (Bad)

P23 run discarded (Star 16 EFH)
 
Last edited:

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
Flight day 2:
Second flight day of the mission started at 24:00:00 GET, while crew was sleeping, and consisted on the following activities:
  1. P23 runs with Earth Horizons (FD2 I)
  2. MCC-2
  3. P23 runs with Earth Horizons (FD2 II)
  4. First TV transmission
  5. P23 runs with Earth Horizons (FD2 III)
  6. P23 runs with Lunar Horizons (FD2 IV)
  7. MCC-3
  8. P23 runs with Earth Horizons (FD2 V)
P23 runs with Earth Horizons (FD2 I):
Crew woke up from the sleep period at 24:45:00 GET, and after that took breakfast and started a P23 run at 26:15:00 GET.
Star 16 EFH, Star 22 EFH and Star 26 ENH. Results are as follows:
+02592 (bad)
+00267 (bad)
----------------
+02617 (bad)
+00268 (bad)

P23 run discarded (Star 16 EFH)
+00682 (bad)
+00044 (bad)
---------------
+00733 (bad)
+00047 (bad)

P23 run discarded (Star 22 EFH)
+00173
+00017

MCC-2:
PAD for MCC-2 was obtained,
giphy.gif

and was as follows:
MCC-2 PURPOSE
SPS/G&N PROP/GUID
+63519 WT N47
-001.52 PTRIM N48
+001.27 YTRIM
+00027 HRS GETI
+00055 MIN N33
+043.06 SEC
+0005.0 DVX N81
-0002.0 DVY
+0001.2 DVZ
175 R
214 P
338 Y
NA HA N44
+0120.2 HP
+0005.5 DVT
0:01 BT
0000.9 DVC
02 SXTS
+209.90 SFT
+13.200 TRN
012 BSS
-02.8 SPA
+0.4 SXP
N/A LAT N61
N/A LONG
N/A RTGO EMS
N/A VIO
N/A GET .05G
Deneb, Vega SET STARS
037 R ALIGN
077 P ALIGN
036 Y ALIGN
Remarks: Requires MCC1 and 3/4
Burn was performed using SPS at GET 27:55:43. Burn duration was 1 second. Residuals as follows:
+00002
+00001
+00001
Not nulled as per mission rules.

SPS Oxid and fuel were 99.4% and no unballance after MCC2. No ullage was used.

P23 runs with Earth Horizons (FD2 II):
Next P23 run was started at 28:15:50 GET.
Star 16 EFH, Star 22 EFH, Star 21 EFH and Star 26 ENH. Results are as follows:
+00538 (bad)
+00050 (bad)
---------------
+03028 (bad)
+00283 (bad)

P23 run discarded (Star 16 EFH)
+00304
+00027
+00101
+00009
+00022
+00002

Rest period:
Crew took a power nap between 30:41:00 GET to 31:05:00 GET.

First TV transmission:
A TV broadcast was started at 31:15:25 GET and finished at 31:30:32 . Transmission was via OMNI D. Crew did a little cabin tour on this transmission, and a planet was shown, maybe Venus.

Rest period:
Crew took a NAP between 31:32:00 GET and 33:40:00 GET.

P23 runs with Earth Horizons (FD2 III):
Next P23 runs started at 34:20:00.
Star 16 EFH, Star 22 EFH and Star 26 ENH. Results are as follows:
+00310 (bad)
+00024 (bad)
---------------
+00513 (bad)
+00039 (bad)
---------------
+00259
+00020
+00051
+00003
+00556 (bad)
+00042 (bad)
---------------
+00246
+00019

PTC Management:
PTC was interrumpted and restarted because spacecraft was close to the area of Gimbal Lock. Interruption was performed at 37:20:00 GET and PTC was restarted at 37:48:50 GET with 0.5º deadband on the DAP, and 2 jets on the roll.

Rest period:
Crew started an sleep cycle from GET 38:06:00 to GET 43:30:00.

P23 runs with Lunar Horizons (FD2 IV):
Next P23 runs, and first ones on Lunar Horizons were started at 44:40:00
Star 33 LNH, Star 37 LNH, Star 45 LFH and Star 42 LFH. Results are as follows:
+00735 (bad)
+00043 (bad)
---------------
+01260 (bad)
+00074 (bad)
----------------
+02146 (bad)
+00125 (bad)

P23 run discarded (Star 33 LNH)
+01311 (bad)
+00076 (bad)
----------------
+11490 (bad)
+00662 (bad)
----------------
+00998 (bad)
+00057 (bad)

P23 run discarded (Star 37 LNH)
+00937 (bad)
+00054 (bad)
----------------
+00984 (bad)
+00057 (bad)

P23 run discarded (Star 45 LFH)
+02220 (bad)
+00126 (bad)
---------------
+00486
+00027

MCC-3:
MCC-3 burn was scrubbed.

Rest period:
Crew took a NAP from 46:22:00 GET to 47:08:00 GET.

P23 runs with Earth Horizons (FD2 V):
Next P23 runs, back on Earth Horizons, started at 47:16:00.
Star 16 EFH, Star 22 EFH and Star 26 ENH. Results are as follows:
+01894 (bad)
+00105 (bad)
----------------
+01728 (bad)
+00095 (bad)
----------------
+01884 (bad)
+00104 (bad)

P23 run discarded (Star 16 EFH)
+00442
+00024
+00015
+00001
 
Last edited:

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
Flight day 3:
Flight day 3 started at 48:00:00, with the crew awake, and consisted on the following activities:
  1. P23 runs with Lunar Horizons
  2. Second TV transmission
  3. MCC-4
  4. LOI Preps
  5. LOI-1
  6. CP Sighting thru hatch window
  7. Third TV Transmission
NAP Period:
Crew took the first NAP period for FD3 between 49:34:00 and 51:01:00. This NAP was not scheduled on the plan, but took it as it was going to be required for the 26ish hours of continuous activity for the "Lunar Day".

P23 runs with Lunar Horizons:
A P23 run was started at 52:17:32 GET. This will be the last P23 runs on the "Going" journey.
Star 37 LNH, Star 33 LNH. Results are as follows:
+01725 (bad)
+00086 (bad)
----------------
+01435 (bad)
+00072 (bad)
----------------
+00316
+00016
+01343 (bad)
+00067 (bad)
----------------
+01186 (bad)
+00059 (bad)
----------------
+01194 (bad)
+00059 (bad)

P23 run discarded (Star 33 LNH)

Power NAP:
Crew took a power nap between GET 53:59:00 and 54:23:00. Also, not planned, but took the chance.

Second TV transmission:
Second TV transmission was started at 55:15:57 and completed at 55:31:16 GET.
Earth was shown, South America, Antarctica and Hawaii was visible, but crew had some difficulty identifying it. Transmission was via Omni D antenna.

NAP Period:
Crew took a NAP between 56:08:00 to 58:32:00. This NAP period was planned.

MCC-4:
PAD for MCC-4 was obtained, and was as follows:
MCC-4 PURPOSE
RCS/G&N PROP/GUID
+63441 WT N47
+000.00 PTRIM N48
+000.00 YTRIM
+00061 HRS GETI
+00006 MIN N33
+016.58 SEC
+0000.0 DVX N81
+0000.3 DVY
+0000.6 DVZ
262 R
045 P
023 Y
NA HA N44
+0122.5 HP
+0000.6 DVT
0:03 BT
0000.6 DVC
36 SXTS
+320.90 SFT
+10.900 TRN
N/A BSS
N/A SPA
N/A SXP
N/A LAT N61
N/A LONG
N/A RTGO EMS
N/A VIO
N/A GET .05G
Deneb, Vega SET STARS
253 R ALIGN
342 P ALIGN
016 Y ALIGN
Remarks: None
Burn was performed using RCS at GET 61:06:17. Burn duration was 3 seconds. Residuals as follows:
+00004
-00000
+00001
Residuals were nulled. Average propellant on the RCS quads after the burn was 360 lbs.

Rest period:
Crew took an sleep period between 62:00:00 and 65:52:00 GET. This sleep period was planned.

LOI Preps:
LOI Preparations were started at GET 67:00:00, starting with the maneuver to LOI-1 attitude by using the RHC. Then, various systems checks were performed. LOI preps were completed at 67:30:00 GET

Power NAP:
Crew took the chance to take a non scheduled power nap between 67:31:30 to 67:47:20 GET.

LOI-1:
PAD for LOI-1 was obtained, and was as follows:
LOI-1 PURPOSE
SPS/G&N PROP/GUID
+63426 WT N47
+001.51 PTRIM N48
+001.27 YTRIM
+00069 HRS GETI
+00006 MIN N33
+025.39 SEC
-2977.5 DVX N81
+0248.9 DVY
+0133.1 DVZ
000 R
191 P
005 Y
+0170.0 HA N44
+0060.0 HP
+2990.8 DVT
4:09 BT
2975.4 DVC
02 SXTS
+234.50 SFT
+22.500 TRN
N/A BSS
N/A SPA
N/A SXP
N/A LAT N61
N/A LONG
N/A RTGO EMS
N/A VIO
N/A GET .05G
Deneb, Vega SET STARS
253 R ALIGN
342 P ALIGN
016 Y ALIGN
Remarks: None
Burn was performed using SPS at GET 69:06:25. Burn duration was 4 minutes, 10 seconds. Residuals as follows:
-00006
+00001
+00001
Not nulled as per LOI Cue Card.

Orbit after shutdown was 169.6 by 60.0 nm.

SPS Oxid and fuel were 59.5% and no unballance after LOI-1. No ullage was used.

CP Sighting thru hatch window & Third TV transmission:
Control points were looked at through the hatch window, at the end of revolution 1 and beginning of revolution 2 around the Moon Other windows were used for CP / Landmark identification, as windows 1 and 4. The Third TV transmission and first one from the Moon, was started at GET 71:41:15, with a high workload. It was hard for the crew to keep the Ordeal attitude of 45º yaw while the TV transmission was running, as the crew was trying to show the Moon. Crew described lunar landscape as "Unforgiving".

1654971207869.png


Transmission ended at 71:51:00.
 

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
Flight day 4:
Flight day 4 started at 72:00:00, with the crew awake, and consisted on the following activities:
  1. LOI-2
  2. Training Photography pseudo landing site
  3. Landmark Lighting Evaluation (pseudo landing site)
  4. P22 tests during lunar revolution 5: P22 CP Sighting with manual optics and P22 pseudo landing site sighting with auto optics
  5. P22 tests during lunar revolution 6: P22 CP Sighting with auto optics and P22 pseudo landing site sighting with auto optics
  6. P22 tests during lunar revolution 7: P22 CP Sighting with both auto and manual optics, and P22 pseudo landing site sighting with auto optics
  7. P22 tests during lunar revolution 8: P22 CP Sighting with both auto optics, and P22 pseudo landing site sighting with auto optics
  8. Fourth TV Transmission
  9. TEI Preps
  10. TEI
  11. P23 runs with Lunar Horizons
Power NAP:
Flight day 4 started with the crew taking a chance to take a power NAP starting from 72:01:00 to 72:16:00 GET. Crew felt better after that.

LOI-2:
Lunar orbit circularization burn (LOI-2) was burnt using the following PAD:
LOI-2 PURPOSE
SPS/G&N PROP/GUID
+47164 WT N47
+000.40 PTRIM N48
+001.17 YTRIM
+00073 HRS GETI
+00028 MIN N33
+028.42 SEC
-0136.2 DVX N81
+0000.0 DVY
+0000.0 DVZ
000 R
179 P
358 Y
+0060.5 HA N44
+0060.0 HP
+0136.2 DVT
0:10 BT
0127.5 DVC
02 SXTS
+271.60 SFT
+15.400 TRN
N/A BSS
N/A SPA
N/A SXP
N/A LAT N61
N/A LONG
N/A RTGO EMS
N/A VIO
N/A GET .05G
Deneb, Vega SET STARS
253 R ALIGN
342 P ALIGN
016 Y ALIGN
Remarks: None
Burn was performed using SPS at 73:28:30 GET. Burn duration was 10 seconds. Residuals are as follows:
-00002
-00005
+00007
Not trimmed as per LOI Cue Card.

Orbit after shutdown was 60.7 by 60.0 nm.
SPS Oxid and fuel were 58.0% and no unballance after LOI-2. No ullage was used.

Training Photography pseudo landing site:
An observation pass over the future landing site was started around 74:10:00 GET. Some land features were identified. Pitch up for training photography was started at 74:12:55. Pictures were taken:
14_b1_1.png

15_b1_2.png

16_b1_3.png

Landing site was identified and pitch up was stopped at 74:17:30 GET.

Landmark Lighting Evaluation (pseudo landing site):
At 76:05:10 GET, P22 was started to perform the landmark lighting evaluation, over the Pseudo landing site.
RTCC MFD´s landmark tracking PAD feature was used for all the P22 runs, as on Apollo 7, as information there is very helpful.
Landing site was dark, was right on the terminator. 407 program alarm was triggered, but was ignored as of this test. Pass over the landing site ocurred approximately at 76:12:00.

P22 tests during lunar revolutions 5, 6, 7, 8:
For the next 4 revolutions, Apollo 8 performed various series of P22 tests. On the RTS recording, these tests start here:
Results are as follows:
Revolution 5:
CP2 manual optics
Pitch down started at 77:30:18 GET
Pitch down stopped at 77:32:20 GET
N49: +00032
+00016
N89: -12648
+76545
+00002
---------------------------
Pseudo Landing Site
Pitch down started at 78:09:37 GET
Pitch down stopped at 78:13:00 GET
Program alarm 122 (marking not called for) was obtained. Crew must have made a mistake, maybe forgot a step or went too fast.
P22 run for Pseudo Landing Site was discarded
Revolution 6:
CP2 auto optics
Pitch down started at 79:28:20 GET
Pitch down stopped at 79:30:09 GET
N49: +00023
+00123
N89: -10200
+77550
-00000
-------------------------
Pseudo Landing Site:
Pitch down started at 80:07:49
Pitch down stopped at 80:09:45
N49: +00004
+00014
N89: +02632
+17013
-00082
Revolution 7:
CP1 manual optics
Pitch down was started at 81:13:00 GET
Pitch down was stopped at 81:14:50 GET
N49: +00001
+00025
N89: -06062
-81415
-00007
--------------------------
CP2 auto optics:
Pitch down was started at 81:26:43
Pitch down was started at 81:28:36
N49: +00004
+00019
N89: -10200
+77550
-00000
-----------------------------
CP3 manual optics
Pitch down was started at 81:45:57
Pitch down was stopped at 81:48:05
N49: +00008
+00080
N89: -09277
+48001
-00013
------------------------------
Pseudo landing site:
Pitch down was started at 82:06:43
Pitch down was stopped at 82:08:56
N49: +00003
+00017
N89: +02632
+17013
-00082
Revolution 8:
CP1 Auto Optics:
Pitch down was started at 83:11:25 GET
Pitch down was stopped at 83:13:18 GET
N49: +00002
+00012
N89: -05250
-81350
---------------------
CP2 Auto Optics:
Pitch down was started at 83:25:12
Pitch down was stopped at 83:26:56
N49: +00001
+00010
N89: -10200
+77550
-00000
-------------------
CP3 Auto Optics:
Pitch down was started at 83:44:27
Pitch down was stopped at 83:46:26
N49: +00000
+00005
N89: -091000
+47950
-00000
---------------------
Pseudo landing site:
Pitch down was started at 84:04:42
Pitch down was stopped at 84:06:53
N49: +00000
+00001
N89: +02632
+17013
-00082

Fourth TV Transmission:
After the crew took dinner, on Revolution 9, another TV transmission, and the second from the moon, was started at 85:45:35 GET. During this transmission, crew had a better chance to describe the lunar landscapes, wich again were described as unforgiving, and also took the chance to celebrate Christmas´s eve with all the people back on Earth. To end the transmission, as the Apollo 8 spacecraft was passing over the future landing site, crew read the first 10 verses from the Genesis book on the Bible. I did the same, based on the mission transcripts:
1656063496672.png


















I made a misreading mistake at verse 5. I corrected reading that again, sorry for that :( . It felt really bad to had made that mistake.
Transmission ended at 86:09:15 GET. I felt proper to go historical and don´t do something new, too creative or different :)


TEI Preps:
TEI preparations started at 87:15:00, with previously having the IMU and GDC alignment. Attitude check was first performed at this time.
During preparations, it was observed that the "Pitch Thumbweel" on the Attitude Set Panel stopped working on the VC.
P30 was started at 88:35:12 GET, concluding after its completion with the TEI preparation checks.

TEI:
Trans Earth Injection burn was performed via the following PAD:
TEI-10 PURPOSE
SPS/G&N PROP/GUID
+46446 WT N47
-000.37 PTRIM N48
+001.14 YTRIM
+00089 HRS GETI
+00016 MIN N33
+004.21 SEC
+3517.1 DVX N81
-0149.3 DVY
-0118.2 DVZ
180 R
358 P
000 Y
N/A HA N44
+0060.3 HP
+3522.2 DVT
3:29 BT
3504.9 DVC
37 SXTS
+326.50 SFT
+13.000 TRN
N/A BSS
N/A SPA
N/A SXP
+007.47 LAT N61
-165.00 LONG
+1261.4 RTGO EMS
+36314 VIO
146:48:42 GET .05G
Deneb, Vega SET STARS
253 R ALIGN
342 P ALIGN
016 Y ALIGN
Remarks: Ullage; 15 seconds, 4 jets
Burn was performed at GET 89:16:05 GET. Another mistake was done, as ullage was forgotten; however, SPS engine was not required again for the rest of the mission. Burn duration was 3 minutes and 29.5 seconds. Residuals were as follows:
-00010
+00006
-00001
Residuals were not zerored, as per mission rules.
SPS Oxid and fuel were 24.4% and no unballance after LOI-2. Ullage was forgotten.

After TEI, some pictures of the moon were taken:
27_bye_bye.png


27_bye_bye_3.png


The pitch "thumbwheel" on the Attitude Set Panel worked again after TEI.

P23 runs with Lunar Horizons:
To conclude the fourth flight day, the first P23 series on the "coming" journey was performed. This was started at 90:30:00 GET.
Star 01 LNH, Star 02 LNH, Star 10 LFH, Star 11 LFH. Results are as follows:
+00003
+00009
+00006
+00018
+00002
+00005
+00001
+00003

After performing a series of housekeeping procedures on the CM, the crew finally went to sleep at 91:51:00, for a 4 hour sleep period.
 
Last edited:

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
Flight day 5:
Flight day 5 started at 96:00:00, with the crew waking up 8 minutes later. Crew reported a good feeling after sleep, Flight Day 5 consisted on the following activities:
  • P23 runs with Lunar Horizons
  • P23 runs with Earth Horizons
  • MCC-5
  • Fifth TV transmission
  • P23 runs with Earth Horizons
  • P23 runs with Lunar Horizons
  • P23 runs with Earth Horizons
First activity of the day consisted in a P52 and GDC align performed between 96:10:00 and 96:18:00 GET. Then, crew take a chance to take a rest periods, and various would be taken on this day; remember that sleep schedules on Apollo 8 were very weird, so needed to take any chance to have sleep.

Rest periods:
Crew took the following rest periods during FD 5:
  • 96:40:00 to 97:58:00 GET (NAP)
  • 98:00:00 to 99:52:00 GET (Sleep)
  • 109:56:00 to 114:46:00 (Sleep)
  • 116:22:00 to 118:40:00 (Sleep) Something weird happened here with the alarm clock, and crew woke up at 119:41:00.
P23 runs with Lunar Horizons:
A P23 run was started at 100:31:15 GET.
Star 02 LNH, Star 11 LFH, Star 01 LNH; results were as follows:
For the first run, Earth was on the optics, instead of Moon. When running P23 again, the codes shown at F V 05 N 70 were bad, so the codes were entered again. What happened was that on the first run, V25 was introduced to enter the codes, but for R3 the data input was not completed by mistake, and the crew continued with PRO without completing V25 data input.
+00003
+00001
+00099
+00015
---------
+00055
+00009
+00102
+00016

P23 runs with Lunar Horizons:
A P23 run was started at 101:31:37 GET.
Star 22 EFH, Star 26 ENH, Star 31 ENH; results are as follows:
+00064
+00010
+00052
+00008
+00615
+00096
---------
+00109
+00017

MCC-5:
PAD for MCC-5 was received, and was as follows:
MCC-5 PURPOSE
RCS/G&N PROP/GUID
+32752 WT N47
+000.00 PTRIM N48
+000.00 YTRIM
+00104 HRS GETI
+00016 MIN N33
+004.15 SEC
+0003.9 DVX N81
+0000.0 DVY
+0000.2 DVZ
180 R
150 P
359 Y
NA HA N44
-0304.3 HP
+0003.9 DVT
0:10 BT
0003.9 DVC
01 SXTS
+103.10 SFT
+20.500 TRN
013 BSS
-00.2 SPA
+8.5 SXP
+007.48 LAT N61
-165.00 LONG
+1261.4 RTGO EMS
+36314 VIO
146:48:50 GET .05G
Deneb, Vega SET STARS
072 R ALIGN
013 P ALIGN
337 Y ALIGN
Remarks: None
Burn was performed using RCS at GET 104:16:04. Burn duration was 3 seconds. Residuals as follows:
+00002
+00001
-00001
Residuals were not nulled, as per mission rules. Average propellant on the RCS quads after the burn was 320.5 lbs.

Fifth TV transmission:
The first TV transmission after the stay on the moon was started at 104:22:10 and completed at 104:29:24 GET.
Earth was shown.

P23 runs with Earth Horizons:
Another series of P23 was started at 105:16:10.
Star 22 EFH, Star 26 ENH, Star 31 ENH; results are as follows:
+00179
+00022
---------
+00045
+00005
+00073
+00009
+00284
+00033
---------
+00221
+00026

P23 runs with Lunar Horizons:
P23 was started at 106:15:56 GET
Star 02 LNH, Star 11 LFH, Star 01 LNH; results are as follows:
+00034
+00004
+00123
+00014
+00056
+00006

P23 runs with Earth Horizons:
P23 was started at 107:38:00 GET, for the last P23 run of the day.
Star 22 EFH, Star 26 ENH, Star 31 ENH; results are as follows:
+00057
+00006
+00068
+00007
+00244
+00025
---------
+00092
+00009

Gimbal lock situation:
While on PTC, and during the crew´s sleep period, the spacecraft entered the Gimbal Lock area at 113:51:40 GET, and the platform was lost at 114:25:16 GET (NO ATT light). Crew woke up at 114:47:00 and saw the problem. Crew wake up was intended to interrupt the PTC, perform a P52 option 3 realignment as platform maintenance, GDC align and resume the PTC and go back to sleep for another 2 hours and 40 minutes. Instead, platform recovery had to be performed. The following was done:
  1. First action was to try to maneuver outside of the Gimbal Lock area at 114:47:40 GET.
  2. After asking for help, idea was to align the IMU to the GDC; the following was done:
    1. IMU Cage switch switched on at 114:59:34 GET.
    2. Maneuver spacecraft, watching GDC, out of the Gimbal lock region. GDC attitude at 115:00:57 was R 096 P 260 Y 306. However, question was that if we had a good GDC.
    3. Maneuver to GDC 0,0,0 starting at 115:06:45 and finishing at 115:16:30 GET.
    4. Go to SCS ATT HOLD.
    5. IMU Cage switch OFF at 115:37:45 GET.
    6. Perform a run of P51 IMU orientation. Stars used were 42 and 37.
    7. Perform a run of P52 option 3. Stars used were 41 and 42. Score was 00001.
    8. Perform GDC align to IMU.
 
Last edited:

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
Flight day 6:
Flight day 6 started at 120:00:00, with the crew waking up at 119:41:00 GET, 1 hour and 1 minute behind schedule, due to an issue with the alarm clock (bad programmed or just didn´t hear it and was sounding for 61 minutes :p ). Flight Day 6 consisted on the following activities:
  • P23 runs with Earth Horizons
  • MCC-6
  • P23 runs with Lunar Horizons
  • P23 runs with Earth Horizons
  • Sixth and last TV transmission
  • P23 runs with Lunar & Earth Horizons
  • Preliminary MCC-7 PAD
Rest periods:
Crew took the following rest periods during FD 6:
  • 135:56:10 to 138:42:00 (sleep)
  • 139:59:30 to 141:06:30 (Sleep-NAP)

P23 runs with Earth Horizons:
A series of P23 was started at 119:45:04.
Star 22 EFH, Star 26 ENH, Star 31 ENH; results are as follows:
+00065
+00004
+00086
+00006
+00070
+00004
"Just a straight thing!":
1658576555378.png


MCC-6:
MCC-6 burn was scrubbed.

P23 runs with Lunar Horizons:
Another series of P23 was started at 122:36:27
Star 02 LNH, Star 01 LNH; results are as follows:
+00068
+00004
+00013
+00001

P23 runs with Earth Horizons:
Another series of P23 was started at 123:24:25
Star 22 EFH, Star 26 ENH, Star 31 ENH; results are as follows:
+00051
+00003
+00043
+00003
+00012
+00001

REFSMMAT status discussion:
At around 125:07:00 GET a debate about REFSMMAT status after the Gimbal Lock situation on the last night was done. Crew felt that the onboard platform was aligned properly, instructions were given to calculate a new REFSMMAT using RTCC MFD. Actions taken for recovery from Gimbal Lock were talked about with the new shift of MCC controllers. As when doing the GDC align last night, there were no big changes in attitude, no new REFSMMAT was uplinked to the CSM. It was confirmed that everything was fine. However, PTC was very carefully monitored to avoid another gimbal lock and try to understand what happened last night.

Sixth and last TV transmission:
A TV broadcast was started at 128:01:35 GET and finished at 128:13:18 . Transmission was via OMNI D. Earth was shown, and it was the best view of Earth through TV transmission on the mission South America and Antarctica were identified. Also a cockpit tour was done. (Crew said two times that the FC´s provided hydraulic pressure to the spacecraft)

1658581440786.png


P23 runs with Lunar & Earth Horizons:
New REFSMMAT was uplinked as discussed with MCC earlier, at 129:36:58. P52 option 1 was performed. It was determined that IMU was off by 2º. P52 option 1 score was +00000. GDC was aligned to IMU.
P23 run was started at 129:55:33. Star 02 LNH. Results are as follows:
+00077
+00005
P23 run was started at 130:06:53. Star 22 EFH, Star 26 ENH, Star 31 ENH; results are as follows:
+00108
+00006
+00002
+00000
+00065
+00002

Preliminary MCC-7 PAD:
At 131:48:22 the following Preliminary MCC-7 PAD was obtained:
MCC-7 PURPOSE
RCS/G&N PROP/GUID
+32690 WT N47
+000.00 PTRIM N48
+000.00 YTRIM
+00144 HRS GETI
+00048 MIN N33
+018.91 SEC
-0002.2 DVX N81
+0000.0 DVY
+0000.1 DVZ
000 R
304 P
000 Y
NA HA N44
+0021.0 HP
+0002.2 DVT
0:06 BT
0002.2 DVC
45 SXTS
+045.90 SFT
+22.800 TRN
NA BSS
NA SPA
NA SXP
+007.46 LAT N61
-164.98 LONG
+1261.5 RTGO EMS
+36314 VIO
146:48:46 GET .05G
Deneb, Vega SET STARS
072 R ALIGN
013 P ALIGN
337 Y ALIGN
Remarks: None
 

Attachments

  • 1658581361988.png
    1658581361988.png
    249.3 KB · Views: 20
Last edited:

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
Flight day 7:
Flight day 7 started with a awake crew at 144:00:00, and consisted in the following activities:
  • MCC-7
  • Entry preparations
  • Lunar entry
  • Post splashdown & crew egress
Change from FD-6 to FD-7:
PAD for MCC-7 was obtained at 143:18:30 and was as follows:
MCC-7 PURPOSE
RCS/G&N PROP/GUID
+32684 WT N47
+000.00 PTRIM N48
+000.00 YTRIM
+00144 HRS GETI
+00048 MIN N33
+018.65 SEC
-0002.4 DVX N81
+0000.0 DVY
+0000.2 DVZ
000 R
304 P
000 Y
NA HA N44
+0021.0 HP
+0002.4 DVT
0:06 BT
0002.4 DVC
45 SXTS
+046.30 SFT
+22.600 TRN
NA BSS
NA SPA
NA SXP
+007.46 LAT N61
-164.98 LONG
+1261.5 RTGO EMS
+36314 VIO
146:48:46 GET .05G
Deneb, Vega SET STARS
072 R ALIGN
013 P ALIGN
337 Y ALIGN
Remarks: None

A preliminary Lunar entry PAD was obtained at 143:23:25

LUNAR ENTRY
MIDPAC AREA
XXX000 R .05G
XXX152 P .05G
XXX000 Y .05G
146:31:19 GET HOR CK
XXX268 P
+007.46 LAT N61
-164.98 LONG
XXX06.5 MAX G
+36226 V400K N60
-006.51 T400K
+1264.8 RTOGO EMS
+36307 VIO
146:48:19 RRT
XX00:28 RET 0.05G
XXX4.00 D0
XX02:08 RET Vcirc
XX00:25 RETBBO
XX03:30 RETEBO
XX08:30 RETDRO
XXXX22 SXTS
+158.60 SFT
+13500 TRN
XXX013 BSS
XX-01.7 SPA
XXX-9.6 SXP
XXXXUP LIFT VECTOR
Remarks: Assumes MCC-7

MCC-7:
Burn was performed using RCS at GET 144:48:20. Burn duration was 6.5 seconds. Residuals as follows:
+00003
+00000
+00000
Residuals were nulled.

Entry preparations:
As steps for Entry Preparations, the following was performed:
  1. CMC Self Check at GET 144:51:40. Successful and complete at 144:55:30.
  2. V35 performed at GET 144:55:45. Successful.
  3. Maneuver to entry attitude at 144:57:25. Maneuver complete at 145:01:55. Attitude check successful at 145:02:15
  4. P52 IMU realign with Option 3 (145:12:00) and GDC Realign.
CM RCS preheat started at 145:21:41, and was required because Systems Test 6C showed 2.5V. Preheat was complete at 145:40:22, meanwhile, EMS Entry test was performed (successful).
Cabin cold soak was activated at 145:40:55 GET.
CM RCS Hotfire was performed at 145:46:35 (Ring 1) and 145:46:55 (Ring 2). Successful.
Final Entry PAD was obtained at 146:03:20 and was as follows:
LUNAR ENTRY
MIDPAC AREA
XXX000 R .05G
XXX152 P .05G
XXX000 Y .05G
146:31:19 GET HOR CK
XXX268 P
+007.46 LAT N61
-164.98 LONG
XXX06.6 MAX G
+36226 V400K N60
-006.52 T400K
+1265.9 RTOGO EMS
+36307 VIO
146:48:19 RRT
XX00:28 RET 0.05G
XXX4.00 D0
XX02:08 RET Vcirc
XX00:25 RETBBO
XX03:29 RETEBO
XX08:30 RETDRO
XXXX22 SXTS
+158.60 SFT
+13.500 TRN
XXX013 BSS
XX-01.7 SPA
XXX-9.6 SXP
XXXXUP LIFT VECTOR
Remarks: None
Everything was running smoothly, until the crew got confused around 146:12:00 GET when performing the GDC align and RSI checkout, because since Entry Interface -1.5 hours, the spacecraft was drifting instead of holding the entry attitude. However, GDC alignment was complete, but crew was nervous after this, hoping that the attitude was correct. Crew saw that there was a pitch rate, witch indicated what haappened, and started maneuvering back to entry attitude at around 146:17:00 GET. This time, spacecraft was left on CMC HOLD.

Lunar entry:
Horizon check was performed at 146:31:23. Successful!
CM/SM Sep occured at 146:33:20.
Crew described that the wait period for waiting to EI was very tense and strefull. On simulations it was not like that.
Entry interface was reached at 146:48:20. Max G for "first" reentry was 6.5G. Max G for "second" reentry was around 5.7G.
Drogue chutes deployed at 146:57:01, at around 24000 ft. Main chutes deployed at 146:58:02, at around 10000 ft.
Splashdown occured at 147:03:03 GET.
1659289843428.jpeg


Post splashdown & crew egress:
Post splashdown procedures were performed. However, as the spacecraft splashed down before sunrise, the crew was instructed to remain inside the spacecraft until sunrise, wich occured at 148:11:00 GET.
(Now, please correct me, NASSP devs) At 147:41:31, the fatidic bell sounded. As I was waiting for a few minutes more to open the hatch (waiting for sunrise), the CO2 on the cabin was rising, causing crew death. I considered this an ECS issue, because my configuration was correct (my post landing valve was Open, and the vent was set to High), and an investigation and fix is currently on the works: https://github.com/orbiternassp/NASSP/issues/783 . I tried to edit the scenario, to resurrect the crew, but failed, so I ignored the issue and continued as if that was caused by an issue.
Hatch was opened at 148:13:36. Crew egress occured at 148:15:26.

vlcsnap-2022-07-31-19h53m02s990.png


Final comments:
As with Apollo 7, again I would like to take another chance to thank everyone involved with NASSP, and everyone who was with me on the stream. For this mission, logistics was easier, as the mission was simpler, in some manner, comapred with Apollo 7. But it was the first time mankind saw the Moon, face to face. Some of you commented that I was more serious on this mission, specially on the way to the moon. I had memories of last year´s attempt, where external and internal human factors contributed to that abort. By the GIF shown on FD2, when I got the PAD for MCC-2, you can see how much stress was reliefed for me.
The mission went really smooth, and I am completely forgetting about the issue we had with the ECS at splashdown. I understand that it was hard to find, and I am happy to find those kind of obscure issues, because it shows that with this RTS stunts, we are making NASSP even better.
Now, as some of you know, I am extremely busy training for Apollo 9, wich will be the next one, and a big challenge. However, now I have more time for it :) . Due to a external factor (you see, logistics) Apollo 9 will launch on january 7th, 2023, and Apollo 10 on may 18 2023 (for this last one, if all goes well).
Maybe I can do Apollo 10 from my studio, I keep the necessity to live alone, just for one or two weeks to perform this missions, wich are now my main project.
After this mission, and Apollo 7, I got even more confidence in doing this kind of stunts, and I think that they will become easier in the logistics point of view.

In a few days I will publish all the screenshots and quicksaves from the mission.

Again, thanks for all the support, and see you on the next one. NASSP4Life!
 

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
Attaching quicksaves for the Real Time Simulation run. Names are processed as best as I could. Also on the zip are the raw quicksaves.

I hope they are useful!
 

Attachments

  • Quicksaves Apollo 8.zip
    9.9 MB · Views: 17

thermocalc

Active member
Joined
Aug 18, 2014
Messages
185
Reaction score
63
Points
28
Location
Bangkok
dear STS,
another very instructive flight .... and very nice performance from you.
sorry to congratulate you only now, but my head was elsewhere...
take care.
 
  • Like
Reactions: STS

thermocalc

Active member
Joined
Aug 18, 2014
Messages
185
Reaction score
63
Points
28
Location
Bangkok
Hi dear STS,
I am back to NASSP after a quite long absence and inspired by your Apollo 8 mission I retried a new one, with NASSP v1941, by paying more attention to details this time (as seen looking at your videos; I am just entered in lunar orbit and I am looking forward to all landmarks marking, so I studied you video part 9/15 in preparation for those).
So far I have accumulated the following questions, which are not “clear” yet, just looking at your “actions” in the video.

Q1) about the virtual cockpit (I am still affectionate to the 2D panel as I can get help from the yellow box helpers, ashamed of me I know, but sooner or later I will memorize the position of the switches and give a try to the VC as well without any help) but I see that sometimes it seems you “translate” the view….how do you do that? (I know I can change sits positions with CTRL+arrows, tilt the views with ALT+arrows, zoom in and out with the mouse, but I didn’t manage to find out how to TRANSLATE up/down/right/left, as I have seen you do…)

Q2) how to set the orbital rate when in ORDEAL? It seems to me that you set the controls in MIN IMP and you just “hit” the pitch control so to “eye balling” when the pitch scale in the ORDEAL FDAI stay fixed … is it so? – I ask as I am not able to keep it so constant as you, having always to adjust from time to time the rate … I am using min impulse … but do I need to set up something in the DAP V48 to make min impulse mode more stable? Or am I just “careless”?

Q3) I saw you mentioned RTCC MFD to calculate T1 for landmark tracking: just to make sure I understood you correctly: you enter the landmark LAT/LONG and the flight plan time to start observation as “guess T1” and you calculate the solution (-> which i guess are the time T1 and T2). am i correct?
Are you doing so in A8, as contrary to others missions, the MCC is not automatically calculating and showing the P22 PAD?
Connected to this question, when you are tracking some landmarks, I saw you mentioned: “…and now let’s start the orb rate”….what time are you using to start it? The time T2 generated by the PAD?

Q4) connected to the HGA and OMNIs antenna management … I understood you are using the V64 occurrences in the original flight plan (but not mentioned in the checklist MFD) to set up the P – Y angles in the HGA manually to get a strong signal, and then going back to auto-track…but I don’t get why sometimes you also switch between the different OMNI antennas positions? Are not them independent antennas, and only the HGA is used?

O1) this is not a question but an observation: nice the “waste disposal” demonstration with the R9 and 251 panels, I never knew about them…

keep looking with interests at all your remaining videos for interesting facts….

Take care and thanks.
Paolo
 
  • Like
Reactions: STS

thermocalc

Active member
Joined
Aug 18, 2014
Messages
185
Reaction score
63
Points
28
Location
Bangkok
...sorry I forgot to mention two unrelated facts:
1) while after Indy91 made available again the Earth Apollo Landmarks, they can be sees in low earth orbit, at time of the Punta Yomomeko P22 i also didn't see the landmark, but i managed to do it correctly after recognizing where Punta Yomomeko is/was - so it seems confirmed also by you that at high altitudes are not displayed (which would be not so problematic indeed), as after all for A7 / A9 should be there, where they are mostly required.
2) when you were in lunar orbit i also saw that once you commented on the Lunar markers, and while again thanks to Indy91, you can indeed see now the moon landscape features (craters names and so on ...) the old Lunar markers for making P22 (CP1, CP2, and so on) are not displayed yet; but i "guess" you should know that they can be seen by using the trick mentioned by MaxQ (i know you want to be realistic as much as possible, so forgive me, but the way you mentioned in the video, i am/was not sure if you know about this "trick" .... and even if and others might not be willing to use, others at the beginning (as myself) might be happy to know...cheers!
 

Attachments

  • old markers.JPG
    old markers.JPG
    70 KB · Views: 17
  • Like
Reactions: STS

STS

Well-known member
Joined
Feb 1, 2009
Messages
486
Reaction score
157
Points
58
Location
Vigo
Website
orbisondas.es
Hi dear STS,
I am back to NASSP after a quite long absence and inspired by your Apollo 8 mission I retried a new one, with NASSP v1941, by paying more attention to details this time (as seen looking at your videos; I am just entered in lunar orbit and I am looking forward to all landmarks marking, so I studied you video part 9/15 in preparation for those).
So far I have accumulated the following questions, which are not “clear” yet, just looking at your “actions” in the video.

Q1) about the virtual cockpit (I am still affectionate to the 2D panel as I can get help from the yellow box helpers, ashamed of me I know, but sooner or later I will memorize the position of the switches and give a try to the VC as well without any help) but I see that sometimes it seems you “translate” the view….how do you do that? (I know I can change sits positions with CTRL+arrows, tilt the views with ALT+arrows, zoom in and out with the mouse, but I didn’t manage to find out how to TRANSLATE up/down/right/left, as I have seen you do…)

Q2) how to set the orbital rate when in ORDEAL? It seems to me that you set the controls in MIN IMP and you just “hit” the pitch control so to “eye balling” when the pitch scale in the ORDEAL FDAI stay fixed … is it so? – I ask as I am not able to keep it so constant as you, having always to adjust from time to time the rate … I am using min impulse … but do I need to set up something in the DAP V48 to make min impulse mode more stable? Or am I just “careless”?

Q3) I saw you mentioned RTCC MFD to calculate T1 for landmark tracking: just to make sure I understood you correctly: you enter the landmark LAT/LONG and the flight plan time to start observation as “guess T1” and you calculate the solution (-> which i guess are the time T1 and T2). am i correct?
Are you doing so in A8, as contrary to others missions, the MCC is not automatically calculating and showing the P22 PAD?
Connected to this question, when you are tracking some landmarks, I saw you mentioned: “…and now let’s start the orb rate”….what time are you using to start it? The time T2 generated by the PAD?

Q4) connected to the HGA and OMNIs antenna management … I understood you are using the V64 occurrences in the original flight plan (but not mentioned in the checklist MFD) to set up the P – Y angles in the HGA manually to get a strong signal, and then going back to auto-track…but I don’t get why sometimes you also switch between the different OMNI antennas positions? Are not them independent antennas, and only the HGA is used?

O1) this is not a question but an observation: nice the “waste disposal” demonstration with the R9 and 251 panels, I never knew about them…

keep looking with interests at all your remaining videos for interesting facts….

Take care and thanks.
Paolo

Hello, thanks for the comments. I proceed to answer:

Q1: Virtual cockpits have "seat positions" and also "view positions" (I think they are called that way). What you see me do is to change the view position, and for that I use the combination Control+Alt+Cursor (Left/Right/Up/Down).

Q2: Yeah, I just eye ball it using Min Imp. IIRC, I think that I even went to 2 jets on pitch at some moments, by changing the configuration on panel 16. There were some procedures for an auto orbital rate that were started to be tested on Apollo 9, so for 8 they did it manually as you saw.

Q3: I used RTCC as we did on 7 to generate the P22 PAD´s, as the MCC is not giving you P22 PAD´s on Apollo 8 at this moment. Maybe @indy91 can clarify better here, so I generated the PAD´s as you say. For the pitch rates during tracking, at T2 I start the 0.5º/Sec pitch down and there is where the tracking is performed. After the marks are completed, I pitch up back to R0,P5,Y0 and restablish the orbital rate. For "...and now let´s start the orb rate...", there are some times on the flightplan where you are supposed to start it, and I also practised a lot the lunar operations of Apollo 8 so I knew from practise when to start them. For example, on the following picture maneuver to Orb Rate attitude is started at 77:00:00 GET and orb rate is initialized there, after you finished the maneuver to the attitude. Then you pitch down at T2, and when tracking is complete, maneuver back to orb-rate and start the orb-rate (around 77:44:00 GET). Can´t remember if I did it this way for this orbit (Revolution 4 to 5) but I should have done it this way:
1663059919586.png


Q4: At the above picture you can see an "Acquire MSFN on OMNIS". There I could use V64 to point the antenna to Earth, and then use it checking the signal strenght. I used the antenna that had more signal strenght, but I also didn´t understand very well how the HGA antenna is different to the Omnis. I believe than on Apollo 8 they used the HGA at various specific GET´s to check it out at different distances. Maybe some dev can explain us how the antennas were managed during apollo missions, specifically when to use HGA or when to use Omnis. For V64 I also used this picture from the Apollo 8 CMP checklist: https://www.ibiblio.org/apollo/Documents/A8-CMP checklist-1004.pdf pg 43.

1663060728096.png


2): Yeah, I saw that change of the configuration file to make the old landmark tracking available again, but I didn´t use it because I had forgotten about that one since 2021 and also because I did want the challenge to try and identify them visually (which was fun).

I hope that I have answered all!

Best regards,
 

rcflyinghokie

LM Junky
Addon Developer
Joined
Jun 4, 2016
Messages
423
Reaction score
205
Points
58
Location
Colorado
Maybe some dev can explain us how the antennas were managed during apollo missions, specifically when to use HGA or when to use Omnis.
Apollo 8 was the first use of the HGA so antenna management was directly proportional to the spacecraft attitude and what data was in need of transmitting.

OMNI use was usually based on the predicted spacecraft attitude throughout the mission, and then switched by crew/MCC request as needed for other maneuvering.

HGA for 8 was typically used for data/TV and was at MCC request. Additionally they had scheduled communication tests at different phases for HGA. This is actually in the flight plan under the telecommunications tests.

Later missions had more predictable attitudes during the mission and in lunar orbit, not to mention better controls of orbital rate, so HGA use was more frequent and could even be used for MCC to control the data and comm equipment during sleep periods.
 

thermocalc

Active member
Joined
Aug 18, 2014
Messages
185
Reaction score
63
Points
28
Location
Bangkok
Q1: Virtual cockpits have "seat positions" and also "view positions" (I think they are called that way). What you see me do is to change the view position, and for that I use the combination Control+Alt+Cursor (Left/Right/Up/Down).
if the "cursor (left/right/up/down) are the "arrow keys" than it seems i have a problems to run / use them to access these "view positions".
if i am in VC and i try to hit any combinations of CTRL+ALT+ARROW keys (up or down or left or right) i got a CTD , an error message and the screen get ROTATED by 90 degrees, to get it back to horizontal way need to hit again the opposite arrow key i used .. see some photos of problems i am having.
i guess this is a leptop related keyboard issue ??? :cry:--- if so, ok, next year when relocating back to Europe after finding a new home I will buy a new PC (desktop) ... so i can wait ....
if instead there is another way/solution for the time being, then i would be glad to know.

note that despite on what the error message says, i was running orbiter in window mode in my screen native resolution ... but it happens also if i go to full screen mode.

all your others replies, are fine, they clarified my previous point, thanks.
about OMNIs and HGA i will read a bit more about the AOM (honestly i didn't pay too much attention to the telecommunications parts, but i will try follow the FP (looking at what you have done) just for sake to better understanding (i remember in my last Apollo 10 missions i was used to do a lot of V64 follwing the FP but everything was running well, but it was another missions, and as said by "rcfly" .... ).
thanks to all.
Paolo
 

Attachments

  • ctrl alt arrow down.JPG
    ctrl alt arrow down.JPG
    78.2 KB · Views: 16
  • ctrl alt arrow left.JPG
    ctrl alt arrow left.JPG
    94.7 KB · Views: 15
  • error message 1.JPG
    error message 1.JPG
    25.7 KB · Views: 15
  • screen resolution.JPG
    screen resolution.JPG
    28.5 KB · Views: 16

indy91

Addon Developer
Addon Developer
Joined
Oct 26, 2011
Messages
1,158
Reaction score
457
Points
98
if the "cursor (left/right/up/down) are the "arrow keys" than it seems i have a problems to run / use them to access these "view positions".
if i am in VC and i try to hit any combinations of CTRL+ALT+ARROW keys (up or down or left or right) i got a CTD , an error message and the screen get ROTATED by 90 degrees, to get it back to horizontal way need to hit again the opposite arrow key i used .. see some photos of problems i am having.
i guess this is a leptop related keyboard issue ??? :cry:--- if so, ok, next year when relocating back to Europe after finding a new home I will buy a new PC (desktop) ... so i can wait ....
if instead there is another way/solution for the time being, then i would be glad to know.

Seems like your laptop has some built-in hotkeys which are not Windows standard. And then the DX9 client doesn't like your graphics settings changing mid simulation session. There is probably a way to disable it in the graphics options, for example like this: https://superuser.com/questions/373832/disable-alt-arrow-display-flip-keyboard-shortcut#:~:text=To free up the Ctrl Alt Arrow shortcuts for VS Code's multiple cursors&text=Click Apply.,Click Apply.

I'm sure with some googling you can figure out how to deactivate it. The CTRL+ALT+Arrows is an Orbiter feature and not a NASSP feature, we are just using it like other Orbiter vessels do. So not much we can do about it, it's a very needed feature to access all the switches in the VC easily.
 
  • Like
Reactions: STS

thermocalc

Active member
Joined
Aug 18, 2014
Messages
185
Reaction score
63
Points
28
Location
Bangkok
EUREKA!!!!!!!!!!!!!
thank you INDY91.
I changed the hot keys combinations to rotate the screen from the intel graphic set up page, and now i can enjoy all the view points STS was alluding too, indeed with those activated, now moving inside the VC is all another experience ... thanks a lot!!!
definitely I must give it a try now to pay respect to all of you developers (as said i thought it was a my laptop related problem and cannot change it for another year .... but now this is not the case any longer :cheers:).

to close this VC topic, allow me a last question:
is there also (maybe) a way to get the visual helpers in the VC running? is there some keys combination to make them work? have been implemented in the meanwhile?
thanks again for the valuable help.
can resume my A8 mission now in peace.....
 

indy91

Addon Developer
Addon Developer
Joined
Oct 26, 2011
Messages
1,158
Reaction score
457
Points
98
to close this VC topic, allow me a last question:
is there also (maybe) a way to get the visual helpers in the VC running? is there some keys combination to make them work? have been implemented in the meanwhile?

No, the yellow boxes around switches to press from the Checklist MFD that we have on the 2D panel have not been implemented yet in the virtual cockpit.
 
Top