On rare occasions, the N7840A software may cause the test to not function correctly. Listed below are symptoms, the procedures to fix them, and the common error messages the software exhibits.
A PNA with an older revision of firmware may cause test execution problems. Refer to the Readme.txt for current firmware revision level requirements.
When the N7840A test software is upgraded to a new revision, no further testing should be performed on existing orders. New orders must be opened for tests performed following the upgrade.
If the test software aborts during a test, the most likely causes are:
|
Cause |
Solution |
|
Incorrect test instruments or devices are being used |
Ensure that the required equipment is being used. See the Required Test Equipment tables. |
|
Incorrect or poor connections |
Check that all test equipment are attached to the correct connector and have solid connections: PC connections, GPIB, UUT connections, and PNA front panel cables. |
|
GPIB problems |
See GPIB Problems. |
|
PNA performance may cause an abort (particularly when checking connections following a prompt) |
Run Performance Check (under the Utilities Test Plan) to check the basic performance of the instrument. |
|
Receiver Compression test aborts |
Make sure the Maximum Leveled Power (Source Maximum Power) test passes before attempting the Receiver Compression test. |
|
Calibration Coefficients test aborts |
May be caused by memory leak in PNA firmware. Close the PNA application, wait 10 seconds, then restart PNA application. |
|
The test requires a power meter and the power meter display contains the message: Please Cal Chan A. |
On the power meter, set the Must Cal function to Off. |
If the above actions do not work, try the following steps one at a time:
Restart the TME application on the PC.
Restart the controller PC.
Ensure the PNA is not hung up. See the next section.
A test is stalled if there is no response at all from the PNA.
To check if the test is stalled, perform the following steps:
On the PNA front panel in the Utility block of keys (located above the USB connector), press the Macro/Local key to force the GPIB to local state and activate the front-panel keys.
Press the green Preset key. The display on the PNA should blank momentarily in the process of refreshing.
If no response is indicated from the above check, try each of the following steps to fix the problem:
Exit and restart the network analyzer application:
On the instrument, click the PNA icon on the Windows desktop to restart the application.
Restart Windows on the PNA network analyzer.
Exit the network analyzer application, if not done yet.
On the network analyzer, move the cursor down to the bottom of the display to make the Windows toolbar appear.
Click the Start button, click Shut Down, and restart the instrument.
As a final option, if you are unable to use a mouse to restart Windows, restart the network analyzer by pressing the lighted power button for more than five seconds.
Listed below are some common error messages that require additional information:
|
Error Message |
Description / Action |
|
Administer may be updating equipment database; equipment may be changing and any test performed may have the wrong equipment assignment. |
Talk to your system administrator about correcting this problem. |
|
Any message containing SCPI command error |
The error is most likely caused by a problem in the PNA firmware. Re-run the test. |
|
Error Initializing UUT Device .... message appears in a window titled HPAutoDetectUUTPrj |
If the PNA appears to be properly connected to the GPIB, check the GPIB settings on the PNA. |