User`s guide
Table Of Contents
- Legal Information
- Equipment Operation
- General Safety Considerations
- Regulatory Information
- List of Related Publications
- Agilent TechnologiesE4418B Options
- About this Guide
- Getting Started
- Power Meter Operation
- Introduction
- Battery Operation (Option 001)
- Zeroing and Calibrating the Power Meter
- Making Measurements with the AgilentE-Series Power Sensors
- Making Measurements with the Agilent8480 Series Power Sensors
- Making Measurements using Sensor Calibration Tables
- Making Measurements using Frequency Dependent Offset Tables
- Setting the Units of Measurement
- Selecting Units of Measurement from the Softkeys
- Making Relative Measurements
- Setting the Resolution
- Setting Offsets
- Setting Averaging
- Measuring Pulsed Signals
- Setting Measurement Limits
- Selecting a Digital or Analog Display
- Setting the Range
- Configuring the Remote Interface
- Recorder Output
- Saving and Recalling Power Meter Configurations
- How Measurements are Calculated
- Presetting the Power Meter
- Self Test
- Operator Maintenance
- Contacting Agilent Technologies
- Menu Reference
- Error Messages
- Specifications
Error Messages
Error Messages
Agilent E4418B User’s Guide 4-11
-361 Parity error in program
The serial port receiver has detected a parity error and consequently,
data integrity cannot be guaranteed.
-362 Framing error in program
The serial port receiver has detected a framing error and consequently,
data integrity cannot be guaranteed.
-363 Input buffer overrun
The serial port receiver has been overrun and consequently, data has
been lost.
-410 Query INTERRUPTED
A command was received which sends data to the output buffer, but the
output buffer contained data from a previous command (the previous
data is not overwritten). The output buffer is cleared when power has
been off, or after *RST (reset) command has been executed.
-420 Query UNTERMINATED
The power meter was addressed to talk (that is, to send data over the
interface) but a command has not been received which sends data to the
output buffer. For example you may have executed a CONFigure
command (which does not generate data) and then attempted to read
data from the remote interface.
-430 Query DEADLOCKED
A command was received which generates too much data to fit in the
output buffer and the input buffer is also full. Command execution
continues but data is lost.
-440 Query UNTERMINATED after indefinite response
The *IDN? command must be the last query command within a
command string.
HP4402.book Page 11 Wednesday, November 29, 2000 4:46 PM