Ceyear 4051 Series, User Manual

Page: 645 / 751

6 Remote control
6.4 I/O Library
631
6.4 I/O Library

Overview of I/O Library
„„„„„„„„„„„„„„„„„„„„„„„„„„„„„„
631

I/O Library Installation and Configuration
„„„„„„„„„„„„„„„„„„„„„„„
632
6.4.1 Overview of I/O Library
The I/O library is a library of pre-written software programs for the instrument, known as the instrument drive
program, i.e. instrument driver. It is an intermediate software layer between the computer and instrument
hardware equipment. It is composed of the function library, utility program, tool kit, etc., and is a set of
software code modules. This set corresponds to a series of planned operations, such as instrument
configuration, reading, writing, triggering, etc. It is installed the computer and used as a connecting bridge and
link between the computer and instrument. With the easy-to-program high-level modular library, the user does
not need to the complex special low-level programming protocol for the specific instrument. It is key to use
the instrument driver to rapidly develop the test measurement application.
From the functional perspective, one general instrument driver is composed of five parts: functional body,
interactive developer interface, program developer interface, subprogram interface and I/O interface, as shown
in Fig. 6.4.
Fig. 6.4 Instrument Driver Structure Model
Details are as follows:
1) Functional body. This is the main functional part of the instrument driver and can be understood as the
framework program of the instrument driver.
2) Interactive developer interface To facilitate use, the graphical interactive developer interface is generally
set in the application environment supporting instrument driver development. For example, the function
panel of Labwindows/CVI is a kind of interactive development interface. Each parameter of the
instrument driver function in the function panel is expressed in the graphical control form.
3) Programming developer interface This is a software interface for the application program to call the
instrument driver function, such as the dynamic link library file of instrument driver.dll in the Windows
system.
4) I/O interface It is used for actual communication between the instrument driver and instrument. It is
allowed to use the special bus I/O software, such as GPIB, or the general standard I/O software (VISAI/O)
to be used over multiple buses.
5) Subprogram interface It is a software interface for the instrument driver to visit other supporting libraries,
such as the data library, FFT function, etc. It will be used when other software modules, operating systems,