# SLC 5/04 via ControlLogix Bridge Communication Performance Tips?

**URL:** <https://forum.inductiveautomation.com/t/slc-5-04-via-controllogix-bridge-communication-performance-tips/18428>\
**Category:** Ignition\
**Created:** [June 12, 2018, 5:43pm UTC](https://forum.inductiveautomation.com/t/slc-5-04-via-controllogix-bridge-communication-performance-tips/18428 "2018-06-12T17:43:39Z")\
**Posts on this page:** 1\
**Showing post:** 2

<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 12, 2018, 6:17pm UTC](https://forum.inductiveautomation.com/t/slc-5-04-via-controllogix-bridge-communication-performance-tips/18428/2 "2018-06-12T18:17:46Z")

</div>

You're kind of toast. By default, DH+ is only 57kbits/second. If all of your hardware is compatible, you can select 230k, but it is still a tiny fraction of the bandwidth available to the slowest ethernet processor. RSLogix is a bandwidth hog -- any programming activity _ **will** _ crush your comms.  
A short-term fix for some would be to swap the 5/04 for a 5/05, using the DHRIO bridge in the Logix chassis to maintain messaging access from the DH+ devices to the new Ethernet devices. When you do that, do check your comm throttles in your status file:

> [@Typical Performance between Ignition and AB SLC 5/05](http://forum.inductiveautomation.com/t/typical-performance-between-ignition-and-ab-slc-5-05/17262/3):
>
> Check “Comms Servicing Selection” and “MSG Servicing Selection” for channel 1 (S:2/15 & S:33/7). If either is set, it will crush your throughput, as only one request will be processed per scan (Comms) or per certain control flow instructions (MSG).

---

_[View the full topic](https://forum.inductiveautomation.com/t/slc-5-04-via-controllogix-bridge-communication-performance-tips/18428)._
