# Modicon TSX57 connection via ModbusTCP or Unitelway

**URL:** <https://forum.inductiveautomation.com/t/modicon-tsx57-connection-via-modbustcp-or-unitelway/75764>\
**Category:** Ignition\
**Created:** [June 30, 2023, 10:34am UTC](https://forum.inductiveautomation.com/t/modicon-tsx57-connection-via-modbustcp-or-unitelway/75764 "2023-06-30T10:34:20Z")\
**Posts on this page:** 5\
**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:** [June 30, 2023, 10:34am UTC](https://forum.inductiveautomation.com/t/modicon-tsx57-connection-via-modbustcp-or-unitelway/75764/1 "2023-06-30T10:34:20Z")

</div>

Hi, I'm trying to connect Ignition's Modbus driver to a legacy Modicon PLC :

- reference is TSX 57203 from Schneider Electric,
- equipped with an ETY 110 communication module (see details below)

In the PLC program I noticed that the Data Link Layer is set to **802.3** instead of _Ethernet_.

- Does Ignition support 802.3 communication for its Modbus TCP driver ?
- Any idea whether I should use a 3rd party driver in order to interface Ignition to this Modicon PLC ?

![communication settings](https://us1.discourse-cdn.com/inductiveautomation/original/3X/e/e/ee2524838ec12731e45c55e5c18aaf330abf72b3.png)

 ![TCP-IP communication options for TSX57](https://us1.discourse-cdn.com/inductiveautomation/original/3X/b/3/b35893837bdf6c566eee637c813a332322f5e3b5.png)

---

<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:** [June 30, 2023, 11:49am UTC](https://forum.inductiveautomation.com/t/modicon-tsx57-connection-via-modbustcp-or-unitelway/75764/2 "2023-06-30T11:49:32Z")

</div>

802.3 is modern Ethernet.

Ethernet II is some ancient variant that didn't catch on, IIRC. Ignition (and the Modbus protocol in general) doesn't care about layer 2, just layers 3 & 4 (Internet Protocol and Transmission Control Protocol).

---

<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:** [July 3, 2023, 2:54pm UTC](https://forum.inductiveautomation.com/t/modicon-tsx57-connection-via-modbustcp-or-unitelway/75764/3 "2023-07-03T14:54:42Z")

</div>

Thanks @pturmel for the clarification on 802.3

I noticed that the real struggle with my TSX device is that it can't mix both Modicon protocols (Unitelway + Modbus) on the same port.  
Currently it's configured to answer only to Unitelway requests, as you can see on the screenshot. Therefore Modbus driver won't get connected to it.

- Is there an option with Ignition to send Unitelway requests ?
- Or should I use a 3rd-party driver ?

---

<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:** [July 3, 2023, 3:08pm UTC](https://forum.inductiveautomation.com/t/modicon-tsx57-connection-via-modbustcp-or-unitelway/75764/4 "2023-07-03T15:08:51Z")

</div>

Probably need a 3rd-party driver. I've never heard of Unitelway. 🤷‍♂️

---

<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:** [July 3, 2023, 4:02pm UTC](https://forum.inductiveautomation.com/t/modicon-tsx57-connection-via-modbustcp-or-unitelway/75764/5 "2023-07-03T16:02:35Z")

</div>

Not surprising for such a rare protocol.

For Modbus, there might be an option to declare manually a Modbus chanel open to my SCADA IP. That means adding one line to the network settings of the PLC. I'll elaborate on that, and share the update.

![add_modbus](https://us1.discourse-cdn.com/inductiveautomation/original/3X/0/f/0ff49f656bed5d034490c136ab6bd61c5f0abac1.png)
