What Parameters in Measurement & Automation Explorer (MAX) Are Ignored When Using an IVI Specific Driver (i.e., not a class driver)? Primary Software: Instrument Drivers/IVI>>IVI Specific DriverPrimary Software Version: N/A Primary Software Fixed Version: N/A Secondary Software: Instrument Drivers/IVI>>IVI Class Driver, Instrument Drivers/IVI>>IVI Compliance Package
Problem: The IVI configuration utility in MAX ignores some fields when used with a specific instrument driver. Background: Users of specific instrument drivers can use the setting in MAX if they pass a logical name to the "resource name" parameter (in either LV or CVI). This allows users to pre-configure some settings. However, the same configuration utility is used for IVI Class Drivers. There are some settings in MAX which do not apply to specific instrument driver users. These include the following: Entries in Driver Session that Are Not Checked (and no error, if any, will be returned): 1. Specific Driver Class 2. Specific Driver Path 3. Specific Driver Prefix 4. Specific Driver Option 5. Interchangeability check 6. Specific Simulation (referring to the Simulation Virtual Instrument) Example: If you are using the IVI Scope driver, the user needs to specify a logical name, which in turn points to a driver session (e.g., tktds3x0). This driver session contains all the information necessary for the class driver to access the specific driver. So, in order for the IVI Scope driver to know about the tktds3x0, the path of the driver file needs to be specified along with its prefix. If one is calling directly from a specific driver, the path to the driver source is already known. And so, the checking mechanism for the path in MAX is completely ignored. Hence, if you have the wrong path, you will NOT get an error. Solution:
Related Links: Attachments:
Report Date: 07/27/1999 Last Updated: 04/11/2008 Document ID: 1NQH2UL2 |
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
