Table Of Contents

UDP Write (UDP Write Binary) (G Dataflow)

Last Modified: March 20, 2017

Writes binary data to a remote UDP socket.

Programming Patterns
connector_pane_image
datatype_icon

port or service name

The port or name of the service you want to write to. You can specify a service name to query the NI Service Locator for the port number that the server registered. port or service name can accept a numeric or string input.

datatype_icon

address

The address of the computer where you want to send a datagram.

This input supports scalar strings and unsigned 32-bit integers.

datatype_icon

connection ID in

A network connection refnum that uniquely identifies the UDP socket.

datatype_icon

data in

The data to write to another UDP socket. In an Ethernet environment, restrict data to 8192 bytes. In a LocalTalk environment, restrict data to 1458 bytes to maintain gateway performance.

datatype_icon

timeout ms

Time, in milliseconds, that the node waits to complete before reporting a timeout error. A value of -1 indicates to wait indefinitely.

Default: 25,000 ms

datatype_icon

error in

Error conditions that occur before this node runs.

The node responds to this input according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Default: No error

datatype_icon

connection ID out

Same value as connection ID.

datatype_icon

error out

Error information.

The node produces this output according to standard error behavior.

Standard Error Behavior

Many nodes provide an error in input and an error out output so that the node can respond to and communicate errors that occur while code is running. The value of error in specifies whether an error occurred before the node runs. Most nodes respond to values of error in in a standard, predictable way.

error in does not contain an error error in contains an error
If no error occurred before the node runs, the node begins execution normally.

If no error occurs while the node runs, it returns no error. If an error does occur while the node runs, it returns that error information as error out.

If an error occurred before the node runs, the node does not execute. Instead, it returns the error in value as error out.

Where This Node Can Run:

Desktop OS: Windows

FPGA: This product does not support FPGA devices


Recently Viewed Topics