Yeah if you arent running 1920x1080 this will make things worse haha. I originally wrote that based on an "expected" 1920x1080I tried making sightings with the AOT FoV set to 60. Star 03 detent 02 gave me +00074. Star 12 detent 06 gave me -00314. So I don't think using FoV 60 helps.
Then I thought I'd try setting the AOT FoV to exactly 46 using the Camera FoV. Star 03 detent 02 gave me -00005. Then I tried star 12 detent 06, and got -00001 (!). So finally some repeatable results. As a further check I tried star 20 (Dnoces) detent 04 and got +00006.
Hmm this is interesting, I will bring it up and see if this could be a difference. But it is supposed to compensate your camera view for your screen resolution...so odd resolutions might be causing that.So if I set the AOT FoV to exactly 46 I seem to be able to get good results using different stars. Adjusting the FoV from 45.79 to 46.00 makes a big difference. I don't know if this is an acceptable resolution to my issue, but it seems to be better than where I was before.
Well, I want to get this right, so back to the wonderful world of P57...EDIT: One thing I will add is you should leave it to whatever it defaults to (45.79) as that is mathematically calculated to be correct. I think the angle differences between that and 46 are likely just differences in technique based on talking to some of the team.
Funny thing is, the center point of the marker is where the star was during Apollo. The stars in orbiter are where they are now, so you SHOULD be using the center point of the markerOn my screen some of these Apollo nav stars are not too bright. When I've been making my sightings, unless the star was very obvious, I've been inadvertently placing my cursor or spiral over the center point of the green crosshairs. The problem there is that looking closely I noticed the star is not always centered in the crosshairs (at least not on my screen). It's not a big difference but I think that has been my problem.
Honestly, given you are on a laptop screen, you should be perfectly fine here based on your results. Yes the stars should be within the crosshairs, but the distance from center is the difference in star location between then and now. Also any zooming/fov change will also mess with the perceived position.I think it might be more an issue with my laptop? To be clear, the stars are always within the crosshairs, I'm only talking about minor deviations from dead center. I played around with it this morning and sometimes when I started the marking sequence the star (let's use Navi as an example) might be slightly off center, low and right. The second time through Navi might appear low but centered left/right. A third time it was almost perfectly centered. So it's not consistent.
It's really small differences, but I think it was enough to affect my marks? Making sure I centered on the star exactly seemed to help my marks.
Ok AGS stuff! I love the AGS haha. So 224/226 are basically your orbital target. Essentially if the AGS flew your ascent where it would take you WRT the moon.Moving on, time to program the AGS. Some of these entries come off the ascent PAD (224/226, 231).
You actually don't enter these in this case on the checklist, they are for comparison. You are to compare your DEDA 047 and 053 addresses to the pad values and they should be close. These values are set in the AGS after you align the AGS to your PGNS. In some cases Houston did ask for changes to these values like on Apollo 15 though so you are welcome to change them if different.The PAD also had values for DEDA 047 and 053. I don't see where on the Lunar Surface Checklist I should enter these? I see later we will read them out, but not sure if this is an input.
232 should already be padloaded. This is your targeted altitude in 100 ft. You can use the value that's already stored which should match the value on the checklist (+00600)Entry 232 (targeted injection alt) I think is going to be around 60 (?) but where would I get the correct value?
Correct +00320465 we left at 32.
Ah these values are used to provide a yaw steering wrt the orbital plane. For example if you needed some left yaw during ascent to face the steerable antenna towards earth, this would hold that yaw during ascent. In the PGNS you can simply yaw and it will hold it but the AGS will if you set out of plane steering (623+1) and use those values which would be read up if non zero as they are octal. I need to hunt for the values for Apollo 15 since they did have a 40 degree yaw during ascent.When I do 514R, 515R, and 516R the coordinates are all zeros. What should I see here?
Yep that will work, 307 is in 0.01 minutes.307 (trans time TPI to Rendz) I believe I came up with during the ascent planning, mine was 45.06
Oh that's just AGS TIG, so it applies to any maneuver. Its basically which AGS time you plan to burn. So you just compute your TIG in AGS time.373 has me stumped. Looking at the AGS manual it can refer to many things (CSI, CDH, TPI, Ext dV), not sure what I do here.
So are you still pre liftoff or post insertion?What am looking at/looking for reading the tweak burn MSK 0063 page? This is the first time I've gotten this far, not sure what it all means.
And once I know what I'm looking at, could you walk me through the burn procedure?
Thanks
Right after insertion, just did the TAR->REN->TI->DIS->CLC->MPT->CLC and I looking at a line of numbers on MSK 0063 that I don't really know what to make of. I was hoping to see something in the DVX, DVY, DVZ variety, but I'm not sure what I'm looking at?So are you still pre liftoff or post insertion?
You should have a TIG and DVX DVY DVZ in the bottom right.Right after insertion, just did the TAR->REN->TI->DIS->CLC->MPT->CLC and I looking at a line of numbers on MSK 0063 that I don't really know what to make of. I was hoping to see something in the DVX, DVY, DVZ variety, but I'm not sure what I'm looking at?
Bottom right of what? I lied earlier, it turns out I'm missing the last two steps of TAR->REN->TI->DIS->CLC->MPT->CLC . I get to TAR->REN->TI->DIS->CLC, and that's as far as I've been able to get. I can't figure out the MPT>CLC part. I'm on the MASK 0063 page and not sure where I go for "MPT" .You should have a TIG and DVX DVY DVZ in the bottom right.
No reason to be embarrassed! I just didn't have a save for insertion and Apollo 15 handy.Bottom right of what? I lied earlier, it turns out I'm missing the last two steps of TAR->REN->TI->DIS->CLC->MPT->CLC . I get to TAR->REN->TI->DIS->CLC, and that's as far as I've been able to get. I can't figure out the MPT>CLC part. I'm on the MASK 0063 page and not sure where I go for "MPT" .
I'm hesitant to share the .scn, this was my first go-through and I'd be embarrassed to share it.
Good question indeed. My first guess is typically you null out a maneuver because the tweak burn takes into account the expected insertion when calculated. But others can probably correct me on this one.There it is!
Question: After shutdown the checklist has us null residuals, then we look at the tweak burn. Why did they do it like that (two steps) instead of skipping the nulling part and just going straight into the tweak calculation? Wouldn't the tweak burn combine both?
Thanks.
Totally normal, lots of retries and saves are a powerful learning tool.It's not pretty, but somehow I'm managing to rendezvous. Between the LM AOH, G&N manual, Timeline book, and Flight Plan (combined with a ton of trial and error) there's enough information to get through the whole procedure. But I will have to go through it again a number of times to figure out how to do it correctly.
Honestly, as much as I love using the AGS, for your first few attempts I would focus on the PGNS. Once you have a PGNS rendezvous mostly down then start learning what the AGS is doing side by side.First area I need to clean up is the AGS. I haven't figured out how to set it up before launch, it's basically just dead weight.
Hmm you should be able to go to the CLC page and just calculate it. MPT should be inactive and all of your parameters loaded before liftoff.I'm shaky on the RTCC/ tweak burn set up. Even though I "pre-set" the TAR>REN stuff it seems like I have to go through the whole RTCC ascent procedure to get tweak values. (Before lift off, should the MPT be active or inactive?)
This one is tricky and I have yet to figure out the actual maneuver, but there is a "yaw/roll maneuver" that is performed here manually to orient to the burn attitude while maintaining radar lock. Letting the computer do it will break lock and they had a trick to it. I need to go back and figure that one out for sure. Don't sweat breaking locks though, crews had it happen often enough IRL and it was a simple case to relock and resume marking.Should I be breaking RR lock when I do the TPI and MCC burns? Going from P34 to P42 I get an F 50 18 that orients me out of lock for the burn, then another F 50 18 to re-orient back when I start P35. Similarly with the two MCCs. Doesn't seem like I'm doing that correctly.
After MCC2 you just bring P20 back up, you will see a little handwritten note in the LM Timeline (attached).And after the second MCC, what should I be doing for orientation? I've been popping back into P35, which orients me back to pointing at the CSM (that's actually P20 kicking back in I think). Do I leave P20 running and let it point me at the CSM? It seems to work out OK but it just feels wrong.
This is the most challenging aspect of the flight imo, takes the most work as you are taking the workload of multiple people and performing it all at once with little automation. I don't know of any direct ascent walkthroughs on here as there aren't too many who have ventured off of the missions with MCC support, so this is probably the first good one!I have a million questions and feel like I'm reaching the end of my self-teaching ability. Has this sequence of events (direct ascent) been discussed in any other threads? You've probably covered this before, and I'd like to read through other people's experiences before I burden you by asking to provide me with a lengthy step-by-step walk through.