# UDP Send

## Overview

![The UDP Send Node.](https://2628349686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwnv17cpjDin2deSlOz0z%2Fuploads%2Fgit-blob-47db1e5c37fa9955e0d6ece692f27dab1e26044c%2Fudpsend.png?alt=media)

**UDP Send** takes a `Message` and passes it through the currently established *UDP* *connection*. This *connection* can be set using the [UDP guideline](https://docs.incari.com/incari-studio/2023.1/toolbox/communication/udp/..#udp-guideline).

Note that if a *connection* has not been established, a new one will be attempted to be made before sending the `Message`. Because of the nature of *UDP*, this is possible and the `Message` will send after the new *connection* is established.

**UDP Communication** in **Incari** is available as a plugin and is enabled as default. However, in the case that it is disabled in the **Plugins Editor**, it will not appear in the **Project Settings** and **UDP Send** will not show up in the [**Toolbox**](https://docs.incari.com/incari-studio/2023.1/toolbox/overview). Please refer to the [**Plugins Editor**](https://docs.incari.com/incari-studio/2023.1/modules/plugins) to find out more information..

[**Scope**](https://docs.incari.com/incari-studio/2023.1/overview#scopes): **Project**, **Scene**.

## Attributes

![The UDP Send Node Attributes.](https://2628349686-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fwnv17cpjDin2deSlOz0z%2Fuploads%2Fgit-blob-96471f5a9255f6f203a77c70bbbff7eb26247b29%2Fudpsendatts.png?alt=media)

| Attribute       | Type          | Description                                                                                                                                                                                         |
| --------------- | ------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `Is Binary`     | **Bool**      | Can be toggled on or off depending on if the `Message` body is binary or not.                                                                                                                       |
| `Configuration` | **Drop-Down** | The desired *UDP* server, which refers back to the selections made under *UDP* in the [**Project Settings**](https://docs.incari.com/incari-studio/2023.1/modules/project-settings/udp-connection). |

## Inputs

| Input             | Type       | Description                                                           |
| ----------------- | ---------- | --------------------------------------------------------------------- |
| *Pulse Input* (►) | **Pulse**  | A standard **Input Pulse**, to trigger the execution of the **Node**. |
| `Message`         | **String** | The *datagram* to be sent to the endpoint.                            |

## Outputs

| Output             | Type      | Description                                                                                                                            |
| ------------------ | --------- | -------------------------------------------------------------------------------------------------------------------------------------- |
| *Pulse Output* (►) | **Pulse** | A standard **Output Pulse**, to move onto the next **Node** along the **Logic Branch**, once this **Node** has finished its execution. |

## See Also

* [Introduction to UDP Nodes](https://docs.incari.com/incari-studio/2023.1/toolbox/communication/udp/..#introduction)