User manual

Programmer’s Guide Page 15 of 64
The first part of the code above finds and initializes all individual digitizers, as shown in section 3.2.1. Of course,
you could also use one of the other 2 methods of identifying individual digitizers.
After AcqrsD1_multiInstrDefine has executed successfully, the instrumentID’s in the list idList become
unavailable for further operations. You must use the returned multiInstrID to refer to the newly defined
MultiInstrument.
You are responsible for making sure that
all participating digitizers are physically connected with AS bus bridges
the modules are of the same model type
the master module has no more memory than any other participating digitizer
an AcqGeo.map file is available if needed by the driver
If the master module has more memory than any other digitizer, the combined instrument will work as long as you
never request more memory than that available in the unit with the shortest memory.
The digitizers within the 'manually' defined MultiInstrument are numbered from 0 to (nbrInList 1), exactly as
presented in the digitizer list idList. For details on channel and trigger source numbering, please refer to section 3.16,
AS BUS OPERATION.
3.2.9. AqGeo.map file positioning
For AS bus MultiInstruments in some systems the driver will need additional information about the physical ordering
of the modules. This information is stored in a file named AqGeo.map which the driver will load when an AS bus
instrument is defined. The driver will search for the AqGeo.map file as follows:
First the file will be searched for in the working directory of the application.
Then the working directory will be searched for a file "AgMD1Fundamental.ini"
Finally the IVIROOT32\Driver\AgMD1 and IVIROOT64\Driver\AgMD1 will be searched for a file
"AgMD1Fundamental.ini"
The "AgMD1Fundamental.ini" file should contain the name of a directory which will also be searched for
the AqGeo.map file. Here is a typical example of its contents:
[Acqiris]
GeoMapPath=C:\Program Files\Acqiris\bin
3.2.10. Simulated Devices
If you want to work with simulated devices, none of the methods above are applicable. Many digitizer modules
supported by the driver can be simulated; analyzers and averagers generate data in digitizer mode. Any memory
option available for the module can be used for a call to Acqrs_setSimulationOptions as shown in this code
fragment:
ViSession instrumentID;
ViStatus status;
status = Acqrs_setSimulationOptions("M2M");
// Initialize the instrument
status = Acqrs_InitWithOptions("PCI::DC110", VI_FALSE, VI_FALSE,
"simulate=TRUE", &(instrumentID));
The first function call sets the instrument options that you want to obtain, e.g. “M2M” for the long memory option of
a DC110. In the second call, you must specify “simulate=TRUE” (without any spaces!). The device driver creates a
simulated device of your choice. The resource name string is always of the form “PCI::aannn”, where aannn is a
valid instrument module name.
The simulation options will apply to all subsequent calls to Acqrs_InitWithOptions, until they are reset with
Acqrs_setSimulationOptions ("").