![Saluki S2438 Series Скачать руководство пользователя страница 113](http://html1.mh-extra.com/html/saluki/s2438-series/s2438-series_user-manual_3636124113.webp)
Tel: 886.909 602 109 Email: [email protected]
113
Application
iStatus = viWaitOnEvent(analyzer, VI_EVENT_SERVICE_REQ, 10000, &etype, &eevent)
//Wait for service request
iStatus = viReadSTB(analyzer, &stat);
iStatus = viClose(eevent); //close the event handle
//Disable the SRQ event
iStatus = viDisableEvent(analyzer, VI_EVENT_SERVICE_REQ, VI_QUEUE);
//Continue running the main program……
}
5.4 I/O Library
5.4.1 Overview of I/O library
As a library of software programs pre-written for the instrument, the I/O library is called an instrument driver. It is
considered as the intermediate layer of the software between the computer and the instrument hardware device,
composed of function library, utility program and tool kit, and used as a software code module set that corresponds to a
planned operation, e.g. configuring, reading from, writing to or triggering the instrument. It resides in the computer as
the bridge and link between the computer and the instrument and provides an easily programmed high-level modular
library so that the user no longer needs to learn complex low-level programming protocols specific to an instrument. The
instrument driver is the key to rapid development and test of measurement applications.
From the aspect of function, a general instrument driver usually consists of a functional body, an interactive developer
interface, a program developer interface, a subprogram interface and an I/O interface as shown in Fig. 5.3.
Fig. 5.3 Structural model of instrument driver
The detailed description is given as follows:
Interactive developer
interface
Program developer
interface
Instrument drive program (functional body)
Subprogram interface
I/O interface (VISA)