YOKOGAWA TA520 User manual

IM 704310-12E
2nd Edition
Time Interval Analyzer
GP-IB Interface

iIM 704310-12E
Foreword Thank you for purchasing YOKOGAWA's TA520 Time Interval Analyzer.
This GP-IB Interface User's Manual contains useful information about the functions and
commands of the GP-IB interface. To ensure correct use of the GP-IB interface, please
read this manual thoroughly before operating it.
Keep the manual in a safe place for quick reference whenever a question arises.
The following manual is provided with this instrument in addition to this GP-IB Interface
User's Manual.
Manual Name Manual No. Description
TA520 User's Manual IM 704310-01E Describes all functions except for the
communications functions for GP-IB interface of
the instrument.
Notices • The contents of this manual are subject to change without prior notice as a result of
improvements in the instrument's performance and functions.
• Every effort has been made in the preparation of this manual to ensure the accuracy
of its contents. However, should you have any questions or find any errors, please
contact your nearest YOKOGAWA representative as listed on the back cover of this
manual.
• Copying or reproduction of all or any part of the contents of this manual without
YOKOGAWA's permission is strictly prohibited.
Trademarks • IBM PC/AT is a registered trademark of International Business Machines Corporation.
• Other product names are trademarks or registered trademarks of their respective
holders.
Revisions • 1st Edition: April 1999
• 2nd Edition: November 1999
LOCAL key
GP-IB connector
Disk No. HF09
2nd Edition:November 1999 (YK)
All Rights Reserved, Copyright © 1999 Yokogawa Electric Corporation

ii IM 704310-12E
How to Use this Manual
Structure of this Manual
This User's Manual consists of five chapters, an appendix and an index as described
below.
Chapter 1 Overview of the GP-IB Interface
Describes the functions and specifications of GP-IB.
Chapter 2 Before Programming
Describes formats used when sending a command.
Chapter 3 Commands
Describes each command.
Chapter 4 Status Report
Describes the status byte, various registers and queues.
Chapter 5 Sample Program
Describes a program example written for a IBM PC/AT series personal
computer written in Quick BASIC version 4.0/4.5.
Appendix Contains references including the ASCII character code table.
Index Provides an alphabetically ordered index.
Conventions Used in this Manual
Symbols used for Notes and Keys
Type Symbol Description
Unit k 1000 e.g.: 100 kHz
K 1024 e.g.: 128 KB (memory capacity)
Note Note Provides information that is necessary for proper operation of the instrument.
Symbols used in syntax descriptions
Symbols which are used in the syntax descriptions in Chapter 4 are shown below. These
symbols are referred to as BNF notation (Backus-Naur Form). For detailed information,
refer to pages 2-5 and 2-6.
Symbol Description Example Example
<> Defined value WINDow<x> <x>=1 to 16 WINDOW2
{} One of the options in is selected. MODE {AUTO|MANual} MODE AUTO
| Exclusive OR MODE {AUTO|MANual} MODE AUTO
[ ] Abbreviated :MEASure[:MODE]
... May be repeated

iiiIM 704310-12E
1
2
3
4
5
App
Index
Contents
Foreword............................................................................................................................................................. i
How to Use this Manual.............................................................................................................................ii
Chapter 1 Overview of the GP-IB Interface
1.1 Name of the Parts and Their Functions ....................................................................................1-1
1.2 Connecting the GP-IB Cable..................................................................................................... 1-2
1.3 GP-IB Interface Functions and Specifications .......................................................................... 1-3
1.4 Settings on the Main Unit .......................................................................................................... 1-5
1.5 Responses to Interface Messages............................................................................................ 1-6
Chapter 2 Before Programming
2.1 Messages.................................................................................................................................. 2-1
2.2 Commands................................................................................................................................ 2-3
2.3 Response .................................................................................................................................. 2-5
2.4 Data ..........................................................................................................................................2-5
2.5 Synchronization with the Controller .......................................................................................... 2-7
Chapter 3 Commands
3.1 Command Listing ......................................................................................................................3-1
3.2 ASCale Group ........................................................................................................................... 3-9
3.3 CALCulation Group ................................................................................................................. 3-10
3.4 COMMunicate Group .............................................................................................................. 3-20
3.5 DISPlay Group ........................................................................................................................ 3-21
3.6 FILE Group ............................................................................................................................. 3-25
3.7 HCOPy Group ......................................................................................................................... 3-28
3.8 HHIStogram Group ................................................................................................................. 3-30
3.9 INPut Group ............................................................................................................................ 3-36
3.10 MEASure Group...................................................................................................................... 3-39
3.11 MEMory Group........................................................................................................................ 3-40
3.12 RECall Group .......................................................................................................................... 3-41
3.13 SAMPle Group ........................................................................................................................ 3-42
3.14 SCSI Group............................................................................................................................. 3-46
3.15 SSTart Group .......................................................................................................................... 3-46
3.16 STARt Group........................................................................................................................... 3-46
3.17 STATus Group......................................................................................................................... 3-47
3.18 STOP Group ........................................................................................................................... 3-48
3.19 STORe Group ......................................................................................................................... 3-48
3.20 SYSTem Group ....................................................................................................................... 3-48
3.21 THIStogram Group.................................................................................................................. 3-50
3.22 TVARiation Group ................................................................................................................... 3-56
3.23 UNIT Group.............................................................................................................................3-58
3.24 Common Command Group ..................................................................................................... 3-59

