I/O Page, New IVI.NET Driver Wizard

Enable VISA-based I/O

This setting controls whether the driver uses the VISA.NET for instrument communication.

Integer format

Specifies the default format code to use for integer values in instrument command strings. Explicit format codes used in the instrument command override this setting.

See the topics under Working With Instrument Commands for more information.

Floating-point format

Specifies the default format code to use for floating-point values in instrument command strings. Explicit format codes used in the instrument command override this setting.

See the topics under Working With Instrument Commands for more information.

String format

Specifies the default format code to use for string values in instrument response strings. Explicit format codes used in the instrument command override this setting. This setting is only used for reading values from the instrument -- not for formatting values sent to the instrument.

See the topics under Working With Instrument Commands for more information.

Boolean True

Specifies a comma-separated list of instrument responses that should be interpreted as a boolean true. For instrument commands, the first string in the list will be used to send a boolean true to the device.

Boolean False

Specifies a comma-separated list of instrument responses that should be interpreted as a boolean false. For instrument commands, the first string in the list will be used to send a boolean false to the device.

SCPI compliant

Indicates whether the instrument uses SCPI-compliant instrument commands. Nimbus provides specialized support for SCPI-compliant instruments. See the topic Special Features For SCPI Commands for detailed information.

Generate direct I/O functions and attributes

This setting controls whether the wizard will generate the IVI-defined methods and properties for directly communicating with the instrument using the underlying I/O mechanism. For a driver using VISA.NET as its underlying I/O library, Nimbus will generate a working implementation of these methods and properties. For a non-VISA-based driver, Nimbus will generate stub implementations that the driver developer must then fill in with an implementation appropriate for their specific I/O library.

The exact syntax and behavior of these functions is prescribed in IVI-3.4: API Sytle Guide.

Important
In order to comply with the IVI Generation IVI-2014, drivers must implement these direct I/O methods and properties. These methods and properties can be created after the wizard runs, but it is typically easier to let the wizard create them upfront.

Enable simulation code generation

Determines whether or not Nimbus ever generates automatic simulation handling code. When true, Nimbus enables the Simulation Editor for properties so that the developer can choose on a property-by-property basis whether or not to instruct Nimbus to generate simulation handling code. Nimbus also generates "stub" simulation code blocks for methods so that the developer has a convenient place to insert their manual method simulation code.

When this setting is false, all properties are set to Manual simulation mode, and the Simulation Editor is disabled. Nimbus also does not generate "stub" simulation code blocks for methods in this case.

This setting is useful in situations where a lower-level software component is handling all of the simulation logic, and the Nimbus driver is simply delegating to that lower-level component. In such cases, it's inconveninet for the developer to explicitly set all properties to Manual simulation mode and to delete all residual and unneeded simulation code generated for methods and properties. With this setting, the developer can simply disable simulation code generation "globally".

Other Resources