RNRP configuration for a single AC800M controller is required?
I have only one AC800M controller(IP: 172.16.1.1) in our project with Micro SCADA as HMI. MicroSCADA uses OPC interface with AC800M.
Q1. Do we need to configure RNRP in the above case? When exactly we need RNRP configuration? what settings I need to do?
Q2: Is it possible to have a AC800M Controller redundancy switch over when fail in CN1 cable alone. (In our project we are not using CN2 port).
When there is cable break on CN1 controller(U), it has to switch automatically to L controller.Is this configuration possible?
Voted best answer
RNRP is "Required" for communications between the controller and the AC800M OPC Server. So it is used even if you are not using 800xA or Compact HMI. RNRP is built in to the base AC800M ethernet settings and is allways active in the controller.
RNRP monitors your network connections and switches over to a redundant path within a few seconds of a failure.
Of course, if you only have one network, then it probably wont make much difference. But RNRP will still give you usefull diagnostic messages about ethernet failures or intermittant loss of comms.
You can also choose to install RNRP on any computer even if an ABB HMI is not used. And honestly, it is a pretty good solution for managing any redundant network.
Note: AFAIK, RNRP works only if 800xA or CHMI 800 is used.Not sure about Micro SCADA HMI.
Answering to Question-1
As a general answer
RNRP stands for Redundant Network Routing Protocol.
From the abbreviation itself we come to know that RNRP is intended for meeting the requirements of having Redundancy in ethernet communication.In other words, an alternate path for the system 800xA/CHMI nodes to reach each other.
For RNRP to really be useful, you need to have two sets of network equiment for having physically separate networks.
For detailed info refer to 800xA Network Configuration Manual.
Removal of the ethernet cable from the port (CN1 cable on CPU-A (U)) would interrupt the communication.This interruption is registered as a fault by the controller, thereby causing a bumpless switchover to the backup(L) CPU.
I believe the 'Use CN2' option will be unchecked in control builder.
Source of Info: