1 / 30

SMOS SODAP Status

SMOS SODAP Status. Michele Zundo ESA/ESTEC EOP-PEP SMOS KP 0 09-Dec-2008. 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.

oksana
Download Presentation

SMOS SODAP Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. SMOS SODAP Status Michele Zundo ESA/ESTEC EOP-PEP SMOS KP 0 09-Dec-2008

  2. 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

  3. SODAP Scope • Switch On and Data Acquisition Phase • Lesson learnt. Insure before instrument commissioning starts the following: • Basic Instrument Health check • Verification Space to Ground Links XB • End to End functional data flow verification • Communication Scenario Verification • Opportunistic feed to processor and DPGS PLM-Health Check + SODAP-RF

  4. SODAP Tasks 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

  5. SODAP Team(1)

  6. SODAP Team(2) + Insa DPGS Operation Team at ESAC

  7. SODAP Timeline (1)

  8. SODAP Timeline (2)

  9. SODAP Procedures (1) 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. SODAP Procedures (2) ESAC

  11. SODAP Procedures (3) SVALSAT

  12. SODAP Week 0

  13. PLM-Health Check • Also known as Pre-SODAP • Implemented week 0 following switch-on • All OK. See Presentation by FOS

  14. SODAP Week 1-2RF and scenarios

  15. Preliminary outcome ESAC (0)

  16. Preliminary outcome ESAC (1)

  17. Preliminary outcome SVAL (2)

  18. Preliminary outcome (3)

  19. Preliminary outcome (4)

  20. Preliminary outcome (5)

  21. Preliminary outcome (6) • 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. Preliminary outcome (7) • ESAC links budgets and behavior at different elevation

  23. Preliminary outcome (8) • SVALSAT RF links budgets and behavior at different elevations

  24. Preliminary outcome (9) • 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. Preliminary outcome (10) • Data continuity checked, major problems observed since data is lost on-board on MM partition 3

  26. Observations working list(1) • 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

  27. Observations working list(2)

  28. Preliminary Conclusions • The System can deliver XB data to support IOCP • Both ESAC and SVAL scenario feasible

  29. Recommendations (both Short and long term) • Initiate IOCP with NRT Communication scenario 2 orbit overlap • Address problem in acq. part of DAS to make it robust or consider alternate procurement. • Initiate implementation of OBSW modifications to cope with MM write error and partition disabling issues • Complete performance evaluation of NRT WAN link. • Decouple XB station commanding from data dissemination

  30. Thanks • Thanks to the all Team for hard work and long hours

More Related