Show simple item record

dc.contributor.authorYin, Xianghong
dc.contributor.authorSulewski, Joe
dc.date.accessioned2016-02-04T22:33:35Zen
dc.date.available2016-02-04T22:33:35Zen
dc.date.issued2011-10en
dc.identifier.issn0884-5123en
dc.identifier.issn0074-9079en
dc.identifier.urihttp://hdl.handle.net/10150/595680en
dc.descriptionITC/USA 2011 Conference Proceedings / The Forty-Seventh Annual International Telemetering Conference and Technical Exhibition / October 24-27, 2011 / Bally's Las Vegas, Las Vegas, Nevadaen_US
dc.description.abstractToday's telemetry systems need to be highly configurable and easily extensible to support a constantly growing number of data acquisition/transmitting components from different manufacturers. One way to achieve this goal is through a standardized descriptive language that can define the system structure as well as end-node devices. The integrated Network Enhanced Telemetry (iNET) program has explored such a possibility by creating a series of standards to define how devices are configured and interoperate with each other. As one of the standards created by the iNET program, the Metadata Description Language (MDL) specifies a common interchange language that defines and configures a Telemetry Network System (TmNS). MDL Instance Documents are used to exchange test requirements, data formats and configuration information among the devices within a TmNS system. MDL, together with other standards created in the iNET program, serve as a foundation for assembling a modern telemetry system. This paper starts with an overview of the MDL-based system description architecture. A typical configuration workflow of an MDL-based system is then described. iNET functionality implementations for new and legacy devices are used as examples to illustrate the power of MDL-based design, as well as the challenges and issues associated with the implementation of the MDL standard. We explain and evaluate the design decisions for a new product, the L-3 NetDAS Recorder, as the case study. We also discuss how a legacy Data Acquisition Unit (DAU) acting as an LTC Data Source Unit can be updated to support MDL based iNET functionality. Our practice shows that more efficient data acquisition systems can be designed and implemented using the metadata definition language as a core tool for equipment and system description. We conclude the paper with design tradeoffs and discussions.
dc.description.sponsorshipInternational Foundation for Telemeteringen
dc.language.isoen_USen
dc.publisherInternational Foundation for Telemeteringen
dc.relation.urlhttp://www.telemetry.org/en
dc.rightsCopyright © held by the author; distribution rights International Foundation for Telemeteringen
dc.subjectMDLen
dc.subjectiNETen
dc.subjectTmNSen
dc.subjectEnd-nodeen
dc.subjectRecorderen
dc.subjectDAUen
dc.titleImplementation of an iNET-Enabled End-Node Utilizing an MDL-Based Telemetry System Architectureen_US
dc.typetexten
dc.typeProceedingsen
dc.contributor.departmentL-3 Telemetry Easten
dc.identifier.journalInternational Telemetering Conference Proceedingsen
dc.description.collectioninformationProceedings from the International Telemetering Conference are made available by the International Foundation for Telemetering and the University of Arizona Libraries. Visit http://www.telemetry.org/index.php/contact-us if you have questions about items in this collection.en
refterms.dateFOA2018-07-18T01:21:50Z
html.description.abstractToday's telemetry systems need to be highly configurable and easily extensible to support a constantly growing number of data acquisition/transmitting components from different manufacturers. One way to achieve this goal is through a standardized descriptive language that can define the system structure as well as end-node devices. The integrated Network Enhanced Telemetry (iNET) program has explored such a possibility by creating a series of standards to define how devices are configured and interoperate with each other. As one of the standards created by the iNET program, the Metadata Description Language (MDL) specifies a common interchange language that defines and configures a Telemetry Network System (TmNS). MDL Instance Documents are used to exchange test requirements, data formats and configuration information among the devices within a TmNS system. MDL, together with other standards created in the iNET program, serve as a foundation for assembling a modern telemetry system. This paper starts with an overview of the MDL-based system description architecture. A typical configuration workflow of an MDL-based system is then described. iNET functionality implementations for new and legacy devices are used as examples to illustrate the power of MDL-based design, as well as the challenges and issues associated with the implementation of the MDL standard. We explain and evaluate the design decisions for a new product, the L-3 NetDAS Recorder, as the case study. We also discuss how a legacy Data Acquisition Unit (DAU) acting as an LTC Data Source Unit can be updated to support MDL based iNET functionality. Our practice shows that more efficient data acquisition systems can be designed and implemented using the metadata definition language as a core tool for equipment and system description. We conclude the paper with design tradeoffs and discussions.


Files in this item

Thumbnail
Name:
ITC_2011_11-10-06.pdf
Size:
268.7Kb
Format:
PDF

This item appears in the following Collection(s)

Show simple item record