Rev.
01
02
03
A
B
ECO
32-200
32-207
32-216
32-223
32-246
Description
Initial Release for comment
Update base on first full run
Incorporate new software packages
Release for flight testing
Add stability criteria; lf_ecal test
Author
RFGoeke
RFGoeke
RFGoeke
RFGoeke
RFGoeke
Approved
Date
1/24/07
4/2/07
5/4/07
6/26/07
9/21/07
CRaTER
Long Form Functional
Test Procedure
Dwg. No. 32-06003.01
Revision B
September 21, 2007
S/N: _____............................... DATE: ____________
.....................................................................................
.....................................................................................
.....................................................................................
Table of Contents
32-06003.01
Page 1 of 17
Revision B
PREFACE ............................................................................................................. 4
1 INTRODUCTION ............................................................................................. 5
1.1
Activity Description ............................................................................................................. 5
1.2
Test Item Description........................................................................................................... 5
1.3
Support Item Description .................................................................................................... 5
2 REQUIREMENTS ........................................................................................... 5
2.1
Verification Plan .................................................................................................................. 5
2.2
List of Required Items ......................................................................................................... 5
3 CONFIGURATION .......................................................................................... 5
3.1
General Constraints ............................................................................................................. 5
3.2
Test Configurations.............................................................................................................. 5
4 PROCEDURES ............................................................................................... 6
4.1
Identification of Test Environment .................................................................................... 6
4.2
Identification of Equipment and Personnel ....................................................................... 6
4.3
Accumulated Operating Time............................................................................................. 7
4.4
Short Form Functional Test ................................................................................................ 7
4.5
Echo Command Function .................................................................................................... 7
4.6
Bus Power Variations .......................................................................................................... 8
4.7
Interrupt 1 Hz Tick .............................................................................................................. 9
4.8
Interrupt 1553 Functions..................................................................................................... 9
4.9
Test Mode............................................................................................................................ 10
4.10
Detector Noise Thresholds ............................................................................................... 11
4.11
Detector Zero Crossing .................................................................................................... 11
4.12
Internal Cal Signal Sweep ............................................................................................... 12
32-06003.01
Page 2 of 17
Revision B
4.13
Coincidence Mask Test .................................................................................................... 12
4.14
Cobalt-60 Radiation Test ................................................................................................. 12
4.15
Dosimeter Tests ................................................................................................................ 13
4.16
Clean Up and Shut Down ................................................................................................ 13
4.17
Accumulated Operating Time ......................................................................................... 13
4.18
Deviation from Baseline Performance............................................................................ 14
APPENDIX A -- CRATERCHECK MAN PAGE .................................................. 16
APPENDIX B -- SAMPLE COBALT-60 DATA ................................................... 17
32-06003.01
Page 3 of 17
Revision B
Preface
The Long Form Test is not run often, for a variety of reasons, and some of its components
yield data that must be evaluated by an observer familiar with the idiosyncrasies of particle
detectors in general and the characteristics of this instrument in particular. Similarly, some data
analysis involves EGSE procedures that are only sketchily described here. It is intended that only
the Project Scientist, Project Engineer, or Project Test Engineer run the Long Form Test.
Rev. 01 is released for general comment.
Rev. 02 is an update based on the experience of the first full run on S/N 10.
Rev. 03 added Echo commands to mark test boundaries and incorporated new test software.
Rev. A had implemented packet checking of test mode plus minor procedural changes.
Rev. B added a range of internal cal signal data plus success criteria for assuring stable
instrument operation over time (see Section 4.18). The Purge Flow test was deleted (tracking a
hardware deletion!). An internal calibration sweep test was added. A criteria for the stability of
the regulated power supplies over a range of input voltages was added.
32-06003.01
Page 4 of 17
Revision B
1 Introduction
The flight hardware for the Cosmic Ray Telescope for the Effects of Radiation (CRaTER)
instrument on the Lunar Reconnaissance Orbiter (LRO) is composed of a single assembly
incorporating both radiation detector and all associated power, command, data processing,
and telemetry electronics. Its external (functional) properties are controlled by the data
(32-02001) and electrical (32-02002) ICDs.
1.1
Activity Description
This procedure will provide a demonstration that the hardware meets as many of its
performance requirements as can be tested within a laboratory environment. In particular
all functional modes, including redundant operations, will be exercised.
1.2
Test Item Description
See para. 1.2 of the Short Form Functional Test Procedure (32-06003.02).
1.3
Support Item Description
See para. 1.3 of the Short Form Functional Test Procedure (32-06003.02).
2 Requirements
2.1
Verification Plan
This Procedure supports the activities contained in the CRaTER EMI/EMC Test Procedure
(MIT Dwg. 32-06006.01), CRaTER Vibration Test Procedure (MIT Dwg. 32-06004.03),
and the CRaTER Thermal-Vacuum Test Procedure (MIT Dwg. 32-06005.01).
2.2
List of Required Items
See para. 2.2 of the Short Form Functional Test Procedure (32-06003.02).
3 Configuration
3.1
General Constraints
See para. 3.1 of the Short Form Functional Test Procedure (32-06003.02).
3.2
Test Configurations
Same as para. 3.2 of the Short Form Functional Test Procedure (32-06003.02) except that
here two MIL-STD-1553 dual-coax cables connect the spacecraft simulator to the
instrument 1553 connector.
Connector mating/demating procedures per MIT 99-03002 shall be observed. Any
connections made directly to the unit under test shall be noted in the mate/demaite log.
Although connector savers will normally be in use, there are times – such as during
vibration testing – where these will have to be removed and later replaced.
32-06003.01
Page 5 of 17
Revision B
4 Procedures
Space is provided for the recording of information of particular significance in the conduct
this test. Where a value simply needs to be verified, as opposed to recorded, a simple check
mark  will suffice. In addition the Test Conductor may redline the procedure to more
accurately document the actual flow of events, both routine and anomalous.
The complexities of running this test makes it difficult for the novice test conductor to
achieve a satisfactory result. At the time of initial controlled release of this document, only
Bob Goeke and Dorothy Gordon are qualified for this effort.
The pages of this section will be attached to the Test Report that is filed each time this
activity is conducted. The telemetry data stream generated by the spacecraft simulator is
also an integral part of the Test Report; that data is archived on crater.bu.edu.
4.1
Identification of Test Environment
Procedure requiring this test:
______________________________________
______________________________________
4.2
Location of Test Environment
______________________________________
Date:
______________________________________
Identification of Equipment and Personnel
Flight Instrument, 32-10000
S/N ____________
Spacecraft Simulator, 32-80201
S/N _____________
Test Conductor
_______________________________
QA Representative:
_______________________________
Other Individuals:
_______________________________
_______________________________
_______________________________
_______________________________
32-06003.01
Page 6 of 17
Revision B
4.3
Accumulated Operating Time
Record the current reading of the cumulative operating time for this instrument by using a
web browser to interrogate the spacecraft simulator at http://csr-dyn-94.mit.edu (or
whatever net address the simulator resides on for this test).
EGSE S/N
4.4
Time in hours:minutes
Initial
Short Form Functional Test
Perform the CRaTER Short Form Functional Test (32-06003.02) and attach the as-run
copy to this report. Do not terminate the sf_log archive program at the end of the test
(or, if you did, restart it now!).
Pass
Fail
Time
Initial
This simple test demonstrates most of the functionality of the instrument (as well as
ensuring that the Instrument GSE is functioning properly). The remaining tests pick up
specialized and redundant functions. We are using the echo command to place markers in
the data stream so that we can go back and review individual tests.
4.5
Echo Command Function
Command
Function
Echo
Value
0x1234
Read, record, and verify the following
Group
System
32-06003.01
From command.tcl
Measurement
Value
Expected
Echo
2 : 0x1234
Page 7 of 17
OK?
Revision B
4.6
Bus Power Variations
Command
Function
Echo
HV Bias
Value
0x4600
On
Adjust the GSE power supply to 27±0.5 VDC, then read and record the following
From house.tcl
Measurement
Value
28VDC Bus
Expected
27±1
+5 Digital
5.0±0.1
+5 Analog
5.0±0.1
-5 Analog
5.0±0.1
Total Power
28VDC Bus
5-8
Time Display
hh:mm:ss
Wall time
Group
Bus Voltages
Command
Function
Echo
OK?
Value
0x4601
Adjust the GSE power supply to 35±0.5 VDC, then read and record the following. Note
that for the regulated voltages, we are interested in the change from the previous condition being
minimal.
From house.tcl
Measurement
Value
28VDC Bus
+5 Digital
Group
Bus Voltages
Expected
35±1
∆ < 12mv
OK?
+5 Analog
-5 Analog
Command
Total Power
28VDC Bus
5-8
Time Display
hh:mm:ss
Wall time
Function
Echo
Value
0x4602
Adjust the GSE power supply to 31±0.5 VDC and proceed to the next section/
Time Completed
32-06003.01
Page 8 of 17
Initial
Revision B
4.7
Interrupt 1 Hz Tick
Command
Function
Echo
1 Hz Tick off
Value
0x4700
(none)
Observe that the /One Hertz/ message appears preceding the time display.
/One Hertz/ message displayed?
Command
Function
Echo
1 Hz Tick on
Initial
Value
0x4701
(none)
Observe that the /One Hertz/ message has disappeared.
/One Hertz/ message absent?
4.8
Initial
Interrupt 1553 Functions
Command
Function
Echo
1553 Side B
Value
0x4800
(none)
Verify that the time display continues to run properly on the B side bus of the 1553
interface.
.
From house.tcl
Measurement
Value
1 sec ticks
Group
Time Display
Command
Function
Echo
1553 Side A
Expected
Wall time
OK?
Expected
Wall time
OK?
Value
0x4801
(none)
Verify that the time display is back running properly on the A side.
Group
Time Display
32-06003.01
From house.tcl
Measurement
Value
1 sec ticks
Page 9 of 17
Revision B
4.9
Test Mode
Command
Function
Echo
Echo
Data Test
Value
0x4900
8
(none)
The Test Mode starts a science telemetry pattern generator within the digital section of the
instrument. (The preceding “echo 8” instructs the system to run the entire suite of tests.)
Run CData to verify that the test mode flag is set to “1” and test data is filling the science
packets. (The Data Test button on the display also changes state here.)
Data Field
Test Mode Flag
Expected
1
OK?
Wait a minimum of 2 minutes before proceeding. (The only way to exit Test Mode is to
Reset the Instrument.)
Command
Function
Reset
HV Bias
Group
Bias Voltage
Value
(none)
On
From house.tcl
Measurement
Value
Thin
Thick
Expected
7510
OK?
22010
We check the results of the Data Test (plus do a number of other consistency checks on the
normal data packets) by running the following on the running data archive file starting in
the initial Short Form test.
rtlm-x <archive_file | craterCheck
The desired outcome is to have no errors – though you will see messages reporting the
clock outage we commanded back in Section 4.7. See Appendix A -- craterCheck man
page for the details.
Data
craterCheck output
32-06003.01
Page 10 of 17
Expected
No errors
OK?
Revision B
4.10 Detector Noise Thresholds
We now enable a single detector channel at a time; the noise threshold is determined by
walking the appropriate LLD up from 64 (or approximately 0 mv) until the number of
reported Good Events is less than 20. When a measurement is completed, reset the LLD to
128. Record the threshold setting, not the feedback voltage.
Function
Echo
Command
Function
Value
0x4A00
LLD Thin
Threshold
LLD Thick
Threshold
OK?
Process D1 Only
Process D2 Only
Command
Process D3 Only
Process D4 Only
Process D5 Only
Process D6 Only
4.11 Detector Zero Crossing
Command
Function
Echo
Value
0x4B00
Run the lf_zero script. This will use the low range internal cal signal to draw a line
between two points and calculate the ADU count of that line when it crosses zero (input).
D1
D2
D3
D4
D5
D6
High
Low
Zero
32-06003.01
Page 11 of 17
Revision B
4.12 Internal Cal Signal Sweep
This test is run purely to gather data which would be used by the science team to crosscalibrate instrument performance in case of on-orbit anomalies. The internal calibration
source is run in both low and high amplitude modes, stepping 8 (command) LSBs and
collecting a few thousand events at each step.
Command
Function
Echo
Value
0x4C00
Run the lf_ecal script.
Time Completed
Success?
4.13 Coincidence Mask Test
Command
Function
Echo
Value
0x4D00
This is a test which, for all combinations of detector processing enable, verifies that one
and only one coincidence mask bit allows good events to be recorded. Since the test
involves 26 processing combinations and the same number of coincidence mask bits, it
takes at least 3 * 212 seconds (3.4 hours) to complete. (We do not attempt to test all
combinations of the coincidence mask, even for a single processing case; that would take
1012 years.)
Run the lf_mask script.
Time Completed
Cases Run
Success?
4.14 Cobalt-60 Radiation Test
Command
Function
Echo
Value
0x4E00
This test works best with a 5 microcurie source held just in front of the telescope aperture
(effectively about 1 cm from the closest thick detector). A stronger source held at a greater
distance would do as well. With some of our older sources one must take into account the
5.3 year half-life in establishing the effective strength.
32-06003.01
Page 12 of 17
Revision B
Run the “lf_cobalt 60” script (it will take 60 minutes worth of data) and compare the
plots to the reference data in Appendix B. (The example is from a 13 hour run!)
Time Completed
Max Counts
D1,3,5
Max Counts
D2,4,6
Success?
4.15 Dosimeter Tests
The dosimeter does not respond to commonly available radiation sources. There is no test
available once the instrument is buttoned up.
4.16 Clean Up and Shut Down
We intentionally use the “clear” command here to exercise that function; the “reset”
command used elsewhere is a more general instruction which affects most of the internal
logic states.
Command
Function
Clear
Value
(none)
Read, record, and verify the following
Group
Total Power
From house.tcl
Measurement
Value
28VDC Bus
Expected
5-8
Bias Voltage
Thin
3±1
Thick
3±1
OK?
Turn off GSE 28VDC power supply and Spacecraft Simulator if no further testing is to
be performed immediately.
Close the archive data file by closing the window opened by sf_log .
Time Completed
Initial
4.17 Accumulated Operating Time
Record the current reading of the cumulative operating time for this instrument by using a
web browser to interrogate the spacecraft simulator at http://csr-dyn-94.mit.edu (or
whatever net address the simulator resides on for this test).
EGSE S/N
32-06003.01
Page 13 of 17
Time in hours:minutes
Initial
Revision B
4.18 Deviation from Baseline Performance
Where applicable, test limits have been defined in this procedure and the accompanying Short
Form Functional. These limits are intended to encompass all operating conditions.
Additionally, we want to assure that the operation of instrument remains stable. To that end
we calculate here – when appropriate – the deviation of various parameters from their baseline
values. (The nominal, ambient temperature and pressure baseline is available from the
CRaTER database under the 32-06001 heading.)
Date of Baseline or Database Ref. Number
Test Ref
Parameter
SFF 4.4 +5 Digital
#/LSB
2mv
Baseline
This Test
Delta
Initial
Limit
10mv
OK?
+5 Analog
-5 Analog
Bulkhead
0.1C
∆Telescope
2.0C
∆Analog
∆Digital
∆DC-DC
SFF 4.5
Power
30mw
0.2w
Bias V, Thin
0.1v
0.5v
Bias V, Thick
0.1v
D1 bias I
0.5µa,
12%/C
greater
of 25%
or 2.5µa
5µa,
12%/C
Greater
of 25%
or 25µa
D3 bias I
D5 bias I
D2 bias I
D4 bias I
D6 bias I
NB: Temperature data is entered here as differences between the monitored value and the
temperature of the bulkhead, instrument reference. The bulk temperature of the instrument
depends upon the environment; to a first order the internal deltas should not.
32-06003.01
Page 14 of 17
Revision B
The Primary Science data is recorded here in ADU. For reference, the thick detectors
have a scale of approximately 20KeV/LSB; the thin detectors approximately 60KeV/LSB.
Test Ref
SFF 4.7
Parameter
D1 Cal Amp
Baseline
This Test
Delta
Limit
OK?
5
D2 Cal Amp
D3 Cal Amp
D4 Cal Amp
D5 Cal Amp
D6 Cal Amp
D1 Noise
0.3
D2 Noise
D3 Noise
D4 Noise
D5 Noise
D6 Noise
LFF 4.11
D1 Zero Cross
0.3
D2 Zero Cross
D3 Zero Cross
D4 Zero Cross
D5 Zero Cross
D6 Zero Cross
32-06003.01
Page 15 of 17
Revision B
Appendix A -- craterCheck man page
NAME
craterCheck -- Search for errors in CRaTER packets in test mode
USAGE
craterCheck
craterCheck.mac
craterCheck.exe
craterCheck.c
#
#
#
#
For use on SUN Solaris machines
For use on Mac OS X machines
For use on Windows machines
Source code
FLAGS
(none)
Uses only STDIN and STDOUT
DESCRIPTION
This program verifies
well as the operation
useful for looking at
running the intrument
diagnostic. First set
the data integrity of the CraterInstrument, as
of the SRAM and 1553 bus subsystems. Although
packets emitted by the intrument in normal mode,
in "text" mode provides a more thorough
up a data archiving process. Then the commands
echo 8
test
sent to the instrument will start a cycle of internal diagnostics whch
should be allowed to continue for at least 2 minutes.
rtlm-x <archive_data | craterCheck
will process the data.
DATA OUTPUT DESCRIPTION
PS - Primary Science SS - Secondary Science HK - Housekeeping SSCnt Source Sequence Count
ApIDErr - Encountered an illegal Application Process ID (not equal to
120, 121 or 122)
HdrBitCorr - Corruption encountered at the beginning of the packet
header (check includes Version Number, Type and Secondary Header Flag)
PLen - indicates that the packet length field does not match the
expected value.
SSCnt - (Source Sequence Counter) errors are listed for each ApID This
error count is non-zero if the detected SSCnt is non-consecutive.
Special cases were added to handle potential GSE problems: Drop1
indicates one dropped packet. Repeat1 indicates a duplicate packet.
Testmode data integrity checking is continued if the Drop1 or Repeat1
error is found. The program resynchs when a more serious PS SSCnt error
is encountered.
Data Errors apply only to the PS Telemetry when the system is in
TestMode. They indicate a test-mode pattern mismatch in the data portion
of the packet. Data Errors are tabulated on a per packet basis and
accumlated for all Testmode packets. If more than four errors are found
in one packet, the MultErrs count is incremented and the system
"resynchs".
BUGS
The program will only work if provided the output of an rtlm -x process,
with or without a 64-byte file header. The program is very intolerant of
variations in input format and has only been used with an rtlm feed.
SEE ALSO
rtlm-x.c, verify
32-06003.01
Page 16 of 17
Revision B
Appendix B -- Sample Cobalt-60 data
32-06003.01
Page 17 of 17
Revision B