HARDWARE- VS. SOFTWARE-DRIVEN REAL-TIME DATA ACQUISITION
dc.contributor.author | Powell, Richard | |
dc.contributor.author | Kuhn, Jeff | |
dc.date.accessioned | 2016-05-04T21:12:12Z | en |
dc.date.available | 2016-05-04T21:12:12Z | en |
dc.date.issued | 2000-10 | en |
dc.identifier.issn | 0884-5123 | en |
dc.identifier.issn | 0074-9079 | en |
dc.identifier.uri | http://hdl.handle.net/10150/608291 | en |
dc.description | International Telemetering Conference Proceedings / October 23-26, 2000 / Town & Country Hotel and Conference Center, San Diego, California | en_US |
dc.description.abstract | There are two basic approaches to developing data acquisition systems. The first is to buy or develop acquisition hardware and to then write software to input, identify, and distribute the data for processing, display, storage, and output to a network. The second is to design a system that handles some or all of these tasks in hardware instead of software. This paper describes the differences between software-driven and hardware-driven system architectures as applied to real-time data acquisition systems. In explaining the characteristics of a hardware-driven system, a high-performance real-time bus system architecture developed by L-3 will be used as an example. This architecture removes the bottlenecks and unpredictability that can plague software-driven systems when applied to complex real-time data acquisition applications. It does this by handling the input, identification, routing, and distribution of acquired data without software intervention. | |
dc.description.sponsorship | International Foundation for Telemetering | en |
dc.language.iso | en_US | en |
dc.publisher | International Foundation for Telemetering | en |
dc.relation.url | http://www.telemetry.org/ | en |
dc.rights | Copyright © International Foundation for Telemetering | en |
dc.subject | Hardware-Driven Architecture | en |
dc.subject | Deterministic | en |
dc.subject | Real-Time Performance | en |
dc.subject | Modular Architecture | en |
dc.subject | Parallel Processing | en |
dc.subject | Distributed Architecture | en |
dc.title | HARDWARE- VS. SOFTWARE-DRIVEN REAL-TIME DATA ACQUISITION | en_US |
dc.type | text | en |
dc.type | Proceedings | en |
dc.contributor.department | L-3 Communications Telemetry & Instrumentation | en |
dc.identifier.journal | International Telemetering Conference Proceedings | en |
dc.description.collectioninformation | Proceedings 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.dateFOA | 2018-09-11T09:53:15Z | |
html.description.abstract | There are two basic approaches to developing data acquisition systems. The first is to buy or develop acquisition hardware and to then write software to input, identify, and distribute the data for processing, display, storage, and output to a network. The second is to design a system that handles some or all of these tasks in hardware instead of software. This paper describes the differences between software-driven and hardware-driven system architectures as applied to real-time data acquisition systems. In explaining the characteristics of a hardware-driven system, a high-performance real-time bus system architecture developed by L-3 will be used as an example. This architecture removes the bottlenecks and unpredictability that can plague software-driven systems when applied to complex real-time data acquisition applications. It does this by handling the input, identification, routing, and distribution of acquired data without software intervention. |