1 Aquarius Command and Control System pre-CDR. Aquarius Command and Control System pre-CDR Agenda

1

Aquarius Command and Control System pre-CDR

Aquarius Command and Control System pre-CDR Agenda

3

Agenda

• Aquarius Science Mission Overview• Aquarius/SACD Ground System Overview• NASA Ground Network AQ/SACD Support• Ocean Biology Network and Information Technology Security• Aquarius Operations Concept – Nominal• Aquarius Operations Concept – Anomaly• Aquarius Command and Control Requirements• Aquarius Command and Control Design• Aquarius Test Bed• Aquarius Command and Control Test Plan• Risks

Acronym List and Backup Slides provided

Aquarius Science Mission Overview

5

Understanding the Interactions Between the Ocean Circulation, Global Water Cycle and Climate by Measuring Sea Surface Salinity

Aquarius Mission Science

WOA 2001 NOAA/NODC

22/3)()()(),( dSSTcSTbTTS

WaterSeaforStateofEquation

fwsw +++=ρρGlobal salinity patterns are linked to rainfall and evaporation

Salinity affects seawater density, which in turn governs ocean circulation and climate

The higher salinity of the Atlantic sustains the oceanic deep overturning circulation

Salinity variations are driven by precipitation, evaporation, runoff and ice freezing and melting

6

Science Objectives and the need for Satellite Measurements

This diagram shows the sampling distribution of all the historical surface salinity measurements

• The data are much too sparse to monitor salinity variations over space and time.

• Systematic global mapping is required to study the climatic interactions between the ocean and atmosphere

• Science Requirements: Global coverage, 150 km and monthly space/time resolution, 0.2 psu accuracy, three year mission

World Ocean Atlas

Science Objectives:

• Determine the mean global surface salinity field, including vast under-sampled regions

• Resolve the seasonal cycle

• Track interannual variations linked to changes in the water cycle and ocean currents

• Improve El Niño predictability

• Reduce the large uncertainty in the marine hydrological budget and its variability

• 86% of mean global evaporation and 78% of global precipitation occur over the ocean

• Better initialize surface hydrology in climate models to improve climate prediction

7

The Aquarius/SAC-D Salinity Mission

Approach: • Integrated L-band ultra-stable

microwave radiometer-radar, 3 fixed beams, 390 km wide swath, 7-day repeat polar orbit

• Monthly averages to reduce measurement noise and achieve 0.2 psu RMS accuracy

• Three year baseline mission to resolve seasonal to interannual variability and robust mean field

• Independent calibration and validation from global in situ ocean observing system

Sensitivity vs Radiometer Frequency

1400-1427 MHz Protected Band

Tb=εT

ε = f(S, T, Freq, Incidence)

WOA 2001 NOAA/NODC

Aquarius/SAC-D is designed to observe the global surface salinity field for three years and to achieve a monthly accuracy that will resolve the

seasonal and interannual variability at 150 km scales.

8

Aquarius Instrument Block Diagram

Aquarius/SACD System Overview

10

Division of Responsibilities

• Pre-Launch

– PI• Defines science requirements

– JPL• Scatterometer development• Project management

– CONAE• SAC-D spacecraft and ground system development

– GSFC• Radiometer development• Aquarius instrument data processing development• Aquarius instrument Mission Operations development

• Post-Launch / Commissioning

– PI• Science management

– JPL• Ad-hoc support as requested by the PI• PO.DAAC archive and distribution of validated Aquarius data

– CONAE• SAC-D spacecraft and ground system operation

– GSFC• Project management• Aquarius instrument data processing, archive, distribution• Aquarius instrument Mission Operations

11

NASA Ocean Biology Processing Group

• Located: Goddard Space Flight Center

• Total Archive size: 332 TB

• Distribution (> 2/04): 27 million files

● Aquarius support is implemented within the framework and facilities of the current NASA Ocean Data Processing System (ODPS) which has been successfully supporting operational, satellite-based remote-sensing missions since 1996, and its capabilities continue to evolve and expand to meet the demands and challenges of future missions

●MISSIONS SUPPORTED• SeaWiFS : 1997 - active• MODIS (Terra and Aqua) : 2000 -

present • CZCS / Nimbus-7 : 1978 - 1986• OCTS / ADEOS-I : 1996 - 1997• Glory data system prototype : 2009

launch• Aquarius / SAC-D : May 2010 launch• VIIRS / NPP : June 2010 launch• Community Processing & Analysis

Software SeaDAS (1991- present)

Consolidated data access,information services and community feedback

oceancolor.gsfc.nasa.gov

12

NASA Management: Oversight of the overall effort, communication/coordination with other NASA organizations and centers and CONAE; oversight of science support, algorithm integration, QC, validation and in situ data support.

Contractor Management: Oversight of contract support staff, including hiring, tasking, review of deliverables and schedules.

Mission Operations: Technical lead for instrument operations and commanding support; interface to instrument engineers and CONAE mission operations.

Systems Engineering and Interface Definition: Technical lead for the data system effort; overall system design, implementation schedule, interface definition, data format specification, reviews and presentations.

Software Engineering: Technical lead for the level conversion / product generation software, including development of the Level 0-to-1 software and integration/packaging of the science (Level 2 and 3) processing software to be provided by the algorithm developers.

Software Development: Support for science code packaging, integration and testing.

Data Systems Support: Integrate the product generation software into the existing automated processing system, develop ingest modules, develop database tables for archive products, develop schedules and recipes for data acquisition, production and migration.

Systems Administration: Specify and acquire new processing and data storage hardware, integrate into existing data processing facility, verify/upgrade network capability for external data transfers.

Quality Control and Validation: Working with the Science Team, develop methodologies, tools, procedures and reports for operational QC; specify data and develop algorithms and tools for data and science algorithm validation.

In Situ Data Support: Work closely with the Aquarius Validation Data System (AVDS) to develop methods and tools for data analysis and quality control, building upon the existing SeaWiFS Bio-optical Archive and Storage System (SeaBASS).

Archive and Distribution: Incorporate Aquarius product browse, search, order and distribution into existing web-based Ocean Color capability and work with JPL PO.DAAC regarding “institutional” archive support requirements.

Aquarius Ground System Responsibilities

Benefits of Discipline-based Processing - Pool of existing expertise at 10 cents on the dollar

13

ADPS ACCSAquarius AquariusData Command &Processing ControlSystem System

Aquarius Ground System Interfaces

14


CONAEMission RFOperations

ServicesCommandCenter

Aquarius Command SchedulesAnd Reports

S-Band

X-Band

Schedule ConfirmationAnd Reports

X-Band

Matera

Cordoba


15





S-Band

X-Band

Wallops Svalbard Alaska McMurdo

NASA Ground Network

S-Band

Vandenberg

CommandsReal-TimeTelemetry &Coordination


X-Band

Matera

Cordoba


16





S-Band

X-Band


NASA Ground Network

Principal Investigator andScience Planning Team

Calibration &Instrument

ConfigurationChange Requests

InstrumentEngineering Team

S-Band

Vandenberg



X-Band

Matera

Cordoba


17


CONAEDataArchive

S-Band

X-Band X-Band

Matera

Cordoba

Mission RFOperations



18


CONAEDataArchive

S-Band

X-Band X-Band

Matera

Cordoba

Mission RFOperations


2 downlinks / day

3 - 5 downlinks / day


19


CONAEDataArchive

S-Band

X-Band

Aquarius Data and Telemetry

Pre-Processor

X-Band

Matera

Cordoba


20


CONAEDataArchive

S-Band

X-Band


Pre-Processor

X-Band

Matera

Cordoba


21


CONAEDataArchive

S-Band

X-Band


Ancillary Data Sources

Pre-Processor

X-Band

Matera

Cordoba


22


CONAEDataArchive

S-Band

X-Band


Science Team andAlgorithm Providers

Algorithms &Science Code

Evaluation Products


Pre-Processor

X-Band

Matera

Cordoba


23


CONAEDataArchive

S-Band

X-Band




Evaluation Products


AVDS Aquarius ValidationData System

Insitu Data

Aquarius Data

Pre-Processor

X-Band

Matera

Cordoba


24


CONAEDataArchive

S-Band

X-Band




Evaluation Products



Insitu Data

Aquarius Data

PO.DAACLevel-1 & Level-3Aquarius Data

Data Users andScience Team

Aquarius L1, 2, 3 DataAncillary DataFeedback

Pre-Processor

SeaDASSoftware

X-Band

Matera

Cordoba


25


CONAEData Mission RFArchive Operations Services

CommandCenter


S-Band

X-Band



NASA Ground Network

Principal Investigator andScience Planning Team

Calibration &Instrument

ConfigurationChange Requests

InstrumentEngineering Team


S-Band

Vandenberg


Evaluation Products





Insitu Data

Aquarius Data

Pre-Processor

PO.DAACLevel-1 & Level-3Aquarius Data

Data Users andScience Team

Aquarius L1, 2, 3 DataAncillary DataFeedback

SeaDASSoftware

X-Band

Matera

Cordoba


NASA Ground Network AQ/SACD Support

Ocean Biology Network and Information Technology Security

Aquarius Operations Concept

Nominal

29

Operations Concept for Achieving Science Objectives

• Orbit description– Sun-synchronous, 6pm ascending node– 98 degree inclination– 657 +/- 1.5 km altitude– 7 day repeat track

• Orbit maneuvers approximately every 28 days (delta V)– +/- 10 km box maintenance– Box tolerance expanded during solar max– Inclination maneuvers possible but not planned into the mission

• Aquarius operated continuously• AQ Science data loss budget

– 2.4 days per month (30.4 days)– Based on maintenance of 0.1 degree thermal stability for AQ

• Optional Cold Sky Calibration Maneuvers– Estimated frequency of 1/month– Thermal transient expected to degrade science data for about 1 orbit

30

AQ/SACD Communications Links

• S-band 4kbps uplink

• S-band 4kbps downlink– Real time Housekeeping Telemetry (HKT)

– 4000 byte frame

– SAC-D, Aquarius and other instrument HKT (8 instruments total)

• X-band 16Mbps downlink– Stored HKT; identical format to the real time HKT frame

– Stored science data for all instruments

– CCSDS

– Aquarius allocation is 4Mbps

31

Operations Ground Station Network• Primary station is CONAE’s ETC facility in Cordoba, Argentina

– Aquarius requires a download at least once every 14 hours to avoid buffer overwrite– Single station provides approximately one d/l per 10 hours if both passes taken

• Orbit track typically takes AQ/SACD over ETC for two successive ascending passes and two successive descending passes.

– One station outage (one “pass set”) results in data overwrite

• Margin provided via the addition of a second X-band station– Italy’s ASI provides the Matera site– Global location is ideal for ETC backup;

• approximately 90 longitudinal degrees from Cordoba. • Higher latitude offers 3 successive ascending or descending passes vs. ETC’s 2.• Dual station outage now required to cause data loss. • System supports use of all available Matera passes

• ASI’s Malindi site in Kenya can be used for S-band downlink– Provides “first look” opportunity for launch vehicle separation, solar array deployment

• NASA Ground Network S-band support– S-band uplink/downlink– Emergency support– Maneuver support

32

Nominal Aquarius Commanding

• Nominal Aquarius commanding includes– Downlink commands

– Possible software maintenace commands

– Cold Sky Calibration targeting requests

• Possible Science commanding includes– Radiometer control commands

• Normally runs as a state machine from on-board Look Up Table (LUT)

• Science may request a change to a different LUT (7 pre-programmed, 1 programmable)

– Automatic thermal control system commands• Setpoint, Power, Integral, Derivative Parameter changes

33

Cold Sky Calibration

• The Cold Sky Calibration is a pitch maneuver under the control of CONAE but requested by the Aquarius science team– Purpose is to rotate Aquarius in the direction of cold space

– Specific cold location is selected by AQ science team

– Serves as an low temperature calibration point for the Radiometer

– Maneuver steps are to:• Pitch toward cold sky

• Cold Sky dwell is planned to be approximately 1 minute

• Pitch in the reverse direction back to earth pointing

• Maneuver occurs away from ground support– NGN provides pre- and post- look pass support

34

Aquarius Downlink• Two Aquarius instruments:

– Radiometer (primary)– Scatterometer (ancillary)

• Support subsystems:– Automatic Thermal Control– Power Distribution Unit– Instrument Command and Data Subsystem (ICDS)– Antenna, feeds and structure

• All subsystems forward science and HKT in fixed formats to the ICDS• ICDS packages HKT and science every 1.44 seconds

– Stored in the ICDS RAD6000 RAM– 110 MB of storage capacity– d/l command downloads buffer in circular fashion until stop cmd received– Passed through CCSDS formatter and on to X-band transmitter

• ICDS packages HKT and software messages in packetized form (vs. fixed format) every 8 seconds.

– 500 bytes– Passed to SACD and inserted into 4000 byte frame– Stored in SACD Mass Memory– When S-band transmitter is on, data is also sent to the ground in real time

35

High Level Description: Aquarius Command Planning Cycle

• Aquarius operations: – prepares two weeks of command loads each week– Forwards commands to the Planning System at ETC– Receives acknowledgement report that they were accepted as

feasible or not

• Approximately one week is available for changes• Then Observatory planning cycle is entered

– Aquarius commands are incorporated into SACD and other instrument command plans

– Final plan is reported back to Aquarius operations

• Plan is uploaded with any duplicate commands deleted

Aquarius Operations Concept

Anomaly

37

Anomaly Resolution Process• Process developed jointly by JPL, GSFC, CONAE Operations Assurance• In flight, the anomaly process is led by CONAE. • Process is captured in SACD document: SD-2510-0062, SAC-D FLIGHT

ANOMALY REPORTING PROCEDURE– Please note that the Science Operations Control Board (SOCB) in Aquarius

documentation equates to the SACD Flight Anomaly Review Board (SAFARB) in CONAE documentation.

• Instrument anomalies will be resolved by Aquarius team with process still led by CONAE

• Process:– Notify management (CONAE, then instrument)– Establish a resolution team led by a control board– Resolve the anomaly under control board authority

• Teams will rely on AQ and SACD testbeds to create and test problems and scripts

– Report the anomaly via the CONAE Flight Anomaly Report (FAR) system

• The Goddard Flight team will also file detailed Aquarius instrument anomaly reports on the Goddard reporting system. Aquarius reports will be sharable with JPL.

38

SAC-D Ops Team

Aquarius Ops Team

SAC-D Instrument Ops Team

Other data observer

Report anomalyReport anomaly

Report anomaly

Report anomaly

Any anomaly observer(s) immediately report the detected ground or Observatory problem to the Mission Operations Manager (MOM)

39

Gathers CONAE analysis team to identify problem source

Notifies Science Operations Control Board of the anomaly

Based on analysis result, MOM selects an anomaly resolution team

May require AQ or 3rd party instrument support; obtain via SOCB

Each SOCB member alerts his system team and selects anomaly resolution team members as needed

1a

1b

2

3

4

MOM initiates anomaly response and notification to formulate response team

40

Ops Team

Anomaly resolution team

Command plans

Cmd Plan execution reports (status reports)

Command plans

Observed telemetry changes and observations

Observed telemetry changes and observations

Feedback to MOM; “fix worked” or “more to be done” or “need more help”, etc

SOCB

Anomaly resolution plan approval

MOM manages anomaly resolution process with support of SOCB

Status to teams

Status to teams

41

Ops Team

Anomaly resolution team Anomaly

notes and logs

SOCB/CONAE

MOM generates and distributes final report; Aquarius anomalies may require an additional, separate report filed at GSFC by AQ GS

Anomaly notes and logs

Anomaly notes and logs

Final Report

Aquarius Final Report to GSFC Anomaly tracking system if appropriate

Aquarius Command and Control Requirements

43

ACCS Requirements, Verification and Validation Matrix

ID (AQ) G. Feldman Verification Method Test ID

L3-AQ-f-148 Requirement: The Aquarius Command and Control Segment shall review CONAE Operations Reports to verify that Aquarius command scripts are transmitted to the Observatory as planned.

Demonstration Test 1; include in ACCS operations procedures

L3-AQ-f-76 Requirement: The complete data file sharing interface between the SAC-D MOCC and the AQ GS ADPS shall be defined in the Aquarius Ground System Interface Control Document.

Analysis As captured in the stated ICD.

L3-AQ-f-78 Requirement: The Aquarius Command and Control Segment shall generate Aquarius instrument commands plans on the SAC-D MOC Scheduler using Aquarius commands and scripts stored on the CONAE database as defined in the SAC-D Ground to Aquarius Ground System ICD.

Demonstration Tests 1, 2

44


L3-AQ-f-146 Requirement: The Aquarius Command and Control Segment shall deliver to the SACD Ground System on an on-going basis for the life of the Aquarius mission the most recent approved versions of all Aquarius command scripts, telemetry scripts, telemetry pages, standard operating procedures and contingency operating procedures necessary for the ETC flight operations team to control and monitor the Aquarius instrument during real-time operations.

Analysis, Demonstration Analysis as captured in AQ GS operations procedures and processes. Demonstration via tests 1, 2.

L3-AQ-f-85 Requirement: The Aquarius Command and Control Segment shall monitor Aquarius instrument health and status by displaying and trending: instrument high rate science data; stored Aquarius House Keeping Telemetry; and selected SACD House Keeping Telemetry.

Demonstration Test a, k, m

45


L3-AQ-f-86 Requirement: The Aquarius Command and Control Segment shall monitor Aquarius instrument telemetry limits and generate indications of out of limits conditions such as audible alarms, printouts, or highlighted values on displays.

Demonstration Tests a, k, m

L3-AQ-f-96 Requirement: The Aquarius Ground System shall generate procedures for the test, validation via the Aquarius test-bed, and upload of instrument software patches via the CONAE MOC.

Analysis Ensure these procedures are included in the AQ GS operations procedure set.

L3-AQ-f-99 Requirement: The Aquarius Command and Control Segment shall have the capability of validating all real time commands to the Aquarius instrument on the Aquarius test-bed.

Demonstration Test l

46


L3-AQ-f-100 Requirement: The Aquarius Command and Control Segment shall submit all real-time command procedures not previously approved to the Science Operations Board for approval.

Analysis As captured in ACCS operations processes

L3-AQ-f-131 Requirement: The Aquarius Command and Control Segment shall document and place under configuration control all commands, scripts, flight software patches, and procedures that have been approved by the Science Operations Control Board.

Analysis As captured in ACCS operations processes and procedures

L3-AQ-f-111 Requirement: The ADPS shall support the archive of the full Aquarius mission data set including science, ancillary, and housekeeping telemetry data.

Analysis Ensure adequate storage exists (analysis completed)

47


L3-AQ-f-136 Requirement: The Aquarius Ground System shall be designed to be testable and verifiable consistent with mission test and verification plans.

Analysis Completion of the AQ GS V&V matrix.

L3-AQ-f-152 Requirement: The Aquarius Ground System shall provide a physical location for the Aquarius Testbed that accommodates the size, power, cleanliness, and thermal environment specified by the JPL Testbed team.

Analysis Receive size and environment specifications from JPL and establish a space that accommodates those.

48

ACCS Gold Rules Compliance Matrix

• Initial Gold Rules Compliance Matrix was generated in May, 2005

• Basis was the 12/10/04 release

• Verified full compliance; no waivers required

• Reviewed again by Steve Scott and David Durham (Aquarius Mission System Engineer) in 2008. Compliance verified.

ACCS Documents

50

ACCS Documentation• L3 Aquarius Ground System and Test Requirements

– AQ-328-0162– Final version available for distribution

• Aquarius Ground System Integration, Test and Training Plan– AQ-336-0244– Final version available for distribution

• Project Service Level Agreement– 451-PSLA-SACD– Final version available for distribution

• Aquarius Operations Processes and Procedures– Future document

• ACCS elements of the Aquarius Ground System to Science Team ICD– Future document; draft state

• AQ GS – SACD GS ICD is a CONAE document– Most recent version available for distribution. Final version due 4/18/08

• Aquarius/SACD Mission Plan is a CONAE document– Final version available for distribution

• Aquarius/SACD Flight Anomaly Reporting Procedure is a CONAE document. – Most recent version available for distribution. Final version due 4/18/08.

51

ACCS Configuration Management

• Ocean Biology Configuration Control via Subversion CM Tool• All ACCS code and documentation under CM

– Command and telemetry scripts– Executables (CONAE tools)– Processes and procedures– Instrument team receivable documents

• Subversion offers web-based access– supports shared configuration control of selected files with SACD– AQ command and telemetry dictionaries– AQ/SACD telemetry scripts and pages – CONAE procedures for AQ operations

• Subversion CM structure has been built and populated with preliminary documents

Aquarius Command and Control Design

53

AQ/SACD Ground System Overview

observatory

CGSSCONAE Ground System Services

SOCSpacecraft Operations Center

CODSCONAE Orbit Dynamics Service FC

Flight Control Subsystem

FUSSForeign User Segment Services

SOPSpacecraft Operations Planning

FGSSForeign Ground System Services

4kbps uplink Sband4kbps downlink Sband16Mbps downlink Xband

54

AQ/SACD GS Uplink Data Flow

observatory



CODSCONAE Orbit Dynamics Service

FCFlight Control Subsystem




4kbps uplink SbandNominal cmd path

Alt/Emerg cmd path

Reports / ARs

Pass plans

reports

Command frames

RF

reports

Pass plans

ARs Action Requests

55

AQ/SACD GS Low Rate Downlink Data Flow

observatory








4kbps downlink Sband

RF

RT Tlm

RT GPS / AOCS Tlm

RT EU Tlm

Orbit Files

RT EU Tlm Files

Nominal 4kbps d/l path

Emerg. 4kbps d/l path

56

AQ/SACD GS High Rate Downlink Data Flow

observatory








16Mbps downlink Xband

RF

Stored Data

Stored Data

Stored Science and AQ/SACD HKT Files

Nominal 16Mbps d/l path

Stored GPS / AOCS Tlm

57

AQ GS Overview I




SOPSpacecraft Planning Center

RT, Stored Data Files

Orbit Files

Action requests

reports

Emergency Voice, Email, Fax

58

AQ GS Overview II



ADPPAquarius Data Pre-processor


Science, HKT, Orbit Files

Orbit Files

Action requests

reports

ADPSAquarius Data Processing System

ACCSAquarius Command and Control System

CONAE

NASA

Science, HKT Files

Science, HKT Files

FUSS

Emergency Voice, Email, Fax

59

Uplink Interfaces, Data Flow


FCFlight Control

Action requests

reports


CONAE

NASA

observatory

Pass Plans

reports


Cmd logs

Pass Plans

RF cmds

RF cmd ack

CGSS

Cmd Frames

cmd ack

60

ACCS Uplink Tools and Actions


Action requests• commands• targeting

ACCS

CONAE

NASA

SInter

Scheduler Client

61

SInter

• SInter (Spacecraft Interpreter), a CONAE deliverable command scripting tool

• SInter example script (next slide)

• SInter used pre-flight– to command the instrument during I&T

– to populate CONAE “Basic Commands” database

– All Aquarius Basic Commands have been created and run successfully against the instrument computer (ICDS)

• SInter used during flight against the Aquarius testbed– for science change scripting

– for anomaly resolution scripting

• Software executables and scripts are maintained under CM

62

scl AQ::S_FOL_mode(integer: beam)require beamValues: beam >0 && beam < 4;

description-- beam_select: beam1=1, beam2=2, beam3=3

local bytes : OpCode,Param,chksum;

{ OpCode = Integer.AsShort(24577 ); Param = Integer.AsShort(beam ); chksum = (OpCode^Param); aqsd.cmd.aq( OpCode + Param + chksum );

}

Example SInter Command Script

63

Scheduler Client

• A CONAE deliverable

• GUI that supports Spacecraft Operations Planning

• Resides on the ACCS

• Interfaces with the CONAE Spacecraft Operations Planning system– Action Requests trigger CONAE planning activities

– For Aquarius, these are• Aquarius commands

• Aquarius Flight software patches (potential)

• Aquarius targeting (cold sky calibration) via Observatory maneuver

64

Action Requests

Generated via the ACCS Scheduler Client (CONAE) Sends to SOP via TCP/IP+HTTPS (ACCS-SOC_AR interface ) Checks Feasibility An individual Action Request includes: scl basic commands command parameters desired execution times preconditions for execution Action Requests support: commands flight software patch uploads cold sky targeting (wide system action)

65

Action Requests

• Generated via the ACCS Scheduler Client (CONAE)– sends to SOP via TCP/IP+HTTPS (ACCS-SOC_AR interface )

– checks Feasibility

• An individual Action Request includes:– scl basic commands

– command parameters

– desired execution times

– preconditions for execution

• Action Requests support:– commands

– flight software patch uploads

– cold sky targeting (wide system action)

66

Command Process

Example Only

67

Flight Software Patch Process

• Patch purpose: anomaly resolution

• JPL responsible for designing and bench testing patch

• ACCS responsible for operational testing against test bed

• Science Operations Control Board approves patch activity

• All patches are formatted as a sequence of Aquarius commands

• Nominal Action Request process followed

• Can be uploaded in realtime or as time-tagged cmds

• Other commands can be interspersed

• Aquarius provides notification of complete receipt of patch

• Flight operations executes final “install” command in real time

68

Flight Software Patch Sequence

• I_module_start – identifies the component ID to be patched– ID inherently specifies whether patch is new or replacement s/w– tells the FSW how many commands make up the patch– Automatically aborts any patch in progress

• I_module_part– One to many 60 byte commands containing patch data and a sequence number

• I_fragment– One or more patch commands of 58 bytes or fewer

• I_module_end– Contains patch checksum– Receipt causes instrument to verify all patch commands received– Sends messages to ground containing any missing patch sequence numbers

• Ground may send missing data, then re-issue I_module_end

– If all commands received, instrument computes checksum• Failed checksum forces discard of patch• “Failed” message inserted into HKT• Otherwise a “success” message is sent in HKT

• I_install_patch– Sent in real-time once successful I_module_end is confirmed– Includes component ID that must match the I_module_start component ID

69

Cold Sky Calibration Process

• Primarily a CONAE task requested by the Aquarius Science team

• Science team places request through the ACCS (TBD format)– Observatory targeting information provided

• SCI-ACCS restricted access email account utilized as the interface between science team and ACCS

• ACCS submits “Wide System Action” AR via the Scheduler Client, specifying cold sky maneuver and target.

70

Downlink Interfaces, Data Flow





RT, Stored Data FilesOrbit Files

Action requests

reports



CONAE

NASA

71

Aquarius Downlink Data




Orbit Files



CONAE

NASA

Observatory RT HKT files Observatory ST HKT files Aquarius Science Files, time sorted, duplicates deleted

Orbit Files Observatory RT HKT files Observatory ST HKT files Aquarius Science Files

72

Aquarius Data Pre-processor (ADPP)




Orbit Files



CONAE

NASA

73

Aquarius Data Pre-processor (ADPP)

• Purpose: to reduce bandwidth requirement– Unable to test the actual link until new MOC is installed– Initial testing provides baseline but no sure metrics

• Two ADPP systems placed at CONAE– Incoming data archived to both– Data fetched by ADPS from only primary ADPP– Configuration and scripting controlled by Goddard– Physical maintenance (if any) performed by CONAE– Sized to accommodate the entire mission, all file types, with margin

• ADPP retrieves orbit files from CODS– SFTP “pull”

• Retrieves Real time Observatory HKT files from SOC– SFTP “pull”– 4000 byte frames sent via S-band link– Frames contain SACD, Aquarius, and other instrument HKT

• Retrieves Stored Observatory HKT files from SOC• Retrieves Aquarius science files from SOC

– Time sorts data– Deletes duplicates

74

Aquarius Data Processing System




Orbit Files


ACCS

CONAE

NASA

Analysis Software

Telemetry Viewer

75

Aquarius Data Processing System

• Part of the Ocean Biology Processing System

• ADPS support for the ACCS includes:– Archive of all mission data including all HKT, science and orbit

files

– Forwards HKT files to the ACCS Telemetry Viewer tool• Sole source of Aquarius software messages

• Duplicates HKT stored in science files, but at lower sampling rate

– Provides science and HKT file access to the Aquarius analysis tools

76

ACCS Telemetry Viewer




Orbit Files


ACCS

CONAE

NASA

Analysis Software

Telemetry Viewer

77

ACCS Telemetry Viewer

• CONAE deliverable

• Purpose is to:– Be able to provide Aquarius telemetry viewing tools to CONAE

– Be able to view data exactly as CONAE does to support discussion of observations, anomaly diagnosis and resolution, etc.

78

tsl Tlmy::AQ.EXT_Temps_OMT1_Hprobe_Temp.Raw()

return bytes : out

label

-- AQ.EXT_Temps_OMT1_Hprobe_Temp.Raw

require

-- The script can be executed if a new 'AQ.Mechanical_Thermal.Message' arrived.

MessageArrived: AQ.Mechanical_Thermal.Message != <hex\ >;

description

-- raw AQ.EXT_Temps_OMT1_Hprobe_Temp

{

out = bytes.extract(AQ.Mechanical_Thermal.Message, 0,1);

}

(Show file)

Example Telemetry Viewer Script

79

ACCS Analysis Software




Orbit Files


ACCS

CONAE

NASA

Analysis Software

Telemetry Viewer

80

ACCS Analysis Software

• Based on the Radiometer FM I&T Analysis tools developed at Goddard

• Development plan:– Expand tools to include remaining instrument data

– Convert tools from Windows to Linux OS

– Investigating whether to convert tools from Matlab to IDL

– Include processing capability for HKT and ancillary data

– Mimic existing Ocean Biology web tools: Generate daily and long-term graphs; investigate creating mid-resolution graphs

– Post graphs to the Web via existing Ocean Biology tools

– Provide existing interactive capability from local machine(s)

81

ACCS Hardware and Link Analyses• Analysis showed that the following requirements apply to the ACCS computer:

– Ultra-secure network connections to CONAE and the ADPS (Windows OS)– Disk storage: 64 MB

• Executables• Command and telemetry scripts, pages (custom elements)• Working files (playback data)• Applies 100% margin

– RAM: 250 MB• Assessed by examining handle, thread, and process statistics with tools in use, especially at start-up• Extracted from basis of test computer providing 504 MB RAM

– Processing speed: 1.5 GHz• Assessed by examining CPU usage statistics while tools were active, especially at start-up• Tools were run on 1.5 GHz processor and demonstrated startup usage of 33% and post-start-up of 8% or less

• Specifications of existing ACCS hardware:– Disk storage: 255 GB – RAM: 2 GB– Processing speed: 3.01 GHz

• Link test results with CONAE– 10 day link test; SAC-C vs. SAC-D link– 87% success rate; transfers also under 12 minutes for 550 MB file (approx AQ fileset size)– 15% of total transferred but with very slow rates (~ 2 – 3 hours)– ADPP employed to increase margin– Examining alternate network options– True testing delayed until MOC upgrade in 2008

Aquarius Test Bed

83

Aquarius Test Bed Requirements

• Information: The AQ Flight Operations Testbed is a tool to investigate and recover from AQ anomalies, test unapproved command sequences and operations procedures, and validate FSW code uploads

• Requirement: All elements of the AQ flight instrument shall be replicated or simulated within the AQ Testbed

• Requirement: All elements of the AQ Testbed shall provide flight like telemetry and science responses to commands.

• Requirement: The ADPU element shall provide flight-like power levels to the Testbed.

• Requirement: The ICDS element shall provide flight-like Scatterometer science processing, ATC control, DPU communications, ground command handling, FSW upload capability, HKT handling and science packet handling.

• Requirement: The Testbed command and telemetry tools shall be identical to the Operational tools.

• Requirement: The Testbed command and telemetry tools shall interface with the AQ instrument via a SAC-D simulator.

• Information: The SAC-D simulator emulates the SAC-D Command and Data Handling System, the 1553 bus, the GPS 1PPS signal and interfaces to both the SAC-D command and telemetry tools and the AQ instrument portion of the Testbed.

SAC-D Cmd/Tlm Tools

S/P Simulator

ICDS full BB

High-rate data downlink sync and storage

1553Cmds/HKTs

1pps

DPU interfaceSimulator

Cmds/timing

Sci/telem

cmdstelem

Generic Reference clock and power supplies

SCAT interfaceSimulator

Aquarius Command and Data Test-bed (at GSFE after commissioning phase is complete. Before that: at JPL)

Thermal/deployment telemetry Simulator

Command/TLM/High-rate data software tools

sADC

4MbpsHigh-rate data

•The main goal of the Command and Data Test-bed is to verify commands are scripted correctly to be accepted by the instrument and echoed back properly in telemetry.

•If possible, EM DPU will be used instead of DPU simulator. This would interconnect the two test beds segments shown here.

•If a FSW patch is needed, it will be tested in a software test-bed first and then in the Command and Data Test-bed.

1553 sniffer

Command and Data Test-bed

ICDS SimulatorBCE & PC

DPU (EM)

Radiometer RF EMs:RBERFECND

Sci/telem

Cmds/timing

HKT

science

Cmds/timing

Radiometer Engineering Test-bed (at GSFC)

85

Test Bed Limitations• Ideal test bed perfectly replicates Observatory and space

environment• Limitations

– No vacuum, no radiation, no orbital variations, no seasonal variations simulated

– Only Radiometer offers some thermally controlled elements– Aquarius and Observatory testbeds are not interconnected– Aquarius provides no antenna, feed, or structure elements– Scatterometer breadboard is not included– Going in plan does not integrate Radiometer and ICDS elements– Radiometer is single (vs. triple) string and DPU is EM, not FM version– Radiometer FM hardware updates not applied to EM– Aquarius Power Distribution Unit is entirely replaced by power

supplies– No temperature sensors or support software included in the Automatic

Thermal Control portion of the test bed

86

Test Bed Capabilities• Capabilities

– ICDS test bed provides• Full Scatterometer processing

• Scatterometer simulator for RF elements is included

• Full flight-like command and telemetry response, although with nearly all simulated inputs and feedback

– Radiometer test bed provides• Limited RF targets may be available

• DPU software updates to match FM may be possible; to be investigated

• Investigating the integration of the ICDS and Radiometer test bed elements

– If Radiometer EM integration is successful• inputs and feedback will be very flight-like, within stated limitations

ACCS Test Plan

88

ACCS Test Plan• Purpose:

– Verify the Aquarius Ground System Level 3 Requirements

– Describe the plan for integrating and testing Aquarius Ground System segments

– Describe the plan for integrating and testing the Aquarius Ground System with the SACD Ground System

– Describe the training plan for Aquarius Ground System operators.

• Test approach– Ensure that AQ GS test objectives are met in a twofold fashion.

• Perform standard component and system level tests that verify Level 3 requirements. (Verification)

• Simulate full operations on a daily basis for at least one year prior to launch. (Validation) This extensive testing will support:

– Stressing the system

– rehearsing anomaly detection and response

– iterative optimization of science data processing algorithms.

89

Test Process• Analyze Level 3 requirements that will be verified and then map them into

test categories.• Develop the Test Cases including test procedures.• Conduct peer review of Test Cases and Test Procedures.• Prepare for tests:

– Verify that the pertinent subsystem tests have been completed successfully– Verify that the appropriate test data is prepared. Generate if necessary.

• Coordinate and execute testing for each major AQ GS component including relevant regression testing.

• Test execution takes place on the day of the test and includes:– Verification of participants, locations, test preparations, etc.– Startup procedures– Execution of the Test (step-by-step) – Close-down procedures

• Debriefing: review and document test results and anomalies

90

Full Ground System Test List• Segment Tests: • ACCS Acceptance Test • ADPP Acceptance Test• ACCS-ADPS Interface Test• ADPP-ADPS Interface Test • ADPS Level 0 to 1A Processing Test• ADPS Level 1 Algorithm Test• ADPS Level 2 Algorithm Test• ADPS Level 3 Algorithm Test• ADPS Retrieval, Scheduling and Archiving Test• SACD SOC-ADPP-ADPS File Exchange Tests • ACCS Command and telemetry verification (against test-bed)• ACCS Script verification (against test-bed) • Ocean Biology Processing Web Based Telemetry Tools Test• PO.DAAC interface test• ADPS – AVDS interface test• System Tests: • SACD MOC-ADPP-ADPS-ACCS End to End Test • Mission Scenarios/Operational Readiness Test with CONAE• Mission End to End Test

Tests involving the ACCS

91

Ground System End to End Test Setup

• SACD MOC-ADPP-ADPS-ACCS End to End Test configuration is identical to flight

• This configuration will be presented in detail later in this slide set

92

Operational Readiness Test System Configuration

• Replaces the Observatory with the Observatory Test Bed

• Observatory Test Bed is housed at the CONAE ground station

• Test Bed is controlled and monitored locally vs via the Flight Control system

• Command and Data files must be manually transferred to and from Aquarius Ground System

• This is adequate for Aquarius Ground System purposes in that we have no real-time control of Aquarius

93

Mission End to End Test Setup

94

ACCS Training Plan

• Aquarius Science, Instrument and Ground System Overview– In-house document that describes the mission elements from an

operations perspective • ACCS User's Guide

– Generally an assembly of CONAE deliverables– Supplemented by in-house training information

• Aquarius Operations Handbook – Policies, Processes and Procedures

• Mission Scenarios– Participation for operators already on board– Documented results for operators hired afterward

• Aquarius Test-Bed– Training scenarios

• Certification

95

ACCS Schedule

ACCS Risks

97

ACCS Risks

• Impacts of CONAE MOC redesign– AQ GS – SAC-D GS testing delayed until Feb ’09

– Any needed redesign and retest likewise delayed

– Mitigation: Fall back to SAC-C design

• Effectiveness of the Aquarius Test Bed for Analyzing and Resolving Anomalies– Lack of total interconnectivity of elements (including Observatory

test bed)

– Limited ability to simulate thermal environment and sensing for a very thermally sensitive instrument

– Mitigation: Risk is being accepted by the project

Acronym List

99

Acronym List, A - EACCS Aquarius Command and Control System ADC Analog to Digital ConverterADPP Aquarius Data Pre-Processor ADPS Aquarius Data Processing SystemAOCS Attitude and Orbit Control System (Observatory)APDU Aquarius Power Distribution UnitAQ AquariusAQ GS Aquarius Ground SystemAR Action RequestASI Agenzia Spaziale ItalianaATC Automatic Thermal ControlBB BreadboardBCE Board Control ElectronicsCCSDS Consultative Committee for Space Data SystemsCM Configuration ManagementCGSS CONAE Ground System ServicesCND Correlated Noise DiodeCODS CONAE Orbit Determination SystemCONAE Comision National de Actividades EspacialesCPU Central Processing UnitCUGSS CONAE User Ground System ServicesCUSS CONAE User Segment ServicesDeltaV Delta Velocity – an in-track orbit adjustment maneuverd/l downlink, downloadDPU Digital Processing Unit (Radiometer)EM Engineering ModelETC Estacion Tierra Cordoba (CONAE Ground Station in Cordoba, Argentina)

100

Acronym List, F - NFC Flight Control (CONAE)FGSS Foreign Ground System Services (CONAE)FM Flight ModelFSW Flight SoftwareFUSS Foreign User Segment Services (CONAE ground system acronym)GHz GigahertzGPS Global Positioning SystemGS GroundSystemGSE Ground System EquipmentHKT Housekeeping TelemetryHKTM Housekeeping TelemetryICDS Instrument Command and Data SystemIT Information TechnologyI&T Integration and TestKbps Kilobits per secondKm KilometerJPL Jet Propulsion Laboratory (Aquarius Project Management and instrument subsystem provider)LVPS Low Voltage Power SupplyLUT Look Up Table (Radiometer)MB MegabytesMbps Megabits per secondMOC Mission Operations Center (CONAE ground system acronym)MOM Mission Operations Manager (a CONAE position)NASA National Aeronautics and Space AgencyNGN NASA Ground Network

101

Acronym List, O - ZOMT Ortho Mode TransducerORT Operations Readiness TestORR Operations Readiness ReviewOS Operating System PC Personal ComputerPPS Pulse Per SecondPSU Practical Salinity UnitsRAM Random Access MemoryRBE Radiometer Back EndRFE Radiometer Front EndRMS Root-Mean-SquaredRF Radio FrequencyRT Real timeSACD Satelite Argentina Cientifica – DSBE Scatterometer Back EndSFE Scatterometer Front EndSFTP Secure File Transfer ProtocolSInter Spacecraft InterpreterSOC Spacecraft Operations ControlSOCB Science Operations Control BoardSOP Spacecraft Operations Planning (system)SP Service Platform (generic term for SAC-D)ST Stored (data)TC TelecommandTCP/IP Transfer Control Protocol/Internet Protocol

Backup Slides

Scatterometer Engineering Test-bed (at JPL)

APDU slice 4 EM

Scat RF BBs:SBE, SCG, SFE, LVPS, RF-deck, Diplexer, couplerICDS

simulator or ICDS-

BB2

LVPS EGSE

(DCCP)

APDUSlice 2 EM

APDU slice2 BCEAPDU

slice 1 EM

ATC controller BB

ATC Heater modules BB

ATC BCE and Labview

RAD6K BB

Standard test/measurement

equipment

ATC engineering Test-bed (at JPL)

APDUSlice 3 EM

APDU slice3 BCE

APDUSlice 5 EM

APDU slice5 BCE

APDU Engineering Test-bed (at JPL)

Flight Software Test-bed (at JPL)

Thermal Modeling Test-bed (ASL/JPL)

Aquarius thermal models for analysis and simulations

ICDS SimulatorBCE & PC

DPU (EM)

Radiometer RF EMs:RBERFECND

Sci/telem

Cmds/timing

HKT

science

Cmds/timing

Radiometer Engineering Test-bed (at GSFC)

•Engineering test-beds stay with the cognizant engineers (at GSFC and at JPL) to investigate functional/performance issues.

EM feed/OMT

Antenna Test-bed (at JPL)

Engineering Test-beds