Creates the reader endpoint of a network stream.
Time, in milliseconds, that this endpoint waits to connect to the other endpoint.
Default: -1 — The endpoint waits indefinitely.
Size of the reader buffer in number of elements. The minimum size is one element.
Name of the endpoint.
Organizing Multiple Endpoints
You can organize multiple endpoints by adding segments to this name to ensure that you connect each writer endpoint to its corresponding reader endpoint. To do this, place a slash between each segment of the name that you specify in your inputs with the organization scheme of your choice.
For example, RT Target/Temperature/Writer and Desktop/Temperature/Reader describe the target the endpoint resides on, the type of data the endpoint streams, and whether the endpoint reads or writes data, allowing you to show which endpoints correspond to one another.
Error with Reused Endpoint Names
If you specify a name that already belongs to another endpoint on the same computer, the first endpoint runs and is created, but the second endpoint returns an error that you can see in error out.
Endpoints that Run Multiple Applications
If this endpoint resides on a computer that runs multiple applications using network streams, you must assign an endpoint URL to this endpoint instead of a name. This node returns an error in error out. Use the following syntax to prompt a connection between the endpoints and avoid this error: //host_name:context_name/endpoint_name.
The URL of the writer endpoint you want to connect to.
Creating a Network Stream
You must designate a writer for your reader endpoint to create a network stream. You can create this network stream in the following ways:
If you do not wire the writer url of the Create Network Stream Reader Endpoint node or the reader url of the Create Network Stream Writer Endpoint node, your endpoints will not create a network stream and your nodes will wait for a connection indefinitely.
Data type of the network stream. This data type must match the data type input on the Create Network Stream Writer Endpoint node.
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.
Default: No error
Allocates buffer memory when the endpoint is created. Specifying an allocation mode only affects the transfer of non-scalar data types.
Name | Value | Description |
---|---|---|
allocate as needed | 0 | Allocates the required memory to store each data element as the element enters the buffer. |
pre-allocate | 1 | Allocates initial buffer memory based on the element wired to the data type input, which determines the amount of memory allocated for each element. |
Selecting an Allocation Mode
Default: allocate as needed
The reference to the reader endpoint.
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.
Use the following URL syntax to connect to an endpoint on a remote computer running one application:
//host_name/endpoint_name
URL Components | Inputs |
---|---|
host_name | 10.0.0.62 |
endpoint_name | reader |
Use the following URL syntax to connect to an endpoint on a remote computer that runs multiple applications:
//host_name:context_name/endpoint_name
URL Components | Inputs |
---|---|
host_name | 10.0.0.62 |
context_name | Application 2 |
endpoint_name | reader |
Use the following URL syntax to connect to an endpoint on a local computer that runs multiple applications:
//localhost:context_name/endpoint_name
URL Components | Inputs |
---|---|
localhost | localhost |
context_name | Application 2 |
endpoint_name | reader |
Where This Node Can Run:
Desktop OS: Windows
FPGA: Not supported
Web Server: Not supported in VIs that run in a web application