Meadville Space Center
Welcome, Guest. Please login or register.
December 03, 2020, 03:55:37 PM

Login with username, password and session length
Search:     Advanced search
Welcome to the new Meadville Space Center forums!
25068 Posts in 2094 Topics by 2267 Members
Latest Member: Apollo Next
* Home Help Search Login Register
  Show Posts
Pages: [1] 2
1  Project Apollo - NASSP / Support & Bugs / Re: No control of attitude thrusters??? on: April 21, 2012, 10:02:47 PM
That's no bug. The SM RCS will not be activated before separation from the SIVB. If you really need attitude control on the booster (for what?), you can perform saturn take-over

How about for P52 alignment prior to TLI.  The checklist says to make sure that roll, pitch and yaw are all nulled.  I have found I need to null a couple, so how can I do it effectively, without attitude thrusters?  Is Saturn take-over still the best way?

Thanks,
Reuben
2  Project Apollo - NASSP / Support & Bugs / Automatic SV Update on: June 03, 2011, 06:49:17 PM
Hi everyone,

I've finally got some time to fool with this amazing simulation again.  Continued congratulations go to the developers.   Thumbs Up

I'm working my through the Apollo 7 mission and I'm wondering if the automatic SV update via the PAMFD is working.  I followed the steps in the vAGC flightplan (several times) and according to the PAMFD, the SV update worked just fine, but I saw no indication on the DSKY that the uplink was in progress or finished.  Is this normal or is there a problem?

I have attached the scenario I'm using.  The scenario starts about 1 minute before an SV update, so the entire "AUTOMATIC SV UPDATE" checklist needs to be completed.

Thanks
3  Project Apollo - NASSP / Support & Bugs / Re: RHC and THC confusion on: October 08, 2008, 01:44:05 PM
Thank you, Tschachim!

Now I understand.  While testing out various control setups I did a "quick and dirty" CSM/SIVB sep and then tried to get the controls the way I wanted.  Unfortunately, I didn't follow the separation checklist and neglected to power the THC and the proper thrusting quads A1,A2,C1,C2.   Duh!

As a result I couldn't get any response from the THC in any configuration I tried.

I'm able to use a logitech controller (dual analog stick, POV hat) that I found as the THC and the keypad as the RHC.   Thumbs Up

Thanks,

Reuben
4  Project Apollo - NASSP / Support & Bugs / RHC and THC confusion on: October 07, 2008, 06:39:06 PM
Hi,

I'm very confused about RHC and THC control with a Virtual AGC scenario.  I don't have any joysticks.  Previously, it was possible to use the numeric keypad for RHC and THC with the '/' as a toggle.  Is this STILL possible?  If so, what settings do I need to make on the Control Tab of the Project Apollo Configuration dialog box.  That dialog tab is very confusing to me.

I also tried using PPJoy with the PPJoyKey application so that I could map a group of keys to the RHC and another group of keys to the THC through separate Virtual Joysticks but cannot find any enough keys on the keyboard in close proximity that don't have an Orbiter function.  Also I couldn't get Orbiter (NASSP more specifically) to recognize the Virtual Joysticks that I created.  So I'm back to trying to use the numeric keypad for both.  Can someone please explain the best way to provide an interface to both the RHC and THC without buying joysticks?

 Bangs Head

Thanks,

Reuben
5  Project Apollo - NASSP / Support & Bugs / Station Keeping on: October 04, 2008, 08:26:05 PM
Hi all,

It's been a while since I've been able to play with NASSP or Orbiter.  I've decided to start over at the beginning (so to speak) and fly Apollo 7 now that an "Apollo 7 release" has been released in Beta.

After reading through the Excel flightplan I've come across a term that I'm hoping to get a full definition for:  Station keeping

The flightplan say to "STATION KEEP WITH SVB", but I don't know exactly what that means.  Does that mean to actually dock with the SVB or just stay in close proximity?


Thanks,
Reuben
6  Project Apollo - NASSP / Programming / Build Problems on: May 02, 2008, 06:04:04 PM
Is anyone else having build problems with the latest in CVS.

I just did a CVS update then a full build and received the following errors

Code:
7>ProjectApolloMFD.obj : error LNK2019: unresolved external symbol _send@16 referenced in function "void __cdecl send_agc_key(char)" (?send_agc_key@@YAXD@Z)
7>ProjectApolloMFD.obj : error LNK2019: unresolved external symbol _connect@12 referenced in function "void __cdecl UplinkStateVector(double)" (?UplinkStateVector@@YAXN@Z)
7>ProjectApolloMFD.obj : error LNK2019: unresolved external symbol _htons@4 referenced in function "void __cdecl UplinkStateVector(double)" (?UplinkStateVector@@YAXN@Z)
7>ProjectApolloMFD.obj : error LNK2019: unresolved external symbol _inet_addr@4 referenced in function "void __cdecl UplinkStateVector(double)" (?UplinkStateVector@@YAXN@Z)
7>ProjectApolloMFD.obj : error LNK2019: unresolved external symbol _closesocket@4 referenced in function "void __cdecl UplinkStateVector(double)" (?UplinkStateVector@@YAXN@Z)
7>ProjectApolloMFD.obj : error LNK2019: unresolved external symbol _WSAGetLastError@0 referenced in function "void __cdecl UplinkStateVector(double)" (?UplinkStateVector@@YAXN@Z)
7>ProjectApolloMFD.obj : error LNK2019: unresolved external symbol _socket@12 referenced in function "void __cdecl UplinkStateVector(double)" (?UplinkStateVector@@YAXN@Z)
7>ProjectApolloMFD.obj : error LNK2019: unresolved external symbol _WSAStartup@8 referenced in function "void __cdecl ProjectApolloMFDopcDLLInit(struct HINSTANCE__ *)" (?ProjectApolloMFDopcDLLInit@@YAXPAUHINSTANCE__@@@Z)

