Emerson Exchange 365

Controller Redundancy | MD+MQ | DeltaV 13.3.1

I am looking for some help in getting my redundant controller pair back into a redundant state.

I came across a pair of controllers where the secondary controller was showing as active and the primary one had a blinking standby light. (Both controllers are MD)
In DeltaV Diagnostics under Redundancy, I found the following details.

• STBY: BAD
• OInteg : BAD
• PExist : YES
• PAvail : NO
• RedEn: YES

I assumed the controller had failed so I removed it and replaced it with a spare MQ. 
I used the controller firmware utility to bring the MQ firmware up the the same as the MD one.

After this operation, I am back where I started. 

The same status in DeltaV diagnostics and a blinking standby light on the new MQ controller. 

Is there another step or something I can check?

Invalid String

• 9 Oct 2024 8:22 PM
• Cancel

4 Replies

• Rune Reppenhagen

  

  • 10 Oct 2024 1:23 PM

  I suggest you contact our Global Service Center to have them diagnose the issue and guide you in resolving it.
  
  Regards,
  Rune

  • Cancel
• Andre Dicaire

  

  • 10 Oct 2024 3:02 PM

  Redundant partner is seen by the Active controller, and the Standby is not getting configured. that is it has not successfully received its download from the Pro Plus.
  
  The redundancy is seen as enabled, which may indicate the redundancy license is properly assigned. You can confirm this by doing a changed setup download. If not properly licensed, you'll get a message to that effect.
  
  That leaves me thinking the Network cables may be switched. The Commissioning activity is done through a broadcast or in the case of a redundant pair, it is handled by the Active controller, which advises the Pro Plus it has a new Standby, and the Pro Plus assigns the Standby the proper Ethernet addresses. The standby resets and comes up as the standby. At this point the IP addresses take effect and if the networks are swapped, the controller cannot receive its download. But it does indicate communication is good in the diagnostics, so it may not be this.
  
  From the Pro Plus, you should be able to ping the standby address at 10.5.0.86 and 10.9.0.86. If this returns valid connection, then your cables are OK. Response should look the same as if you ping the active primary controller 10.4.0.86.
  
  If it is not the licensing or cables, I don't have any other suggestion. Opening a call with GSC would be my next step.

  Andre Dicaire

  • Cancel
• Jesse Delanoy

  

  • 10 Oct 2024 3:24 PM

  In reply to Andre Dicaire:

  We ran into a similar issue earlier in the year with an SQ controller pair. In our situation a logic download happened at the same time another person flashed a firmware update to the redundant controller. I don't recall the exact LED indications or diagnostics indications, but the result was similar. We tried swapping the redundant controller with a new spare at the same firmware version as the active controller with no luck. Ultimately we had to perform a full controller download to resolve the redundancy issue. I would definitely log a call with GSC as there may be a better path to resolve this issue. In our situation the controller was not actively running anything so we could be aggressive in our attempts to resolve the issue, and did not log a GSC call.

  • Cancel
• Invalid String

  

  • 10 Oct 2024 9:45 PM

  In reply to Andre Dicaire:

  Thanks Andre,
  I checked my primary and secondary connections and they are correct, I was also able to ping the standby controller from the ProPlus with no issues.
  I downloaded changed setup data to the controller and it went through without issue.
  Still in the same position.
  
  
  I know better than to believe that Andre would call the GSC.... That phone only rings one direction..
  
  
  All good.
  We have some downtime on the horizon where I can run a full controller download. I'll take a closer look at it during that time.
  
  Thanks!

  • Cancel