Agilent MXA ACP automated measurement

[tpq43]

I am trying to configure the Agilent MXA N9020A  Signal Analyzer to measure ACP using the MXA VI's available on the NI website.  I have been encountering the same error for some time now, the error I am experiencing is an Unexpected Number of Parameters #115.  The VI's error surfaces when the Configure Carrier (List Property) VI is called.  I have only one carrier and the used inputs to the VI are Measurement Noise Bandwidth, Enable Carrier Power Present, Method List, VISA and Error I/O.  I have attempted setting a break point, and manually stepping through the VI and I still do not understand what is causing the error.  I am new to using the tool but I have written a few other VI's to successfully configure the MXA.  I am not sure if this is related but I am not retrieving measurement data from the equipment.  I am using the read measurement poly VI with others selected.  I have an 1D indicator array at the measurement data connection.  Any help you can supply is appreciated.

[SunnyBoy]

I have got the same problem. I'd like to know whether the problem be solved or not and how to solve it.Thanks.

[ColeTrain]

Hello Guys,

I have been looking through the driver and there are a number of VIs that could potentially throw errors.  Can you narrow down which specific function is throwing the error and take a screen shot of the error that is thrown?

[ColeTrain]

K, so I found the VI called Configure Carrier.  I didn't realize it was a measurment VI and not a configuration VI.  So... with that said, what properties are you passing this VI?  Have you probed inside of the VI to view the strings that the VI creates?  Once you have the full string that's being passed, you can most likely contact Agilent to see if they know what it should be or if it's looking for a different syntax.

[tpq43]

It was some time ago when I posted this message.  From my previous error description and reviewing the working VI I resolved the problem by converting the scalar noise bandwidth into an single element array using the build array primitive.  Also ensure each input to the list property VI shares the same array dimension.  Additionally, I added the carrier count polymorphic VI with a carrier count of "1" before the list property VI.

I  hope this helps as I mentioned previously it has been sometime since I posted this message.

[SunnyBoy]

Thanks for your reply. I have only one carrier. The problem indicating Unexpected Number of Parameters #115 has been solved by converting the scalar parameter list ( Carrier spacing list,Filter alpha,Noise Bandwidth list, Method List etc.)into a single element array.I also probed inside of the VI to view the strings that the VI creates, and the SCPI commands produced were OK.But there is another problem.I found that my setting to the carrier and offset didn't work. After running my VI the offset Freq was set to 3MHz and the IBW was set to 2MHz defaultly, unlike what I set manually.

The VI and the screen shot of the ACPR are attached below.Thank you.

[ColeTrain]

Hello SunnyBoy,

What is the string that is being passed to the VISA Write inside of the Configure Frequency (Center Span) VI?  Have you verified that you are entering the proper case structure (should be case 0).

[SunnyBoy]

 The VISA Write inside of the Configure Frequency (Center Span) VI works. I have verified that the strings passed are OK, that is

:ACP:FREQ:SPAN 5000000.000000;:FREQ:CENTER 8.365000E+8;

So the problem lies in other aspects. Thank you.

[SunnyBoy]

It seems that the read measurement(others) VI returns settings to be default.

[SunnyBoy]

Hello,my dear friends. I've solved my problem. After I changed the Radio Device BTS/MS set from MS to BTS, the VI worked well. Then I noticed that when I tested ACPR by setting parameters in Meas Setup manually, the Radio Device couldn't be changed, set to BTS by default. So,the  Radio Device in my program (Cofig Carrier-List sweep,Config Offset Freq and IBW)  can be only set to BTS.

But how to change the Radio Device from BTS to MS? There is a solution. We can set the Radio Std to a standard signal such as IS-95 or WCDMA etc. , and make the Radio Device MS, then we change the Radio Std back to None in Mode Setup. The Radio Device can be set to MS and Everything will be working well.