Click or drag to resize

Special Features For SCPI Commands

Many instruments today follow the SCPI (Standard Commands for Programmable Instruments) standard supported command set. Nimbus offers special convenience features for SCPI-based instruments. By checking the SCPI compliant check box on the I/O Page of the Driver Settings Editor, you are telling Nimbus that the instrument commands associated with methods and properties are SCPI compliant.

When a driver project is SCPI-compliant, Nimbus automatically strips the optional characters from the SCPI command string. This allows the developer to enter the full verbose form of the SCPI command in the Method General Editor and have the full text appear in the help page for the method. However, the Nimbus-generated code that sends the command to the instrument will use the minimal form of the command.

Consider the SCPI command below:


If this command is associated with a method or property via the Method General Editor, the command that will ultimately be sent to the instrument as follows:


Note that all of the optional characters enclosed in square brackets have been removed, as have all of the lowercase characters.

Tip Tip

It is best to always enter the full SCPI command when associating instrument commands with methods and properties so that the full text shows up in the driver help file. Nimbus automatically adds the instrument commands to the driver help file index and builds a special page that maps instrument commands to driver methods and properties. Most users will expect to see the full form of the SCPI command in such contexts.

See Also

Download a complete CHM version of this documentation here.