Download presentation
Presentation is loading. Please wait.
1
SOC-Instrument Team interfaces
CHRIS WATSON ESAC
2
«TC-History example» Now on SOC-Public (under MOC documents, since a MOC interface) Command history display printout from time: to time: Current printout time: 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 ZCD01101 Perform Connection Test ADMF170A SOL E D E MS unknown * S SS S SX ZCD2Z00C Define HK: OBC - OMM Sta ADMS000A SOL E D E MS unknown * S SS S SX ZCD00305 Enable HK Para Rpt Gen ADMS000A SOL E D E MS unknown * S SS S SX Tabular synthesis of released commands Shows acknowledgements (e.g. service-1) in right hand columns …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 Shows parent sequence XML version contains more info including UniqueID (= ObservationID)
3
«TC packet retrieval example»
Same location Raw TC-packet content. Similar format to TM retrievals 104 byte ignorable SCOS-header (c.f. 76 byte for TM) Depending on how you want to work, you may prefer TC-history, or TC-packets, or both These examples are Platform data.
4
File transfer File transfer ICD
First external draft ICD now available on SOC public In summary from the instrument teams side this involves sFTP 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 sFTP server, just different in-tray/out-tray for each. First tests with instrument teams in coming months
5
OBT->UTC reference implementation
Watch out for MSBit (unsynchronised flag) Comments we received Python2 Packet timestamps at MOC We’d like to get response from each team Please don’t convert using the simple (and wrong) clock_epoch + OBT_ticks
6
IOR – Instrument Commanding
Version 0_7 on the SOC public, since Sunday Main changes 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 “ObservationID”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. 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 XML namespace probably not ideal
7
EFECS and TMC No update for this SOWG
Pending comments from Instrument Teams, to be incorporated where suitable No feedback from MAG on example files yet
8
Pending ICDs 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).
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.