|
This page summarizes the functionality included in FSW Release
6.6 (B0-6-6) and lists the JIRA issues resolved
in the Release.
User procedures for Release 6.3 are described in the LAT Flight Software User Guide.
A cumulative list of procedure changes since that Release is provided below. Users of Release 6.6 should
also review the entries for the JIRA items
resolved in Release 6.6.
Additional files, materials, and release documentation for Release 6.6 (including complete 6.6 command and telemetry interface reference documentation) are available on the B0-6-6 Release Page.
I. Functionality of Release 6.6
Release 6.6 supports end-to-end operation of the LAT using the SIU and EPUs and provides all functionality required for “software checkout” and Phase I (full LAT) testing in Building 33. Release 6.6 has the following capabilities:
- Full support for LAT internal hardware interfaces and the LAT external interfaces with the Spacecraft.
- Full boot capabilities on the SIU and EPUs
- CPU watchdog management
- Command and telemetry processing and a complete set of commands and telemetry to support end-to-end operations, as well as handle Spacecraft ancillary messages
- Processing of all time signals and messages from the Spacecraft, and drift-corrected timekeeping
- CPU memory and EEPROM file system management
- Delivery of event data from the hardware to the Spacecraft Solid State Recorder
- Configurable filtering of event data
- Collection of charge injection calibration data
- Operational mode control to manage pointed observations, sky survey observations, and target of opportunity observations
- Load shed management and operations during SAA transit
- Thermal control system
- Instrument configuration by file and readback of instrument configuration
Release 6.6 does not support collection of instrument diagnostic data (CR calibration data, trigger rate data, etc).
It does not fully implement automatic repoint requests and LAT GRB
detection algorithms.
II. Procedure Changes Since Release 6.3
- Release 6.4: To address JIRA item FSW-539, the offline
LCI_parser utility was modified to recognize a new calibration
run control configuration parameter, <latc_delay>, to
supplement the existing <delay> parameter.
This new "LATC settling period" is imposed at the start of each
calibration cycle. Both <latc_delay> and <delay> are specified
in increments of 1/100 second; 200 is a typical value for <latc_delay>,
while 2 is typical for <delay>. The <latc_delay> parameter is valid in LCI configuration files for any type of calibration: ACD, TKR, or CAL.
- Release 6.4: New fields were added to the CpuMetr housekeeping telemetry packet (APID 0x22B): LHKSIUPCIERR, LHKSIUCMERR, LHKSIUUMERR, LHKEPU0PCIERR, LHKEPU0CMERR, LHKEPU0UMERR, LHKEPU1PCIERR, LHKEPU1CMERR, LHKEPU1UMERR, LHKEPU2PCIERR, LHKEPU2CMERR, LHKEPU2UMERR. These fields store counters for the number of RAD750
bridge chip hardware errors (PCI, correctable memory, and uncorrectable
memory, respectively) encountered on the SIU and each EPU. See the
command and telemetry interface reference documentation posted on the B0-6-6 Release Page
for the layout of the new CpuMetr packet.
- Release 6.5: The CPU map defined in the LPACPUS field of the
LPASTART telecommand is now used to set the values in the entire 32 bit EBM destination enables register, and thus define which CPUs participate in
round-robin, event broadcast, and data broadcast addressing. In
addition, LPA now accesses this EBM enables register in
read-modify-write fashion. See the JIRA entry for FSW-551.
- Release 6.5: The LAT Instrument Manager (LIM) provides two new
telecommands that allow the power system configuration and detector configuration to be dumped in telemetry over the Science Data Interface
to the SSR:
- The LIMPIGRECORD command (APID 0x663, function code 16) instructs
LIM to dump the contents of various PDU and EBM configuration registers
to the SSR in packets with APID 0x3FE. The telecommand takes a single
parameter, LIMDEST, though in Release 6.5., this parameter is ignored
and all data are sent to the SSR. The data is packaged into LSFdatagrams
with TypeID 0xF0800. FSW provides routines to decode this data in the QPIG package.
- The LIMLATCRECORD command (APID 0x663, function code 17) instructs
LIM to read the instrument (LATC) configuration and dump the contents to
the SSR in packets with APID 0x3FD. The telecommand takes a single
parameter, LIMDEST, though in Release 6.5., this parameter is ignored
and all data are sent to the SSR. The data is packaged into LSFdatagrams
with TypeID 0xF0900.
- See the command and telemetry interface reference documentation
posted on the B0-6-6 Release Page.
- Release 6.5: On the ground, for debugging purposes, operators may
wish to switch from SIU control to external crate control if the SIU
enters a bad state. Switching back to SIU control once debugging is
complete requires that the SIU send the Look At Me (LAM) LATp command to
the Command/Response Unit. The LAT Instrument Manager, which runs solely
on the SIU, now provides a LIMLOOKATME telecommand (APID 0x664, function code 0),
in response to which it sends the necessary LAM command. The telecommand requires no
parameters.
- Release 6.5: The framework for exchanging discrete signals and
telecommands between FSW and the GBM is now in place. In Release 6.5,
the LAT Physics Acquisition (LPA) application defines 5 telecommands
(LPAGBMCALCINFO, APID 0x660 function code 1; LPAGBMCREPRECOM, APID 0x660
function code 2; LPAGBMCLOSEOUT, APID 0x660 function code 3;
GFSWLATTRIGGER, APID 0x6F1, function code 1; GFSWLATCLOSEOUT, APID
0x6F1, function code 3) exchanged between the SIU, Spacecraft, and GBM; and 3 alert telemetry packets (ALRTRG,
APID 0x341; ALRTUPDATE, APID 0x342; ALRTCLOSE, APID 0x343). (Note: This
messaging infrastructure will undergo qualification testing in Release
7.0). See the command and telemetry interface reference documentation
posted on the B0-6-6 Release Page.
- Release 6.5: Mnemonics for the LTCnmRITTEMP and LTCnmRESTEMP fields
in the DiagLTC telemetry packet (APID 0x2DA) issued by the LAT Thermal
Control application were incorrectly named. See the JIRA entry for FSW-541.
III. FSW Packages Changed or Added in Release 6.6
Release 6.6 provides “flight” code modules, which are loaded and executed on LAT CPUs, and the corresponding source code. In addition, Release 6.6 contains unit tests, test support code, ground support utilities, and qualification test documents and scripts.
- FSW packages that were changed or added since Release 6.5 are
itemized here.
- All FSW packages in Release 6.6 are itemized here.
IV. JIRA Items Resolved in Release 6.6
Bug
- [FSW-570] - Incorrect length in calibration data record
- [FSW-571] - CAL context data overwrites encoded event data
- [FSW-572] - The ground based debugging tools have two errors that adversely affect the primitive dump tools
- [FSW-573] - Tracker data appears to be corrupted
- [FSW-574] - CAL layer counts are in reverse order
New Feature
- [FSW-569] - QMEM supports the new CCSDSP package and the DFIP migration of DfiVsc-Assembler to DfiCcsds-Assembler
|
