The ViSession handle that you obtain from Ivi_SpecificDriverNew. The handle identifies a particular IVI session.

If the attribute you specify is based on a repeated capability, pass a repeated capability identifier. You can pass one of the identifiers strings that the specific instrument driver defines, or a virtual name the end-user defines in the configuration file.

If the attribute you specify is not based on a repeated capability, pass VI_NULL or an empty string.

Pass the ID of an attribute for this parameter.

The include file for a specific instrument driver defines constant names for all of the user-accessible attributes that apply to the driver. This includes attributes that the IVI engine defines, attributes that the instrument class defines, and attributes that are specific to the particular instrument. Each defined constant name begins with PREFIX_ATTR_, where PREFIX is the specific instrument prefix.

For each IVI engine attribute, the specific driver include file uses the same constant name that appears in ivi.h, except that the specific instrument prefix replaces the IVI prefix. For example, ivi.h defines IVI_ATTR_CACHE, and the Fluke 45 include file, fl45.h, defines the following constant name:

#define FL45_ATTR_CACHE  IVI_ATTR_CACHE

For each instrument class attribute, the specific driver include file uses the same constant name that appears in the instrument class include file, except that the specific instrument prefix replaces the class prefix. For example, the DMM class include file, ividmm.h, defines IVIDMM_ATTR_RANGE, and fl45.h defines the following constant name:

#define FL45_ATTR_RANGE  IVIDMM_ATTR_RANGE

For each specific instrument attribute, the specific driver include file defines a constant name and assigns a value that is an offset from IVI_SPECIFIC_PUBLIC_ATTR_BASE. For example, fl45.h defines the following constant name:

#define FL45_ATTR_HOLD_THRESHOLD \ (IVI_SPECIFIC_PUBLIC_ATTR_BASE + 3L)

For each attribute that is private to an instrument driver, the instrument driver source file defines a constant name and assigns a value that is an offset from IVI_SPECIFIC_PRIVATE_ATTR_BASE. For example, hp34401a.c defines the following constant name:

#define HP34401A_ATTR_TRIGGER_TYPE \ (IVI_SPECIFIC_PRIVATE_ATTR_BASE + 1L)

If the range table for the attribute contains a meaningful minimum value, the function returns the minimum value in this parameter.

For tables of type IVI_VAL_DISCRETE or IVI_VAL_RANGED, the minimum value is the lowest discreteOrMinValue in the table.

For tables of type IVI_VAL_COERCED, the minimum value is the lowest coercedValue in the table.

If you are not interested in this value, you can pass VI_NULL.

If the range table for the attribute contains a meaningful maximum value, the function returns the maximum value in this parameter.

For tables of type IVI_VAL_DISCRETE or IVI_VAL_RANGED, the maximum value is the highest discreteOrMinValue in the table.

For tables of type IVI_VAL_RANGED, the maximum value is the highest maxValue in the table.

For tables of type IVI_VAL_COERCED, the maximum value is the highest coercedValue in the table.

If you are not interested in this value, you can pass VI_NULL.

Returns VI_TRUE (1) if the range table for the attribute indicates that it contains a meaningful minimum value. Otherwise, returns VI_FALSE (0).

If you are not interested in this value, you can pass VI_NULL.

If you are not interested in this value, you can pass VI_NULL.

Returns VI_TRUE (1) if the range table for the attribute indicates that it contains a meaningful maximum value. Otherwise, returns VI_FALSE (0).

If you are not interested in this value, you can pass VI_NULL.