> For the complete documentation index, see [llms.txt](https://docs.jcore.io/clarity-gateway/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.jcore.io/clarity-gateway/connections/ethernet-ip/sending-values-to-ethernet-ip.md).

# Sending values to EtherNet/IP

In this example we'll configure Clarity Gateway to send the value of an Iron Pi analog input to an EtherNet/IP connection.

## Read / Write channels

Read / Write channels are read from the device on every scan cycle, but can also be written in response to a user or software command. This is useful for control setpoints and other user-settable values.

To enable read / write behavior on a channel, set up a "From EtherNet/IP" channel, and then turn on the "Settable" switch in the channel settings.

{% hint style="info" %}
Read / Write EtherNet/IP channels are available in Clarity Gateway version 5.6.0 and higher.
{% endhint %}

## Channels To EtherNet/IP

In contrast to Read / Write channels, Channels To EtherNet/IP write data from a Clarity Gateway internal tag to an EtherNet/IP tag on every scan cycle.

In the page for your EtherNet/IP connection, scroll down to the **Channels To EtherNet/IP** section. Click the **Show Detected** switch if it is not already on:

![](/files/kCOn1Qqomuqd1qAQ6Qmw)

All EtherNet/IP tags you can send to will then appear in the table. In this example we'll be sending to **Real Tag 1**:

![](/files/mfcXc4HXWopYzSDmwdy7)

First check the **Enabled** checkbox to enable this mapping:

![](/files/AVQsOfx0A1squAyUTgvF)

Then enter the **System Tag** to send values from. In this example we'll use **channel1:**

![](/files/InHWIwiUHv4EtQk1BOFA)

Finally, click **Save:**

![](/files/DnRhOQqoQ8vReBY2HVrP)

Once the mapping is applied, the arrow should change color from gray to blue to indicate that the mapping is active:

![](/files/QcFqXoGcZDm2N45jIeA1)

## Advanced mapping

For more options when mapping a channel, click the `+` icon in the **Channels To EtherNet/IP** section:

![](/files/gv7u5HkG4GLhxGEVvuHQ)

This will take you to a separate **Create Channel** page. In that page, first enter the Clarity Gateway **System Tag** you would like to send to MQTT. In this example, we'll be using **channel1**, which is configured as a Local I/O analog input:

![](/files/Jy4qALdCaODLSvgM3DSD)

Optionally, you can enter a **Slope** and **Offset** to transform the values that get sent to EtherNet/IP. In this example we will enter **2** and **3**:

![](/files/a8JAXuw4R1OlX9dRnB5j)

Finally, enter the **EtherNet/IP Tag** to send to. In this example, we'll send values to **Real Tag 1**:

![](/files/jL07y8bytgSz1gR44rqX)

Finally, click **Save** to create the channel:

![](/files/1bi4iPJvRmQVMrQ2QqZ5)

Once the channel has been created, you will return to the connection page. The new channel should appear in the **Channels To EtherNet/IP** table.

![](/files/WIsRaEGNEwBZk4NJb44U)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.jcore.io/clarity-gateway/connections/ethernet-ip/sending-values-to-ethernet-ip.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.