# Modbus address Problem with TCP/IP device

**URL:** <https://forum.inductiveautomation.com/t/modbus-address-problem-with-tcp-ip-device/74348>\
**Category:** Ignition\
**Created:** [May 31, 2023, 12:06pm UTC](https://forum.inductiveautomation.com/t/modbus-address-problem-with-tcp-ip-device/74348 "2023-05-31T12:06:17Z")\
**Posts on this page:** 4\
**Page:** 2

<div class="post-metadata">

**Author:** ![Ryan\_Allen](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_allen/32/47013_2.png) [@Ryan\_Allen](https://forum.inductiveautomation.com/u/Ryan_Allen)\
**Post date:** [May 31, 2023, 9:15pm UTC](https://forum.inductiveautomation.com/t/modbus-address-problem-with-tcp-ip-device/74348/21 "2023-05-31T21:15:08Z")

</div>

Again, IIRC, i used the proper range similar to how you have done it. But it didn't work until i matched the start address to the modbus address.

The 0-10 was meant to be an example, not the exact value i used.

---

<div class="post-metadata">

**Author:** ![sherman](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sherman](https://forum.inductiveautomation.com/u/sherman)\
**Post date:** [May 31, 2023, 9:16pm UTC](https://forum.inductiveautomation.com/t/modbus-address-problem-with-tcp-ip-device/74348/22 "2023-05-31T21:16:44Z")

</div>

Huh. Well I promise you don't have to -- here is an example of a device that is currently functioning for me:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/9/098a9c892bb29e6cb6a4dc94486cf523ff53838e.png)

---

<div class="post-metadata">

**Author:** ![Ryan\_Allen](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ryan_allen/32/47013_2.png) [@Ryan\_Allen](https://forum.inductiveautomation.com/u/Ryan_Allen)\
**Post date:** [May 31, 2023, 9:17pm UTC](https://forum.inductiveautomation.com/t/modbus-address-problem-with-tcp-ip-device/74348/23 "2023-05-31T21:17:22Z")

</div>

Good to know! Maybe i was changing a few things at a time and incorrectly associated that change as the fix.

---

<div class="post-metadata">

**Author:** ![sherman](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sherman](https://forum.inductiveautomation.com/u/sherman)\
**Post date:** [May 31, 2023, 9:18pm UTC](https://forum.inductiveautomation.com/t/modbus-address-problem-with-tcp-ip-device/74348/24 "2023-05-31T21:18:48Z")

</div>

Been there! The curse of changing multiple things at once -- often faster but leaves ambiguity as to the actual fix.

[Previous page](https://forum.inductiveautomation.com/t/modbus-address-problem-with-tcp-ip-device/74348.md?page=1)