beautypg.com

4 program message structure, Program message structure -58, Figure 3-4 is a – KEPCO MBT Series User Manual

Page 96

background image

3-58

MBTSVC111609

FIGURE 3-4. TREE DIAGRAM OF SCPI COMMANDS USED WITH MBT-G POWER SUPPLIES

3.3.5.4

PROGRAM MESSAGE STRUCTURE

SCPI program messages (commands from controller to power supply) consist of one or more
message units ending in a message terminator. The message terminator is not part of the syntax; it
is defined by the way your programming language indicates the end of a line (such as a “new-
line” or “end-of-line” character). The message unit is a keyword consisting of a single command
or query word followed by a message terminator (e.g., CURR? or TRIGline>). The message unit may include a data parameter after the keyword separated by a space;
the parameter is usually numeric (e.g., CURR 5), but may also be a string (e.g.,
OUTP ONne>). Figure 3-5 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

[:SCALar]
: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?