Concept
AS-P and AS-P-NLS Installation
The AS-P-SMK and AS-P-NLS-SMK use the model TB-ASP-W1 for mounting. To install the AS-P on the terminal base, follow these instructions:
Position the AS-P directly to the right of the first (leftmost) PS-24V power supply module on the series I/O bus structure
Slide the TB-ASP-W1 terminal base to the left in the DIN rail and mate it together with the TB-PS-W1 power supply terminal base
Connect the various Central IO modules to the right side of the TB-ASP-W1 base
The AS-Ps have three communication ports which must be configured for use with the smoke control system. In a smoke control system, the Ethernet port is the primary communications channel connecting through the EIS Series switches (hubs) to the other AS-P servers and MP controllers in the system, the BACnet/IP port of the Fire Alarm Panel (FAP), and the host Workstation(s) for configuration and supplemental system monitoring.
The AS-Ps Servers also provide two RS-485 communication ports. In a smoke control system, these two ports are used to communicate with the b3, MNB, or i2 series controllers or the FSCS panel. Typically, only a single FSCS panel is configured in the system and one of the AS-P servers is assigned the function of managing the FSCS panel and configuring COM-A or COM-B for the Modbus protocol for the FSCS.
The two AS-P Servers include 12 terminals (#1 to #12) along the top of the terminal base. Two separate plug-in terminal blocks are provided on the top of the AS-P server to permit you to easily disconnect and connect the two RS-485 channels (A and B).
Terminals 3 and 4 provide 5 V power for RS-485 biasing, while terminals 1 and 2 and 5 and 6 provide RS-485 communications.
On the AS-P-SMK server, terminals 8 and 9 provide RS-485 communications for connecting to a twisted pair network with LON controllers and terminals 11 and 12 that allow the connection of the FTT-10 Free Topology Transceiver LON network. In the EcoStruxure BMS smoke control system, the LON networks and controllers are available only for HVAC comfort controls and must not be applied to any portion of the smoke control system.
All terminations on the two AS-P Servers are associated with serial data communications. All circuits are Power-Limited.
You connect the RS-485 twisted pair bus from the b3 or MNB controllers to the terminals on the three-position and four-position terminal blocks that plug into the receptacles on the top of the unit on the AS-P server. These terminals are numbered 1 through 7. For the COM-A RS-485 bus, you connect the MS/TP TX/RX+ and TX/RX- signal wires to terminals 1 and 2 respectively. You connect the cable shield to the earth ground in the enclosure. For the second RS-485 bus (COM-B), you connect the MS/TP TX/RX+ and TX/RX- signal wires to terminals 5 and 6 respectively, and the cable shield to ground. Terminal 4 supplies a 5.0V output which you can use for the RS-485 network bias when required.
The direct connected RS-485 bus cable can be up to 4000 feet in length. You must connect the MS/TP bus in a direct daisy chain fashion (cable running from one node to the next) with no cable stub connections directly to the main bus. You can connect an RS-485 repeater to extend the length or accommodate stub connections.
See the discussion on repeaters.
See also the section on cable routing and cable type recommendations.
The RS-485 port serving the b3 and MNB controllers is configured for the following:
BACnet MS/TP
Data Rate: 9600 to 76,800bps
Format: 8 Data bits, No Parity, 1 Stop bit
The MS/TP communications path is supervised from the AS-P Server. The AS-P application program must be configured to monitor the integrity of communications to the b3 and MNB controllers and continuously report the status of the network connection to all smoke control system controllers. This status information is continuously collected by the AS-P/AS Server operating as the FSCS manager and the server program must indicate a System Comms Fault on the FSCS panel if a loss of communications occurs with any smoke controllers.
The RS-485 ports used to provide MS/TP bus connections to the smoke control system b3 and MNB series controllers must be isolated from connections to other devices that are not part of the UL 864 listing.
You can connect other non-UL 864 MS/TP products in two ways.
1) You can select a separate MS/TP port from an AS-P Server to handle non-listed controller products not partipating in the smoke control system. The separate RS-485 channel from the AS-P server provides the isolation from non-listed products. You must not connect MNB and b3 controllers partipating in the smoke control system to the bus serving the non-listed products.
2) You may connect an MS/TP bLINK repeater on an MS/TP bus serving smoke control applications. You can use a far-side branch port from the repeater to connect non-listed MS/TP BACnet product(s) to the AS-P Server (AS-P-SMK). The AS-P must not include the non-listed controller in the smoke control applications. The non-listed controller will be part of other building automation and comfort control systems. The repeater requirements are discussed in the sections that follow.
You connect the RS-485 twisted pair bus from the i2 controllers to the terminals on the three-position and four-position terminal blocks that plug into the receptacles on the top of the unit on the AS-P server. These terminals are numbered 1 through 7. For the COM-A RS-485 bus, you connect the Infinet 2 TX/RX+ and TX/RX- signal wires to terminals 1 and 2 respectively. You connect the cable shield to the earth ground in the enclosure. For the second RS-485 bus (COM-B), you connect the Infinet 2 TX/RX+ and TX/RX- signal wires to terminals 5 and 6 respectively, and the cable shield to ground. Terminal 4 supplies a 5.0V output which you can use for the RS-485 network bias when required.
The direct connected RS-485 bus cable can be up to 4000 feet in length. You should connect the Infinet 2 bus in a continuous, daisy-chain, bus configuration. You can connect an RS-485 repeater to extend the length or accommodate stub connections.
See the discussion on repeaters.
See also the section on cable routing and cable type recommendations.
The RS-485 port serving the i2 controllers is configured for the following:
Infinet 2 protocol
Data Rate: 19,200bps
Format: 8 Data bits, No Parity, 1 Stop bit
The Infinet 2 communications path is supervised from the AS-P server (AS-P-SMK and AS-P-NLS-SMK). The AS-P application program must be configured to monitor the integrity of communications to the i2 controllers and continuously report the status of the network connection to all smoke control system controllers. This status information is continuously collected by the AS-P/AS Server operating as the FSCS manager and the server program must indicate a System Comms Fault on the FSCS panel if a loss of communications occurs with any smoke controllers.
The RS-485 ports used to provide Infinet 2 bus connections to the smoke control system i2 series controllers must be isolated from connections to other devices that are not part of the UL 864 listing.
You can connect other non-UL 864 Infinet 2 products in two ways:
1) You can select a separate Infinet 2 port from an AS-P Server to handle non-listed controller products not partipating in the smoke control system. The separate RS-485 channel from the AS-P Server provides the isolation from non-listed products. You must not connect i2 controllers partipating in the smoke control system to the bus serving the non-listed products.
2) You may connect an Infilink Repeater on an Infinet 2 bus serving smoke control applications. You can use a far-side branch port from the repeater to connect non-listed, i2 protocol product(s) to the AS-P Server. The AS-P must not include the non-listed controller in the smoke control applications. The non-listed controller will be part of other building automation and comfort control systems. The repeater requirements are discussed in the sections that follow.
You can configure either of the two COM-A and COM-B ports for the Modbus protocol and use them for communications with the FSCS panel. The Modbus interface uses the same RS-485 interface. For the COM-A RS-485 bus, you connect the Modbus TX/RX+ and TX/RX- signal wires to terminals 1 and 2 respectively. You connect the cable shield to earth ground (terminal 3 if mounted in FSCS enclosure).
For the second RS-485 bus (COM-B), the Modbus TX/RX+ and TX/RX- signal wires connect to terminals 5 and 6 respectively, and the cable shield connects to ground (terminal 7 if mounted in the FSCS enclosure). Terminal 4 supplies a 5.0 V output which you can use for RS-485 network bias when required.
The RS-485 port serving the FSCS is configured for the following:
Modbus protocol
Mode: Modbus Slave
Data Rate: 9600 to 38,400bps
Format: 8 Data bits, No Parity, 1 Stop bit
The FSCS communications cable is supervised from the FSCS panel. A break in that connection will be indicated on the FSCS panel by the FSCS COMM FAULT visual indicator and the audible horn. For more information, see FSCS Basics .
The AS-P Server (AS-P-SMK) can be configured with either MS/TP or Infinet 2 on one channel and Modbus on the other channel independently.
When using either the COM-A or COM-B port, connect one of the shield terminals (3 or 7) to the earth ground rail in the enclosure using 16 AWG wire or larger.
The direct connected RS-485 bus cable can be up to 4000 feet in length. There is no repeater approved for use in the smoke control system with the Modbus protocol. Since it is only a one to one connection, and it will typically involve a relatively short connection from the Smoke Control Server to the FSCS, a repeater is not needed. The Modbus protocol may be used on other AS-Ps handling applications such as HVAC comfort control and electrical metering.
The RS-485 Modbus port selected for the FSCS management must not be connected to any other Modbus devices. The only Modbus device defined for use in the smoke control system is the FSCS panel.
You can use any standard CAT-5 or CAT-6 Ethernet cables with RJ-45 modular connectors to connect the network switch to Ethernet Port 1 located along the bottom of the AS-P Server. The standard cable distance limit on the 10/100 BASE-T connection is 100 meters.
This cable connection must be from the AS-P Server to one of the EIS series UL 864 approved Ethernet Switch/Hub units listed in this guide.
The other 10/100 BASE-T ports on the EIS hub can extend for the standard 100 meter length when connecting to other EIS hubs, other AS-P/AS Servers, MP controllers, or to the BACnet/IP interface of the Fire Alarm Panel. The fiber optic versions of the EIS hubs are recommended to support extended cable distances and provide robust Ethernet communications with immunity for EMC in the environment.
The single USB host port on the AS-P server (adjacent to the Ethernet port) provides the standard USB 2.0 Type-A port connection. They are used to supply optional memory and/or communications interface options. These options are not used within the EcoStruxure BMS smoke control system application.
The AS-P Server provides a USB device port on the face of the unit below the RS-485 LEDs. This is a miniature USB 2.0 Type-B port connection. This port is used for connection through a USB cable (up to 3 meters in length) to a maintenance/diagnostic PC for commissioning functions such as installation of firmware when the Ethernet connection is not usable. The USB device port is not used within the EcoStruxure BMS smoke control system application.
Terminal Base Installation
Power Rating
PS-24V Power Supply Module
Automation Server Installation
Central IO Module Installation
FSCS Basics
Module and MP Controller Status LEDs