smos sodap status

Commissioning KP 0ESAC December 2009 1

Michele ZundoESA/ESTEC

EOP-PEP

SMOS KP 009-Dec-2008

SMOS SODAP Status

Commissioning KP 0ESAC December 2009

Presentation Summary

• SODAP Scope• SODAP Tasks• SODAP Team• SODAP Timeline• SODAP Procedures• SODAP Execution:

– SODAP Week 0– SODAP Week 1, 2

• SODAP Outcome• SODAP Observation• Conclusion and Recommendations

2


SODAP Scope

3

• Switch On and Data Acquisition Phase• Lesson learnt. Insure before instrument

commissioning starts the following:

1. Basic Instrument Health check2. Verification Space to Ground Links XB3. End to End functional data flow verification4. Communication Scenario Verification5. Opportunistic feed to processor and DPGS

PLM-Health Check + SODAP-RF


SODAP Tasks

4

For both ESAC and SVALSAT :• Check RF-links and budget • Verify XB masks and behaviour at high low

elevation and identify operational constraints.

• Confirm correctness timing of station and PLM XB scheduling

• Exercise the different scenarios foreseen in Communication Baseline Doc

• Exercise autonomous downlink and OBSW reset

• Verify Data delivery to DPGS


SODAP Team(1)

5


SODAP Team(2)

6

+ Insa DPGS Operation Team at ESAC


SODAP Timeline (1)

7


SODAP Timeline (2)

8


SODAP Procedures (1)

9

Described in:

• Plan for RF activities during SMOS SODAP SO-PL-ESA-GS-6515

• SMOS SODAP-RF Procedure Issue 0 Draft 2

SO-GS-ESA-TP-6623



10

ESAC



11

SVALSAT


SODAP Week 0


PLM-Health Check

• Also known as Pre-SODAP

• Implemented week 0 following switch-on

• All OK. See Presentation by FOS

13


SODAP Week 1-2RF and scenarios


Preliminary outcome ESAC (0)

15


Preliminary outcome ESAC (1)

16


Preliminary outcome SVAL (2)

17


Preliminary outcome (3)

18



19



20



21

• All 27 tests executed.

• More than 50 Gbyte data acquired and analysed.

• 135 XB passes have been scheduled

• Functional chain OK (timing, dependency on elevation) i.e.

no operational constraint identified.

• Timing setting tuned at LOS

• Different setting of stuffing data with good results (TBC)

• SVAL XB tracking using SB for initial lock tested



22

• ESAC links budgets and behavior at different elevation



23

• SVALSAT RF links budgets and behavior at different

elevations



24

SVALSAT Conclusion

• The Eb/No observed is between 15 and 20 dB over all

passes taken. This shows that there is a large system

margin. At 15 dB Eb/No the IF input level is -40 dBm

and the antenna tracking receiver SNR is about 17.5 dB.

The threshold SNR for antenna autotrack is 10 dB. This

means that there is a system margin of 7.5 dB.



25

• Data continuity checked, major

problems observed since data is

lost on-board on MM partition 3


Observations working list(1)

26

• Informal working list of observations to be

changed to formal at subsystem level

OBS/AR/NC/SPR if/as needed.

• List will be cleaned up at end of SODAP

• Major issues from SODAP point of view are:

• Missing Packet detected (problem with on-

board MM writing) (see presentation from

FOS)

• Duplicated/lost XB_DOWNLINK to SVALSAT

• Occasional crashes of DAS acquisition

• Inconsistent performance of E2E WAN

transfer


Observations working list(2)

27


Preliminary Conclusions

28

• The System can deliver XB data to

support IOCP

• Both ESAC and SVAL scenario feasible


Recommendations

29

1. Initiate IOCP with NRT Communication scenario

2 orbit overlap

2. Address problem in acq. part of DAS to make it

robust or consider alternate procurement.

3. Initiate implementation of OBSW modifications

to cope with MM write error and partition

disabling issues

4. Complete performance evaluation of NRT WAN

link.

5. Decouple XB station commanding from data

dissemination

(both Short and long term)


Thanks

30

• Thanks to the all Team for hard work and long

hours

smos sodap status

Documents