Attribute based instrument drivers

Proceedings of the 6th IEEE International Conference on Intelligent Data Acquisition and Advanced Computing Systems Pub Date : 2011-11-10 DOI:10.1109/IDAACS.2011.6072719

J. Kominek, Juergen Straub, J. Zidek

{"title":"Attribute based instrument drivers","authors":"J. Kominek, Juergen Straub, J. Zidek","doi":"10.1109/IDAACS.2011.6072719","DOIUrl":null,"url":null,"abstract":"The task of programming instruments in a test system has always been a concern for end users and a major cost for the overall system development. Many users know that programming can often be the most time-consuming part of developing a system. The developer spends much valuable time learning the specific programming requirements of each instrument in the system. Almost all instruments are designed for interactive use through a physical front panel and also offer remote control capability via a communication port on the back of the instrument. An instrument driver, in the simplest definition, is a set of software routines that handles the programmatic details of controlling and communicating with a specific instrument. The most successful instrument driver concepts have always distributed instrument drivers in source code and provided end users with access to the same tools developers use to write drivers. With this philosophy, new instrument drivers were often easily developed by end users through modifying an existing driver for another instrument.","PeriodicalId":106306,"journal":{"name":"Proceedings of the 6th IEEE International Conference on Intelligent Data Acquisition and Advanced Computing Systems","volume":"121 1","pages":"0"},"PeriodicalIF":0.0000,"publicationDate":"2011-11-10","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":"1","resultStr":null,"platform":"Semanticscholar","paperid":null,"PeriodicalName":"Proceedings of the 6th IEEE International Conference on Intelligent Data Acquisition and Advanced Computing Systems","FirstCategoryId":"1085","ListUrlMain":"https://doi.org/10.1109/IDAACS.2011.6072719","RegionNum":0,"RegionCategory":null,"ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":null,"EPubDate":"","PubModel":"","JCR":"","JCRName":"","Score":null,"Total":0}

引用次数: 1

Abstract

The task of programming instruments in a test system has always been a concern for end users and a major cost for the overall system development. Many users know that programming can often be the most time-consuming part of developing a system. The developer spends much valuable time learning the specific programming requirements of each instrument in the system. Almost all instruments are designed for interactive use through a physical front panel and also offer remote control capability via a communication port on the back of the instrument. An instrument driver, in the simplest definition, is a set of software routines that handles the programmatic details of controlling and communicating with a specific instrument. The most successful instrument driver concepts have always distributed instrument drivers in source code and provided end users with access to the same tools developers use to write drivers. With this philosophy, new instrument drivers were often easily developed by end users through modifying an existing driver for another instrument.

查看原文

微信好友朋友圈 QQ好友复制链接

本刊更多论文

基于属性的仪器驱动

测试系统中编程工具的任务一直是最终用户关心的问题，也是整个系统开发的主要成本。许多用户都知道编程通常是开发系统中最耗时的部分。开发人员花费了大量宝贵的时间来学习系统中每个仪器的特定编程需求。几乎所有仪器都设计为通过物理前面板进行交互使用，并通过仪器背面的通信端口提供远程控制功能。仪器驱动程序，在最简单的定义中，是一组软件例程，用于处理控制和与特定仪器通信的编程细节。最成功的仪器驱动概念总是在源代码中分发仪器驱动程序，并为最终用户提供访问开发人员用于编写驱动程序的相同工具的权限。有了这个理念，新的仪器驱动程序往往很容易通过修改现有的驱动程序为另一个仪器的最终用户开发。

本文章由计算机程序翻译，如有差异，请以英文原文为准。

求助全文

约1分钟内获得全文去求助

来源期刊

Proceedings of the 6th IEEE International Conference on Intelligent Data Acquisition and Advanced Computing Systems

自引率

0.00%

发文量