An INSTR resource implementation for a USB system SHALL return the error VI_ERROR_INV_EVENT when a user tries to enable for a USBTMC device (base-class or USB488) that does VI_EVENT_USB_INTR not have an interrupt IN pipe. RULE 5.1.65 An INSTR resource implementation for a USB system SHALL generate only when VI_EVENT_USB_INTR the interrupt header contains a vendor-specific notification as defined by the USBTMC specification. OBSERVATION 5.1.12 A USB488 service request notification will not cause to be generated. VI_EVENT_USB_INTR RULE 5.1.66 IF a framework is 32-bit, THEN the values of the attributes and VI_ATTR_RET_COUNT SHALL be identical. VI_ATTR_RET_COUNT_32 RULE 5.1.67 IF a framework is 64-bit, THEN the values of the attributes and VI_ATTR_RET_COUNT SHALL be identical. VI_ATTR_RET_COUNT_64 RULE 5.1.68 IF a framework is 32-bit, THEN the attribute SHALL NOT be defined. VI_ATTR_RET_COUNT_64 OBSERVATION 5.1.13 A user on a 32-bit framework cannot transfer more data than would fit in a 32-bit size.
An INSTR resource implementation for a USB system SHALL return the error VI_ERROR_INV_EVENT when a user tries to enable VI_EVENT_USB_INTR for a USBTMC device (base-class or USB488) that does not have an interrupt IN pipe. RULE 5.1.65 An INSTR resource implementation for a USB system SHALL generate VI_EVENT_USB_INTR only when the interrupt header contains a vendor-specific notification as defined by the USBTMC specification. OBSERVATION 5.1.12 A USB488 service request notification will not cause VI_EVENT_USB_INTR to be generated. RULE 5.1.66 IF a framework is 32-bit, THEN the values of the attributes VI_ATTR_RET_COUNT and VI_ATTR_RET_COUNT_32 SHALL be identical. RULE 5.1.67 IF a framework is 64-bit, THEN the values of the attributes VI_ATTR_RET_COUNT and VI_ATTR_RET_COUNT_64 SHALL be identical. RULE 5.1.68 IF a framework is 32-bit, THEN the attribute VI_ATTR_RET_COUNT_64 SHALL NOT be defined. OBSERVATION 5.1.13 A user on a 32-bit framework cannot transfer more data than would fit in a 32-bit size.
vpp43_2015-06-19.docx