07-15-2002 09:08 AM
07-15-2002 01:34 PM
07-16-2002 06:38 AM
07-24-2007 05:58 PM
Its almost 7 years later and Im using an Agilent 34970A and trying to communicate with it using an Agilent 82357A GPIB/USB cable.
The downloaded VIs for the 34970A are giving me heck with the VISA Resource name and I also get an error as I pass throught the VISA Open VI. This is all in the Initialization VI.
Anyone have any experience with these two pieces of hardware and LV code that works well? By the way the 34970A and the 82357A work great with Agilent's Benchlink Datalogger.
Nick
07-24-2007 08:03 PM - edited 07-24-2007 08:03 PM
Message Edited by Dennis Knutson on 07-24-2007 07:04 PM
07-25-2007 11:54 AM
Dennis,The fix was easier than I expected. I followed the instructions listed below which I foundon the NI Device Driver Reference CD for NI-VISA, Da go figure!
I was up and communicating quickly. An hour later after working the VIs,the temps and voltages were reading well.SUPPORT FOR AGILENT/HP CONTROLLERS----------------------------------
NI-VISA now works with Agilent/HP GPIB and VXI controller cards. To
use this feature, go into the Measurement & Automation Explorer, select
"Tools>>NI-VISA>>VISA Options", choose the Passports tab, and enable the
NiVisaTulip.dll Passport. NI-VISA will automaticaly find and access any
GPIB or VXI devices. However, NI-VISA will not configure the Agilent/HP
hardware; you must still do that with the Agilent/HP I/O Config utility.
If you have both National Instruments and Agilent/HP controllers in the same
system, you must configure the cards at different system addresses, such as
GPIB0 and GPIB1. If both vendors try to use the same interface address,
NI-VISA will report an error from viFindRsrc or VISA Find Resources.