# 1756-EWEB on Control Logix and AB Ignition Module

**URL:** <https://forum.inductiveautomation.com/t/1756-eweb-on-control-logix-and-ab-ignition-module/42360>\
**Category:** Ignition\
**Created:** [January 18, 2021, 3:21pm UTC](https://forum.inductiveautomation.com/t/1756-eweb-on-control-logix-and-ab-ignition-module/42360 "2021-01-18T15:21:54Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![serge.payer](https://avatars.discourse-cdn.com/v4/letter/s/848f3c/32.png) [@serge.payer](https://forum.inductiveautomation.com/u/serge.payer)\
**Post date:** [January 18, 2021, 3:21pm UTC](https://forum.inductiveautomation.com/t/1756-eweb-on-control-logix-and-ab-ignition-module/42360/1 "2021-01-18T15:21:54Z")

</div>

I have seen 2 posts on this AB Web interface Card but no clear answers…

Our Control Logix PLC will be using the 1756-EN2T EthernetIP Card (Slot 2) for Controls communications.  
To read and write data from Ignition, we plan on using the 1756-EWEB Controler.  
Question 1: Will the Ignition Allen Bradley Driver Module work with the 1756-EWEB and give us access to all TAGs on our Control Logix?  
Question 2: Would it be preferable to just select another Ethernet Controler for the PLC? Any suggestion?

Thanks in advance.

---

<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:** [January 18, 2021, 3:55pm UTC](https://forum.inductiveautomation.com/t/1756-eweb-on-control-logix-and-ab-ignition-module/42360/2 "2021-01-18T15:55:11Z")

</div>

Why would you use the 1756-EWEB instead of just connecting Ignition via the EN2T and the Logix driver?

---

<div class="post-metadata">

**Author:** ![lrose](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/lrose/32/62724_2.png) [@lrose](https://forum.inductiveautomation.com/u/lrose)\
**Post date:** [January 18, 2021, 4:08pm UTC](https://forum.inductiveautomation.com/t/1756-eweb-on-control-logix-and-ab-ignition-module/42360/3 "2021-01-18T16:08:06Z")

</div>

I believe they are saying that they plan on using the EN2T for the local control (i.e. remote I/O). It is often desirable to keep I/O traffic off of the main plant network.

That being said, why the EWEB, a 1756-ENBT would work just fine in this application unless you have a specific need for advanced networking tools such as sockets. For that matter, if you’re using a L8 series controller the connection on controller is all you need and you can forego the extra ethernet card altogether.

---

<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:** [January 18, 2021, 4:11pm UTC](https://forum.inductiveautomation.com/t/1756-eweb-on-control-logix-and-ab-ignition-module/42360/4 "2021-01-18T16:11:27Z")

</div>

When I need to separate control from other networks, I just use another EN2T (never an ENBT any more–too limited). The EWEB cannot do any class 1 communications. It is only useful if you need the web server functionality.

---

<div class="post-metadata">

**Author:** ![PAYERNAN](https://avatars.discourse-cdn.com/v4/letter/p/439d5e/32.png) [@PAYERNAN](https://forum.inductiveautomation.com/u/PAYERNAN)\
**Post date:** [January 18, 2021, 4:17pm UTC](https://forum.inductiveautomation.com/t/1756-eweb-on-control-logix-and-ab-ignition-module/42360/5 "2021-01-18T16:17:15Z")

</div>

Just like you are saying, we just want to separate both networks.  
I think I got my answers from pturmel: We will only get a second EN2T since there is no need for a Web Interface (I imagine even more access and security management to do also…)

Thanks all for your fast reply.