DeltaV Serial Comms To ControlLogix using a 1770-KF2 connected to a 1756-DHRIO??

Hi.

I am migrating a AB PLC5 to a ControlLogix (1756-L83).

The system currently has a DeltaV DCS Controlling all analog and PID. The DeltaV has a Serial Card connected to a 1770-KF2 (Data Highway communication Interface) connected to a PLC5 DH+ port on the Processor.

The DeltaV System is reading and writing to the PLC5.

The Delta V is staying and I don't plan to have to do much if anything to the existing DeltaV system.

Can anyone tell me if I can retain this serial comms link by leaving the DeltaV to KF2 connection as is, and connecting the KF2 to a 1756-DHRIO card which will reside in the new ControlLogix Rack?

I can map the addresses in  the ControlLogix to represent the existing PLC5 Type addresses that the DeltaV is currently talking to.

Hopefully someone has done this before and can give me confidence it will work.

Thanks

  • Have you looked at the DeltaV solution for modernizing the PLC5 to DeltaV ? Here is a video of that solution and you can find a product description here. Since there is a DeltaV already in place, this could save a lot of time in system integration. Feel free to contact me for further information and I will be happy to direct to your local sales contact in New Zealand.

  • There are many options.

    Yes, you can keep the DeltaV RS232 -> KF2 -> DHRIO -> 1756-backplane -> L83 controller, but there are two things that must be configured.
    (1) In the DHRIO, configure the CLX Controller slot number so the DH+ messages will get forwarded to the CLX controller. The default is slot 0, but adjust this to match your actual system. see p51 lvmcc-pubs.rockwellautomation.com/.../1756-UM514C-EN-P.pdf
    (2) In the CLX Controller, configure the PLC5 Mapping table so the PLC5 registers are routed to CLX array tags. see p113, literature.rockwellautomation.com/.../1756-rm094_-en-p.pdf The PLC mapping will route the following PLC files identifiers: N, B, L, & F, to INT, DINT, and REAL array types.

    You might consider RS232 to EtherNet/IP via Aparian DF Router (sold through Prosoft) where the RS232 DF1 node address is routed to the CLX controller (which is the IP address plus the CLX contorler slot number). This solution will eliminate the KF2 and DRIO. see p5 www.aparian.com/.../49-app-note-honeywell-serial-interface-setup www.aparian.com/.../df1router
  • In reply to pmhamilton:

    Thanks for the support.
    Looking at it initially it looked feasible , just wanted to run it past others who may have had similar experience.
    It gives me more confidence when recommending this to the customer. Have you seen or setup this particular scenario.?
    DeltaV RS232 -> KF2 -> DHRIO -> 1756-backplane -> L83 controller.
    I will have a look at the RS232 to Ethernet/IP solution you mentioned.
    Cheers
  • In reply to JeffH:

    I haven't done that exact scenario, but close enough. I have done PROVOX -> Intelligent Device Interface - RS232 DF1 -> KF2 -> DHRIO -> L6x. The Logix tag assess should be the same for L6/L7/L8. Prior to the Prosoft/Aparian DF1 Router, we would use the 1761-NET-ENI as the RS232(DF1) to EtherNet/IP interface. On the newer DeltaV systems, I have used the VIM or the EIOC and EtherNet/IP Class 3 Explicit messaging to the Logix controller.
  • In reply to pmhamilton:

    Excellent. Thanks again for the advice/info.
  • In reply to JeffH:

    Check out the red lion products as well. I have found them to be much easier to use than prosoft as well as have a TON more functionality for about the same price. They have a few tiers of the data station protocol converters but I have listed one below.

    Look up part number DA30D0F000000000
  • In reply to Daugenet:

    Thanks Daugenet. Sounds good so will investigate.