IEEE SCPI编程手册：1999版 - 仪器仪表程控指南

需积分: 50 119 浏览量更新于2023-05-15 2 收藏 3.23MB PDF 举报

"IEEE官方SCPI编程手册，详细阐述了Standard Commands for Programmable Instruments (SCPI)的语法和风格，基于IEEE488.2协议，适用于仪器仪表的程控编程和API接口设计。" SCPI（Standard Commands for Programmable Instruments）是一种通用的命令集，专门用于编程控制可编程仪器，如示波器、信号发生器、频谱分析仪等。它建立在IEEE488.2协议的基础上，该协议是 GPIB（General Purpose Interface Bus，通用接口总线）的第二版，主要用于物理仪器之间的数字通信。SCPI的出现使得不同厂商的仪器能够通过统一的命令语言进行操作，极大地简化了测试和测量系统的集成。在1999年发布的这个版本中，SCPI标准详细定义了其语法和风格，包括命令的构造、参数的表示、错误处理等方面，旨在提供一种一致且易于理解的编程接口。手册的目的是鼓励整个测试和测量市场全面考虑并采用SCPI标准。尽管SCPI联盟对标准不提供任何保证，但允许在保持完整性的前提下复制整份文档，每份副本上都应显著显示版权信息、意图声明和复制授权。 SCPI的语法特点包括： 1. **层次结构**：命令结构清晰，通常由类别、子类别和具体命令组成，如`*IDN?`用于询问设备身份。 2. **参数化**：命令参数可以是数值、字符串或数组，使用括号包围，如`VOLT 10`设置电压为10V。 3. **错误处理**：使用错误状态码和消息，如`*ERR?`查询最后的错误信息。 4. **命令兼容性**：保留了GPIB的一些传统命令，同时增加了新的功能，以提高易用性和灵活性。在实际应用中，开发人员会根据SCPI标准创建适配器库或驱动程序，使得软件可以通过标准接口与硬件通信。这些接口通常包含在仪器的嵌入式系统中，也可以是独立的软件模块，例如IVI（Interchangeable Virtual Instruments）库。对于仪器仪表的程控编程，理解并熟练使用SCPI是至关重要的。这不仅可以提高自动化测试的效率，还能确保跨平台和跨设备的一致性。而SCPI与IEEE488.2的结合，使得物理层的通信有了标准化的基础，降低了多设备集成的复杂性。 SCPI是测试测量领域中一个强大的工具，它提供了标准化的命令集，简化了仪器的编程，促进了不同设备间的互操作性。通过深入学习和应用SCPI，工程师能够更高效地实现对仪器仪表的控制和数据采集。

4.1.3.1 Overlapped and Sequential Commands

KI005IEEE 488.2 defines a distinction between overlapped and sequential commands. As defined

in IEEE 488.2, a sequential command is one which finishes executing before the next

command starts executing. An overlapped command is one which does not finish executing

before the next command starts executing. These types of commands are described in IEEE

488.2, section 12. Examples are given in IEEE 488.2, appendix B.

KI005IEEE 488.2 defines three common commands (*OPC, *WAI, *OPC?) which a device

controller can use to synchronize its operation to the execution of overlapped commands.

The definitions for these common commands appear in sections 10.18, 10.19, and 10.39 of

IEEE 488.2. All three are required by IEEE 488.2, even if none of the device’s commands

are overlapped.

KI005Implementing any device commands as overlapped will increase the complexity of the

implementation of the three synchronization common commands.

KI005Each overlapped command has associated with it a Pending Operation flag. The device sets

this flag TRUE when it passes the corresponding command from the Execution Control

block to the Device Action block. The device sets the flag false when the device operation is

finished, or has been aborted.

KI005IEEE 488.2 defines a No Operation Pending flag. This flag is FALSE whenever any Pending

Operation flag is TRUE, and is TRUE whenever all Pending Operation flags are FALSE.

IEEE 488.2 also permits device designers to decide which overlapped commands are

included in the No Operation Pending flag. A device may implement commands which

select which overlapped commands are included in the No Operation Pending flag, although

the SCPI standard does not include such a command.

KI005IEEE 488.2 requires user documentation to clearly indicate which commands, if any, are

overlapped, and which overlapped commands are included and which are excluded from the

No Operation Pending flag.

KI0054.1.3.2 *CLS

KI005This command clears all status data structures in a device. For a device which minimally

complies with SCPI, these registers are:

