# 2 modbus requesters on the same client IP targeting the same modbus server IP

**URL:** <https://forum.inductiveautomation.com/t/2-modbus-requesters-on-the-same-client-ip-targeting-the-same-modbus-server-ip/73698>\
**Category:** Ignition\
**Created:** [May 14, 2023, 11:01pm UTC](https://forum.inductiveautomation.com/t/2-modbus-requesters-on-the-same-client-ip-targeting-the-same-modbus-server-ip/73698 "2023-05-14T23:01:27Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Marc.Akoto](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marc.akoto/32/19291_2.png) [@Marc.Akoto](https://forum.inductiveautomation.com/u/Marc.Akoto)\
**Post date:** [May 14, 2023, 11:01pm UTC](https://forum.inductiveautomation.com/t/2-modbus-requesters-on-the-same-client-ip-targeting-the-same-modbus-server-ip/73698/1 "2023-05-14T23:01:27Z")

</div>

Hi, I have the following config, and I would like to have your advice :

- On system with IP1 : 2 modbus clients (2 different SCADA systems)
- On system with IP2 : 1 modbus server (the machine PLC)
- The modbus link in Ignition tend to disconnect every one and then

I know it's not the best option to have 2 SCADA coexist on the same host, and I'm requesting a separate system for this purpose. But in the meantime, to run my testings, this system (IP1) is the only one from which I can access all PLC and industrial LAN.

Here's my question :  
When both clients send modbus requests at the same time, is there a way to avoid conflicts, and make sure the response will get to the proper requester ?

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [May 14, 2023, 11:34pm UTC](https://forum.inductiveautomation.com/t/2-modbus-requesters-on-the-same-client-ip-targeting-the-same-modbus-server-ip/73698/2 "2023-05-14T23:34:12Z")

</div>

If this is Modbus TCP there should be no conflicts unless the server you’re communicating with has a broken implementation.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [May 15, 2023, 12:11am UTC](https://forum.inductiveautomation.com/t/2-modbus-requesters-on-the-same-client-ip-targeting-the-same-modbus-server-ip/73698/3 "2023-05-15T00:11:51Z")

</div>

Check if the machine PLC has a setting for how many modbus TCP clients are allowed.

If it is not modbus TCP, then you will need a **modbus gateway** device to manage the traffic.

---

<div class="post-metadata">

**Author:** ![Marc.Akoto](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/marc.akoto/32/19291_2.png) [@Marc.Akoto](https://forum.inductiveautomation.com/u/Marc.Akoto)\
**Post date:** [May 15, 2023, 12:15am UTC](https://forum.inductiveautomation.com/t/2-modbus-requesters-on-the-same-client-ip-targeting-the-same-modbus-server-ip/73698/4 "2023-05-15T00:15:41Z")

</div>

Got it, it's Modbus TCP, so I'll check the implementation/limitations on the modbus server side.  
thanks fo your guidance @Kevin.Herron @pturmel