Interface IVxi3
Note: Keysight's VISA COM does not support a COM server for VXI. The IVxi-related interfaces are listed in this help file because they are included in the global VISA COM library.
Description
The IVxi3 interface defines the methods and COM properties specific to VXI and GPIB-VXI INSTR sessions.
Methods
|
Use of this method is discouraged. All the non-deprecated standard attributes are accessible via properties on the appropriate COM interfaces. |
|
|
Use of this method is discouraged. All the non-deprecated standard attributes are accessible via properties on the appropriate COM interfaces. |
|
|
Locks the resource. |
|
|
Unlocks the resource |
|
|
Opens the resource. This is the first method on IVisaSession or any of its derived interfaces to be called. In general, you will not call this method because you will use the Resource Manager to create resources. |
|
|
Closes the resource. Sending the resource's COM object's reference count to zero (and thus destroying the object) also executes a close, but this method may be useful for environments with garbage collection or other facilities that make object lifetimes non-deterministic. |
|
|
Sources a software or hardware trigger dependent on the interface type. For a VXI device, if the TriggerID property is TRIG_SW, then the device is sent the Word Serial Trigger command; for any other values of the attribute, a hardware trigger is sent on the line corresponding to the value of that attribute. For VXI software triggers, TRIG_PROT_DEFAULT is the only valid protocol. For VXI hardware triggers, TRIG_PROT_DEFAULT is equivalent to TRIG_PROT_SYNC. |
|
|
Sendsthe device a miscellaneous command or query and/or retrieves the response to a previous query. This operation can send a command or query, or receive a response to a query previously sent to the device. The mode parameter specifies whether to issue a command and/or retrieve a response, and what type or size of command and/or response to use. |
Properties
|
A numeric version for this component. |
|
|
The VISA-defined version information for the specification version to which this component complies. |
|
|
The name of the hardware interface (GPIB, ASRL, etc.). |
|
|
The board number of the hardware interface. |
|
|
The type number of the hardware interface. |
|
|
The current locking state of the interface. |
|
|
The option string corresponding to the current state of the resource. |
|
|
The programmatic ID that can be used by COM to create this object. |
|
|
The VISA resource name of the currently open resource. This name is the canonical version of the resource name and therefore may vary from the resource string used to open/init the resource. |
|
|
The session type string, such as "INSTR" or "INTFC". |
|
|
The ID number of the vendor of this software component. |
|
|
The name of the vendor of this software component. |
|
|
The I/O timeout in milliseconds for I/O communication on this resource session. |
|
|
The return value from the last method call on this interface. This property may be useful in Visual Basic, where positive return values, such as warnings and other non-error return values, cannot be retrieved. See the Return Values page for a list of positive return values. |
|
|
Logical address of the commander of the VXI device used by the given session. |
|
|
Specifies the address modifier to be used in high-level access operations, such as OutXX and MoveOutXX, when writing to the destination. |
|
|
Represents the VXI-defined device class to which the resource belongs: either message based (VXI_CLASS_MESSAGE), register based (VXI_CLASS_REGISTER), extended (VXI_CLASS_EXTENDED), or memory (VXI_CLASS_MEMORY). VME devices are usually either register based or belong to a miscellaneous class (VXI_CLASS_OTHER). |
|
|
Determines which FDC channel will be used to transfer the buffer. |
|
|
Determines which FDC mode to use (Normal mode or Stream mode). |
|
|
If set to true, a channel pair will be used for transferring data. Otherwise, only one channel will be used. |
|
|
Specifies whether the given device is an immediate servant of the controller running VISA. |
|
|
Logical address of the VXI or VME device used by the given session. For a VME device, the logical address is actually a pseudo-address in the range 256 to 511. |
|
|
Logical address of a given device in the mainframe, usually the device with the lowest logical address. Other possible values include the logical address of the slot-0 controller or of the parent-side extender. Often, these are all the same value. The purpose of this attribute is to provide a unique ID for each mainframe. A VISA manufacturer can choose any of these values, but must be consistent across mainframes. If this value is not known, the attribute value returned is UNKNOWN_LA. |
|
|
Manufacturer identification number of the VXIbus device. |
|
|
The name of the manufacturer, as a string. The value of this property should be used for display purposes only and not for programmatic decisions, as the value can be different between VISA implementations and/or revisions. |
|
|
Base address of the device in VXIbus memory address space. This base address is applicable to A24 or A32 address space. |
|
|
Size of memory requested by the device in VXIbus address space. |
|
|
VXIbus address space used by the device. The three types are A16 only, A16/A24, or A16/A32 memory address space. |
|
|
Model code for the device. |
|
|
Model name of the device, as a string. The value of this property should be used for display purposes only and not for programmatic decisions, as the value can be different between VISA implementations and/or revisions. |
|
|
Identifier for the current triggering mechanism. |
|
|
Physical slot location of the VXIbus device. If the slot number is not known, UNKNOWN_SLOT is returned. |
|
|
Specifies the address modifier to be used in high-level access operations, such as InXX and MoveInXX, when reading from the source. |
|
|
Shows which VXI trigger lines this implementation supports. This is a bit vector with bits 0-9 corresponding to TRIG_TTL0 through TRIG_ECL1. |
|
|
Specifies whether the device is IEEE 488.2 compliant. |