File uvcs_sheet1.txt -- Last modified Mon Jun 19 14:59:42 1995


                   COMMISSIONING PHASE BLOCK SHEET

1. INSTRUMENT AND BLOCK NUMBER: UVCS, Block 1

2. BLOCK IDENTIFICATION: UVCS Switch-on

3. PURPOSE: Initial checkout, monitor HK

4. SUB-BLOCKS: (see Note 1)
   NR.   IDENTIFICATION
   1.1   Switch-on and checkout
   1.2   Monitor Status
   1.3   Initialize S/W
   1.4   Monitor Status

5. SUB-BLOCKS TABLE: (see Note 2)
   NR. - DURATION - PREVIOUS - COMMANDING - TELEMETRY - POINTING
   1.1    2:00        N/A      PRO, NRT-d      H (?)     None
   1.2    0:15        Nom.        NRT-d        H         None     
   1.3    2:30        Nom.     NRT-d,PRO       H         None
   1.4    0:15        Nom.        NRT-d        H         None

6. SCHEDULING REQUIREMENTS: (see Note 3)
   Schedule block 1 a.s.a.p. after initial SVM checkout completed.  
   No interruption by MCC2. 1.2 and 1.4 are opportunities to adjust
   parameters as a result of monitoring. 1.3 has 00:15 included for
   adjustment. 1.1, 1.2, 1.3, and 1.4 to be scheduled one day (approx 
   24 hours) apart.
   Note that the sub-blocks scheme implies a small change from the one
   in the timeline.

7. SPECIAL REQUIREMENTS: (see Note 4)
   1.1 and 1.3 require coordination with FOT
   
8. SUCCESS CRITERIA AND/OR EXPECTED OUTPUT:
   UVCS on, main mechanisms verified, HK normal

9. RELEVANT PROCEDURES
    U_PWR_ON(1)

10. CROSS-REFERENCE TO TEST SHEETS: (list identifiers for test sheets)
    Ask Sylvano

11. RELEVANT SECTION OF TIMELINE (backpage)

BLOCK1 -- UVCS SWITCH-ON

BLOCK1.1 -- SWITCH-ON, CHECKOUTS
	
      4 & 00:00 # UVCS power ON (A side) # SMOCC executes U_PWR_ON(1) (ded.) 
	
      4 & 00:30 # Transfer UVCS control to IWS # (dedicated)

      4 & 01:00 # Check mechanism launch lock/switch status # (dedicated) 
     
      4 & 01:15 # Check-out commanding by IWS # (dedicated) 
;               # send UBNO cmd, verify cmd counters and S/C toggle bit state

      4 & 01:30 # Check out heaters and heater power relay # (dedicated)
    
      4 & 02:00 # Monitor UVCS status # for 48 hrs while in INIT mode (shared)


BLOCK1.2 -- INITIALIZE S/W

      6 & 00:00 # Verify checksums of EEPROM segments with flight s/w # (ded.)

      6 & 00:30 # Main flight s/w ON (JUMP) # Only if SEU rate is low (ded.)

      6 & 00:45 # UVCS Local On-Board Time (LOBT) update by SMOCC # (dedicated)
;               # IWS checks OBT vs. LOBT 

      6 & 01:00 # Enter Installation mode and set software flags (TBC) # (ded.)

      6 & 01:30 # Dump onboard tables and check against MOPS database # (ded.)

      6 & 02:00 # Enter Pre-Operations software mode # (dedicated)

      6 & 02:15 # Monitoring UVCS status # for at least 24 hrs (shared)


Note 1: Sub-blocks are functional units within a block. Operations can
        be interrupted between blocks, but usually not within a block.

Note 2: In this table the following information is sought:

    DURATION:   Estimation of time needed (dd & hh:mm), without contingency.
                 
    PREVIOUS:   Previous (sub)block(s) necessarily completed before the
                present subblock. Nominal (entry: Nom) is all (sub)blocks
                with lower number. Exceptions are noted with X (i.e.
                X 2.5, 2.6 means, all previous subblocks need be completed,
                except 2.5 and 2.6)  

    TELEMETRY:  Telemetry mode and submode required. Options: High (H),
                Medium (M), Low (L). For submodes: 1,2,3 (??). Nominal
                during cruise phase is H2 after ?? days, M between
                12 hours and ?? days, and L before 12 hours after launch.

    COMMANDING: Commanding mode required. Options are NRT dedicated
                (entry NRT-d), NRT shared (NRT-s), STOL procedure (entry:
                PRO and procedure identifyer), no commanding, for example
                monitoring  HK, or outgassing  (entry: None). Others ??

    POINTING:   Pointing requirements: none (entry: None), or nominal
                to Sun with no accuray guaranteed during cruise (entry:
                Nom). Other options are: no interference by other 
                instruments or reaction wheels (No-I), and ??

    SCHEDULING: Any scheduling requirements, such as at a certain time
                after launch, before or after MCC2, 

Please leave entries blank only when the information is not known, not
for nominal (entry: Nom), or not applicable (N/A), or obvious cases (they
may not be obvious to others). Please use footnotes to the table if entry 
does not fit into table.

Note 3: Describe any scheduling requirements, for example preferred, earliest
        and latest time for early switch-on activities, scheduling before or
        after MCC2, preferred time or preferred interval with respect to     
        previous activities (for example intervals between intercalibrations),
        etc.??                   

Note 4: Describe any special circumstances, for example when an activity
        is to be continued during non-contact hours, under automatic
        control, when coordination with other experiments or the FOT (for
        SVM operations) is required, etc.