![Transcription Center logo](/themes/custom/tc_theme/assets/image/logo.png)
This transcription has been completed. Contact us with corrections.
MAVS 1, 2 & 3 are in 3 gas cans. MAVS experiments are German. (MEA are U.S. investigators). All 3 MAVS EXPS can be operated simultaneously, (+ concurrently with MEA). [[left margin]] DFVLR (W. Ger Gov't Agency)→ [[pointing to German]] [[left margin]] MAVS 1 (A) (Guenter Otto) lasts 84 hrs, with "cooldown" perios ~ every 24 hrs • During these periods, VRCS accelerations levels are maximum allowable (and are sufficiently "quiet" - GG or free drift not req'd) • MAVS EXP's can be operated simultaneously (all are independent) • EXP's not sensitive to PRCS during non-cooldown (low-G) portions....OMS burn o.k.? MAVS 2 ≡ Margoni convection in floating zone (similar to SPAS-01 MAVS) MAVS 3 ≡ solidification front (particle size no crystal growth) [MAVSES all contain furnaces] • MEA requires "view" of space, to radiate heat [taking it to stby activates, among other things, freon pumps in MEA] • specifically - need a list of software conditions which cause ① MAVS shutdown ② MEA shutdown can they be restarted? (physically possible? allowed by flight rules?) • MAVS....if one shuts down can it be restarted, or do you destroy existing data? • what does "deact" do? ... is it reversible? [need schematics?] NOTE: logging of on/off times ("+- 1 sec") is to correlate EXP to ORB accelerations. But DSTA data is avg over 1 sec....this is not critical (± a couple of sec)