Meadville Space Center
Welcome, Guest. Please login or register.
November 24, 2020, 02:19:42 AM

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 2267 Members
Latest Member: Apollo Next
* Home Help Search Login Register
+  Meadville Space Center
|-+  Project Apollo - NASSP
| |-+  Project Apollo - NASSP News & Discussion
| | |-+  Support & Bugs (Moderators: movieman, Tschachim, Swatch, lassombra)
| | | |-+  CMC Update Excel Sheet for Excel 2007
« previous next »
Pages: [1] Print
Author Topic: CMC Update Excel Sheet for Excel 2007  (Read 2222 times)
bertog
Full Member
***
Posts: 30

g.bertolino@garellicomputers.com
View Profile
« on: March 27, 2007, 08:29:49 AM »

Hi,

Regarding the DEC2OCT Excel 2007 issue I've tested that the Excel Sheet provide in the doc folder have trouble related at the Excel 2007 function called DEC2OCT.

So I've rename the original function in "irOCT2DECT" and I've made the change in all the sheets.

Attached at this post the 2007 version of CMC Update Sheet. Once opened you have to activate macros

Cheers Guido

* CMC Update 2007.zip (23.09 KB - downloaded 88 times.)
Logged

<< Hey, there it is ! There it is !! Son of a gun, right down the middle of the road !! >> - Pete Conrad
Christophe
Project Team Member
Hero Member
****
Posts: 1072


View Profile Email
« Reply #1 on: March 27, 2007, 10:07:28 AM »

Thanks Bertog. Good work!  Thumbs Up
Logged
Tschachim
Project Apollo - NASSP
Administrator
Hero Member
****
Posts: 3700


nassp.sf.net


View Profile WWW
« Reply #2 on: March 27, 2007, 10:30:55 AM »

Yeah, thanks a lot! I committed your version to CVS, welcome to the Project Apollo developers!  Happy

Cheers
Tschachim
Logged

bertog
Full Member
***
Posts: 30

g.bertolino@garellicomputers.com
View Profile
« Reply #3 on: March 27, 2007, 11:03:13 AM »

Yeah, thanks a lot! I committed your version to CVS, welcome to the Project Apollo developers!  Happy

Cheers
Tschachim

Thank you very much  Very Happy ... I'm glad to help in some way this outstanding project !
Logged

<< Hey, there it is ! There it is !! Son of a gun, right down the middle of the road !! >> - Pete Conrad
kneecaps
Project Team Member
Full Member
****
Posts: 217


36711000 kneecaps@shockpulse.co.uk
View Profile
« Reply #4 on: May 08, 2007, 04:01:31 AM »

