Government
Tektronix operator,
Tektronix, Inc. hereby grant6 such permission for distribution
of
such documents to any
in the Metrology Data Interchange Data Base
that
copyright notice and ownership statement exactly a-& it appears
in the original, together with the Legend "Reproduded with
pemieeion,a
aeon% 1[
all copies
This permission has been approved by the Intellectual
Industry
Committee of Tektronix
ded
to GIDEP to grovide’the requested permission.
the request
Exchange
service and
GTDEP
of the original work include the entire
to grant permission to
Pro
ram (GPDEP) to reproduce
nstruction manuals,
P
user that is a full participant
of
GIDEP provided
and
a
copy of this memo may
the
geG&dy
Group Pat&t Counsel Group Patent C&nsal v
Copyright ’
Contents of this publication may not be reproduced in an’
form without the written permission of Tektronix, Inc.
Products of Tektronix, Inc. and its subsidiaries are coverer
by U.S. and foreign patents and/or pending patents.
TEKTRONIX. TEK, SCOPE-MOBILE, and an
registered trademarks of Tektronix, Inc. TELEQUIPMENT i!
a registered trademark of Tektronix U.K. Limited.
Printed in U.S.A. Specification and price change priviledgel
are reserved.
1988
Tektronix, Inc. All rights reservec
INSTRUMENT SERIAL NUMBERS
Each instrument has a serial number on a panel insert, tag
or stamped on the chassis. The first number or letter
designates the country of manufacture. The last five digits
of the serial number are assigned sequentially and arc
unique to each instrument. Those manufactured in the
United states have six unique digits. The country o
manufacture is identified as follows:
BOO0000 Tektronix, Inc., Beaverton. Oregon, USA
100000
200000
300000
700000
Tektronix Guernsey, Ltd., Channel Islands
Tektronix United Kingdom, Ltd., London
Sony/Tektronix, Japan
Tektronix Holland, NV, Heerenveen,
The Netherlands
First Printing-March 1988
CONTENTS
GPIB Command Reference
.....................
Page
l-l
Alphabetical GPIB Command Reference
Event Tables ................................
Character Charts
............................
..........
2-l
3-1
4-l
INTRODUCTION
This guide contains two references of the GPIB
ommands listed in Appendix A of the Programmers
deference Guide included with the 2440. The first reference,
GPIB Command Reference,” sorts the commands
ccording to type: Vertical Commands, Horizontal
:ommands, etc.; the second reference, “Alphabetical GPIB
Fommand Reference,” according to the alphabetical order
f the commands. Both lists omit the descriptions for the
ommands-consult Appendix A of the Programmers
leference Guide for those descriptions.
Also included in this guide are the Event Codes and their
escriptions. These are codes which the 2440 issues over
ie GPIB that represent errors, warnings, and other
iessages of interest to System Programmers.
At the end of the guide are two charts. The first chart
hows the character set the 2440 displays. The second
hart shows ASCII symbols and their GPIB equivalents.
,ee the Programmers Reference Guide for information on
ow to use these charts.
,~” ..- .-- .___ -.--_L--_Il_
GPIB Command Reference
GPIB Command
Reference
Throughout this Table (and the following Table), headers
md arguments are listed in a combination of bold upper
:ase and nonbold lower case letters. The instrument
accepts any abbreviated header or argument containing at
sast all the characters shown in bold upper case. Any
:haracters added to the abbreviated (upper case) version
nust be those shown in lower case. For a query, a question
nark (?) must immediately follow the header. Link
arguments shown in brackets ( [I) are defaults (don’t send
he brackets as part of the argument). In any command that
ras a default, omitting the link argument sets the default.
‘or example, ‘RUN ACQUIRE’ and ‘RUN’ are equivalent.
Some headers use numeric arguments in the ANSI
(3.42 standard format. This format states that there are
hree types of numbers; integers, reals, and reals with
exponents (these are called NRl, NR2, and NR3
espectively). Each type of number is composed of ASCII
ligits with the most significant digit sent first. Any of these
hree number types is acceptable whenever a numeric
argument is required. Here are some examples of each of
he three number types:
:NRl> 375,
:NR2> +12.589, 1.37592, - 00037.5
:NR3>
Sometimes in one of the argument columns of this table
<types> or <data src> appears and references a
ootnote at the bottom of the page. In this case, the
lrgument to use is any one of those in the referenced
ootnote.
Command Errors are issued when a GPIB *grammatical” error has been made. Check the spelling and
structure of the input strings. Set CER to ON to
receive SRQ’s when any of these events occurs. If
CER is OFF, the 2440 will not assert SRQ.
Code
108
109
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
Description
Checksum error in CURVE transfers.
Count = 0 or EOI set on byte count.
Symbol or number too long.
Invalid character or control character input.
EOI set on back slash.
Invalid number input.
EOI set on string character before ending quote.
Symbol not found.
Command or query argument is illegal in this
syntax.
Character should be a colon.
Valid symbol, but not a legal header.
Character should be a comma, a semicolon, or
EOI.
Too many query arguments.
Command only. May not be sent as a query.
Query only. May not be sent as a command.
EOI asserted before waveform was completed.
Incorrect word string input.
Number expected on incoming ascii waveform.
Comma expected on incoming ascii waveform.
Incoming ascii waveform has more than 1024
data points.
Illegal LLSET string.
PIB Pocket Guide 3-l
___. ..^_
-. ---
Event Tables
Execution Error Events
Execution errors are issued when a particular scope
setting doesn’t allow the current command to be exe-
cuted the way the user would like. Set EXR to ON
to receive SRQ’s when any of these events
occurs.
EXR is OFF, the 2440 will not assert SRQ.
If
Code
203
250
251
252
253
254
255
256
257
259
260
261
262
263
264
265
266
267
268
269
Description
I/O buffers full, output dumped.
Selected recall memory is unset.
Measurement requested on an empty reference
memory.
Waveform requested via GPIB is not valid or
available.
Too many numbers were sent in (stack overflow’
No Video Option installed when SETTV
commands issued.
Target selected for cursors not displayed.
Clear overload condition before changing to 50 S
coupling.
Waveform selected for reference source is not
valid.
No ADD or MULT on previously SAVEd
waveforms; ENVELOPE waveform invalid.
No cal commands allowed while front panel is
doing cal.
No sequence by that name to delete.
Can’t save sequence-out of memory.
Can’t send a partial waveform to an empty ref.
Not enough edges to extract the parameter.
Asked for rise time but no rising edge.
Asked for fall time but no falling edge.
Delay Measurement targets must have matching
Sec/Div settings.
One or more of the following conditions are not
satisfied:
BASE<PROXIMAL<MESIAL=zDlSTALsTOP,
BASE<MESIALP<TOP,
PROXIMAL>MIN and DISTALtMAX,
MIN<MESIAL2<MAX
Repet waveform not filled when measurement
requested.
3-2 GPIB Pocket Guic
Execution Error Events (cant)
Event Tables
Code
270 No measurements during live Roll-enter Save
mode first.
271 Measurement requested on a Delta Delay target
but B Horizontal and Delta Delay modes are not
on.
272 RMS measurement invalid due to 2440 internal
overflow.
275 Sequencer currently active-new sequence
commands not accepted.
Internal Errors are issued when something has hap-
pened to the hardware of the 2440 that the controller
might like to know about. Set INR to ON to receive
SRQ’s when any of these events occurs. tf INR is
OFF, the 2440 will not assert SRQ.
Cal execute command returns with FAIL.
A 50-R overload occurred. Input coupling
Description
Internal Errors
System Messages
System Messages are issued to inform the controller
of bus system management events. There is no way
to mask these events except by setting RQS to OFF.
The event 459 indicates that the 2440 is currently
asserting SRQ on the bus and the controller must
read the status byte out before reading the
event code.
Code Description
401 2440 was just powered on.
There is an SRQ pending.
459
iPlB Pocket Guide 3-3
Event Tables
User Request Events
User Request events are issued when any of the
bezel buttons on the 2440 front panel are pushed.
The MENUOFF command needs to be issued before
these events will be reported. This command allows
the user to monitor front panel responses (as well as
to clear the menu for writing custom text to the
screen when desired). Set USER to ON to receive
SRQ’s when any of these events occurs. If USER is
OFF, the 2440 will not assert SRQ.
Code Description
450 Menu key #l was pushed (leftmost)
451 Menu key #2 was pushed.
452 Menu key #3 was pushed.
453 Menu key #4 was pushed.
454 Menu key #5 was pushed (rightmost).
Probe Identify Events
Probe ldentifv events are reported by the 2440 when
the probe identify feature found on certain probes is
actuated. (You can replicate this action by grounding
the outer code ring to the inner shell on the front
panel input BNC.) Set PID to ON to receive SRQ’S
when any of these events occurs. If P/D is OFF, the
2440 will not assert SRQ.
Code
455 CHl probe identify was used.
456 CH2 probe identify was used.
457 EXTl probe identify was used.
458 EXT2 probe identify was used.
3-4 GPIB Pocket Guide
Description
Event Tables
Operation Complete Events
Operation Complete events are issued when the con-
troller needs to know when the 2440 has completed
a task. Set OPC to ON to receive SRQ’s when any
of these events occurs. If OPC is OFF, the 2440 will
not assert SRQ.
Code
461
Single Sequence has completed.
462
Save-On-Delta has detected a difference and
gone to Save.
463
A print or plot is complete.
464
Current cal command started with an EXECUTE
is done.
465 Step command is done.
Complete sequence is done.
466
467 Autoset search is complete.
Execution Warnings are issued when the command
received has been done, but the result might not be
what the user expected to see. Set EXW to ON to
receive SRQ’s when any of these events occurs, If
EXW is OFF, the 2440 will not assert SRQ.
Code Description
539 50 MHz bandwidth limit not available in 2440.
Bandwidth limit set to 100 MHz.
540 RMS measurements need at least 1 period.
541 Amplitude too small to do an accurate timing
measurement.
542 Measurement crossing points on Envelope may
be misplaced.Turn on Marks to see where
measurement was taken.
543 Too few points acquired to guarantee Histogram
accuracv for this measurement.
Description
Execution Warning
GPIB Pocket Guide 3-5
Event Tables
Execution Warning (cant)
Code
Waveform has points off the top of vertical
544
window.
Waveform has points off the bottom of vertical
545
window.
Waveform has points off the top and bottom of
546
vertical window.
Rising/Falling edge has too few points for optimal
547
accuracy.
Min/Max method should not be used for
548
Overshoot/Undershoot measurements.
549
Not enough samples taken to do accurate Time,
Freq, Period, Pulse Width, or Delay measurement.
Set Sec/Div faster if possible.
Only Delay 1 will be displayed if in Average.
550
Word Recognizer Probe is disconnected.
551
552
A and B Sec/Div are locked together.
More than 1024 binary points were sent; excess
553
discarded.
554
No absolute cursors in slope.
555
A trigger coupling and logsrc changed.
A trigger source change forced logsrc to off.
556
No Average in Roll. Acquire mode or A Trigger
557
mode changed.
No live vertical expansion unless averaging. Gain
558
changed.
560 Volts/Div value requested was rounded or limited.
561 Variable Volts/Div value requested was limited.
Vertical Position value requested was limited.
562
A or B trigger level was limited.
563
Trigger Holdoff value requested was limited.
564
Horizontal Position value requested was limited.
565
A or B Sec/Div setting requested was rounded.
566
Delay by Events events number was limited.
567
568 Delay by Time Delay value was limited.
Number of Envelopes requested was rounded.
569
Number of Averages requested was rounded.
570
572 Cursor reference value requested was rounded.
Description
3-6
GPIB Pocket Guide
Command Error Events
Event Tables
Code
Horizontal position value (XPOS) for cursors was
573
limited.
Vertical position value (YPOS) for cursors was
574
limited.
Intensity value requested was limited.
575
Line number of screen text message was limited.
576
578
The XINCR value was rounded or limited.
579
The PTOFF value was rounded or limited.
580
The YMULT value was rounded or limited.
Trigger position number requested was limited.
582
An ascii data point was rounded to fit into 127 to
583
-128.
Waveform data level value requested
584
Start or Stop number was changed.
585
588 The YOFF value was limited.
587 Extexp value requested was limited.
Hysteresis number requested was rounded.
588
Attribute number requested was rounded.
589
Description
was
Device Dependent Message
Device Dependent messages are issued when the
front panel user of the 2440 has done something that
the controller
might
want to know
about.
DEVDEP to ON to receive SRQ’s when any of these
events occurs. If DEVDEP is OFF, the 2440 will not
assert SRQ.
limited.
Set
Code Description
650 Waveform was requested from front panel.
Waveform transmission was aborted from front
MENUOFF command was executed or front panel
I” 1 Lz pushed.
iPlB Pocket Guide 3-7
Event Tables
Fatal Error
A Fatal Error is issued when something completely
unexpected happens inside the 2440. This normally
is caused by a hardware failure.
prevent this error from being reported except by
turning RQS to OFF.
Code Description
750 Fatal error.
There is no way to
3-8
GPIB Pocket Guid
_..-...- . ._.._ -, .---_- “”
Event Tables
2440
On the following two pages is the 2440 Status Byte
able. It lists each status byte code, along with the
istrument status indicated by each code, that can be
eturned when the EVEnts query is sent by the controller.
Status bytes
iPlB Pocket Guide 3-9
2440 Status Bytes
Title
Binarya
RQS Off
Idle
No Status To Report 000x 0000 0
Power On 010x 0001
Operation Complete
OROX
0010 2
User Request OROX 0011 3
Command Error OR1 x 0001 33
Execution Error ORlX 0010 34
internal Error OR1 x 0011 35
Execution Warning
a“R” is set to 1 if the GPIB and RQS are on; otherwise; it is 0.
“X” is the Busy Bit and will be set if the 2440 is busy at the time the status byte is read. Any
time the 2440 is doing something for which the OPC SRQ can be sent (calibration or self test,
single sequence, Save-On-Delta, or plotting) the bit will be sent true (1); otherwise, it
will be a 0.
Character Charts
ASCII and 2440 Character Charts
3B Pocket Guide
4-1
ASCII & GPIB CODE CHART
ASCII 81 GPIB CODE CHART
4-2
GPIB Pocket Guic
Loading...
+ hidden pages
You need points to download manuals.
1 point = 1 manual.
You can buy points or you can get point for every manual you upload.