Turn ON procedure JD/JM/FT November 14, 2001 On Sun Workstation: 1. Logon procedure: USER ID: ngims PASSWORD: Spoon! Open a terminal window by clicking the terminal icon (a computer terminal) 2. Invoking NGIMS GSE software: In the x-term window, type negse in the terminal command line to initiate the NEGSE software. The NEGSE command window pops up. Notice that the window descriptor bar on the NEGSE command window has the format Test XXXX (RO) RO indicates that you have read only privilege to the Oracle database. You must create a new test that will have RW (read and write) privilege to the database as follows. 3. Setting up test environment on NEGSE prior to creating test record. NEGSE archives test data by stuffing the real time data into an Oracle database. The database has information tags to describe test conditions/environments such as Flight Software Version, Hardware type (EM, FM, or Breadboard), Mux table IDs, Flat table, Config table, Scale Table ID numbers, etc. etc. Scale table IDs changes the data number to engineering unit conversion factors for real-time data display purposes. The method to update the tables are the same; tables must be changed prior to setting up a new test archive (step 4). 4. Creating new test archive on NEGSE: Click on NewFile icon (top left hand corner of NEGSE command window, signified by a piece of white paper) to create new test ID archive A test management window pops up At bottom of left hand of the Test Management window, click New.. button This will bring up the Test ID window, which contains the new Test ID number, and a description box where you can type a description of the test. Type description of test in the Description window within the Test Management window Leave the software version number from the previous description. Click OK button at bottom center of Test Management Window Click Cancel button at bottom right of Test management window to close Test Management window. Note the test number at window descriptor bar of NEGSE command window: Test #### (RW) The (RW) indicates that you have read write priviledges to the Oracle database. Type run 277 on command line of NEGSE command window. Many display windows will pop up. 5. Creating new Test Archive on SCSIM: On Spacecraft Simulator (Dell PC) Double click NGIMSSCSIM.exe icon to bring up SCSIM GSE Single Click on the New File button (signified as a piece of white paper.) on the top left hand corner. A "CreateNewArchive" window pops up. It provides a command line where you will type in the current Test ID as TestID #### The Test ID #### number must be the same as the testID number on the Sun WS. Single click the OK button. 6. Connecting SCSIM and NEGSE systems On Sun Workstation: Type conn command line of NEGSE command window. The System will connect to the SCSIM computer. See "connection #0 successful" message on both command windows on NEGSE and SCSIM. 7. Turning on flight hardware On Flight hardware table: Power on current chart recorder. White button down = power on. Turn on the main power and observe 33.5 and 2.43 A displayed on the supply. Turn on the output switch (red rocker in center) Observe a peak of ~1A on the chart recorder, decaying to .52+/- .01 A on the digital display in the supply. Wait 5 seconds until 1553 hardware initialize 8. Enabling 1553 data flow to SCSIM and NEGSE On Spacecraft Simulator (Dell PC) Type start on command line of SCSIM control window. You will see a little blinking green light on the interface control window on the SCSIM status bar. This signifies a heartbeat of 1553 Non-Packetized Telemetry to the SCSIM. You will also see scrolling "NP" packets on the NEGSE command window. Both are important and shows normal telemetry traffic. 9. Enabling telemetry data on power up On Sun Workstation: Type on command line of test management window. tm on Check voltages on AMUX windows. It is a good idea to enable telemetry when first powering up to check some key voltages and currents. However, the baseline and functional test does enable TM. If we were going to run the baseline or functional right away, then TM On is not necessary. A very important reading is the IMON setting (chart in upper left hand corner) Imon current range: Minimum 0.52A (power on) Maximum 1.5A (science mode) If the current ever exceeds the above range: click stop in script window if running a script Type initmode on NEGSE command line Type tm on to enable telemetry If power still high, TURN OFF POWER IMMEDIATELY!!! 10. Running baseline or functional test On Sun Workstation: Type on command line of test management window. Run 297 or whatever # (baseline test) Or Run 296 or whatever # (functional test) 11. Disconnecting and powering off upon completion of test On Sun Workstation: Type on command line of SCSIM control window. Disc Exit On Dell PC: Type on command line of SCSIM control window. Stop Exit Caveats: a. Do not resize windows. Resizing may cause NEGSE to hang!! b. Try to keep moving windows (that's an OK action) to a minimum. c. If SCSIM has been used for any communication programs, such as Netscape or Internet Explorer, the system must be restarted before the start of acquiring data d. To make plots better, the SCSIM must be stopped and started just before starting a new test. To reset MET time and flight computer, do following: On PC, Type Stop Power off flight unit Follow instructions #3 and #4 (to set up new test log) e. If there is any chance of using standard plotting programs for the entire test, type NOP 1 6200 as the last command prior to closing the test. f. Scripts: Type No. Script No. Baseline 44 297 Functional 13 296 Table Display ? 277 To invoke scripts, type on WS command line: run