iv IM 704310-12E
1.3 GP-IB Interface Functions and Specifications
Chapter 4 Status Report
4.1 Overview of the Status Report ..................................................................................................4-1
4.2 Status Byte................................................................................................................................ 4-2
4.3 Standard Event Register ........................................................................................................... 4-3
4.4 Extended Event Register ..........................................................................................................4-4
4.5 Output Queue and Error Queue................................................................................................ 4-5
Chapter 5 Sample Program
5.1 Before Writing the Program.......................................................................................................5-1
5.2 Setup Example.......................................................................................................................... 5-1
5.3 Example of Statistical Data Output ...........................................................................................5-2
5.4 Example of Output in BINARY Format...................................................................................... 5-4
5.5 Example of Output in ASCII Format .......................................................................................... 5-5
Appendix
Appendix 1 ASCII Character Code...................................................................................................App-1
Appendix 2 Error Messages .............................................................................................................App-2
Appendix 3 Overview of IEEE 488.2-1992 .......................................................................................App-5
Index........................................................................................................................................................... Index-1

Overview of the GP-IB Interface
1-1IM 704310-12E
1
Chapter 1 Overview of the GP-IB Interface
1.1 Name of the Parts and Their Functions
Front Panel
CH
AB
CH
EXT ARM/GATE IN INHIBIT IN
The word [Remote]
appears in the top right
corner of the screen
when the instrument is in
the remote mode.
LOCAL key
(SHIFT+AUTO SCALE)
key
Press to cancel the
remote mode and enter
the local mode in which
the panel keys are
enabled. UTILITY key
Press to enter the
communication settings.
Remote
Rear Panel
GP-IB connector
The connector used for
connecting the controller
(PC) with the GP-IB
cable.
1.1 Name of the Parts and Their Functions
LOCAL key
GP-IB connector

1-2 IM 704310-12E
1.2 Connecting the GP-IB Cable
GP-IB Cable The GP-IB connector on the rear panel is a 24-pin connector that conforms to IEEE
Standard 488-1978. Use a GP-IB cable that also conforms to IEEE Standard 488-1978.
Connection Method
Connect the GP-IB cable as shown.
GP-IB connector
GP-IB cable
Points to Note • Be sure to tighten the screws on the GP-IB cable connector firmly.
• The instrument can be connected to more than one item of equipment (such as a
personal computer). However, it is not possible to connect more than 15 items of
equipment (including the controller) to a single bus.
• If you connect the instrument to more than one other item of equipment, make sure
that a different address is used for each item.
• Each connecting cable must be 2 m or less in length.
• The total length of all the cables must not exceed 20 m.
• While communications are in progress, more than two-thirds of the connected items of
equipment must be turned ON.
• When connecting more than one item of equipment, connect the items so that the
connection route forms a star or linear configuration. Loop or parallel wiring is not
allowed.
1.2 Connecting the GP-IB Cable

Overview of the GP-IB Interface
1-3IM 704310-12E
1
1.3 GP-IB Interface Functions and Specifications
GP-IB Interface Functions
Listener function
• Allows you to make the same settings which you can make using the panel keys on
the instrument (except for the power ON/OFF and GP-IB communications settings).
• Receives commands from a controller requesting output of set-up and waveform data.
• Also receives status report commands.
Talker function
Outputs set-up and waveform data.
Note
The listen-only, talk-only, and controller functions are not available on this instrument.
Switching between Remote and Local Modes
Switching from Local to Remote Mode
Remote mode is activated when a REN (Remote Enable) message is received from a
controller while local mode is active.
• The word [Remote] appears in the top right corner of the screen (see page 1-1).
• All front panel keys except the LOCAL key are now inoperative.
• Settings that were entered in local mode are retained.
Switching from Remote to Local Mode
Pressing the Local key in remote mode puts the instrument in local mode. However, this
is not possible if Local Lockout has been set by the controller (page 1-7).
• The word [Remote] in the top right corner of the screen disappears (see page 1-1).
• All front panel keys are operative.
• Settings that were entered in remote mode are retained.
1.3 GP-IB Interface Functions and Specifications

