Placement of the BMENUA0100 Module

The BMENUA0100 module can be placed into an Ethernet slot on the local main rack (i.e. in the same rack as the CPU) in the following configurations:

  • an M580 standalone configuration.

  • an M580 standalone Safety PAC configuration.

  • an M580 Hot Standby configuration.

  • an M580 Hot Standby Safety PAC configuration.

NOTE:

  • The BMENUA0100 module can be used with all M580 CPUs.

  • In the event a network loop is created, the BMENUA0100 module goes into NOCONF (Not configured) state. To help prevent loops and related events, when you use the BMENUA0100 control port, split the control port network and the CPU backplane network physically (via wiring splitting) and not only logically (via the subnet and subnet mask settings).

Connecting via the HTTPS Protocol

If your application experiences connection problems, check with your local IT support to confirm that your network configuration and security policies are consistent with HTTPS (port 443) access to the BMENUA0100 module IP address.

The BMENUA0100 module accepts the HTTPS connections with transport layer security (TLS) protocol v1.2 or later. For example, Windows 7 could require an update to enable TLS 1.2 to upgrade the firmware of the BMENUA0100 or access to its web site.

Installation of the BMENUA0100 Module in a Flat Network

For multiple M580 racks connected on a single subnet (i.e., a flat network architecture) that include BMENUA0100 modules with the control port disabled, install each BMENUA0100 module in a different slot number in its respective rack (except for Hot Standby configurations, where the BMENUA0100 modules are installed in the same slot number). Alternatively, it is strongly recommended that you use a router to isolate the racks and thereby avoid potential address conflicts among BMENUA0100 modules.

Adding Prefixes to Device (Role) Names in Flat Network Designs

When an architecture includes multiple BMENUA0100 modules, which communicate with other devices, such as M580 CPUs that are configured on the same subnet, it is recommended to use prefixes for the device (or role) name of all devices, including M580 CPUs. This naming convention makes it possible for BMENUA0100 modules to differentiate among the M580 CPUs, and determine which CPU is placed on which rack. This naming convention helps eliminate uncertainty relating to a flat network design. For example, without unique prefixes, a BMENUA0100 module cannot determine which M580 CPU it should communicate with for retrieving its own configuration after an application download.

The device name prefix can be set in Control Expert in the tab Tools > Project Settings > Configuration.

Access to the BMENUA0100 embedded OPC UA Server

In the topological architectures described in this chapter, the BMENUA0100 communication module Ethernet backplane port and its control port can be used to provide access to the OPC UA server embedded in the module. For a description of when these ports can be used to access the embedded OPC UA server, refer to the descriptions of the Control port and the Ethernet backplane port in the topic External Ports.

Maximum Number of BMENUA0100 modules per Configuration

The maximum number of BMENUA0100 modules supported in an M580 configuration are:

M580 Configuration Type

Maximum Number of BMENUA0100 Modules

Standalone

Two (2) in the local main rack for both standalone1 and Hot Standby1,2 standard and safety configurations.

Safety PAC

Hot Standby

Hot Standby Safety PAC

1. When two (2) BMENUA0100 modules are used in a main rack:

  • Performance of each module will be slower than if a single module had been used.

  • Enable the control port in the configuration for both modules.

2. In Hot Standby designs, place the BMENUA0100 module(s) in the same slot number(s) in the respective local main racks.

Change Configuration on the Fly (CCOTF)

The BMENUA0100 module does not support CCOTF.