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?
AZOEMEM1711 30636
EMEM1712 33227
Earth's azimuth (279,115422 deg). Constant in Orbiter, thus non-mission specific.
AYO,AXOEMEM1713 to 1716 all 0
earth's precision and nutation. Orbiter's earth doesn't have that.
EMSALTfor LEO entry:
EMEM2017 2
EMEM2020 24622
for lunar entry:
EMEM2017 2
EMEM2020 30420
Altitude when 0.05g occurs. 284843 ft resp. 297431ft. Those are the original values, not tested in orbiter. Should work, anyway.
TVC/DAPEMEM3012 5
EMEM3013 200
EMEM3014 100
EMEM3015 0
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
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?
DVTHRESHEMEM1353 632
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,ALFAPADEMEM3007 6632
EMEM3010 3146
EMEM3011 74344
Presettings for entry DAP. Figured out by me some time ago. Work quite good.
HORIZALTEMEM1354 0
EMEM1355 21450
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,WRENDVELEMEM2000 240
EMEM2001 754
Initial settings for P20's w-matrix. No source known, but any small value <> 0 is good (0 would render P20 inoperative).
RMAX,VMAXEMEM2002 77776
EMEM2003 77776
Thresholds for FL V06N49. Set to some very low value, so that every mark leads to N49.
WORBPOS,WORBVELEMEM2004 1750
EMEM2005 3146
P22' w-matrix. Same problem as for P20, same 'solution'. Delco suggests 0 for both.
ATIGINCEMEM2021 0
EMEM2022 21450
P35's time from final pass to TPM-burn. 90 sec seemed a good value.
PTIGINCEMEM2021 0
EMEM2022 21450
P75's time from final pass to TPM-burn. Again, 90 sec seemed a good value.
WMIDPOS,WMIDVELEMEM3000 5161
EMEM3001 311
P23's w-matrix. See WORBPOS & co.
YACTOFF,PACTOFFEMEM3025 0
EMEM3026 0
SPS trim angles. Both 0, as our SPS engine has no offset from CSM's center of mass.
ECSTEEREMEM3424 0
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.
CDUCHKWDEMEM1341 0
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:EMDOTEMEM0110 ?
EMEM0111 ?!
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?
RPVAREMEM2007 ?
'Variance of the primary body radius error', to quote GSOP 5.2-52. Used by P22. Suggestions?
RVAR,RVARMINEMEM3002 ?
EMEM3003 ?
EMEM3004 ?
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:?
ALTVAREMEM1356 ?
'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:?
INTVAREMEM2177 ?
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:?
S22WSUBLEMEM2006 ?
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.
504LMEMEM2011 ?
?
?
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:POLYNUM,SATRLRT,RPSTART,POLYSTOP
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?