210 likes | 357 Views
Telemetry Flows, Processing and Archiving. Data Flows. THEMIS Probe. TDRS. Berkeley Ground Station. Wallops Ground Station. KSC & Astrotech. Merritt Island Ground Station. Compatibility Test Van. Swales I&T Facility. UCB I&T Facility. White Sands Complex (WDISC). Secure
E N D
Telemetry Flows, • Processing and Archiving
Data Flows THEMIS Probe TDRS Berkeley Ground Station Wallops Ground Station KSC & Astrotech Merritt Island Ground Station Compatibility Test Van Swales I&T Facility UCB I&T Facility White Sands Complex (WDISC) Secure Intranet Santiago Ground Station Secure VPN Tunnel Via Open Internet Open / Closed IONet GSFC NMC Open IONet Dial-up Phone Line Berkeley Mission Operations Center Hartebeesthoek Ground Station Different Routes for End-to-end Data Flows Between Probes and GDS Elements
HBK Data Flows • Detail of Data Flows Between MOC and HBK • ITOS Workstations for HBK Passes Are Completely Isolated from Other Networks
Network Topology Secure Network Topology CheckPoint Firewall at MOC Controls Network Traffic Between Four Secure Subnets: 1. Isolated Operations Network (ION) Hosts ITOS Workstations and Flight Dynamics Systems 2. Berkeley Ground Station (BGS) Subnet Hosts All Ground Station Systems 3. NASA Open/Restricted/Closed IONet Access Via T-1 Line 4. THEMIS I&T Subnet – Partly Via VPN Tunnel Across Open Internet Firewall Rules Configured to Only Allow Very Restricted Access Between Subnets, Ensuring Proper Security On All Network Segments ITOS Workstations Configured and Tested During I&T − No Change for On-orbit Operations Required
Mission Control Network Network Architecture All Ground Stations and I&T Systems Connect to Dedicated Ports on Primary IP Frame Router to Establish TLM and CMD Socket Connections Router Switches TLM and CMD Socket Connections Through to Multiple ITOS Systems Process Controlled by Automated Scheduling System
TLM & CMD Data Routing • Telemetry & Command Routing Scheme • Frame Router Acts as Server • Provides Matrix Switching Capability • Connections Based on Scheduling Information from SatTrack Gateway Server or via Operator Commands • Handles Incoming Connections from Ground Stations, White Sands Complex, I&T EGSE Racks and ITOS Systems • Port Assignment • Each Ground Station and Spacecraft Control Client (ITOS) Has Dedicated Ports for TLM, CMD & CTL • Spacecraft Control Clients (ITOS) Are Patched Through to Any Ground Station via Switch Configuration in Routing Matrix • Science Data Tool (SDT): Connects to Secondary Frame Router • Standard Frame Format with SMEX/EDOS Header for All Data Flows • I&T End-to-end Tests • Ground Stations • Space Network
Routing of Data Streams Linking FrameRouter and FrameRelay Allows Distribution of Real-time Telemetry Data to Many ITOS Workstations Remote Control via SatTrack Gateway Server
Telemetry Data Format • Telemetry Data Format • CCSDS V1 Frame Format • Telemetry Data Routed by Virtual Channels • Annotated Channel Access Data Units (CADUs): 1274 Bytes • SMEX/EDOS Annotation Header: 10 bytes (Generated at Ground Station) • Attached Synchronization Marker: 4 bytes • Virtual Channel Data Unit: 1100 bytes • Reed-Solomon Code Trailer: 160 bytes
Telemetry Data Delivery • Delivery of Real-time Telemetry Data • TCP/IP Network Socket Connection (BGS/GN/SN) • Initiated by Ground Station • Dial-up Modem Line (HBK) • Call Initiated by MOC
Telemetry Data Delivery • Delivery of Stored Telemetry Data • Post-pass File Transfer • Initiated by Ground Station or MOC
Telemetry File Naming • Telemetry File Naming Conventions • Format • FACILITY.PROBE_BUS_NAME.TLM_VCN.YYYY_DDD_HHMMSS.dat • Examples • BGS.THEMIS_A.TLM_VC0.2007_028_060312.dat • WLP.THEMIS_B.TLM_VC1.2007_029_012031.dat • MIL.THEMIS_C.TLM_VC2.2007_038_102319.dat • AGO.THEMIS_D.TLM_VC3.2007_032_151745.dat • HBK.THEMIS_E.TLM_VC6.2007_034_234512.dat • WSC.THEMIS_A.TLM_VC0.2006_301_001834.dat • SSL.THEMIS_A.TLM_VC0.2006_003_121132.dat • SAI.THEMIS_A.TLM_VC0.2006_003_121132.dat • JPL.THEMIS_A.TLM_VC0.2006_003_121132.dat • KSC.THEMIS_A.TLM_VC0.2006_003_121132.dat • File Transfer from SAFS • tha20061217235417p03vc0.dat • thb20061218223421p03vc3.dat
TLM & CMD Header Utilization SMEX Header: Also Known as EDOS Header PFLP Header: Provided by Enertec Systems
Telemetry Processing at JPL Probe ITOS FilterForward FrameRouter Real-time IGSE Jim’s Packet Splitter Packet Files
Telemetry Processing Probe Ground Station Tim’s SOC Processing
Telemetry Processing Level 0 Packet Files by APID Level 1 ??? Level 2 CDF Files
BTAPS Requirements • BTAPS Requirements • Application • Multi-mission Trending and Plotting System • Used with RHESSI and THEMIS • MySQL Database • Hold All BAU and IDPU Engineering Data For Life of Mission • Total Data Volume 56 GBytes for 3 Years • Decommutate Telemetry Packets • Store Data in Physical Units • Include Data Quality Checks and Verification • Packet Lengths • THEMIS Packets May Cross Frame Boundaries • Separate Engineering Conversion Table for Each Probe • Conversions May Change Over Time • Web Interface for Data Access • Output Data in ASCII Format Over Any Time Range • Graphics Capability • Plots Over Any Time Range • Include Up To Six Telemetry Mnemonics on One Plot • Plot Mnemonics Versus Time or Other Mnemonics
BTAPS Implementation • BTAPS Implementation • In-house Development at SSL • Programming Language (PERL, MySQL, PHPLOT) • Solaris and Linux Platform Support • Development of Tools for Procedure and Feature Testing • Develop Individual Tools for Various Tasks • Data Acquisition • Database Handling • Plotting • Web Interfaces • Project Duration • Prototype Version Completed One Year Prior to THEMIS Launch • Operational Version Completed and Tested by THEMIS FOR • Configuration Control • Standard Workspace SVN Control
Future Points of Discussion • Real-time Science Data Flows • Usage of VC2 Instead of VC3 Telemetry Data for Instrument Testing • Ephemeris Products • Product Generation • Integration of Ephemeris into CDF Products • Pass Scheduling • Scheduling Process • Format of Pass Schedule Files