Concept
EcoStruxure BMS Smoke Control for Infinet i2
In addition to the MPX IP controllers and the b3 and MNB families of BACnet MS/TP controllers, the EcoStruxure smoke control system also supports the proprietary Infinet i2 family of controllers when connected to the AS-P-SMK smoke control server. The AS-P-SMK server provides integrated support for the Infinet i2 controllers and has been part of the UL864 system listing since evaluation in 2018.
For more information, see EcoStruxure BMS Smoke Control for MP-X IP Controls .
For more information, see EcoStruxure BMS Smoke Control for BACnet MS/TP .
As with the b3 and MNB families of MS/TP controllers, the Infinet controllers continue to communicate directly with the AS-P-SMK server to which they are connected, regardless of the introduction of the IP level controllers. To meet requirements for HVAC controls and the smoke control applications, the engineer can configure the system so that the Infinet controllers are able to exchange system variables with the AS-P Script or Function Block application programs. Application variables are transferred via the system's variable binding tools to and from the MP-X IP controllers and/or BACnet MS/TP controllers.
The EcoStruxure BMS smoke control system can be constructed with two primary tiers of networks. In the first tier is the IP network, which interconnects all the Smoke Control Servers, MP-X series IP controllers, one or more WorkStations, and optionally, other Enterprise Servers and Report Servers. The second tier of communications networks, positioned below the first, connect below the AS-SMK and AS-P-SMK Smoke Control Servers. On the AS-P-SMK server, this second tier can include b3 BACnet MS/TP controllers or Infinet i2 controllers.
On the AS-P-SMK Smoke Control Server, either of the two RS-485 ports (Channel A or Channel B) can be configured for any one of these three options:
BACnet MS/TP field bus
Infinet i2 field bus (as discussed in this section)
Each Infinet bus interface supports up to 127 i2 field controllers.
Modbus protocol interface (for the FSCS)
In a smoke control system, the FSCS is managed by a Smoke Control Server, using one of the two RS-485 ports on the server. This port is 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.
When using a UL864 listed Fire Alarm Panel (FAP) equipped with an IP network interface, the FAP resides on the IP network and sends alarm information via BACnet/IP to the Smoke Control Server that is acting as the FAP manager (AS-SMK 1 or AS-P-SMK 1 in the preceding figure). In addition, the same Automation Server could also be managing the FSCS panel through the Modbus channel. The BACnet/IP connection is supervised by the Smoke Control Server (AS-SMK 1 or AS-P-SMK 1), while the Modbus connection is supervised by the FSCS. The other two Automation Servers (AS-SMK 2 or AS-P-SMK 2, and AS-SMK 3 or AS-P-SMK 3) represent the second network tier of the system, with two field buses extending down from each. These field buses connect the field controllers listed in this guide, up to the maximum allowed number.
For more information, see Infinet i2 Series Field Controllers .
With Ethernet networks, you cannot achieve the interconnection between the Automations Servers, AS-Ps, 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. For more information, see Infinet i2 Network Accessories .
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 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 1 (AS-P-SMK 1) manages the Modbus connection to the FSCS panel
Automation Server 2 (AS-SMK 2), or AS-P 2 (AS-P-SMK 2) manages two Infinet 2 channels of i2 field controllers and provides a collection of I/O 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 3 (AS-P-SMK 3) manages two RS-485 channels of field controllers
Field Controller Buses lists all Infinet 2 models approved for the EcoStruxure BMS smoke control application
The Infinet 2 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 Infinet 2 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 Infinet 2 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 i2 series products performing smoke control applications.
Connect an Infilink Repeater to any Infinet 2 channels from the Smoke Control Servers and connect the non-UUKL products on one of the separate ports on the InfiLink. 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 Infilink Repeater(s) connected downstream on segment(s) from the initial Infilink Repeater, the segment(s) connecting between Infilink Repeaters must not be connected to any non-UUKL products.
In the following figure, Automation Server (AS-SMK 1), or AS-P (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 (AS-P-SMK 2) shows the application of an Infilink Repeater to segment and isolate an Infinet 2 bus. The Infilink provided bus segments can be used for UUKL products or non-UUKL products, but both must not be mixed on the same copper segment.
The Infinet 2 bus operates at 1200, 2400, 4800, 9600, and 19200 baud. Most Infinet 2 systems are installed at 19200 baud because it is the recommended baud rate.
The following figure presents an example smoke control system configuration used to develop the application programs and submit for the 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.
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
EcoStruxure BMS Smoke Control for MP-X IP Controls
EcoStruxure BMS Smoke Control for BACnet MS/TP
Basic Application Functions
FSCS Basics
Infinet i2 Series Field Controllers
Infinet i2 Network Accessories