User manual

Programmer’s Guide Page 15 of 66
2.4. Visual Basic .NET
Visual Basic .NET support is available with example programs in the <AcqirisDxRoot>\VB.NET directory.
The VB.NET sample program comes in 8-bit single segment or multi-segment versions. The .vbproj and
_x64.vbproj files give access to the complete application, respectively for the 32-bits and 64-bits version of the
operating system. The <AcqirisDxRoot>\include directory contains the .vb and _x64.vb files needed to access the
Acqiris driver. For the 32-bits version of the operating system , all applications need to reference AcqrsInterface.vb
and either AcqrsD1Interface.vb for digitizer use or AcqrsT3Interface.vb for time-to-digital converters. For the 64-
bits version of the operating system, use AcqrsInterface_x64.vb, AcqrsD1Interface_x64.vb and
AcqrsT3Interface_x64.vb.
Note: The programming advice in the rest of this manual is given for the C language interface. However, it is equally
valid for Visual Basic .NET. Refer to the Acqrs..(_x64).vb files for the correspondence between the Visual Basic
and C-language names of the Acqiris driver functions.
2.5. MATLAB
MATLAB is a very powerful environment to analyze and display data. The MEX interface can be used with
MathWorks MATLAB 7.3 or a newer version. The interface from it to the Acqiris products offers simple direct
access to the Acqiris driver. An example is in the directory <AcqirisDxRoot>\MATLAB.
To use it,
either set the MATLAB current directory (cd Command) to <AcqirisDxRoot>\MATLAB
or the file from that directory to the directory of your choice.
GetStarted
Filename: Aq_GetStarted.m
Argument: No Argument
This first example shows you how to perform a single acquisition. The desired configuration is loaded. You
then start the acquisition, and read and plot the acquired data.
2.6. Wind River VxWorks
The Agilent Acqiris driver for VxWorks is now provided as one library file (.a extension) instead of two
downloadable modules (.out extension) as was the case up to release 3.1. Currently supported VxWorks versions are
VxWorks 5.5 and VxWorks 6.4. Currently supported processor models are PowerPC 603, PowerPC 604, PowerPC
440 and Pentium.
NOTE: The processor models PowerPC 603, PowerPC 440 and RTOS VxWorks 5.5 will not be supported in future
releases.
NOTE: Wind River VxWorks 5.5.1 will not be supported in future releases.
2.6.1. Libraries
There is a different driver library for each VxWorks version, and for each processor model. The
vxworksXXX/AqDrvVxW_YYY.a file (where XXX is the VxWorks version and YYY the processor model) must
be included into the VxWorks image. For example, on a VxWorks 5.5 running on a Pentium, you must use the
vxworks5.5/AqDrvVxW_PENTIUM.a file.
2.6.2. Inclusion of the driver library
To include the driver library into a VxWorks image, set the path of the '.a' file as the value of the LIBS macro
(separated by a space if there are several libs). If you are using Tornado, don't forget to click on 'Add/Set' button
before closing the macro window.
2.6.3. Inclusion of an application
First, compile your application into an object file (.o extension). Then include your application into the VxWorks
image by setting the path of the object file as the value of the EXTRA_MODULES macro. You must add the
compilation flag –D_ACQIRIS to compile correctly.