APIs of Agilent 34952A module

[Ebru]

Hi,
I am using Agilent 34952A module in 34980A Multifunction SW/Meas. Unit. I read the informations about "using third party products" and applied them. In driver session part, there exists two files both for 34980A and 34952A. I created driver session and logical name for 34980A. But for 34952A, in the driver session part, I selected 34952 and nothing(IviSwtch & IviDriver) appeared on provided API section but appropriate product appeared as 34980A. Nevertheless, I created driver session&logical name. And it gave no error. However, I couldn't see DIO, totalizer on the screen. How can I achieve this problem?

[Jason_D]

Ebru,

Are you using LabVIEW or LabWindows/CVI to program this instrument?  Are you using this instrument driver?  When you say that you look at a document about using third party products can you link me to that document or provide me the address so that we can be on the same page?

Are you looking to control your device with your own IVI based controls or a prebuilt project and VIs like in the driver I linked above?

[Ebru]

I've forgot to indicate the program that I've used. I am using NI Switch Executive. And I am using  "IVI-COM and IVI-C drivers for NI Switch Executive". "Using third party products" title can be found in NISE MAX Help section.

I created driver session and logical name for 34980A. In this case, 34952A modules were not recognized since 34980A and 34952A drivers appear seperate. Any modules other than 34952A had no problem. I did the same thing for 34952A. However, again I saw only other modules.

[Dennis_Knutson · Accepted solution]

I'm confused as to what you are doing. The switch executive will support the 34980 with the appropriate modules (i.e. scanners, muc, etc) but I don't see how it would support the digital I/O module as it is not part of the switch class. Frankly, I'm not sure the digital I/O fits into any IVI class.

NI Switch Executive would be used with other programs such as TestStand or LabVIEW. What master program are you using? From there, you should be able to call into the 34980A specific driver and control the digital I/O.

[Ebru]

I am dealing with automated test systems. In this context, now I am working on Self Test ITA. One part of this is just to test the all modules of 34980A. Development environment will be TestStand 4.1.x and for switching purposes we will use Switch Executive 3.0. Thanks for your reply indicating that 34952A does not support any IVI class. I will try to control it from TestStand as you describe.

[Ebru]

By the way, I have another question. DMMs of 34921A(mux) and 34932A(matrix) gives error while creating the virtual device. However, on the screen there was no problem. I saw the errors when I start to run NI Spy. My published APIs include IviDmm, IviSwtch and IviDriver. DMM was a problem for previous editions, not for 1_4_2_0.msi driver and NISE 3.0,  wasn't it? I've attached the error list copied from NI Spy.