I am having the "Meas Uncal" from N9010A EXA while testing radiated emissions. The remote setting was from ETS-Lindgren's TILE6! program as following:
QP measurement in zero span, RBW=120kHz, VBW=300kHz, sweep=200 ms (10001pts).
When changed sweep = auto from Tile6!, EXA displayed sweep = 269 seconds (If I remembered correctly). Tile6! application treated the long sweep as no response and terminated its operation.
When set sweep = 200 seconds, still got "Meas Uncal". I could not stand to try any longer sweep.
Thank you for any advise in advance.
QP measurement in zero span, RBW=120kHz, VBW=300kHz, sweep=200 ms (10001pts).
When changed sweep = auto from Tile6!, EXA displayed sweep = 269 seconds (If I remembered correctly). Tile6! application treated the long sweep as no response and terminated its operation.
When set sweep = 200 seconds, still got "Meas Uncal". I could not stand to try any longer sweep.
Thank you for any advise in advance.
When the EXA is in zero span, there is no setting for auto sweep time. If the TILE6! program had sent the command to set sweep time to auto, the error message “Settings Conflict: Sweep Time cannot be auto-coupled while in Zero Span” would have been displayed and the sweep time would have remained at 200ms.
Also, when in zero span, changing the sweep time to 269 seconds and then to 200 seconds will not generate a Meas Uncal indication. However, if the span was changed to 2.57 MHz and sweep time set to auto coupled, the auto coupled sweep time would be 269s. If you then change the sweep time to 200s, a Meas Uncal will be indicated because the analyzer is sweeping faster than the auto coupled sweep time. This is proper behavior.
Therefore, check to make sure that when you set sweep = auto in the TILE6! program that the EXA span remains set to 0 Hz (zero span). If the span is being set to a non-zero value, then you need to consult ETS-Lindgren about this issue. Their definition of “sweep = auto” might not be equivalent to Agilent’s “sweep time = auto coupled”.
The “no response” behavior is something that the TILE6! program should be able to deal with. The TILE6! program is probably timing out. If the program is setting the sweep time to a high value, it should also change its timeout value to allow for the longer sweep time. This is an issue you will need to discuss with ETS-Lindgren.
Regards -