Meadville Space Center
Welcome, Guest. Please login or register.
October 26, 2020, 08:39:45 PM

Login with username, password and session length
Search:     Advanced search
Project Apollo - NASSP 6.4.3 released!
http://nassp.sf.net
25068 Posts in 2094 Topics by 2266 Members
Latest Member: twa517
* Home Help Search Login Register
  Show Posts
Pages: [1] 2 3 ... 7
1  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: V8 Release Work Thread on: May 11, 2018, 08:14:58 PM
Is gyro drift modeled yet? Or will a proper P52 align the IMU indefinitely?
2  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: Optrics Covers on: April 04, 2018, 05:43:25 PM
It takes a while to reach full right. Is the trunnion counter stopped? And are the Optics powered on? As obvious as that second one is I've made that mistake a few times  Embarassed
3  Project Apollo - NASSP / Support & Bugs / Re: LM G&C checklists anywhere? on: January 13, 2018, 03:59:47 PM
Right here: https://history.nasa.gov/afj/ap12fj/pdf/a12_lm_g&n.pdf

It's LM G&N Dictionary for Apollo 12. Same format as the CM G&N Checklists. I've used it a lot and it's very consistent with the Luminary version in NASSP. The Apollo 15 DELCO manual on ALSJ is also helpful. Managed to rendezvous with the CM (and whiff plenty more times  ROTFL) using a combination of the two for help.
4  Project Apollo - NASSP / Support & Bugs / Re: CMC/LGC Restart on: December 26, 2017, 05:41:12 PM
It has happened with nearly every scenario that has been quicksaved or loaded from a current state. So it has not happened on a fresh scenario. But if I save that scenario and continue it later, the problem will eventually occur. Make sense?
5  Project Apollo - NASSP / Support & Bugs / Re: CMC/LGC Restart on: December 26, 2017, 01:41:45 PM
It has happened on 1x, when switching panels or opening the Ctrl-F4 menus. This one has just happened to be on 60x because it is the most reproducible. The sim was smooth at 60x before the restart. Should I try and force those other errors as well? It can make NASSP almost unflyable - had the computer restart in the middle of P12 when I switched from the CDR side to LMP side of the LM.
6  Project Apollo - NASSP / Support & Bugs / Re: CMC/LGC Restart on: December 25, 2017, 03:59:14 PM
Here is the scenario after a restart. This time there was an alarm code. The restart also happened when switching to an external view. This one happened by running the time acceleration up to 60x for a few seconds then back to 1x. Opening an external MFD prompt on the descent also lead to a restart.

There seems to be a link to the demand placed on the CPU and a hardware restart. I never had this problem before an early December build, and NASSP was the only thing upgraded in my Orbiter folder.
7  Project Apollo - NASSP / Support & Bugs / Re: CMC/LGC Restart on: December 25, 2017, 09:41:15 AM
It is a few builds ago. Started flying Apollo 11 about 2 weeks ago so the most recent build as of 12/18. I updated and will see what happens. And I did check V05N09E, just abbreviated it as 05 09. All 3 registers show 00000. If I still have the issue I will post a scenario here.
8  Project Apollo - NASSP / Support & Bugs / CMC/LGC Restart on: December 24, 2017, 03:15:41 PM
In nearly every scenario I often get a hardware restart either when ending time acceleration or swapping panels. The restart will rarely reset the CMC clock, but will often change the computer from P00H to another seemingly random program (usually in the Pre-Thrusting groups of 30s or 70s). The hardware restart is accompanied by a program alarm lt, with no program alarm in the 05 09 display. Is this typical at this stage of NASSP 8? Haven't been keeping up to date with the IRC.
9  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: Virtual AGC on: September 14, 2017, 05:51:26 PM
There was a NASA documentary on planning a lunar trajectory, but it was pretty rudimentary. Pick an azimuth that gets you to the antipode on time - launch to southern sites over the Atlantic and Northern ones over the Pacific. I guess what it would come down to is needing an "LOI Search" function that looks for the cheapest TLI by searching LOI times within a given range. But that would change the location of the moon at arrival, which means a new antipode, then a new TLI time, then a new launch azimuth. It would really all have to be done on the pad then, maybe even before opening Orbiter in some sort of mission planning spreadsheet. Probably not something necessary for a few versions yet.

