SOCInstrument Team interfaces CHRIS WATSON ESAC ESOC Chris

  • Slides: 8
Download presentation
SOC-Instrument Team interfaces CHRIS WATSON ESAC ESOC | Chris Watson | ESA/ESOC | Page

SOC-Instrument Team interfaces CHRIS WATSON ESAC ESOC | Chris Watson | ESA/ESOC | Page 1

 «TC-History example» n Now on SOC-Public (under MOC documents, since a MOC interface)

«TC-History example» n Now on SOC-Public (under MOC documents, since a MOC interface) https: //issues. cosmos. esa. int/solarorbiterwiki/display/SOSP/TCrelated+example+files Command history display printout from time: 2016. 326. 00. 000000 to time: 2016. 330. 00. 000000 Current printout time: 2016. 355. 18. 51. 392000 Display view mode: BRIEF Sort order: RELEASE Filter status: INACTIVE Name Description Sequence Domain Release Time Execution Time S D C G B IL ST Source FC TC Q R GTO A SS 1122 CC --------------------------------------------------------------------------------ZCD 01101 Perform Connection Test ADMF 170 A SOL 2016. 328. 08. 27. 52. 027051 2016. 328. 08. 27. 58. 500798 E D E MS unknown -- -- * S SS S SX ZCD 2 Z 00 C Define HK: OBC - OMM Sta ADMS 000 A SOL 2016. 328. 08. 30. 40. 708728 2016. 328. 08. 30. 49. 156597 E D E MS unknown -- -- * S SS S SX ZCD 00305 Enable HK Para Rpt Gen 2016. 328. 08. 30. 41. 743777 2016. 328. 08. 30. 55. 396602 E D E MS unknown -- -- * S SS S SX ADMS 000 A SOL n Tabular synthesis of released commands n Shows acknowledgements (e. g. service-1) in right hand columns • n …exact mapping of columns to be confirmed. May not be final configuration (For MTL commanding especially) these statuses change depending on when you retrieve the history • Uplink in pass - execution(often outside of visibility) – service-1 on ground at next pass n Shows parent sequence n XML version contains more info including Unique. ID (= Observation. ID) ESOC | Chris Watson | ESA/ESOC | Page 2

 «TC packet retrieval example» n Same location https: //issues. cosmos. esa. int/solarorbiterwiki/display/SOSP/TCrelated+example+files n

«TC packet retrieval example» n Same location https: //issues. cosmos. esa. int/solarorbiterwiki/display/SOSP/TCrelated+example+files n Raw TC-packet content. Similar format to TM retrievals n 104 byte ignorable SCOS-header (c. f. 76 byte for TM) n Depending on how you want to work, you may prefer TC-history, or TC-packets, or both n These examples are Platform data. ESOC | Chris Watson | ESA/ESOC | Page 3

File transfer n File transfer ICD • First external draft ICD now available on

File transfer n File transfer ICD • First external draft ICD now available on SOC public • In summary from the instrument teams side this involves • s. FTP server • with fixed IP for whitelist, and SOC user account • Specific directory convention for in-tray, out-tray (and “transferred”) • …read the ICD for full details • MOC will use virtually the same system (e. g. for PDOR/MDOR reception) • Different directory naming (and user) • • => ITs ought to be able to send/receive to MOC and SOC, using the same s. FTP server, just different in-tray/out-tray for each. First tests with instrument teams in coming months ESOC | Chris Watson | ESA/ESOC | Page 4

OBT->UTC reference implementation https: //issues. cosmos. esa. int/solarorbiterwiki/display/SOSP/Translate+from+OBT+to +UTC+and+back n Watch out for MSBit

OBT->UTC reference implementation https: //issues. cosmos. esa. int/solarorbiterwiki/display/SOSP/Translate+from+OBT+to +UTC+and+back n Watch out for MSBit (unsynchronised flag) n Comments we received • Python 2 • Packet timestamps at MOC n We’d like to get response from each team n Please don’t convert using the simple (and wrong) clock_epoch + OBT_ticks ESOC | Chris Watson | ESA/ESOC | Page 5

IOR – Instrument Commanding n Version 0_7 on the SOC public, since Sunday n

IOR – Instrument Commanding n Version 0_7 on the SOC public, since Sunday n Main changes n • Clarifications/Corrections on details of xml structure, learnt from working with real examples • Major change to filenaming (resolves long-standing IOR# ambiguity) • Change to SOLO-HI resource info approach • Clarifications on what leap-seconds will look like for planning • Proposal for “Observation. ID”s linked to SOOP instances • Example IOR built by SOC (using fictitious sequence calls) now available The IOR format is deliberately very similar to the PDOR format used at MOC for commissioning/contingencies. • n Hope is that this makes it easy to adapt to using PDORs Open issues / future updates • Filename “metadata” not yet duplicated inside the file • Backup plans at LTP not yet covered • • i-VSTP slot-reservation may need to be tweaked ESOC | Chris Watson | ESA/ESOC | Page 6 XML namespace probably not ideal

EFECS and TMC n No update for this SOWG • Pending comments from Instrument

EFECS and TMC n No update for this SOWG • Pending comments from Instrument Teams, to be incorporated where suitable • No feedback from MAG on example files yet ESOC | Chris Watson | ESA/ESOC | Page 7

Pending ICDs n Summary of interfaces to be defined • Boresight definition • Selective

Pending ICDs n Summary of interfaces to be defined • Boresight definition • Selective requests • Power allocation (TBC) • Pointing triplet (discussed in MADAWG. e. g. identifying desired feature location with a science model). ESOC | Chris Watson | ESA/ESOC | Page 8