> For the complete documentation index, see [llms.txt](https://kb.motion.cloud/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kb.motion.cloud/motion-platform-software/devices/add-a-modbus-device.md).

# Add a Modbus Device

## Prerequisites <a href="#prerequisites" id="prerequisites"></a>

To successfully add your Modbus TCP devices into Motion, make sure:

* You've already activated a Motion Hub with which you want to associate your BACnet device
* The Motion Hub and the BACnet device are connected to the same local area network and the network is not blocking communication between the Motion Hub and the BACnet device

## Adding a Modbus TCP Device <a href="#adding_a_modbus_tcp_device" id="adding_a_modbus_tcp_device"></a>

Every Modbus TCP Device will need to be manually entered.  Every Modbus TCP device requires an IP Address and a Slave ID, and in the steps below we will instruct users on how to do this.

### **Step 1**: Navigate to "Add Devices" view <a href="#step_1-_navigate_to_-add_devices-_view" id="step_1-_navigate_to_-add_devices-_view"></a>

| Steps                                                                                      | Screenshots                      |
| ------------------------------------------------------------------------------------------ | -------------------------------- |
| From anywhere in the Motion Platform, click "Controls" on the left-hand side vertical menu | ![](/files/ghIe1ToBBieSyyWmOqCV) |
| Under the Controls menu, click "Devices"                                                   | ![](/files/ejJ73D7oxxuLx68P9N3o) |
| Click "Add Devices" tab                                                                    | ![](/files/6QimcrLwFmYar1bhIDzb) |

### **Step 2**: Navigate to "Add Device Manually" view <a href="#step_2-_navigate_to_-add_device_manually-_view" id="step_2-_navigate_to_-add_device_manually-_view"></a>

| Steps                                                                       | Screenshots                      |
| --------------------------------------------------------------------------- | -------------------------------- |
| Click on the "Manual Entry" option, located inside of the Modbus TCP window | ![](/files/EzFY3iTHhLFrNDeVt5Wh) |

### **Step 3**: Input Modbus TCP device details <a href="#step_3-_input_modbus_tcp_device_details" id="step_3-_input_modbus_tcp_device_details"></a>

You are now in the "Add Device Manually" view for a Modbus TCP device.  You will now input the following information in the following sections:

1. Motion Hub
2. Name
3. Local IP Address
4. Protocol
5. Modbus Slave ID
6. Save/Revert

| Inputs                                                                                                                                                                                                                                                                                          | Screenshots                      |
| ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------- |
| <h4 id="motion_hub">Motion Hub</h4><p>Select the Motion Hub associated with the device to be added.</p><p></p><p>Click on the Motion Hub section to view the pop-up menu of connected Motion hubs </p><p></p><p>Search for or click on the preferred Motion Hub that will read this device </p> | ![](/files/4AsiXVX2k7XDTU9eR0BK) |
| <h4 id="name">Name</h4><p>Give your new device a name that will make it easily identifiable on the platform </p><p><br>Input the desired name in the section below</p>                                                                                                                          | ![](/files/MkVGDnOCFBf12Z2AMpiS) |
| <h4 id="local_ip_address">Local IP Address</h4><p>Locate the Local IP address provided by the device manufacturer. </p><p><br>Input the Local IP address in the appropriate section  </p>                                                                                                       | ![](/files/pBgWBQwYPTBtVnftucYU) |
| <h4 id="protocol">Protocol</h4><p>Make sure the protocol name reads "Modbus TCP".</p><p><br>If not, click on this section and choose "Modbus TCP"</p>                                                                                                                                           | ![](/files/msmZuKq8nWG3HUoblsnT) |
| <h4 id="modbus_slave_id">Modbus Slave ID</h4><p>Locate the Modbus Slave ID which will be provided by the device manufacturer in the user manual.</p><p><br>Input the Modbus Slave ID in the section below</p>                                                                                   | ![](/files/p5Xsn3DIGsvqRtsGb3qr) |
| <h4 id="save-revert">Save/Revert</h4><p>Make sure everything is correct, and click the "Save" button</p>                                                                                                                                                                                        | ![](/files/LzWrYxRilyybO9IefFZ0) |

<br>


---

# 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:

```
GET https://kb.motion.cloud/motion-platform-software/devices/add-a-modbus-device.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
