# Disconnected: Protocol: EIP - Unknown

**URL:** <https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667>\
**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:** 1\
**Showing post:** 6

<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:** [July 18, 2025, 2:25pm UTC](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667/6 "2025-07-18T14:25:58Z")

</div>

> [@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.)

---

_[View the full topic](https://forum.inductiveautomation.com/t/disconnected-protocol-eip-unknown/108667)._
