5 System Functions
System
Repeat (RPT) - This field shows the number of consecutive instances of the event, uninterrupted by other
events. If an event occurs 5 times with no other intervening event, the value of repeat will be 5.
If the value of Repeat is 1 the field does not display. If the value of Repeat is >1, the time and date shown
are those of the most recent occurrence. If the value of repeat reaches 999,999 it stops there.
Time - Shows the most recent time (including the date) at which the event occurred.
Key Path
System, Show
Mode
All
Remote Command
:SYSTem:ERRor[:NEXT]?
Example
:SYST:ERR?
Notes
The return string has the format:
“<Error Number>,<Error>”
Where <Error Number> and <Error> are those shown on the Show Errors screen
Backwards Compatibility
Notes
In some legacy analyzers, the Repeat field shows the number of times the message has repeated
since the last time the error queue was cleared. In the X-Series, the Repeat field shows the number
of times the error has repeated since the last intervening error. So the count may very well be
different than in the past even for identical signal conditions
Unlike previous analyzers, in the X-Series all errors are reported through the Message or Status lines
and are logged to the event queue. They never appear as text in the graticule area (as they
sometimes do in previous analyzers) and they are never displayed in the settings panel at the top of
the screen (as they sometimes do, by changing color, in previous analyzers).
As a consequence of the above, the user can only see one status condition (the most recently
generated) without looking at the queue. In the past, at least in the Spectrum Analyzer, multiple
status conditions might display on the right side of the graticule.
In general, there is no backwards compatibility specified or guaranteed between the error numbers in
the X-Series and those of earlier products. Error, event, and status processing code in customers’
software will probably need to be rewritten to work with X-Series.
In the legacy analyzers, some conditions report as errors and others simply turn on status bits.
Conditions that report as errors often report over and over as long as the condition exists. In the X-
series, all conditions report as start and stop events. Consequently, software that repeatedly queries
for a condition error until it stops reporting will have to be rewritten for the X-series.
Initial S/W Revision
Prior to A.02.00
Previous Page
See
Key Path
System, Show, Errors
Initial S/W Revision
Prior to A.02.00
Sequence Analyzer User's & Programmer's Reference
153
Содержание E6650A EXF
Страница 34: ...1 About the Test Set Mouse and Keyboard Control 34 Sequence Analyzer User s Programmer s Reference...
Страница 94: ...2 Programming the Test Set Common Commands 94 Sequence Analyzer User s Programmer s Reference...
Страница 129: ...4 Mode Functions Undefined variable Primary ProductName Sequence Analyzer User s Programmer s Reference 129...
Страница 145: ...5 System Functions Undefined variable Primary ProductName Sequence Analyzer User s Programmer s Reference 145...
Страница 206: ...5 System Functions System 206 Sequence Analyzer User s Programmer s Reference...
Страница 214: ...6 List Sequence Measurements File File See File on page 146 214 Sequence Analyzer User s Programmer s Reference...
Страница 474: ...6 List Sequence Measurements Mode Mode See Mode on page 130 474 Sequence Analyzer User s Programmer s Reference...
Страница 478: ...6 List Sequence Measurements Print Print See Print on page 151 478 Sequence Analyzer User s Programmer s Reference...
Страница 642: ...6 List Sequence Measurements System System See System on page 152 642 Sequence Analyzer User s Programmer s Reference...