|
This page summarizes the functionality included in FSW Release
B0-6-9 and lists the JIRA issues resolved
in the Release.
User procedures for B0-6-6 are described in the LAT Flight Software User Guide.
A cumulative list of procedure changes since that Release is provided below. Users of B0-6-9 should
also review the entries for the JIRA items
resolved in B0-6-9.
Additional files, materials, and release documentation for B0-6-9 (including complete
0-6-9 command and telemetry interface reference documentation) are available on the B0-6-9 Release Page.
I. Functionality of B0-6-9
B0-6-9 supports end-to-end operation of the LAT using the SIU and EPUs.
0-6-9 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
B0-6-9 does not support collection of instrument
diagnostic data (CR calibration data, trigger rate data, etc). It does
not fully implement automatic repoint requests or the LAT GRB
detection algorithm.
II. Changes Affecting Procedures Since Release 0-6-6
- B0-6-7: At the end of a physics data taking run using LPA,
on receipt of the LPASTOP command, FSW checks whether the detector configuration changed during the run.
If the configuration did change, the detector register configuration data is dumped to the
SSR in telemetry with APID 1021.
- B0-6-7: The contents of various hardware error and status (ESR)
registers are now sent with other LAT detector configuration dump telemetry
to the Solid State Recorder. If the LPALATCCNSFLG of the LPASTART
command is set to instruct FSW to dump the LAT configuration to the SSR
at the start of the data collection run, a separate telemetry
packet of ESR data is sent along with the configuration register
dump data. The ESR packet is sent any time the detector configuration is
dumped - in response to an LPASTOP command (see the
previous note) or in response to the LIMLATCRECORD command. The ESR data packet has the same APID (1021) as the
other configuration data telemetry; within the telemetry packet, the ESR data is
organized as a single LSFdatagram with TypeID = 0x900 wrapping a single
LSFcontribution with TypeID = -1. The ESR data packet is always the
last telemetry packet in any sequence of packets with APID 1021 dumped in response to LPASTART, LPASTOP,
or LIMLATCRECORD. See FSW-594 for the list of
ESR registers dumped.
- B0-6-8: New status information was added to thermal
control telemetry, both in the LTC diagnostic telemetry packet (DiagLTC,
APID 730) and in the housekeeping LtcData0 packet (APID 558). Both
packets contain a new field, LTCHTRREG, recording the current state of
the LTC system (running or stopped, active or passive) and the current
state of the SIB heater control register for each heat pipe reservoir
heater, 0-11. See the 0-6-8 command and telemetry handbooks (Cmd_Tlm_*.pdf) on the B0-6-8 Release Page
for the layout and encodings of the new field.
- B0-6-8: The ITOS definition for the Slew-Request command (APID
1536) sent by FSW to the spacecraft as part of the ARR response sequence
was added to the ITOS database. The command definition had previously
been hard-coded into the LAT Instrument Manager application code, but
not "published" as part of FSW's ITOS products (database and command and
telemetry handbook) .
- B0-6-8: When performing "fast boot", the boot code now takes
secondary boot flags from the Boot Diagnostics Area in RAM instead of
using hard-coded defaults. Operators wishing to use fast boot can issue
the LBTRTOSEXEC telecommand (APID 1600), setting the secondary boot
flags as desired; later reboots with the LBTRESET telecommand (using the
fast boot option settings) will then use the pre-set secondary boot flags. Alternatively,
operators may set the secondary boot flags directly in RAM using the LMEMLOADMEM command.
The secondary boot flags start at address 0000FF84
and occupy 4 bytes. The encoding of the secondary boot flags is
documented in the Primary Boot Code Design Document on the
FSW Traveler
Documents page, and various CPU boot use cases are described in the
FSW User Guide .
III. FSW Packages Changed or Added in B0-6-9
B0-6-9 provides “flight” code modules, which are loaded and executed on LAT CPUs, and the corresponding source code. In addition, B0-6-9 contains unit tests, test support code, ground support utilities, and qualification test documents and scripts.
- FSW packages that were changed or added since B0-6-8 are
itemized here.
- All FSW packages in B0-6-9 are itemized here.
IV. JIRA Items Resolved in B0-6-9
Bug
- [FSW-617] - QLATC_print doesn't handle input data containing CCSDS pkts with more than one APID
- [FSW-624] - Compressed data is encoded incorrectly in some cases
- [FSW-630] - The width of the livetime register in the GEM is incorrectly specified to be 24 bits. It should be 25 bits.
- [FSW-632] - Attempts to reburn the SUROM on EPUs using DDT result in kernel panic and reboot
- [FSW-634] - Correct bug in ground base portion of EDS. EBF_streamEvtWrite has a boundary condition error
Improvement
- [FSW-618] - Documentation for several apids needs to be added to standard webpage
- [FSW-622] - LATC verification error should report a split failure in the [-,+][x,y][0,8] notation.
- [FSW-625] - Bounds checking on values specified for register fields in the input XML has been requested.
- [FSW-629] - Improve looking for and dealing with errors in the CCSDS packet handling
- [FSW-639] - Enhance the FSW private ground based utilities qsep_print and qsep_extract to be able to skip over missing CCSDS packets
New Feature
- [FSW-614] - PBC should include a host-based utility that interprets and displays the contents of boot housekeeping telemetry.
|
