beautypg.com

6 message terminator, 5 understanding the command structure, 6 program message syntax summary – KEPCO EL Series Electronic Load Operator Manual P/N 243-1295 Firmware Version 3.87 to 3.xx User Manual

Page 51: Message terminator -15, Understanding the command structure -15, Program message syntax summary -15, Gh 3.13.6)

background image

SERIES EL 022013

3-15

3.13.4.6 MESSAGE TERMINATOR

The message terminator defines the end of a message. One message terminator is permitted:

• new line () is defined as CR (Carriage Return, 0D

H

) followed by LF (Line Feed, 0A

H

)

NOTE: The examples shown in this manual assume a message terminator will be added at the

end of each message. Where a message terminator is shown it is represented as
meaning CR (0D

H

) followed by LF (0A

H

).

3.13.5

UNDERSTANDING THE COMMAND STRUCTURE

Understanding the command structure requires an understanding of the subsystem command
tree illustrated in Figure 3-3. The “root” is located at the top left corner of the diagram. The
parser goes to the root if:

• a message terminator is recognized by the parser
• a root specifier is recognized by the parser

Optional keywords are enclosed in brackets [ ] for identification; optional keywords can be omit-
ted and the electronic load will respond as if they were included in the message. The root level
keyword [SOURce] is an optional keyword. Starting at the root, there are various branches or
paths corresponding to the subsystems. The root keywords for the EL Series

are :MEASure,

:INPut, :OUTPut, [:SOURce], :PROTection, :STATus, and :SYSTem. Because the [SOURce]
keyword is optional, the parser moves the path to the next level, so that VOLTage, CURRent,
and MEASure commands are at the root level.

Each time the parser encounters a keyword separator, the parser moves to the next indented
level of the tree diagram. As an example, the STATus branch is a root level branch that has
three sub-branches: OPERation, CHANnel, and QUEStionable.

A command must contain the short form (the part of the command in capital letters in appendix
B) or the full command. Commands and values are not case sensitive.

Command strings must be sent as a single message at all times. it is possible to send multiple
command/query strings by separating the commands with a CR. If multiple commands and/or
queries are sent this way, each response must be separated by a CR.

Commands that change a setting must be preceded or followed by a query. This response must
be accepted by the host prior to sending a new command. Example: volt 10\rvolt?\r\n changes
the voltage setpoint of the EL load (\r is CR and \n is NL).

3.13.6

PROGRAM MESSAGE SYNTAX SUMMARY

• Common commands begin with an asterisk (*).

• Queries end with a question mark (?).

• Program messages consist of a root keyword and, in some cases, one or more message

units separated by a colon (:) followed by a message terminator. Several message units
of a program message may be separated by a semicolon (;) without repeating the root
keyword.