# Presentation: 710091

## EDOS STATUS AND FUTURE CHANGES

**EDOS ****STATUS AND FUTURE CHANGES**

**AURA SCIENCE MEETING**
- Presented by
- Terri Wood
- EDOS Project Mgr, Code 586

## EDOS Status

**EDOS Release C5.0 (Operational – June 2006)**
-  Since June 2006, EDOS captures the spacecraft science downlinks at the ground stations in a data-driven mode of operation.
-  EDOS front-end devices servicing the antennas (12) are configured to receive data automatically in a 24x7 mode of operation.
-  No schedules are involved and all operation is automated end-to-end.

**Notes:**
Summary or review the state of C5.0

## EDOS Ground System Functions – C5.0 Operational

**EDOS Ground System Functions – C5.0 Operational**

## AURA Monthly Average Percent Recovery

**Note 1: Day 338/1615 z – AURA Command and Data Handling (CDH) subsystem data Formatter Multiplexer Unit/ Solid State Recorder (FMU/SSR) experienced an anomaly**
**Note 2: The monthly average percent recovery is based on the average of the daily percent recovery. The daily percent recovery is based on the estimated number of packets for multiple instrument APIDs and the corresponding actual number of packets collected from the downlinks.**
**Note 3. After March 2008, the HIRDLS data has not been usable but EDOS is still producing the products **

**(1)**

**Notes:**
Know what the reasons are for data transfer failures for AURA
Is the HIRDLS data included in the graphics listed above anyway?

## EDOS Upcoming Change

- EDOS is planning to deploy a major system upgrade referred to as **Release C5.1** replacing all servers and implementing a central Monitor and Control system
- The system is currently running in parallel operations along with C5.0.
- The transition of the release to operations is expected to occur around **December 2008** timeframe.
- EDOS products generated will NOT change however we request your support for independent verification and validation of the products by your systems.

## Release C5.1 

- New front end processing design:
- Increases EDOS spacecraft capture rate to 500 Mbps
- Allows flexible reconfiguration/upgrades via FPGA image file
- Prioritized traffic on the high rate lines between the GSIFs and the LZPF
- Central Control and Monitoring via GUI screens standardized and accessed via a web browser
- External Web server provides telemetry downlink status to ground station and Flight Ops Teams
- Efficient data transfer by moving to Linux based hardware platform

**Key features...**

**Notes:**
Make sure we prioritize the features by discussing what is relevant to the instrument teams first...

Also discuss who these features will benefit like the external web server will enable the FOT to view the quality of the downlink data earlier and resolve any anomalies in the data sooner which will ultimately help the instrument teams.

Discuss how all these updates will put EDOS in a better posture or make EDOS scalable enough to add on new missions (FPGA, and data capture rate)

In terms of prioritization, Aqua comes first then Aura data

C5.1 system will hopefully mask the problems associated with the different hardware platforms (IRIX to LINUX) with the data transfer failures.
Won’t get as many ftp errors as we got from the SGI/IRIX box

## EDOS DATA-DRIVEN - PHASE 2  (C5.1 Operational -December 2008)

## Steps toward Transition to C5.1

| Step | Action | Status |
| --- | --- | --- |
| 1. | EDOS provides new IP addresses to all
users to allow connectivity from new
EDOS systems  | Completed – Connectivity
verified for all users |
| 2. | EDOS sends products from new EDOS
system (C5.1) for several hours | Some week day during the
1stor 2nd week of November |
| 3. | EDOS resumes delivering products from
current operational system (C5.0) | For two weeks after step 2
date |
| 4. | EDOS receives/evaluates feedback from
customers | Same two week period after step 2 date |
| 5. | EDOS transitions to C5.1 system based on
successfully feedback from customers | Planned -  C5.1 transition to
occur during December
  Specific date and time
to be provided by email |

**Notes:**
Give the rough schedule for EDOS...
Slice notice (within a week of slice)
Slice on Tuesday October 28th’
ORR dry run Wednesday Nov 5th
ORR Wednesday November 12th
Transition Tuesday November 18th.

## Next Steps...

- After C5.1 release to Operations, next priority will be to address the changes for the AUTO-OPS mode of operation for AQUA and AURA.
- Currently EDOS does not recover the packet split between CADUs residing in successive contacts sessions and in the AUTO-OPS mode of operations those packets are lost.
- EDOS will incorporate an overlap capability to reassembling the packet spanning multiple CADUs.
- The delays experienced with the deployment of the C5.1 release have impacted the completion of this activity.

**Notes:**
Discuss all the reasons for implementing AutoOps...
Reduce operations costs
No overlap in the data but EDOS will provide overlap solution
Reduce the amount of problems that occur at the ground stations
Give the reasons for why C5.1 was late...too complex
Plan to undergo the discussions after we transition and implement fix by summer of 2009

## The Team...