CMC's P20/32 does not mark and the LM's plane change does not make any sense

Zuppermati

Member
Joined
Feb 16, 2020
Messages
32
Reaction score
5
Points
8
Hello everyone.
I apologize in advance for any grammar mistake (I'm on my phone and the auto corrector can be a pain).

I've been as busy as ever with my job and I managed to progress with my Apollo 11 simulation very slowly, but I finally made it back to lunar orbit from the lunar surface and I'm dealing with the rendez-vous.

I am having issues with both the CSM and the LM. From what I understand, although NASSP's checklist ignores this step altogether, I have to perform P20 and P32 on the CSM in order to get, among many other things, a more accurate yDot for the LM. I have been following the "CSM rendezvous procedures" (G mission) I found on ibiblio. Now, I was following turryboeing's streams as well and I could see from the very beginning how something was wrong with my setup since setting the EMS function and the EMS mode to VHF range did nothing on the range display (which is always stuck at 0 0) while on his stream he was getting data from the very beginning.

Anyway, on page 88, at time 124+49, it instructed me to key V93E, V57E and V87E. I did not have the time to learn about these verbs as much as I wanted to, but I understand how V87 is needed to enable the CSM to take marks using the VHF. Except that it does nothing. V16N45 displays zero (both before and after V87) and I keep getting a tracker light on the DSKY. I thought that maybe I had to take marks using the sxt instead, but from what I understand orbiter is kinda limited and I cannot see it on the telescope until something like 60nm, not even its yellow box (which makes no sense since orbiter can mark Neptune on the planetarium but not something some 100k nm behind you), so I have no idea what I have to do.

I also tried to simply ignore the CSM's side of the deal and focus on the LM but to no avail. When I arrive at the plane change burn, I get relatively high numbers (which make no sense since my LM's plane is perfectly aligned with the CSM from the start). Rotating the LM around does not reduce such values on the DSKY (unlike with the CSI), the display does not blank at T-35 seconds, and even if I perform the burn the Dv values do not drop. Or better, they do drop but by extremely small amounts (so the values are definitively updating on the display). Ignoring the burn causes the next burn TIG to be before the plane change burn itself, and changing it on the pad is useless since it gets recomputed by the lgc anyway. If I ignore it, I eventually get weird program alarms (can't remember which and I deleted the scn file, please tell me if you need them) that block the whole process.

Chances are that I did not understand something but I tried literally everything to no avail.

Many thanks in advance and regards
 
I am having issues with both the CSM and the LM. From what I understand, although NASSP's checklist ignores this step altogether, I have to perform P20 and P32 on the CSM in order to get, among many other things, a more accurate yDot for the LM. I have been following the "CSM rendezvous procedures" (G mission) I found on ibiblio. Now, I was following turryboeing's streams as well and I could see from the very beginning how something was wrong with my setup since setting the EMS function and the EMS mode to VHF range did nothing on the range display (which is always stuck at 0 0) while on his stream he was getting data from the very beginning.
Which step are you saying NASSP ignores?

And if you arent getting VHF ranging, you dont have your VHF configured correctly.
Anyway, on page 88, at time 124+49, it instructed me to key V93E, V57E and V87E. I did not have the time to learn about these verbs as much as I wanted to, but I understand how V87 is needed to enable the CSM to take marks using the VHF. Except that it does nothing. V16N45 displays zero (both before and after V87) and I keep getting a tracker light on the DSKY. I thought that maybe I had to take marks using the sxt instead, but from what I understand orbiter is kinda limited and I cannot see it on the telescope until something like 60nm, not even its yellow box (which makes no sense since orbiter can mark Neptune on the planetarium but not something some 100k nm behind you), so I have no idea what I have to do.
If you dont have VHF ranging up (as you said you couldnt get anything on EMS in the above message) then you dont have any ranging data for the CMC to take marks.
If you are on a current version of NASSP you should be able to see the LM much further than 60 nmi now, but yes that was an orbiter thing we have a workaround in NASSP for.
I also tried to simply ignore the CSM's side of the deal and focus on the LM but to no avail. When I arrive at the plane change burn, I get relatively high numbers (which make no sense since my LM's plane is perfectly aligned with the CSM from the start). Rotating the LM around does not reduce such values on the DSKY (unlike with the CSI), the display does not blank at T-35 seconds, and even if I perform the burn the Dv values do not drop. Or better, they do drop but by extremely small amounts (so the values are definitively updating on the display). Ignoring the burn causes the next burn TIG to be before the plane change burn itself, and changing it on the pad is useless since it gets recomputed by the lgc anyway. If I ignore it, I eventually get weird program alarms (can't remember which and I deleted the scn file, please tell me if you need them) that block the whole process.
This sounds like you havent followed the procedures correctly or missed steps.

What might be helpful is if you pop over to our discord and we can take a look and help walk you through a rendezvous and explain how things work. Rendezvous is complex and everything has to essentially be done correctly and in the right order.

 
Good evening
Which step are you saying NASSP ignores?

I meant the CM's side of the rendezvous procedure. At least in my version of NASSP, it completely ignores it. After lunar liftoff, it goes straight to "station keeping with LM". P20 and friends are completely ignored.

With that being said, it turned out that what I believed to be the VHF RNG reset switch was instead a switch with a similar name in panel 2 (in my defense, both are cited in the procedure and so it is not hard to mix them up). Now I am getting both the VHF range on the EMS, a reasonable yDot, and all the marks I wanted. However, the problem with the plane change remains: the DSKY does not go blank and thrusting with the RCS does not do anything. Out of curiosity: could it be that I have to null out the y axis ALONE (which I guess it's like nullying the AGS value on register 501)? Because I noticed that thrusting on the y axis does reduce the value on that register, although V16 N85 stays the same...

PS: discord hates me and the link you sent me is apparently expired
 
I meant the CM's side of the rendezvous procedure. At least in my version of NASSP, it completely ignores it. After lunar liftoff, it goes straight to "station keeping with LM". P20 and friends are completely ignored.
Oh then you must have an old version! I added CSM side checklists for 11 a long time ago!
With that being said, it turned out that what I believed to be the VHF RNG reset switch was instead a switch with a similar name in panel 2 (in my defense, both are cited in the procedure and so it is not hard to mix them up). Now I am getting both the VHF range on the EMS, a reasonable yDot, and all the marks I wanted. However, the problem with the plane change remains: the DSKY does not go blank and thrusting with the RCS does not do anything. Out of curiosity: could it be that I have to null out the y axis ALONE (which I guess it's like nullying the AGS value on register 501)? Because I noticed that thrusting on the y axis does reduce the value on that register, although V16 N85 stays the same...

PS: discord hates me and the link you sent me is apparently expired
That might have been my mistake! Here is a fresh one...

 
Also, feel free to jump in the #nassp channel and ask away, many can help you :)
 
Back
Top