Meadville Space Center
Welcome, Guest. Please login or register.
December 01, 2020, 10:40:21 AM

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 [3] 4
31  Project Apollo - NASSP / Project Apollo - NASSP Development / Re: Odd errors when rebuilding modules on: November 01, 2006, 02:01:53 AM
You need to install the Orbiter 2006-P1 SDK.

Cheers
Tschachim

OK, so I had only installed the P1 SDK to one of my two installations Duh! I rebuilt everything, and it works great.

Some days, I think my purpose in life is to serve as a warning to others...

  thanks!
  Scott
32  Project Apollo - NASSP / Project Apollo - NASSP Development / Odd errors when rebuilding modules on: October 31, 2006, 10:40:42 AM
I'm running across some odd errors when rebuilding modules that I haven't seen before.  I'm compiling with the Visual C++ 2005 express edition, and most of the modules build correctly, but I'm getting the following errors:


When building Sat5_LMPKD, I get the following on lemautoland.cpp

..\lemautoland.cpp(340) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator
..\lemautoland.cpp(1885) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator
..\lemautoland.cpp(2244) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator
..\lemautoland.cpp(2440) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator

  and on apolloguidance.cpp

..\apolloguidance.cpp(2253) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator
..\apolloguidance.cpp(2641) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator

Sat5_LMPKD
lemautoland.cpp
..\lemautoland.cpp(340) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator
..\lemautoland.cpp(1885) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator
..\lemautoland.cpp(2244) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator
..\lemautoland.cpp(2440) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator

apolloguidance.cpp
..\apolloguidance.cpp(2253) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator
..\apolloguidance.cpp(2641) : error C2675: unary '-' : 'VECTOR3' does not define this operator or a conversion to a type acceptable to the predefined operator

  I get the same errors on apolloguidance.cpp when building Saturn1B and Saturn5NASP

  Finally, when I build SIVb, the following errors happen when I get to sivb.cpp

..\sivb.cpp(668) : error C3861: 'DelMesh': identifier not found
..\sivb.cpp(669) : error C3861: 'DelMesh': identifier not found
..\sivb.cpp(670) : error C3861: 'DelMesh': identifier not found
..\sivb.cpp(671) : error C3861: 'DelMesh': identifier not found
..\sivb.cpp(715) : error C3861: 'DelMesh': identifier not found
..\sivb.cpp(716) : error C3861: 'DelMesh': identifier not found
..\sivb.cpp(717) : error C3861: 'DelMesh': identifier not found
..\sivb.cpp(718) : error C3861: 'DelMesh': identifier not found
..\sivb.cpp(1360) : error C3861: 'DelMesh': identifier not found

  If anybody has a idea how this non-programmer can correct these, please let me know!

  thanks,
  Scott
33  Meadville Space Center / Off Topic / Re: Apollo in Movies on: October 25, 2006, 10:54:59 PM
Hello,

thanks for the quick answer!

what I forgot to mention about point 2 in my first post: They were about to make the LOI burn, when the DSKY showed these strange numbers.

Also they ignited the SPS when they were still in contact with the Earth and they had LOS during the burn. Wasn't the real burn all behind the moon?

  Yes, it was.  I suppose that theoretically, you could design an approach and orbit insertion that took place while still in view of Earth, but given all the limitations of the system, LOI happened while they were on the back side..

  And, as you mentioned in your earlier post, orange lights on the DSKY are more "critical" than the white ones--unless the orange "GIMBAL LOCK" light and the "NO ATT" light are both on together.  Then (as Gene Cernan once explained) you're in deep yogurt.

Quote
And on the Apollo 17 Episode they show Chris Kraft talking to Gene Cernan. Gene had asked for a 4th EVA and Chris said no. Is there a record that states that Cernan and Schmitt originally wanted to make four EVAs?

  Well, I know that Chaikin mentions that Schmitt pushed for a fourth EVA during the planning stages, but the mission planners felt it might cut into their consumables margins.

Quote
EDIT: Were there four EVAs planned for Apollo 18-20?
  I don't think those missions ever got that far in the planning stage.

  take care,
  Scott
34  Meadville Space Center / Off Topic / Re: Apollo in Movies on: October 14, 2006, 07:23:05 PM
Hello again!

3. On the apollo 12 episode, they tell them to switch SCE to AUXILLARY (after the lightning strike). Al Bean (or the guy who played him in the episode) reached for the switch right in front of him (on the main panel). But I never found that switch, whether in the documents on in NASSP beta. What would it do and where is it located?

Cheers!

It's located at the bottom of panel 3, right in the center. If you find the "AC Indicator" rotary at the bottom the panel, start looking to the left of that. Going left from that rotary switch, there are four switches that control the AC inverters powering AC bus 2, a "dummy" switch, and one that sets the PCM bit rate to either "high" or "low". Right next to that are two swtiches labeled "power"--the one on the left is the SCE (Signal Condition Equipment). Flipping that swtich it to "AUX" switches it over to it's auxilliary power source.

