VISA or IVI drivers, example code?

[jto2]

Hello,

I have an Agilent DSO-X-2004A oscilloscope and I've downloaded two different set's of drivers that work. Here are the links to the drivers.

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=9E84674573AF6AB8E0440021287E6A...

http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=A661BD7B892F06B2E0440021287E6A...

The first one is the Agilent 2000 3000 4000 X-Series drivers, that require only NI VISA-4.6

The second is the Agilent agx2k3k Oscilloscope drivers, that require NI VISA-4.6 or IVI Compliance 4.3

The second one has example codes, which are VERY helpful for me since I am new to LabVIEW. The first one does not have examples, but seems to have more thorough driver library with more scope options to set. Without the examples though, I will have a tough time. Can I find examples for those drivers somewhere?

When mixing blocks from different drivers, I get broken wires with the message "source is IVI session of class, sink is VISA session of class". Maybe if I could resolve that, I could mix the driver blocks.

Thanks

John

[jto2]

The answer is that both driver sets have example code in their .zip files. The first one (Agilent 2000 3000 X-Series) just didn't have the examples show up in the Instrument I/O palet, and the other one (agx2k3k) did. You can add the examples to the palet by following the instructions here:

http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/merging_vis_on_palette/ 

The question of which set to use is still open. The Agilent 2000 3000 X-Series drivers are "Certified LabVIEW Plug and Play (project-style) Instrument Drivers", and the agx2k3k dirvers are "Certified Multi-Enviornment IVI Instrument Drivers"

For a new user like myself, it's very hard to know the differences and how they may effect me down the road. Hopefully someone with more experience can chime in. 

- John

[Dennis_Knutson]

Project driver examples are available in the same way as all other examples - Help> Find Examples.

IVI drivers from NI are written in C and you cannot easily edit them. Nor can you mix IVI and LabVIEW functions.