Interface IVxiBackplane
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 IVxiBackplane interface provides the properties and methods specific to the VXI BACKPLANE resource.
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. |
|||||||||||
Asserts the specified device interrupt or signal. This operation can be used to assert a device interrupt condition. In VXI, for example, this can be done with either a VXI signal or a VXI interrupt. On certain bus types, the statusID parameter may be ignored. |
|||||||||||
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. |
|||||||||||
Asserts the specified utility bus signal. This operation can be used to assert either the SYSFAIL or SYSRESET utility bus interrupts on the VXIbus backplane. This operation is valid only on FRAMEVXI BACKPLANE and SERVANT (mainframe) and VXI SERV (servant) sessions. Asserting SYSRESET (also known as HARD RESET in the VXI specification) should be used only when it is necessary to promptly terminate operation of all devices in a VXIbus system. This is a serious action that always affects the entire VXIbus system. |
|||||||||||
Maps the specified trigger source line to the specified destination line. This operation can be used to map one trigger line to another. This operation is valid only on BACKPLANE (mainframe) sessions.
If this operation is called multiple times on the same BACKPLANE resource with the same source trigger line and different destination trigger lines, the result should be that when the source trigger line is asserted, all of the specified destination trigger lines should also be asserted. If this operation is called multiple times on the same BACKPLANE resource with different source trigger lines and the same destination trigger line, the result should be that when any of the specified source trigger lines is asserted, the destination trigger line should also be asserted. However, mapping a trigger line (as either source or destination) multiple times requires special hardware capabilities and is not guaranteed to be implemented. |
|||||||||||
Undoes a previous mapping from the specified trigger source line to the specified destination line. This operation can be used to undo a previous mapping of one trigger line to another. This operation is valid only on BACKPLANE (mainframe) sessions. |
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 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. |
|
Identifier for the current triggering mechanism. |
|
Shows the current state of the VXI trigger lines. This is a bit vector with bits 0-9 corresponding to TRIG_TTL0 through TRIG_ECL1. |
|
Shows which VXI trigger lines this implementation supports. This is a bit vector with bits 0-9 corresponding to TRIG_TTL0 through TRIG_ECL1. |
|
Shows the current state of the VXI/VME interrupt lines. This is a bit vector with bits 0-6 corresponding to interrupt lines 1-7. |
|
Shows the current state of the VXI/VME SYSFAIL (SYStem FAILure) backplane line. |