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, IP-IO Smoke Control, MP-C Smoke Control, MP-V Smoke Control
Functionalities: Smoke Control
Product version: 2022, 2023, 2024

EcoStruxure BMS Smoke Control for BACnet MS/TP

The EcoStruxure smoke control system supports the MP controllers and IP-IO modules mentioned previously in this guide. For more information, see EcoStruxure BMS Smoke Control for MP Controller IP Controls .

Along with those EcoStruxure system products and configuration, the smoke control system also supports the b3 and MNB family of BACnet MS/TP controllers. All three of the AS-P/AS Smoke Control Server models have provided integrated support for these MS/TP controllers since the original system Smoke Control listing. All of these controllers continue to communicate directly wth the Smoke Control Servers to which they are connected regardless of the introduction of the IP level controllers described previously. For more information, see EcoStruxure BMS Smoke Control for MP Controller IP Controls .

The system engineer has the ability to pass BACnet variables between the IP level and MS/TP level controllers as needed using the standard variable binding and application program features common to both families.

MS/TP System Network Tier

The EcoStruxure BMS smoke control system is constructed with two primary networking tiers. At the top is the IP network which interconnects all the Smoke Control Servers, MP controllers, Workstation(s) and optional other Enterprise and Report Servers. The EcoStruxure BMS provides a second tier of communications networks that connect below the Smoke Control Servers. Up to two RS-485 token passing BACnet MS/TP networks are supported from each Automation Server or AS-P server via Channel-A and Channel-B. Each of the two BACnet network ports support up to 127 MS/TP field controllers.

Either of the two RS-485 channels (A or B) on the Smoke Control Servers can be configured for the following:

  • BACnet MS/TP field bus (as discussed in this section)

  • Infinet (i2) field bus (AS-P-SMK only)

  • Modbus protocol interface (for the FSCS)

    In a smoke control system, one Smoke Control Server will be assigned to manage the FSCS using one of the two RS-485 ports on that Smoke Control Server. The port will be configured for the Modbus protocol to communicate with the FSCS panel. For more information, see FSCS Basics .

The following figure presents a simple diagram of the two tier architecture. It does not show the MP controller IP level controls described previously in the guide. The MP controllers can optionally be applied in any of the system configurations described in the document

action_zoom_plus_stroke Two tier network

Two tier network

When using a UL 864 listed fire alarm panel (FAP) with an IP network interface, the FAP resides on the IP network and sends alarm information via BACnet/IP to the Smoke Control Server acting as the FAP manager (AS-SMK 1 or AS-P-SMK 1 in the figure). The same Automation Server or AS-P server may also manage the FSCS panel through the Modbus channel. The BACnet/IP connection is supervised from the Smoke Control Server (AS-SMK 1 or AS-P-SMK 1). The Modbus connection is supervised from the FSCS. The two other Smoke Control Servers (#2 and #3) show the second MS/TP network tier of the system with two BACnet MS/TP buses extending down from AS-SMK 2 (AS-P-SMK 2) and AS-SMK 3 (AS-P-SMK 3). These buses connect to the family of field controllers (b3 and MNB Series) listed in this guide.

System Diagram

With Ethernet networks, you cannot achieve the interconnection between the Smoke Control Servers, FAP and Workstations without additional Ethernet communications equipment. In a smoke control system, the communications required to execute the applications can only pass through equipment included within the UL 864 system listing. To support the IP network with smoke control systems, the EIS series Ethernet switch products discussed in this guide are approved to interconnect the smoke control IP products.

The following diagram presents a collection of these system elements:

  • EIS Series Ethernet Switch

    Fiber optic models allow operation through extended distances with EMI immunity. The 8 port copper only versions can be used with smaller networks

  • Automation Server 1 (AS-SMK 1), or AS-P server 1 (AS-P-SMK 1) manages and supervises the BACnet/IP connection to the Fire Alarm Panel

  • Automation Server 1 (AS-SMK 1), or AS-P server 1 (AS-P-SMK 1) manages the Modbus connection to the FSCS panel

  • Automation Server 2 (AS-SMK 2), or AS-P server 2 (AS-P-SMK 2) manages two MS/TP channels of b3 field controllers and provides a collection of Central IO modules. The 10 fully configured models are listed. All of the models ending with H are available without the H providing the same I/O without the manual override Hand-Off-Auto control on the front.

  • Automation Server 3 (AS-SMK 3), or AS-P server 3 (AS-P-SMK 3) manages two MS/TP channels of MNB and b3 field controllers

  • Field Controllers Buses lists all BACnet MS/TP models approved for the EcoStruxure BMS smoke control application

action_zoom_plus_stroke Example smoke control system dialog diagram

Example smoke control system dialog diagram

The BACnet MS/TP bus serving the controllers performing smoke control must not be connected directly with any non-UUKL listed products. When non-UUKL products need to be connected with the MS/TP network for general purpose HVAC comfort control application, one of the following two options can be used:

  • Connect the non-UUKL product to a separate/isolated MS/TP channel on a Smoke Control Server. For example, the B channel port on a Smoke Control Server could be used to connect non-UUKL products while the A channel is used with the b3 and MNB series products performing smoke control applications.

  • Connect a b-Link Repeater to any MS/TP channels from the Smoke Control Servers and connect the non-UUKL products on one of the separate ports on the b-Link. That port used to service non-UUKL product must not be used for connecting to any controller participating in the smoke control application. Additionally, when there is a tiered structure with additional b-Link Repeater(s) connected downstream on segment(s) from the initial b-Link Repeater, the segment(s) connecting between b-Link Repeaters must not be connected to any non-UUKL products.

In the following figure, Automation Server (AS-SMK 1), or AS-P server (AS-P-SMK 1) shows an example of using the two ports to isolate non-UUKL products, while Automation Server (AS-SMK 2), or AS-P server (AS-P-SMK 2) shows the application of a b-Link Repeater to segment and isolate an MS/TP bus. The b-Link provided bus segments can be used for UUKL products or non-UUKL products, but both must not be mixed on the same copper segment.

action_zoom_plus_stroke Connection of Non-UUKL Listed Products

Connection of Non-UUKL Listed Products

The MS/TP bus operates at serial data transmission rates of 9600, 19200, 38400, or 76800 bps. Most system installations are installed using 76,800bps. In some installations, however, it may be necessary to lower the speed to 38,400 bps due to the effect of cable characteristics, cable length or node count.

Smoke Control System Configuration - Example

The following figure presents an example smoke control system configuration used to develop the application programs for UL 864 system testing and evaluations. The system is presented here simply as a reference associated with features, requirements, and restrictions that must be observed when configuring a compliant smoke control system.

action_zoom_plus_stroke EcoStruxure Building Operation smoke control system configuration example

EcoStruxure Building Operation smoke control system configuration example

The controllers and other products comprising the example are all represented with boxes. The product model number is shown in blue text. The magenta text lists the smoke control equipment references in the example smoke control application. A number of application programs based on this sample system configuration are provided elsewhere in the smoke control system design guide. For more information, see Basic Application Functions .

  • Smoke Control Operational Overview
  • Basic Application Functions
  • EcoStruxure BMS Smoke Control for MP Controller IP Controls
  • FSCS Basics