Saluki S5800E Series, Руководство пользователя

Страница: 165 / 173

Tel: 886.909 602 109 Email: sales@salukitec.com
www.salukitec.com
165
Chapter 10 Programming Guide
10.1 SCPI Language Basics
This section is not intended to teach you everything about the SCPI (Standard Commands for Programmable
Instruments) programming language. The SCPI Consortium or IEEE can provide that level of detailed information.
For more information, please refer to:
IEEE Standard 488.1-1987, IEEE Standard Digital Interface for Programmable Instrumentation. New York, NY, 1998.
IEEE Standard 488.2-1987, IEEE Standard Codes, Formats, Protocols and Comment Commands for Use with
ANSI/IEEE Std488.1-1987. New York, NY, 1998.
10.1.1 Command keyword and syntax
The instrument does not distinguish between upper and lower case letters. In the documentation, upper case letters
indicate the short form of the keyword. The lower case letters indicate the long form of the keyword. Either form may
be used in the command.
Example: Sens:Freq:Star 1.5 mhz is the same as SENSE:FREQ:start 1.5 MHz
NOTE: The command SENS:FREQU:STAR is not valid because FREQU is neither the short, nor the long form of the
command. Only the short and long forms of the keywords are allowed in valid commands.
10.1.2 Creating valid commands
Commands are not case sensitive and there are often many different ways of writing a particular command. These are
examples of valid commands for a given command syntax:
Command Syntax Sample Valid Commands
[SENSe:]BANDwidth[:RESolution] <freq> The following sample commands are all identical. They will all
cause the same result.

Sense:Band:Res 1700

sens:band 1.7KHZ

band 1.7kHz
[:SENSe]:DETector[:FUNCtion]
NEGative|POSitive|SAMPle

DET:FUNC neg

Detector:Func Pos
INITiate:CONTinuous ON|OFF|1|0 The sample commands below are identical.

INIT:CONT ON

init:continuous 1