Preliminary Targets and Tools for Telemetry and Command Data Handling
A discussion on utilizing existing tools for manipulating telemetry data, addressing key issues like validation, and the importance of Symbolic replacement in telemetry files. Recommendations for validating files before shipping using tools like xmllint and XMLSpy are highlighted.
Download Presentation
Please find below an Image/Link to download the presentation.
The content on the website is provided AS IS for your information and personal use only. It may not be sold, licensed, or shared on other websites without obtaining consent from the author. Download presentation by click this link. If you encounter any issues during the download, it is possible that the publisher has removed the file from their server.
E N D
Presentation Transcript
SEDS to XTCE And to T&C Targets Preliminary Kevin R. NASA GSFC/ASRC Inc (for J. Wilmont NASA GSFC/SOIS Working Group Lead)
The Basic Framework Possibly manipulate; - Flatten arrays - Flatten dotted name mnemonics - Subset - Remove unsupported elements in target - Rename items Note: has GSFC XTCE exporter, used for LRO but not mature ITOS T&C Read contents of files using JAXB, find CCSDS related Cmd/Tlm packet descriptions, convert to XTCE Existing GSFC Telemetry only Importer Tool with mission use lineage (DAT, SDO, MMS) SOIS EDS XML File XML File XML File XML File(s) SOIS EDS SOIS EDS SOIS EDS XTCE Ball Cosmo T&C XML File(s?) Note: has XTCE exporter, not tested Existing GSFC tools & Ball Cosmos Importer. Currently being used by JPL+GSFC w/LRO telemetry database untried Basic tlm/cmd database, still may need: - Ground calibrators - Limits - Units - Better descriptions - Command arg extraction or refinement - Mission related specialization Note: a basic import of XTCE telemetry would be possible without a large level of effort ASIST T&C Existing GSFC Telemetry Importer Only. Used for DAT, SDO, MMS. (also ingested but did not use: GPM, EO1) SOIS EDS XSD XTCE Send tlm packet for display (or commands) XSD (V1.1)
What We Did So Far Possibly manipulate (existing GSFC): - Flatten arrays - Flatten dotted name mnemonics - Subset - Remove unsupported elements in target - Rename items Note: has GSFC XTCE exporter, used for LRO but not mature ITOS T&C Read contents of files using JAXB, find CCSDS related Cmd/Tlm packet descriptions, convert to XTCE Existing GSFC Telemetry only Importer Tool with mission use lineage (DAT, SDO, MMS) SOIS EDS XML File XML File XML File XML File(s) SOIS EDS SOIS EDS SOIS EDS XTCE Ball Cosmo T&C XML File(s?) Note: has XTCE exporter, not tested Existing GSFC tools & Ball Cosmos Importer. Currently being used by JPL+GSFC w/LRO telemetry database untried Basic tlm/cmd database, still may need: - Ground calibrators - Limits - Units - Better descriptions - Command arg extraction or refinement - Mission related specialization - For mission ops may need mission Note: a basic import of XTCE telemetry would be possible without a large level of effort ASIST T&C Existing GSFC Telemetry Importer Only. Used for DAT, SDO, MMS. (also ingested but did not use: GPM, EO1) SOIS EDS XSD XTCE Send tlm packet for display (or commands) XSD (V1.1)
Key Issues CFs EDS Files Did Not Validate SEDS XSD may have drifted since creation of files Some had simple syntax errors Others the element had changed name In others the element had moved (or seemed to have moved) Recommendation: files should be validated against schema before shipping. Linux users can use xmllint and windows users can use XMLSpy, and there s also OxygenXML which is good and may run on other platforms. Eclipse IDE has some XML support. CFs EDS File have SYMBOLICS Even if the above were addressed (less the last bullet), the SYMBOLIC replacement needs addressing I took the path of adding unions to key attributes that allow for ${PATH/NAME} as well as the original data type Conclusion: it s nice to get files that validate. SYMBOLICS still need replacement in that scenario. The other way is to pre-process the files. I don t have a pre-processor though. CFs Content Issues: The overarching issue is one of correctness need better explanation of how SEDS.xsd really works Beyond that Key Problem: How do we recognize in a standard way all CCSDS related packet descriptions in an XTCE file A subproblem is how do we recognized the ones that are telemetered and commanded as these should go into the T&C database Recommendation: Standardize on CCSDS packet definition hierarchy in ContainerDataType Including packet header, packet APID, packet header fields How to deal with a secondary header which is likely a time stamp for GSFC Standard interfaces descriptions? Look at XTCE GovSat which answered this for XTCE-land as a starting point
