GPIB Write Function

Writes data to the GPIB device identified by address string.

Right-click the node and select Synchronous I/O Mode»Synchronous from the shortcut menu to write data synchronously.


icon

Inputs/Outputs

  • ci32.png timeout ms (488.2 global) —

    timeout ms specifies the time, in milliseconds, that the function waits before timing out.

    The operation aborts if it does not complete within timeout ms. To disable timeouts, set timeout ms to 0.

    To use the 488.2 global timeout, leave timeout ms unwired or set the input to –1. Then use the SetTimeOut function to change the default value of timeout ms. The default is 10000.

  • cstr.png address string —

    address string contains the address of the GPIB device with which the function communicates.

    You can input both the primary and secondary addresses in address string by using the form primary+secondary. Both primary and secondary are decimal values, so if primary is 2 and secondary is 3, address string is 2+3.

    If you do not specify an address, the functions do not perform addressing before they attempt to read and write the string. They assume you have either sent these commands another way or that another controller is in charge and therefore responsible for the addressing. If the controller is supposed to address the device but does not do so before the time limit expires, the functions terminate with GPIB error 6 (timeout) and set bit 14 in status. If the GPIB is not the Controller-In-Charge, do not specify address string.

    When there are multiple GPIB controllers that LabVIEW can use, a prefix to address string in the form ID:address (or ID: if no address is necessary) determines the controller that a specific function uses. For example, to set GPIB controller 2 to talk to a device on address 3, use the prefix 2:3. If a controller ID is not present, the function defaults to controller (or bus) number 0.

  • cstr.png data —

    data is the data the function writes to the GPIB device.

  • ci16.png mode (0) —

    mode indicates how to terminate the GPIB Write.

    This input accepts the following values.

    0Send EOI with the last character of the string.
    1Append CR to the string and send EOI with CR.
    2Append LF to the string and send EOI with LF.
    3Append CR LF to the string and send EOI with LF.
    4Append CR to the string but do not send EOI.
    5Append LF to the string but do not send EOI.
    6Append CR LF to the string but do not send EOI.
    7Do not send EOI.
  • cerrcodeclst.png error in —

    error in describes error conditions that occur before this node runs. This input provides standard error in functionality.

  • i1dbool.png status —

    status is a Boolean array in which each bit describes a state of the GPIB Controller.

    If an error occurs, the function sets bit 15. GPIB error is valid only if bit 15 of status is set.

    The following table shows the numeric value and symbolic status of each bit in status. This table also includes a description of each bit.
    Status BitNumeric ValueSymbolic StatusDescription
    01DCASDevice Clear state
    12DTASDevice Trigger State
    24LACSListener Active
    38TACSTalker Active
    416ATNAttention Asserted
    532CICController-In-Charge
    664REMRemote State
    7128LOKLockout State
    8256CMPLOperation Completed
    124096SRQISRQ Detected while CIC
    138192ENDEOI or EOS Detected
    1416384TIMOTimeout
    15-32768ERRError Detected
  • ierrcodeclst.png error out —

    error out contains error information. This output provides standard error out functionality.

    • When you transfer data from or to a hardware driver synchronously, the calling thread is locked for the duration of the data transfer. Depending on the speed of the transfer, this can hinder other processes that require the calling thread. However, if an application requires that the data transfer as quickly as possible, performing the operation synchronously dedicates the calling thread exclusively to this operation.

    Note In most applications, synchronous calls are slightly faster when you are communicating with 4 or fewer instruments. Asynchronous operations result in a significantly faster application when you are communicating with 5 or more instruments. The LabVIEW default is asynchronous I/O.

    Examples

    Refer to the following example files included with LabVIEW.

    • labview\examples\Instrument IO\GPIB\Simple GPIB.vi