Telemetry Processing and Archiving − 1 Telemetry Flows, Processing and Archiving

Telemetry Processing and Archiving − 2 Data Flows Swales I&T Facility Berkeley Mission Operations Center White Sands Complex (WDISC) Compatibility Test Van GSFC NMC Wallops Ground Station Different Routes for End-to-end Data Flows Between Probes and GDS Elements Berkeley Ground Station THEMIS Probe Secure Intranet TDRS Secure VPN Tunnel Via Open Internet Open / Closed IONet Open IONet Hartebeesthoek Ground Station Dial-up Phone Line Santiago Ground Station Merritt Island Ground Station KSC & Astrotech UCB I&T Facility

Telemetry Processing and Archiving − 3 HBK Data Flows Detail of Data Flows Between MOC and HBK ITOS Workstations for HBK Passes Are Completely Isolated from Other Networks

Telemetry Processing and Archiving − 4 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

Telemetry Processing and Archiving − 5 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

Telemetry Processing and Archiving − 6 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

Telemetry Processing and Archiving − 7 Frame Routing Details

Telemetry Processing and Archiving − 8 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 Processing and Archiving − 9 TLM Data Routing During I&T

Telemetry Processing and Archiving − 10 Telemetry Data Format Virtual ChannelPriorityData TypeData Source VC00Real-timeProbe State-of-health Data (BAU) VC11PlaybackProbe State-of-health Data (BAU) VC22Real-timeInstrument Data (IDPU) VC33PlaybackInstrument Data (IDPU) VC4N/ANot Used VC5N/ANot Used VC64PlaybackProbe Bus Events (BAU) VC75Fill DataGenerated Fill Data (CIM) 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 Processing and Archiving − 11 Telemetry Data Delivery Data RoutingTransfer MediumVirtual ChannelsMaximum Data Rate BGS to MOC/SOC Secure Local Area Network (100 Mbps) VC0, VC1, VC2, VC kbps NASA/GN to MOC/SOC Secure, Shared TCP/IP Network Connection (T1 Line, 1.5 Mbps) VC0, VC2, VC kbps MOC to HBK Dial-Up Modem Line (56 kbps) (TBD) VC kbps WDISC to MOC Secure, Shared TCP/IP Network Connection (T1 Line, 1.5 Mbps) VC kbps I&T to MOC/SOC Secure TCP/IP Connection via VPN VC0, VC1, VC2, VC3, VC6 Limited by Open Internet 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 Processing and Archiving − 12 Telemetry Data Delivery Data RoutingTransfer Medium Virtual Channels Maximum Data Volume / Pass Latency BGS to MOC/SOC Secure Local Area Network (100 Mbps) VC0, VC1, VC2, VC3, VC6 225 MBytes Required: 1 hour Desired: 30 min WLP, MILA to MOC/SOC Open Internet VC0, VC1, VC2, VC3, VC6 225 MBytesRequired: 24 hours Desired: 12 hours AGO, HBK to MOC/SOC Open Internet VC0, VC1, VC2, VC3, VC6 225 MBytesRequired: 24 hours Desired: 12 hours WSC to MOC/SOC N/AVC0N/A I&T to MOC/SOCOpen Internet VC0, VC1, VC2, VC3, VC6 VariableN/A Delivery of Stored Telemetry Data Post-pass File Transfer Initiated by Ground Station or MOC

Telemetry Processing and Archiving − 13 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_ dat –WLP.THEMIS_B.TLM_VC1.2007_029_ dat –MIL.THEMIS_C.TLM_VC2.2007_038_ dat –AGO.THEMIS_D.TLM_VC3.2007_032_ dat –HBK.THEMIS_E.TLM_VC6.2007_034_ dat –WSC.THEMIS_A.TLM_VC0.2006_301_ dat –SSL.THEMIS_A.TLM_VC0.2006_003_ dat –SAI.THEMIS_A.TLM_VC0.2006_003_ dat –JPL.THEMIS_A.TLM_VC0.2006_003_ dat –KSC.THEMIS_A.TLM_VC0.2006_003_ dat File Transfer from SAFS –tha p03vc0.dat –thb p03vc3.dat

Telemetry Processing and Archiving − 14 Data TypeBGS 11mWLP 11mMILA 9mAGO 9mHBK 10mSN Real-time Telemetry DataSMEX PFLPSMEX Post-pass Telemetry DataSMEX PFLPN/A Real-time Command Data TLM & CMD Header Utilization SMEX Header:Also Known as EDOS Header PFLP Header:Provided by Enertec Systems

Telemetry Processing and Archiving − 15 Network Certification Matrix Network Function TestedBGS 11mWLP 11mMILA 9mAGO 9mHBK 10mSN Receive System Performance Long-loop Telemetry Playback Firewall Configuration IP Network Connectivity to FrameRouter Real-time TLM Data Transfer to MOC Real-time CMD Data Transfer from MOC Real-time TRK Data Transfer to FDC Post-pass TLM File Transfer to MOC Post-pass UTDF File Transfer to FDC Acquisition Vector Transfer Pass Schedule Transfer to/from DSMC Clock Correlation / Time TaggingN/A WDISC Remote Control InterfaceN/A SWSI Remote Control InterfaceN/A Voice Loop MOC-to-Facility Complete Pass & Mission Simulations

Telemetry Processing and Archiving − 16 Telemetry Processing at JPL Probe ITOS FrameRouter Jim’s Packet Splitter FilterForward Real-time IGSE Packet Files

Telemetry Processing and Archiving − 17 Telemetry Processing Probe Ground Station Tim’s SOC Processing

Telemetry Processing and Archiving − 18 Telemetry Processing Level 0 Packet Files by APID Level 1 ??? Level 2 CDF Files

Telemetry Processing and Archiving − 19 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

Telemetry Processing and Archiving − 20 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

Telemetry Processing and Archiving − 21 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