Can't get Agilent DSO3202A oscilloscope to work with LabView

[ajshutler]

I want to acquire data from my Agilent DSO3202A oscilloscope using LabView.  I have downloaded all of the latest IVI drivers and plug-and-play modules from NI's website.  Through MAX, I have installed the ag3000 IVI driver and given it a new logical name, "o_scope."  I cannot see the oscilloscope any other way.  The only connection it has on the backside of it is a single USB port.  Window's Device Manager sees the oscilloscpe and has installed it properly.  However, when I launch one of the example VI's contained in the plug-and-play LLB and set the I/O port to "o_scope" or "ag3000," nothing runs properly.  I have yet been able to acquire data. 

Granted, I'm new to IVI drivers and may be doing something terribly wrong.

Any ideas?

[Dennis_Knutson]

For one thing, you are mixing apples and oranges. The plug and play driver is a native LabVIEW driver and does not use the IVI driver at all. An IVI logical Name control is different than a VISA Resource Name control. If you want to use the IVI driver, try dropping the IVI Scope Class Initialize function onto the block diagram, right click on the logical name input and select Create Control or Create Constant. Click on the little arrow and see if your logical name is available. To use the 3202A dll, the driver should install a LabVIEW driver for this as well though that sort of defeats the whole purpose of using an IVI driver.

If you want to use the plug and play driver, then it should be listed in MAX under Devices and Interfaces. Try doing a refresh if it's not. If it's USBTMC, it will be listed and when you create a VISA Resource Name for the plug and play initialize function, it will be listed.

Note that the driver page says that only the GPIB and serial interfaces are supported. You should check in windows device manage to see if it listed as USBTMC. If it's not, you may need a new driver from Agilent.

Edit: a quick look at the programming manual only mentions GPIB and serial. There is also mention of needing special Agilent software in order to use the USB port for remote programming. This would indicate to me that it is not USBTMC. A call to Agilent would probably be in order.

Message Edited by Dennis Knutson on 08-31-2009 11:49 AM