Pacific UPC-32 Operation Manual page 91

5.2 CONVENTIONS (cont)
14. Multiple data parameter names and values must be separated by commas.
15. 'Multiple keyword' messages may be sent without duplicating the first level SCPI keyword (i.e.,
SOURce).
e.g., :SOURce:VOLTage1,120; VOLTage2,120; VOLTage3,120.
A keyword is a single word beginning with a colon (:).
16. Program Messages MUST be terminated with a LINE FEED (0Ahex, 10dec) or END (EOI)
signal. This is referred to as an end-of-string <eos>. A Carriage Return character (0Dhex,
13dec) is converted to a LINE FEED by the UPC. Further SCPI commands shall begin with a
first level keyword (i.e.,:SOURce:).
17. All values shown in angle brackets <> are examples of real values used with commands but
labels are sometimes used to indicate a variable which is not known until actual time of use.
e.g., <AMPS meter range> might actually be <50>.
Units such as AAC, Hz or % shown after the angle bracketed value are not to be included inside
the value, but are shown as a reference to the units. The angle brackets are not part of the
value.
18. The UPC data input buffer is 8k bytes, as is its data output buffer. No program message may
exceed this length.
19. All :SOURce: commands also support query. An alternate method of writing or reading the
presently active :SOURce:FORM, COUPLing, VOLTage, FREQuency, CURRent:LIMit, PHASe,
and WAVEFORM values is to use PROGram 0 (see examples). PROGram 0 contains the
MANUAL MODE parameters.
NOTE: Sending any :SOURce: command invokes MANUAL MODE and REMOTE CONTROL.
20. Command strings may contain spaces.
21. The UPC interface accepts IEEE-488.2 NR1, NR2 and NR3 numeric formats. Most query
responses are NR1 or NR2 types. i.e., NR1=120, NR2=120.0, NR3=1.2E+02.
SECTION 5
79
REMOTE OPERATION