vi IN ViSession Unique logical identifier to a session. buf ViBuf IN Represents the location of a data block to be sent to device. count ViUInt32 IN Specifies number of bytes to be written. retCount OUT ViUInt32 Represents the location of an integer that will be set to the number of bytes actually transferred. Return Values This is the operational return status. It returns either a Type ViStatus completion code or an error code as follows. Completion Code Description VI_SUCCESS Operation completed successfully. Error Codes Description VI_ERROR_INV_SESSION The given session or object reference is invalid (both VI_ERROR_INV_OBJECT are the same value). VI_ERROR_NSUP_OPER The given does not support this operation. vi VI_ERROR_RSRC_LOCKED Specified operation could not be performed because the resource identified by has been locked for this vi kind of access. VI_ERROR_TMO Timeout expired before operation completed. VI_ERROR_INV_SETUP Unable to start write operation because setup is invalid (due to attributes being set to an inconsistent state). VI_ERROR_IO An unknown I/O error occurred during transfer. Description This operation is similar to and does not perform any kind of data formatting. It differs from viWrite() in that the data is written to the formatted I/O write buffer (the same buffer as used by viWrite() and related operations) rather than directly to the device. This operation can intermix with viPrintf() the operation, but mixing it with the operation is discouraged. viPrintf() viWrite() Table 6.2.1 Special Values for Parameter retCount Value Action Description VI_NULL Do not return the number of bytes transferred. Related Items See the INSTR resource description. Also see and viWrite() viBufRead(). Implementation Requirements RULE 6.2.10 IF the operation returns THEN the write buffer for the specified session viBufWrite() VI_ERROR_TMO, SHALL be cleared.
vi IN ViSession Unique logical identifier to a session. buf IN ViBuf Represents the location of a data block to be sent to device. count IN ViUInt32 Specifies number of bytes to be written. retCount OUT ViUInt32 Represents the location of an integer that will be set to the number of bytes actually transferred. 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 VI_ERROR_INV_SESSION VI_ERROR_INV_OBJECT The given session or object reference is invalid (both are the same value). VI_ERROR_NSUP_OPER The given vi does not support this operation. VI_ERROR_RSRC_LOCKED Specified operation could not be performed because the resource identified by vi has been locked for this kind of access. VI_ERROR_TMO Timeout expired before operation completed. VI_ERROR_INV_SETUP Unable to start write operation because setup is invalid (due to attributes being set to an inconsistent state). VI_ERROR_IO An unknown I/O error occurred during transfer. Description This operation is similar to viWrite() and does not perform any kind of data formatting. It differs from viWrite() in that the data is written to the formatted I/O write buffer (the same buffer as used by viPrintf() and related operations) rather than directly to the device. This operation can intermix with the viPrintf() operation, but mixing it with the viWrite() operation is discouraged. Table 6.2.1 Special Values for retCount Parameter Value Action Description VI_NULL Do not return the number of bytes transferred. Related Items See the INSTR resource description. Also see viWrite() and viBufRead(). Implementation Requirements RULE 6.2.10 IF the viBufWrite() operation returns VI_ERROR_TMO, THEN the write buffer for the specified session SHALL be cleared.
vpp43_2016-02-26.docx