MXA burst power

[BrentSchenk · Accepted solution]

I think I have figured out the source of the problem.  I dont have my MXA with me right now but i would like to see an NI Engineer hopefully confirm that this will fix it and later this afternoon i will be able to test it out myself.  Anyways the problem lies in the VI at the very base that keeps track of the desired measurement that is to be taken.  Its a VI set for reentrance so its supposed to be an "object" and the data is stored in the shift register so that each time the VI is called it retrains the data in the same memory space from the last time it was called.  The order for the measurements in this "object" is as follows:

0 Swept SA

1 Adjacent Channel Power

2 Channel Power

3 Burst Power

4 Power Stat CCDF

5 Spurious Emissions

6 Spectrum Emission Mask

7 List Sweep

I think that every other VI in the driver is expecting the following order so that it can issue the desired commands to the instrument:

0 Swept SA

1 Channel Power

2 Occupied Bandwidth (which I find weird because it isnt even in the "object" )

3 Power Stat CCDF

4 Adjacent Channel Power

5 Burst Power

6 Spurious Emissions

7 Spectrum Emission mask

8 List Sweep

If anyone can hopefully confirm this is wrong and please change the driver so that I can get a correct working one that would be much appreciated.

Regards,

Brent

Message Edited by BrentSchenk on 10-16-2008 10:50 AM

[BrentSchenk]

bump

I'd rather this fix doesn't get lost and that maybe this might fix the broken driver.  I won't bump this thread up anymore after this.

[Caleb_W]

Hi Brent,

I don't have the same box to actually confirm the change in codes will work, but I will definately look into the issue to see if there is something that needs to be changed in our instrument driver.  If a fix is needed, I can't guarantee a timeframe for the fix, so it might be best if you go ahead and make the change on your end.