KEPCO KLP Series Developers Guide, Rev 3 - Manual (Page 83)

KLP-DEV 041213
6-3
6.4.11 CALIBRATE SUBSYSTEM
CAL commands and queries are used to perform calibration of the unit via the control interface. These
commands must be issued in a specific sequence in order to properly calibrate the unit. To use these com-
mands, refer to Kepco’s website (www.kepcopower.com/drivers) and download the LabWindows/CVI Ver-
sion 5 driver for KLP. This file provides remote calibration capability and uses the following supported
commands and queries:
CAUTION: The CAL commands are provide for reference only. Use of these commands in any way, other
than in the supplied remote calibration application, may result in irrecoverable corruption of the
internal calibration files.
CAL:CEXT command
CAL:CGA command
CAL:CURR:LEV command
CAL:CURR[:DATA] command
CAL:DPOT command
CAL:SAVE command
CAL:STAT command and query
CAL:VEXT command
CAL:VGA command
CAL:VOLT:LEV command
CAL:VOLT[:DATA] command
CAL:ZERO command
6.5 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 (“newline” character). The message unit is a keyword consisting of a sin-
gle 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 sepa-
rated by a space; the parameter is usually numeric (e.g., CURR 5), but may also be a
string (e.g., OUTP ON). Figure 6-1 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.
6.5.1 KEYWORD
Keywords are instructions recognized by a decoder within the KLP, referred to as a “parser.”
Each keyword describes a command function; all keywords used by the KLP are listed in Figure
6-2.
Each keyword has a long form and a short form. For the long form the word is spelled out com-
pletely (e.g. STATUS, OUTPUT, VOLTAGE, and TRIGGER are long form keywords). For the
short form only the first three or four letters of the long form are used (e.g., STAT, VOLT, OUTP,
and TRIG). The rules governing short form keywords are presented in Table 6-1.
You must use the rules above when using keywords. Using an arbitrary short form such as
ENABL for ENAB (ENABLE) or IMME for IMM (IMMEDIATE) will result in an error. Regardless
of which form chosen, you must include all the letters required by that form.
To identify the short form and long form in this manual, keywords are written in upper case let-
ters to represent the short form, followed by lower case letters indicating the long form (e.g.,