An error generally causes the analyzer to display a tooltip across the lower part of the screen. The tooltip provides a textual description of the error, e. g.:
The errors can be divided into three categories:
Remote errors (SCPI errors) may occur during the execution of a remote control program. They include an error code, followed by the short description of the error. Remote errors are specified and described in the SCPI standard; they are cleared upon *CLS.
Software errors (setting errors) can occur e.g. if numeric entries in an analyzer dialog are incompatible with each other or with the current analyzer state. These errors are generally self-explanatory and easy to correct.
Hardware errors indicate an incorrect hardware state. Some of the hardware errors cause the instrument to be switched off in order to avoid damage. Hardware errors with possible causes and remedies are listed below.
A misspelled command header causes SCPI error –113, "Undefined
header;..."; a misspelled parameter causes SCPI error –141,
"Invalid character data;...". The GPIB
explorer
provides a list of all supported commands and their character data parameters.
Hardware errors can be detected at various stages of the start-up or measurement procedure.
Configuration errors occur on start-up of the analyzer, e.g. if a hardware module or configuration file cannot be detected. Configuration errors cause an entry in the error log (Info –Error Log).
Asynchronous errors can occur any time while the analyzer is operating. The analyzer is checked periodically for asynchronous errors.
Measurement errors are due to inadmissible hardware settings and states during the measurement process.
Asynchronous errors can occur any time while the analyzer is operating. The analyzer is checked periodically for asynchronous errors. Many of these errors also cause an entry in the status reporting system.
|
Error |
Description |
Remedy |
Bit no.*) |
|
Instrument temperature is too high |
The analyzer detects that the instrument temperature is too high. After three warnings, the analyzer is shut down. |
Reduce ambient temperature, keep ventilation holes of the casing unobstructed. |
7 |
|
Receiver overload protection tripped |
The analyzer detects an excessive input level at one of the ports. If this condition persists, all internal and external generators are switched off (Channel – Power Bandwidth Average – RF Off). |
Reduce RF input level at the port. Check amplifiers in the external test setup. |
3 |
|
Reference frequency lock failure |
With external reference signal (System – External Reference active) or option ZVAB-B4 (oven quartz), the reference oscillator is phase locked to a 10 MHz signal. The message appears when this phase locked loop (PLL) fails. |
For external reference: check frequency and level of the supplied reference signal. |
1 |
|
Converter clock frequency lock failure |
The clock generator for the AD converter clock is phase locked to the reference oscillator. The message appears when this PLL fails. |
– |
– |
|
Oven cold |
With option R&S ZVAB-B4, oven quartz: The oven temperature is too low. |
Wait until the oven has been heated up |
8 |
*) The following bits in the STATus:QUEStionable:INTegrity:HARDware register are set when the error occurs.
The following errors are due to inadmissible hardware settings and states during the measurement process. Some of the errors also cause an entry in the status reporting system.
|
Error |
Description |
Remedy |
Bit no.*) |
|
Unstable level control at port <i> |
The analyzer detects an excessive source level at one of the ports. The signal is turned off and the sweep halted. |
Check signal path for the wave ai, especially check external components. Then press Channel – Sweep – Restart. |
9 |
|
Problem concerning external generator Gen<i> |
An external generator has been configured, however, it cannot be controlled or provides error messages. If several generators cause problems, the lowest number is indicated. |
Check whether the generator is properly connected and switched on. Check the GPIB address; exclude address conflicts when using several external generators or other equipment. |
10 |
|
Problem concerning external power meter Pmet<i> |
An external power meter has been configured, however, it cannot be controlled or provides error messages. If several power meters cause problems, the lowest number is indicated. |
Check whether the power meter is properly connected and switched on. Check the GPIB address; exclude address conflicts when using several external power meters or other equipment. |
11 |
|
Time grid too close |
The sweep points for a time sweep are too close, the analyzer cannot process the measurement data until the next sweep point starts. |
Increase stop time, reduce no. of points, increase IF bandwidth. If possible reduce number of partial measurements, e.g. by restricting the number of ports measured. |
12 |
|
Overload at DC MEAS <range> |
The input voltage at one of the DC input connectors on the rear panel is too high. |
Reduce input voltage. |
13 |
|
Port <i> output power unleveled |
The level control is unsettled or unstable, possibly due to an external disturbing signal. |
Change generator level at the port; check external components. |
2 |
*) The following bits in the STATus:QUEStionable:INTegrity:HARDware register are set when the error occurs.
This section applies to instruments which are not
equipped with option R&S ZVAB-B18, "Removable Hard Disk".
On older network analyzers, the virtual memory paging file is disabled. This means that the operating system cannot use the hard disk to extend its RAM. For very complex setups with many traces and large numbers of sweep points the limited RAM size may cause software crashes.
To enable the paging file, press the Windows key to access the desktop of your analyzer. Press Start > Control Panel > System > Advanced > Performance: Settings > Advanced > Virtual Memory: Change. In the Virtual Memory dialog, select System managed size > Set and close all dialogs using the OK buttons.
Restart the analyzer to enable the new virtual memory settings.
Our customer support centers are there to assist you in solving any problems that you may encounter with your network analyzer. We will find solutions more quickly and efficiently if you provide us with the information listed below. Simply open the relevant dialogs in the Info menu, press Print to File, and send us the file.
Setup Info: The instrument setup information (Info – Setup Info) contains your instrument settings. You can also send us the NWA setup file (*.zvx) that you generate after the fault occurs (File – Save...).
Option Info: The option info (Info – Option Info) informs us about the status of all software and hardware options of your analyzer.
Hardware Info: The hardware info (Info – Hardware Info) shows us the installed options and hardware assemblies.
Error Log: The error log (Info – Error Log) contains a chronological record of errors.
Save
System Report: The system report command (Info
– Save
System Report) starts a selftest, collects the setup, option, and
hardware information and the error log and writes everything to a *.zip
file. The *.zip file also contains the current eeprom data and a screenshot
of the NWA display. It is written to the report directory C:\Rohde&Schwarz\Nwa\Report.
The file name contains the current date and time, e.g. report_16112010_1120.zip.
Save System Report provides the most comprehensive information,
comprising all other Info files.
If possible, list the operating sequence (after the last preset of the instrument) that caused the fault.
Please refer to the Contact section for information about useful Rohde & Schwarz addresses.
