user_standard Log on
Log on to rate and give feedback 1 2 3 4 5 Log on to rate


Products: AS-P Smoke Control, Automation Server Smoke Control, MP-C Smoke Control, MP-V Smoke Control
Functionalities: Smoke Control
Product version: 2.0

EcoStruxure BMS Smoke Control for MP-X IP Controls

EcoStruxure Building Management for smoke control includes a wide variety of hardware controllers, I/O modules, and a family of software products. EcoStruxure Building Operation refers to the software running in the Smoke Control Servers, Enterprise Servers, Report Servers and Workstations. The EcoStruxure BMS is an integrated solution for building management that combines environmental control, energy management, energy monitoring/metering, alarm management, security and reporting. The system can be customized for building management applications extending from small office buildings to skyscrapers and office, school, or industrial campus environments.

IP System Network Layers and MS/TP Network Tiers

The EcoStruxure BMS smoke control system is constructed with two primary networking tiers. At the top is the IP network which interconnects all of the new IP level controllers (MP-C, MP-V, IP-IO, etc.), the Smoke Control Servers, Workstation(s) and optional other Enterprise and Report Servers. The BACnet/IP interface option for the Fire Alarm Panel (FAP) also operates at the top tier if contact interface to the FAP is not used. There are several configuration and flexibility options available on the IP network level associated with how the MP-X IP controllers are connected to the system. Refer to the immediate following sections for more detail on this subject.

The EcoStruxure BMS also continues to support a second tier of communications networks that connect below the Automation Servers or AS-Ps. This 2 nd tier of networking refers to either the BACnet MS/TP network or the Infinet (i2) network. Both of those 2 nd tier network options use an RS-485 electrical interface. Each AS-P Smoke Control server supports one or two of the MS/TP and/or Infinet network interfaces with the two RS-485 interfaces provided on the Smoke Control Servers. The earlier model Automation Server (AS) does not support Infinet which requires the model AS-P. The following discussion is focused on the MP-X IP level controllers, and is applicable when installing a system combination with either MS/TP networks or Infinet i2 controllers.

For more information, see EcoStruxure BMS Smoke Control for BACnet MS/TP .

For more information, see EcoStruxure BMS Smoke Control for Infinet i2 .

As briefly described above, each of the MP-X IP controllers provides two Ethernet ports. These ports deliver Ethernet protocol and switch capabilities that provide the installer with several options when configuring the Ethernet network interconnecting the MP-X controllers and connecting to the Smoke Control Servers chosen to host the selected set of MP-X controllers. These capabilities and options are discussed in the following sections.

AS-P-SMK and MP-X (-SMK) Ethernet Ports


Be aware that references to the MP-X also include IP-IO versions of the platform.

Each AS-P and MP-X device provides two ethernet ports. The MP-Xs and AS-Ps contain an embedded, configurable, 2 port Ethernet Switch. These devices can be configured with the switch active to allow port 2 to be used as a switched access to the primary smoke control IT network present on port 1. The device uses a single IP address. On both the AS-P and MP-X, port 2 may be disabled to disconnect any further Ethernet connections on port 2.

The AS-P has an additional mode where it can be configured for Dual IP addresses with the second address applied to port 2 and no Ethernet switch functions. In this mode, port 2 provides the option of an isolated or private network for MP-X controllers to be connected or chained. The private network may be operated with static IP addresses manually assigned to each controller, or a simple automatic assignment of IP addresses (Auto-IP). Optionally, AS-P port 2 can be configured to act as a DHCP server for the private smoke control network. Devices not listed in this document may not be installed anywhere along the daisy-chain Ethernet linkage to all controllers performing smoke control functions during system operation.

action_zoom_plus_stroke Ethernet ports and IP addressing

Ethernet ports and IP addressing

MP-X Network Architectures: Flat vs. Layered

The MP-X Ethernet network can be configured in a flat architecture where all controllers reside on the IT Network (Smoke Control Network). Here, the controllers either directly connect to a port from one of the approved multi-port Ethernet switches on the IT Network; or alternatively the controllers connect directly to a previous AS-P server (or MP-X controller) that passes through a switched connection to the IT Network as shown in the following figure.

The approved EIS series Ethernet switches can be linked together with copper or fiber cables to extend the smoke control IT network over the facility area as required to achieve all IT Network connections to the servers and controllers.

The MP-X Ethernet network may also be configured in a layered architecture where an AS-P is directly connected to the IT Network with port 1 and port 2 is arranged in Dual IP mode. Here, the AS-P does not provide Ethernet switch functions and instead creates a new private or isolated IP network. One or more MP-X controllers can be connected in a daisy-chain topology to the AS-P created private network. With the AS-P servers operating as smoke control zone managers, this layered scheme may be a convenient method for isolating the MP-X communications and cabling for the controllers being managed (hosted) by the AS-P server as shown.