1-4 IM 704310-12E
GP-IB Interface Specifications
Electrical and mechanical specifications: Conforms to IEEE Standard 488-1978.
Mechanical specifications : Refer to the table below.
Code : ISO (ASCII) code
Mode : Addressable mode/Talk-only mode (switched
automatically)
Address setting : Addresses 0 to 30 can be selected from the
GP-IB setting menu, which is displayed when
you press [GP-IB] soft key after having pressed
the UTILITY key.
Remote mode clear : Remote mode can be cleared by pressing the
LOCAL key (SHIFT+AUTO SCALE key).
However, this is not possible if Local Lockout
has been set by the controller.
Mechanical Specifications
Function Subset Name Description
Source handshaking SH1 Full source handshaking capability
Acceptorhandshaking AH1 Fullacceptorhandshakingcapability
Talker T6 Basic talkercapability,serialpolling,
untalk on MLA(My Listen Address), No
talk-only capability
Listener L4 Basiclistenercapability,unlistenonMTA
(My Talk Address), no listen-only capability
Servicerequest SR1 Fullservicerequestcapability
Remotelocal RL1 Fullremote/localcapability
Parallelpoll PP0 Noparallel pollingcapability
Deviceclear DC1 Fulldeviceclearcapability
Devicetrigger DT0 Nodevicetriggercapability
Controller C0 Nocontrollerfunction
Electricalcharacteristic E1 Opencollector
1.3 GP-IB Interface Functions and Specifications

Overview of the GP-IB Interface
1-5IM 704310-12E
1
1.4 Settings on the Main Unit
1.4 Settings on the Main Unit
Procedure
1. Press the UTILITY key to display the Utility menu.
2. Press the [GP-IB] soft key to display the GP-IB menu.
ESC
3. Use the rotary knob to select the address.
ESC
Explanation
Selecting the address
Devices that are connected with the GP-IB cable have their own unique address within
the GP-IB system. This address is used to identify the different devices. Therefore,
when connecting the instrument to another device such as a PC, the address of the
instrument must be selected. The address is selected from the following range. The
default setting is [1].
Selectable range: 0 to 30

1-6 IM 704310-12E
1.5 Responses to Interface Messages
1.5 Responses to Interface Messages
What is an Interface Message?
An interface message (also called an interface command or bus command) is issued by
the controller. Interface messages are classified as follows.
Uni-line messages
Messages are transferred through a single control line. The following three types of uni-
line message are available.
• IFC (Interface Clear)
• REN (Remote Enable)
• IDY (Identify)
Multi-line messages
Eight data lines are used to transmit a message. Multi-line messages are classified as
follows.
Address commands
Valid when a piece of equipment is designated as a listener or a talker. The following
five address commands are available.
• Commands valid for pieces of equipment designated as listeners
GTL (Go To Local)
SDC (Selected Device Clear)
PPC (Parallel Poll Configure)
GET (Group Execute Trigger)
• Command valid for pieces of equipment designated as talkers
TCT (Take Control)
Universal commands
Valid for any item of equipment, irrespective of whether the item is designated as a
listener or a talker. The following five universal commands are available.
LLO (Local Lockout)
DCL (Device Clear)
PPU (Parallel Poll Unconfigure)
SPE (Serial Poll Enable)
SPD (Serial Poll Disable)
In addition to the above commands, a listener address, talker address or secondary
command can be sent in an interface message.
Differences between SDC and DCL
The SDC command is an address command and requires that both the talker and
listener be designated. DCL is a universal command and does not require that the
talker and listener be designated. Hence, SDC is used for specific items of equipment,
while DCL can be used for any equipment connected to the communications bus.

Overview of the GP-IB Interface
1-7IM 704310-12E
1
Response to Interface Message
Response to a uni-line message
• IFC (Interface Clear)
Clears the talker and listener. Stops output if data is being output.
• REN (Remote Enable)
Switches between remote and local modes.
• IDY (Identify) is not supported.
Responses to a multi-line message (address command)
• GTL (Go To Local)
Switches to local mode.
• SDC (Selected Device Clear)
Clears the program message (command) which is currently being output. Also empties
the output queue (page 4-5).
• GET (Group Execute Trigger)
Same as *TRG.
•COMMunicate:WAIT will be stopped immediately.
• PPC (Parallel Poll Configure) and TCT (Take Control) are not supported.
Responses to a multi-line message (universal command)
• LLO (Local Lockout)
Invalidates the LOCAL key on the front panel, disabling switching to local mode.
• DCL (Device Clear)
Same as SDC.
• SPE (Serial Poll Enable)
Sets the talker function to serial poll mode for all equipment connected to the
communications bus. The controller polls equipment sequentially.
• SPD (Serial Poll Disable)
Clears serial poll mode as the talker function for all equipment connected to the
communications bus.
• PPU (Parallel Poll Unconfigure) is not supported.
1.5 Responses to Interface Messages

