Models Page, IVI-COM Driver Settings
The Models Page is used to define the list of instrument models supported by the driver. Nimbus allows the driver's method and property behavior to vary based on model or family. The topic Adding Support for Multiple Instrument Models explains many of the multi-model Nimbus concepts.
Right-click a model or family node.
Choose Add Model.
Enter the desired model name.
The name chosen here is NOT an arbitrary identifier. This name must exactly match the model string read from the device during initialization, such as the response to the "*IDN?" string. See the topic Adding Support for Multiple Instrument Models for an explanation of how Nimbus determines the connected instrument model.
Nimbus allows a driver to organize its supported list of models into related groups called families. Only a single level of hierarchy is supported -- in other words, you cannot have families of families. Unlike the instrument model names, the instrument family names are not used directly in any externally visible way. They are only used within Nimbus to group and organize models.
Right-click an existing family.
Choose Add Family.
Enter the desired family name.
The name chosen here is treated as an arbitrary identifier as does not need to match any actual identifier read from the instrument.
Nimbus supports the notion of a default model to handle the situation where the driver is operating in simulation mode and thus cannot determine what instrument model to use when executing driver-specific implementation code. The default model is used only for simulated driver sessions and only if no Model parameter is passed to Initialize.
See the topic Adding Support for Multiple Instrument Models for a discussion of the default instrument model.
Right-click an existing model.
Choose Make default model.
The selected model is shown in bold font.
Download a complete CHM version of this documentation here.