L-OBS-13x
Observatory Level LAT/Spacecraft Interface Test
Outline
1 December 06
v3
Initial Configuration / Entrance Criteria:
REVISION SUMMARY
1.
LICOS can send commands to AstroRT and receive science and
telemetry data from Spacecraft Integration & Test (SCIT) console.
2.
Spacecraft and the LAT are on and operating in the selected
redundancy configuration.
3.
The spacecraft is providing valid 1PPS, Timetone, Spacecraft Position,
and Spacecraft Attitude data.
4.
The SSR is active and the SC_Ready line is enabled.
Purpose:
5.
The GBM is on and operating.
The L-OBS-13x procedure verifies the proper function of the fully crossstrapped hardware interfaces between the LAT and the Spacecraft.
Final Configuration / Exit Criteria:
Vers
Date
Description of Change
0
1
11/20/06
11/27/06
Initial Draft
Incorporate SASS comments.
2
11/29/06
Incorporate tabletop comments.
3
12/1/06
Delete 1PPS and Timetone FSW message checks. Clarify timestamp test.
1.
All LAT-SC interface tests passed.
Description:
The L-OBS-13x – LAT/SC Interface Functional test case, run in
coordination with a Spacecraft AstroRT script, verifies the functionality of
the LAT/SC Interfaces not tested during the LAT Power-On (L-OBS-00x).
The Spacecraft is powered into either an all primary unit or all redundant
unit configuration while the LAT is powered into one of the redundancy
configurations 1-5 in order to verify the all prime, the all redundant, and the
cross-strapped LAT-SC interfaces. The functionality verified includes the
GBM supplied Immediate Trigger Signal (ITS), GPS (Time-tone) Message,
the GPS Time Hack (1 PPS signal), the Observatory attitude and position
data (the Spacecraft Ancillary telecommand), 1553 telecommands,
command rate, and the Spacecraft Ready line all provided by the SC, Time
Consistency Check, Clock Correlation, and Event Ancillary Data functions
that operate on the SC supplied data.
Constraints:
Reference:
QUIESCENT, PHYSICS, ARR
LAT-TD-07665 LAT Flight Software User Guide
1.
All telemetry check and command execution failures must be
coordinated with Systems Engineering before proceeding.
2.
Limits and initial state is for ambient power on only.
Parent Procedure:
None
Child Procedure(s):
None
Relevant Modes of Operation:
Estimated Duration:
30 minutes
GLAST
1
L-OBS-13x
STEP
OWNER
1.
LAT
2.
SC
3.
SC
4.
LAT
GLAST
Observatory Level LAT/Spacecraft Interface Test
Outline
DESCRIPTION
ACTION
EXPECTED RESPONSE
1 December 06
v3
COMMENTS
Verify LICOS time is
synchronized to UTC.
Verify the Timetone messages
provided to the LAT by the SC are
time synchronized to UTC.
Enable LAT Commanding
Start the LatSc1553Interface script
when instructed to do so by the
Observatory test conductor.
[Need SC verifiers for this item]
In AstroRT commanding window
select:
Options
OTCC Ready?
Ready
Select the LatSc1553Interface
script from the LICOS script
window and chose the cfg file
consistent with the current
redundancy configuration.
In LICOS Proxy Window, indicator shows
“Ready”.
LatSc1553Interface is running.
2
L-OBS-13x
STEP
5.
OWNER
LAT
Observatory Level LAT/Spacecraft Interface Test
Outline
DESCRIPTION
Upload a large FSW file of
sufficient length to fully load the
command interface at 20
commands per second (including
the magic 7) for 1 minute
minimum.
ACTION
Verify that a load is not currently
in progress.
b. Upload a large file to the SIU
Load the file ebc_siu.f which
generates the following
commands:
LFILUPLSTART
LFILESIZE
LFILUPLDATA
OFFSET
DATA
LFILEDATA1
…
LFILEDATA47
a.
c.
6.
LAT
GLAST
Verify the receipt of the 1PPS and
Timetone messages by comparing
the timestamp placed by LAT
FSW in the CCSDS Housekeeping
packet headers to the UTC time
obtained by LICOS.
Average command rate for
upload > 12 commands/sec.
a. Compare a minimum of 20
consecutive Housekeeping
packet timestamps to UTC and
verify LAT time is incrementing
and each timestamp within ± 2
seconds (TBD) of UTC (when
accounting for leap seconds,
currently 1).
b. Provide the timestamp from
each packet in UTC, the
corresponding UTC obtained by
LICOS, and the calculated time
delta between the two in the test
report.
EXPECTED RESPONSE
1 December 06
v3
COMMENTS
a. LHKSFILSTATE = START
b. Expected command confirmation
for first
command
LITCTASK = LFS (2)
LITCCMDHDRAPID = 1601
LITCCMDHDRFNC = 0
c. LITCEXESTATUS = SUCCESS
Command counter for LFS increments once
for LFILUPLSTART
LHKLFSCMDSENT increments by one
d. Command counter for LFS increments once
for each packet in the load file
LHKLFSCMDSENT increments for each
packet
e. State of the upload state machine after the
load is complete:
LHKSFILSTATE = LOAD
LHKSFILCURSIZE = LFILESIZE after
load is complete
f. LHKSFILPKTCNT = number of
LFILEUPLDATA commands in the binary
file
g. (Total commands sent)/[(FLCP_SUCCESS
receipt time) - (FUPL_SUCCESS receipt
time)] > 12 commands/second
Each timestamp is within ± 2
seconds (TBD) of the associated
UTC when accounting for leap
seconds.
3
L-OBS-13x
STEP
Observatory Level LAT/Spacecraft Interface Test
Outline
OWNER
DESCRIPTION
7.
SC
Provide an a priori defined set of
SC position and attitude data to the
LAT in the Magic 7 for 1 minute
minimum.
[Need SC verifiers for this item]
8.
LAT
Offline (in post-test analysis)
verify the LAT Science Data
stream received during this test
contains the identical set of SC
position and attitude data provided
by the SC in the Magic 7.
a.
9.
SC
Set the SC_Ready line to “Not
Ready” for 1 minute.
[Need SC verifiers for this item]
10.
LAT
Verify FSW indicates, using LAT
Diagnostic telemetry, the
SC_Ready line is set to “Not
Ready”.
a.
GLAST
ACTION
EXPECTED RESPONSE
The Science data contains Magic 7 data
identical to that provided by the SC.
MAGIC7 = A priori SC data
1 December 06
v3
COMMENTS
This needs to be
defined. Should (or
must) it be time
varying? In either case
can GD provide a file
for comparison?
One suggestion was for
LICOS to compare,
offline, the attitude and
position data provided
in SC Hsk to that in the
LAT Science data.
Those SC Hsk monitors
would need to be added
to the list of tlm LICOS
receives to use that
approach.
The active SIU indicates the SC_Ready line
is set to “Not Ready” by repeatedly
providing the following diagnostic
messages.
LCMMSGOUT
LCMMSGNODE = active SIU
LCMMSGTASK = LCS
LCMMSGNAME = LCBTXERR
LCMMSGOUT
LCMMSGNODE = active SIU
LCMMSGTASK = LSM
LCMMSGNAME = BADSEND
LCMMSGOUT
LCMMSGNODE = active SIU
LCMMSGTASK = MSG
LCMMSGNAME = GAPBEGIN
LCMMSGOUT
LCMMSGNODE = active SIU
LCMMSGTASK = MSG
LCMMSGNAME = GAPEND
4
L-OBS-13x
STEP
Observatory Level LAT/Spacecraft Interface Test
Outline
OWNER
DESCRIPTION
11.
LAT
12.
LAT
Verify FSW indicates, using LAT
Diagnostic telemetry, the
SC_Ready line is set to “Ready”.
The LatSc1553Interface script
completes successfully and passes.
13.
LAT
14.
SC
15.
LAT
16.
LAT
17.
LAT
18.
SC
Dump Science and Housekeeping
data from SSR.
19.
LAT
Verify Science and Housekeeping
data dumped from SSR has been
received.
GLAST
Start the LatGrbHandling suite.
Instruct the GBM to send the
Immediate Trigger Signal only
(with no message traffic).
Verify the receipt of the ITS signal
from the GBM.
ACTION
EXPECTED RESPONSE
1 December 06
v3
COMMENTS
Wait 20 seconds after the SC_Ready line is set
to “Ready” and verify the diagnostic messages
indicated in step 14 above cease.
The LICOS script engine indicates
LatSc1553Interface PASSED.
Select the LatGrbHandling suite
from the LICOS script window and
chose the cfg file consistent with
the current redundancy
configuration.
A 36 second muon run has completed
successfully, the LAT is configured to accept
an Immediate Trigger Signal (ITS), and
LatGrbHandling is paused awaiting an ITS
from the GBM.
[Need SC verifiers for this item]
Monitor LAT message traffic to
verify receipt of the ITS from the
GBM.
a.
Wait 10 minutes to allow GBM
interrupt to time out so that
Physics mode can be entered in
subsequent scripts. Proceed once
the LAT has returned to Physics
mode.
The LatGrbHandling script
completes successfully and passes.
The following Diagnostic message is
received:
For the Primary GBM:
LIMTOPMODE =4
LIMTACTION = 69
LIMTSTATUS = SUCCESS
For the Redundant GBM:
LIMTOPMODE =4
LIMTACTION = 70
LIMTSTATUS = SUCCESS
a. Verify the GBM timeout has expired by
observing that the LAT returned to Physics
mode from ARR mode:
LIMTOPMODE =4
LIMTACTION = 46
LIMTSTATUS = SUCCESS
The LICOS script engine indicates
LatGrbHandling PASSED.
[Need SC verifiers for this item]
[Is any LAT action required??]
An SSR dump is
required to get the M7
data off the SSR for
off-line analysis.
[Need LICOS verification for this item]
5
L-OBS-13x
GLAST
Observatory Level LAT/Spacecraft Interface Test
Outline
1 December 06
v3
6