KI005 SESR (IEEE 488.2)

OPERation Status Register (SCPI)

QUEStionable Status Register (SCPI)

Error/Event Queue (SCPI)

KI005Execution of *CLS shall also clear any additional status data structures implemented in the

device. The corresponding enable registers are unaffected. See the table in Command

Reference, 20.7.

KI005*CLS forces the device into OCIS and OQIS (see 4.1.3.3 and 4.1.3.4) without setting the No

Operation Pending flag TRUE and without setting the OPC bit of the SESR TRUE and

without placing a “1” into the Output Queue.

KI005

1999 SCPI Syntax & Style

4-2 SCPI Compliance Criteria

For example, suppose a device implements INITiate[:IMMediate] as an overlapped

command. Assuming that the trigger model is programmed so that it will eventually return to

the IDLE state, and that INITiate[:IMMediate] takes longer to execute than *OPC, sending

these commands to this device:

KI005 INITiate;*OPC

KI005results in initiating the trigger model and, after some time, setting the OPC bit in the SESR.

However, sending these commands:

KI005 INITiate;*OPC;*CLS

KI005still initiates the trigger model. Since the operation is still pending when the device executes

*CLS, the device does not set the OPC bit until it executes another *OPC command.

KI0054.1.3.3 *OPC and *WAI

KI005A device is in the Operation Complete Command Active State (OCAS) after it has executed

*OPC. The device returns to the Operation Complete Command Idle State (OCIS) whenever

the No Operation Pending flag is TRUE, at the same time setting the OPC bit of the SESR

TRUE. See IEEE 488.2 Fig 12-4. The following events force the device into OCIS without

setting the No Operation Pending flag TRUE and without setting the OPC bit of the SESR:

KI005power on

KI005receipt of the dcas message (device clear)

KI005execution of *CLS

KI005execution of *RST

KI005Implementation of the *OPC and *WAI commands is straightforward in devices which

implement only sequential commands. When executing *OPC the device simply sets the

OPC bit of SESR. Executing *WAI is a no-operation. The device is, in effect, always in

OCIS.

KI005In devices which implement overlapped commands the implementation of *OPC and *WAI

is a little more complicated. After executing *OPC the device must not set the OPC bit of

SESR until the device returns to OCIS, even though it continues to parse and execute

commands. After executing *WAI the device must execute no further commands or queries

until the No Operation Pending flag is TRUE, or receipt of a dcas message, or a power on.

KI0054.1.3.4 *OPC?

KI005SCPI adds the requirement that *OPC? is implemented as a sequential command.

KI005A device is in the Operation Complete Query Active State (OQAS) after it has executed

*OPC?. The device returns to the Operation Complete Query Idle State (OQIS) whenever

the No Operation Pending flag is TRUE, at the same time placing a “1" in the Output Queue.

See IEEE 488.2 Fig 12-6. The following events force the device into OQIS without setting

the No Operation Pending flag TRUE and without placing a ”1" in the Output Queue:

KI005power on

KI005receipt of the dcas message (device clear)

KI005

1999 SCPI Syntax & Style

SCPI Compliance Criteria 4-3

Implementation of the *OPC? query is straightforward in devices which implement only

sequential commands. When executing *OPC? the device simply places a “1" in the Output

Queue.

KI005The implementation of overlapped commands in a device complicates the implementation of

*OPC? and places some restrictions on the implementation of the Message Exchange

Protocol (MEP). IEEE 488.2 dictates that devices shall send query responses in the order that

they receive the corresponding queries (IEEE 488.2 6.4.5.4). Although IEEE 488.2

recommends that *OPC? be the last query in a program message, there is nothing to prevent

a controller program from ignoring this suggestion. This is why *OPC? must be sequential.

KI0054.1.3.5 *RST

The “*RST Conditions” chapter of Volume 1 gives pretty a lucid description of the SCPI

requirements of *RST. There are, however, some implications.

KI0054.1.3.5.1 Interaction With the Synchronization Commands

KI005*RST stops the execution of any overlapped commands. The natural outcome of this is that

the No Operation Pending flag will go TRUE. Execution of *RST must place the device in

OCIS before setting the No Operation Pending flag TRUE, so that the effect of any pending

*OPC command is nullified (that is, the OPC bit of the SESR does NOT get set).

KI0054.1.3.5.2 Implications For *SAV and *RCL

KI005In devices which implement the optional *SAV and *RCL common commands, the scope of

