Emerson Exchange 365

PK Controller

We are evaluating a SMART MCC interface to a DeltaV DCS.  

Currently I have an MX Controller that is tied to M-Series conventional I/O Cards on 8-wide carriers, for all the req’d motor controls (along with all the instrumentation I/O).  We also have a VIM2 module connected to it as we have a few devices that we will communicate with over Modbus TCP (DeltaV being the client). 

If we went with a SMART MCC, I was wondering if replacing the MX Controller/Carrier with a PK Controller/Carrier would be the optimum solution and do the trick (the DeltaV is a v14.3.1). 

The idea would be to replace the MX with a PK and tying the PK to the SMART MCC network that we would be interfacing with over an EthernetIP Protocol. 

One of the main questions I have is, how would I then handle the Modbus TCP devices? Can I natively talk Modbus TCP and Ethernet IP with the PK? I.e., can one port on the PK be set up to communicate with the SMART MCC over an EIP protocol and another port on the PK Carrier be set up to talk to devices over Modbus TCP (or is it an either/or)?  Or would I need a separate VIM or EIOC for the Modbus TCP network? Can I even hang a VIM on a PK Controller? Its white paper says a VIM2 is supported I thought, but I don’t know how you install a VIM on it (it didn’t look like you could put any connectors on the left). Or would I have to get a separate EIOC? 

Further to that, can you please clarify the 6 ports that the Carrier comes with (i.e., P01-P06).  We were looking into just a single PK Controller (non-redundant controller).  BOL mentioned the left set of ports is the ‘primary’ side and the right is the ‘secondary’ network. Does this mean if we were to only have one PK Controller, that we would only have access to the 3 on the left side? Can you have a simplex PK Controller be tied to both a primary and a secondary network (and a EIP network and a Modbus TCP network)? 

Im trying to figure out the most effective DeltaV solution with minimal hardware, for our above needs (an EIP and Modbus TCP network on same DeltaV controller). Dont have any experience really with the PK and the documentation is not very clear to me.

Thanks for the help!

imh301

• 19 May 2020 3:19 AM
• Cancel

3 Replies

• Nathan Hunt

  

  • 12 Feb 2021 7:44 PM

  imh301
  Did you get anywhere on this design?
  I am looking at a similar design as well.

  • Cancel
• Andre Dicaire

  

  • 13 Feb 2021 1:00 AM

  In reply to Nathan Hunt:

  On a v14.3.1 system, go with the PK. Processor has 4 times capacity as SX/MX. I recommend a PK750. You can definitely configure 750 IO signals without worrying that you run out of CPU.
  
  PK talks one Ethernet device protocol at a time, either Modbus TCP or Ethernet IP. The VIM also talks one protocol at a time. If you want two protocols at the same time, PK can handle one and a VIM can handle the other. If the VIM were redundant, that would be one protocol max for an MX controller. PK would provide for two with VIM.
  
  PK can be simplex or redundant. Each controller connects its primary Ethernet port to the left Ethernet Module, and the Secondary port to the Right Module. The modules are identical and it is their location on the carrier that denotes them Primary (left) (Ports 1,2 and 3) and Secondary (right)(Ports 4, 5, and 6). They are ungrouped by default, which means they are isolated for connection to different subnets. Top port is always for DeltaV comms. You bind the RJ45 ports to protocols and they keep traffic separate and dedicated to the designated ports.
  
  The VIM carrier on the PK installs to the Right of the controller. This is true for MX as well, though typically they are insalled to the Left. The rule is the VIM carrier(s) must be before the first IO carrier. So there can be two VIM carriers to the right of the PK and then your IO or and Extender cable.
  
  The question you should be asking is do I need both Modbus TCP and Ethernet IP. What are the current Modbus devices. The EIOC is intended for integrating subsystems like PLC's, or Analyzers or other monitoring systems that are not necessarily integral to the control functions. Think SCADA where the data will be consumed primarily by operators or historized. These are often Modbus and would fit quite well under an EIOC.
  
  Moters, Drives, protection relays that are used in control modules with interlocking and closed loop control would be best connected to the controller hosting the process control loops. I like Ethernet IP over Modbus TCP because of the contextual data structures, which often allow a single bidirectional mapping that. Modbus mappings often are spread out and require additional Logical Devices. But both get the job done.
  
  If you can't have all devices on the same protocol, you either need to add a VIM to the controller, or add an EIOC. Both are valid. The EIOC offers redundant communication with a simplex processor, and also redundant processor, just like PK. It has more capacity than VIM2 and is configured natively, i.e. without VIMNet explorer.
  
  If you go with the VIM, I would suggest Ethernet IP on the PK for motors and drives, and Modbus TCP on the VIM for "other" devices.
  
  The EIOC supports PRP networks, Parallel Redundant Protocol. The PK is expected to also support this in the future. This allows the redundant connections to share the same IP subnet. Simplex IP devices are connected to PRP enabled switches, and these are connected to the primary and secondary ports of the EIOC/PK. Traffic is simultaneous on both networks and so there is no delay in switchover if one network fails. You can increase overall availability of the device network connections where a single point of failure affecting multiple devices is defined by the switches used: 1 port, 4 port, 8 port or more. Furthermore, each such switch forms are separate "bus" of devices. By grouping devices appropriately, you can maintain operation even if you lose one switch. For an MCC line up, increasing the availability of the network could allow you to use the network for all command functions and remove hardwired start/stop IO.
  
  Many customers would still keep an emergency stop/shutdown command wired, but full soft control is possible even for more critical assets.
  
  Emerson has a Service team specialized in Industrial Ethernet system designs. I'd suggest you consider engaging them to help you make the best decision for your plant requirements.

  Andre Dicaire

  • Cancel
• gamella

  

  • 15 Feb 2021 6:15 AM

  In reply to Andre Dicaire:

  Andre, I was not aware of PK being capable to work with VIMs. May you direct me to DeltaV Documentation (Books on-line??) describing this??

  • Cancel