Spacecraft Onboard Interface Services Application Support Services Working
Spacecraft Onboard Interface Services Application Support Services Working Group (SOIS-APP WG) Electronic Data Sheets and Common Dictionary of Terms Introduction CCSDS Spring 2013 Meeting
Usage of EDS 15/04/2013 SOIS APP WG Spring 2013 2
SOIS and EDS 15/04/2013 SOIS APP WG Spring 2013 3
EDS XML Schema • CCSDS 876. 0 XML Specification for Electronic Data Sheets for Onboard Devices » An Electronic Data Sheet (EDS) for an onboard device electronically describes • (Set of) Device’s functional interfaces and access methods › Device-specific Access Protocol (DAP): how to access the device • Examples include: using subnetwork services • SOIS Physical functional interface and Device-specific Access Protocol (DAP) mapping functionalhow interface onto SOIS › Functional Interface: to access the. Subnetwork functions. Services provided by the • Virtual functional interface and Device Abstraction Control Procedure device, virtualised from the access method (e. g. using engineering (DACP) mapping the Functional Interface onto a Device-specific Access units rather than raw values) Protocol (DAP) • Virtual functional. Control interface. Procedure and Software(DACP): Bus messages & implied › Device Abstraction mapping the message exchange pattern & protocol Functional Interface onto the DAP › Ancillary Information: text, figures etc. » The book describes the structure and required elements within an EDS, independent of any particular technology 15/04/2013 SOIS APP WG Spring 2013 4
Common Do. T • CCSDS 876. 1 Common Dictionary of Terms for Onboard Devices » Defines common syntactic and semantic types used in EDS for onboard devices, independent of representation in any particular technology » Resulting information will eventually be submitted to SANA 15/04/2013 SOIS APP WG Spring 2013 5
Generic Functional Interface • Not standardised (yet) » Standardised functional interface for a class of devices, e. g. common functions of star trackers » Represented either textually and/or fragment of XML EDS schema 15/04/2013 SOIS APP WG Spring 2013 6
EDS and Common Do. T Relationships and Structure Common Do. T Generic Functional Interface Device EDS Some Functional Interfaces are Generic Functional Interfaces, i. e. completely standard Functional Interface Some Functional Interfaces extend Generic Functional Interfaces with manufacturerspecific extensions DACP Other Functional Interfaces are completely manufacturerspecific DAP Subnetwork Service Subnetwork` Service 15/04/2013 SOIS APP WG Spring 2013 All Functional Interfaces, DACPs and DAPs make use of terms from the Common Do. T They may also make use of manufacturer-specific terms, but these are composed of more simple terms from the Common Do. T DAP is defined in terms of using subnetwork-specific Subnetwork Services, e. g. Memory Access Service using ECSS 1553 Get/Set Services 7
XML Representation The Generic Functional Interfaces’ XML files are expected to eventually be managed by SANA Common Do. T The Common Do. T XML file is managed by SANA imports Generic Functional Interface imports Each device has it’s own EDS uses The EDS XML Schema file is managed by SANA 15/04/2013 imports EDS XML Schema SOIS APP WG Spring 2013 uses Device Data Sheet An EDS may be incomplete, e. g. a device EDS supplied by a manufacturer need not have any Functional Interfaces. Conversely an EDS used for device simulation in software testing may only have a Functional Interface 8
CCSDS SOIS Electronic Data Sheets Work Plan • Electronic Data Sheets for Onboard Devices » Specification – Blue/Magenta Book » XML Schema » Led by ESA from TRP Activity, alternative from ESA YGP project • Common Dictionary of Terms » Specification – Blue/Magenta Book » Online dictionary managed by CCSDS SANA Presenter 1 & Presenter 2 » Led by NASA from SPA Ontology 08 January 2022 • Schedule: » » » » 15/04/2013 1 st complete draft of Books and XML Schemas for Spring 2013 meeting Prototyping example device EDS with device-specific functional interfaces Refine Books and XML Schemas for Fall 2013 meeting Possible prototype device EDS with generic functional interfaces Revise Green Book (Issue 3) to capture consolidation of resulting EDS 1 st Agency Review of Books and XML Schemas for Spring 2014 meeting CESG Poll for publication of Books and XML Schemas for Fall 2014 meeting Publish Books and XML Schema End of 2014 SOIS APP WG Spring 2013 9
• • Early experience of consideration of contents of device data sheets from ESA TRP project 3 selected devices » » » • FOG Astrix 120 Gyro (MIL-STD-1553 B simple sensor) Sodern Hydra Star Tracker (MIL-STD-1553 B complex sensor) NPAL Camera (Space. Wire complex sensor) [No actuator ] Together them have 50 TCs and 32 sets of TM data (~30, 000 parameters) Separately VSRF AOCS Instruments have a number of (roughly) generic functional interfaces » Gyro and Star Tracker have some mapping onto this, so provides basis for virtual functional interface (DVS) » 3 & 15 attributes and 1 & 3 commands respectively (~25 parameters) » This information is not provided by device manufacturer but by system or OBSW engineer • Remainder of TM data sets and TCs are not of interest to specific onboard applications, e. g. AOCS » => No need to represent in virtual functional interface (DVS) • Still required for downlinking and may be required for generic onboard applications, e. g. onboard monitoring or automation » => Still represented in raw functional interface (DAS) • => Reinforces position that only raw functional interface is provided in EDS by a device manufacturer 15/04/2013 SOIS APP WG Spring 2013 10
- Slides: 10