|
How ADLINK PCI-3488 Works
The objective of a test and measurement application is to test a specific UUT (Unit Under Test) automatically. A typical automatic testing system includes testing programs and various testing equipment connected to the host computer via a GPIB interface. To manage the connections with GPIB instruments, testing programs are usually developed according to the following model:
ADEs (Application Development Environments), the environment where applications are written, are popular because users can implement any function needed using textual programming (ex. VC++/VB,TestExec) or graphical programming (ex. LabVIEW*) techniques. A vital part of a test and measurement application is to control and communicate with GPIB instruments. Two techniques are generally used to control the GPIB interface: invoke the native driver API or use the existing instrument drivers via VISA.
A native driver API is provided by most GPIB interface vendors and is usually in the form of ANSI C functions. For users who need more detailed control over GPIB instruments, using a driver API with SCPI string commands is a good choice. For others who want to keep away from complicated instrument commands, instrument drivers developed for specific ADEs (ex. LabVIEW*/TestExec) can significantly simplify the complexity of instrument control. Most of the instrument drivers use a VISA library to control the GPIB interface and communicate with instruments. VISA support is essential in this case.
ADLINK's PCI-3488 works with your applications in both ways. Its GPIB-32.DLL provides binary compatibility with the world's most popular NI-488.2* driver software The PCI-3488 also provides VISA library support that can be used with most common instrument drivers written by instrument vendors. Regardless if you are using VC++, VB, Delphi,LabVIEW*, or any other T&M ADE, PCI-3488 is the most cost-effective GPIB solution compatible with all your applications.
| 
