visa class conflict on one PC but not on another

[schiedeck]

Hello

My problem is, that vi's (LabVIEW-drivers for the data aquisition unit
34970A, but also any self-created) with VISA functions doesn't work on
one PC, but on another PC (with the same LabVIEW version 6.0 and the
same operation system Windows 2000) they do.

The reason why it doesen't work on one PC is a class conflict between
VISA resource name control and the VISA function block (read, write,
....).

On the PC with the problem also a framegrabber-card is installed. May
this cause the problem? Or maybe any other software?

I haven't installed any HPIB or other drivers for the data aquisition
unit on any PC. But also when I install the driver, the problem isn't
solved. (I tried both ways.)

Thanks for help, Florian.

[Labviewguru]

Florian,

This sounds all too familiar to me, even the same instrument (by the way, kudos to Agilent, what a great instrument!).

I would suggest opening MAX on each computer and doing a manual inventory of all software on both systems. MAX will tell you what versions of what software you have (I hope). You may be missing a core VISA component.

If that doesn't help, and you don't get an answer here, try contacting NI at ni.com/ask.

[JRA]

That is a great suggestion. Make sure you have the full NI-VISA driver installed. You may also want to check to see if that VISA resource is listed in MAX. Even though the software is present, you communication line may not be detected.

You can open up the VISA Alias Editor to find which resource names exist on your computer. Then you can use the VISA Interactive Control to actually test the VISA resource. Open the Interactive Control from Tools>>NI-VISA>>Interactive Control. Double-click the resource name of your device and select the Basic I/O tab on the panel that appears. This allows you to write to and read from your device to test if VISA works with it at all.

Testing with these two utilities should give you some more information about what is goin
g on in your system.