Let me know how you get on. The following figure shows this palette and some of the VIs and subpalettes that are shipped with it. I hope the snaps below will help to explain the problem: Log in or Sign up. Can anyone advise me based on what I have provided, or are there still other settings I am missing?

Uploader: Yolabar
Date Added: 10 July 2009
File Size: 19.31 Mb
Operating Systems: Windows NT/2000/XP/2003/2003/7/8/10 MacOS 10/X
Downloads: 65104
Price: Free* [*Free Regsitration Required]

Message 10 of Enabling autozero optimizes the instrument for accuracy, while disabling optimizes for speed. The Utility VIs might also include other custom instrument driver VIs that perform operations such as calibration or storage and recall of setups.

Action VIs are different from Configuration VIs because they do not change the instrument settings but order the instrument to carry out an action based on its current configuration. We know it is slightly different as it’s the a not the a, so 8114x may be the cause. Each routine corresponds to a programmatic operation such as configuring, reading from, writing to, and triggering the instrument.

Solved: LabVIEW: Identification Query Failed – Discussion Forums – National Instruments

Message 1 of Make sure agilnt for each successful call to the Initialize VI, you use a matching Close VI to avoid maintaining unnecessary memory resources. Of course Tulip was ticked for that to happen: The problem I am facing has not been solved yet. I looked in the manual at the frequency, period setting functions and the index. Log in or Sign up. What might the problem be? You also can use the Instrument Driver Finder to open example programs covering everything from analysis and presentation to using your instrument driver.


Sep 1, 2. Generally, you need to call the Close VI sgilent once at the end of an application or when you finish communication with an instrument. This what I can see on MAX: Once the measurement is complete, the Close VI is aglent which performs an instrument error query and terminates the software connection to the instrument.

It asks you to uncheck the ID query at the initialise vi and if the driver and hardware are compatible, it should work. I don’t know where you got the driver, but labviww is reading the binary block transfer all wrong. Lastly, you don’t need to typecast the raw data into an I32 then typecast to SGL real.

Accepted by topic author Liira. Generally, you need to call the Initialize VI only once at the beginning of an application.

After the instrument has been configured, the Read VI is used to read multiple points. I cannot proceed to Search, even if I changed the manufacturer to Agilent Technologies.


How to program a Pulse generator

Then when I go to to run this driver, I see the next: You can use an instrument driver for a particular instrument as is.

I’d give this a go and see how you get on However, when trying to run the plug-and-play examples, this error occurs “The ID Query failed. Instrument drivers simplify instrument control and reduce test program development time by eliminating the need to learn the programming protocol for each instrument. You may also be using a model that is not officially supported by this driver.

BaluncoreSep 2, Query but I don’t know if the case for the A. Labview instrument driver Agilent XX: The square wave output could be used to drive the Agilent PG. Message 9 of Was it right to install Agilent Driver to control HP?