Instrument ID Query fails.... N5230C & E8362C

cca...@gmail.com

unread,

Dec 7, 2020, 1:29:45 PM12/7/20

to VNA Tools

Hello,

If I use a USB GPIB adaptor I have no problems.

If I try to connect over ethernet, I always get the ID Query fails. I have no problems sending commands through test panels, LV, or .NET apps.

Any ideas?

-Chris

1. viOpenDefaultRM (0x00001001)

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.7816 Call Duration 00:00:00.0000

Status: 0 (VI_SUCCESS)

2. viParseRsrcEx (0x00001001, "TCPIP0::A-E8362C-20804::inst0::INSTR", 6 (0x6), 0 (0x0), "INSTR", "TCPIP0::A-E8362C-20804::inst0::INSTR", "A-E8362C-20804")

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.7816 Call Duration 00:00:00.0020

Status: 0 (VI_SUCCESS)

3. viParseRsrcEx (0x00001001, "TCPIP0::A-E8362C-20804::inst0::INSTR", 6 (0x6), 0 (0x0), "INSTR", "TCPIP0::A-E8362C-20804::inst0::INSTR", "A-E8362C-20804")

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.7856 Call Duration 00:00:00.0020

Status: 0 (VI_SUCCESS)

4. viOpenDefaultRM (0x00001007)

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.7876 Call Duration 00:00:00.0000

Status: 0 (VI_SUCCESS)

5. viOpen (0x00001007, "TCPIP0::A-E8362C-20804::inst0::INSTR", 0 (0x0), 2000 (0x7D0), 0x00000006)

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.7876 Call Duration 00:00:00.0099

Status: 0 (VI_SUCCESS)

6. viInstallHandler (TCPIP0::A-E8362C-20804::inst0::INSTR (0x00000006), 0x3FFF2009 (VI_EVENT_IO_COMPLETION), 0x00000281F186A62C, NULL)

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.7976 Call Duration 00:00:00.0000

Status: 0 (VI_SUCCESS)

7. viClose (0x00001001)

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.7976 Call Duration 00:00:00.0010

Status: 0 (VI_SUCCESS)

8. viWrite (TCPIP0::A-E8362C-20804::inst0::INSTR (0x00000006), "*IDN?", 5 (0x5), 5 (0x5))

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.7986 Call Duration 00:00:00.0019

Status: 0 (VI_SUCCESS)

9. viRead (TCPIP0::A-E8362C-20804::inst0::INSTR (0x00000006), "Agilent Technologies,E8362C,MY43020804,A.09.42.22.", 16384 (0x4000), 50 (0x32))

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.8006 Call Duration 00:00:00.0000

Status: 0 (VI_SUCCESS)

10. viSetAttribute (TCPIP0::A-E8362C-20804::inst0::INSTR (0x00000006), 0x3FFF001A (VI_ATTR_TMO_VALUE), 3000 (0x0000000000000BB8))

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:13.8006 Call Duration 00:00:00.0000

Status: 0 (VI_SUCCESS)

> 11. viEnableEvent (TCPIP0::A-E8362C-20804::inst0::INSTR (0x00000006), 0x3FFF200B (VI_EVENT_SERVICE_REQ), 1 (0x1), 0 (0x0))

> Process ID: 0x00000F78 Thread ID: 0x000032B4

> Start Time: 13:20:13.8006 Call Duration 00:00:04.0061

> Status: 0xBFFF0015 (VI_ERROR_TMO)

12. viStatusDesc (TCPIP0::A-E8362C-20804::inst0::INSTR (0x00000006), 0xBFFF0015 (VI_ERROR_TMO), "Timeout expired before operation completed.")

Process ID: 0x00000F78 Thread ID: 0x000032B4

Start Time: 13:20:17.8068 Call Duration 00:00:00.0010

Status: 0 (VI_SUCCESS)

Michael Wollensack METAS

unread,

Dec 8, 2020, 2:23:54 AM12/8/20

to VNA Tools

Hi,

If it works over GPIB and not over Ethernet then it could be a Firewall issue.

Starting from METAS VNA Tools V2.3.2 the installer adds an rule for METAS VNA Tools to allow VXI-11 with service requests.

If you just use NI MAX to communicate your are not using SRQs.

I'll sent you the newest version of VNA Tools in a private mail.

Please let me know if it solved the problem.

Regards

Michael

Chris C

unread,

Dec 9, 2020, 10:51:03 AM12/9/20

to VNA Tools

Hi Michael,

The new version solved my issues connecting via Ethernet, thank you!

Somewhat strange was our N5230C had no issues with using the default LAN Device name, however, our E8362C had to be changed to "hpib7,16".

Our PXI P9371A will not work, also with a ID Query Failed error. I don't believe you support this device based on the PNA driver code but I had thought that the P9XXXX and P5XXXX are on the same FW, I do not have a P5XXXX to test but was thinking of modifying the code to allow the P9XXXX to see if it will work. Any thoughts on this?

if (idn.IndexOf("Agilent Technologies,E836") < 0 &&

idn.IndexOf("Agilent Technologies,N52") < 0 &&

idn.IndexOf("Keysight Technologies,N52") < 0 &&

idn.IndexOf("Keysight Technologies,E508") < 0 &&

idn.IndexOf("Keysight Technologies,M937") < 0 && // PXI over HiSLIP

idn.IndexOf("Keysight Technologies,M948") < 0 && // PXI over HiSLIP

idn.IndexOf("Keysight Technologies,M980") < 0 && // PXI over HiSLIP

idn.IndexOf("Keysight Technologies,P50") < 0) // USB over HiSLIP

{

throw new System.Exception("Instrument identification query failed.");

}

Michael Wollensack METAS

unread,

Dec 10, 2020, 3:50:09 AM12/10/20

to VNA Tools

Hi,

> Somewhat strange was our N5230C had no issues with using the default LAN Device name, however, our E8362C had to be changed to "hpib7,16"

Please ask Keysight why

> Our PXI P9371A will not work, also with a ID Query Failed error.

I've added the P937 series to the PNA driver. I'll send you another private email with the updated driver dll (just replace the dll under 'C:\Users\Public\Documents\Metas.Instr\Drivers').

Please report back. If it works it will be part of VN Tools V2.4.3.

General remark, please use HiSLIP and not VXI-11 when it's possible, see https://scdn.rohde-schwarz.com/ur/pws/dl_downloads/dl_application/application_notes/1ma208/1MA208_2e_HiSLIP.pdf

Regards

Michael

Chris C

unread,

Dec 14, 2020, 9:08:29 AM12/14/20

to VNA Tools

Michael,

Didn't see the update and had already modified the driver to work. I will replace with the one you e-mailed me to make sure I am using your code and not modified code.

Initial testing looks promising; no errors or warnings. Hopefully later this week I will find time to go through an entire calibration including noise characterization of the VNA to verify all functions.