Contact an Expert

Thread: Can't connect to N5244A via LAN


Permlink Replies: 3 - Pages: 1 - Last Post: Sep 4, 2012 2:04 AM Last Post By: Herbert
Herbert

Posts: 2
Registered: 09/03/12
Can't connect to N5244A via LAN
Posted: Sep 3, 2012 12:52 AM
Click to report abuse...   Click to reply to this thread Reply
I have been plowing through all the docs and can't seem to find an answer. It feels like I am missing something obvious. I am trying to connect to the N5244A over a LAN and have no success. I can ping the device but when I try using NI Measurement & Automation explorer or the Agilent IO Control to add the N5244A I do not get a connection to the device. It is not found. Yet I can add other instruments.

I would like to do some LabVIEW programming, using the Agilent drivers, but cannot get past first base. I cannot open a VISA session in NI MAX or Agilent IO Control. I am suspecting there is a configuration problem on the N5244A. Any suggestions you might have would help alleviate some frustration! Thanks.
Dr_joel


Posts: 2,731
Registered: 12/01/05
Re: Can't connect to N5244A via LAN
Posted: Sep 3, 2012 12:58 AM   in response to: Herbert in response to: Herbert
Click to report abuse...   Click to reply to this thread Reply
The easiiest way to resolve most connection problems is to add a user to the pna that matches the user name of the windows PC you are using, giving it the same password. Make that user an administrator.

There are other ways around the problem but this is usuually the simplest.
bhokkan

Posts: 328
Registered: 12/01/05
Re: Can't connect to N5244A via LAN
Posted: Sep 3, 2012 10:25 AM   in response to: Dr_joel in response to: Dr_joel
Click to report abuse...   Click to reply to this thread Reply
Attachment SICL GPIB SCPI.png (14.2 KB)
For your connection from NI-MAX, are you trying to connect to the PNA via VXI-11 (a.k.a. SICL/LAN), or are you trying to connect via TCP/IP Socket? If you're trying to connect to the PNA via a resource string of "TCPIP0::hostnameOfPNA" or "TCPIP0::hostnameOfPNA::inst0::INSTR", then you're trying VXI-11. The VISA resource string for establishing a socket connection to the PNA is "TCPIP0::hostnameOfPNA::5025::SOCKET".

The first thing you should check is whether the appropriate server is enabled on the PNA (if you're not the only user of your instrument then perhaps someone else turned the server(s) off). The checkboxes for those are on the PNA's "SICL/GPIB/SCPI" dialog, which you get to from the dropdown menu Utility->System->Configure->SICL/GPIB/SCPI, or from hardkey/softkeys System->Configure->SICL/GPIB... See the attached image.

"Automatically Enable on Startup" selects for the VXI-11 / SICL LAN server to always automatically launch whenever the PNA application is started. If that checkbox is unselected then that server has to be enabled by the user (via the "SICL Enabled" checkbox) each time after the PNA app is launched, before you can make that type of connection from another machine. When "Automatically Enable on Startup" is enabled, the "SICL Enabled" checkbox afterward is selected and ghosted. All instruments in the PNA family shipped from Agilent since early 2008 have had "Automatically Enable on Startup" selected by default. If a user unchecks that, the setting is stored in the registry and installing new PNA firmware does not change the setting.

The "Sockets Enabled" checkbox on that same dialog controls the PNA's SCPI socket server. That checkbox's setting also gets stored in the registry / survives app shutdown/restart.
Herbert

Posts: 2
Registered: 09/03/12
Re: Can't connect to N5244A via LAN
Posted: Sep 4, 2012 2:04 AM   in response to: bhokkan in response to: bhokkan
Click to report abuse...   Click to reply to this thread Reply
Thanks to both for your suggestions, it helped me focus on specific issues. It was the structure of the VISA resource string that was my problem (i.e. the SOCKET part). Hadn't come across the SOCKET variant previously and hadn't seen anything in the documentation that hinted at this issue. There is so much documentation that it is easy to miss a detail. I have now got to the point where I can read back the response to an IDN? query in LabVIEW. Again, thanks for your contribution.

Point your RSS reader here for a feed of the latest messages in all forums