Controlling Agilent N9310A - VISA conflict

[yoppy]

I need to control Agilent N9310A using Labview. But LV cannot detect the N9310A. After searching here and there, I found that NI-VISA Passport for TULIP should be activated. I've activated it and the result is the same, cannot detect N9310A. When I use VISA OPEN REPORT from Agilent's IO Library Suite, it shows that there is a conflict between NI-VISA and AGILENT-VISA.

Please anyone share suggestions. Thanks.

[smercurio_fc]

TULIP would be required if you're using an Agilent controller. Are you actually using that? What interface are you using with the device? GPIB? TCP/IP? USB? Serial? Tin can and string?

Unless absolutely necessary (and you have not indicated anything to imply this), you should not have two installations of VISA. Pick one. Since you're using LabVIEW, you should have NI-VISA installed only. Why do you need Agilent VISA?

[yoppy]

N9310A uses USB interface. Actually I dont really need Agilent VISA. I just wanted to know what features Agilent's software offers. Now I have uninstalled Agilent VISA. But Labview still doesn't detect the N9310A. Devices and Interfaces section on MAX doesn't also list USB device. I'm using MAX ver 4.2. What haven't I do yet?

[Aldo_A]

Hi yoppy,

try downloading and installing our driver for the N9310A and see if that helps in detecting the instrument: http://search.ni.com/nisearch/app/main/p/bot/no/ap/tech/lang/en/pg/1/sn/catnav:id/q/agilent%20n9310a...

[Dennis_Knutson]

The presence of an instrument driver has absolutely nothing to do with MAX detecting an instrument. The detection requires that the device be a USBTMC type and that is defined in the windows driver.

How does the instrument appear in windows device manager. If it's listed as USBTMC, then I would completely uninstall all versions of VISA, then install only NI-VISA.

[yoppy]

I have also installed N9310A driver for Labview like Aldo's suggestion. Windows device manager could detect N9310A as USBTMC. Still it didn't work. Then I tried to upgrade the MAX to version 4.6. Suprisingly, problem solved. I am not really sure if it is the problem of outdated MAX. Anyway, problem solved. Thanks everybody.