MAESTRO Status

1
MAESTRO Status

• October 3-9, 2002
• 6 days testing at University of Toronto
• October 31, 2002
• Alignment Testing at DFL
• November 14-18, 2002
• T-VAC at DFL
• December 2002
• Instrument completed at EMS
• January 2003
• 3 days testing at U of T
• January 2003
• Shock Test at DFL
• MAESTRO has not yet been adequately tested either
  operationally or scientifically

2
MAESTRO Testing Requirements

• Operational Testing
• Does the instrument react as required?
• Anomalies to be noted and worked off
• Scientific Testing
• Does the instrument meet the requirements?

3
MAESTRO Anomalies

• Anomaly A2
• During the transition SLEEP-gtSTANDBY the ROE
  boards do not apparently initialise correctly
• Possible Cause
• Problem with UART reset codes
• Resolution
• Code update to be tested
• Notes
• This is actually a false indication caused by
  random bits in the communication UARTS the ROE
  boards do initialise correctly

4
MAESTRO Anomalies

• Anomaly A3
• Some problem with heater command
• Cause
• Unknown
• Resolution
• Unknown
• Notes
• Trying to track down exactly what this anomaly
  consists of

5
MAESTRO Anomalies

• Anomaly A4
• Errors on bus?
• Cause
• Unknown
• Resolution
• Unknown
• Notes
• Several alignment runs had missing data

6
MAESTRO Anomalies

• Anomaly A5
• Dropped packets on science bus
• Cause
• Unknown
• Resolution
• Unknown
• Notes

7
MAESTRO Anomalies

• Anomaly A6
• Missing packets on science bus
• Cause
• Unknown
• Resolution
• Unknown
• Notes

8
MAESTRO Anomalies

• Anomaly A8
• BS_FIRM_CRC was "0", should be "1"
• Cause
• Unknown
• Resolution
• Unknown
• Notes
• Need to recheck to see if this is actually
  happening

9
MAESTRO Anomalies

• Anomaly A9
• Diode tests failed
• Cause
• Wrong command was sent
• Resolution
• Send correct command
• Notes
• Need to verify

10
MAESTRO Anomalies

• Anomaly A10
• There were corrupt packets (type?) in alignment
  data
• Cause
• Insufficient time between issuing "select table"
  and "select science" commands
• Resolution
• Allow sufficient time between commands
• Notes
• Need to verify

11
MAESTRO Operational Testing

• Recommend
• Full regression testing against spacecraft before
  delivery to U of T include software updates as
  necessary
• Full operational testing at U of T before moving
  to the test tank
• Full scientific testing in the ICF facility
• To include both solar and backscatter ports
• Soak testing (gt100 hours continuous) of
  instrument operation before leaving ICF

12
MAESTRO Test Results October 2002

• The spectral coverage and wavelength dispersion
  results are good
•  The Instrument Line Shape function looks too
  wide. Future tests during MAESTRO/FTS co-testing
  using lasers with diffusers should conclude
  whether this is due to multiple Hg spectral lines
  or a focusing problem
•  Finer grid FOV mapping using the Xe lamp as well
  as lasers, planned during MAESTRO / FTS
  co-testing, should provide more accurate slit
  dimensions. The slit width determined from this
  data is too big, and there is insufficient data
  to determine the slit length.
•  Linearity and pixel-to-pixel gain results seem
  acceptable, although strange attenuation features
  which are probably due to the wire mesh need to
  be investigated further.
•  Noise and dark current characterization could
  not be performed due to problems with the A/D
  converter during baseline testing.
•  The scan rod maximum sweep rate was 10 times
  higher than the maximum specified in the IRD
  document
•  The internal test diodes seem to be functioning
  properly.