Ask Me About Webinar: Data Center Assets - Modeling, Cooling, and CFD Simulation
Join our 30-minute expert session on July 10, 2025 (9:00 AM & 5:00 PM CET), to explore Digital Twins, cooling simulations, and IT infrastructure modeling. Learn how to boost resiliency and plan power capacity effectively. Register now to secure your spot!
Use this portal to submit your innovative ideas to make Geo SCADA Expert and Devices such as SCADAPack, Trio and Realflo of greater value to you and to the SCADA & Telemetry community. Every idea will be individually reviewed by our team for merit and will be marked Under Consideration.
Search in
I want to convert a customer's Allen Bradley PLC points to Ethernet/IP and eliminate the OPC server that is using Ethernet/IP, however they have quite a few PLCs that have DF1 addresses like N16:11/16 and Geo SCADA's driver doe not support those.
In the OPC server's driver that DF1 identifier ends up being 'usable' via CIP because CIP allows for tunneling of other data, so DF1 can be encapsulated within a CIP message. It's called PCCC. Thanks @BevanWeiss for explaining this to me.
So it would be great if PCCC support was added to the Ethernet/IP driver so more Allen Bradley PLCs can be communicated to directly.
Link copied. Please paste this link to share this article on your social media post.
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.