Search results

Just saw this thread! Sorry about no response! Get it all sorted? Also, the ORDEAL is used to monitor TLI since the SIVB doesn't burn inertially, it actually moves its burn vector at an expected rate which matches what the ORDEAL can generate, so one ball allows the pitch to remain more or less...

@jarmonik ^ Mind taking a look?

Yeah it is not inconsistent, only Apollo 7 and 9 had SCS use in their burns, and it was strictly for testing.

Missions that use SCS for burns (Apollo 7 and 9 for instance) were to test the SCS. All other mission burns (Apollo 8, and 10-17) were planned to burn with PGNS, with SCS as a followup/backup. Which burns using one or the other are you referring to?

Glad you enjoyed it! Hopefully more changes can be added in the near future to properly simulate all the things you had to work around. Also thanks for finding a few bugs :) They normally wouldnt have been noticed on a routine flight.

Looks like this is a bug, RTCC is throwing a calculation error with masses of propellant. I will let @indy91 take a look. EDIT, I just realized you are in a CM/LM configuration, so the error is thrown because there is no propellant mass in the SM anymore. That is why its crashing. You needed to...

This got a hotfix, with more changes on the way but the meter no longer needs power. Fix is in work here, there was an unnecessary condition check on the auto rcs coils. Hmm looks like another mistake in the simulation! The EL lights should have power from the DC computer cb. I will get a fix...

Yeah that has them just on the main bus tie switches.

Yeah in this case, the LM is still powering MN B and MN A is brought up because both A and B are needed to heat the CM RCS. Unfortunately we dont have the power simulation necessary yet to allow the LM to power the CSM.

Looks like another case of incorrect NASSP code! They should fire in RHC normal and man att accel command without any AC power, but there are checks in the code incorrectly preventing it.

I can check into that hot fire later today

When I looked at your save, the MNA values are what I copied to generate those MNB values.

In any case, the fuel cell shouldnt have thrown a NaN (kind of a divide by zero state) so anything helps us look into it.

Would you mind sharing the save before the NaN? I can see if it was procedural (ie not getting the FC off the bus) or if there is something else going on. Also the test meter is wired incorrectly, those injector temps only need the INST power to generate a signal, so thats on our end :P

Yeah looks like something got screwed up way back when, your main bus tie is still "tied" to fuel cell 2 and it has generated NaN values, so nothing can power up properly through the main busses. Could you humor me and dig back through your save files and find where your fuel cell 2 went to...

Something is screwy with this save it seems, I need to dig a bit more, but you should have power in MNA and MNB. I will report back. Also I see in the save there are a few NaN's which is a computation error (not your fault.)

I will check out the save and see. Actual LM lost Bat 2 due to a short as it is :)

I could be way off here, but it seems injector temperature data is only powered through the instrumentation bus (V1 and V2 busses) not the SCE/FLT BUS. I need to do some digging but our modeling could be wrong here haha!

Are you sure you should be able to see the injector temps at that point? If you can give me a mission time that you are currently following along with I can backtrack.

Sounds good, I actually have improvements for the injector temps in an update coming up, so you might notice them a little cold compared to how they were in the mission