Search results

The Apollo 13 mission in NASSP now uses LM131R1, the actually flown LGC version! The LGC software for Apollo 13 had a complicated development history. But basically, we have been using Luminary 131 in NASSP for a long time, which is an earlier version of the software. Fairly late into the...

The current MCC solution for the CDH burn uses a time of ignition that gets calculated differently in the RTCC than in the LGC. That kind of happened on the actual mission, too, so mission control took the LGC time for the CDH burn, re-calculated the burn for that time and that became the CDH...

"SV/RR LOS > 3 deg" means that the direction to the CSM as the LGC knows it differs by more than 3 degrees than the direction that the RR is pointing to. So either LGC or RR is wrong, in the LGC it would be the state vector, with the RR it would be a side lobe lock-on. Delta SV means, when the...

The problem seems to be on the CMC software side. If I cause a restart with Verb 69 and then re-zero the optics the issue is gone. Something in the CMC software might be thinking it has to issue SPS thrust vector control commands instead of optics commands, they use the same interface. I bet...

Oh you know, what happened a few months ago is that we got rid of separate MCC vs non-MCC scenarios. All launch scenarios are now MCC scenarios, at least those missions that support it (Apollo 7-11, Apollo 12 experimentally). And if you would want to deactivate the MCC and fly an Apollo 7-11...

Is this one of the scenarios in the WIP Scenarios folder? We forgot to update the scenario version in those T-4h launch scenarios, I'll fix that asap.

P40 is calculating a preferred REFSMMAT the same way as the RTCC would do with the P30 (heads up) REFSMMAT option. Run P30, make sure V48 has the right trim angles because they used in the REFSMMAT calculation, and then enter P40 for just the first display. Then you should get 0,0,0 for the...

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.

I think you are confusing GMT and GET. GMT in the RTCC is counting up from midnight Greenwich Mean Time of the launch day. The RTCC uses mainly this for time keeping, because it is an "absolute time" and doesn't depend on the liftoff time or even modified liftoff time like on Apollo 14, 16 and...

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...

In the real RTCC they had a feature to generate a custom uplink. And for that you could input numbers in engineering units, tell it what scaling and precision (single, double or even triple) you want and it would generate the data for an uplink. That would be quite helpful here I guess as it...

The worksheet is 15 years old, so I am pretty sure it works haha. If you are using Excel for the web, I think VBA macros (which this is) doesn't work in there. Different method. Go here: https://coderstoolbox.net/number/ Put 432000 seconds in decimal, add two zeros because the AGC measures...

It's not running the script to calculate the octal values. Was there no prompt to allow or disallow scripts when you opened the file? The numbers would appear where you see the #NAME?

The time you want to load is the acqusition time like during landmark tracking (T2). So when I flew Apollo 12 I switched to the CSM and calculated a landmark tracking PAD there and the T2 time was then what I input into the LGC. For the conversion to octal, I am sure we can come up with a...

Another update: -Various improvements to the Launch Window Processor. I had first implemented the LWP for the Shuttle, then I ported it to my RTCC MFD for NASSP to calculate launch time and parameters for Skylab launches and made various improvements to it in the process. Now I ported these...

A small update to the MFD: -Easier initialization of launch date. Launch date and launch time are separately input now. -Deorbit opportunties are discarded if their estimated time of ignition is earlier than the time to start searching. -Added some single-vehicle maneuver types (node-shift and...

That is from the FDO Console Handbook, Volume 3, On-Orbit Trajectory Operations. I found it in the L2 subscriber section on the nasaspaceflight.com website. I hate that it is behind a paywall, but it still doesn't feel right to send this document out to everyone. It would be quite useful to any...

Yep, you are correct. The effect will be random because uninitialized variables are used and it will only occur on the first timestep, but the AGS is looking at the accelerometers constantly and will incorporate the data, not like the AGC where that only happens if Average G is running. Will be...

I had the same issue, I installed SSV in an older Orbiter 2016 install with an older DX9 Client version and what fixed it for me was to just update the DX9 Client to the newest version.

Perfect, the astronauts telling the "flight controllers" what day it is so that they can calculate their launch accurately :D I'll also discard all deorbit opportunities with a TIG before the input time to start the search, as you talked about in your previous post.