For GPIB, ASRL, USB, and VXI software triggers, is the only valid protocol. VI_TRIG_PROT_DEFAULT For VXI hardware triggers, is equivalent to VI_TRIG_PROT_DEFAULT VI_TRIG_PROT_SYNC. viAssertTrigger() For a PXI resource, will reserve a trigger line for assertion, or release such a viAssertTrigger() reservation. Instrument drivers should use to ensure that they have ownership of a trigger line before performing any operation that could drive a signal onto that trigger line. The protocol VI_TRIG_PROT_RESERVE VI_TRIG_PROT_UNRESERVE, parameter can be either or which reserve a trigger line and release the reservation, respectively. Related Items See the INSTR resource description. Implementation Requirements RULE 6.1.23 For compatibility with earlier versions of this specification, SHALL be equal to VI_TRIG_PROT_DEFAULT VI_NULL. RULE 6.1.24 IF the attribute is set to for a session to an ASRL INSTR or TCPIP VI_ATTR_IO_PROT VI_PROT_NORMAL SOCKET resource, THEN the operation SHALL return viAssertTrigger() VI_ERROR_INV_SETUP. RULE 6.1.25 An INSTR resource implementation of for a USB System SHALL return the error viAssertTrigger() for a USBTMC base-class (non-488) device. VI_ERROR_INV_SETUP RULE 6.1.26 An INSTR resource implementation of for a USB System SHALL return the error viAssertTrigger() for a USBTMC 488-class device that does not implement the optional trigger VI_ERROR_INV_SETUP message ID. 6.1.8 viReadSTB(vi, status) Purpose Read a status byte of the service request. Parameters Name Direction Type Description vi IN ViSession Unique logical identifier to the session. status OUT ViUInt16 Service request status byte. Return Values Type This is the operational return status. It returns either a ViStatus completion code or an error code as follows. Completion Code Description VI_SUCCESS Operation completed successfully. Error Codes Description
For GPIB, ASRL, USB, and VXI software triggers, VI_TRIG_PROT_DEFAULT is the only valid protocol. For VXI hardware triggers, VI_TRIG_PROT_DEFAULT is equivalent to VI_TRIG_PROT_SYNC. For a PXI resource, viAssertTrigger() will reserve a trigger line for assertion, or release such a reservation. Instrument drivers should use viAssertTrigger() to ensure that they have ownership of a trigger line before performing any operation that could drive a signal onto that trigger line. The protocol parameter can be either VI_TRIG_PROT_RESERVE or VI_TRIG_PROT_UNRESERVE, which reserve a trigger line and release the reservation, respectively. Related Items See the INSTR resource description. Implementation Requirements RULE 6.1.23 For compatibility with earlier versions of this specification, VI_TRIG_PROT_DEFAULT SHALL be equal to VI_NULL. RULE 6.1.24 IF the attribute VI_ATTR_IO_PROT is set to VI_PROT_NORMAL for a session to an ASRL INSTR or TCPIP SOCKET resource, THEN the operation viAssertTrigger() SHALL return VI_ERROR_INV_SETUP. RULE 6.1.25 An INSTR resource implementation of viAssertTrigger() for a USB System SHALL return the error VI_ERROR_INV_SETUP for a USBTMC base-class (non-488) device. RULE 6.1.26 An INSTR resource implementation of viAssertTrigger() for a USB System SHALL return the error VI_ERROR_INV_SETUP for a USBTMC 488-class device that does not implement the optional trigger message ID. 6.1.8 viReadSTB(vi, status) Purpose Read a status byte of the service request. Parameters Name Direction Type Description vi IN ViSession Unique logical identifier to the session. status OUT ViUInt16 Service request status byte. Return Values Type ViStatus This is the operational return status. It returns either a completion code or an error code as follows. Completion Code Description VI_SUCCESS Operation completed successfully. Error Codes Description
vpp43_2018-10-19.docx