Range Checking occurs in the instrument-specific driver. Back to Top 4. You can use this simulation capability with or without the class drivers. Rate this document Select a Rating 1 – Poor 2 3 4 5 – Excellent. With IVI drivers, you can check the status of an instrument after every function that interacts with the instrument without adding extra VI calls. IVI drivers verify that the values you specify for an attribute are valid.

Uploader: Mezikus
Date Added: 23 September 2012
File Size: 24.79 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 60681
Price: Free* [*Free Regsitration Required]

However, as you can imagine, random data is rluke very meaningful for your program or your units under test UUTs. If simulating, make sure that you select Specific Driver from Simulate With.

Using IVI Drivers in LabVIEW – National Instruments

Driver Sessions consist of an instrument driver software module, general property settings, and, when you are not in simulation mode, a hardware asset. Message 7 of The display mode of a string may be changed when right clicking and select another display mode.

If an instrument error occurs at that time, the IVI Engine returns an error through the error out control. Message ffluke of Learn more about our privacy policy. To verify the values you are planning to send the instrument, while you develop the test application.

Getting Started Using National Instruments IVI with LabVIEW or LabWindows/CVI

The option string configures the IVI driver features that you choose: Do you send a cr lf in labview? Before buying a new instrument, you can install the IVI-specific driver for that particular instrument and run your test program. Message 2 of To take multiple readings, click Read repeatedly.


Record Value Coercions flkke a list of all coercions for Integer and Real values passed to the instrument driver VIs.

When using traditional instrument drivers, you have labvuew supply some functions with the name of the channel that you would like to configure or measure. Lets you simulate the data that you normally acquire using built-in algorithms to simulate data generation. This range-checking operation happens completely in software in the specific driver.

Fluke fl45 Meter – IEEE (GPIB) Driver for LabVIEW – National Instruments

Therefore, the first step in instrument simulation is simply labvieew able to make function calls from your test program to an instrument driver without each labviee returning labviee error. Range Checking — One of the key responsibilities of the IVI instrument-specific drivers is range checking.

You may also refer to channels when using specific drivers by using virtual channel names. Note To complete the exercises in this document, you do not need to have the actual instruments because you can run IVI drivers in simulation mode. Often you choose an instrument setting from a range of values for example from 1.

With IVI drivers, you can check the status of an instrument after every function that interacts with the instrument without adding extra VI calls.


FLUKE, 45, [sn redacted], 1. Instrument drivers specify the instrument driver DLL while the hardware asset properties specify the resource name to access a physical device.

Standardization in IVI also enables instrument interchangeability in your test labiew. You can change the specific instrument drivers and corresponding instruments in your system underneath the class driver without affecting your test code. Rate this document Select a Rating 1 – Poor 2 3 4 5 – Excellent.

This site uses cookies to offer you a better browsing experience. In addition to generating data, you labvview use simulation drivers to inject simulated errors into your program.

Simulation mode provides the benefits shown in Table 1. If you previously configured the fl45 driver session for a Fluke 45 Digital Multimeter, you can set and use the Initialize VI of the flukw driver.

The developer can conditionally call the error query VI to learn more details about the instrument-specific error. If you change instruments in the future, you will need to re-implement this work for each new instrument added.