Hope that helps,
Scott
35  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: State Vector update on: September 30, 2006, 02:28:32 AM
Hi,
 I followed the state vector update instructions but when it says read the values in the green box on the excel spreadsheet all the values show is #NAME?, and i'm sure that i followed everything right.
Any ideas? And also how often am I supposed to do a state vector update?

Thanks,
Alex


  In addition to what Christophe said, you'll also get that error if the macros in the spreadsheet are disabled.

  take care,
  Scott
36  Project Apollo - NASSP / Support & Bugs / Re: Apollo 7 scenario no longer works with latest beta on: September 27, 2006, 09:51:11 PM
Did you change anything in the CVS folders?


  I've got the same problem as Brittany.  I updated all the CVS folders, but it appears that I've got the most recent version of everything, since the update didn't bring any new files (other than the A11 sound files and a couple of A11 scenarios).

  FWIW, the Apollo 8 VAGC launch scenario seems to work fine.  Don't know if that's any help to anybody.

  I'll try rebuilding the modules and see if that affects the problem.

  thanks,
  Scott

  (edited to add) I rebuilt several of the modules, and A7 is now sitting on the pad like it should. I rebuilt the following (in order):

ASTP
Crawler
Floodlight
LES
LRV
ML
MSS
PanelSDK
ProjectApolloMFD
s1b
s1c
Sat1Abort1
Sat1Abort2
SAT5_LMPKD
Sat5Abort1
Sat5Abort2
Saturn1b

I tested right after rebuilding Sat1Abort2, and A7 was still missing, so I'm guessing at least some of the problem is in the build of Saturn1b.

  hope this helps,
  Scott
37  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: word file documentation on: September 03, 2006, 04:02:49 PM
Hallo Apollo guys,

I am back with some questions regarding Apollo 7 with VAGC.
Once in low parking orbit I tried to follow some items in the checklists mentioned in G&C documentations, doing that I got the following problems:

4. I tried while in orbit P30 and P40: during P30 checklist (ref. pag. 4-1) during step 3, I got
F16 45 and the TFI time was counting up (not down), moreover the orange PROG light on the DSKY was ON and it always stayed on; however, I didnt care about it


Hmmm. Did you enter a TIG that was in the future? If you're at 25:00:00 GET and you want the burn to happen in 30 minutes, you'd enter

+00025
+00030
+00000

Also, the "PROG" alarm means that there was some sort of problem. If it doesn't display an alarm code, enter V05 N09E and it should display the alarm code in Register 1. After you've looked up the code (and figured out what to do about it), "KEY REL" should return you to the program so you can recycle or make any changes you need to make.

