Meadville Space Center

Project Apollo - NASSP => Support & Bugs => Topic started by: Tschachim on July 01, 2006, 06:20:07 AM



Title: Bug reports
Post by: Tschachim on July 01, 2006, 06:20:07 AM
Hi Apollo fans,

if you find a bug in the latest beta (there's no further development of the 6.4 versions) please report it here after you checked if the bug is already in the list:
http://sourceforge.net/tracker/?atid=716072&group_id=129726&func=browse

Cheers
Tschachim


Title: Re: Bug reports
Post by: Juhowee on December 07, 2007, 06:19:56 PM
Hmm... I have started P02 in AGC and programmed it (V16E) to show time to lift-off. When I load quicksave, AGC doesn't countdown anymore. This isn't problem, I just programmed it again. But is it a little bug?


Title: Re: Bug reports
Post by: movieman on December 07, 2007, 06:20:59 PM
Yeah, that's been around for a long time; I don't quite understand why it happens because the AGC keeps displaying VERB 16, but not processing it.


Title: Re: Bug reports
Post by: Juhowee on January 25, 2008, 10:50:53 AM
I made CVS Update. Now I have bad problem that comes soon after launch. I startet Apollo 11 Quickstart. I made some launch preparation:

AGC:

PRO
V37E N01E
V33E
V33E
V16E

Then I align my GDC and set my propellant indicators.

Launch, yaw and roll works normally, but pitching is problem. My rocket pitches and pitches too much and finally its going to ground. See attach.



Title: Re: Bug reports
Post by: lassombra on January 25, 2008, 11:24:22 AM
Did you build new modules when you updated?


Title: Re: Bug reports
Post by: Juhowee on January 25, 2008, 11:36:37 AM
Did you build new modules when you updated?

Build? Do you mean "programming" or something like that? I cant make CVS update in Modules folder. Do I have to download this (http://sourceforge.net/project/downloading.php?groupname=nassp&filename=ProjectApollo_Beta_20080115.zip&use_mirror=mesh)?


Title: Re: Bug reports
Post by: lassombra on January 25, 2008, 12:29:33 PM
This may be the source of your problem.  I believe there are a couple minor incompatibilities between the current CVS tree and the latest modules pack.  I'll probably get a new modules pack up before the end of the month, as we have quite a few changes.


Title: Re: Bug reports
Post by: ts230 on October 13, 2008, 12:25:06 PM
Launch, yaw and roll works normally, but pitching is problem. My rocket pitches and pitches too much and finally its going to ground
I have the same Problem!!
Have you an idea how to fix it?


Title: Re: Bug reports
Post by: Tschachim on October 13, 2008, 04:51:50 PM
Are Complex flight model and Limited fuel enabled on the "Parameters" tab of Orbiter's Launchpad?

Cheers
Tschachim


Title: Re: Bug reports
Post by: ts230 on October 13, 2008, 09:58:37 PM
@Tschachim

That works :)!


Title: Re: Bug reports
Post by: NLS le pingouin on April 04, 2010, 03:31:21 PM
I think the BUS CONT circuit breaker, that are attached to the FC REACS VALVES switch don't works.
This is what I have done :
226
*FUEL CELL 1/REACS close
*FUEL CELL 1/BUS CONT close
3
*FUEL CELL REACTANTS/1 off
The MASTER ALARM sounds. So :
3
*FUEL CELL REACTANTS/1 on
*FUEL CELL MAIN BUS /1 on
And there is no more alarme.

I tried this thing two more times. One with FC REACS VALVE on LATCH and I cannot shut down the reactants valves.
And one more time with the FUEL CELL 1/BUS CONT opened so the FC REACS VALVE would not be powered. But in this case, I cannot shut down the reactants valve.

edit : I found another thing. I was still playing with the FUEL CELL REACTANTS switch, when I quit orbiter with the FC BUS DISCONNECT alarm light on. When I load again this state, the MASTER ALARM was still toning, but the yellow alarm light wasn't anymore.


Title: Re: Bug reports
Post by: meik84 on April 27, 2010, 03:26:14 PM
Just played around a bit with P23: It doesn't do any harm to the SV, why? The missing horizon alt can't be the cause, I hacked in the original numbers from Apollo 8 and still got all balls in N49 (therefore, the CMC places the LLOS near the horizon nicely now :cool7777:). Or is this infamous W-matrix more clever then me (can't be -P22 produced numbers in N49 on my last try)?


Title: Re: Bug reports
Post by: irnenginer on April 27, 2010, 11:47:20 PM
I think you are on the right track woth the W-matrix. You may need to give the W-Matrix nonzero value before P23 will work.

I have not had much luck getting P23 to work so far.


Title: Re: Bug reports
Post by: meik84 on April 28, 2010, 11:00:02 AM
You're right. This smart CMC seems to have separate W-matrixes for P20, P22 and P23. P22 seems to be intialized already, so you only need to do that for P23:
V67E
F 06 99
V25E
+08000E
+00070E
+00003E
PRO

That's the procedure described here -> http://history.nasa.gov/ap10fj/docs/p23-w-matrix-tlc.pdf (http://history.nasa.gov/ap10fj/docs/p23-w-matrix-tlc.pdf), just changed R1, as the CMC didn't accept the +80000 (maybe an issue of Colossus - Apollo 10 flew with Comanche, I guess). With this, P23 produces sensible numbers in N49. The only thing we need now is something to compare the onboard SV with the 'real' SV -just to see if we are as good as Jim Lovell ('the man with the golden hands'). :wink:
Or in EMEMs:
EMEM1355 21450 (HORIZON ALT -not the best, but quite good)
EMEM3000 5161
EMEM3001 311


Title: Re: Bug reports
Post by: Tschachim on April 28, 2010, 11:05:25 AM
I think the BUS CONT circuit breaker, that are attached to the FC REACS VALVES switch don't works.
...

Thanks for reporting that and sorry for my late answer. I'll take a look as soon as I have more time for Project Apollo again.


Title: Re: Bug reports
Post by: NLS le pingouin on April 29, 2010, 04:29:42 AM
No problem. I was looking for the source code of project Apollo. As soon as I really understand the structure of all that I will try to help. I was trying to implement this : http://www.ibiblio.org/mscorbit/mscforum/index.php?topic=2333.0 (http://www.ibiblio.org/mscorbit/mscforum/index.php?topic=2333.0)
But I don't understand in wich file I could do that. For the moment I am workless, so one day I will take the time to do that.


Title: Re: Bug reports
Post by: movieman on April 30, 2010, 01:54:56 AM
There's a caution and warning base class which is probably where you'd want to start looking; I think we model the two power supplies but I don't know whether either of them can fail.


Title: Re: Bug reports
Post by: eddievhfan1984 on May 24, 2010, 11:05:51 PM
I don't know whether this qualifies as a bug, but here are two things that confuse me.

1. I'v been experimenting with the P34 and P35 programs in Apollo 7 (rendezvous transfer initiate and midcourse correction/braking respectively). I get P34 to work just fine, but when I run P35, the AGC freezes, with the COMP ACTY light constantly lit, and it won't accept a P00 command or anything. The computer just kept running for an hour before I said f*** it and pulled the CMC breakers in frustration. What's up with that?

2. While performing SPS burns, I've found that the engine is gimbaling under CMC control when it is apparently unnecessary. I have my dV CG switch set correctly and my DAP in proper configuration, but it still happens. Anyone know why?


Thanks for the assist.


Title: Re: Bug reports
Post by: Tschachim on August 16, 2010, 09:10:23 AM
I think the BUS CONT circuit breaker, that are attached to the FC REACS VALVES switch don't works.
...

I fixed all that, I did the FC pump and purge cb's on panel 226, too, the schematics are attached for reference. The scenario format changed because of the loading/saving bug.

2. While performing SPS burns, I've found that the engine is gimbaling under CMC control when it is apparently unnecessary.

Could you elaborate and/or attach a scenario? Why do you think the thrust vector control is unnecessary?

Cheers
Tschachim


Title: Re: Bug reports
Post by: meik84 on August 16, 2010, 04:09:01 PM
Quote
1. I'v been experimenting with the P34 and P35 programs in Apollo 7 (rendezvous transfer initiate and midcourse correction/braking respectively). I get P34 to work just fine, but when I run P35, the AGC freezes, with the COMP ACTY light constantly lit, and it won't accept a P00 command or anything. The computer just kept running for an hour before I said f*** it and pulled the CMC breakers in frustration. What's up with that?
Set EMEM 2022 to 21450 an try again. This sets ATIGINC to 90 sec. ATIGINC is the time "from now on" (to be precisely from start of P35) till execution of the MCC. When it is set to 0, the AGC will think you want to do it now and will never stop calculating. Oh, and don't forget: you've got to run P34 first, otherwise P35 will have no time of intercept and do garbage. Are you "just playing around" or really doing a rendezvous? I haven't come this far by now, as we can't calculate the CCR and CSI burns yet. :(


Title: Re: Bug reports
Post by: eddievhfan1984 on August 19, 2010, 11:10:56 PM

Could you elaborate and/or attach a scenario? Why do you think the thrust vector control is unnecessary?

Cheers
Tschachim

What I'm saying is that when the burn program starts and the SPS gimbal check is done, it does not come back to a neutral position, and the effect of gimbaling just causes the burn to be performed incorrectly. I think it was just random action on the part of the CMC, as I redid the operation, and had no issues.

Set EMEM 2022 to 21450 an try again. This sets ATIGINC to 90 sec. ATIGINC is the time "from now on" (to be precisely from start of P35) till execution of the MCC. When it is set to 0, the AGC will think you want to do it now and will never stop calculating. Oh, and don't forget: you've got to run P34 first, otherwise P35 will have no time of intercept and do garbage. Are you "just playing around" or really doing a rendezvous? I haven't come this far by now, as we can't calculate the CCR and CSI burns yet. :(

I was actually trying to do the SIVB rendevous in Apollo 7. I did do the P34 first. However, I haven't tried messing with the CMC RAM (EMEM) registers. As for the P32-P33 programs, I didn't use those either.  :wink: I was working off the checklist-provided burns.



Title: Re: Bug reports
Post by: Puma on December 18, 2016, 02:00:10 PM
I want to report the following bugs:
=====================

I have tested your latest build: NASSP-V7.0-Beta-master-302.zip and I have encounter the following problems.
First the Saturn V inclination on launch pad is wrong, then the rocket crashes into the ground, I have tried with most of the modules on tab off and I have tested also with other Orbiter ad-dons and everything is fine, so it makes me think is an NASSP issue. the second bug is related to the Apollo checklist.mfd, back in the days in older releases once you press a button or do anything according to the checklist, the yellow market used to disappear, now it never does it, so you have to press pro manually, it is not so important most of the times, but you need to understand that with a 2d panel some buttons do not look to be pressed or not. any way I attached some pictures, I hope you find the solution. Thanks!. 


Title: Re: Bug reports
Post by: indy91 on December 18, 2016, 02:10:12 PM
That poor Saturn IB crashing looks hilarious!

The Beta version you downloaded is not Orbiter 2016 compatible. The (hopefully soon) to be released NASSP 7.0 version will be for Orbiter 2010. There is a version for Orbiter 2016 already, but it needs a lot more work: https://github.com/dseagrav/NASSP/releases/download/NASSP-V7.0-Beta-Orbiter2015-225/NASSP-V7.0-Beta-Orbiter2015-225.zip

I rarely but occasionally have the Checklist MFD not reacting to buttons or switches being used. Not sure how that would be related to the wrong Orbiter version, so maybe there actually is a problem here. I'll look into it.


Title: Re: Bug reports
Post by: Puma on December 18, 2016, 02:28:11 PM
Thanks, yes I do really tried on orbiter 2016, but any way. regarding the Apollo checklist.mfd bug I could load a little video for showing the bug it if you need it, by the way I tried the version you suggested and have the same results.


Title: Re: Bug reports
Post by: indy91 on December 19, 2016, 06:38:20 AM
Are you sure the Checklist MFD is set to AUTO - ON? And the only problem I really had were the DSKY keys. If you press these keys for too short a time, then the Checklist MFD didn't register it as a key press.


Title: Re: Bug reports
Post by: Puma on December 19, 2016, 10:25:03 AM
You are absolutely right! it need to be in auto mode, but for me it was kind of weird since auto mode was miss interpreted by me as automatic checklist execution, LOL, but fortunately it is not, by the way I find to be more realistic if I set the Orbiter time to : 0.1X since there are a lot of buttons to press and must of the time at launch I am behind schedule still pressing buttons, LOL, Do you know when Apollo 11 mission will be available? Thank you very much! :ThumbsUp432:


Title: Re: Bug reports
Post by: indy91 on December 19, 2016, 10:41:38 AM
You are absolutely right! it need to be in auto mode, but for me it was kind of weird since auto mode was miss interpreted by me as automatic checklist execution, LOL, but fortunately it is not,

Yes, there is something a little bit confusing about this. If you start Orbiter and go to Extras -> Vessel configuration -> Project Apollo configuration -> Virtual AGC Mode then you will indeed find a "Enable automatic checklist execution" option. This option however is a fully automatic mode, which automatically flips every switch for you, if all you want is a demonstration. The "AUTO" mode, which you can enable in the MFD itself with Orbiter already running, just means that it is automatically processing your input. This can be confusing of course. In the Vessel configuration I would suggest using the "Slow automatic checklist execution", if it isn't already enabled.

Quote
by the way I find to be more realistic if I set the Orbiter time to : 0.1X since there are a lot of buttons to press and must of the time at launch I am behind schedule still pressing buttons, LOL,

With some practice you will be easily able to do it in time. That happens when you use the T-4 hours launch scenario, right? The Checklist MFD with the flashing marker is already a great help with that, it really reduces the time you have to spend searching for the right button.

Quote
Do you know when Apollo 11 mission will be available? Thank you very much! :ThumbsUp432:

Well, there is an Apollo 11 scenario! You will find it under: "\Scenarios\Project Apollo - NASSP\Broken Scenarios\Virtual AGC\Apollo 11 - LVDC++ Launch.scn" NASSP 7.0 is only for Orbiter 2010 and will only fully support the Apollo 7 and 8 missions. What that means is that the Lunar Module is far from finished and a lot of procedures and maneuvers haven't been fully worked out yet. So you are mostly on your own trying that scenario. It's a fully configured LVDC++ scenario at least, so you don't have to use LTMFD or anything like that for TLI. It's all in the launch scenario already and TLi will happen automatically. I would suggest trying an Apollo 8 TLI with the Checklist MFD as your helper before you move on to Apollo 11.