Either method can be applied or a combination of the two can be used instead. This combination is referenced as a Hybrid architecture.

action_zoom_plus_stroke Flat and layered network architectures

Flat and layered network architectures


The IT Network referenced here is the primary smoke control network created with the interconnection of one or more of the approved Ethernet switches across the facility. It must not depend upon any connections to non-UL-864 listed devices. For example, while a port from an approved smoke control switch may be connected to a switch port on the general IT network to support Workstation supervision and system monitoring or support, the smoke control system and its operation must not depend on any external services (for example, a DHCP server). Static IP address assignments are required for the smoke control devices residing on the primary smoke control IT Network.

IP Configuration Examples

The IP network in the currently-listed smoke control system is propagated through a facility with a collection of EIS series Ethernet switches. Typically, it is recommended you use the model with 6 copper ports and 2 fiber ports with the fiber ports used to interconnect the switches in a daisy-chain arrangement. This arrangement shown in the following figure which presents some examples of network configuration options with the MP-X IP controllers.

As shown in the figure, copper port 1 of EIS switch #1 (left-hand switch) feeds the main IP network Ethernet to a single MP-X controller (#1). This one-on-one switch connection to a EIS switch port can be used where practical throughout the system. Normally, the dual IP ports of the MP-X controllers are used to daisy chain multiple MP-X IP controllers to a single port on an EIS switch such as shown in the connection to port 2 of EIS switch #1. This EIS port serves the IP network to the MP-X controllers in a daisy-chain connection (MP-X # 2 – 6 in the figure).

action_zoom_plus_stroke IP control Ethernet network layers in smoke control

IP control Ethernet network layers in smoke control

Many MP-X controllers may be connected directly or indirectly through the daisy chain to the IP network where needed in the facility. The MP-X controllers must be discovered and hosted by one AS or AS-P Smoke Control Server in the system. Typically, the MP-X is hosted by a server responsible for managing the functions performed by the respective MP-X and takes on the responsibility for supervising the communications integrity to each of its hosted MP-X controllers.

Copper port 3 on EIS switch #1 connects the IP network to the AS-SMK #1 in the sample system. Since the model AS-SMK only has a single Ethernet port, the MP-X controllers hosted by the model AS-SMK (if any) must achieve a switched connection to the IP network. The MP-X IP network connection for those managed by an AS-SMK should typically be achieved with an EIS port such as switch-1 port-5 as shown in the figure.

Fiber port #2 on switch 1 connects the IP network to EIS switch #2 in the figure. This can be done through several meters or up to 2000 meters of fiber. Copper port 1 on EIS switch #2 connects the IP network to the AS-P-SMK #2 in the example system. Since model AS-P-SMK #2 provides dual Ethernet ports, multiple connection options are available for the MP-X controllers being hosted and managed by the AS-P. The top portion of AS-P graphic represents Ethernet port 1 and the bottom represents Ethernet port 2.

Optionally, the AS-P may host the MP-X(s) in the same manner as described previously for the model AS with the MP-X controllers making individual or daisy-chain connections to the EIS Switch ports. However, the AS-P is frequently installed in the same general area of the MP-X controllers it is hosting and managing. Use of the 2 nd Ethernet port on the AS-P may be advantageous for connecting the subordinate MP-X controllers.

In the previous figure, a daisy-chain linkage of MP-X controllers is shown connecting to port 2 of the AS-P-SMK #2. In the example, the dashed blue line from port 1 to port 2 on the AS-P indicates that the AS-P is configured to provide a switched Ethernet connection between port 1 and port 2. This causes the AS-P to use only a single IP address and makes all of the port 2 connected MP-X controllers appear on the primary IP network. This may be useful if most of the MP-X controllers are to be hosted and managed by the AS-P to which they are connected, but one or more of the MP-X controllers need to be hosted by another AS or AS-P Smoke Control Server elsewhere on the primary IP network.

Copper port 5 on EIS switch #2 connects the IP network to the AS-P-SMK #3 in the sample system. Here, the AS-P is configured in dual IP Mode creating an isolated IP network off port 2. All MP-X controllers connected to port 2 must be hosted and have their communications integrity supervised or managed by that AS-P. The figure shows the isolated LAN as a single daisy chain of MP-X controllers (#17-21). This private LAN may utilize additional EIS series switches if it is advantageous to configure the private LAN as a Star or Tree configuration, instead of a single contiguous daisy chain. In other words, AS-P port 2 may connect to an EIS 8 port switch and then star out in 7 directions on the other 7 ports of the EIS switch.