Still, it's awesome to see the pace NASSP is moving at! I wouldn't of dreamed going to Tycho would've been close to possible in NASSP this year.
10  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: Virtual AGC on: September 13, 2017, 08:58:32 PM
Just out of curiosity being the Zerlina scenario uses a hypothetical landing site: how possible is it to land at alternate sites right now? I can see it being relatively simple (using the RTCC MFD and creating a new terrain model) if the site chosen is at the same longitude as a historical site: like flying to Tycho with Apollo 14 or Copernicus with Apollo 12. What about somewhere like Marius Hills for instance? It is too far west for the proper lighting conditions, so none of the historical launch times work. This would mean having to update the TEPHEM, and I would assume the lunar polynomial among other things? It would boil down to just having to change the launch time, but how many part of the padload would be impacted? And can they be recalculated manually?
11  Project Apollo - NASSP / Support & Bugs / Re: BPC not showing on LH RDV window on: September 02, 2017, 06:47:58 PM
The BPC had a small portal window over window 2 giving only the CDR a clear view. There are a few diagrams of it. Not sure why, but I guess in case the IU failed. Gene Cernan remarked in "In the Shadow of the Moon" that the CDR could have flown the stack into orbit using only the stars.
12  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: Virtual AGS Development on: August 08, 2017, 01:25:45 PM
So is the AGS working out of the box (has NASSP embedded VAGS?) or does it needs external VAGS application running and NASSP acts only as input/output?

Has anyone some LM saves with AGS working?

Is there any LM guidance and control manual that describes AGS?

I've been able to use the AGS without any background applications and it saves under AEA in the scenario file. I've been using this to help me learn it:

https://www.hq.nasa.gov/alsj/LM_AGS_FP6_OperatingManual.pdf
13  Project Apollo - NASSP / Programming / Re: Apollo RTCC MFD on: July 13, 2017, 03:47:25 PM
I'm getting flying Apollo 10 and am at loi, however I think the rtcc is giving me a bad ls refsmmat. After uplinking and doing p52 opt 1 Agc can't point the optics at the right stars and I get terrible Loi results, i.e. 436x-137. Will attach scn

edit: this scn is just before refsmmat uplink

I had the same issue at LOI on Apollo 12. Completely forgot about it, or would have included it in my error report. A newly calculated and uploaded REFSMMAT and P52 Opt 1 did the job for me, but that still doesn't explain the error the first time around. Out of curiosity, did you have the NO ATT light remain illuminated long (like ~1 min) after the FDAI slewed to the new orientation? That was always the clue to to me something was amiss.
14  Project Apollo - NASSP / Support & Bugs / Re: LV GUID Light on: July 12, 2017, 12:15:14 PM
EDIT: Didn't have to dig all that deep. The IGM failure flag is set in your scenario. Probably due to the problem during launch. With the flag set the LVDC never uses the IGM again. I'm not entirely sure if the IGM was actually disabled forever if a problem happens during launch. But our LVDC right now will not steer the Saturn anymore after a failure has been detected. All you can do in that case is using the manual TLI procedure. I will intevstigate whether the IGM failure (and as a result the Guidance Failure light) is really permanent or if it can be used for an automatic TLI after the Saturn was manually flown into orbit.

To answer the burn resulted a workable but poor trajectory. I assumed it was mainly because I had to shut down manually. The IU did point the S-IVB slightly out of plane (about a 5 degree left yaw) and there was a lot of thruster activity when the uplink was complete, but I guess no IGM. I'll see if I can dig through some pdfs as well.
15  Project Apollo - NASSP / Support & Bugs / H-Mission Errors on: July 12, 2017, 09:58:58 AM
Sorry I did not attach the lvlog. I wanted to fly through the whole mission and then report any issues all together so I wouldn't forget any files. I encountered a few issues on the Apollo 12. This is my completed first landing mission so some may be user error:

1) The LV GUID lt that I began this topic with. I haven't been able to reproduce it, but if I do I will attach the log and the scenario.

2) TLI required a manual shutdown using the Keypad -. The burn was up-linked to the IU with the RTCC and the EMS dV counter was set. I reproduced it without running Program 47, but that has no effect on the IU. The lvlog and scenario are attached.

3) When Orbiter's REF was the Sun, the RTCC MFD would crash when minimizing the MFD on the P30 Maneuver PAD page. I have not been able to reproduce this after updating. Perhaps it has been handled?

4) I would get a program alarm 20430 (overflow of the P00h-do loop) before lunar lift off. There was an LGC restart during Lunar Stay which caused the clock to reset. Updating the clock gave me a COMP ACTY light in P00H until the alarm. I think this is just the realistic behavior of the LGC iterating the state vectors after a massive clock update, but I have included the scenario before and after updates. I tried an upload with no program running (so V36E, Clock update, LM SV, CSM SV, V37E 00E) and the error persisted but became less frequent. Copying the pad-load from the launch scenario solved the problem and did not interfere with launch and rendezvous. This may not be a bug but more a consequence of the buggy EPS. I included the files anyway.
Pages: [1] 2 3 ... 7
Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!