As already stated, it is deemed necessary to standartize the non-mission-specific EMEMs for Colossus 249. I took a look and made out the following (any remarks and/or corrections are welcome):
@Tschachim: I consider to put those on a extra sheet in the .xls and leave the others on the resp. mission tap. Concur?AZO
Earth's azimuth (279,115422 deg). Constant in Orbiter, thus non-mission specific.AYO,AXO
EMEM1713 to 1716 all 0
earth's precision and nutation. Orbiter's earth doesn't have that.EMSALT
for LEO entry:
for lunar entry:
Altitude when 0.05g occurs. 284843 ft resp. 297431ft. Those are the original values, not tested in orbiter. Should work, anyway.TVC/DAP
The whole TVC/DAP config stuff, works well with CSM alone. No idea what happens when we add the LM, though. Those are the values from the .scn, the .xls says different for some. Does anybody know the reason for that?DVTHRESH
AFAIK the 'engine fail' threshold; CMC will switch to engine fail routine if DVTHRESH isn't attained after engine on command + some (very short) time.LADPAD,LODPAD,ALFAPAD
Presettings for entry DAP. Figured out by me some time ago. Work quite good.HORIZALT
P23's horizon altitude, i.e. the distance between the point the astronaut marks on and the 'real' horizon. This is Jim Lovell's value he used on AP8. Could be refined a little, but works.WRENDPOS,WRENDVEL
Initial settings for P20's w-matrix. No source known, but any small value <> 0 is good (0 would render P20 inoperative).RMAX,VMAX
Thresholds for FL V06N49. Set to some very low value, so that every mark leads to N49.WORBPOS,WORBVEL
P22' w-matrix. Same problem as for P20, same 'solution'. Delco suggests 0 for both.ATIGINC
P35's time from final pass to TPM-burn. 90 sec seemed a good value.PTIGINC
P75's time from final pass to TPM-burn. Again, 90 sec seemed a good value.WMIDPOS,WMIDVEL
P23's w-matrix. See WORBPOS & co.YACTOFF,PACTOFF
SPS trim angles. Both 0, as our SPS engine has no offset from CSM's center of mass.ECSTEER
Cross product steering constant for P31. Range from -4 to +4. See GSOP 5.3-24 for further info. We don't use P31, so I recommend leaving it 0.CDUCHKWD
SXTMARK CDU CHECK DELAY. Used in R53. When not 0, CMC will check after mark button has been pressed and the time defined in CDUCHKWD has elapsed if optic CDUs have changed by more then 3 bits. If yes, alarm 121 is issued and R53 exits. This is some sort of CDU operational test. Our CDUs can't fail, so I recommend 0.Obviously non-mission specific, but still unkown to me:EMDOT
SPS flow rate, i.e. the mass lost during 1 sec of SPS burn. 7 and 8 have EMEM0110 1116 in the .scn, but the .xls offers EMEM0111(sic!) 1116 for 7 and EMEM0110 1045 & EMEM0111 34325 for 8. Anyone any idea?RPVAR
'Variance of the primary body radius error', to quote GSOP 5.2-52. Used by P22. Suggestions?RVAR,RVARMIN
RVAR is the 'range error variance corresponding to a percentage error' and RVARMIN is the 'minimum range error variance'(GSOP 5.2-78). Used in P20 for the VHF ranging. Delco: 0 for RVAR, (200 ft)² for RVARMIN. Scaling:?ALTVAR
'A priori estimate for the angular error variance of an alternate line-of-sight measurement per axis'(GSOP 5.2-83). Used in P20 when the SXT isn't used for marks on the LM. Delco: (3.9mrad)². Scaling:?INTVAR
According to GSOP 5.2-77 is this the variance of the coasting integration error, i.e. how good the coasting integration routine of the SVs works. Delco says: (14 m) ². Scaling:?S22WSUBL
Third diagonal component of P22's w-matrix. I guess this depicts the error in the landmarks altitude. 0 is no good, I presume the same scaling as WORBPOS and WORBVEL. Delco says 10000m as a value. Still got to find out the scaling, though.504LM
Moon's libration vector(GSOP5.5-16). This has to be a vector, so we need 3 adresses and not 1. Values unkown. Do we need them, anyway? Does orbiters moon have any libration?The whole IMU compensation stuff (SFE,BIAS,ADIA,ADSRA,NBD)
Do we need that? I don't know anything about our IMU...Others, but known to me and yet to be determinated:
Saturns roll/pitch programm in CMC language. I won't change anything on them, facing the dawn of LVDC++.
Edit: I'm currently digging around in literature, so this post was and will be subject to edits. So don't wonder.
Edit2: Gets ahead quite fast.
Only 7 EMEMs left; rough values for all but one of them.
Edit3: I dug around in the code a bit and found out that obviously some adresses are completely wrong and some are shifted by 1. Am I reading the code wrong or is the .xls wrong?