Adding other EIS switches on the spokes of the star from the original switch ports changes it to a Tree (or distributed star topology).

IP Network Topology Limits

The IP network is extremely flexible and supports a very large capacity of IP level controllers. To stay within tested design and loading guidelines, it is recommended that the system configuration observe the following capacity limits.

  • 50 MP-X controller maximum per daisy chain

  • 39 MP-X controller limit for daisy chain (Preferred)

    The smaller limit is recommended when support for the future introduction of RSTP protocol is an objective. This will be available when a managed switch is UL 864 recognized and approved for use in the system.

  • 50 MP-X controllers per model AS-SMK

  • 200 MPX controllers per model AS-P-SMK

EcoStruxure BMS Software

The EcoStruxure BMS software is an open architecture platform operating in the Windows PC environment. It provides a friendly, comprehensive, and customizable set of tools that control and monitor the facility management system through the IP network and MS/TP networks. The software includes graphics editing for creating customized graphical displays to provide easily interpreted presentations of the information monitored in the facility and accommodate central management and control of the equipment in the facility.

The smoke control system does not depend on these resources to operate. However, it can use them to assist in diagnosing faults reported on the FSCS panel. For more information, see FSCS Basics .


While the term EcoStruxure BMS refers to the whole suite of hardware and software products, it is worth noting that the Workstation, Enterprise Server, Report Server or WebStation, which may exist on the IP network, do not participate in the execution of smoke control applications and are not depended upon to transport smoke control communications.

The WorkStation and servers are an integral part of the overall HVAC facility management system and are used to monitor and manage systems operation including the smoke control applications. After engineering and programming of the smoke control applications within the Smoke Control Servers, IP Level controllers (MP-X) and field controllers, the EcoStruxure BMS provides password restricted access to the Automation Servers and controllers responsible for smoke control applications.

IP Network Connection Requirements

The IP network provides the main communication bus throughout a facility. The EIS series Ethernet switches are installed around the facility as needed to achieve the distributed port connections for the Automation Servers, or AS-Ps and other IP network components. The network connections used for the smoke control application cannot make use of any other communications devices other than the UUKL recognized EIS Series switches and other IP network products listed in this guide.

Category 5 or 6 twisted pair cables with RJ-45 connectors should be used for connecting to the Ethernet port(s) on the Automation Server, AS-P, or MP-X IP controllers. The recommended maximum cable length is 100 meters (330 feet).


When using the earlier Automation Server (AS-SMK), its Ethernet port must connect to an EIS series switch located in the same room and the CAT 5/6 cable must not extend outside the room where the Automation Server is located. This is a UL 864 compliance restriction placed on the AS-SMK due to EMI sensitivity and the need for the ElectroMagnetic Interference (EMI) protection offered by the EIS switch. This restriction only applies to the discontinued model AS-P and not to any of the other IP level products listed in this guide.

All of the ports on the EIS series switches provide isolation from the other ports. A fault on one port will not affect the other ports. The spare 10/100BASE-T ports on the EIS series switches (fiber and copper models) can be used to connect with non-UUKL devices such as Workstations, servers and 3rd party products used within the building automation system.


For compliance with UL 864 system listing, the products that are not UUKL listed and the EIS ports serving those products must not be used to execute smoke control system applications. The smoke control system must operate with or without their connection, or failure of those products.

Further information on the IP Network Ethernet switches mentioned here and the option for an IP level BACnet/IP fire alarm panel are discussed in the following section of this guide. Specifically, it provides more detailed information on a system with the b3 and MNB family of BACnet MS/TP controllers. For more information, see EcoStruxure BMS Smoke Control for BACnet MS/TP .

A subsequent section then describes the system configuration with the Infinet i2 family controllers. For more information, see EcoStruxure BMS Smoke Control for Infinet i2 .

Note here that nothing has changed with these controllers in regards to the smoke control system described in this document and the support provided for them in the Smoke Control Servers. Either of the two 2 nd tier controller networks (BACnet MS/TP or Infinet) still extend from either one or both of the two RS-485 ports provided by the model AS-P-SMK. The same is true for the model AS-SMK with the exception that the Infinet (i2) protocol is not supported in the AS-SMK software. The AS-SMK only supports BACnet MS/TP and/or Modbus. In the previous section discussing the MP-X IP controllers, the RS-485 ports were not referenced. However, the MS/TP, Infinet and Modbus capability discussed in the following sections can be used along with MP-X IP level functions.

  • EcoStruxure BMS Smoke Control for BACnet MS/TP
  • EcoStruxure BMS Smoke Control for Infinet i2