Agilent E5810

[Whitman_Cougar]

The second screen shot shows what happened if I input "gpib0,5". In short, it doesn't allow me to do that.

[Whitman_Cougar]

This 3rd screen shot shows what happened if I input "gpib0" only. Basically, NI-MAX accepted it and the result is shown in the screen shot I posted last week. It seems NI-MAX has a bug.

[J_Oneill]

Hi,

Could you just check that you have the NI-VISA Passport for GPIB checked in the VISA Passport Options?

Open MAX and select Tools » NI-VISA » VISA Options

In the VISA Options tab, select Passports under General Settings. Then ensure that theNiVi488.dll - NI-VISA Passport for GPIB is checked. 

Thanks,

[Whitman_Cougar]

Hi, James,

It is selected. Please see the attachment.

[J_Oneill]

Could you try and add a new device by "GPIB-ENET" instead of "VISA TCP/IP Resourse" right click Devices and Interfaces >> create new... >> select GPIB-ENET and follow the wizard.

[Whitman_Cougar]

Hi, James,

I tried it. But the GPIB-Ethernet Wizard couldn't locate a GPIB-Ethernet device, either with automatically browsing or manually specifying an IP address.

[J_Oneill]

Hi,

Possibly Agilet VISA is being used as apposed to NI VISA, or vice versa, try experimenting with NI VISA or Aglilets version as the Primary VISA in Conflict Manager within MAX

Could you possibly give me an exact description of your system. Possibly there is a compatibility issue. Have you ever been able to talk to GPIB instruments through your Agilent E5810? Or directly for that matter?

Best regards,

James O'Neill - Applications Engineer - National Instruments 

[Whitman_Cougar]

Hi, James,

I used both "NI VISA" and "Agilent VISA" as a primary VISA. One at a time. But neither worked.

My system is set up: an Agilent E5810A LAN/GPIB Gateway is connected to my company's network through a Netgear Ethernet switch. My computer is in the same subnet as E5810A. An Agilent 6812B is connected to E5810A through its GPIB interface. It worked fine until I upgraded NI-MAX to 5.3.3.

Currently, I am able to see and talk to 6812B under "Devices and Interfaces" in NI-MAX as "GPIB0::5::INSTR". Not sure how NI-MAX found it. But I used to be able to see it and talk to it under "Network Devices" as "TCPIP0::10.202.11.241::gpib0,5::INSTR" like the Agilent software does.

James, I think the main point is why NI-MAX doesn't take LAN Device Name: gpib0,5 as it instructs users to do so. It used to be fine. Did you ask NI-MAX software development engineers about this?

Thanks,

[billko]

---

@Whitman_Cougar wrote:

Hi, James,

I used both "NI VISA" and "Agilent VISA" as a primary VISA. One at a time. But neither worked.

My system is set up: an Agilent E5810A LAN/GPIB Gateway is connected to my company's network through a Netgear Ethernet switch. My computer is in the same subnet as E5810A. An Agilent 6812B is connected to E5810A through its GPIB interface. It worked fine until I upgraded NI-MAX to 5.3.3.

Currently, I am able to see and talk to 6812B under "Devices and Interfaces" in NI-MAX as "GPIB0::5::INSTR". Not sure how NI-MAX found it. But I used to be able to see it and talk to it under "Network Devices" as "TCPIP0::10.202.11.241::gpib0,5::INSTR" like the Agilent software does.

James, I think the main point is why NI-MAX doesn't take LAN Device Name: gpib0,5 as it instructs users to do so. It used to be fine. Did you ask NI-MAX software development engineers about this?

Thanks,

---

That looks like Windows XP.  I don't think MAX 5.x is compatible with WinXP.

[edit] actually, I'm so confused about compatibility, I don't know if that is true or not.

[billko]

---

@billko wrote:

---

@Whitman_Cougar wrote:

Hi, James,

I used both "NI VISA" and "Agilent VISA" as a primary VISA. One at a time. But neither worked.

My system is set up: an Agilent E5810A LAN/GPIB Gateway is connected to my company's network through a Netgear Ethernet switch. My computer is in the same subnet as E5810A. An Agilent 6812B is connected to E5810A through its GPIB interface. It worked fine until I upgraded NI-MAX to 5.3.3.

Currently, I am able to see and talk to 6812B under "Devices and Interfaces" in NI-MAX as "GPIB0::5::INSTR". Not sure how NI-MAX found it. But I used to be able to see it and talk to it under "Network Devices" as "TCPIP0::10.202.11.241::gpib0,5::INSTR" like the Agilent software does.

James, I think the main point is why NI-MAX doesn't take LAN Device Name: gpib0,5 as it instructs users to do so. It used to be fine. Did you ask NI-MAX software development engineers about this?

Thanks,

---

That looks like Windows XP.  I don't think MAX 5.x is compatible with WinXP.

[edit] actually, I'm so confused about compatibility, I don't know if that is true or not.

---

I think I got confused with LabVIEW compatibility, not Windows compatibility.