Before Programming
2-1IM 704310-12E
2
Chapter 2 Before Programming
2.1 Messages
Messages
Blocksofmessagedataaretransferredbetweenthe
controllerandthisinstrumentduringcommunications.
Messagessentfromthecontrollertothisinstrument
arecalledprogrammessages,andmessagessent
backfromthisinstrumenttothecontrollerarecalled
responsemessages.
Ifaprogrammessagecontainsaquerycommand,i.e.
acommandwhichrequestsaresponse,this
instrumentreturnsaresponsemessage.Asingle
responsemessageisalwaysreturnedinreplytoa
programmessage.
Program Messages
Asexplainedabove,thedata(message)sentfrom the
controllertothisinstrumentiscalledaprogram
message.Theformatofaprogrammessageisshown
below.
<PMT>
;
Program message unit
<Program message unit>
Aprogrammessageconsistsofzeroormoreprogram
messageunits;eachunitcorrespondstoone
command.Thisinstrumentexecutescommandsone
byoneaccordingtotheorderinwhichthey are
received.
Programmessageunitsaredelimitedby a ";".
Foradescriptionoftheformatoftheprogram
messageunit,refertotheexplanationgivenfurther
below.
Example
Unit Unit
:MEASURE:MODE HHISTOGRAM;FUNCTION PERIOD,A<PMT>
<PMT>
PMTisaterminatorusedtoterminateeachprogram
message.Thefollowingthreetypesofterminatorare
available.
NL (NewLine) : Sameas LF(Line Feed). ASCII code
"0AH"isused.
^END : ENDmessagedefined inIEEE488.1.
(EOIsignal)
(Thedatabyte sentwith an END
messagewillbethefinalitemofthe
programmessageunit.)
NL^END : NLwithanEND messageattached
(NLisnotincludedintheprogram
message.)
Program message unit format
Theformatofaprogrammessageunitisshownbelow.
,
<Program header>
<Program data>Space
<Program header>
Aprogramheaderisusedtoindicatethecommand
type.Fordetails,refer topage2-3.
<Program data>
Ifcertainconditionsarerequiredfortheexecutionofa
command,programdatamustbeadded.Programdata
mustbeseparatedfrom theheaderby a space(ASCII
code "20H").If multipleitemsofprogramdata are
included,theymustbeseparated bya ","(comma).
Fordetails,refer to page2-5.
Example
Header Data
:SAMPLE:GATE:MODE EVENT<PMT>
2.1 Messages

2-2 IM 704310-12E
Response Messages
Thedatareturnedbythisinstrumenttothecontrolleris
calledaresponsemessage.Theformatofa response
messageisshownbelow.
<RMT>
;
<Response message unit>
<Responsemessageunits>
Aresponsemessageconsistsofoneormore
responsemessageunits:eachresponsemessageunit
correspondstooneresponse.
Responsemessageunitsaredelimitedbya[ ;].
Fortheresponsemessageformat,refertothenext
page.
Example
Unit Unit
:SAMPLE:GATE:MODE EXTERNAL;POLARITY POSITIVE<RMT>
<RMT>
RMTistheterminatorusedforeveryresponse
message.Onlyonetypeofresponsemessageis
available; NL^END.
Response message unit format
Theformatofaprogrammessageunitisshownbelow.
,
<Rsps. header> <Response data>
Space
<Response header>
Aresponseheadersometimesprecedestheresponse
data.Responsedatamustbeseparatedfromthe
headerbya space.Fordetails, referto page2-4.
<Response data>
Responsedataisusedtodefinearesponse.Ifmultiple
itemsofresponsedataareused,theymustbe
separatedbya "," (comma). Fordetails,refer to page
2-5.
Example
Data Header Data
500.0E-03<RMT> :SAMPLE:INTERVAL MINIMUM<RMT>
Ifaprogrammessagecontainsmorethanonequery,
responsesaremadeinthesame orderasthequeries.
Normally,eachqueryreturnsonlyoneresponse
messageunit,buttherearesomequerieswhichreturn
morethanoneresponsemessageunit.Thefirst
responsemessageunitalwaysrespondstothefirst
query,butitisnotalwaystruethatthe 'n'thunit
alwaysrespondstothe 'n'thquery.Therefore,ifyou
wanttomakesurethat aresponseismade toeach
query,theprogrammessagemustbedividedupinto
individualmessages.
Points to Note concerning Message Transmission
• Itisalwayspossibletosendaprogrammessageif
thepreviousmessagewhichwassentdidnot
containanyqueries.
• Ifthepreviousmessagecontainedaquery,itisnot
possibletosendanotherprogrammessageuntila
responsemessagehasbeenreceived.Anerrorwill
occurifaprogrammessageissentbeforea
responsemessagehasbeenreceivedinitsentirety.
Aresponsemessagewhichhasnotbeenreceived
willbediscarded.
• Ifanattemptismadebythe controllertoreceivea
responsemessage,evenifthereitnoresponse
message,anerrorwilloccur.Anerrorwillalsooccur
ifthecontrollermakesanattempttoreceivea
responsemessagebeforetransmissionofa
programmessagehasbeencompleted.
• Ifaprogrammessageofmorethanone unitissent
andsomeoftheunitsareincomplete,this
instrumentreceivesprogrammessageunitswhich
theinstrumentthinkscompleteandattemptsto
executethem.However,theseattemptsmaynot
alwaysbesuccessfulanda responsemaynot
alwaysbereturned,eveniftheprogrammessage
containsqueries.
Dead Lock
Thisinstrumenthasabuffermemoryinwhichboth
programandresponsemessagesof1024bytesor
morecanbestored.(Thenumberofbytesavailable
willvarydependingontheoperatingstateofthe
instrument.)Ifbothbuffermemoriesbecomefullatthe
sametime,thisinstrumentbecomesinoperative.This
stateiscalleddeadlock.Inthis case,operationcanbe
resumedbydiscardingtheresponsemessage.
Nodeadlockwilloccur,ifthesizeoftheprogram
messageincludingthePMTiskeptbelow1024 bytes.
Furthermore,nodeadlockwilloccuriftheprogram
messagedoesnotcontainaquery.
2.1 Messages

