Frequency Response TroubleshootingThis topic offers troubleshooting for the frequency response performance tests and adjustments:
Performance Test TroubleshootingIf the Frequency Response Test fails by a small amount (5 dB or less), the instrument can probably be fixed by performing the Flatness Adjustment. If an adjustment cannot fix the problem, or the test fails by a large error (5 dB or more), this would indicate a faulty assembly. In order to troubleshoot an RF problem, refer to the analyzer Service Guide for troubleshooting procedures and the overall block diagram. Assemblies can be bypassed by injecting 322.5 MHz or 22.5 MHz signals at the appropriate places. If the frequency response test fails at frequencies 3.6 GHz and above (high bands), the following should be done:
If the frequency response test fails at frequencies below 3.6 GHz (Low band), the following should be done:
If frequency response fails at several frequencies between 9 kHz and the maximum frequency range of the analyzer (failures in both High band and Low band), and a readjustment does not fix the problem, suspect assemblies that are common to both High and Low bands such as a damaged Input Attenuator or the A11 Low Band Switch Assembly. If the Frequency Response test fails in the Preamp On path, run the Attenuator Slope (Preamp On) Adjustment. Classic TechniqueThe Frequency Response tests are performed with classic power sensor/splitter techniques. Mismatch error (though present) is minimized by using good connector care practices. The Frequency Response specification below 3.6 GHz is very small, so any mismatch error could affect the test results. If a millimeter UXA fails the Frequency Response test (even after being adjusted), it could indicate that there is a problem with the test setup, or the UXA input. Timeout ErrorsThe EA3 Frequency Response Performance Test will sometimes encounter a GPIB timeout when the test is started. This timeout will occur if Basic Mode (I/Q Analyzer) is not preloaded in the signal analyzer. This situation occurs if large measurement applications (LTE for instance) are preloaded on the instrument instead of Basic Mode. The timeout occurs because the analyzer tries to start Basic Mode, but it must first remove applications from memory in order to load Basic Mode. If the time to clear memory and then load Basic Mode takes too long, then TME will interpret this to be a GPIB timeout. The way to fix this timeout issue is to manually preload Basic Mode in the analyzer. Adjustment TroubleshootingClassic TechniqueThe Frequency Response Adjustment has three distinct steps. Each step can have a unique failure mode.
PNA-X TechniqueThe millimeter UXA and PXA (Options 544 and 550) frequency response adjustment uses a PNA-X network analyzer for the signal source. The PNA-X provides a vector corrected input signal to the DUT. In other words, the frequency response corrections are the true amplitude corrections with mismatch error removed from the system. If there are connectivity problems with the power meter when running the adjustments or utilities that use the network analyzer, ensure the power meter is correctly connected to the PNA-X. Please refer to the power sensor calibration section in the Network Analyzer Freq Sweep Calibration topic. If the connections have been thoroughly checked and are correct, then there may be a problem with the network analyzer. A system recovery of the network analyzer may be necessary. Please contact network analyzer support for more information and procedures. Note that the firmware version may change and information will be lost after doing the recovery. |