Meadville Space Center
Welcome, Guest. Please login or register.
August 07, 2020, 03:42:55 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
+  Meadville Space Center
|-+  Project Apollo - NASSP
| |-+  Project Apollo - NASSP Development
| | |-+  Programming (Moderators: movieman, dseagrav, Swatch, lassombra)
| | | |-+  TVC DAP is a Go
« previous next »
Pages: [1] Print
Author Topic: TVC DAP is a Go  (Read 1177 times)
irnenginer
Project Team Member
Sr. Member
****
Posts: 271



View Profile
« on: March 06, 2006, 12:52:05 AM »

I am on my last verification run with padload values for the TVC DAP for the CSM by itself. The Magic numbers are

  EMEM3012 5
  EMEM3013 200
  EMEM3014 100
  EMEM3016 30000
  EMEM3017 2000
  EMEM3020 20000
  EMEM3021 500
  EMEM3022 4000
  EMEM3023 1000
  EMEM3024 1000
  EMEM3027 10000
  EMEM3030 75024
  EMEM3031 47207
  EMEM3032 1066
  EMEM3033 33013
  EMEM3034 77705
  EMEM3035 61340
  EMEM3036 57377
  EMEM3037 74664
  EMEM3040 14414
  EMEM3041 36243
  EMEM3042 74624
  EMEM3043 73117

Thanks goes to Tschachim for getting close, I just tweaked to make them work better. For those following how the numbers are. EKPRIME is a very important number, though not mentioned in the docs at all. Any number over 200 the spacecraft goes unstable. EKTLX/I is set about as high as it will go. Any higher and it throws a program alarm 1202.

The DAP is VERY stable now. I have run 3 P30/40 burns with 0 residuals, all the while using the RCS in a attempt to throw it off. It is fun to set the Rate scale to 5/1 and watch the DAP correct for RCS thrusts (remember to use the keyboard, the RHC is not enabled to run RCS during burns)

Despite all this P37/40 burns still throw a program alarm 1407. I think that this may be a problem in the Colossus code. I saw widely crazy delta V BEFORE the burn even began. I did have the burn complete once with the alarm and it seemed to work fine from a DAP point of view.

This load seems also to cause a program alarm 1107 (phase table error, assume erasable memory destroyed) on startup. But just ignore it.

I will hold off committing this for Apollo 8 to give a chance for someone to find a bug. Note I did not work on the CSM/LM numbers since I wanted to get apollo 8 working first.
Logged
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!