4 program message structure, Program message structure -9, Ars 3.6.4 thr – KEPCO TMA 4882-27 User Manual

Page 35: Figure 3-2 is a

Advertising
background image

TMA 4882-27 021910

3-9

FIGURE 3-2. TREE DIAGRAM OF SCPI COMMANDS USED WITH TMA 4882-27 CONTROLLER

3.6.4

PROGRAM MESSAGE STRUCTURE

SCPI program messages consist of one or more message units ending with a terminator. The ter-
minator is not part of the syntax; it is defined by the way your programming language indicates
the end of a line. The message unit is a keyword consisting of a single command or query word
followed by a terminator (e.g., CURR?<newline> or TRIG<end-of-line>). The message unit may
include a data parameter after the keyword separated by a space; the parameter is usually
numeric (e.g., CURR 5<newline>), but may also be a string (e.g., OUTP ON<newline>). Figure
3-3 illustrates the message structure, showing how message units are combined. The following
subparagraphs explain each component of the message structure.

NOTE: An alternative to using the message structure for multiple messages defined in the fol-

lowing paragraphs is to send each command as a separate line. In this case each com-
mand must use the full syntax shown in Appendix B.

INITiate

[:IMMediate]
:CONTinuous

INSTrument

:CATalog
:NSELect
:SELect
:STATe

MEASure

:CURRent?
:VOLTage?

OUTPut

[:STATe]

[SOURce:]

VOLTage

[:LEVel]

[:IMMediate]
:TRIGgered

CURRent

[:LEVel]

[:IMMediate]
:TRIGgered

FUNCtion

:MODE

ROOT : (colon)

STATus

:OPERation

:CONDition?
:ENABle
[:EVENt]?

:PRESet
:QUEStionable

:CONDition?
:ENABle
[:EVENt]?
:INSTrument?

:ENB
:ISUM

:INSTrument1?

:ENB

:INSTrument2?

:ENB

SYSTem

:COMMunication

:GPIB:ADDRess
:SERial

:BAUD
:ECHO
:PACE
:PROM

:ERRor?

:CODE?

:ALL?

:LANGuage
:SET
:VERSion?

Advertising