EasyManua.ls Logo

Fluke 9500B - Page 205

Fluke 9500B
297 pages
Print Icon
To Next Page IconTo Next Page
To Next Page IconTo Next Page
To Previous Page IconTo Previous Page
To Previous Page IconTo Previous Page
Loading...
Appendix A to Section 8: 9500B Maintenance — Error Reporting Subsystem 8-A1
Final Width = 215mm
ALWAYS: record the total message content for possible use by the Service Center.
8.A.1 Error Detection
All errors which cannot be recovered without
the user's knowledge, result in some system
action to inform the user via a message, and
where possible restore the system to an
operational condition. Errors are classified by
the method with which they are handled.
Recoverable errors report the error and then
continue. System errors which cannot be
recovered cause the system to reset via the
Power-on state to a system trip error report
state, from which a 'resume' may clear the
error, but generally such messages are caused
by hardware or software faults, which require
user action.
8.A.2 Error Messages
8.A.2.1 System Trip Errors
For all system trip errors, the error condition is
reported only via the front panel. The error
will pull the processor reset line to restart the
system as at power-on. The screen will display
a message indicating that there has been a
system trip error and thus the processor has
been reset. A user may continue by use of the
'resume' key, or from power on, and initiate
repair if the fault persists.
Appendix A to
Section 8 of the
User’s Handbook for
Model 9500B
Error Reporting Subsystem
Note to users: For the sake of completeness, this appendix collects together the error codes which might be generated either on the instrument
front panel, or via the IEEE 488 system bus.
The following is a list of error numbers, which
will be displayed with their fault descriptions:
9501 - DAC Default Characterisation. Failed
9502 - Failed to clear Flash RAM
9504 - No ADC ready bit after 160ms
9505 - Flash RAM protected by switch
9510 - Measurement failed to complete
9512, Output off request did not complete
9514, Output Off Expected
9515, Main unit control loop failure
9516, Internal overheating: Check air vents
9517, Internal frequency Failed to re-lock
9518, ADC failed to complete measurement
9519, Rf DAC control loop failure
9520, TV waveform control loop failure
For the following errors, an error number will be allocated at
run time:
UNDEFINED SYSTEM TRIP ERROR
OPERATING SYSTEM ERROR
8.A.2.2 Recoverable Errors
8.A.2.2.1 Type of Errors
These consist of Command Errors, Execution
Errors, Query Errors and Device-Dependent
Errors. Command, Query and Execution Errors
are generated due to incorrect remote
programming. Device-Dependent Errors can
be generated by manual as well as remote
operation. Each of the reportable errors is
identified by a code number.
8.A.2.2.2 Error Reporting
In response to a bus or a keyboard error, there
are certain categories of error reporting.
Primarily, the error will be reported to the
original source of the error, but in some cases
will be reported to both local and remote
operators. Locally, the error will be displayed
on the front-panel screen; remotely, it will set
the relevant ESR bit, and add the error to the
Error Queue.
Note about the ERROR Queue
(accessible via the IEEE-488 Interface)
The Error Queue is a sequential memory stack.
Each reportable error has been given a listed
number and explanatory message, which are
entered into the error queue as the error occurs.
The queue is read destructively as a First-In/
First-Out stack, using the query command
SYSTem :ERRor? to obtain a code number
and message.
Repeated use of the query SYSTem :ERRor?
will read successive Device-Dependent,
Command and Execution errors until the queue
is empty, when the 'Empty' message (0,"No
error") will be returned.
It would be good practice to repeatedly read
the Error Queue until the 'Empty' message is
returned.
The common command *CLS clears the queue.

Table of Contents

Other manuals for Fluke 9500B

Related product manuals