Before Programming
2-3IM 704310-12E
2
2.2 Commands
Commands
Therearethreetypesofcommand(programheader)
whichcanbesentfromthecontrollertothis
instrument.Theydifferintheformatoftheirprogram
headers.
Theyare
• Commoncommandheader
• Compoundheader
• Simpleheader
Common Command Header
Commandsdefinedin IEEE488.2-1992are called
commoncommands.Theheaderformatofacommon
commandisshownbelow.Anasterisk( *)mustalways
beattachedtothebeginningofacommand.
<Mnemonic>
?
*
Anexampleofacommoncommand
*CLS
Compound Header
Commandsdesignedtobeusedonlywiththis
instrumentareclassifiedandarrangedinahierarchy
accordingtotheirfunction.Theformatofacompound
headerisillustratedbelow.Acolon( :)mustbeused
whenspecifyingalower-levelheader.
:
<Mnemonic>
?:
Anexampleofacompoundheader
MEASURE:FUNCTION
Simple Header
Thesecommands(headers)arefunctionally
independentofeachotherandarenotarranged
hierarchically.Theformatofasimpleheaderisshown
below.
<Mnemonic>
?:
Anexampleofasimpleheader
START
Note
A mnemonic is a character string made up of alphanumeric
characters.
When Concatenating Commands
Command Group
Acommandgroupisagroupofcommandswhichhave
thesamecompoundheader.Acommandgroupmay
containsub-groups.
Example Commandsrelatingtothesampling
SAMPLE? SAMPLE:GATE?
SAMPLE:GATE:MODE SAMPLE:GATE:EVENTSIZE
SAMPLE:GATE:POLARITY SAMPLE:GATE:TIME
SAMPLE:INTERVAL SAMPLE:ARMING:SOURCE
SAMPLE:ARMING:DELAY:MODE
SAMPLE:ARMING:DELAY:TIME
When Concatenating Commands of the Same
Group
Thisinstrumentstoresthehierarchicallevelofthe
commandwhichiscurrentlybeingexecuted,and
performsanalysisontheassumptionthatthenext
commandtobesentwillalsobelongtothesamelevel.
Therefore,itispossibletoomittheheaderifthe
commandsbelongtothesamegroup.
Example INPUT:ACHANNEL:COUPLING AC;IMPEDANCE
I50<PMT>
When Concatenating Commands of Different
Groups
Acolon( :)must beincludedbeforetheheaderof a
command,ifthecommanddoesnotbelongtothe
samegroupastheprecedingcommand.
Example MEASURE:MODE TSTAMP;:DISPLAY:ITEM
LIST<PMT>
When Concatenating Simple Headers
Whenyoutypeinasimpleheaderafter another
command,youmustincludeacolon( :)beforethe
simpleheader.
Example MEASURE:MODE TSTAMP;:START<PMT>
When Concatenating Common Commands
Commoncommandsdefinedin IEEE488.2-1992are
independentofhierarchicallevel.Thus,itisnot
necessarytoaddacolon( :)beforeacommon
command.
Example MEASURE:MODE TSTAMP;*CLS;FUNCTION
DUTY,A<PMT>
2.2 Commands

