Table of Contents
Advertisement
Error Messages
Analyzer Break (613)
Cause: Status message.
Analyzer limitation; all range resources in use
Analyzer limitation; all pattern resources in use
Analyzer limitation; all expression resources in use (10360)
Cause: Your trace specification would use more than the maximum number of
resources available to the analyzer.
Action: Simplify the trace specification.
Analyzer trace running (1304)
Cause: This error occurs when you attempt to change the external analyzer
mode while a trace is in progress.
Action: Halt the trace before changing the external analyzer mode.
BNC trigger break (616)
Cause: This status message will be displayed if you have configured the
emulator to break on a BNC trigger signal and the BNC trigger line is
activated during a program run. The emulator is broken to the monitor.
Break caused by CMB not ready (611)
Cause: This status message is printed during coordinated measurements if
the CMB READY line goes false. The emulator breaks to the monitor. When
CMB READY is false, it indicates that one or more of the instruments
participating in the measurement is running in the monitor.
Action: None, information only.
Break condition configuration aborted (653)
Cause: Occurs when <CTRL>c is entered during the configuration of break
conditions.
Break due to cause other than step (689)
Cause: An activity other than a step command caused the emulator to break.
This could include any of the break conditions or a <CTRL>c break.
448
Advertisement
Table of Contents
