Neutral Gas Ion Mass Spectrometer (NGIMS) NGIMS Post Launch Check Out For CONTOUR NGIMS Contributors: Prepared by: _______________________ _______________________ Alice Bowman Florence Tan _______________________ Jaime Demick _______________________ Wayne Kasprzak _______________________ Paul Mahaffy _______________________ Eric Raaen Approved by: _________________________ Jack Richards NGIMS Instrument Manager 1.0 Scope This document describes the post launch check out procedures (STOL scripts and SEQGEN sequences) that will be run during the post launch period in August and Sept 2002 for the Neutral Gas Ion Mass Spectrometer (NGIMS) 2.0 Overview The NGIMS instrument will be turned on for post-launch checkout only after the Solid Rocket Motor (SRM) burn on August 15, 2002. The post launch activity time line can be found in Appendix A or on the CONTOUR website at: https://sd-forum.jhuapl.edu/CONTOUR/. 3.0 References 1. All NGIMS scripts, CAS', and fragments called out in Appendices. 2. NGIMS Telemetry Format document NGIMS-FSW-06-telemetry-v2_9.doc 3. NGIMS Telemetry Data Format NGIMS/GSFC-FT02 4.0 Nomenclature Sequence and scripts may have a suffix "v" denoting revision numbers. As of May 20, 2002, "v" equals "D" or "d". 5.0 NGIMS checkout description The post launch checkout consists of two parts. Part 1 is the first opportunity to turn on the instrument, after the SRM burn, during the period, August 17th - 22nd 2002. The spacecraft will not be 3-axis mode during this period, as such, real time data cannot be guaranteed. Test 1 of NGIMS' checkout will consist of a power-on using MO_ngims_pwrup.prc (which includes a TM On), and power-off using MO_ngims_pwrdn.prc with data recorded in the SSR and replayed back to the ground. This test will allow NGIMS engineers to evaluate the health of the instrument in advance of Part Two of the checkout. Part Two of the checkout will occur during the September 8th to September 21st, 2002 period. Preliminary estimates for staffed DSN coverage (or real time data transmittal) are TBC1 hours per day. Since we need to monitor some state of health parameters in real time, we will run the test over TBD2 days. For Test 2, as general checkout, NGIMS will power up (MO_ngims_pwrup.prc), perform a memory dump (MO_ngims_mem_dump.prc), and check sensor pressure using MO_ngims_BALoEmis.prc and MO_ngims_BAHiEmis.prc in real time. In the event that the sensor pressure is too high (BA Out > 100 pA in Low Emission or High Emission BA Out > 1000 pA), NGIMS must not continue the sensor checkout. In that case, NGIMS should monitor the pressure using the MO_ngims_BALoEmis.prc and MO_ngims_BAHiEmis.prc scripts in real time repeating the test a day apart for up to 4 days. If the pressure drops to "safe" levels, NGIMS will proceed with the checkout and run the sensor checkout pre-breakoff sequenced Baseline1-3 in low emission. Next, to establish pre-load instrument status, NGIMS will run the low emission functional script (MO_ngims_functional19a.prc). Then, because pre-launch tests show mass shifts, NGIMS will load a new config table (MO_ngims_PatchCFG72.prc) that will shift and widen sensor and spectra peaks. To confirm the load, NGIMS will dump (MO_ngims_DumpSubScans.prc) from the config table area and compare with the expected image. Finally, NGIMS will run the MO_ngims_functional19a.prc script to verify new config table settings. If the new config table loads do not correctly shift the mass peaks, and because it may take time to query and analyze the data, NGIMS will power down using MO_ngims_pwrdn.prc allowing a day to determine the next operation. If the new tables are not successful, NGIMS needs a contingency day (Test 3) to reload the old config table (MO_ngims_PatchCFG69b.prc) to restore the system back to old settings before continuing with the next tests. In addition, NGIMS will dump memory and compare (MO_ngims_DumpSubScans.prc) and run the MO_ngims_functional19a.prc script as a verification of the load. For Test 4, NGIMS will perform Pyro Break Off and Rupture Valve operations. Prior to the Pyro Break Off, NGIMS will power up (MO_ngims_pwrup.prc) and perform two functional checkouts, potentially in high emission (MO_ngims_functional20a.prc), and another in low emission (MO_ngims_functional19a.prc). The functional checks include a pressure check at the start and sensor pressure must be monitored. If sensor pressure is too high, the checkout must not continue. The reason for the two functional scripts is to track sensor operation. Previously, NGIMS has always run functional tests in low emission. Performing a low emission functional check prior to Pyro Break Off provides another data point in tracking the performance of the sensor. However, the high emission functional check, a more risky check in pre-break off state, may be skipped if time pressures arises. The instrument must be powered off (MO_ngims_pwrdn.prc) to perform the Pyro Break Off. The Pyro Break Off commands are spacecraft generated commands (Test 4A) and pyro fire commands must be separated by 5 seconds. The spacecraft operator can verify that the pyro arm commands were executed by looking at the telltale in the C & DH Telemetry (see Test 4A) page. The fire commands have no indicator bit in the telemetry page. Upon Pyro Break Off, the residual gasses in the sensor will outgas into the vacuum of space. If we run a functional in low emission to check the operation of the sensor after the break off, we will most likely have very low signal. Thus, we anticipate that all functional checkouts after the pyro break off will have to be performed in high emission to capture any meaningful data. Time permitting, we therefore decided to run a functional script in high emission prior to the pyro break off to establish the pre-break off state of NGIMS in high emission. After the Pyro Break off, NGIMS will monitor sensor pressure in low and high emission to verify low pressure (Test 4B - MO_ngims_pwrup.prc, MO_ngims_BALoEmis.prc, MO_ngims_BAHiEmis.prc, MO_ngims_BAOff.prc). If sensor pressure remains too high, then it may be either the break off did not occur or the BA pressure gauge was damaged. If the pressure still reads high, we will power off and re-run Test 4B to refire the Pyro. And Test 4B rerun shows no effect, NGIMS will proceed to check out the sensor in low and high emission (Test 4C) but being prepared to turn off immediately if high counts are observed. Depending on DSN coverage, the low and high emission functional checks can occur the next day if there is not enough time to check out the sensor. If there is not enough time and the pressure reads as expected, the low emission functional check can be skipped and only the high emission functional check can be run. Next, the Rupture Valve commands (Test 4D) can be run. If the rupture valve commands directly follow the high emission functional (which includes a pressure check), then it is unnecessary to monitor sensor pressure (MO_ngims_pwrup.prc, MO_ngims_BALoEmis.prc, MO_ngims_BAHiEmis.prc, MO_ngims_BAOff.prc, but run MO_ngims_CalLeakHi.prc) and the rupture valve commands can take place (NGI_RUPTURE_Val_Pwr ON, MO_ngims_Valve2Close.prc, MO_ngims_Valve1Close.prc, MO_ngims_Valve1Open.prc (2X), NGI_RUPTURE_Val_Pwr OFF). There must be at least a one second wait between the valve 1 close commands and the valve1 open commands and a 5 second wait between each valve open set of commands. Again, the test conductor must verify that the rupture commands occurred. Following the puncture of the rupture valve, NGIMS shall perform a coarse pressure reference by running the pressure check suite of commands. To confirm Valve 2 operation after rupture, NGIMS will run the MO_ngims_CalLeakHi.prc script and power down. Test 5 is used to established the Cal Cell leak rate. It consists of opening valve 2 (MO_ngims_Valve2Open.prc) and letting the sensor pressure stabilize to an operational point. Valve 2 is the valve to the calibration cell. See Appendix H for timing diagram. While the gas is leaking out of the calibration cell, NGIMS must monitor the pressure of the sensor (MO_ngims_BALoEmis.prc) in real time. It is imperative that Valve 2 be opened at the beginning of a long 8-hour DSN coverage to allow real time monitoring of pressure. We estimate that within less than an 8 hour period, the pressure will drop to a safe level (BA Out < 100pA in Low Emission) to allow pressure in high emission. NGIMS can probably transition to the high emission pressure check (MO_ngims_BAHiEmis.prc) during the same DSN coverage. After the current day's DSN coverage is over, in the next 16 hours, NGIMS can then keep monitoring the pressure using high emission pressure (SEQUENCED) checks every hour if possible, and at the minimum, every 4 hours (Test 6). Each pressure check must be run for at least 10 minutes. The data will be transmitted to the SSR to be stored and transmitted to Earth at the next DSN pass. We assume that the data from the pressure check will be quickly available so that we can analyze the SSR data to plan for the next round of tests. The caveat is that the pressure in the cell should not be allowed to drop below 66 torr. For a failsafe operation, NGIMS should establish a sequenced close valve 2 macro after a maximum of 20 hours to prevent gas from leaking out longer than necessary. Laboratory data showed that the pressure will drop from 350 torr to 66 torr after more than 30 hours. If it looks as if the pressure will drop below 66 torr during the non-real time hourly checks, we will stop the calibration gas from leaking out by closing valve 2 (MO_ngims_Valve2Close.prc) and wait until real time coverage is available. When real time data is available, NGIMS will re-open valve 2 (MO_ngims_Valve2Open.prc) and monitor the pressure decay (MO_ngims_BaHiEmis.prc) in real time. If, during real time monitoring the pressure has fallen to about 66 torr, NGIMS can zero in on the appropriate pressure by opening valve 2, running pressure check in high emission, and closing valve 2, and watching the pressure. When 66 torr is achieved, NGIMS will turn on the sensor (first low emission, then repeat in high emission) and obtain fractional mass spectra from 1-300 amu in the CS and OS using MO_ngims_CalDecayLo.prc and MO_ngims_CalDecayHi.prc scripts. The step to monitor counts and pressure may be repeated numerous times until the optimum pressure/count combination is achieved. Finally, valve 2 will be closed (MO_ngims_Valve2Close.prc), and NGIMS will perform high emission Fractional Mass 1-300 CS and OS to check for leaks in valve 2 again (MO_ngims_CalLeakHi.prc). A contingency config table load is planned for Day 8 if necessary. The following chart summarizes post launch operations for NGIMS. Note that each NGIMS day does not reflect consecutive days. See section 5 for detailed notes on each test. Test Goal Test functions Script names Type Data flow/actions req MO_ngims_PostLaunch_Test1.prc 8/17/02 to 8/22/02 (5 min) Check if NGIMS survives launch and SRM burn. Power up collect TM data for 2 minutes Power down MO_ngims_pwrup.prc MO_ngims_pwrdn.prc STOL STOL Data transmittal at 1.59 Kbps. NGIMS TM rate = 3123.2 bits/sec excluding spacecraft overhead. It may be a problem to obtain real time data. Assumptions: SSR data available prior to Test 2. MO_ngims_PostLaunch _Test2a.prc (20 min) No earlier than 9/8/02 - Instrument CheckOut period starts 9/8/02 Sensor checkout - date contingent on successful G&C checkout - as soon as possible. * Check if NGIMS survives launch and SRM burn. * Detailed checkout using NGIMS Baseline. * Continue gathering test data from pre-launch testing - run Functional test in low emission. * Load and verify new config tables to handle mass shifts * Run low emission functional test to verify tables MO_ngims_pwrup.prc MO_ngims_mem_dump.prc (6min) MO_ngims_BALoEmis.prc (7min) MO_ngims_BAHiEmis.prc (7min) MO_ngims_pwrdn.prc STOL STOL STOL STOL STOL Data will be available in real time at 85Kbps. Spacecraft in 3 axis mode. If pressure too high (BAOUT low emis > 100pA), DO NOT continue with hi emis BA check, sensor checkout. Monitor pressure, repeat a day apart for 4 days?? MO_ngims_PostLaunch _Test2b.prc (2.5 hrs) Baseline Low Emis - includes a power up in the sequence. Change sequenced baseline to low emis. Add pwrdn. CAS_NGIMS_StartUpSeq CAS_NGIMS_BaselineLo1D CAS_NGIMS_BaselineLo2D CAS_NGIMS_BaselineLo3D CAS_NGIMS_pwrdn SEQ SEQ SEQ SEQ SEQ Data will be available in real time at 85Kbps. Do baseline if pressure drops. If still too high, no baseline and no load new table (do after pyro breakoff). Power off in sequenced baseline to stop if necessary. Proceed directly to Test2c if time permits. MO_ngims_PostLaunch _Test2c.prc (1.5 hrs) Load at 500 b/s Power up Functional Low Emis Load new table #1 Dump and compare Functional Low Emis Power down MO_ngims_pwrup.prc MO_ngims_functional19a.prc (40 min) MO_ngims_PatchCFG72.prc (6 min3) MO_ngims_DumpSubScans.prc (2 min) MO_ngims_functional19a.prc (40 min) MO_ngims_pwrdn.prc STOL STOL STOL STOL STOL STOL Data will be available in real time at 85Kbps. Delay 8 hours to verify data MO_ngims_PostLaunch _Test3.prc (contingency) (1 hr) Reload old table if new table not successful Power up Re-Load old table (plus masstables) Dump data and compare Functional Low Emission Power Down MO_ngims_pwrup.prc MO_ngims_PatchCFG69b.prc (6 min) MO_ngims_DumpSubScans.prc (6 min) MO_ngims_functional19a.prc (40 min) MO_ngims_pwrdn.prc STOL STOL STOL STOL STOL Data will be available in real time at 85Kbps.. Only restore what was changed in Test2c If Instrument Pressure too high, do not do. MO_ngims_PostLaunch _Test4a.prc (80 min) Check out NGIMS before breakoff (low and high emission) Power Up Functional Low Emission Functional High Emission MO_ngims_pwrup.prc MO_ngims_functional19a.prc (40 min) MO_ngims_functional20a.prc (40 min can skip) MO_ngims_pwrdn.prc (can skip) STOL STOL STOL Data will be available in real time at 85Kbps. Run Pre-pyro Breakoff Functional with Low Emission (v 19d for tracking data) and High Emission (v 20a to capture the pre-breakoff status) to see current state of instrument. If Instrument Pressure too high, do not do either functional. If pressure OK, then proceed. MO_ngims_PostLaunch _Test4b.prc (25 min) Break off NGIMS cover - Pyro breakoff Power down Pyro Break Off MO_ngims_pwrdn.prc NGI_PRI_CAP_ARM ARM NGI_SEC_CAP_ARM ARM PS_PRI_PYRO_FIRE ENABLE PS_SEC_PYRO_FIRE ENABLE STOL STOL STOL STOL STOL Telltale on HK telemetry Primary: CDH(1,2)_PSE_NGIM_CARM1 Secondary: CDH(1,2)_PSE_NGIMS_CARM2 (Safe=0, Arm=1) Verify arming was OK. No telltale on fire pulse. Wait 5 seconds between pyro fire commands Do this TWICE at MOST MO_ngims_PostLaunch _Test4c.prc (80 min) Verify Pyro break off Verify pressure lowered by the vacuum of space. MO_ngims_pwrup.prc MO_ngims_BALoEmis.prc (10 min) MO_ngims_BAHiEmis.prc (10 min) MO_ngims_BAOff.prc MO_ngims_pwrdn.prc (can skip this) If 4B not good, then do Test 4C again STOL STOL STOL STOL STOL It is preferable that this test as soon as Test 4a completes but next DSN pass is also OK. Data will be available in real time at 85Kbps. If instrument pressure too high, run pressure check twice more, 2 days apart to monitor pressure. If pressure is too high, then we have a problem - did we really break off or was BA gauge damaged? Retry break off again. If BA damaged, we can't know what the pressure is. If we verified that break off occurred, then run functional (preparing to turn off immediately if we see high counts). MO_ngims_PostLaunch _Test4c.prc (contingency) (1 hr) Check out NGIMS after breakoff (low and high emission) Functional Low Emission Functional High Emis MO_ngims_pwrup.prc (can skip this) MO_ngims_functional19a.prc (40 min -if pressure v low, skip to 20a) MO_ngims_functional20a.prc (40 min) MO_ngims_pwrdn.prc (can skip) STOL STOL STOL STOL STOL Data will be available in real time at 85Kbps. Run Functional19a (lo emission), followed by Functional20a (hi emission) if BA pressure normal (Should observe a very clean mass spectrum. If 2nd break off still show high pressure, run Functional19a/20a anyhow, preparing to turn off immediately if see high counts. (If in doubt, always execute baseline primarily to see if anything has shorted out or if there are any other.) Problems from an electronic point of view; lens scans and mass spectra are going to be almost useless without a major gas source- (we believe the sensor will be very clean, maybe -Schedule contingency or backup time for potential problems. MO_ngims_PostLaunch _Test4d.prc (3 hr) Rupture Valve operations: Check out NGIMS before rupture (low and high emission) Rupture valve 1 Check out NGIMS after rupture (low and high emission) Coarse pressure reference Rupture Valve Coarse pressure check Check for leaks after rupture Power down MO_ngims_pwrup.prc (can skip this) MO_ngims_BALoEmis.prc (can skip) MO_ngims_BAHiEmis.prc (can skip) MO_ngims_BAOff.prc (can skip) MO_ngims_CalLeakHi.prc (50 Min) NGI_RUPTURE_VAL_Pwr ON MO_ngims_Valve2Close.prc Wait 1s MO_ngims_Valve1Close.prc wait 1 s MO_ngims_Valve1Open.prc Wait 5 s MO_ngims_Valve1Open.prc NGI_RUPTURE_VAL_Pwr OFF MO_ngims_BALoEmis.prc (10 min) MO_ngims_BAHiEmis.prc (10 min) MO_ngims_BAOff.prc MO_ngims_CalLeakHi.prc (50 min) MO_ngims_pwrdn.prc (wait is not necc, can skip) STOL STOL STOL STOL STOL STOL STOL STOL STOL STOL STOL STOL STOL STOL STOL STOL Depending on DSN coverage, the rupture valve scripts may follow immediately after the Pyro breakoff and the pressure check in low and high emission scripts may be skipped. If bad DSN coverage break, then we need to get a course pressure reference. Data will be available in real time at 85Kbps. Verify Rupture Valve operation in RT, monitor no change in pressure. Verify no leak across calibration cell. If leak, restart 4D from BALoEmis.prc to MO_ngims_CalLeakHi.prc to reseat valve and check leak. Make sure Valve 2 is closed before operating rupture valve (valve 1)! Wait 1 second betw close and open valve. Wait 5 seconds each valve open proc. If BA Emis shows > 100pA, do not proceed to high emission. BA High Emission Test- if BA high is OK (<1000pA) turn off BA gauge and proceed to CalLeakHi.prc. If BA high is >1000pA, turn off BA and repeat after waiting. NOTE: nominal BA high = 300pA. Check for leaks after rupture. Run MO_ngims_CalLeakHi.prc To establish Valve 2 is properly sealed. This test will scan in both low and high emission to determine if gas from the calibration cell is leaking through valve 2 after rupturing valve 1. Can do Test 5 at earliest chance. MO_ngims_PostLaunch _Test5.prc (8 hrs) Collect data to establish leak rate (Release Cal Gas, get leak data, calculate leak rate) ie. Open Valve 2 and determine, via the BA Gauge, the decay rate for conditioning calibration cell Power Up Open Valve 2 Pressure Check lo emis Power Down MO_ngims_pwrup.prc MO_ngims_Valve2Open.prc MO_ngims_BALoEmis.prc (may be a long test) MO_ngims_BAHiEmis.prc (may be a long test) If all OK, jump to Test 6. MO_ngims_Valve2Close.prc(can skip) MO_ngims_BAOff.prc (10 minutes after closing valve 2) MO_ngims_pwrdn.prc (can skip) STOL STOL STOL STOL STOL STOL STOL Data will be available in real time at 85Kbps. (need 8 hrs total) - if 2 hr DSN coverage available, OK to run in "chunks". If, DSN coverage ends, wait until the next DSN pass to go on. If all OK, can skip to Test 6 without closing valve. Need approx 12 hours to calculate time period to keep Valve 2 open to establish cal cell pressure in test 6. Decay time estimated to be 30 - 40 hrs MO_ngims_PostLaunch _Test6a.prc 20 hours Condition Cal cell. Once an optimal pressure is reached, obtain spectra in both sources in low and high emission with the calibration gas. Power Up Open Valve 2 Pressure Check lo emis Pressure Check hi emis Pressure Check hi emis Close Cal Cell to prevent overleakage MO_ngims_pwrup.prc (can skip) MO_ngims_Valve2Open.prc(can skip) MO_ngims_BALoEmis.prc (can skip) MO_ngims_BAHiEmis.prc (can skip) MO_ngims_BAOff.prc MO_ngims_pwrdn.prc Do for 10 min every hour CAS_NGIMS_PressureChk_Hi Contents: MO_ngims_pwrup.prc MO_ngims_BAHiEmis.prc MO_ngims_BAOff.prc (10 min) MO_ngims_pwrdn.prc CAS_NGIMS_CloseCalCell Contents: MO_ngims_pwrup.prc MO_ngims_BAHiEmis.prc MO_ngims_Valve2Close.prc (20 hrs after the first valve 2 open in Test 6A) MO_ngims_BAOff.prc (10 min after valve 2 closes) MO_ngims_pwrdn.prc STOL STOL STOL STOL STOL STOL SEQ SEQ Data will be available in real time at 85Kbps. Can do if 2 hr coverage available. Stay on as long as possible/ necessary. DSN coverage ends. RT/SSR (non RT, discrete), make sure data readily available. May be able to use Time Tag Macros to repeat each seq 4 or 5 times. Close Valve 2 after 20 hours in SEQ or STOL (if DSN coverage allows it) to prevent too much pressure drop. If RT data available in DSN pass, and need to open or close valve, do so. If DSN timing coverage is such that PressureChk_Hi & the CloseCalCell sequences can be performed in RT, we will run these functions in RT. MO_ngims_PostLaunch _Test6b.prc Run pressure Check Close valve 2 MO_ngims_pwrup.prc MO_ngims_BAHiEmis.prc MO_ngims_Valve2Close.prc MO_ngims_Valve2Open.prc MO_ngims_pwrdn.prc STOL STOL STOL STOL Get data from SSR. Delay 8 hours to allow for data playback and analysis. Do Test 7 at earliest chance. MO_ngims_PostLaunch _Test7.prc (6 hrs) Cal cell health check - prepare for sensor turn on, turn on sensor, check for leaks. Then repeat CalLeakHi. Power Up Open valve 2 Pressure Check hi emis Close valve 2 Open Valve 2, low emission, flat and frac mass OS/CS spectra, Close Valve 2, initmode Open Valve 2, low emiss, flat, hi emiss, flat and frac mass OS/CS spectra, Close Valve 2, initmode Check for leaks - OS/CS spectra (2 hrs), power down MO_ngims_pwrup.prc MO_ngims_Valve2Open.prc MO_ngims_BAHiEmis.prc (10 min) MO_ngims_Valve2Close.prc MO_ngims_BAOff.prc (10 min after Valve 2 closing) MO_ngims_CalDecayLo.prc MO_ngims_CalDecayHi.prc (iteration can be > 2 times) MO_ngims_CalLeakHi.prc MO_ngims_pwrdn.prc STOL STOL STOL STOL STOL STOL STOL STOL Data will be available in real time at 85Kbps. Keep monitoring pressure, if pressure attained, close valve 2. Verify cal cell conditioning was correct. RT (continuous) RT - Verify no leaks Wait 1 day minimum to do Test 8 Test 8 Contingency table load if spectra shift Table load (contingency) Dump data and compare Functional Low Emission MO_ngims_pwrup.prc MO_ngims_PatchCFG73.prc MO_ngims_loadft??.prc MO_ngims_DumpSubScans.prc MO_ngims_DumpFlat.prc MO_ngims_functional19a.prc MO_ngims_pwrdn.prc STOL STOL STOL STOL STOL STOL STOL Data will be available in real time at 85Kbps. RT RT RT RT RT 5.1 Script description This section describes NGIMS scripts that will be run during the post launch check out period. Some scripts have names that are self explanatory and are not included here. MO_ngims_functional19a.prc This script performs: * EEPROM and RAM dumps * Electrode short test * Instrument Pressure Check - BA Low Emission. If instrument pressure too high, do not continue.* * If Lo Emiss OK, continue with instrument pressure check - BA High Emission. If instrument pressure too high, do not continue.* * If BA High Emiss OK, continue with rest of functional with ion source filaments in low emission. MO_ngims_functional20a.prc This script performs: * EEPROM and RAM dumps * Electrode short test * Instrument pressure check - BA Low Emission. If Instrument Pressure too high, do not continue.* * If Lo Emiss OK, continue with instrument pressure check - BA High Emission. If instrument pressure too high, do not continue.* * If BA High Emiss OK, continue with rest of functional with ion source filaments in high emission. MO_ngims_CalDecayLo.prc This script assumes that pressure is optimal for filament operation. * Open Valve 2 * Turn on ion source filaments in low emission * Obtain a flat table closed source scan * Close valve 2 * Obtain CS and OS fractional scans via round robin with valve 2 closed * Open Valve 2 * Obtain CS and OS fractional scans via round robin with valve 2 open * Close Valve 2 * System to initmode MO_ngims_CalDecayHi.prc This script assumes that pressure is optimal for filament operation. * Open Valve 2 * Turn on ion source filaments in low emission * Obtain a flat table closed source scan * Close valve 2 * Switch filaments to high emission * Obtain CS and OS fractional scans via round robin with valve 2 closed * Open Valve 2 * Obtain CS and OS fractional scans via round robin with valve 2 open * Close Valve 2 * System to initmode MO_ngims_CalLeakHi.prc * Perform scans in both low and high emission to determine if gas from the calibration cell is leaking through valve 2. MO_ngims_BALoEmis.prc * Perform pressure check with BA filament in low emission. MO_ngims_BAHiEmis.prc * Perform pressure check with BA filament in high emission. MO_ngims_PatchCFG72.prc (based on details of NGIMS Baseline on Test 2) * Rewrites the config table space in EEPROM0 * Modify config 69 by shifting masses 49 - 140 in subscan tables and widening 140 - 301 MO_ngims_PatchCFG69b.prc * Rewrites the config table space in EEPROM0 * Modify config 19 by pointing masstable 50-70 to subscan 200-220 5.2 Table loads Only small portion of tables will need to be uploaded (about the size of a MUX table). Refer to Appendix L for calculation of table upload times. But for worst-case scenario, we will put a placeholder for software; instrument flat and config table upload activities during post launch checkout to be ready for post hibernation next year. 5.3 Analysis tools NGIMS needs the following tools to analyze post check out data: * RAM dump compare tool * EEPROM dump compare tool (ability to modify NEGSE memory) * Kulite and BA pressure data extraction tool * Kulite and BA pressure plot program None of these programs have been written at the time of this writing. Appendix A: Post Phasing Orbit Timeline Appendix B: List of SEQGEN CAS's tested on the Spacecraft CAS_NGIMS_Baseline1D CAS_NGIMS_Baseline2D CAS_NGIMS_Baseline3D CAS_NGIMS_StartUpSeq CAS_NGIMS_PwrDownSeq CAS_NGIMS_TM_ON CAS_NGIMS_FuncEnc1D CAS_NGIMS_FuncEnc2D CAS_NGIMS_FuncEnc3D CAS_NGIMS_FarEncD CAS_NGIMS_PreEncD CAS_NGIMS_EncD CAS_NGIMS_PostEncD CAS_NGIMS_PostEncCalD CAS_NGIMS_PostEncCalPHDD CAS_NGIMS_UPDATE_CFG1_GLOBALS CAS_NGIMS_UPDATE_CFG2_GLOBALS CAS_NGIMS_UPDATE_CFG3_GLOBALS CAS_NGIMS_UPDATE_MTB1_GLOBALS CAS_NGIMS_UPDATE_MTB2_GLOBALS CAS_NGIMS_UPDATE_MTB3_GLOBALS Appendix C: List of SEQGEN Fragments tested on the Spacecraft NGIMS_CSFil2_ON_LowEms NGIMS_EM NGIMS_Mode3Enc NGIMS_DAC3 NGIMS_EM_NormParm NGIMS_Mode3Parm NGIMS_DAC12 NGIMS_Fil_Off NGIMS_Mode4Enc NGIMS_DAC13 NGIMS_Fil_On NGIMS_Mode4Parm NGIMS_DACOR_1 NGIMS_Fils_HiEmis NGIMS_Mode5Enc NGIMS_DACOR_2 NGIMS_Fils_LowEmis NGIMS_Mode5Parm NGIMS_DACOR_3 NGIMS_FLAT NGIMS_Mode6Enc NGIMS_DACOR_6 NGIMS_FLAT_MARK NGIMS_Mode6Parm NGIMS_DACOR_7 NGIMS_FLAT_MARK_NoDCON NGIMS_Mode7Parm NGIMS_DACOR_8 NGIMS_FLAT_PHD NGIMS_Mode8Parm NGIMS_DACOR_9 NGIMS_FLAT_PHD_Parm NGIMS_Mode9Parm NGIMS_DACOR_12 NGIMS_FreqCorr_Off NGIMS_Mode10Parm NGIMS_DACOR_13 NGIMS_FreqCorr_On_EM1NormVParm NGIMS_Mode10Parm NGIMS_DACOR_14 NGIMS_FreqCorr_On_Norm NGIMS_Mode11Parm NGIMS_DACOR_15 NGIMS_FreqCorr_On_1% NGIMS_ModeCSFrac NGIMS_DACOR_16 NGIMS_FreqCorr_On_.5% NGIMS_NOOP NGIMS_DACOR_17 NGIMS_INITMODE NGIMS_NOOP_Mark NGIMS_DACOR_18 NGIMS_InitTstCon_Part1 NGIMS_OSFil2_ON_HiEms NGIMS_DACOR_19 NGIMS_InitTstCon_Part3 NGIMS_OSFil2_ON_LowEms NGIMS_DACOR_20 NGIMS_IonMode NGIMS_PHD_Parm NGIMS_DACOR_21 NGIMS_LimitCheck NGIMS_Pressure_Test_Part0 NGIMS_DACOR_22 NGIMS_LOADMT_B1 NGIMS_Pressure_Test_Part1 NGIMS_DACOR_23 NGIMS_LOADMT_B2 NGIMS_Pressure_Test_Part2 NGIMS_DACOR_24 NGIMS_LOADMT_B3 NGIMS_Pressure_Test_Part3 NGIMS_DACOR_25 NGIMS_LOADMT_T1 NGIMS_PwrDn NGIMS_DACOR_26 NGIMS_LOADMT_T2 NGIMS_PwrOn NGIMS_DACOR_27 NGIMS_LOADMT_T3 NGIMS_StandbyON NGIMS_DACOR_28 NGIMS_MassTable_SetUp NGIMS_StartUp NGIMS_DACOR_29 NGIMS_Mode1Parm NGIMS_TM_ON NGIMS_ELEC_Short_TST NGIMS_Mode2Parm Appendix D: List of SEQGEN CAS' tested on the Simulator CAS_NGIMS_BaselineLo1D CAS_NGIMS_BaselineLo2D CAS_NGIMS_BaselineLo3D CAS_NGIMS_PressureChkHi CAS_NGIMS_CloseCalCell Appendix E: List of STOL scripts tested on the spacecraft BaselineTest67_NoValves_hiEmis.prc MO_ngims_BALoEmis.prc MO_ngims_BAHiEmis.prc (does not contain loadmt 18, not available for use) MO_ngims_BAOff.prc MO_ngims_functional19a.prc MO_ngims_init_mode.prc MO_ngims_pwrdn.prc MO_ngims_rupture2.prc (remove - will not be used) MO_ngims_CalValueCheck2.prc (remove - will not be used) MO_ngims_configtableloadID61table69.prc Appendix F: List of tested STOL scripts to be tested on Simulator and submitted under Configuration Management MO_ngims_BAHiEmis.prc (make sure loadmt 18 included) MO_ngims_functional20a.prc MO_ngims_Valve1Open.prc MO_ngims_Valve1Close.prc MO_ngims_Valve2Open.prc MO_ngims_Valve2Close.prc MO_ngims_CalDecayLo.prc MO_ngims_CalDecayHi.prc MO_ngims_CalLeakHi.prc MO_ngims_PatchCFG72.prc (see section 5.1 for description) MO_ngims_PatchCFG69b.prc (see section 5.1 for description) MO_ngims_DumpSubScans.prc MO_ngims_DumpConfig.prc MO_ngims_DumpFlat.prc MO_ngims_DumpRam.prc MO_ngims_DumpEEProm.prc MO_ngims_mem_dump.prc MO_ngims_OS_Fil1On_Hi.prc MO_ngims_OS_Fil1On_Lo.prc MO_ngims_OS_Fil2On_Hi.prc MO_ngims_OS_Fil2On_Lo.prc MO_ngims_CS_Fil1On_Hi.prc MO_ngims_CS_Fil1On_Lo.prc MO_ngims_CS_Fil2On_Hi.prc MO_ngims_CS_Fil2On_Lo.prc MO_ngims_OSFil1Off.prc MO_ngims_OSFil2Off.prc MO_ngims_CSFil1Off.prc MO_ngims_CSFil2Off.prc Appendix G: List of STOL procedures tested on the simulator ngims_PostLaunch_Test1.prc ngims_PostLaunch_Test2a.prc ngims_PostLaunch_Test2b.prc (sequenced - tested) ngims_PostLaunch_Test2c.prc ngims_PostLaunch_Test3.prc ngims_PostLaunch_Test4a.prc ngims_PostLaunch_Test4b.prc ngims_PostLaunch_Test4c.prc ngims_PostLaunch_Test4d.prc ngims_PostLaunch_Test5.prc ngims_PostLaunch_Test6a.prc ngims_PostLaunch_Test6b.prc ngims_PostLaunch_Test7.prc ngims_PostLaunch_Test8.prc Appendix H: List of STOL scripts created MO_ngims_BALoEmis.prc MO_ngims_BAHiEmis.prc MO_ngims_Valve1Open.prc MO_ngims_Valve1Close.prc MO_ngims_Valve2Open.prc MO_ngims_Valve2Close.prc MO_ngims_CalDecayLo.prc MO_ngims_CalDecayHi.prc MO_ngims_CalLeakHi.prc MO_ngims_DumpSubScans.prc MO_ngims_PatchCFG72.prc MO_ngims_PatchCFG69b.prc MO_ngims_configtableloadID61btable69.prc MO_ngims_DumpSubScans.prc MO_ngims_mem_dump.prc MO_ngims_DumpConfig.prc MO_ngims_DumpFlat.prc MO_ngims_DumpRam.prc MO_ngims_DumpEEProm.prc Appendix I: List of contingency STOL scripts created MO_ngims_OS_Fil1On_Hi.prc MO_ngims_OS_Fil1On_Lo.prc MO_ngims_OS_Fil2On_Hi.prc MO_ngims_OS_Fil2On_Lo.prc MO_ngims_CS_Fil1On_Hi.prc MO_ngims_CS_Fil1On_Lo.prc MO_ngims_CS_Fil2On_Hi.prc MO_ngims_CS_Fil2On_Lo.prc MO_ngims_OSFil1Off.prc MO_ngims_OSFil2Off.prc MO_ngims_CSFil1Off.prc MO_ngims_CSFil2Off.prc Appendix J: Check Timing Diagram Appendix K: In-Flight Calibration Cell Pressure Decay (Lab Data) Appendix L: Sensor Diagram Appendix M: Patch Tables Transmission Time Calculations APL Contacts: Karl Fielhauer 240-228-3147 Steve Williams 240-228-8883 Dean Sibol 240-228-8429 Mike Furrow 240-228-3725 Definitions: Transmission rate: 500 bits per second 16 bits per word 8 bits per byte Table size : AMB 11 (Configtbl) 1812 AMB 27 (subscan tbl) 4352 Total number of words 6164 Patch command: Each patch command has 4 words of overhead and can patch a maximum of 31 words per patch. (for a total of 70 bytes per command) Total number of Patches Total Number of patches = Ceiling (1812/31) + Ceiling (4352/31) = 59 + 141 = 200 patches Total number of words: Ceiling (6164/31) * 4 + 6164 = 6960 words CCSDS packet to Transfer frame: The Cmdif program translates 1 patch command into 1 packet. One can add the psuedo commands "begin packet" and " end packet" directive at the beginning and end of the packet as an input to the cmdif program. The begin and end frame directives ensure the load goes up as 1 load. The maximum number of bytes per packet is 2554 bytes. However, STOL will default to packetizing 1 command per packet. The buildtctf software confines the packet into a frame. The maximum frame size consists of a maximum of 1000 bytes. However, by default, maximum frame size is 1 packet per transfer frame. At the worst case, we will have 1 command per packet and 1 packet per frame. Each CCSDS packet has an additional 14 bytes to make up the transfer frame: 5 byte transfer frame header 2 byte error control on transfer frame 1 byte segment header 6 bytes of packet header Worst case: 1 command per packet per transfer frame: 70 + 14 = 84 bytes Commands to the spacecraft are transmitted in Command Link Transmission Units (CLTU)4. In order to transform the transfer frame to a CLTU: First, the transfer frame is put into code blocks. 1 code block = 8 bytes, but only 7 bytes contain data. Thus each 84-byte transfer frame will the transformed into 12 Code Blocks: 84 * 8/7 = 96 bytes Second, each code block has a start sequence or sync word of 2-byte and a tail sequence of 8 bytes. Now we have 106 bytes, which makes a CLTU (Start, Code Block, Sync word, Tail Sequence) Add 1 idle byte at the end (idle sequence - alternating pattern of 1 and 0s before the sync word, between successive CLTU) Total bytes = 107 bytes. Transmission time for 200 patch commands: 5.71 minutes (200 patches * 107 bytes/ patch * 8 bits/byte ) / (500 bits/s) = 5.71 minutes Appendix N: Acronym List BA Bayer Alpert (NGIMS Pressure Gauge) C & DH Command and Data Handling CAS Canned Activity Sequence CLTU Command Link Transmission Unit CONTOUR Comet Nucleus Tour CS Closed Source DSN Deep Space Network EEPROM Electrically Erasable Programmable Read Only Memory G&C Guidance and Control NGIMS Neutral Gas and Ion Mass Spectrometer OS Open Source R2D2 The name of CONTOUR archival workstation RT Remote Terminal SDC Science Data Center SEQ Sequence SEQGEN Sequence Generator SRM Solid Rocket Motor SSR Solid State Recorder STOL Satellite Test and Operations Language TM Telemetry 1, 2 Coverage is being negotiated via the Science Operations Coordination at the time of this writing. 3 See Appendix M 4 Extra "one-time" only bytes: In addition, if the very very first CLTU transmitted, we'll have to add the Acquisition Sequence (also alternating patters of 1 and 0 63 bytes). We can safely ignore this as it is a one time deal. RF Hardware sees the following as part of a CLTU transmission: 1 Synch word part of a CLTU (Command link transmission unit) 8 byte tail sequence at the end of the CLTU 7 byte fill data at the end of transfer frame (no need if packet is even) NGIMS/GSFC-FT03 CONTOUR NGIMS NGIMS Post Launch Check Out Document Rev. : 1.2 Date: July 16 2002 Page: 1