Hi,
  Great work on the conversion. I have a slight problem however. I notice that the original spreadsheet takes the time from the AGC memory location, however the modified version requires that you provide GET (via launch and current MJD inputs. What is the reason behind this?

I'm thinking that the GET entry will simply cause the AGC clock to be adjusted rather than changing the calculation of the state vector.

Logged

"Okay. As soon as we find the Earth, we will do it."
- Frank Borman, Apollo 8

Current Work: ?? What next??

Future Work:
I know the AGC pretty well so anything need doing there?

On Hold/Completed:
SPS TVC in P40 issues.
P11 FDAI Error Needles (98%) complete. Comitted. Working A7 scenario.
P06 AGC Standby. Concluded. It's done by the AGC PSU.
Got us a complete AOH Volume II
Christophe
Project Team Member
Hero Member
****
Posts: 1072


View Profile Email
« Reply #5 on: May 08, 2007, 04:45:18 AM »

Hi,
  Great work on the conversion. I have a slight problem however. I notice that the original spreadsheet takes the time from the AGC memory location, however the modified version requires that you provide GET (via launch and current MJD inputs. What is the reason behind this?

I'm thinking that the GET entry will simply cause the AGC clock to be adjusted rather than changing the calculation of the state vector.



Negative! Happy
To update the state vector, the AGC needs to know at what time exactly the new state vector is valid, that's why the entry of the 2 MJD's (orbiter parameters) is required in order for the calculator to compute the GET and then to convert it into the octal numbers acceptable by the DSKY. This does not change the CMC clock time at all.

However you're pointing out something a bit tricky and in my mind responsible for the sometime inaccuracy of vAGC prediction while you've proceed to a state vector update:
I noticed while working on the EOCA that's the CMC clock time may be slightly off the orbiter time. it's very small, something like a few hundredth of seconds, but it may be enough to confuse the prediction. Perhaps it would be better first to update the CMC clock before updating the state vector.

To update the CMC clock you can either:
- Use V55 to increase or decrease the CMC clock. This is possible with the current vAGC version.
- Use the P27 via V70 and update the liftoff time. This feature would be possible too but there is currently no way to compute the octal numbers. I think this should be not so hard and I probably put that later in the CMC update.xls file.

It worth the try, indeed;
Logged
kneecaps
Project Team Member
Full Member
****
Posts: 217


36711000 kneecaps@shockpulse.co.uk
View Profile
« Reply #6 on: May 08, 2007, 06:47:44 AM »

To update the CMC clock you can either:
- Use V55 to increase or decrease the CMC clock. This is possible with the current vAGC version.
- Use the P27 via V70 and update the liftoff time. This feature would be possible too but there is currently no way to compute the octal numbers. I think this should be not so hard and I probably put that later in the CMC update.xls file.

It worth the try, indeed;

So the problem, simply stated is that if you enter the current MJD and the liftoff MJD directly from Orbiter, this can/does differ slightly from the CMC clock.

Also, what should one use as the liftoff MJD. When for CMC calculation purposes should 'liftoff' be defined? It's something like GET +00:00:04
or something ?

Logged

"Okay. As soon as we find the Earth, we will do it."
- Frank Borman, Apollo 8

Current Work: ?? What next??

Future Work:
I know the AGC pretty well so anything need doing there?

On Hold/Completed:
SPS TVC in P40 issues.
P11 FDAI Error Needles (98%) complete. Comitted. Working A7 scenario.
P06 AGC Standby. Concluded. It's done by the AGC PSU.
Got us a complete AOH Volume II
kneecaps
Project Team Member
Full Member
****
Posts: 217


36711000 kneecaps@shockpulse.co.uk
View Profile
« Reply #7 on: May 17, 2007, 07:57:48 AM »

I'm having a problem with the latest CMC Update sheet.

I enabled macros in 2007 when prompted on opening the sheet.

It seems as if the calculations are having problems with some the NEGATIVE (-) values of RPOS and RVEL as found in the scenario file.

These negative values cause the fields they populate (EMEMs) to blank out. Making them positive causes the calculations to work again.

Values from the SCN file are:
-5702015.87
2529418.36
2319158.62

-498.528
4577.431
-6201.615

Any ideas?
Logged

"Okay. As soon as we find the Earth, we will do it."
- Frank Borman, Apollo 8

Current Work: ?? What next??

Future Work:
I know the AGC pretty well so anything need doing there?

On Hold/Completed:
SPS TVC in P40 issues.
P11 FDAI Error Needles (98%) complete. Comitted. Working A7 scenario.
P06 AGC Standby. Concluded. It's done by the AGC PSU.
Got us a complete AOH Volume II
Christophe
Project Team Member
Hero Member
****
Posts: 1072


View Profile Email
« Reply #8 on: May 17, 2007, 03:34:27 PM »

Yeah it seems that there is somrething wrong with the macro or something else. I tried the values you put in your post in the old CMC update file version and that worked well.
In case you lost it I put it in an attached file for download:

* CMC Update.zip (23.01 KB - downloaded 71 times.)
Logged
Christophe
Project Team Member
Hero Member
****
Posts: 1072


View Profile Email
« Reply #9 on: May 17, 2007, 03:38:18 PM »

Quote from: Kneecap
Also, what should one use as the liftoff MJD. When for CMC calculation purposes should 'liftoff' be defined? It's something like GET +00:00:04
or something ?

Still not very clear for me. I'll look at that when I redo the wordfile checklist.

Anyway, that's something needing to be clarified. In NASSP/vAGC, what is exactly the "Range zero"?
« Last Edit: May 17, 2007, 04:28:36 PM by Tschachim » Logged
irnenginer
Project Team Member
Sr. Member
****
Posts: 271



View Profile
« Reply #10 on: May 19, 2007, 11:40:31 PM »

I cannot be too much help with Excel 2003 (which seems to work fine). I can say the macro handles negitive numbers very differently in order to get them expressed properly in octal.

Does it simply blank or does it have an error field?
Logged
Christophe
Project Team Member
Hero Member
****
Posts: 1072


View Profile Email
« Reply #11 on: May 20, 2007, 10:13:21 AM »

I cannot be too much help with Excel 2003 (which seems to work fine). I can say the macro handles negitive numbers very differently in order to get them expressed properly in octal.

Does it simply blank or does it have an error field?

Simply blank I think.
Hi irnenginer; How about your work on the vAGC and the moon vectors?
Logged
kneecaps
Project Team Member
Full Member
****
Posts: 217


36711000 kneecaps@shockpulse.co.uk
View Profile
« Reply #12 on: May 20, 2007, 02:05:04 PM »

I cannot be too much help with Excel 2003 (which seems to work fine). I can say the macro handles negitive numbers very differently in order to get them expressed properly in octal.

Does it simply blank or does it have an error field?

It displays blank, this is however running 2007....I should have never upgraded!! GRRR!!! I can't run the 2003 version due to the OCT2DEC issue.
Logged

"Okay. As soon as we find the Earth, we will do it."
- Frank Borman, Apollo 8

Current Work: ?? What next??

Future Work:
I know the AGC pretty well so anything need doing there?

On Hold/Completed:
SPS TVC in P40 issues.
P11 FDAI Error Needles (98%) complete. Comitted. Working A7 scenario.
P06 AGC Standby. Concluded. It's done by the AGC PSU.
Got us a complete AOH Volume II
Pages: [1] Print 
« previous next »
Jump to:  

Powered by MySQL Powered by PHP Powered by SMF 1.1.10 | SMF © 2006-2009, Simple Machines LLC Valid XHTML 1.0! Valid CSS!