Can't see the Tab Menu Above? Get The Flash Plug-In Now! Or you can scroll to the bottom for a TEXT Menu

 

About The SCPI Consortium 

The SCPI Consortium is an organization whose members share a common commitment to develop a common interface language between computers and test instruments. The SCPI Standard is built on the foundation of IEEE-488.2, Standard Codes and Formats. It requires conformance to IEEE-488.2, but is pure software standard. SCPI syntax is ASCII text, and therefore can be attached to any computer test language, such as BASIC, C, or C++. It can also be used with Test Application Environments such as LabWindows/CVI, LabVIEW, or HP VEE. SCPI is Hardware Independent. SCPI strings can be sent over any instrument interface. It works equally well over GPIB, RS-232, VXIbus or LAN networks. 

The SCPI Consortium Charter

The charter of the SCPI Consortium is to improve the effectiveness of instrument test 
software by increasing ease of use and improving the interoperability of multivendor test 
systems. By developing a common, easily understood, "English-like" instrument language, 
the Consortium hopes to improve ease of programming for a wide variety of instruments. 
In addition, use of SCPI's "English-like" syntax should improve test software documentation and maintainability. 

Operating Rules 

The SCPI Consortium meets at least once per year, and at any time members feel it is necessary to consider new commands. In the last few years we have met at least twice per year. The Annual meeting is normally in the last week of January of each year, held in San Diego, CA. Other meetings are scheduled as needed, usually hosted by one of the members. 

New proposals must be posted to all members electronically at least one month before the scheduled meeting at which the proposal is to be discussed. This is to give members time to review and comment. The SCPI Consortium has a proposal format that must be followed. The concept is that a proposal must be made with the exact wording to be added to the SCPI Standard. An explanation of the problem (instrument requiring the new command) and how this proposal solves the problem is expected as part of the proposal. 

Additional commands can be added to the standard at any time, even if the SCPI Consortium has not approved them. In this case, the SCPI Rules require that you list these commands separately in your instrument documentation, so that users will not expect to find the new commands in other SCPI instruments. 

Relationship to VXIplug&play Systems Alliance 

The VXIplug&play Systems Alliance is a natural complement to the SCPI Standard. The 
Charter of the VXIplug&play Systems Alliance is to develop instrument driver technology for a broad range of instruments. These are primarily VXIbus instruments, but the driver technology is useful for other instruments, such as GPIB instruments, as well. 

VXIplug&play drivers can use SCPI protocol for Message-based VXI instruments that 
speak SCPI, but can be adopted for register-based instruments as well. For more 
information on the VXIplug&play Systems alliance and its charter, function, specifications, and membership, go to www.vxipnp.org
 
 


HOME | SCPI INFO | SCPI CONSORTIUM | MEMBERSHIP | LINKS