2-4 IM 704310-12E
When Separating Commands with <PMT>
Ifaterminatorisusedtoseparatetwocommands,
eachcommandisaseparatemessage. Therefore,the
commonheadermustbetypedinforeachcommand
evenwhencommandsofthesamecommandgroup
arebeingconcatenated.
Example MEASURE:MODE TSTAMP<PMT>MEASURE:
FUNCTION DUTY,A<PMT>
Upper-level Query
Anupper-levelqueryisacompoundheadertowhicha
questionmarkisappended.Executionofanupper-
levelqueryallowsallagroup 'ssettingstobeoutputat
once.Somequerygroupscomprisingmorethanthree
hierarchicallevelscanoutputalltheirlowerlevel
settings.
Example MEASURE?<PMT>→:MEASURE:
MODE HHISTOGRAM;FUNCTION PERIOD,A;
SLOPE RISE
Inreplyto a query,aresponse canbereturned asa
programmessagetothisinstrument.Transmittinga
responsecanrestorethesettingsmadewhenthe
querywasexecuted.However,someupper-level
querieswillnotreturnset-updatawhichisnotcurrently
inuse.Notethatnot allagroup 'sinformationwill
necessarilybesentoutasaresponse.
Header Interpretation Rules
Thisinstrumentinterpretstheheaderreceived
accordingtothefollowingrules.
• Mnemonicsarenotcasesensitive.
Example "MEASure" canalso be writtenas
"measure" or "Measure".
• Thelower-casepartofa headercanbeomitted.
Example "MEASure" canalso be writtenas
"MEASU" or "MEAS".
• Iftheheaderendswithaquestion mark,the
commandisaquery.Itisnotpossibletoomitthe
questionmark.
Example "MEASure?" cannotbeabbreviated to
anythingshorterthan "MEAS?".
• Ifthe "x"atthe endofamnemonic isomitted,it is
assumedtobe "1".
Example If "WINDow<x>" iswrittenas "WIND", this
represents "WINDow1".
• Anypartofacommandenclosed by[]canbe
omitted.
Example CALCulation[:WINDow1]:AVERage? can
bewritten as "CALCulation:AVERage?".
However,apartenclosedby[]cannot beomittedifis
locatedattheendofanupper-levelquery.
2.2 Commands

