16SCPI Programming FundamentalsSCPI Language BasicsSCPI Language BasicsThis section provides a basic introduction to the SCPI language. For more details about SCPI, see IEEE Standard488.2–1992.Topics covered in this section include:• “Command Keywords, Separators and Syntax” on page 16• “Creating Valid Commands” on page 17• “Special Characters in Commands” on page 17• “Parameters in Commands” on page 19• “Writing Multiple Commands on the Same Line” on page 21Command Keywords, Separators and SyntaxKeywords, Parameters & Separators: A typical SCPI command is made up of keywords separated by colons. Thekeywords are followed by parameters that can be followed by optional units. The parameter list is separated from thecommand by a space.Example: :SENSe:FREQuency:STARt 1.5 MHZUpper- vs. Lower-Case Usage: The instrument does not distinguish between upper and lower case letters. In thedocumentation, upper case letters indicate the short form of the keyword, whereas lower case letters indicate the longform of the keyword. Either form may be used in the command.Example::Sens:Freq:Star 1.5 mhzThis is the same as:SENSE:FREQ:start 1.5 MHzNOTE The command :SENS:FREQU:STAR would not be valid because FREQU is neither the short, northe long form of the command. Only the short and long forms of the keywords are allowed invalid commands.Multiple SCPI commands on the same line: This is permissible if the commands are separated by a semicolon. See“Writing Multiple Commands on the Same Line” on page 21.Initial Colon: In general, SCPI commands start with a colon, as shown above. You may choose to omit the initial colon,but, if you do so, note that SCPI rules for the interpretation of Compound Headers will be invoked by the commandinterpreter. For full discussion and examples of Compound Headers, see Appendix A of IEEE Standard 488.2–1992. Forexamples, see “SCPI Termination and Separator Syntax Examples” on page 21.