1 / 12

GLAST Large Area Telescope: Instrument Science Operations Center CDR

Gamma-ray Large Area Space Telescope. GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 3.2 Instrument Flight Software Jeff Fisher FSW Manager. FSW Team Mission. FSW team is responsible for Design and delivery of FSW (pre-delivery)

leal
Download Presentation

GLAST Large Area Telescope: Instrument Science Operations Center CDR

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Gamma-ray Large Area Space Telescope GLAST Large Area Telescope: Instrument Science Operations Center CDR Section 3.2Instrument Flight Software Jeff Fisher FSW Manager

  2. FSW Team Mission FSW team is responsible for • Design and delivery of FSW (pre-delivery) • Processing Software Change Requests (SCRs) (postdelivery) • Providing software updates • Validation and Verification (V&V) of all software changes by ISOC Test Team • Maintenance of the Instrument Test Bed • V&V of SCRs • V&V of command sequences • Investigatation of anomalies

  3. Relation between FSW and ISOC • Through FSQ • Coding the software that will operate the LAT • Testing the software • Configuration management • Development of Test Bed • Beyond FSQ • Continue code/test/CM cycle as part of the ISOC operations • Maintenance of Test Bed • Review commanding, HK, and performance on a frequent and regular basis

  4. FSW Testbed Block Diagram Event Builder (EB) output side. The EB is an element of the GASU. LAT Instrument SIIS To SSR To SIU To EPU(s) “SolidStateRecorder” Spacecraft Interface Unit Event Processing Unit(s) Sensorsreplaced withFront EndSimulators(FES) Other Tasks Other Tasks 1553 Rx service LCBRx MSGservice 1 PPSInterrupt GBM Interrupt 1 PPSInterrupt MSGservice Discretes(to SIU PIDs) LCB Rx service Slaves Slaves Masters 1553 Q Q Q SC Att./Time SC Att./Time SC Att./Time Q Q Q Instr. Phys. Instr. Phys. Q Q Q Q Q File/Object File/Object File/Object Q Q Q Q HSK HSK HSK Q Q Q Q Watchdog Watchdog Watchdog Q Q TCS Q Q Q Q LCB Tx service 1553 Tx service LCB Tx service Q Q Q From SIU From EPU(s) Event Assembly Event Builder (EB) input side. The EB is an element of the GASU. Command/Response Unit (CRU). The CRU is an element of the GASU.

  5. Technical Approach • FSW is LAT controller • Philosophy is to do what must be done in real time onboard but defer more complicated decisions to ISOC on ground • Provides a high level interface to control LAT • FSW development is following an iterative model • Functionality is developed and tested against available HW • Errors are corrected • Additional functionality is developed and validated against newer hardware

  6. FSW Update Process • 1) Software Change Request Issued • 2) Investigate SCR • a) Action required? • If NO, close SCR with explanation • 3) Design FSW Revision/Update • 4) Review the Design of FSW Revision/Update • a) Design acceptable? • If NO, return to Step 3 • 5) Produce Revised Code • 6) Review Revised Code • a) Code acceptable? • If NO, return to Step 3 or Step 5 • 7) Test Revised Code against Testbed • a) Test passed? • If NO, return to Step 3 or Step 5 • 8) Deliver Update • 9) Close SCR

  7. FSW Status • Team is in place • Flight Unit level coding is underway • SW Integration phase is Q4 • Builds produced as needed to support I&T • SW Test Scripts underway, completion in Q4 • FSW Qualification Testing begins January 2005

  8. FSW Team • JJ Russell – architect, event SW designer • Tony Waite – technical lead, ITC designer • Sergio Maldado – Housekeeping, Cmd Telemetry • James Swain – LATC, DAQ, LEM • Steve Mazzoni – Watchdog, Thermal Control, ISIS

  9. FSW Team (cont’d) • Ed Costello – Charge Injection Calibration • Ed Bacho – LCB driver, ISIS • Owen Saxton – FES Simulation • Kim Lo- CM/builds • Mark Arndt – Documentation • Rich Morin – Web Pages/Doc • NRL – Boot, File System, Attitude Processing

  10. FSW Test Process • Allocate mission requirements to FSW • 198 Requirements have been identified • Develop FSW Test Plan • All requirements are mapped to test procedures • The set of procedures contains scripts that demonstrate the requirements

  11. FSW Test Status • Draft of LAT SW Test Plan created • All mission requirements applicable to FSW have been allocated • Requirements have been allocated to test procedures • HW requirements for the test procedures have been identified • Test development schedule is in place

  12. FSW Test Team - Current Focus • Eric Hansen (Lead, ISIS, modes, diagnostics) • Igor Kouzenko ( TKR, CAL,ACD) • Tbh1 (commands, telemetry, initialization) • Tbh2 (physics)

More Related