The BMENOP0300 module supports the M580 redundancy function. In an M580 redundancy system, the primary and standby PACs continuously exchange data including the state RAM of the two BMENOP0300 modules.

Use the IP address xx.xx.0.xx to validate a redundant configuration, then rebuild your Control Expert project.

SCADA:

In an M580 redundancy system, the primary PAC performs SCADA functions in the same manner as a standalone PAC. The standby PAC does not communicate with SCADA, but does monitor PAC memory each scan and generates reports.

On switchover, the primary PAC closes the connection with SCADA; the standby PAC starts to listen for and accept new connection requests from SCADA. The former standby PAC, now the primary, first applies the data values received from the former primary to its local database, and then begins to perform SCADA functions after a SCADA connection is established.

Report Functions:

On every PAC cycle, the two BMENOP0300 modules synchronize the buffered report Entry ID value. After switchover, confirm that SCADA explicitly sets the Entry ID to the BMENOP0300 module in the new primary PAC so that the module can continue to send buffered reports. If the Entry ID is not synchronized, or if synchronization is not successful, the oldest reports are re-sent during switchover buffer time. In this case, SCADA can detect if it has received a duplicated event report by comparing the report time tags.

The Integrity Period setting can be used in a redundant system to generate buffered and unbuffered reports on both primary and standby BMENOP0300 modules. We recommend you not use this feature.

GOOSE:

Only the BMENOP0300 module in the primary PAC can publish GOOSE transmissions.

The BMENOP0300 modules in both the primary and standby PACs receive GOOSE data from the remote IED. However, the data received by the standby PAC is not added to memory, but is only added to the local database.

On switchover, the BMENOP0300 module in the standby PAC takes over the task of sending GOOSE. However, the stNum and sqNum fields are not synchronized.

Connection with Remote IED:

Only the BMENOP0300 module in the primary PAC communicates with the remote IED; the BMENOP0300 module in the standby PAC does not establish a connection with remote IED.

The BMENOP0300 modules in both the primary and standby PACs synchronize data out values from PAC memory to the local database. However, because the standby PAC doesn't send output data to the remote IED, the remote IED receives output data only from the BMENOP0300 module in the primary PAC.

GOOSE:

The BMENOP0300 modules in both the primary and standby PACs receive GOOSE data from the remote IED. However, the data received by the standby PAC is not added to memory, but is only added to the local database.

Report Functions:

It is recommended to automatically enable the report function for buffered and unbuffered report control blocks by setting the AutoEna field to 1 (auto enable). After switchover, the BMENOP0300 module sets the Entry ID to the remote IED and automatically enables the report when establishing a connection with the remote IED.

Switchover:

On switchover, the BMENOP0300 module in the primary PAC closes the connection with remote IED; the BMENOP0300 module in the former standby PAC, now the primary, begins to communicate with remote IED.

If the execution of a report control block/GOOSE command, polling command, or control operation is interrupted by a switchover, the high byte of the Status element for that object returns a detected error bit. It is recommended to add an error handling procedure to your program logic that will manage this detected error by re-sending the command.

Use the following formula to determine the BMENOP0300 module IP address recovery time in a M580 redundancy system:

500 ms (IP address swapping) + connection establishment time (3 s)