Thanks,
Reuben
7  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 Testing using Apollo 8 Flightplan on: April 18, 2008, 12:01:05 PM
After my last post, but before any replies, I tried V96 and that did stop the lock up.  I did not immediately to a SV update as I was scheduled to do one shortly there after.  Once I terminated the PTC at PeT=3.800k I did the SV update and things were OK.

I performed the LOI according to the SCS maneuvers of the flight plan but did not stay in orbit!  Before the burn took place I made a visual inspection of my orientation wrt to the moon and the CSM was pointed in the direction of travel.  Shouldn't I have been facing SPS-engine-bell-first for the burn to place me into orbit?

After the burn I could clearly see that I was not in orbit.  IMFD confirmed this.  I reloaded the scenario back to PeT=3.800k and tried the whole thing again with the same results.  Any clues as to why the IMFD BV screen is telling me to point the ship the wrong way?  I have attached the scenario at PeT=-1.400k after the ship has been oriented correctly (according to IMFD).

I am still running this scenario on the Jan 16 module release and not the latest in CVS.  irnenginer, do you recommend I use the new Solar Ephemeris solution in CVS?

I'm beginning to think that I should restart the mission over using the lastest in CVS as I am not happy with my course maneuvers all the way back to TLI.


8  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 Testing using Apollo 8 Flightplan on: April 17, 2008, 05:19:54 PM
I added the EMEM values to my scenario and just as Admiral stated, the lock up disappeared within 30 seconds.  I was able to do my 2nd MCC with no problems.  Happy

However, I am now at MET 065:16:00 and the lock up has resumed.  I have since save the scenario a couple of times and verified that the most recent scenario still contains those EMEM values.  Any ideas?

9  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 Testing using Apollo 8 Flightplan on: April 16, 2008, 04:23:26 PM
So, irnenginer, are you are able to model the entire diagram then?  If so, I'd say you're on your way to a solution.   Thumbs Up

Sadly, I'm not very versed in mechanical control theory.  I don't think I can be much help after all.   Sorry

Good Luck!
10  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 Testing using Apollo 8 Flightplan on: April 16, 2008, 12:36:33 PM
irnenginer,

Thanks for the scenario data.  I'll give that a try soon.

After looking at the block diagram you mentioned, I don't believe it's coincidental that the page number is 6-66.  WOW!!  Shocked

I'm not sure I understand what all the grpahical symbols mean.  For example the circle with the 'X' or the '+' with a slash that has 2 horizontal ends.

In addition, it doesn't appear that all the mathmatical symbols are defined.  I don't see a definition for TS (Tau).
11  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 Testing using Apollo 8 Flightplan on: April 15, 2008, 01:28:08 AM
Hey irnenginer,

From where I sit, it looks as if you're still very far ahead of us.   Wink  Let me know if I can be of help on the TVC.  After re-reading your posts, it sounds like a PID control loop would do the trick.

Thanks for the link to the AGC manual, BlueDragon.  That is by far the most comprehensive source I've seen!

Reuben

12  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 Testing using Apollo 8 Flightplan on: April 14, 2008, 06:10:09 PM
yep.  According to the manual, going to V96 does not maintain state vectors, so you would need to update them when you bring it out of suspension.

What manual are you speaking of?
13  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 Testing using Apollo 8 Flightplan on: April 14, 2008, 04:35:24 PM
Thank you BlueDragon and Admiral.

I reference a printed copy of the flight plan/checklists and neglected to print the "errors" page.  Embarassed

If V96 suspends state vector integration, is it necessary to do a state vector update after the CMC has been reset?

Thanks,
Reuben
14  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 Testing using Apollo 8 Flightplan on: April 14, 2008, 03:34:06 PM
Admiral,

I have run into the same CMC issues.

Between 052:30:00 MET (after 3rd P23 of the mission ) and 060:00:00 MET I noticed I had a constant Comp Activity light come on.

The 2nd mid course correction had prog error 1520 or error 1202 alarms occur at execute.  P00 would not set and the comp Activity light stayed on.

I found this to be somewhere between hours MET 056:00:00 and MET 057:00:00.  Right around the time IMFD projected I would enter moon SOI.  Did you try to resolve the COMP ACTY problem prior to the 2nd MCC, and if not, is that why you received the 1520 and 1202 alarms?

To fix, I did a V36 CMC restart procedure.  This cleared the comp activity light error and I performed an IMU recovery.  Interestingly I was out of both Earth and Moon SOI according to IMFD so did not do a state vector update until I was in th Moon SOI well after the burn.

Where is the V36 procedure documented?  It's not in the Apollo 8 checklist.  How did you perform an IMU recovery?  Can you provide me with (or point me to) a procedure for that?

I am currently at MET 058:30:00.  I would like to resolve the COMP ACTY before the P52 alignment and 2nd MCC.

Thanks,
Reuben
15  Project Apollo - NASSP / Support & Bugs / Re: Apoolo 8 Testing using Apollo 8 Flightplan on: April 08, 2008, 12:49:26 PM
It would be an honor to join your team!!  Excited!  I certainly don't want to step on anyone's toes though.

I must confess that as a married father of two my time is a precious commodity, but I would very much like to help in any way that I can.  I think it would really help me understand what all the switches I'm toggling are really doing!

I would be very appreciative if someone would help me get started (i.e. create a working project, compiling/building, etc.).

Admiral, I will let you know how the mission progresses.

Reuben
Pages: [1] 2
Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!