LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

I want A Driver for N5224B (Network Analyzer). Does it exist?

Hello I am Beginner on LabView.

 

Recently, I found the Driver for N5224B (Network Analyzer).

 

But, I only found the Diver for N5224"A". 

 

 

So, I tryed whether the Driver for N5224A compatibility with N5224B, but it is not compatibility with N5224A.

 

So, I wonder if there is a driver compatible with N5224B. And If there is no compatible Driver, is there any SCPI instruction related to N5224B?

 

Thank You!

0 Kudos
Message 1 of 4
(2,391 Views)

Hi Seongmo,

 


@seongmo1476 wrote:

is there any SCPI instruction related to N5224B?


Why don't you ask the manufacturer of your NetworkAnalyzer for some manuals?

Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 4
(2,381 Views)

https://www.keysight.com/main/techSupport.jspx?cc=US&lc=eng&nid=-32497.1212363&pid=2811518&pageMode=...

I assume you either have an Agilent or keysight network analyzer. The driver is available on their site.

0 Kudos
Message 3 of 4
(2,326 Views)

What is the problem with the N5224A driver? The most likely is that it checks in the Initialization explicitly for the N5224A identifier in the identification response. This can be easily solved by modifying the initialize function to allow both identifiers.

Another problem might be that the B version implements new funcitonality that the old device didn't have. That can be a problem of course but could be solved by adding the new funcitonality. It should not affect the funcitonality of the old functions however unless HP/Agilent/Keysight decided to change the entire command set, which they usually don't if they only change the revision letter at the end of the model number.

 

The driver on the Keysight site is an IVI driver. While it should work and can be used of course, its implementation is in a DLL made available to LabVIEW through Call Library Nodes. That is ok to use but prevents you from debugging your program by going into the driver functions itself to see what happens and that can be sometimes a problem.

Rolf Kalbermatter  My Blog
DEMO, Electronic and Mechanical Support department, room 36.LB00.390
0 Kudos
Message 4 of 4
(2,303 Views)