Event Routing

Introduction

The event routing component allows events from sub stations to be routed to SCADA within a single BMENOR2200H module.

To route events, one RTU master channel and at least one RTU outstation channel are needed inside the system. The solution is to create a logic RTU master and outstation in a single BMENOR2200H module. In the logic master, points are created to represent points in sub stations, and in the logic slave, points are created to simulate the behavior of points in sub stations. The event routing component is responsible for collecting events in the logic master. These events are sent from sub stations and trigger the same events in the logic slave.

BMENOR2200H module components:

NOTE: Event routing capabilities are possible only within a single module.

There are no automatic event routing capabilities between two BMENOR2200H modules (a slave/server and a master) that are configured in the same station.

In a hierarchical architecture, time stamped events are automatically transferred from low-end slave sub stations to the SCADA (or master) through the station. The automatic transfer uses path-through events functionality with a single BMENOR2200H module configured in both the master and outstation.

Configuration

Configure the BMENOR2200H module for event routing on the data mapping configuration page.

Considerations:

The BMENOR2200H module does not detect events for event routing points in an outstation.
There is no web page to configure event routing.
In a valid configuration for event routing points, only one point is occupied in our database to reduce the data size stored in memory. Use the device DDT to see the point and its structure in the Variables list.

NOTE: With the loss of power management, you can specify in the configuration if you want to poll more events from the BMENOR2200H modules, fallback to SCADA, and help reduce the number of lost events.

Point configuration considerations:

Configuration	Description
channel (See the note below.)	For routing events, configure one master channel and at least one outstation channel. One master channel is required so that the system can connect with more sub slaves, and more slave channels allow for more SCADA in the system. NOTE: Refer to the channel configuration instructions.
master data mapping (See the note below.)	Add data points in the master channel. These points show the mapping of master points in the sub slave which communicate with the master channel NOTE: Refer to the DNP3 data object mapping instructions.
outstation point	After you configure the points in the master channel, the corresponding point is listed in the outstation channel. The points used to route are different from the normal points of the outstation. The parameters (CPU type, CPU address, variable name, and time stamp) of CPU mapping are no longer available, and the available parameters are read only. Their lifetime is consistent with peer point configuration in the master.
NOTE: When you configure these points in the master channel, select the events of the points to be routed, and route events to the corresponding outstation channel. For example, if the master channel receives events from the sub slave Binary Input point and routes them to the logic slave channel, they become events of the Binary Input point. Considerations: When you specify one point in the master for event routing, such as the binary input point, one corresponding point configuration is automatically generated in the logic outstation channel. The point configuration for the logic outstation channel is read only; it cannot be changed or removed in its DB mapping panel. If the channel number, session number, or point number mismatches in the outstation channel, an error page appears. If you choose the route to the channel as None, the point does not need to be routed to an outstation.

Channel Combination for Event Routing

To route events inside the RTU module, use the configuration instructions to combine the master channel and outstation channel.

The supported combinations are:

Master Channel	Outstation Channel
DNP3 net client	DNP3 net server

Limitations

Events are routed inside the module. This means that it is not possible to route events between two or more modules and also that the PLC application in the CPU cannot get and process the events. (The CPU can still get the point value in events just like the standalone master channel.)
Only events are routed. Requests (commands) from SCADA are not routed to the sub slave. This means that inside the BMENOR2200H module, there is no other data exchange or communication between the master channel and the outstation channel except for events.
In the system, SCADA cannot communicate with sub slaves. The solution uses the logic outstation in the BMENOR2200H module to simulate sub slaves, so SCADA can communicate only with the logic the outstation in the BMENOR2200H module, and the sub slave can communicate only with the logic master in the BMENOR2200H module.
Some information related to events may be changed. Key information related to events like point value, flag, and time stamp is kept during event routing. Other information related to events like point number, events class, and variation is changed according to the outstation channel configuration.
For broken connections, the downstream outstation does not generate events to an upstream supervision system.

Events Buffer Size

Confirm that the events buffer of the outstation are greater than the events buffer in the sub slave; otherwise, events are lost.