Quote
and I made V37E40E (as in P40 SPS THRUSTING, ref.5-1), I got a SPS burn but the spacecraft oriented itself not prograde (I want to increase the speed 500ft/m prograde) and after the burn my orbit was not bigger but smaller and it was entering the Earth (actually the burn reduce my orbit in a collision one).I tried many times, but no success.the vessel never orient prograde before to start the burn (The DAP itself works fine, it orients the vessel in any new P R Y attitude that I enter via V49


I'm not sure why, but if the burn was entered for a earlier time, that may have something to do with it (I don't know--I'm just guessing). Another possibility is that there has been a problem with the Apollo 7 scenario that may be causing the problem.

  I'm afraid I'm not much help on your other problems....

  take care,
  Scott
38  Project Apollo - NASSP / Project Apollo - NASSP News & Discussion / Re: Apollo 8 scenario - Middle course correction(s) on: August 21, 2006, 10:01:39 PM
I have a hard time with TLI

  NBH,

  Here's the problem:

  The "parking orbit" that you go into in Apollo 8 isn't in the same orbital plane as the moon's orbit.  So if you make a normal "prograde" burn (burning along the same plane that you're flying), you're going to miss the moon by a whole lot, unless you do a huge "plane change" burn. (The amount the two orbits are out of plane varied from mission to mission.  I think Apollo 8 and 12 were about the largest, if I remember correctly).

  If you take a look at http://www.ibiblio.org/mscorbit/mscforum/index.php?topic=347.15, it explains how to do an "off plane" intercept of the moon.  Then, you'll just need to do one or two smaller burn to adjust your course once you get closer to the moon.  I've run the Apollo 8 scenario several times, and once I got the hang of it, I can pretty consistently get to LOI (Lunar Orbit Insertion) with about 95-96% of my fuel remaining
39  Project Apollo - NASSP / Support & Bugs / Re: $#%^&$% Gimbal Lock on: August 17, 2006, 11:17:44 PM
I'd like to suggest another section of documentation that is severly lacking.

 (snip)

The Scope: An overview of the systems and their basic requirements during a mission. If you want a good template for what I'm talking about check out Rob Conley's Mercury Familiarization Guide. Something like this for Apollo would be EXTREMELY helpful in learning the ropes. Most don't need a highly technical explenation of the systems, just a conceptual understanding. Personally I feel that Conley's Familiarization Guide is just about the best add-on doc I've ever come across in the Orbiter-verse.

  I just downloaded it, and you're right--that is a great doc, and I think it's something I could do.  Just to make it easier to follow, I'll probably end up doing two of them: One for the CSM, and one for the LM.

  Thanks for the idea! (and thanks to Christophe for the OK).
40  Project Apollo - NASSP / Support & Bugs / Re: $#%^&$% Gimbal Lock on: August 17, 2006, 12:10:24 AM
Hi!
I' know that I'm a bit late with the G&C checklist because I was very busy in real life last month an I just come back from 10 days of hollydays.
New parts of the G&C check (including the P40's and P50's) should come very soon.

Cheers

  Christophe,

  I hope you don't think I was pushing for more documentation.  The stuff you've produced has been a huge help, and makes it a lot more interesting than just button pushing Thumbs Up

  What I was thinking was that when it comes time to write up the "Initialization Procedures" part of the documentation, I'd like to lend a hand, if you'll have me.  I write documentation (and teach computer classes) for a living, so I might be useful to you.

  take care,
  Scott
41  Project Apollo - NASSP / Support & Bugs / Re: $#%^&$% Gimbal Lock on: August 09, 2006, 03:33:40 AM
I think you have to run P53 prior to P54 if you gimbal lock like that. it is discussed elswhere tooo but to be nice: Wink

V37E53E
ENTR (Ball will go to all zeros)
PRO
you'll see F 06 94
V22E
+57476E
PRO
Sight 2 two stars like below. The only diffence is you enter the star code after making the sight so you enter for say star 40

ENTR
PRO
V21E
40E
PRO

After that then run P54 as dseagrav explains

  That did it!  Many thanks to you and dseagrav.  I spent most of the day yesterday looking for how to realign the platform, so I must have missed running P53.  I'm going to try to get some time this week, and document the procedure for exactly how to do this.  When I've got it done, I'd like to forward it to somebody (I think Christophe is the "document guy") for possible inclusion in the docs.

  I can't write code, but I can do documents, so maybe I can contribute.

  thanks,
  Scott
42  Project Apollo - NASSP / Support & Bugs / Re: $#%^&$% Gimbal Lock on: August 08, 2006, 05:56:41 PM
OK, let me start "fresh", and give that procedure a try.

  thanks,
  Scott
43  Project Apollo - NASSP / Support & Bugs / $#%^&$% Gimbal Lock on: August 08, 2006, 01:42:56 AM
While running the Apollo 7 VAGC launch scenario, I decided to simuate a crew rest period (OK, I took a nap, and let the sim run).  When I came back, I had drifted into gimbal lock  Duh!

Is there any sort of documentation floating around on how to get the platform realigned?  The CMC general doc in my \Doc\Project Apollo - NASSP\Check List\G&C checklist\colossus_1A_249 folder mentions using V41 N20 to coarse align the ICDU's, and I did that, but it now thinks the gimbal angles are 0,0,0 (which is what it says to do when in gimbal lock). 

Beyond that, I don't have a clue what the next step is.  I tried updating the state vector using P27 and the state vector update spreadsheet, but loading the data into the AGC didn't seem to do anything. I also tried running P54, but when I start it (N37E 54E), it says I'm running program 54, but the "Prog" light on the left of the DSKY lights, and I get a flashing "37" in the verb field.  Basically, I can go to P00H, but that's about it.

Is there a procedure written down somewhere on how to realign while in orbit?  If not, (and there are bits and pieces here and there that someone can point me towards), I'd be more than happy to write up a procedure for it (documentation is a good part of what I do IRL).

  thanks,
  Scott
44  Project Apollo - NASSP / Support & Bugs / Re: Apollo 8 TLI in version 6.4.3 on: August 03, 2006, 11:23:07 PM
I installed the NASSP version 6.4.3 on a laptop to play around with, while I travel.  I tried the Apollo 8 scenario, but the TLI didn't work out well.  How do I do TLI with the Transfer MFD?   I tried the tutorial at http://www.jdkbph.com/ALMT/ but it didn't work.



Brittany,

  Obviously, I'm new here, but I had the same problem.

  My understanding is that if you do TLI with the Transfer MFD, the burn is purely prograde, and the Apollo 8 orbit isn't in the same plane as the moon's orbit so you miss the moon, unless you do a huge plane change burn on the way out.

  I use the IMFD, and do an "Off-Plane Intercept", and let it do an "autoburn" which gives me the out of plane component that I need (I just tell myself that it's Mission Control sending the burn data to the SIVB IU, which I understand it how it really happened).  Then, I just need a couple of small MCC's to get things "cleaned up"

If you look at http://www.ibiblio.org/mscorbit/mscforum/index.php?topic=347.15, Tschachim has a nice description of how to do it.  I've managed to get to LOI within about 20 minutes of the historical time, and with about 95% fuel left in the SM when it came time for LOI, and ended up with a pretty decent lunar orbit (about 70 X 110 miles, and a 165 deg inclination).
45  Project Apollo - NASSP / Support & Bugs / Re: CTD when separating CM from SM on: August 02, 2006, 11:27:32 PM
WOW! You did all that overnight?! (or in the past 12 hrs) That's amazing!

Well, it's really just reading the instructions, and knowing that since MS has a new version of VC++ Express, that you need to modify the directories to match where it loads stuff...

I might be dangerous if I knew what I was doing.

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