# Disconnected: Protocol: EIP - Unknown **URL:** \ **Category:** Ignition\ **Tags:** ignition81, perspective\ **Created:** [July 18, 2025, 12:25pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667 "2025-07-18T12:25:07Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![Anant\_Upadhyayula](https://avatars.discourse-cdn.com/v4/letter/a/e36b37/32.png) [@Anant\_Upadhyayula](https://forum.inductiveautomation.com/u/Anant_Upadhyayula)\ **Post date:** [July 18, 2025, 12:25pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/1 "2025-07-18T12:25:08Z")
Everything was working fine and no changes to the firmware or program or any ignition settings, no updates to Ignition either. ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/d/8/d82d418c3a795c077a25e04b55d75d21ad436c1d.png) ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/d/5ddcbcb9ea91a7a63db33e1b1d066c01e913e144.png) I would appreciate your help. ---
**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:** [July 18, 2025, 12:48pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/2 "2025-07-18T12:48:41Z")
Sounds like the only remaining culprits are the network components and the operating systems between Ignition and that device. You should use wireshark on the gateway to see what traffic, if any, is getting through. ---
**Author:** ![Anant\_Upadhyayula](https://avatars.discourse-cdn.com/v4/letter/a/e36b37/32.png) [@Anant\_Upadhyayula](https://forum.inductiveautomation.com/u/Anant_Upadhyayula)\ **Post date:** [July 18, 2025, 1:48pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/3 "2025-07-18T13:48:14Z")
We lost the program in the PLC. I was surprised to see that. It happen second time this month. My mind did not go there because couple of weeks ago we downloaded latest program. But anyways it is fixed now, we will keep an eye. Thank you. ---
**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:** [July 18, 2025, 2:10pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/4 "2025-07-18T14:10:17Z")
That is a rather old processor. Have you checked its lithium battery? (They only last for ~10 years.) ---
**Author:** ![Anant\_Upadhyayula](https://avatars.discourse-cdn.com/v4/letter/a/e36b37/32.png) [@Anant\_Upadhyayula](https://forum.inductiveautomation.com/u/Anant_Upadhyayula)\ **Post date:** [July 18, 2025, 2:21pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/5 "2025-07-18T14:21:14Z")
yes battery was replaced Jan-2020, atleast that is what the sticker on the PLC says. I will look into it, for now I added an alarm notification to monitor and this silent death until someone from the floor reaches out about the accuracy of the data. The goal is to get rid of this all together and move to L83-EP family controllers. Too many moving parts to do a clean cutover. ---
**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:** [July 18, 2025, 2:25pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/6 "2025-07-18T14:25:58Z")
> [@Anant\_Upadhyayula](#): > > move to L83-EP family controllers Ewwww! Selecting the "P" suffix is a _ **really** _ bad idea: > [@Ignition & Rockwell PlantPAx v5.0](https://forum.inductiveautomation.com/t/ignition-rockwell-plantpax-v5-0/94206/4): > > I would not use the built-in PlantPax instructions. At all. They are permanently constructed with no-access members, and therefore can never be optimized for efficient external access. (There are placeholders for these datatypes in all 5580 and 5380 processors, so I've already had the opportunity to analyze these. And discuss the issue in my manual's application notes.) The alternate method that FTLinx uses to assemble data blocks has limited buffer space, so won't help significantly on la… (Read the whole thing. Read all the inner links when you have the time.) ---
**Author:** ![Anant\_Upadhyayula](https://avatars.discourse-cdn.com/v4/letter/a/e36b37/32.png) [@Anant\_Upadhyayula](https://forum.inductiveautomation.com/u/Anant_Upadhyayula)\ **Post date:** [July 18, 2025, 2:31pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/7 "2025-07-18T14:31:03Z")
Thank you for sharing, I think we are stuck with it now. We got L83-EPs before we embarked on ignition. We had GEMS and Rockwell discontinued it so are best path was to move towards Plant-PAx. so I guess we will have to learn the hard way now. ---
**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:** [July 18, 2025, 2:41pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/8 "2025-07-18T14:41:48Z")
As noted, it isn't the **processor** , but the **PlantPax** that is the problem.