When you specify an attribute value, IVI drivers also identify dependencies for the attribute ranges on other instrument settings. Simply replace the resource name string with fl This simple data generation process will return data values to the program variables so subsequent function calls do not fail for lack of data. Range checking is enabled by default, but you can disable it after you debug your application in order to increase execution speed. Unlike traditional drivers, IVI drivers have a simulation mode in which you can make calls to the driver without being connected to an instrument. Under the General tab, you can enable or disable initialization options.
|Date Added:||2 April 2011|
|File Size:||29.74 Mb|
|Operating Systems:||Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X|
|Price:||Free* [*Free Regsitration Required]|
For example, generate a value of 3.
The IVI Driver Library also includes a soft front panel for each class driver for interactively controlling any instrument that fits in the class.
Refer to the instrument driver help to determine the array data type. Select fl45 from Driver Session as shown in the following figure. The specific instrument labvies contain the information for controlling a particular model of an instrument, including the command strings, parsing code, and valid ranges of each setting for that particular instrument.
The second mechanism for simulating data in the IVI architecture is labvkew a simulation driver.
If you do not have the actual instrument connected to your system, make sure that you select Specific Driver in the Simulate With drop-down. The class driver knows which specific instrument driver to call and what attributes to call when you configure a logical name in MAX and pass it to the class driver’s Initialize VI.
Unlike traditional drivers, IVI drivers have a simulation mode in which you can make calls to the driver without being connected to an instrument. The IVI Engine uses this dynamically-calculated range to verify the setting.
The IVI technology establishes a standard instrument-driver architecture with built-in mechanisms for enabling simulation and simulated data. In addition to generating data, you can use simulation drivers to inject simulated errors into your program. Focusing on the ease of use, traditional instrument drivers did not always provide optimal performance.
Range checking is enabled by default, but you can disable it after you debug your application in order to increase execution speed. Selecting help for Initialize method. Instrument drivers simplify instrument control and reduce test program development time by eliminating the need to learn the programming protocol for each instrument. When the VI performs a frequency sweep, only the frequency parameter changes. There are three different levels of simulation: Dotted properties are a shorthand alternative to cascading multiple Property Nodes that return interface references needed for wiring properties and methods specific to a given interface.
If the new instrument cannot handle any of the settings required by the program, the specific driver in simulation mode will catch this incompatibility with an out-of-range error.
The specific drivers contain information for controlling a specific instrument, such as command strings, parsing code, and valid ranges for instrument settings. If an instrument error occurs at that time, the IVI Engine returns an error through the error out control.
To enable one of the IVI features, you set its value to 1 in the option string. Using a Simulation Driver labivew an Instrument-Specific Driver — The instrument-specific driver performs a very important role ensuring that the values to be sent to the instrument are within range for that particular instrument even when the instrument is not connected to the computer. Because you have access to this source code, you are free to modify the driver C code to add your own data generation algorithms to generate simulated data that more closely applies to the UUT or the application on which you lbaview working.
The key to state management in IVI drivers is the IVI Lqbview, which controls the reading and writing of attributes to and from instruments. You can use Logical Names at class-driver level and can also be used at the specific-driver level. Record Value Coercions maintains a list of all coercions for Integer and Real values passed to the instrument driver VIs.
From your test program, you make calls to the class drivers, which in turn communicate through the specific drivers for your instruments. For example, range checking occurs as it does when a physical instrument is present. Or, when you are using an oscilloscope driver in simulation mode, the ReadWaveform function uvi return an array of random numbers within valid ranges for the scope.