AO2: Adjusted PaO2 up slightly to ~93 to keep O2_V below 9.5, esp. since it crept up to ~10.15 during RF02 Breath Test: 18:32:45-->18:33:45 See 100329_RF02_InletBreathTest1.png Observation: No discernable peaks. Delayed Cal at 19:23ish to get in missed approach at Cold Bay 19:32:03 Restored calInt to 50 (purging) Bad turbulence during descent into Kona. Seems to reflect in cal. Allowed system to cal, and switched inlet to purge at 02:15:40 because turbulence would probably make opening valves any later impossible. Will lose last 5-10 mins of data going into Kona as a result. Post-processing 141113: TCRYO climbs at very end of flight MED: 19:52ish Flask 11, b1174, broke while closing 20:52 Flask 16, b1318, broke while closing Conclusion: New foam is too dense/hard, and causes flasks to become brittle during shipment... 22:20ish, MEDUSA system rebooted, at position 24, sending air flow to bypass. I didn't notice this until about 23:00, and then spent some time trying to determine why this had happened. I reran prepurge, and samples 1-23 and am now purging pos 24 again. This suggests a problem in the MEDUSA code However, since the DSM was having trouble around 22:01, when pos 24 happened to be engaged it's possible that the DSM caused MEDUSA to be unable to register its valve position, ultimately causing it to reboot., Around 01:00 lost P control because we headed to 41Kft. I'm letting the system stay in 130/580 for now since we will soon be dropping back down, and sampling at the higher flow rate Inlet P is only off by 3-4 torr (126ish) BLINKING VALVESTAT SIGNALS MEDUSA is clearly having some problems interpreting valve stat signals. Problem seems to happen every few (5-10) seconds for a second or two. Every few seconds, now in position 31, values blink. Trying to see whether disconnecting Valve Stat1 line to DSM helps. 01:12:55 disconnected ValveStat1 problem still occuring 01:13:50 disconnected Valvestat2, reconnected VS1 problem stops occuring (appears to) 01:17:20 reconnected VS2 problem reoccurs, but occasionally seems to go away for 30 or so secs at a time. Not convinced that disconnected vs2 really helped. Trying again 01:21:40 disconnecting VS2 Seems to go away while VS2 is disconnected. 01:24:?? Reconnecting VS2 All this time, AEROS is having some issues. it's possible this is linked to a bug in the DSM AEROS did, indeed crash, around 01:10, and is then returned to online status at 01:27 01:32 Still occasionally seeing blinking, though. PAVEL: Planning and Vehicular Expidiency Liason