beautypg.com

2 other required commands, 3 other useful commands, 4 optional commands – KEPCO BIT 4886 Operator Manual User Manual

Page 51: 6 status subsystem, 7 system subsystem, 4 program message structure, Other required commands -17, Other useful commands -17, Optional commands -17, Status subsystem -17

background image

BIT 4886 120413

4-17

4.6.3.5.2 OTHER REQUIRED COMMANDS

VOLT:MODE LIST (PAR. B.59) or CURR:MODE LIST (PAR. B.50). These commands start the
list and VOLT:MODE FIX (PAR. B.59) or CURR:MODE FIX (PAR. B.50) stop the list. LIST com-
mands are not accepted while a list is running. If LIST:COUNT is between 1 and 255, when the
count decrements to 0, the list stops and the unit automatically moves to VOLT:MODE FIXED or
CURR:MODE FIXED state. To execute the list again, either VOLT:MODE LIST or CURR:MODE
LIST must be sent again.

4.6.3.5.3 OTHER USEFUL COMMANDS

LIST:COUNT:Skip (PAR. B.29). This command provides the ability to execute the initial points
only once whenever a list is run. It is used to set initial preconditions prior to running a repetitive
sequence.

LIST:DIR (PAR. B.34) This command changes the order of the list.

LIST:VOLT:POINTS? (PAR. B.47) or LIST:CURR:POINTS? (PAR. B.33) These queries return
the number of points in a list and provide a simple way to insure that all points entered were
properly processed and as intended.

4.6.3.5.4 OPTIONAL COMMANDS

Most commands have associated Queries (?) These are useful for troubleshooting/debugging
lists but are not needed in most cases.

The LIST:SEQ command is provided for backward compatibility. It is not recommended to be
used in any new designs as it may be eliminated at some point in the future.

4.6.3.6

STATUS SUBSYSTEM

This subsystem programs the power supply status register. The power supply has two groups of
status registers: Operation and Questionable. Each group consists of three registers: Condition,
Enable, and Event.

4.6.3.7

SYSTEM SUBSYSTEM

This subsystem is used to establish system settings Program Message Structure.

4.6.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 (required by Kepco power modules). The message
terminator is not part of the syntax; it is defined by the way your programming language indi-
cates the end of a line (such as a “newline” 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 TRIG). 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 ON). Figure 4-6 illustrates the message structure, showing
how message units are combined. The following subparagraphs explain each component of the
message structure.