# Living with A-B ControlLogix v20.19 **URL:** \ **Category:** Ignition\ **Created:** [February 1, 2021, 3:34pm UTC](https://forum.inductiveautomation.com/t/living-with-a-b-controllogix-v20-19/42819 "2021-02-01T15:34:50Z")\ **Posts on this page:** 1\ **Showing post:** 6
**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:** [February 1, 2021, 5:55pm UTC](https://forum.inductiveautomation.com/t/living-with-a-b-controllogix-v20-19/42819/6 "2021-02-01T17:55:47Z")
You might also consider moving critical data traffic to a class 1 connection... (shameless self-promotion): > [@Automation Professionals' v8.1 Module Updates](http://forum.inductiveautomation.com/t/automation-professionals-v8-1-module-updates/40804/3): > > So, my Ethernet/IP module has two quite different use cases: The original case is to make an Ignition Gateway function as a virtual Remote I/O chassis that AB Logix processors could include in their I/O tree. (Or from any other brand that can scan E/IP remote I/O devices.) I/O protocols are far more robust than typical SCADA request/reply protocols over TCP/IP, so this approach alleviates the primary cause of momentary pushbutton misery. While reducing UI latencies on Ignition UIs to near-h… It is possible to move a substantial amount of tag data at blistering-fast rates (compared to a polling connection) no matter what firmware is involved. Some code required on the PLC side, though. --- _[View the full topic](https://forum.inductiveautomation.com/t/living-with-a-b-controllogix-v20-19/42819)._