140 likes | 391 Views
RBSP EFW CTG. Command, Telemetry, and Ground Support Equipment (CTG). Will Rachelson UC Berkeley Space Sciences Lab wrachelson@ssl.berkeley.edu. Outline of CTG Topics. CTG Requirements and Functions GSE during Instrument Integration and Test Board-level configurations
E N D
RBSP EFW CTG Command, Telemetry, andGround Support Equipment(CTG) Will Rachelson UC Berkeley Space Sciences Lab wrachelson@ssl.berkeley.edu EFW INST+SOC PDR
Outline of CTG Topics • CTG Requirements and Functions • GSE during Instrument Integration and Test • Board-level configurations • GSE Backplane Interface Board • CTG MOC Interface • GSEOS • GSE-Related Milestones and Progress EFW INST+SOC PDR
Functions of CTG • CTG design driven by requirements described in: • Project Data Management Plan • SOC Software Development Plan • MOC-SOC ICD • SOC Requirements Document • EFW Subsystem Specification Docs • The Matrix (Section 15 = GSE) • Primary Functions of the CTG: • Support instrument and spacecraft integration and test (I&T). • Provide the communications layer to and from the MOC as required by the MOC-SOC ICD. • Monitor basic instrument state of health (SOH) through the production of quick-look and trended SOH products. EFW INST+SOC PDR
Instrument Integration and Test • This is the general configuration of the GSE used to bring up the individual boards of the IDPU, as well as in testing the integrated IDPU. • IDPU boards have low level hardware interfaces, so GSE Backplane Interface Board is needed to control them from the GSE PC. • GSE PC runs GSEOS, which is extended to talk to devices such as the GPIB test equipment, the Backplane Interface Board, and the Spacecraft Emulator. EFW INST+SOC PDR
GSE Supporting BEB Testing • DCB not yet available to command the BEB, so GSE I/F board acts as a DCB. Devices under test housed in VME card cage. • Allows GSE to make DC and AC transfer function measurements (gain, offset, phase, DAC calibration) on the combined Sensor/Preamp/BEB system. • GPIB-controlled signal generator provides semi-realistic stimulus to BEB sensor inputs. • “SciCal GSE” provides the functionality of relevant sections of the LVPS. • GSE laptop uses GSEOS to command low-level hardware interfaces (GPIB, USB) EFW INST+SOC PDR
GSE Supporting DCB Testing • This configuration is for testing the DCB by itself, primarily to exercise the DCB’s flight software. • Backplane Interface board provides I/O to DCB (as DFB for test pattern generation). • Spacecraft Emulator provides communication with DCB through S/C Interface • GSE laptop uses GSEOS to command low-level hardware interfaces (GPIB, USB) EFW INST+SOC PDR
GSE Supporting PCB (LVPS) Testing • GSE used to program the LVPS’s shift register to command motors/actuators, as well as read back housekeeping values. • Backplane Interface board provides I/O to PCB (as DCB). • GSE laptop uses GSEOS modules to command the LVPS modes. EFW INST+SOC PDR
GSE Supporting IDPU Level Integration • This configuration is the three previous setups combined into one. • Primary GSE interface at this level is through the S/C Emulator. • GSE Computer can command optional test equipment as needed for test procedures EFW INST+SOC PDR
GSE Backplane I/F Board Interface board from THEMIS • Allows GSE PC to command individual boards over a USB interface – an FPGA receives commands from the PC, performs low-level I/O, and sends back data. • Many circuits duplicated from the DCB. • Separate Power Supply to reduce noise. EFW INST+SOC PDR
CTG MOC Interface Configuration Overview • Command interface to MOC via TCP/IP (1 per S/C) • Generate validated instrument commands and upload to MOC queues for execution • Receive science and housekeeping data from the MOC • Monitor Instrument state of health, respond to alerts • Process data and distribute products • On-Orbit Realtime Ops • Verify correct UTC<->MET time conversions • Equipment located in IT-secure area (authorized user list). EFW INST+SOC PDR
GSEOS Screenshot of GSEOS during DCB Breadboard Testing • Standard features: • ITF, CCSDS formats • Logging • Trending displays • Limit Checking • Command Encoding • Telemetry Decoding • Scripting (STOL/Python) • Multiple views • EFW Customizations: • Populated Command/Telemetry database with limit definitions • Notification/paging mechanisms • Low level routines to talk to GBIP test equipment and other hardware • Scripts used for testing • MOC interface as specified in MOC-SOC ICD EFW INST+SOC PDR
CTG Milestones and Status Milestones: • DCB ETU Testing – Oct 2008 • Requires: GSE I/F Board, GSEOS basic features, S/C Emulator • BEB ETU Testing – November 2008 • Requires: SciCal GSE, GSEOS BEB extensions, GSE I/F Board • LVPS ETU Testing – November 2008 • Requires: GSE I/F Board, GSEOS LVPS extensions • IDPU ETU – Delivery to I&T Feb 2009 • Requires: GSEOS EFW extensions, S/C Emulator • Status: • GSE I/F Board: • Schematic completed, ready for layout • GSEOS: • Basic features already used with S/C Emulator to test DCB Breadboard (July 2008) • Displays decoded CCSDS packets and raw data • Needs to be extended to command the GSE I/F board, GPIB hardware, decode EFW telemetry, encode commands, communicate with MOC, etc. • S/C Emulator: • APL Mini-Emulator delivered and tested with DCB breadboard. • BEB SciCal GSE: • Bench power supplies purchased EFW INST+SOC PDR