For a given scanner, the following rules must be satisfied:

• The total number of requests (Modbus TCP) and connections (EtherNet/IP) of the active I/O profiles that appear in the Communication Mapping Views does not exceed the capacity of the scanner.

• The total number of devices (Modbus TCP and EtherNet/IP) that are scanned does not exceed the capacity of the scanner.

For details on the capacity, refer to manual of the module, which is used for scanning.

When the DHCP client of a CRA adapter module is enabled, the Identifier attribute must be correctly configured.

For a given scanner, each scanned device needs to have a unique device number independently of the communication protocol that is used by the device.

For a given module, all local slave connections of a same type (for example, Exclusive Owner ) that appear in the Local Slaves subcategory must have a unique number.

The Default Gateway/Bridge Device attribute can only be used when the scanner is a BMENOC0301/11.4 communication module.

For a given module, if two local slave connections have the same number (for example, Local Slave 1 ) but a different connection type, the values of their Default RPI T->O, Input Size, and Default RPI O->T attributes must be identical.

For BMENOP0300 modules, the values that you enter for interfaces and ports in the Topology Manager also need to be entered manually in the IEC 61850 Configuration Tool. You can open the tool from Control Expert Editor after it is installed.

For BMENOS0300 modules, the configuration of the Ethernet ports needs to be performed by using the rotary switches located on the module. Configuring Service L2 in the PROPERTIES pane has no impact.

For details, refer to the module installation and configuration guide.