Before Programming
2-5IM 704310-12E
2
2.3 Response
Onreceivingaqueryfromthecontroller,this
instrumentreturnsaresponsemessagetothe
controller.Aresponsemessageissentinoneofthe
followingtwoforms.
• Responseconsistingofaheaderanddata
Ifthequerycan beusedasa programmessage
withoutanychange,acommandheaderisattached
tothequery,whichisthenreturned.
Example SAMPLE:GATE:MODE?<PMT>→:
SAMPLE:GATE:MODE EVENT<RMT>
• Responseconsistingofdataonly
Ifthequerycannotbeused asaprogrammessage
unlesschangesaremadetoit (i.e.itisaquery-only
command),noheaderisattachedandonlythedata
isreturned.Somequery-onlycommandscanbe
returnedafteraheaderisattachedtothem.
Example STATUS:ERROR?<PMT>→
0,"NO ERROR"<RMT>
When returning a response without a header
Itispossibletoremovetheheaderfromaresponse
consistingofaheaderanddata.The
"COMMunicate:HEADer" commandis used todo this.
Abbreviated form
Normally,thelower-casepartisremovedfroma
responseheaderbeforetheresponseisreturnedto
thecontroller.Naturally,thefullformoftheheadercan
alsobe used.For this,the "COMMunicate:VERBose"
commandisused.Thepartenclosedby[] isalso
omittedintheabbreviatedform.
2.4 Data
Data
Adatasectioncomesaftertheheader.A spacemust
beincludedbetweenthe headerandthedata.The
datacontainsconditionsandvalues.Dataisclassified
asbelow.
Data Description
<Decimal> Value expressed as a decimal number
(Example: CH2's probe attenuation
→SAMPle:GATE:EVENtsize 100)
<Voltage><Time> Physical value
(Example: Gate time
<Percent> →SAMPle:GATE:TIME 1US)
<Register> Register value expressed as either binary, octal, decimal
or hexadecimal
(Example: Extended event register value
→STATus:EESE #HFE)
<Character data> Specified character string (mnemonic). Can be selected
from { }
(Example: Selecting of gate mode
→SAMPle:GATE:MODE {EVENt|TIME|EXTernal})
<Boolean> Indicates ON/OFF. Set to ON, OFF or value
(Example: Panorama display ON
→DISPlay:PANorama:STATe ON)
<Character string data>Arbitrary character string
(Example: File name to be saved
→FILE:DELete:SETup "SETUP_1")
<Block data> Arbitrary 8-bit data
(Example: Response to acquired waveform data
→#6000010ABCDEFGHIJ)
<Decimal>
<<Decimal>indicatesavalueexpressedasa decimal
number,asshowninthetablebelow.Decimalvalues
aregivenin theNR form specifiedin ANSIX3.42-
1975.
Symbol Description Example
<NR1> Integer 125 –1 +100000
<NR2> Fixed point number 125.0 –.90 +001.
<NR3> Floating point number 125.0E+0 –9E–1 +.1E4
<NRf> Any of the forms <NR1> to <NR3> is allowed.
• Decimalvalueswhicharesentfromthecontrollerto
thisinstrumentcanbesentinanyoftheformsto
<NR3>.In thiscase,<NRf> appears.
• Forresponsemessageswhicharereturnedfrom
thisinstrumenttothecontroller,theform(<NR1>to
<NR3>tobeused) isdeterminedby thequery.The
sameformisused,irrespectiveofwhetherthevalue
islargeorsmall.
• Inthe case of<NR3>, the "+"after the "E"canbe
omitted,butthe "–"cannot.
• Ifavalueoutsidethesettingrange isentered,the
valuewillbenormalizedsothatitisjustinsidethe
range.
• Ifthevaluehasmorethanthesignificantnumberof
digits,thevaluewillberounded.
2.3 Response/2.4 Data

2-6 IM 704310-12E
<Voltage>, <Time>, <Percent>
<Voltage>,<Time>and<Percent>indicatedecimal
valueswhichhavephysicalsignificance.<Multiplier>
or<Unit>can beattached to<NRf>.They canbe
enteredinanyofthefollowingforms.
Form Example
<NRf><Multiplier><Unit> 5MV
<NRf><Unit> 5E-3V
<NRf><Multiplier> 5M
<NRf> 5E-3
<Multiplier>
Multiplierswhichcanbeusedareshownbelow.
Symbol Word Description
EX Exa 1018
PE Peta 1015
T Tera 1012
GGiga 10
9
MA Mega 106
K Kilo 103
M Mili 10-3
U Micro 10-6
N Nano 10-9
P Pico 10-12
F Femto 10-15
A Atto 10-18
<Unit>
Unitswhichcanbeusedareshownbelow.
Symbol Word Description
VVolt Voltage
SSecond Time
PCT Percent Percent
• <Multiplier>and<Unit>arenotcasesensitive.
• [U]isusedtoindicate[ µ].
• [MA]isusedforMega(M)todistinguishitfromMili.
• Ifboth<Multiplier>and<Unit>areomitted,the
defaultunitwillbeused.
• Responsemessagesarealwaysexpressedin
<NR3>form.Neither<Multiplier>nor<Unit>is
used,thereforethedefaultunit isused.
<Register>
<Register>indicatesaninteger,andcanbeexpressed
inhexadecimal,octalorbinaryaswell asasadecimal
number.<Register>isusedwheneach bitofavalue
hasaparticularmeaning.<Register>isexpressedin
oneofthefollowingforms.
Form Example
<NRf> 1
#H<Hexadecimal value made up of the digits 0 to 9, and A to F> #H0F
#Q<Octal value made up of the digits 0 to 7> #q777
#B<Binary value made up of the digits 0 and 1> #B001100
• <Register>isnotcasesensitive.
• Responsemessagesarealwaysexpressedas
<NR1>.
<Character Data>
<Characterdata>isaspecifiedstringofcharacterdata
(amnemonic).Itismainlyusedtoindicate options,and
ischosenfromthecharacterstringsgivenin{}.For
interpretationrules,referto "HeaderInterpretation
Rules"onpage 2-4.
Form Example
{EVENt|TIME|EXTernal} EVENt
• Aswith aheader, the "COMMunicate:VERBose"
commandcanbeusedtoreturnaresponse
messageinitsfullform.Alternatively,the
abbreviatedformcanbeused.
• The "COMMunicate:HEADer" commanddoesnot
affect<characterdata>.
<Boolean>
<Boolean>isdatawhichindicates ONorOFF,andis
expressedinoneofthefollowingforms.
Form Example
{ON|OFF|<NRf>} ON OFF 1 0
• When<Boolean>isexpressed in<NRf>form,OFF
isselectediftheroundedintegervalue is[0]andON
isselectediftheroundedintegeris[Not0].
• Aresponsemessageisalways [1]ifthevalueis ON
and[0]if itis OFF.
2.4 Data

Before Programming
2-7IM 704310-12E
2
<Character String Data>
<Characterstringdata>isnot aspecifiedcharacter
stringlike<Characterdata>.Itisanarbitrarycharacter
string.Acharacterstringmustbeenclosedinsingle
quotationmarks( ')ordoublequotationmarks( ").
Form Example
<Character string data> 'ABC' "IEEE488.2-1987"
• Responsemessagesarealwaysenclosedindouble
quotationmarks.
• Ifacharacterstringcontainsadoublequotation
mark("),thedoublequotationmarkwillbereplaced
bytwoconcatenateddoublequotationmarks( "").
Thisrulealsoappliestoasinglequotationmark
withinacharacterstring.
• <Characterstringdata>isanarbitrarycharacter
string,thereforethisinstrumentassumesthatthe
remainingprogrammessageunitsarepartofthe
characterstringifnosingle( ')ordoublequotation
mark(")isencountered.Asaresult, noerrorwillbe
detectedifaquotationmarkisomitted.
<Block data>
<Blockdata>isarbitrary8-bitdata.<Blockdata>is
onlyusedforresponsemessages.Response
messagesareexpressedinthefollowingform.
Form Example
#8<8-digit decimal value><Data byte string> #8000010ABCDEFGHIJ
•#8
Indicatesthatthedatais<Blockdata>.
• <6-digitdecimalvalue>
Indicatesthenumber of bytesofdata. ( 000010=10
bytes)
• <Databytestring>
Theactual data.( ABCDEFGHIJ)
• Dataiscomprisedof 8-bitvalues(0to 255).This
meansthattheASCIIcode[0AH],whichstandsfor
[NL],canalso beacode usedfordata. Hence,care
mustbetakenwhenprogrammingthecontroller.
2.5 Synchronization with the
Controller
OntheTA520,therearenooverlapcommands which
permittheexecutionofthenextcommandbeforethe
executionofthepreviouscommandcompletes. If
multiplecommandsaresentsequentially,the
executionofthenextcommandishelduntilthe
executionofthepreviouscommandcompletes.
How to Achieve Synchronization
Synchronizationissometimesrequiredforreasons
otherthancommunicationsrelatedreasons,suchas
theactivationofatrigger.
Forexample,iftheprogrammessage(see below)is
transmittedtomakeaninquiryaboutthedatawhichis
acquiredduringsinglemeasurement,the
"MEMory:SEND?" commandwillbe executedwhether
acquisitionhasbeencompletedornot,causinga
commandexecutionerror.
:SSTart;:MEMory:SEND?<PMT>
Inthiscase,synchronizationwiththetimeatwhich
acquisitioniscompletedmustbeaccomplished,as
shownbelow.
Using STATus:CONDition? query
A "STATus:CONDition?" queryis usedto make an
inquiryaboutthecontentsoftheconditionregister
(page4-4). Itispossibletojudgewhetheracquisition
isinprogressornotbyreadingbit0ofthecondition
register. Themeasureddata is effectiveifbit 0is "1".
Ifitis "0",acquisitionisinprogress,thusthe
measureddataisnoteffective.
Example :SSTart<PMT>
STATus:CONDition?<PMT>
(Returnstothepreviousstatusifbit0is
foundtobe[1]whentheresponseis
decoded.)
MEMory:SEND?<PMT>
A "MEMory:SEND?" querywillnot beexecuteduntil bit
0oftheconditionregisterhasbeensetto[ 1].
2.4 Data/2.5 Synchronization with the Controller

2-8 IM 704310-12E
Using the extended event register
Changesintheconditionregisterarereflectedinthe
extendedeventregister(page4-4).
Example STATus:FILTer1 RISE;:STATus:EESE 1;
EESR?;*SRE 8;SSTart<PMT>
(Servicerequestisawaited.)
MEMory:SEND?<PMT>
"STATus:FILTer1 RISE" indicatesthatthe transitfilter
issetso thatbit0 ( FILTer1)oftheextended registeris
setto "1" whenbit0oftheconditionregister is
changedfrom[ 0]to [ 1].
"STATus:EESE 1" isa commandused toreflect the
statusofonlybit0oftheextendedeventregisterinthe
statusbyte.
"STATus:EESR?" isusedto clearthe extendedevent
register.
The "*SRE" commandisused togeneratea service
requestcausedbytheextendedeventregisteronly.
"MEMory:SEND?" willnotbe executeduntila service
requestisgenerated.
Using the COMMunicate:WAIT command
The "COMMunicate:WAIT" commandhalts
communicationsuntilaspecificeventisgenerated.
Example STATus:FILTer1 RISE;:STATus:EESR?;
SSTart<PMT>
(Responseto STATus:EESR? isdecoded.)
COMMunicate:WAIT 1;:MEMory:
SEND?<PMT>
Fora descriptionof "STATus:FILTer1 RISE" and
"STATus:EESR?",referto "Usingthe extendedevent
register "onthispage.
"COMMunicate:WAIT 1" meansthatcommunications is
halteduntilbit0oftheextendedeventregisterissetto
[1].
"MEMory:SEND?" willnotbe executeduntil bit0of the
extendedeventregisterissetto[ 1].
2.5 Synchronization with the Controller