# Communication Studio 5000 with HMI Ignition

**URL:** <https://forum.inductiveautomation.com/t/communication-studio-5000-with-hmi-ignition/109620>\
**Category:** Ignition\
**Tags:** rockwell\
**Created:** [August 11, 2025, 10:09pm UTC](https://forum.inductiveautomation.com/t/communication-studio-5000-with-hmi-ignition/109620 "2025-08-11T22:09:45Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Automation\_AO](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@Automation\_AO](https://forum.inductiveautomation.com/u/Automation_AO)\
**Post date:** [August 11, 2025, 10:09pm UTC](https://forum.inductiveautomation.com/t/communication-studio-5000-with-hmi-ignition/109620/1 "2025-08-11T22:09:45Z")

</div>

Hi everyone,

I’m working on a proposal to migrate a PLC from L55 to L81E and replace the WinCC supervision system with one developed in Ignition. I have a question about the communication between Studio 5000 and Ignition: I understand it must be through an OPC server, but is it necessary to install and license FactoryTalk Linx or RSLinx, or would Ignition’s built-in OPC/driver be enough to communicate between the PLC and the Ignition HMI?

Thanks in advance 🙂 .

---

<div class="post-metadata">

**Author:** ![Transistor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/transistor/32/3380_2.png) [@Transistor](https://forum.inductiveautomation.com/u/Transistor)\
**Post date:** [August 11, 2025, 10:13pm UTC](https://forum.inductiveautomation.com/t/communication-studio-5000-with-hmi-ignition/109620/2 "2025-08-11T22:13:00Z")

</div>

> [@Automation\_AO](#):
>
> I have a question about the communication between Studio 5000 and Ignition:

Studio 5000 is the software package used to program the Rockwell PLCs. You don't want Ignition talking to Studio 5000. You want it to talk to the PLC (which is what you asked later in the question).

Ignition's native drivers talk to the A-B PLCs.

---

<div class="post-metadata">

**Author:** ![robertm](https://avatars.discourse-cdn.com/v4/letter/r/ea5d25/32.png) [@robertm](https://forum.inductiveautomation.com/u/robertm)\
**Post date:** [August 12, 2025, 1:11am UTC](https://forum.inductiveautomation.com/t/communication-studio-5000-with-hmi-ignition/109620/3 "2025-08-12T01:11:42Z")

</div>

As Transistor said, the native Ignition Logix driver talks to Control Logix PLCs. Just be sure you study the best practices for communicating to Logix PLCs in regards to AOIs (avoid direct reference), UDTs, Tag Groups, et al.

> [@Ignition & Logix Best Practice Tips for better communications](https://forum.inductiveautomation.com/t/ignition-logix-best-practice-tips-for-better-communications/60386):
>
> Hi All, After a whole bunch of issues I have gone down the rabbit hole of what is wrong with our setup on site. I will preface this by saying I a relatively new to all of this.... so be gentle stuck_out_tongue Based on much reading(such wow) I believe I have a list of things our site could take away for a better system. Some of them are easy to implement, whilst some of them need... significant work to realize. Especially the AOI approach in point 5 expressionless Before going too far a…

Also, if this is a one off replacement, you may want to consider an Ignition Edge setup (2 clients) instead of a full blown Ignition install. Depends on what the future expansion plans would be.