Search results

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

That is all correct. The target is the vehicle for which the state vector is calculated. So for a CSM state vector to the CMC or LGC you should select Kitty Hawk (the CSM) as the target. The slot where the state vector is being uplinked to is determined by the uplink type (LGC CSM vs. LGC LM)...

Ah this is a fun one! Due to an unfortunate series of events involving a bug that got fixed a year ago, this older mission scenario and a change in behavior of the ascent stage, the AGS has a wrong pitch cant angle for the APS loaded. Basically, the APS engine is canted by 1.5° in pitch to...

The latest NASSP release should have a fix for this bug. When you load the scenario from above the SPS-6 calculation will now give a good Maneuver PAD. I solved the problem by adjusting the desired apogee height if the height at TIG is above that. So as I said, in your case the calculation...

Ok the problem is that the SPS-6 maneuver tries to get you into a 95x130 NM orbit, but the maneuver point happens at an altitude of 131.7 NM. That obviously doesn't work. Might be the reduced drag that we have right now that caused you to still be in an orbit with an apogee of above 130 NM. I...

Hmm, I think your orbit is shaped incorrectly. The perilune after LOI must be placed quite exact in altitude and location so that DOI can happen at that perilune. Otherwise there will be a large DVZ component of the burn (-257.6 ft/s in your case) and the apolune after DOI is incorrect. This...

In the SPQ the TPI time is usually an input and in the AGC it's always an input. Maybe you are running the SPQ mode to achieve a specific Delta Height? The SPQ has two modes. When you use "Fixed TPI time" then it works like in the AGC. TPI time has to be input and it will iterate on the DH to...

The Descent Engine Command Override switch is only used during powered descent and it is a redundant signal to keep the DPS engine running. What you definitely don't want to happen is that some short power interruption causes the DPS engine to switch off when you are hovering above the surface...

I will do a few checks in that scenario then, state vector etc. RLS is radius of the landing site. The AGS uses the value stored in address 231 as the reference for altitude calculations. The procedure you are doing there is to prepare a manual state vector update on the lunar surface. The...

That scenario is a bit early, that's right after DOI. It's not like I don't want to fly this scenario the hour to PDI, but it's also possible that a procedural error after this scenario is the cause of the issue. So do you maybe have a different scenario where the same issue appears, maybe a few...

Well you gave it a good test for a non-circular case haha. And it's probably ok if you stay in that elliptical orbit until later, even the TEI targeting shouldn't have a problem with that. Have you been doing the tweak burn using the two impulse processor? I feel like that would have given you...

Did you target the circularization burn to get into the 69.9 x 54.2 orbit? This doesn't really work right in Orbiter. The actual lunar gravity perturbations will change this orbit to near circular by the time of LOPC-1. But that can't be simulated in Orbiter yet. So it's probably best to...

Oh yes, that's a bug. I guess I just copied and pasted the GET_Display function, which is just below Angle_Display, and modified it. But I forgot about the "time" variable which somehow didn't give a build error when I didn't change that to "angle". Thanks for finding that!

Only the LEVA can deploy the flag and LRV. Only the LEVA vessel can deploy flag and LRV. Right now it's limited to one. I don't think it take a huge amount of updates to allow two though. Nope, doesn't work yet.

I mean the actual code of the EVA vessel. I can check your scenario, too, if you want, it could very well be a bug.

Yeah it is "V" and I can deploy the LRV in an old Apollo 17 scenario of mine. When looking at the code, the only checks are: "ApolloNo > 14" and then of course "LRVDeployed", a status variable that prevents you from deploying the LRV more than once. And then this last check before the LRV gets...