Emerson Exchange 365

Using an original 14.3.0 firmware is pretty old and had some known issues with certain devices, so it's actually surprising that it works there and not with the latest. That being said, without a lot of information on your setup, what you are talking to, what types of errors you are seeing in diagnostics, etc, it's difficult to guess, but the one most common thing that I see people overlook is that with a redundant PK or EIOC, the redundant node has an IP address that is one more than what is configured. For example, if you configure 192.168.1.1, the redundant is going to be 192.168.1.2. This can sometimes trip people up. First, they might overlap (which I believe now has a warning), but the other thing that happens is if a device can only support a single scanner in read write mode, it doesn't always like a redundant setup (though in 14.FP2, PRP is supported to alleviate this).

Sorry for not a lot of help in the post, but if you have any more details about what you are seeing, it might help us troubleshoot better. In cases of Ethernet/IP, a wireshark trace is always the best help as you can examine the actual packets and what error message they are producing best.

There was a major change in the PK controller's IOP port connectivity from v14.3.0 to subsequent versions.  This required that such an upgrade had to be done offline.  

So I'm wondering if the port assignments were affected, or need to be redefined.  Check the port properties to make sure the Ports you are using are isolated from the DeltaV network assignments.  

Above, the left shows only the top ports of the IOPs is enabled.  In the middle all three ports on each IOP are independent.  Not saying this is what you need, (it is not) but make sure to check this is configured correctly.

The Right image is the P01 advanced properties and you need to ensure you've bound the protocol to the right Ethernet ports.  

The Ethernet IP protocol is widely used.  Given that you came from the 14.3.0 version and the change in behavior of the IOP's, this is likely the source, but you'll have to confirm.  Let us know.

Andre Dicaire

In reply to Andre Dicaire:

Hi Andre Dicaire  Matt Forbis 

Thank you for the response!

To add more on the setup, this is a development system with a simplex PK controller. I had connected my Ethernet/IP device and Port 1 of IOP to a network switch which was then connected to my PC.

I had read the KBA regarding the upgrade process for PK controller and followed it.

After the firmware upgrade, I enabled Port 2 on the IOP and connected my device directly to the IOP with P01 assigned to Port 2. Port 1 is on the DeltaV network and connected to my PC.

          

The device settings below are unchanged from previous configuration where it was working correctly.

  

In reply to Chaitanya Adkar:

It looks to me like everything you have there is a valid configuration and should work (without knowing specifics about the device of course).
I also checked against the changes from 14.3.0 to 14.5 around Ethernet/IP and unfortunately, I'm not seeing anything obvious that might directly apply that could have broken something. That being said, I think unfortunately, we would probably need to see a wireshark trace between the EIOC and Device to look at why the device and/or DeltaV is not setting up a valid connection.

In reply to Matt Forbis:

 Hi Andre Dicaire Matt Forbis 

Thanks for confirming that the configuration settings look good. Just after I posted my reply yesterday, I did a reboot on the Pro+, deleted the PDT/LDT configuration and downloaded the PK controller. Then reconfigured and downloaded the PDT/LDT with same settings.

This worked (I am not sure why) and I am able to communicate with my device. I had tried this before including manually decommissioning the PK by reseating the IOPs but it didn't work then.

Unfortunately, I didn't save a Wireshark trace from when I was having issues.

Thank you for your support and providing me detailed solutions to the issue.