Instrument Control (GPIB, Serial, VISA, IVI)

cancel
Showing results for 
Search instead for 
Did you mean: 

Unable to communicate with Agilent 34410a in Labwindows/CVI via TCP/IP

Hi there!
In Labwindows/CVI I'm not able to communicate with an Agilent 34410a via TCP/IP protocol using NI-VISA libraries. MAX fails to detect the instrument during the visa-tcp/ip resource "create new" procedure. I installed the instrument driver for the specific model and added the passport for it but without success.
Got some suggestion?
Thanks
Rolly Grisenti
0 Kudos
Message 1 of 13
(6,274 Views)
Hello Rolly,
         If you are only using CVI and NI-VISA, I don't believe that there are any passports that you need to add.  The TCP/IP Passport should be enabled by default.  The instrument driver for the instrument should not affect whether or not the instrument is detected in MAX, so you should concentrate on the instrument's TCP/IP settings and troubleshoot your network.  Get the IP address from the instrument and try to ping it.  If it sucessfully pings, then just try manually adding it in MAX.

If it does not sucessfully ping, make sure that the instrument is setup for DHCP, check your firewalls, network cables, etc...  If there is someone else in your area that can communicate with the instrument, then it is probably a problem with your computer.

Let us know how it goes,

NathanT
0 Kudos
Message 2 of 13
(6,260 Views)
Hi NathanT,

the Agilent is regularly assessed on the LAN and received the proper IP by the DHCP manager: in fact I'm able to communicate in a telnet session or by  http by a browser.The Agilent responds perfectly. In MAX, when I try to add it manually I constantly get a" Insufficient location informatio or device or resource is not present in the system" error.

Rolly grisenti
0 Kudos
Message 3 of 13
(6,253 Views)
Hi NathanT,

the Agilent is regularly assessed on the LAN and received the proper IP by the DHCP manager: in fact I'm able to communicate in a telnet session or by  http by a browser.The Agilent responds perfectly. In MAX, when I try to add it manually I constantly get a" Insufficient location informatio or device or resource is not present in the system" error.

Rolly grisenti
0 Kudos
Message 4 of 13
(6,249 Views)
Hello Rolly,
          According to the duplicate post, you are using MAX 4.3 and VISA 4.2.  Is the instrument on the same subnet as your PC?  It is interesting that you can communicate with it over telnet and web browser, but not through MAX.  If you have not done so yet, I recommend temporarily disabling your firewall and seeing if that helps.  Maybe one of our MAX experts will have some other suggestions.

Cheers,

NathanT
0 Kudos
Message 5 of 13
(6,210 Views)
Hi NathanT,
I don't use any firewall on my computer. I also tried to assign both ( Agilent and myPC) to the same subnet without success. The last trial I implemented was to connect by a crossover cable the PC and Agilent assigning 2 IP as follows : myPC 169.254.4.20 and Agilent 169.254.4.10 but obstinately MAX refused to recognize the instrument. The curious matter is that MAX, in all the trials I made, sees the instrument but , at the end, it states "no vxi or lxi instrument found on the network"....hopeless
Rolly Grisenti
0 Kudos
Message 6 of 13
(6,190 Views)
Are you sure that it is a VXI-11 or LXI instrument? Have you tried the raw socket option in MAX?
0 Kudos
Message 7 of 13
(6,187 Views)
Hi there,
yes I'm sure for both question. The Agilent has got the logo LXI on the screen and I've tried also the manual entry: before that I scanned the opened ports on the DMM and used that numbers in the manual procedure.
Cheers
Rolly
0 Kudos
Message 8 of 13
(6,183 Views)
Do you have multiple ethernet ports on this computer or does it also have wireless? Some people have run into problems when trying to use an instrument connected to a non-default network port.

-Josh
0 Kudos
Message 9 of 13
(6,179 Views)
Rolly,

Two other things that would be helpful in diagnosing the problem are an NI-Spy capture and a Wireshark capture, capturing the communication between the host PC and the device while the discovery process is going on. Be sure to configure Wireshark to capture all TCP and UDP communication. Please post those two if possible, and it will be much easier to try to figure out what goes wrong.

Pankaj

0 Kudos
Message 10 of 13
(6,171 Views)