# PLC protocol change over 4RF ethernet radio

**URL:** <https://forum.inductiveautomation.com/t/plc-protocol-change-over-4rf-ethernet-radio/16613>\
**Category:** Ignition\
**Created:** [January 16, 2018, 6:42pm UTC](https://forum.inductiveautomation.com/t/plc-protocol-change-over-4rf-ethernet-radio/16613 "2018-01-16T18:42:22Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![matt.turner80](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@matt.turner80](https://forum.inductiveautomation.com/u/matt.turner80)\
**Post date:** [January 16, 2018, 6:42pm UTC](https://forum.inductiveautomation.com/t/plc-protocol-change-over-4rf-ethernet-radio/16613/1 "2018-01-16T18:42:22Z")

</div>

I am changing over from MDS radios via KEP to 4RF IP radios. I’ve noticed recently that the protocol on the gateway changes and searches on its own to go from EIP (which I need) to PCCC (which causes a comm loss). I am using AB Micrologix 1100/1400 PLCs in the field. I have my timeout settings for 1 min which is more than enough. I was curious if anyone has had this issue before and what could be done to solve it.

Thanks.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [January 16, 2018, 6:45pm UTC](https://forum.inductiveautomation.com/t/plc-protocol-change-over-4rf-ethernet-radio/16613/2 "2018-01-16T18:45:29Z")

</div>

Disclaimer: I am not a PLC guy, at all.  
But I think the discussion here might help you out?

> [@PCCC protocol causing problems](http://forum.inductiveautomation.com/t/pccc-protocol-causing-problems/11651):
>
> Ignition Version 7.8.2 Java™ SE Runtime Environment (build 1.8.0\_92-b14) Java HotSpot™ 64-Bit Server VM (build 25.92-b14, mixed mode) OS : Ubuntu 14.04 Is there a way yet to stop a protocol from being used? I have an issue where remote equipment (ML1400) will loose connection because any number of accidental or purposeful reasons. The problem then becomes that Ignition will try the PCCC protocol and if the timing is right (often is) when the equipment comes back on it will connect to it usi…

---

<div class="post-metadata">

**Author:** ![matt.turner80](https://avatars.discourse-cdn.com/v4/letter/m/bc8723/32.png) [@matt.turner80](https://forum.inductiveautomation.com/u/matt.turner80)\
**Post date:** [January 16, 2018, 6:49pm UTC](https://forum.inductiveautomation.com/t/plc-protocol-change-over-4rf-ethernet-radio/16613/3 "2018-01-16T18:49:17Z")

</div>

Seems to still be an issue even in version 7.9.6.

---

<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 16, 2018, 6:53pm UTC](https://forum.inductiveautomation.com/t/plc-protocol-change-over-4rf-ethernet-radio/16613/4 "2018-01-16T18:53:11Z")

</div>

Try setting a connection path of 1,0.

I’d like to get a setting on the driver that lets you choose between “auto” (the current behavior) and explicitly choosing a protocol but it may not happen until Ignition 8.

---

<div class="post-metadata">

**Author:** ![doug.breshears](https://avatars.discourse-cdn.com/v4/letter/d/7c8e57/32.png) [@doug.breshears](https://forum.inductiveautomation.com/u/doug.breshears)\
**Post date:** [January 16, 2018, 7:31pm UTC](https://forum.inductiveautomation.com/t/plc-protocol-change-over-4rf-ethernet-radio/16613/5 "2018-01-16T19:31:18Z")

</div>

I dealt with this by using firewall filter (ubuntu 14.04)…

```
# iptables -t filter -I OUTPUT 1 -m tcp -p tcp --dport 2222 -j REJECT
# iptables -L -n
Chain OUTPUT (policy ACCEPT)
target prot opt source destination         
REJECT tcp -- 0.0.0.0/0 0.0.0.0/0 tcp dpt:2222 reject-with icmp-port-unreachable

```

To keep this permanently we install a package…

```
apt-get install iptables-persistent
```