Use of DeltaV PK Controllers and Siemens PLC

Hi Everyone,

I'm trying to wrap my head around the PK controller for use at a facility.  Ideally we are trying to eliminate the use of profinet couplers and VIM2 cards and talk directly to equipment.  I know the PK controller is capable of Ethernet/IP communications to devices and I believe Rockwell PLCs.

Has there been any installations or examples of using it to talk to Siemens PLC skids?  For example, getting handshaking between DeltaV and a Filling Line or lyopholizer without the use of a VIM2 card?  Also, is the PK controller capable of native OPC UA communications, or will I require an EIOC as well?

We are attempting to simplify our installation hardware and keep engineering costs lower.  With OPC, Ethernet/IP, profibus, and profinet communication protocols to bring in, I'm wondering if the PK controller is the most viable option to simplify or if we should stick with standard SX controllers and use appropriate hardware to make the connections (OPC servers, profinet couplers with VIM2).  I'm aware that for profibus either way we need the profibus cards to communicate to that equipment.

Note: we will be using DeltaV version 14.3.1.  This is a greenfield installation, so getting the basis of design correct is key, and I have all options available to me at the moment.

Christiana Spencer

  • I would recommend the PK controller.

    Anything the SX can do the PK can do better...

    when comes to integrating, CPU will play a huge role and the PK sets you up for success.

    You can add a VIM to the PK, you can't add PK to an SX. (you can replace the SX later for added expense)

    the PK currently supports OPCUA server, and cannot read from OPC servers. The EIOC is an OPCUA client for integrating data into DeltaV.

    The PK is the newest controller family with significant CPU and integration capabilities. A PK750 is 10% higher cost than SX, but will handle 750 IO with full featured library like PCSD. An SX with PCSD is limited to anywhere from 400 to 800 IO, due to CPU.

    With EthernetIO in use, PK 750 is actually lower cost than SX with VIM.

    Then there is future enhancement. The PK is poised to evolve, while the SX is not.

    Since v14.3.1 brings all three controller families to the same OS and same functionality. PK ethernet IO are natively configure.

    over all, PK controllers can reduce controller costs by 20 to 40 %, because you need fewer controllers.

    Andre Dicaire

  • In reply to Andre Dicaire:

    I was really hoping you'd chime in, Andre! Thank you very much. I am leaning heavily to the PK controller, but I'm trying to convince my colleagues it's woth it. They look at controller vs controller expense and at very little else. This provides some real numbers I can go to them with. I really appreciate it!

    Sounds like if I want to talk to Siemens I will still need a VIM, but we have a lot of Ethernet/IP devices to bring in, so I think the PK controller is the smarter option.

    Thanks!

    Christiana Spencer

  • In reply to Andre Dicaire:

    In additional Andre great recommendation, Here are a few documents that will help answers a lot of questions especially around your questions

    .white-paper-deltav-bridge-en-5943062.pdf

    PK Controller FAQ.pdf

    Let us know what is your final architecture and your solution to accomplish this.