1 / 34

TDS Flight Software

TDS Flight Software. Jason Hinze University of Minnesota. Roadmap. TDS hardware overview FSW development tools and techniques FSW l evel 4 requirements FSW h igh-level design diagram FSW subsystem descriptions. TDS Hardware Overview. TDS FSW Development Tools and Techniques.

elysia
Download Presentation

TDS Flight Software

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. TDS Flight Software Jason Hinze University of Minnesota

  2. Roadmap TDS hardware overview FSW development tools and techniques FSW level 4 requirements FSW high-level design diagram FSW subsystem descriptions

  3. TDS Hardware Overview

  4. TDS FSWDevelopment Tools and Techniques Highly-orthogonal C code modules Minimal SPARC assembly language Lightweight task dispatcher GCC cross-compiler suite Subversion (SVN) repository Heritage code from STEREO/WAVES FSW Shared code with FIELDS DCB FSW

  5. FIELDS Flight Software Level 4 Requirements, Part 1

  6. FIELDS Flight Software Level 4 Requirements, Part 2

  7. TDSFlight SoftwareLevel 4 Requirements

  8. TDS FSWHigh-level Design Diagram

  9. System Manager SubsystemLevel 5 Requirements

  10. System Manager SubsystemDescription Initializes CPU and memories at boot-time. Selects and invokes software images from EEPROM. Coordinates transitions to/from Safe Mode. Programs and dumps EEPROM. Writes and dumps CPU RAM.

  11. Spacecraft Interface SubsystemLevel 5Requirements

  12. Spacecraft Interface SubsystemDescription Drives the two bulk asynchronous serial port peripherals connected to the A/B communication links to the spacecraft. Receives Spacecraft Time and Status Message from the spacecraft. Forwards spacecraft time information to Real-Time Clock subsystem. Sends Instrument Critical Housekeeping Data to the spacecraft. Receives telecommands from the spacecraft. Sends telemetry to the spacecraft via the active serial port.

  13. DCB Interface SubsystemLevel 5 Requirements

  14. DCB Interface SubsystemDescription Drives the CDI slave peripheral connected to the DCB. Receives the Spacecraft Clock Message from the DCB. Forwards time information to the Real-Time Clock subsystem. Receives telecommands from the DCB Sends telemetry to the DCB Coordinates TDS/DCB failover activities.

  15. MAGi Interface SubsystemLevel 5 Requirements

  16. MAGi Interface SubsystemDescription • Drives the CDI master peripheral connected to MAGi. • Sends Sample Clock Messages to MAGi. • Sends commands to MAGi. • Collects raw magnetometer data from MAGi. • Reduces magnetometer data for Coordinated Burst Signal. • Reduces magnetometer data for SWEAP. • Reduces magnetometer data for science telemetry. • Generates CCSDS telemetry packets from science telemetry data. • Low-rate data to the Spacecraft • High-rate data to the DCB

  17. SWEAP Interface SubsystemLevel 5 Requirements

  18. SWEAP Interface SubsystemDescription Drives the CDI master peripheral connected to SWEAP. Sends Sample Clock Messages to SWEAP. Collects health and status information from SWEAP. Sends commands to SWEAP. Sends the SWEAP-format magnetometer data vector to SWEAP. Sends the Coordinated Burst Signal from the DCB to SWEAP.

  19. AEB2 Interface SubsystemLevel 5 Requirements

  20. AEB2 Interface SubsystemDescription Collects health and status information from AEB2. Controls the antenna electronics in AEB2.

  21. LNPS2 Interface SubsystemLevel 5 Requirements

  22. LNPS2 Interface SubsystemDescription Collects health and status information from LNPS2. Controls the electronics in LNPS2.

  23. TDS Acquisition SubsystemLevel 5 Requirements

  24. TDS Acquisition SubsystemDescription • Controls analog muxes to select TDS channel inputs. • Multiple plasma wave E-field data sources • Plasma wave B-field data source • One additional pseudo-channel collects SWEAP particle counts. • Calculates a quality metric for each acquired TDS event. • Directs the TDS memory controller to store the next acquired event into the buffer corresponding to the lowest-quality stored event. • Telemeters the highest-quality stored event when telemetry allocation is available. • Generates CCSDS telemetry packets from selected TDS event.

  25. Housekeeping SubsystemLevel 5 Requirements

  26. Housekeeping SubsystemDescription Collects health and status data from all subsystems. Generates CCSDS telemetry packets from collected health and status data.

  27. Instrument Status Reporting SubsystemLevel 5 Requirements

  28. Instrument Status Reporting SubsystemDescription Collects instrument status data from all subsystems. Generates CCSDS telemetry packets from collected instrument status data.

  29. Telemetry Manager SubsystemLevel 5 Requirements

  30. Telemetry Manager SubsystemDescription • Receives CCSDS telemetry data from all telemetry-generating subsystems. • Applies quota and priority constraints to telemetry stream by APID. • Routes telemetry to Spacecraft Interface or DCB Interface by APID. • Distinct routing criteria for master and slave mode.

  31. Command Manager SubsystemLevel 5 Requirements

  32. Command Manager SubsystemDescription Receives telecommands from Spacecraft Interface. Receives telecommands from DCB Interface. Receives local commands from local command sources. Distributes commands to all subsystems as needed.

  33. Real-Time Clock SubsystemLevel 5 Requirements

  34. Real-Time Clock SubsystemDescription Maintains a real-time clock synced to the spacecraft. Maintains a real-time clock synced to the DCB. Selects a real-time clock for local use depending on current failover mode. Makes selected real-time clock available to all subsystems.

More Related