Search results

You chose launch day 180 in the config file, but June 27th is the 178th day of the year. If I use 178 there it gives me a good solution. Despite the input launch day, it will use current time as the initial guess. That's why it found the solution 2 days before your launch day, hence the negative...

I believe that is correct. Ullage burn until RCS propellant depletion.

I need to update the REFSMMAT section of the RTCC MFD manual... The landing site REFSMMAT depends both on the CSM state vector (its orbital plane really) and the landing site coordinates. And that would be the CSM state vector at the time of landing, not some time before LOI. So there used to...

If it's an older NASSP version, we had some bugs with animations, random parts of the mesh were suddenly animated I think. Hopefully it's just one of these bugs that are already fixed!

Inspired by the recent release of Space Shuttle Vessel, I've been flying a bit more Shuttle than Apollo spacecraft these days and I made an update to the MFD: -Change coordinate system used in the MFD to a true equator, Greenwich median (TEG) system. This is the kind of change where you...

In the launch checklist you can find these tables, left side is nominal TLI and right side is manual TLI: The greek letter psi is the yaw angle during the burn. And what you saw is probably close to the nominal TLI. During a manual TLI you simplify the procedure a bit and use a constant yaw...

Well this issue makes no sense to me as the REFSMMAT calculation page always saves in the CUR slot and the REFSMMAT uplink page always uplinks the CUR one as well. If either of you can reproduce it then I could maybe retrace this issue with the same scenario and specific inputs MFD inputs, but...

Well I have no idea how downlinking the REFSMMAT solved this issue, but I am glad it did :D

Hmm I don't know exactly why the procedure is as written in the flight plan, but it was to preserve the CMC state vector. Ever since TEI the onboard state vector was mostly left alone and only updated with P23s, to simulate a no-comm situation where it's all on the CMP and P23 to navigate. When...

Do you see the REFSMMAT changing on the REFSMMAT page when you do the calculation? You can use the DWN button to get the current REFSMMAT from the CMC. When you then calculate, does it change at all?

The REFSMMAT tables for CSM and LM aren't really used much yet. When you calculate a new REFSMMAT on the REFSMMAT calculation page is will always be saved as the current (CUR) REFSMMAT. No need to move them around with G00. Which type of REFSMMAT did you have before and which did you want to...

EVAs with both astronauts are now supported! This one should have been implemented a long time ago, but until now only one astronaut could exit the LM. There are a few smaller limitations. The CDR always exits first and only the CDR can span the flag and the LRV (on the later missions)...

Ok, so even if your first scenario, where the DSKY state is a little bit buggy, I can press the / button on the Numpad, which switches to translation (and I do get the sound for that). And then I press 2 on the Numpad to translate updwards and as a result I get a 0252 in R1 on the DSKY, a new...

Unless it is just seconds before the scenario you already posted it's probably not going to be more useful than the current scenario already is. But maybe your memory of events could help. I figured out one more thing about your issue. The AGC doesn't continually update the DSKY, instead it...

I think there are different size limits for scn files vs. txt files. And NASSP files have been exceeding the limit for scenarios ever since the AEA memory also had to be saved. I don't know more yet, but something in your LGC seems buggy. Like, not even simple DSKY inputs like Verb 1 Noun 1 are...

Then I will need to check in your scenario what could be wrong. Maybe something with the LGC or so...

Hmm, then the TTCA commands aren't coming through to the LGC. Could be a wrong joystick configuration or some switch setting. Do you have any joystick enabled as the TTCA in the NASSP setting of the Orbiter launchpad?

Ah yeah, it's a double unfortunate situation. With the AGS, when I first got the PGNS to AGS downlink working I had to implement a hack that buffers three "packages" of PGNS data for the AGS to process. Otherwise this wouldn't even work at 1.0x time acceleration at 60fps. But I guess with good...

Absolutely no CSM or LM state vectors ever arrived in the AGS in your "after bad 414+1" scenario, I can see that from the AEA memory in your scenario. What it could be is, for the LM the AGS automatically includes accelerometer data if a certain acceleration threshold is reached. So the CSM...

Just from what I can see with some tools in the RTCC MFD: In that scenario the LGC CSM state vector is good, the LGC LM state vector has a 18,000 feet downrange error which is fairly bad. The two AGS state vectors are both garbage, the position vectors of them are completely zero. So they...