instrument settings affected by these commands shall be the same as that affected by *RST.

This means that if *RST has any effect upon a command, then so must *RCL. Conversely, if

the device designer wants *RCL to have an effect upon a command, then *RST must also

have an effect upon that command. Inversely, and more importantly, if the device designer

wants a command to be EXCLUDED from the scope of *SAV and *RCL, then it must also

be excluded from the scope of *RST.

KI005KI0054.1.3.5.3 *RST and *RCL as Overlapped Commands

KI005While *RST stops the execution of running overlapped commands, the instrument designer

may find it useful to make the *RST command, itself, overlapped. For example, if resetting

requires the return to an initial position of a slow-reacting, electro-mechanical device. In this

case, performance may be better served with *RST overlapped as subsequent commands

may be parsed and executed while the resetting is completing. Even while overlapped, the

*RST command shall always complete the resetting of device state variables before

subsequent commands are processed to insure the integrity of *RST exception programming.

For similar reasons, *RCL may be an overlapped command.

KI005If *RST or *RCL is overlapped, its Pending-Operation flag shall be reported in the

No-Operation-Pending flag.

KI005If execution of *RST or *RCL causes a device operation which is equivalent to executing an

overlapped command, the device shall set TRUE the Pending-Operation flag associated with

that command.

1999 SCPI Syntax & Style

4-4 SCPI Compliance Criteria

PH022

4.2.2 Optional Commands

All other commands in the “Command Reference” are considered optional, depending on the

capabilities of the instrument. That is, the control of any instrument capability that is

described in SCPI shall be implemented exactly as specified by using the appropriate SCPI

defined commands. For example, an instrument dedicated to voltage measurement would

not implement commands for sensing frequency. Certain commands, if implemented,

require that other commands also be implemented.

When a device does not support all alternative parameter values that are allowed for a SCPI

command, it may implement a subset of these values unless otherwise stated. For example,

if an instrument implements only RECTangular and UNIForm data shaping for its

CALCulate:TRANSform:WINDow command, it may generate an error on receipt of any

other SCPI defined parameter value (FLATtop,HAMMing, etc). However, a device must

implement all parameters of a multi-parameter SCPI command.

Commands required to implement a SCPI-described capability may be omitted under special

conditions. The special condition exists when a command to be implemented affects a part

of the instrument in which the configuration is fixed, and that the fixed configuration for that

command corresponds to the value it would take on when an IEEE 488.2 *RST reset

command is issued. For example, an instrument with a display that is configured to be

permanently on does not need to implement the command that turns the display ON or OFF,

since at *RST it is required by SCPI to be ON. If an instrument has a fixed configuration in

which a setting does not correspond to the *RST value, then the instrument shall implement

the command for that setting even though it has only a single legal value.

4.2.3 Documentation Requirements

The documentation for a SCPI instrument shall list the version number for which the

instrument complies. This information shall appear on instrument specification sheets and

related documents, as well as the programming manual.

HP076The manual for a SCPI instrument shall have a separate section titled “SCPI Conformance

Information”. This section shall list separately:

The SCPI version to which the instrument complies

The syntax of all SCPI confirmed commands implemented by the instrument.

Confirmed commands are those commands which are published in the latest

version of SCPI to which the instrument conforms. Commands in the

DIAGnostic subsystem, and other commands which are not intended for end-user

use need not be documented in this section.

HP000,HP001

The syntax of all SCPI approved commands implemented by the instrument.

Approved commands are those commands which have been approved by the

SCPI Consortium, but are not contained in the version of SCPI to which the

instrument conforms.

HP000

The syntax of all commands implemented by the instrument, which are not part of

1999 SCPI Syntax & Style

4-6 SCPI Compliance Criteria

剩余818页未读，继续阅读

fifodct

粉丝: 2
资源: 2

IEEE SCPI编程手册：1999版 - 仪器仪表程控指南

scpi-parser-2.1.zip_SCPI_SCPI 解析_SCPI解析器_Scpi server_scpi parse

SCPI协议1999版

基于单片机的SCPI命令解析模块的设计与实现.pdf

IT6322B-UM-EN-231250.pdf

DAQ97-90002.pdf

自动化测量-Python.pdf

SCPI Command Reference.pdf

Keysight频谱仪9020A指令手册——[9020A]N9060-90027.pdf

SCPI基础知识介绍.pdf

SCPI 1999 PDF WORD.rar

最新资源