Table Of Contents

UDP Multicast Open (Write-Only) (G Dataflow)

Last Modified: December 18, 2017

Opens a UDP multicast socket with write-only access on the port you specify.

Programming Patterns
connector_pane_image
datatype_icon

net address

The network address of a network interface on the local device where this node listens for data.

  • If you do not specify a network address, the OS picks a default interface that is used to receive data. If the node is read/write and you do not specify a network address, this node sends and receives data on all interfaces.
  • If you have more than one network interface on your server, such as two Ethernet interfaces, you can specify an address so that this node listens for data only on the interface with that address.
  • If this input is on a node with write access, this is also the interface on which data will be transmitted.

Default: 0

datatype_icon

port

The local port you want to use to send and receive UDP datagrams.

datatype_icon

time-to-live

Number of routers, minus 1, to forward a datagram. The time-to-live (TTL) value applies to all datagrams sent using this socket. Setting a larger TTL value than your application requires can cause high network utilization. The following table lists the action that occurs to a multicast datagram when you specify a value for the time-to-live input.

0 The datagram remains on the host computer.
1 Hubs/repeaters and bridges/switches forward the datagram to every client on the same local subnet that subscribes to that IP address. Routers do not forward the datagram.
>1 Sends the datagram, and routers forward it through the number of layers that time-to-live is set to, minus 1. Because most routers are not configured by default to forward multicast packets, you may need to configure your router to forward multicast packets.

Default: 1

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

A network connection refnum that uniquely identifies the connection. Use this value to refer to this connection in subsequent node calls.

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

Web Server: Not supported in VIs that run in a web application


Recently Viewed Topics