infinity smoke control guide - fire alarm resources

Andover Controls Corporation i

Infinity Smoke Control GuideElectronic Version

Controlling Tomorrow’s World

Technical Manuals Online! - http://www.tech-man.com

ii Infinity Smoke Control Guide

Version B

Reproduction or distribution forbidden.Copyright 1995, 1996 Andover Controls.

Subject to change without notice.

Order No. 30-3001-446

Copyright 1995, 1996Andover Controls Corporation300 Brickstone SquareAndover, Massachusetts 01810All Rights Reserved.

Published by the Engineering Department at Andover Controls Corporation.

IMPORTANT NOTICE

Examples in this book are for illustrative purposes only and have never been tested in an actual building.

This product is subject to change without notice. This document does not constitute any warranty, express or implied. Andover Controls Corporation reserves the right to alter ca-pabilities, performance, and presentation of this product at any time.

The following trademarks are used in this manual:

CROSSTALK is a registered trademark of Digital Communications Associates, Inc.

IBM is a registered trademark of International Business Machines, Inc.

VT is a trademark of Digital Equipment Corporation.


TOC

Chapter 1

The Fundamentals of SmokeControl

One of the most hazardous situations that you can face in a building is smoke. While fires themselves are often damaging, it is smoke that can cause the most injuries. For example, at the World Trade Towers in February 1993, over 1,000 were injured by the smoke that resulted from the fire.

To protect your building’s occupants, as well as furnishings and equipment that may be damaged by smoke, you need a smoke control system. A smoke control system, as its name implies, controls the flow of smoke in your building in the event of fire. It keeps smoke from spreading throughout the building, giving the building’s occupants a clear evacuation route, as well as preventing further damage to the building’s interior.

This chapter gives you an overview of smoke control theory.


The Fundementals of Smoke Control

1-2 Infinity Smoke Control Guide

TOC

Under standing Types of Smoke Cont rol Syst emsTwo types of smoke control systems exist—dedicated and nondedicated. The dedicated smoke control system is installed in a building for the sole purpose of controlling smoke. A nondedicated smoke control system uses parts of the building’s HVAC system to control smoke.

In most instances, a building has both nondedicated and dedicated systems. Nondedicated systems are used throughout the building for normal areas (offices, manufacturing). Dedicated systems are used for special areas, such as elevator shafts, stairtowers, and other areas that need special smoke control techniques.

The operation of the nondedicated smoke control equipment is verified by the “comfort level” in the areas that are served by the equipment. In other words, if the HVAC equipment is not functioning properly, the building’s occupants will be aware of this and the problem will get fixed.

The operation of the dedicated smoke control equipment is verified by an automatic self-test that is performed on a weekly basis.



Andover Controls Corporation 1-3

TOC

Using Pr essur e to Cont rol SmokeThe basic concept behind controlling smoke, regardless of whether it is with a dedicated or nondedicated system, is to use air pressure to confine and (if possible) vent smoke from the building.

You cannot confine smoke by simply closing all access ways (such as doors and vents) to the room that has the fire in it. Even with these passages closed off, smoke can disperse throughout a building via cracks, holes made for pipes and electrical wires, and spaces around doors and windows. Smoke is driven through these small openings by the expanding gases from the fire. Smoke can also be driven onto other floors by the stack effect, which causes air to rise in buildings. The stack effect is caused by the difference in the interior and exterior temperature of the building. The following diagram shows how smoke can disperse throughout a building.

Figure 1-1. Smoke Infilt rating Areas Adjacent to the Fire

Since smoke is carried by the movement of air, you can stop the spread of smoke throughout the building by lowering the air pressure in the area containing the fire and by raising the air pressure in the surrounding areas and floors. The difference in pressure (also called the pressure differential) between the smoke-filled area and the surrounding areas acts as a barrier to the smoke, pushing it back into the smoke-filled area. The next illustration shows how this works.

Area on Fire Adjacent AreaAdjacent Area

AdjacentArea




TOC

Figure 1-2. Air Pressu re Containing Smoke

You lower the air pressure in the smoke-filled area by shutting off all air flow into it and turning on the exhaust fans from the area to full capacity. This technique pulls the smoke out of the area and vents it outside of the building.

You pressurize the areas and floors surrounding the fire by turning off all exhaust systems (including closing any exhaust dampers) and forcing supply air to those areas at full capacity. The air in the pressurized areas tends to leak into the smoke zone, using the same cracks and holes that the smoke would use to get out. This airflow into the burning room keeps the smoke from spreading.

Areas that are neither being pressurized nor depressurized (i.e. areas far away from the fire) have both their air inlets and air return systems turned off. Turning off the air return prevents the smoke that is being vented into the return air system from coming into the area.

In cases where there are large openings (such as an open doorway) between the area on fire and an adjacent area, smoke can be confined by a large volume of air. Pumping large amounts of air through the adjacent space creates a constant draft through the opening into the smoke zone (as shown in the next illustration). The draft through the open space keeps back the smoke, confining it to the smoke zone. The amount of air required to keep the smoke from penetrating the open space is quite large, so you should avoid this sort of situation when possible.

Air PressurePositive








Negative Pressure




TOC

Figure 1-3. Keeping Smoke Away from a Large Openin g




TOC

Creating S mok e ZonesIn order to contain the smoke by using pressure, you must divide the building into smoke control zones. A floor or several floors of the building can be a single zone, or one floor can be broken into a number of zones. A zone must be separated from other zones by smoke dampers, airtight doors, and smoke-proof barriers.

When a fire breaks out, the smoke control system can then pressurize all of the zones around the one where the fire broke out (called the fire zone), isolating the smoke to that single zone.

If the smoke control system is nondedicated, the layout of the smoke control zones should take into consideration the layout of the HVAC system. You should place multiple areas served by the same VAV boxes in the same smoke control zone. Also, the smoke control zones must conform to any fire control zones that have been established, because the smoke detectors are tied into the fire detection system. Also, keeping the smoke control zones and the fire control zones the same makes coordinating the two systems simpler.

Smoke Con trol vs. Fire Contro l Systems

The smoke control system is usually separate from the fire control system, since they have different goals. The fire control system’s goal is to contain and extinguish the fire as fast as possible. These systems, which halt the fire but not the smoke, are often triggered automatically, relying on the heat of the fire to activate the system. Although smoke control systems are also automatic, you must have manual overrides for the automatic controls. Another difference between smoke control and fire control systems is that where fire control systems, such as sprinklers, often rely on only a water supply, smoke control systems usually rely on electricity to run fans and dampers. So, some smoke control systems have a standby power supply. Standby power provides the smoke control system with electricity in case the main power fails.

The smoke control system should be designed to work with the fire control system and not interfere with its operation. For instance, if the building has a sprinkler system, then the smoke control system does not need to control a large quantity of smoke, since the size of any fire should be smaller.




TOC

A smoke control system may also have to be designed to work with gas-based fire extinguishers, such as the halon gas systems installed in many computer rooms. If the smoke control system tried to vent a room with such a system, it would probably vent the fire suppressing gas as well. Removing the gas lets the fire continue burning. Also, pressurizing the areas surrounding an extinguisher equipped room reduces the effectiveness of the system as well. Air forced into the room from the outside by pressure can provide the fire with the oxygen it needs to continue burning. So, gas-based fire extinguishers and smoke control systems should not be active at the same time in the same area.

The smoke control system receives the location of the fire from the fire panel. The fire panel uses a combination of smoke and heat sensors to determine where the fire is located.

In the event that signals are received from more than one smoke zone, the smoke control system should continue automatic operation in the mode determined by the first signal received.

Smoke control systems should never be triggered by manual pull boxes. The risk of someone pulling a box someplace other than the fire zone is too high for you to trust your smoke control system to this form of activation.

All smoke control systems installed in buildings must meet the standards established by the National Fire Protection Association in their publication NFPA 92A, Smoke Control Systems, 1988 edition. You can find additional information regarding fire alarm control units in the Underwriters Laboratories Inc. Standard UL 864.




TOC

Designing a Smoke Cont rol S ystemWhat is the basic goal of the smoke control system? To maintain a tenable environment. A tenable environment allows:

• The building’s occupants to evacuate safely

• The fire fighters to get to the fire zone

The first step you take in designing your smoke control system is to lay out the smoke control zones, as previously explained. After the smoke zones are established, you have to address the following design factors:

• The zone-by-zone smoke control strategies to use

• The amount of pressure needed to contain smoke

• Proper separation between zones

• The fans and ductwork used in the smoke control system

• Dampers required for smoke control

• The air inlets and outlets used in the smoke control system

• Duct smoke detectors

Devising a Smoke Co ntrol Strategy

For each zone in your building, you have to establish a smoke control strategy. The smoke control strategy is a series of steps the smoke control system must take to contain the smoke. For each zone, you must decide:

• Whether you should depressurize the zone if a fire occurs.

• If the zone is to be depressurized, by how much you should depressurize it.

• Which adjacent zones should be pressurized and how much pressure is required.

Some zones in your building may need special consideration. As mentioned earlier, zones that have gas fire extinguisher systems should not be vented (depressurized) and the zones surrounding the fire zone with such a system should not be pressurized. You may not be able to pressurize other areas, such as hospital or animal labs, due to the risk of contaminating surrounding areas.

Consider the number of zones surrounding the fire zone that should be pressurized. While in theory, all you need to do is to pressurize all of the




TOC

zones immediately surrounding the fire zone, it is possible that smoke can find its way around the pressurized areas and infiltrate zones far away. Depending on the size of your building, and the capacity you plan to have in the smoke control system, you may decide you want to pressurize more than just the surrounding zones. But, the more zones you want to pressurize, the larger your air supply system needs to be.

Write down the state that all fans, dampers, and other smoke control equipment should be in to control smoke in each zone. Later, you have to program this information into the smoke control system. This information gives the smoke control system a strategy for containing smoke in each possible fire zone.




TOC

Determining th e Amount of Pressure NeededSince air pressure is what keeps smoke from spreading, the primary design factors are the amount of pressure that you need to confine the smoke and the size of the system used to create this pressure.

For the smoke control system to create a barrier of air pressure between the smoke zone and surrounding zones, the amount of pressure required varies with the height of the ceiling and whether or not the building has a sprinkler system. The next table shows the minimum pressure differential needed to keep smoke out of surrounding rooms.

For buildings without sprinklers and with ceiling heights not shown in the table, you can use the following formula to determine the minimum amount of pressure needed to keep smoke out:

H is the distance between the fire space and a surrounding space where

the pressure differential is zero. A figure of the floor to ceiling height

is a conservative estimate.

To is the absolute room temperature of the surrounding zones measured in °R (degrees Rankine). Typically, To = 530° R (70° F). The conversion from °R to °F is: °R = °F + 460.

Tf is the absolute temperature of the hot gases in the fire zone. It is also measured in °R. Typically, Tf is 2160° R (1700° F).

Table 1-1. Minimum Pressu re Differential to Pressu rize Fire Zone

Sprinkler System

Ceiling Height

Minimum Pressure Differential (wg)

Yes Any 0.05

No 9 ft 0.10

No 15 ft 0.14

No 21 ft 0.18

MinimumPressure 7.64 H×1To-----

1Tf----– SafetyFactor+×=

23--




TOC

SafetyFactor is a constant added to the results to make sure they are sufficient. A value of 0.03 wg (inches water gauge) is recommended.

Pressure buildup in an area depends on how much leakage there is. Leakage occurs through joints, cracks, openings for pipes and wires, gaps between doors and their door jams, and so forth. The better the zone is sealed off from its neighbors, the easier it is to maintain the required pressure. Since larger openings, like doorways that are normally open, require large amounts of air to maintain pressurization, you should avoid this type of situation.




TOC

Separating ZonesYou must separate smoke zones from one another by smoke barriers, which prevent smoke from passing through them. Smoke barriers can be a wall, a floor, or a ceiling. Any openings in the smoke barrier must be closed with a smoke-proof fitting. For example, all duct work going through a smoke barrier must have a smoke damper in it. A smoke damper is a damper that prevents smoke from passing through it when fully closed. (Refer to the dampers section below for more information.) During a smoke emergency all of the fittings should seal themselves, so that smoke cannot penetrate the barrier.

Since the smoke control zones should be the same as the fire control zones, you usually separate your zones with a fire rated partition. A fire rated partition is a wall that is built of fire resistant materials and that reaches from floor to ceiling. Different floors should be separated by a fire rated ceiling, a ceiling made of fire resistant materials. Both fire rated partitions and fire rated ceilings are rated for the amount of time they can withstand a fire. Any openings in a fire rated partition or ceiling must be sealable with a fire rated closure, such as fire rated doors or fire damper.

Selectin g Dampers

The dampers used to isolate the smoke zone must be smoke dampers. Smoke dampers are dampers that meet the requirements given in UL 555S, Standard for Leakage Rated Dampers for Use in Smoke Control Systems. Following this standard ensures that the dampers are able to block the smoke when they are fully closed. These dampers may be different from those you might use in an HVAC system that does not perform smoke control.

In a smoke control system, the dampers must be able to travel to their desired setting in 75 seconds. All dampers must be fitted with end position microswitches to provide feedback to the smoke control system. These switches let the control system know the position of the dampers, since smoke dampers are usually either fully closed or fully open.

Dampers sometimes function as both smoke dampers and fire dampers. Fire dampers are dampers that block a fire from penetrating a fire rated partition via a duct. These dampers are normally open, held in place by a fusible link. The fusible link is a heat-sensitive device that releases the




TOC

dampers when it is heated to a certain temperature. Once the fusible link releases, the dampers close by the force of gravity. So, fire dampers operate even if the electricity has failed. The specifications for fire dampers appear in the document UL555, Standard for Fire Dampers.

If you want a damper to function as both a smoke damper and a fire damper, it must meet the requirements for both devices. These dampers can be operated by electric motors or pneumatics. But it must, however, also have a fusible link or other means of closing automatically, like a regular fire damper. The control system can override the closure due to temperature. The damper needs the fusible link in case the automatic control of the damper by the control system is interrupted.

Choosin g Fans an d Duct Work

The fans and duct work used in the smoke control system must be capable of providing the amount of pressure you calculated earlier. In a nondedicated system, this may mean that you need to install fans that have a higher capacity than the HVAC system calls for. The ducts must be capable of taking the pressurization (or the depressurization, for the fire zone’s return duct) that the smoke control system will exert.

Both the fans and the ducts should meet the requirements stated in NFPA 90A, Standard for the Installation of Air Conditioning and Ventilating Systems.

Fans for a smoke control system normally do not have to meet any special heat resistance rating. In a smoke control system, fans must be able to reach the required setting in 60 seconds. Each fan must have a pressure monitor mounted so that the smoke control system can receive feedback on the status of the fan to determine whether it is actually operating or not.

In some climates, the outside air can be so cold that drawing it directly inside the building can damage the building’s interior (freeze pipes or damage temperature-sensitive equipment, for example). In these cases, some sort of preheater needs to be installed on the air inlet. The smoke control system does not have to control the heater as closely as one in an HVAC system, since maintaining comfort levels is not an issue. It simply has to make sure the air sent into an area is not going to damage the building’s interior.




TOC

Posi tioni ng Air Inlets and Outlets

You need to carefully consider the placement of the air inlets and outlets on your building. If you place an outlet that vents smoke too close to an air inlet, the air intake can draw the smoke back into the building.

Since smoke rises, the exhausts that vent smoke should be placed well above air inlets. The exhausts should be placed at least 3 ft above the roof level, to allow space for the smoke to rise and disperse.

Keeping smoke outlets far away from air inlets does not guarantee that the air brought into the building is always smoke free. You may want to place smoke detectors in air inlets that operate during a smoke emergency. If the detector finds smoke in the incoming air, it alerts the control system. The control system has to decide whether or not to shut down the air inlet.

You should refer to NFPA 90A for more information on smoke detectors in inlets and outlets.




TOC

Employ ing Dedica ted Smok e Cont rol Syst emsMost of the systems discussed so far have been nondedicated systems. Even in a building whose primary smoke control system is nondedicated, you may have special zones or functions where you need to use a dedicated system. The most common dedicated system is a dedicated smoke control system for a stairtower.

StairTo wers

Stairtowers are stairwells with a ventilation system and are isolated from the main building. The only connection between the building and the stairtower is fire-rated doors on each floor. Since the building’s occupants should use the stairtower to leave during an evacuation, keeping the stairtower smoke free is vital.

A stairtower has its own dedicated system that pressurizes the stairwell to keep smoke out. This dedicated system can take several forms, from a fan mounted in the roof of the stairtower, to a duct system that delivers air to each level.

You must pressurize a stairtower enough to keep smoke out. However, if the pressure in the stairtower is too great, then opening the doors leading into the stairtower can be difficult. You must strike a balance. The stairtower smoke control system must pressurize the stairway enough to keep the smoke out, but it must not pressurize it so much that the doors cannot be opened.

Figure 1-4. The Effec ts of Too Much and Too Little Pressur e

Too Much Pressure Too Little Pressure

Stairtower BuildingStairtower Building




TOC

Figure 1-5. Parts of a Stair tower Syste m

Fire Rated Door

StairtowerBuilding

Exhaust Fanor Vent

Supply Fan

PressureVents

AirSupplyDuct




TOC

Ensur ing Door s Can Be OpenedThe table below shows the maximum allowable pressure differential across a door in inches water gauge based on how wide the door is and how much force the automatic door closing mechanism exerts. At the pressures shown in the table, the door requires 30 lbf (pound of force) to open, the maximum limit suggested by the NFPA Life Safety Code.

The table above assumes a door height of 7 ft and a distance from the doorknob to the knob side of the door of 3 in. If your door does not meet these requirements, or has opening hardware other than a doorknob, such as panic hardware, then refer to the ASHRAE publication Design of Smoke Control Systems for Buildings for a formula to calculate the proper opening force. The door widths in the table are only valid for doors that are hinged at one end. For other types of doors, see the ASHRAE document.

Many door closers vary the amount of force as the door opens. They provide less resistance in the early stages of opening the door than they do later, when the door is almost fully open. The force to open the door shown in the previous table represents the force needed to open the door only enough to let air flow through the opening. Once air is able to flow, the force exerted by the difference in air pressure on the door lessens. Therefore, when calculating the force required to open the door, you may need to lower the door closer force.

Table 1-2. Pressur e Different ial Across Doors

Door Closer Force (lbf)

Pressure Differential for Various Door Widths (inches)

32 in 36 in 40 in 44 in 48 in

6 0.45 0.40 0.37 0.34 0.31

8 0.41 0.37 0.34 0.31 0.28

10 0.37 0.34 0.30 0.28 0.26

12 0.34 0.30 0.27 0.25 0.23

14 0.30 0.27 0.24 0.22 0.21




TOC

Cont rolling P ressure in a Stair towerStairtower smoke control systems are divided into two categories—noncompensated and compensated. Noncompensated systems simply turn on a fan to pressurize the stairtower. The fan’s speed does not change to compensate for doors opening and closing. The more doors that are open, the more the pressure differential between the stairwell and the building drops.

Figure 1-6. Compensated and Noncompensated Stair tower Syst ems

A compensated system adjusts the airflow to make up for pressure lost through open doors. It can use dampers to relieve excess pressure in the stairtower to ensure that the pressure does not go over the maximum limit.

There are a number of ways compensated stairtower smoke control systems can control pressurization. In a basic system with a roof-mounted fan blowing air into the stairtower, pressure can be regulated by varying the speed of the fan, the pitch of the fan’s blade, the inlet vanes, or the number of fans operating (assuming there is more than one).

More sophisticated systems use ducts to deliver air to several points in the stairtower. The dampers can be controlled to maintain the appropriate pressure in their zone.

Vent

Variable-SpeedFan

Constant

FanSpeed




TOC

Figure 1-7. Examples of Controllin g Stair tower Pressure

Duct systems can also use bypass dampers and ducts to control the amount of air flowing from the fan to the outlets. The bypass dampers are opened when the stairtower is at the proper pressure, so that excess air flows not into the duct system, but into the bypass duct and back to the air inlet. See the next diagram for an example of a bypass duct system.

Figure 1-8. A Bypass Pressur e Control System

Air PressureDuct

Pressurization Fan

Bypass DuctAir Intake

Bypass Duct Dampers




TOC

There are also a number of ways a compensated stairtower smoke control system can get rid of excess air pressure, to ensure that the doors leading into the stairtower can open properly. One or more vents to the building’s exterior (with dampers) can be used in the stairtower to release excess pressure. These dampers can be barometrically controlled (being forced open by the excess air pressure) or controlled by electric motors or pneumatics as in conventional HVAC systems. In both cases, the dampers must be placed far enough away from the air supply to prevent venting of air that has not yet been able to disperse through the stairtower. Vents can also lead into the building, but you should consider carefully the impact of venting extra pressure into the building before using this type of vent.

In some cases, a ground-level stairtower door can be used in place of dampers. This door automatically opens and closes to maintain the proper amount of pressure in the stairtower. The door is usually locked, for security reasons. During an emergency, the smoke control system has to be able to override the lock. Using a door in this manner has its problems, since wind effects close to the base of a building could prevent the air from escaping through the door.

Figure 1-9. Methods of Controllin g Stair tower Pressure

You can also use an exhaust fan to vent the excess pressure from the stairtower. Such a fan should be designed to operate only when the stairtower is overpressurized. It should never be on when the pressure differential between the building and the stairtower is below the lowest limit.

Roof-mounted Exhaust Fan

Automatic Door Used to Vent Pressure

Vent to Outside with Barometricallyor Automatically Controlled Dampers




TOC

ElevatorsElevator shafts present a special menace with regards to smoke control. The elevator shafts form perfect chimneys to draw smoke into the upper levels of a building. Since elevators usually have openings on each floor, and the seals on the elevator doors are often poor, the elevator shaft can become a mechanism to spread smoke throughout a building. Smoke control in an elevator shaft is an important consideration in the overall smoke control plan.

Figure 1-10. Smoke Contr ol For Elevator Shafts

If you could manage to make them safe during smoke emergencies, elevators would ease the evacuation of the building, especially for people in wheelchairs. To have the elevators usable during a smoke emergency, you need to pressurize the elevator shafts the same way you pressurize a stairtower.

However, pressurizing the elevator shaft presents a number of problems. While the elevator doors can be fitted with improved seals and rubber sweeps, these systems will not totally eliminate air leakage. Also, most elevator shafts are not designed to be pressurized. They often have large openings at the top where the cables feed into the winding room. Shafts are often constructed of porous material that cannot contain the air pressure. And since most shafts are not designed to be inspected after the elevators are installed, finding and repairing cracks that would let smoke infiltrate or pressure escape is difficult.

Pressurization Fanfor Elevator Shaft

Low Pressure AreaCreated by Elevator

Low Pressure AreaCreated by Elevator

Special SmokeProof Elevator Doors




TOC

Another primary problem with letting elevators run during a smoke emergency is the localized pressure differences that the cars create as they travel up and down the shafts. For example, a car moving down from the top of the shaft may create a small low air pressure zone near the shaft’s top, which can pull smoke from the fire zone into the shaft.

At the present time, these issues have not been resolved. Pressurizing the elevator shafts so that the elevators can operate during a smoke emergency is still being studied. In general, elevators should not be used as an escape route during an evacuation.




TOC

Detec ting SmokeThe fire control system is the system that is connected to the smoke and fire detectors. Every smoke zone should have a Listed smoke and fire detector installed in it. The detectors should be located so that they will detect the presence of smoke or fire before it spreads beyond the zone. Once the fire control system detects the fire, it relays to the smoke control system the zone and the type of alarm that was triggered. The smoke control system then takes action.

Never use manual pull stations to start the smoke control system. There is no guarantee that the person pulling the alarm is in the same smoke zone as the fire. The automatic smoke control system should take only those actions that are common to all smoke strategies when a manual pull station is activated. For example, the stairwell can be pressurized in response to a manual pull box alarm. Implementing a specific smoke control strategy must wait until the smoke detectors locate the fire zone.

Configu ring and Monitoring a Smoke Control System

The smoke control system should be able to act on its own in response to detecting smoke. When it detects smoke, the system enacts the strategy you planned out (as discussed in the design section of this article). The automatic smoke control should stick with the strategy to control smoke in the first zone that smoke is detected in. It would be difficult for you to create strategies for controlling smoke in all possible combination of zones.

The automatic smoke control system must have the highest priority over all other automatic control systems in the building. It must override energy management, occupancy schedules, or other controls. The smoke emergency will probably last only several hours, so the impact on energy management should be minimal. The only systems that should be able to automatically override the smoke control system are such safety systems as high pressure limiters.

Considering how unpredictable smoke is, you must have a manual control panel from which the smoke control system can be monitored and overridden. This panel, called a Firefighter’s Smoke Control Station (FSCS), allows firefighting personnel to take manual control of the smoke control system.




TOC

Firefig hter’s Smoke Control Stat ion

The Firefighter’s Smoke Control Station (FSCS) is a graphic annunciating control panel that gives firefighters information about the state of the smoke control system as well as manual control over all of its components. The FSCS should be located in a secure room or cabinet to prevent unauthorized personnel from tampering with it. The room or cabinet should be clearly marked so that firefighters can quickly locate the FSCS.

The Fireman’s Smoke Control Station panel has a diagram of the building showing the entire smoke control system, along with status lights and override switches for all of the system’s components. The diagram of the building should include all smoke control zones, all of the ducts leading to and from the zones with arrows indicating the direction of air flow in the ducts, and a clear indication of which zone each piece of equipment serves.

The panel must have controls to activate all fans, dampers, and other equipment related to the smoke control system. These manual controls must be able to override all automatic control of smoke control equipment. In particular, the FSCS must be able to override:

• Hand/off/auto switches

• Local start/stop switches on fan motor controllers

• Freeze detection devices

• Duct smoke detectors

The FSCS must not override such safety controls as:

• Electrical overload protection

• Maintenance personnel’s electrical disconnects

• High limit pressure switches

• Any fire/smoke damper thermal control as required by UL33 (standard for heat responsive links for fire protection service), heat responsive links, or UL555S (the standard used for leakage rated dampers for use in smoke control systems).

In non-dedicated systems, local motor controller’s hand/off/auto switches can remain in-circuit with the FSCS panel. But, they can remain in-circuit only if the switches are in a locked room accessible only to authorized personnel. Also, if such a switch is thrown, a trouble alarm must sound in the building’s main control center.




TOC

The indicator lights on the FSCS provide information about the functioning of the system. The following colors should be used for the FSCS indicators:

• Green—Fans and other equipment are running or dampers are open.

• Yellow—Dampers are in the closed position.

• Orange or Amber—The equipment has failed.

• Red—A fire has been detected in the area.

The FSCS has a lamp test button that turns on all the panel’s lights. Use this button regularly to make sure none of the lights has burned out.

The FSCS gets information on the status of the smoke control system’s equipment from proof monitors on the equipment itself. Each fan that has a capacity over 2,000 cfm capacity should be mounted with a pressure monitor. Smoke dampers should be fitted with end-range microswitches to indicate that they are fully opened or fully closed.

All of the failure lights on the FSCS (the orange or amber ones) represent the state of the equipment as determined by the proof sensors. The failure light comes on if the piece of equipment is not in the state its control is set for within its trouble indication time. This time is 60 seconds for a fan and 75 seconds for a damper. If, within that time, the proof sensors do not report that the piece of equipment has responded to the control system’s command, the FSCS indicates that the piece of equipment has failed.




TOC

Test ing t he Syst emDuring the installation, you should perform operational tests that make sure the components and subsystems of the smoke control system are installed correctly. After the installation is done, you must perform acceptance tests, to prove that the smoke control system is capable of doing what it was designed to do. The testing procedures are covered in a later chapter of this manual.

Bibliogr aphyThe National Fire Protection Association. NFPA 90A, Standard for the Installation of Air Conditioning and Ventilating Systems. The National Fire Protection Association.

The National Fire Protection Association. 1988. NFPA 92A, Recommended Practices for Smoke Control Systems. The National Fire Protection Association.

Underwriters Laboratories, Inc. UL 555S, Standard for Leakage Rated Dampers for Use in Smoke Control Systems. Underwriters Laboratories, Inc.

Underwriters Laboratories, Inc. UL 555, Fire Dampers. Underwriters Laboratories, Inc.

Underwriters Laboratories, Inc. UL 864, Control Units for Fire-Protective Signaling Systems. Underwriters Laboratories, Inc.


TOC

Chapter 2

Infini ty Smoke ControlSystem Components

This chapter presents a general overview of the Infinity smoke control system and describes the UL listed system components used, the features of each component, and their role within the system. The following components are described:

• CX9200 main controller

• SCX920S controller

• TCX840 series controllers

• TCX850 series controllers

• TCX860/865 series controllers

• EnergyLink 2500 repeater

• InfiLink 200 repeater

• InfiLink 210 repeater

• FSCS (Firefighter’s Smoke Control Station)

• Fire Panel


Infinity Smoke Control System Components


TOC

Smoke C ontrol System OverviewFigure 2-1 shows the components that are used in an Infinity smoke control system and how they are connected together. The component descriptions in the remainder of this chapter describe in more detail the role of each component in the system. Notice that the smoke control system itself is electrically isolated from the non-smoke control components.

Figure 2-1. Smoke Control Syste m Overview

CX9200SCX920S TCX 850 Infilink

fiber opticEnergyLink 2500

Infinet Cable

EnergyNet

RS-232

Smoke Detectors,Fire Detectors,Manual Pull Boxes,

SX8000Workstation

Cable

Non-Smoke Control Components

TCX 860/5

UL Listed Smoke Control Components

series series 210Infilink

200

Etc.

Cable

RS-232Cable

cable

fiber opticcable

TCX 840series




TOC

CX9200 Cont rollerThe CX9200 serves as the central controller in the Infinity smoke control system. It controls the communication between the other system components within the smoke control system. The CX9200 can be used in a dedicated or a non-dedicated smoke control application. The CX9200 connects to other controllers in the following ways:

• The CX9200 connects to other CX9200 controllers via the EnergyNet network.

• The CX9200 connects to the Infinet controllers, such as the SCX920S, the TCX850 series, TCX 840 series, or the TCX860/865 series, via the Infinet network.

• The CX9200 also connects to both the FSCS and Fire panel using 2 RS-232 ports.

When the CX9200 is utilized for smoke control, it performs the following functions:

• Initializes the smoke control system.

• Receives fire alarms from the Fire Panel and instructs the Infinet controllers to execute a smoke control strategy.

• Reads the manual override settings and updates the LEDs and alarm on the FSCS.

• Performs weekly self-tests on all the dedicated components in the smoke control system.

• Monitors the controllers in the smoke control system and signals the FSCS when there is a communication fault or output override.

Features

• Plain English programming language

• 1 Energynet communications port

• 3 RS-232/RS-485 communications ports

• 1 RS-232/RS-485/RS-422 communications port

• Supports up to 254 Infinet controllers

• Battery backup: 1 hour full UPS to 72 hours for memory only

• 115V/230V AC power input

• DCX250 touch-screen display option

• 9600 bps Infinity Modem option

• ENL2500 Energynet repeater option




TOC

SCX920S Controlle rThe SCX920S controller is used to control a large piece of equipment, such an AHU (Air Handling Unit), or several smaller pieces of equipment, such as smoke dampers. The SCX920S communicates with the CX9200, as well as other Infinet controllers, via the Infinet network. The SCX920S can be used in a dedicated or a non-dedicated smoke control application.

Features


• 16 Universal inputs that can be configured to measure Voltage, Current, Temperature, or Digital (contact closure) values

• 8 Outputs that can be either FormC relay contacts, Voltage outputs, or Current outputs

• 1 RS-485 Infinet port

• Lithium battery backup for memory and Real Time Clock

• 24V/115V/230V AC power input

• Available in either an open class plastic housing, designed to be placed in a Listed enclosure, or as a fully enclosed unit with a locking door

• Optional Local Display/Keypad option




TOC

TCX840 Series Cont rollersThe TCX840 series includes the TCX840, TCX843, TCX845, TCX846 controllers. The TCX840 series controllers are used to control small pieces of equipment that require fewer I/O points than an SCX920S, such as VAV boxes or stairwell fans. The TCX840 series communicates with the CX9200, as well as other Infinet controllers, via the Infinet network. The TCX840 series can be used in a dedicated or a non-dedicated smoke control application.

Features


• Universal inputs that can be configured to measure Voltage, Current, Temperature, or Digital (contact closure) values

• Analog outputs can be either voltage or current

• Air-flow sensor that measures differential pressure


• Lithium battery backup for memory

• 24V AC power input

Table 2-1 lists the Input/Output capabilities of each of the controllers in the TCX840 series.

Table 2-1. TCX840 ser ies I /O capabi lities

TCX840 TCX843 TCX845 TCX846

Universal Inputs 2 2 4 4

Form A Outputs 2 5 5 5

Tri-State Outputs 1 2 2 2

Analog Outputs 0 0 2 2

0 - 1" Air-flow Sensors 1 1 0 1




TOC

TCX850 Series Contro lle rsThe TCX850 series includes the TCX850, TCX851, TCX852, TCX853, and TCX855 controllers. The TCX850 series controllers are used to control small pieces of equipment that require fewer I/O points than an SCX920S, such as VAV boxes or stairwell fans. The TCX850 series communicates with the CX9200, as well as other Infinet controllers, via the Infinet network. The TCX850 series can be used in a dedicated or a non-dedicated smoke control application.

Features



• Air-flow sensors that measure differential pressure



• 24V AC power input


Table 2-1. TCX850 series I/O capabiliti es

TCX850 TCX851 TCX852 TCX853 TCX855

Universal Inputs 4 4 2 6 4

Form A Outputs 3 3 1 3 3

Tri-State Outputs 1 1 1 1 1

0 - 1" Air-flow Sensors 1 0 1 2 0

0 - 0.2" Air-flow Sensors 0 0 0 0 1




TOC

TCX860 Series Cont roller sThe TCX860 series includes the TCX860, TCX861, TCX862, and TCX863 controllers. Like the TCX850 series, the TCX860 series controllers are used to control VAV boxes. The TCX860 series communicates with the CX9200, as well as other Infinet controllers, via the Infinet network. The TCX860 series can be used in a dedicated or a non-dedicated smoke control application.

The TCX860 series controllers have a built-in motor and gear assembly for direct control of a damper.

Features



• Analog outputs can be either Voltage or Current

• Air-flow sensors that measure differential pressure from 0 to 1 inches water gauge

• One RS-485 Infinet port


• 24 V AC power input


Table 2-2. TCX860 Series I/O Capabilities

Input/Output Types TCX 860 TCX 861 TCX 862 TCX 863

Universal Inputs 4 4 2 4

Form A Outputs 3 3 3 3

Analog Outputs — 2 2 2

Airflow Sensors 1 1 1 1

Damper Motor 1 1 1 —

EMX170 ports — 1 1 1

Powerfail PCB — — 1 —




TOC

TCX865 Series Cont roller sThe TCX865 series includes the TCX865, TCX866, TCX867, TCX868 and TCX869 controllers. Like the TCX860 series, the TCX865 series controllers are used to control VAV boxes. The TCX865 series communicates with the CX9200, as well as other Infinet controllers, via the Infinet network. The TCX865 series can be used in a dedicated or a non-dedicated smoke control application.

The TCX865 series controllers have a built-in motor and gear assembly for direct control of a damper.

Features


• Universal inputs that can be configured to measure Voltage, Temperature, or Digital (contact closure) values

• Analog outputs can be either Voltage or Current

• Air-flow sensors that measure differential pressure from 0 to 1 inches water gauge

• One RS-485 Infinet port


• 24 V AC power input


Table 2-1. TCX865 Series I/O Capabilities

Input/Output Types TCX 865 TCX 866 TCX 867 TCX868 TCX 869

Universal Inputs 2 2 2 2 2

Form A Outputs 3 3 0 3 3

Analog Outputs 0 0 0 0 2

Airflow Sensors 1 1 1 1 1

Damper Motor 1 1 1 —

Sensor ports 0 0 0 1 1

Real Time Clock 0 1 0 1 1




TOC

EnergyLi nk 2500The EnergyLink 2500 is an active network hub for the EnergyNet network that has slots for plugging in various media interface modules.

The EnergyLink 2500 can perform the following functions:

• Allows the Energynet to be used in a star configuration

• Extends the length of an Energynet network

• Connects different Energynet media types together

• Allows for electrical isolation on an Energynet network by using fi-ber optics.

Features

• Slots for up to 7 media interface modules

• Mounts inside the CX9200 cabinet

• Power (+5V DC) supplied by the CX9200 power supply

Table 2-3 lists the 3 different media interface modules that are available for the EnergyLink 2500.

Table 2-3. EnergyLink 2500 Media Interface Modules

Media Type Media Interface Module

Twisted Pair (10BASE-T) ENL2501

Thin Coaxial (10BASE-2) ENL2502

Fiber Optic (10BASE-FL) ENL2503




TOC

Infilink 200The InfiLink 200 is a repeater and network expander for the Infinet network.

The InfiLink 200 can perform the following functions:

• Amplify an RS-485 Infinet signal, thus allowing for extension beyond 4,000 feet

• Expand an RS-485 Infinet signal into 4 more RS-485 channels, thus allowing for up to 127 Infinet controllers on a network

• Convert an RS-485 signal into an RS-232 signal

Features

• 5 RS-485 ports

• 1 RS-232 port

• Switch selectable baud rates

• Enclosure is standard





TOC

Infilink 210The InfiLink 210 is a fiber optic repeater for the Infinet network. The InfiLink 210 is used to convert a single RS-485 Infinet signal into 2 fiber optic Infinet channels. Therefore, if an Infilink 210 is used at each Infinet controller, the entire network can use fiber optics. The Infilink 210 can be used to electrically isolate one section of the Infinet network from another section.

Features

• 1 RS-485 port

• 2 fiber optic ports. Each port has a Receive Data connection and a Transmit Data connection.

• Switch selectable baud rates

• Enclosure is standard





TOC

The FSCSThe Firefighter’s Smoke Control Station (FSCS) is a custom panel that provides full monitoring and manual control capability over all smoke control equipment. In the event of an emergency, it is used by the fire department to override the smoke control system.

Features

The FSCS should contain a building diagram that clearly indicates the type and location of all smoke control equipment, and the areas served by the equipment (smoke control zones). Since the FSCS uses a graphical depiction of the building, each FSCS will be unique and must be custom made.

The FSCS graphic must show all fans in excess of 2000 CFM, all dampers or groups of VAV boxes, and all major ducts and how the ducts are connected together. The FSCS graphic must provide a clear indication of the direction of airflow in the ducts.

If the FSCS graphic is too large to fit on a single panel, multiple panels may be used.

Manual Overrides

The FSCS must provide manual controls that will override any piece of equipment in the smoke control system. The FSCS must have the highest priority in the smoke control system. The FSCS must be able to override any other manual or automatic control that is being used in the system, except when these controls are intended to protect against electrical overloads, provide for personal safety, or prevent major system damage. VAV boxes that are all located within and serve one designated smoke control zone may be controlled collectively.

Fans require a 3-position control that provides ON-AUTO-OFF capabilities. Dampers require a 3-position control that provides OPEN-AUTO-CLOSE capabilities. The AUTO position is removed if the override is for a piece of equipment that can only be controlled by the FSCS.

In addition to the controls mentioned above, you can also have a 3-position control for each zone that provides PRESSURIZE-AUTO-EXHAUST capabilities.




TOC

Status Indicators

The actual status of the smoke control equipment must be clearly indicated on the FSCS by the use of visual indicators with appropriate legends.

Fans must have a single indicator that turns on when the fan’s differential pressure “proof sensor” indicates that the fan is operating.

Dampers must have 2 indicators: one that turns on when the damper’s end-limit “proof sensor” indicates that the damper is closed, and one that turns on when the damper’s other end-limit “proof sensor” indicates that the damper is open. Both indicators should be off when the damper is positioned between the open and closed positions.

The FSCS should provide a status indicator for each zone that signals whether or not the zone is in an alarm condition.

The FSCS should provide status indicators for each piece of equipment that signals when there has been an equipment failure. For instance, if the fans do not turn on within 60 seconds, or the dampers do not reach the desired position within 75 seconds, the fault indicator should turn on.

Table 2-4 lists the status indicator colors that must be used on the FSCS

Table 2-4. FSCS Status Indicator col ors

Status Color

Damper OPEN or Fan ON Green

Damper CLOSED Yellow

System or Equipment FAULT Amber/Orange

Zone ALARM Red




TOC

Other Features

The FSCS will also have the following features:

• Master Key – This key will silence the audible alarm and enable all of the controls on the FSCS. This key must be made available to authorized personnel only.

• Clear Faults Button -- This momentary push-button will clear all of the fault indicators on the FSCS. This push-button is not enabled unless the Master key is ON. If the fault corrects itself, the fault indicator will automatically turn off. If the fault returns, the fault indicator will turn on again. If there is a fault detected during the weekly self-test of a dedicated controller, the fault indicator for that piece of equipment will stay on until it is cleared. The Clear Faults push-button is wired to an input on the FSCS, just like any other switch.

• Lamp Test Button - This momentary push-button turns on all of the status indicators on the FSCS, thus allowing the operator to determine if there is a bad indicator.

• Audible Alarm – The alarm sounds when there is a smoke emergency or when there is an equipment fault. Turning the Master key ON is the only way to silence the alarm.

Orderi ng In format ion

Andover Controls’ UL listing includes a custom FSCS panel that is manufactured by Automation Displays Incorporated. For ordering information, contact:

Automation Displays Inc.3533 North White AvenueEau Claire, Wisconsin 54703(715) 834-9595




TOC

Design Guidel ines

In order to have the FSCS built to your specifications, you will need to supply the following:

• An accurate drawing of the smoke control system. This drawing will be used to create the FSCS front panel graphic.

• A second copy of the FSCS drawing indicating the colors of the status indicators.

• A third copy of the FSCS drawing indicating the colors that are to be used for the front panel graphic. Consult Automation Displays, Inc. for a list of options.

• Specify whether you need a flush-mount or a surface-mount panel.

• Specify whether or not you need a transparent cover for the FSCS.

• Specify whether or not you need a terminal block wired to the FSCS inputs, to be used for Zoned Wiring to the Fire Panel.

Automation Displays, Inc. will provide you with a copy of the FSCS drawing that indicates the I/O numbers that correspond to each LED output and each switch input on the FSCS. Each 2 position switch requires 1 input and each 3 position switch requires 2 inputs.

The FSCS you order from Automation Displays Inc. will contain the following:

• An Automation displays’ Autoface IV graphic door with a keylock.

• Switches and Status Indicators for each piece of smoke control equipment.

• A “Master” keyswitch, a “Clear Faults” push-button, a “Lamp Test” push-button and a sonalert audible annunciator.

• An Automation Displays’ Q-Card CPU board with the “Andover Data Interface” firmware that is wired to an RS232 Protection PCB.

• An Automation Displays’ 80 Point Driver card for every 80 status indicators.

• An Automation Displays’ 80 Point Driver card for reading the FSCS switches. A 2 position switch requires 1 input and a 3 position switch requires 2 inputs. A Switch Protection PCB is also included.

• A 5V DC power supply for the Q-Card, the 80 Point Driver cards, and the FSCS Status Indicators.

Refer to Chapter 5 for a drawing of an example FSCS graphic.




TOC

The Fi re PanelThe Fire Panel connects to all of the smoke detectors, fire detectors, manual pull boxes, fire alarms, etc.within the building. When one of the Fire Panel sensors detects a problem, the Fire Panel informs the Infinity smoke control which sensor is in an alarm condition and what the alarm condition is. The Infinity smoke control system receives all of it’s alarm information from the Fire Panel. The smoke control zones must correspond to the Fire Panel’s fire zones.

There are two methods for connecting the Fire Panel to the Infinity smoke control system: using an RS-232 communications channel or by the Zoned Wiring method.

RS-232 Communi cations

As part of Andover Controls’ UL Listing, the following Fire Panels can communicate directly with the CX9200 via RS-232:

Simplex Time Recorder Co. Series 41001 Simplex PlazaGardner, Massachusetts 01441(508) 632-2500

Edwards Systems Technology, Inc. Model # IRC-3195 Farmington AvenueFarmington, Connecticut 06032(203) 678-0410

Zoned Wiring

If you are using a Fire Panel that is not listed above, you will have to connect to the Infinity smoke control system using the Zoned Wiring method. This requires running a set of wires for each zone from a contact closure output on the Fire Panel to inputs on the FSCS. The CX9200 will poll the FSCS to determine when a zone is in an alarm condition. If you plan on using this method, you must specify that a terminal block be provided with the FSCS that connects to the FSCS inputs. See the following chapter for more details.


TOC

Chapter 3

Instal lation and Layou tThis chapter gives instructions for installing and interconnecting the Infinity smoke control system components.

All wiring in an Infinity smoke control system must comply with the National Electric Code (NFPA 70), as well as any state or local regulations.

Special requirements for using Infinity equipment to perform smoke control is covered in detail in this chapter. For general installation instructions, see the installation guides for each individual component. These installation guides are shipped with the Infinity controllers. Topics covered in this chapter are:

• Installing the CX9200

• Installing Infinet Controllers

— The SCX920S

— The TCX840 series

— The TCX850 series

— The TCX860/865 series

— The Infilink 200

— The Infilink 210

• Installing the FSCS

• Installing the Fire Panel


Installation and Layout


TOC

Inst alli ng the CX9200For detailed information on how to mount and connect the wiring to the CX9200 and it’s peripherals, refer to the following Andover Controls documentation:

Infinity CX9200 Hardware Installation Guide (P/N 30-3001-347)Energylink 2500 Installation Guide (P/N 30-3001-393)DCX250 Installation Guide (P/N 30-3001-196)Infinity Modem Guide (P/N 30-3001-404)

Cable Limitations

• The RS-232 cable between the CX9200 and the FSCS must be no longer than 20 feet, and must be enclosed in conduit.

• The RS-232 cable between the CX9200 and the Fire Panel must be no longer than 20 feet, and must be enclosed in conduit.

Comm Port Ass ignments

In a smoke control system, it is recommended that you use the following Comm Port assignments:

• COMM1 – FSCS panel RS-232

• COMM2 – Infinet Network

• COMM3 – User terminal

• COMM4 – Fire Panel RS-232

Isolati ng Energynet Co ntrol lers

In a system that performs smoke control, the CX9200s have to be electrically isolated from other Energynet devices using the Energylink 2500 and the ENL2503 fiber optic module. This is done in order to ensure that a fault on one of these devices will not interfere with the operation of the smoke control system. The Energylink 2500 is only required when connecting CX9200s to other Energynet devices, it is not required between CX9200s.

The Energylink 2500 mounts in the CX9200 cabinet and receives it’s power from the CX9200 power supply.

Figure 3-1 shows the use of the Energylink 2500 to isolate the CX9200 from other Energynet controllers.




TOC

Figure 3-1. Isolatin g the CX9200

CX9200with

Energylink 2500

CX9200

Other Energynet Components

FiberOptics

Smoke Control Components

Energynet Energynet




TOC

Installi ng Inf inet Controller sFor detailed information on how to mount and connect the wiring to the various Infinet controllers and repeaters, refer to the following Andover Controls documentation:

SCX920 Installation Guide (P/N 30-3001-170)TCX840 Installation Guide (P/N 30-3001-493)TCX850 Installation Guide (P/N 30-3001-173)TCX860 Installation Guide (P/N 30-3001-390)TCX865 Installation Guide (P/N 30-3001-497)Infilink 200 Installation Guide (P/N 30-3001-178)Infilink 210 Installation Guide (P/N 30-3001-394)

Smoke Con trol Requi rements

In addition to the information contained in each installation guide, the following requirements apply when using the Infinet controllers and repeaters in a smoke control system.

The SCX920S

• When using the SCX920S in a dedicated smoke control application, the manual overrides must be disabled. The SCX920 installation guide explains this process in detail.

• When using the SCX920S in a non-dedicated smoke control application, you must do one of the following:

— Disable the manual overrides, or

— Locate the SCX920S in area only accessable to authorized personnel, and provide an OVERRIDE status indicator on the FSCS that turns on when the outputs are overridden. The FSCS audible indicator must also turn on.

• If the AC input voltage is to be set to 24 V, an Andover Controls’ Listed transformer must be used to supply the 24V AC input power . These transformers must be placed in a Listed enclosure and must be wired according to the National Electric Code, as well as any state or local regulations.

Table 3-1 lists the step-down transformers that are available from Andover Controls.




TOC

The TCX840 and TCX850 series

• Only an Andover Controls’ Listed transformer may be used to supply the 24V AC input power for the TCX840 and TCX850 series. These transformers must be placed in a Listed enclosure and must be wired according to the National Electric Code, as well as any state or local regulations.


• All of the Input and Output wiring on the TCX840 and TCX850 series must remain in the same room.

The TCX860/865 series

• Only an Andover Controls’ Listed transformer may be used to supply the 24V AC input power for the TCX860/865 series. These transformers must be placed in a List-ed enclosure and must be wired according to the National Electric Code, as well as any state or local regulations.


• All of the Input and Output wiring on the TCX860/865 series must remain in the same room.

The Infi link 200

• Any cables connected to the RS-232 port must be less than 20 feet in length, and must be enclosed in conduit.

The Infi link 210

• The Infilink 210 must be used to electrically isolate the Infinet controllers that are performing smoke control from the non-smoke control Infinet controllers. This is

Table 3-1. Lis ted 24V Step-down Transformers

Voltage PRI:SEC VA Rating Part NumberPrimary and Secondary Connections

115V : 24V 40 VA 01-2100-378 Solderless Lug

115V : 24V 40 VA 01-2100-323 Wires

277V : 24V 50 VA 01-2100-379 Solderless Lug

208/240V : 24V 40 VA 01-2100-407 Wires




TOC

done in order to ensure that a fault on one of these devices will not interfere with the operation of the smoke control system. The Infilink 210 is not required between every Infinet controller, it is only required between groups of controllers that are performing smoke control and groups of controllers not performing smoke control.

Figure 3-2 shows the use of the Infilink 210 to isolate the Infinet smoke control components.

Figure 3-2. Isolatin g the Infinet Controller s

CX9200

Other Infinet Controllers

FiberOptics

Smoke Control Components

SCX920STCX840 series

TCX860/865 seriesInfilink 200

Infilink210

Infilink210

Infinet

TCX850 series




TOC

Installi ng the FSCSFor detailed information on how to mount the FSCS, refer to:

Automation Displays Inc.3533 North White AvenueEau Claire, Wisconsin 54703(715) 834-9595

Location and Access

The FSCS should be located close to the other fire fighter’s systems that are in the building. Means should be provided to ensure only authorized access to the FSCS. When acceptable to the authority having jurisdiction, the FSCS should be located in a room that is separated from public areas by a suitably marked and locked door. The location, room size, access means, and other physical design considerations of the FSCS location must be acceptable to the authority having jurisdiction.

Inside the FSCS

Figure 3-3 shows what the typical components inside an FSCS will look like. Since the FSCS is custom made for each application, the internal layout will vary from panel to panel.




TOC

Figure 3-3. Typical Internal Components in an FSCS

80 POINT LED DRIVER CARD

80 POINT SWITCH INPUT CARD

Q-CARD PROCESSOR PCB

1234

SWITCHPROTECTION

PCB

WIRING

TROUGH

RS-232PROTECTION

PCB

OUT IN COM

+5V DC POWER SUPPLY

+5V

+5V

COM

COM

HNG

ON

1 A

RS-232 FIELDWIRING TERMINALS

AC POWERFIELD WIRINGTERMINALS

POWER SWITCHAND LINE FUSE




TOC

Field Wiring Terminals

The following are the only field connections that are required when installing an FSCS. All field wiring must be installed by qualified personnel and must comply with the National Electric Code, as well as any state or local regulations.

AC Power Wir ing

The AC input voltage is connected to the AC POWER FIELD WIRING TERMINALS.

Figure 3-4 shows this terminal block and how it is wired.

Figure 3-4. AC Power Terminal Blo ck

RS-232 Communi cati on Port Wiring

The RS-232 cable from the CX9200 connects to the FSCS at the RS-232 FIELD WIRING TERMINALS. This cable must be less than 20 feet in length, and must be enclosed in conduit.

Figure 3-5 shows this terminal block and how it is wired to the CX9200.

HNG

The HOT Terminal (Black wire)The NEUTRAL Terminal (White wire)The GROUND Terminal (Green wire)




TOC

Figure 3-5. RS-232 Terminal B lock

Zoned Alarm Contact Wiring (Opt ional)

As stated in the previous chapter, if you are not using a Fire Panel that is part of the Andover Controls Listing, you will have to connect the Fire Panel to the smoke control system using the Zoned Wiring method. This involves connecting a set of wires for each zone from the Fire Panel to the FSCS. Each contact closure output on the Fire Panel will be wired to an input on the FSCS, which is read by the CX9200. These FSCS inputs will be wired at a terminal block in the FSCS (not shown). This wiring must be less than 20 feet in length, and must be enclosed in conduit.

The Q-Card Processor P CB

The Q-Card controls the RS-232 communications with the CX9200, reads the FSCS switch inputs from the 80 Point Switch Input cards, and controls which Status Indicators will be turned on by the 80 Point LED Driver cards.

The Q-Card has a Reset switch and an Options dipswitch. Pressing the Reset switch resets the processor, but maintains the current status of the LEDs. The Options dipswitch is used to set the RS-232 baud rate and to enable the auto-blanking feature. When the auto-blanking feature is on, the status LEDs will be cleared if the FSCS does not receive any data from the CX9200 within 10 seconds. The Q-Card only reads the Options dipswitch after a Reset.

COMMONDATA INDATA OUT

RS-232PROTECTION

PCB

OUT IN COM

Wire to pin 7 on the CX9200 RS-232 portWire to pin 2 on the CX9200 RS-232 portWire to pin 3 on the CX9200 RS-232 port




TOC

Table 3-2 shows the settings for the Options dipswitch..

Andover Controls recommends setting the FSCS for 9600 baud, with auto-blanking disabled, therefore all the dipswitches are OFF.

Figure 3-6 shows the location of the switches on the Q-Card.

Figure 3-6. The Q-Card swit ch sett ings

Table 3-2. Q-Card Options Dip switch Sett ings

Switch Position: 1 2 3 4

Auto-blanking ON ON

Auto-blanking OFF OFF

9600 Baud OFF OFF OFF

7200 Baud OFF OFF ON

4800 Baud OFF ON OFF

3600 Baud OFF ON ON

2400 Baud ON OFF OFF

1200 Baud ON OFF ON

600 Baud ON ON OFF

300 Baud ON ON ON

Q-CARD PROCESSOR PCB

1 2 3 4

Reset Switch Options Dipswitch




TOC

Installi ng the Fire Pane lRefer to the Fire Panel manufacturer’s documentation for installation and wiring instructions.

The Fire Panel connects to the CX9200 through an RS-232 cable. This cable should be no longer than 20 feet in length, and must be enclosed in conduit.

Figure 3-7 shows how to wire the RS-232 cable from the Fire Panel to the CX9200.

Figure 3-7. Fire Panel RS-232 Wiring

a. Simplex Model 4020

XMITRTSRCVCTSGND

Port A

CX9200 DB-25

Pin 2 (TD)

Pin 3 (RD)

Pin 7 (GND)

b. Edwards Syst ems Techn ology Model IRC-3

CX9200 DB-25

Pin 2 (TD)

Pin 3 (RD)

Pin 7 (GND)

TXDRXD

COMM

TB1


TOC

Chapter 4

Configuring the SystemThis chapter briefly describes how to configure the smoke control system and how to communicate with the various smoke control system components. For more detailed information concerning these and other topics, refer to the following Andover Controls manual:

Infinity CX Programmer’s Guide (P/N 30-3001-166)

This chapter does not attempt to explain the system’s programming language or how to write smoke control application programs. Refer to Chapter 5 for example smoke control programs.

Topics covered in the chapter are:

• Logging On to the CX9200

• Using the Command Window

• Using the Menus

• Logging Off the CX9200

• Assigning Security Levels to Users

• Setting the System Date and Time

• Configuring the Commports

• Creating and Editing Points

• Creating and Editing Files


Configuring the System


TOC

Log ging on to the CX92 00When you first power up the CX9200, COMM3 at 9600 baud is the default communications port for your terminal. After connecting an RS-232 cable between your terminal and COMM3, type WINDOW . You will not see the word WINDOW on your terminal as you are typing. The CX9200 will respond with the Infinity Window.

The Infinity Window prompts you for a User Name first. If the CX9200 has just been powered up or reset, you must type in the predefined User Name ACC. Otherwise, type in your own User Name.

The Infinity Window then prompts you for a Password. If the CX9200 has just been powered up or reset, you must type in the predefined Password ACC. Otherwise, type in your own Password.

If you logged in under the User Name ACC and Password ACC, you are the system administrator and have full access to the system. You should change the Password ACC to another Password in order to prevent unauthorized access to the system. For details, refer to the section in this chapter on Assigning Security Levels to Users.

Figure 4-1 shows the Infinity Window.

Figure 4-1. The Infini ty Window

iewV ditE onnectC ogoutL

INFINITY

User Name

PasswordACC

(C) 1990 Andover Controls Corporation

Version 1.5




TOC

Using the Comma nd WindowOnce you have logged on to the CX9200, the Command window will be displayed. The Command window is the main window in the Infinity system.

Along with the Command window, you will see the Main Menu Bar at the top of the screen and the StatusBar at the bottom.

Figure 4-2 shows the Command window.

Figure 4-2. The Command Window.

The Main Menu Bar

The Main Menu Bar has selections for View, Edit , Connect and Logout. The current selection will be highlighted. The View and Edit selections will cause a Pulldown Menu to appear. The Main Menu Bar selections will be discussed in more detail throughout this chapter.

The Command Window

The Command window allows you to enter commands directly to the smoke control system. You enter these commands at the Command


Command Window - INFINITY1

R>




TOC

window’s R> prompt. You toggle between the Main Menu Bar and the Command window using the F4 key.

You can print the values of System Variables, Start and Stop Programs, or execute many other commands from the Command window. For example, if you type the following:

R>PRINT DATE

The CX9200 will respond by printing the Date and Time inside the Command window.

The StatusBar

The StatusBar can be used by a program to Print any information that is available in the Infinity system.




TOC

Using the M enusAlthough many of the Infinity Menus look different, they all respond to the same set of keystrokes. This section summarizes some of these keystrokes.

You change between the Main Menu Bar selections using the LEFT and RIGHT ARROW keys. In order to accept a selection, you can either press ENTER while the selection is highlighted, or enter the first letter of the selection.

You change between selections in a pulldown menu using the UP and DOWN ARROW keys. In order to accept a selection, you can either press ENTER while the selection is highlighted, or enter the first letter of the selection.

Once in another menu, you use the TAB key to change from attribute to attribute. To go to the previous attribute, hit the ESC key, then the TAB key.

If an attribute uses a small window and has a list of selections that have a set of parentheses before them, use the UP and DOWN ARROWS to change between the selections, and use the SPACE bar to accept a selection. After you accept the selection, an X will appear in the parentheses.

When the system is prompting you to enter a name, you can press the F2 key to get a list of the available choices.

The F4 key allows you to toggle between the Menu Bars and the Windows.

Logging Off th e CX9200In order to Log Off the CX9200, simply select the Logout selection from the Main Menu Bar.

After Logging Off the CX9200, it will not respond to anything you type on the terminal. You must perform the Logging On procedure if you want to communicate with the CX9200 again.




TOC

Assi gning Securit y Levels to UsersThis section describes how to assign new Users for the Infinity system and how to set the Passwords and Security Levels for these Users.

Starting at the Main Menu Bar, select the Edit function. A pulldown menu will appear showing what Edit functions are available. Select the Users option from the pulldown menu.

Figure 4-3 shows the Edit pulldown menu.

Figure 4-3. Edit p ulldown menu

After selecting Edit Users, you will be prompted to enter the User Name. Type in the Name of the User that you want to add or change and hit ENTER. For example, if you want to change the Password of the initial predefined user, enter ACC. You may also use the F2 key to view the selections that are available to you.

The User Window will now appear on the screen. The User Window allows you to enter the Password, set the Security Level, and enter other information about this User.



R>

Edit

FilesCommportsControllersInfinet ControllersSystem Date & TimeSystem VariablesPersonsAreasDoors

PointsUsers




TOC

When you want to select a particular security level, hit the SPACE bar and an (X) will appear to the left of the selection. When you are done editing this User, TAB over to the Save box and hit ENTER. This new User information will now be entered into the system.

Figure 4-4 shows the User Window.

Figure 4-4. The User Window


Command Window - INFINITY1User - INFINITY1 ACC

( ) View Only( ) Acknowledge Alarms( ) Change Values( ) Enable/Disable( ) Configure( ) Program(X) Administrate

( ) No Access

Full NamePassword

Login ProgramLogout Program

User Name ACC

ACC

Security Level

SAVE

SAVE AS

CANCEL

DELETE

TEACH




TOC

Setting t he Syst em Date and TimeStarting at the Main Menu Bar, select the Edit function. A pulldown menu will appear showing you the Edit functions that are available. Figure 4-3 shows the Edit pulldown menu.

Select the System Date & Time option from the pulldown menu. The System Time window, which allows you to set the date and time, will now appear on the screen. Enter the date and time in the same format that appears in the window. When the date and time are set, TAB to the OK box and hit ENTER. You have now set the date and time throughout the Infinity system.

Figure 4-5 shows the System Time window.

Figure 4-5. The Syste m Time Window



R>

System Time - INFINITY1

March 24 1994 15:20:00Date and Time

OK CANCEL




TOC

Conf igur ing th e Commpor tsThe CX9200 has four Communication Ports that must be configured for use with the smoke control system. In a smoke control system, it is recommended that you assign the Commports as follows:

• COMM1 - RS-232 port for the FSCS

• COMM2 - Infinet Network

• COMM3 - User Terminal

• COMM4 - RS-232 port for the Fire Panel

Configu ring COMM1 for the FSCS

Starting at the Main Menu Bar, select the Edit function. A pulldown menu will appear showing you the Edit functions that are available. Figure 4-3 shows the Edit pulldown menu.

Select the Commports option from the pulldown menu. After selecting Edit Commports, you will be prompted to enter the Commport Name. You can either type in COMM1 , or press the F2 key for a list of the available selections. After entering COMM1 , press the ENTER key and the Commport window will appear on the screen.

The Commport window allows you to enter a description, set the Default Mode, and set the Baud rate. For use with the FSCS, the Commport should be set up as follows:

• Description = FSCS Interface (for example)

• DefaultMode = Printer

• Baud rate = Baud9600

Once the information has been entered, TAB to the SAVE box and hit the ENTER key. Comm1 has now been configured.

Figure 4-6 shows the Commport window.




TOC

Figure 4-6. The Commpor t Window

Configu ring COMM2 for Infin et

Select Edit Commports and enter COMM2 at the Name prompt. When the Commport window comes up, set the DefaultMode attribute to Infinet .

When you hit the TAB key the Commport window will change slightly and two more boxes will appear that are labeled Learn and View. These new selections apply to an Infinet port. The Learn box instructs the CX9200 to poll the Infinet Network and bring any available controllers On-line. The View box instructs the CX9200 to print out the status of the Infinet controllers.

The attributes should be set as follows:

• Description = Infinet Port (for example)

• DefaultMode = Infinet


Once the attributes are set properly, TAB to the Learn box and hit ENTER. The CX9200 will respond with a window that says Learn Mode is Active.



( ) Window( ) Command( ) Infinet( ) Lbus( ) Autoset( ) TankNet( ) Xdriver

(X) Printer

Name COMM1

DefaultModeSAVE

CANCEL

Commport - INFINITY1 COMM1

Description FSCS Interface

Mode Printer

( ) Baud1200( ) Baud2400( ) Baud4800(X) Baud9600( ) Baud19200

( ) Baud300

Baud




TOC

When the CX9200 has completed polling the Infinet Network, it will display the Infinet Summary window. This window shows the name, port, model, serial number and status of all of the Infinet devices.

Figure 4-7 shows an example of the Infinet Summary window.

Figure 4-7. The Infin et Summary wind ow

The F4 key will bring you back to the Commport window. Use the UP ARROW key to go to the SAVE box and hit the ENTER key. The CX9200 will display the Command window. COMM2 has now been configured for Infinet.

If this is the first Learn you have performed on this Infinet Network, the CX9200 will assign a name to each controller that is based on it’s serial number and port. You can change these names to something more meaningful, such as AHU1 or FLOOR2_TCX, by going to the Edit pulldown menu, selecting Infinet Controllers , pressing the F2 key to list the available choices, and selecting the Infinet controller name that you would like to change.

The CX9200 will display the Infinet Controller window. You can now change the name of the Infinet controller. You can also add a Description for this Infinet controller, such as Floor 1 Air Handling


Infinet Summary - INFINITY1

Name Model Serial Number ID StatusPort

920 80858 1 OnlineCOMM2lc_0080858

920 80857 2 OnlineCOMM2lc_0080857

853 63078 3 OnlineCOMM2lc_0063078




TOC

Unit . When you have done this, TAB to the Save box and hit the ENTER key. The CX9200 will return to the Command window.

Figure 4-8 shows the Infinet Controller window.

Figure 4-8. The Infin et Contr oller Window

From the Main Menu Bar, you can select View, then Infinet Controllers to verify your name changes and to view the status of all of the Infinet controllers.

Configu ring COMM3 for the Users Termi nal

The default settings are as follows:

• DefaultMode = Autoset


• TerminalType = VT100

If you need to change any of these settings, or you want to enter a description, you select Edit Commports and use COMM3 as the name.


Command Window - INFINITY1Infinet Controller - INFINITY1 AHU1

Name AHU1 SAVE

SAVE AS

CANCEL

DELETE

RESET

Model 920

Description Floor 1 Air Handling Unit

Port COMM2

Infinet ID 1

Serial Number 80858

Error

Error Time

Error Count 0

Version 1.5

Status OnLine

Reconfigs 0




TOC

Configu ring COMM4 for the Fire Panel

This section describes how to configure COMM4 to communicate with the Fire Panel. The CX9200 communicates with the Fire Panel using a piece of software called an Xdriver, which is available from Andover Controls. Instead of selecting Edit Commports from the Main Menu Bar to configure COMM4, you load an Xdriver “.dmp” file into the CX9200 using a computer that is running a communications program.

Each Fire Panel will have it’s own unique Xdriver. If you are using a Simplex Fire Panel, you will need the SPX Xdriver. If you are using an Edwards Systems Technology Fire Panel, you will need the EST Xdriver.

Loading an Xdriver

You should receive four files in your Xdriver package, one for each commport. Since COMM4 is being used for the Fire Panel, you will either use the spxcom4.dmp Xdriver for a Simplex panel, or the estcom4.dmp Xdriver for an Edwards Systems Technology panel. The Xdriver loading procedure is as follows:

• If your CX9200 controller name is not “INFINITY1”, then you must edit the Xdriver file and change all occurrences of “INFINITY1’’ to your controller name.

• If your CX9200 Energynet ID is not “1”, then you must change the number at the end of the line “Dictionary : CONTROLLER NAME : 1” to your controller’s Energynet ID.

• Go to the Command window on the CX9200 and type load -o-m at the R> prompt and hit the ENTER key.

• From your computer, send the appropriate Xdriver “.dmp” file.

• When the reload is done, the CX9200 will return to the Command window. Type print COMM4 xdriverstatus at the R> prompt and the CX9200 should respond with “Installed”.

See the section titled Creating and Editing Points for instructions on how to create variables that use the Xdriver port.




TOC

Creating and Ed iting PointsThis section explains how to create and edit a Point. A point refers to a variable that is used by the Infinity system. For example, a Point can be an input on a controller, an output on a controller, a numeric variable, a character string, or an Xdriver variable.

Creating an Input/Output Poin t

Select Edit Points from the Main Menu Bar. Enter the name of the Infinet controller at the InfinetCtlr prompt. Enter the name of the Point at the Name prompt. If it is a new Point, you will have to type in the name that you wish to give the Point, such as:

OADmp for the Outside Air Damper output Sfan for the Supply Fan output

If you are editing an existing Point, you can hit the F2 key at the Name prompt and get a list of the available choices.

After entering the Point Name, the Point window will appear. The Point window allows you to define the attributes of this Point. You must set the Type of Point, such as Input or Output. You must set the Electrical Type for an Input/Output Point, such as Voltage, Digital, Current, or TriState. You must set the Channel Number for each Input/Output Point. The Channel Number refers to the physical Input or Output number on the Infinet controller. Each Infinet controller will have different Input/Output capabilities. Refer to Chapter 2 for an explanation of each controller.

If you select the DETAILS box, you can enter a Description of the Point, enter the Display Format for a Point, or define other attributes of the Point.

When you are done entering the attributes, TAB to the SAVE box in the Point window and hit the ENTER key. The CX9200 will return you to the Command window.

Figure 4-9 shows an example of a Point window.




TOC

Figure 4-9. Example Point Window

Creating a Numeric Point

A Numeric Point is a variable that can be used by the Infinity system. A Numeric Point is created the same way as an Input or Output point. When you call up the Point window, set the Type to Numeric. A Numeric Point does not have selections for Channel Number or Electrical Type because they do not apply. You can select the DETAILS box in order to enter a description for the point.

Creating an Xdriver Point

An Xdriver Point is a variable that will be used by the CX9200 to get alarm and status information from the Fire Panel. In order to create an Xdriver Point, create a Numeric Point and select the DETAILS1 box.

A window will appear on the screen prompting you to enter a Port. Enter COMM4 for the Port because that is the Port that the Fire Panel is connected to. Press the TAB key (not ENTER) after typing in COMM4 and some additional fields will appear on the screen. The number of fields and the name of the fields will be different for different Xdrivers. These fields correspond to the physical Fire Panel sensor numbers that



(X) Output( ) Numeric( ) DateTime

( ) Input

Name Sfan

TypeSAVE

SAVE AS

Point - INFINITY1 AHU1 Sfan

(X) Digital( ) Current( ) TriState( ) Pneumatic( ) ReaderDoor

( ) Voltage

Electrical Type

(X) Enabled( ) Disabled

State

=

( ) HiResVoltage( ) HiResCurrent

CANCEL

DETAILS

Channel Number 1




TOC

this Xdriver Point is to represent. Refer to your Fire Panel manufacturer’s documentation for a description of these fields.

Figure 4-10 shows the Simplex Xdriver fields.

Figure 4-10. Simplex Xdriver Fields

Figure 4-11 shows the Edwards Systems Technology fields.


Point - INFINITY1 Smoke.SPX

Port COMM4

SAVE

CANCELCard

Point

Sub-Point

Status/Time




TOC

Figure 4-11. EST Xdriver Fields

Refer to Appendix A for a list of the possible Xdriver values that can be received from the Fire Panel, and what Events they correspond to.


Point - INFINITY1 Smoke.EST

Port COMM4

SAVE

CANCELLoop

Address




TOC

Creating and Ed iting Fil esThis section briefly explains how to create and edit a File. A File can be a Program, a Function, a Data file or a Report. These Programs, which run in the CX9200 and in the Infinet controllers, determine how the Infinity smoke control system operates.

The Programs are written in Andover Controls’ Plain-English language. It is beyond the scope of this manual to explain the Plain-English language or how to write Programs. Refer to the following Andover Controls documentation for Plain-English programming instructions:

Plain English Language Reference (P/N 30-3001-165)Infinity CX Programmer’s Guide (P/N 30-3001-166)

Creating a Program

Select Edit Files from the Main Menu Bar. If the Program will be running in an Infinet controller, enter the name of the Infinet controller at the InfinetCtlr prompt. If the Program will be running in the CX9200, leave the InfinetCtlr prompt blank. Enter the name of the Program at the Name prompt. If it is a new Program, you will have to type in the name that you wish to give the Program, such as:

SmokeSelfTest FSCS_Interface

If you are editing an existing Program, you can hit the F2 key at the Name prompt and get a list of the available choices.

After entering the Program Name, the File window will appear. The File window allows you to enter a Description for the Program or define the attributes of the Program, such as State, Flowtype or whether or not the Program should start automatically.

Figure 4-12 shows the File window.




TOC

Figure 4-12. The File Window

After entering the information into the File window, TAB to the SAVE box and hit the ENTER key. The CX9200 will now bring up the Editor window. The Editor window allows you to create a new Program or edit an existing Program.

When you are editing a File, the File Menu Bar is at the top of the screen. The File Menu Bar has pulldown menus that allow you to use the Editor. Hit the F4 key to toggle between the Editor window and the File Menu Bar.

When you are finished editing your program, select the File pulldown menu from the File Menu Bar, then select the Save option. The CX9200 will now compile and save your program. The compiler will alert you if there are any errors in the program.

If you configured the Program for AutoStart, it will begin to run after it is compiled and saved. If not, you can Start or Stop the Program from the Command window, or from another Program.

To exit the Editor and return to the Command window, select File Quit from the File Menu Bar.



( ) Function( ) Data( ) Report

(X) Program

Filename SmokeSelfTest

TypeSAVE

CANCEL

File - INFINITY1 SmokeSelfTest

(X) Enabled( ) Disabled

State

Description

DELETE

DETAILS

Weekly Dedicated System Tests

(X) FallThru( ) Looping

FlowType

(X) Command Line( ) AutoStart




TOC

Figure 4-13 shows the Editor window, the File Menu Bar, and part of a sample program.

Figure 4-13. The Editor

Functions, Data files and Reports are created the same way as a Program.

The File Menu Bar

• The File pulldown menu allows you to Open a File, Save a File, modify the Configuration of a File, set the Firing Order of a File, or Quit the Editor and return to the Command window.

• The Edit pulldown menu allows you to Cut, Copy, Paste, Clear, and Select text within the Editor.

• The Search pulldown menu allows you to Find text, find and Replace text, or search for the Next Error or the Previous Error.

• The Check selection will check for errors in your File.

• The Tools pulldown menu will allow you to view a Point Summary, a File Summary, a Program Summary, a System Variable Summary, or the Message window. It will also allow you to Edit a Point, Edit a System Variable, or create a split screen that contains the Command Window on the top of the screen and the Editor on the bottom half.

File earchS heckC oolsT

INFINITY1 - SmokeSelfTest

ditE

Begin_prog:

‘Clear Self-Test FaultsAH3Sfan.ST.Fail = OffFL2SADmp.ST.Fail = OffFL2RADmp.ST.Fail = OffFL3SADmp.ST.Fail = OffFL3RADmp.ST.Fail = OffFL4SADmp.ST.Fail = OffFL4RADmp.ST.Fail = Off

RunTests:Print “ RUNNING DEDICATED SELF-TEST “ to COMM3 StatusBar

CloseDampers:SMKDMPRS DefaultDmprPosn = On

WaitForDampers:If TS < (MaxDamperTime + 5) then Goto WaitForDampers


Smoke Control Programs


TOC

Chapter 5

Smoke Cont rol ProgramsThis chapter describes some example Infinity smoke control programs. These example programs are for illustrative purposes only. Since each system is unique, your programs will not be identical to these examples, but the same principles will apply.

The HVAC example programs were included to show how the smoke control mode must have priority over the HVAC modes. The HVAC programs do not perform any HVAC functions.

These programs are written in Andover Controls’ Plain-English language. It is beyond the scope of this manual to explain the Plain-English language or how to write applications programs. Refer to the following Andover Controls documentation for Plain-English programming instructions:


Topics covered in this chapter are:

• Example Smoke Control System

• CX9200 Programs

— Programs for Communicating with the FSCS

— Programs for Verifying Equipment Operation

— Programs for Smoke Control

— Programs for Controlling the System

• Controlling the Smoke Dampers

• Controlling the Air Handling Units

• Controlling the Stairwell Fan

• Controlling the VAV Terminals




TOC

Example S moke C ontrol SystemFigure 5-1 shows a block diagram of the smoke control components that could be used to create a smoke control system for a small, four story building. This example system will be used as the basis for the programs in this chapter.

Figure 5-1. Example Smoke Control Syst em

SCX920SAHU-1Floor 1

CX9200Main Controller

Firefighter’s SmokeControl Station

Fire PanelSimplex or EST

RS-232RS-232

SCX920SSmokeDampers

SCX920SAHU-2Floors 2-4

Floors 2-4

TCX840VAV TerminalFloor 2



TCX853AHU-3Stairwell

INFINETRS-485




TOC

Figure 5-2 shows the FSCS graphic for the example system.

Figure 5-2. Example FSCS

AHU-2

Firefighter’s Smoke Control Station

CLEARFAULTS

LAMP TEST MASTER KEY

SONALERT

AHU-3

AHU-1

AHU-1 SUPPLY FAN

STATUS FAILON AUTO OFF

AHU-1 RETURN FAN


AHU-1 RA DAMPER

OPEN FAIL CLOSEDOPEN AUTO CLOSED

AHU-1 OA DAMPER


AHU-1 EX DAMPER


AHU-2 RA DAMPER


AHU-2 OA DAMPER


AHU-2 EX DAMPER


AHU-2 RETURN FAN


SA SMOKE DAMPER


RA SMOKE DAMPER


SA SMOKE DAMPER


RA SMOKE DAMPER


SA SMOKE DAMPER


RA SMOKE DAMPER



ZONE 2 VAV DAMPER


ZONE 3 VAV DAMPER


ZONE 4 VAV DAMPER

SMOKE ALARMPRESS AUTO EXHAUST

ZONE 4


ZONE 3


ZONE 2


ZONE 1

SMOKE ALARMPRESS AUTO

STAIRWELL

AHU-2 SUPPLY FAN


AHU-3 SUPPLY FAN


FLOOR 4VAV CONTROLLERS

AHU-2 CONTROLLER

FAULT OVERRIDE

FLOORS 2 - 4


SMOKE DAMPERCONTROLLER


AHU-1 CONTROLLERFLOOR 1

AHU-3 STAIRWELLCONTROLLER

FAULT OVERRIDE

FAULT OVERRIDE FAULT OVERRIDE

FAULT OVERRIDE FAULT OVERRIDE

FAULT OVERRIDE

4TH FLOOR - ZONE 4

3RD FLOOR - ZONE 3

2ND FLOOR - ZONE 2

1ST FLOOR - ZONE 1

ANDOVER CONTROLS




TOC

CX9200 ProgramsThe CX9200 is the central controller in the smoke control system. It controls the communications with the Infinet controllers, the FSCS, and the Fire Panel. The CX9200 is also responsible for initiating a smoke control strategy, verifying that the system components are functioning properly, and performing a weekly self-test on the dedicated smoke control equipment.

Table 5-1 lists the programs, functions, and data files that the CX9200 uses to control the example system. :

Table 5-1. CX9200 Files

NAME TYPE DESCRIPTION

PilotLights Function Updates the FSCS LED and Override numerics in the CX9200 with the Infinet controller point values.

LampPointMap Data Maps the CX9200 numerics to the LED numbers on the FSCS.

OutputLampString Function Formats the string that is sent to the FSCS in order to update the LEDs.

DecodeSwitches Function Uses the string that was read from the FSCS for the override switches and sets the corresponding CX9200 numerics.

FSCS_Interface Program Controls the RS-232 interface between the CX9200 and the FSCS.

NetStatus Function Checks the Comm status of the Infinet controllers.

PlantFaultCheck Function Determines whether or not the fans and dampers have reached their desired state within the time allowed by NFPA 92A.

HornControl Program Controls the state of the FSCS audible annunciator.

ClearFaults Program Clears all faults when the FSCS “MASTER KEY” is ON and the “CLEAR FAULTS” pushbutton is pressed.

FireAlarmCheck Function Determines whether or not, and in which zones, to perform smoke control. Sets the FSCS Alarm LEDs based on the inputs from the Fire Panel.

SmokeSelfTest Program Runs a weekly self-test on the dedicated controllers.




TOC

These files are explained in detail in this section. As stated previously, this is not the only way to program your system to perform smoke control, it represents one example.

Refer to Appendix B for an explanation of the Points used in the example programs.

Main Program The main sequencing program. This program determines what the entire system is doing by calling the other programs and functions.

FirstAid Program Initializes the system when a System Error occurs, or when the System Time is changed.

Table 5-1. CX9200 Files





TOC

Prog rams for C ommunicati ng with the FSCS

PilotLights

Type: FunctionDescription: Updates the FSCS LED and Override numerics in the CX9200 with the Infinet controller point values.

Code: ‘ Update LED Numerics AH1Sfan.On = AHU1 SfanSt AH1Rfan.On = AHU1 RfanSt AH2Sfan.On = AHU2 SfanSt AH2Rfan.On = AHU2 RfanSt AH3Sfan.On = AHU3 SfanSt AH1OADmp.Opn = AHU1 OADmp.Opn AH1OADmp.Cls = AHU1 OADmp.Cls AH1EADmp.Opn = AHU1 EADmp.Opn AH1EADmp.Cls = AHU1 EADmp.Cls AH1RADmp.Opn = AHU1 RADmp.Opn AH1RADmp.Cls = AHU1 RADmp.Cls AH2OADmp.Opn = AHU2 OADmp.Opn AH2OADmp.Cls = AHU2 OADmp.Cls AH2EADmp.Opn = AHU2 EADmp.Opn AH2EADmp.Cls = AHU2 EADmp.Cls AH2RADmp.Opn = AHU2 RADmp.Opn AH2RADmp.Cls = AHU2 RADmp.Cls FL2VAV.Opn = Flr2TCX VAVDmp.Opn FL2VAV.Cls = Flr2TCX VAVDmp.Cls FL3VAV.Opn = Flr3TCX VAVDmp.Opn FL3VAV.Cls = Flr3TCX VAVDmp.Cls FL4VAV.Opn = Flr4TCX Damper.Opn FL4VAV.Cls = Flr4TCX Damper.Cls FL2SADmp.Opn = SMKDMPRS Fl2.SASDmp.Opn FL2SADmp.Cls = SMKDMPRS Fl2.SASDmp.Cls FL2RADmp.Opn = SMKDMPRS Fl2.RASDmp.Opn FL2RADmp.Cls = SMKDMPRS Fl2.RASDmp.Cls FL3SADmp.Opn = SMKDMPRS Fl3.SASDmp.Opn FL3SADmp.Cls = SMKDMPRS Fl3.SASDmp.Cls FL3RADmp.Opn = SMKDMPRS Fl3.RASDmp.Opn FL3RADmp.Cls = SMKDMPRS Fl3.RASDmp.Cls FL4SADmp.Opn = SMKDMPRS Fl4.SASDmp.Opn




TOC

FL4SADmp.Cls = SMKDMPRS Fl4.SASDmp.Cls FL4RADmp.Opn = SMKDMPRS Fl4.RASDmp.Opn FL4RADmp.Cls = SMKDMPRS Fl4.RASDmp.Cls ‘ Update Override Numerics AHU1.OVRR = AHU1 OverrideOn AHU2.OVRR = AHU2 OverrideOn SMKDMPRS.OVRR = SMKDMPRS OverrideOnReturn

File Explanation:

This function sets the CX9200 numerics in the left column equal to the Infinet controller points in the right column. The CX9200 numerics are used to control their corresponding LED on the FSCS and to set the “.OVRR” override fault numerics.




TOC

LampPointMap

Type: DataDescription: Maps the CX9200 numerics to the LED numbers on the FSCS.

Code: Record 80 String 16 “SpareLamp “ “AH3Sfan.On “ “AH3Sfan.Fail “ “AH2Sfan.On “ “AH2Sfan.Fail “ “AH2OADmp.Opn “ “AH2OADmp.Fail “ “AH2OADmp.Cls “ “AH2RADmp.Opn “ “AH2RADmp.Fail “ “AH2RADmp.Cls “ “FL4SADmp.Opn “ “FL4SADmp.Fail “ “FL4SADmp.Cls “ “FL4VAV.Opn “ “FL4VAV.Fail “ “FL4VAV.Cls “ “AH2EADmp.Opn “ “AH2EADmp.Fail “ “AH2EADmp.Cls “ “AH2Rfan.On “ “AH2Rfan.Fail “ “FL4RADmp.Opn “ “FL4RADmp.Fail “ “FL4RADmp.Cls “ “Zone4.ALM “ “STRWL.ALM “ “AHU2.Fail “ “AHU2.OVRR “ “FLR4TCX.Fail “ “FLR4TCX.OVRR “ “AHU1.Fail “ “AHU1.OVRR “ “FLR3TCX.Fail “ “FLR3TCX.OVRR “ “SMKDMPRS.Fail “




TOC

“SMKDMPRS.OVRR “ “FLR2TCX.Fail “ “FLR2TCX.OVRR “ “AHU3.Fail “ “AHU3.OVRR “ “FL3SADmp.Opn “ “FL3SADmp.Fail “ “FL3SADmp.Cls “ “FL3RADmp.Opn “ “FL3RADmp.Fail “ “FL3RADmp.Cls “ “FL3VAV.Opn “ “FL3VAV.Fail “ “FL3VAV.Cls “ “Zone3.ALM “ “FL2SADmp.Opn “ “FL2SADmp.Fail “ “FL2SADmp.Cls “ “FL2RADmp.Opn “ “FL2RADmp.Fail “ “FL2RADmp.Cls “ “FL2VAV.Opn “ “FL2VAV.Fail “ “FL2VAV.Cls “ “Zone2.ALM “ “AH1Sfan.On “ “AH1Sfan.Fail “ “AH1OADmp.Opn “ “AH1OADmp.Fail “ “AH1OADmp.Cls “ “AH1RADmp.Opn “ “AH1RADmp.Fail “ “AH1RADmp.Cls “ “AH1EADmp.Opn “ “AH1EADmp.Fail “ “AH1EADmp.Cls “ “AH1Rfan.On “ “AH1Rfan.Fail “ “Zone1.ALM “ “SpareLamp “ “SpareLamp “ “SpareLamp “ “SpareLamp “ “Horn “




TOC

File Explanation:

This data file contains the CX9200 numerics that are used to set the state of all of the LEDs on the FSCS. If the numeric is turned ON, the corresponding LED on the FSCS will turn ON.

The position of the numeric in the file must correspond to the LED Addresses for that LED. The LED Adrress is determined by the internal FSCS wiring from the LED to the I/O card. The FSCS manufacturer will supply you with the LED Addresses. Since the I/O cards have 80 points each, there should be 80 entries in LampPointMap for each I/O card.

For example, the LED Addresses for this example are as follows:

LED 0 --> SpareLamp (not used)LED 1 --> AH3Sfan.ON (AHU3 Supply Fan STATUS LED)LED 2 --> AH3Sfan.Fail (AHU3 Supply Fan FAIL LED)LED 3 --> AH2Sfan.ON (AHU2 Supply Fan STATUS LED) . .LED 80 --> Horn (Audible Annunciator)

The last output, called “Horn”, controls the state of the audible annunciator on the FSCS.




TOC

OutputLampString

Type: FunctionDescription: Formats the string that is sent to the FSCS in order to update the LEDs.

Code: Numeric Loop String 1 LampState

‘ Insert start parenthesis LampWriteString = “(” ‘ Fill in lamps 0 to 79 For Loop = 1 to 80 If getname(LampPointMap[Loop][1] ; “ Value”) = On then ~ LampState = “X” Else LampState = “Z” LampWriteString = left(LampWriteString, Loop) ; LampState Next Loop ‘ Insert end parenthesis LampWriteString = left(LampWriteString, 81) ; “)” Return (LampWriteString)

File Explanation:

This function generates the string (LampWriteString) that must be sent to the FSCS in order to set all of the LEDs and the Horn. It does this by reading the “value” of all 80 numerics that are in the data file named OutputLampString .

If the CX9200 numeric is ON, an “X” is placed in it’s position. If the numeric is OFF, a “Z” is placed in it’s position. The 1st character controls LED 0, the 2nd character controls LED 1, and so on. The string must begin with a parenthesis and end with a parenthesis. A typical string would have 80 characters and look like the following:

LampWriteString = “(ZZZXXZXZZZZZZZXXZXZ...XZXZZZ) ”

Wherever there is an “X” in the string the LED will be ON, and wherever there is a “Z” the LED will be OFF.

Refer to Appendix C for a complete discussion of the FSCS communications protocol.




TOC

DecodeSwitches

Type: FunctionDescription: Uses the string that was read from the FSCS for the override switches and sets the corresponding CX9200 numerics. Code: Numeric SwitchState, SWS SWS = search(InBuffer, “(000”) If SWS <> 0 then ‘ Input string found, offset past 4 intro characters. SWS = SWS + 4

If mid(InBuffer, SWS + 0, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off SpareSwitch = SwitchState If mid(InBuffer, SWS + 1, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH3Sfan.OVR.On = SwitchState If mid(InBuffer, SWS + 2, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH3Sfan.OVR.Off = SwitchState If mid(InBuffer, SWS + 3, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2Sfan.OVR.On = SwitchState

If mid(InBuffer, SWS + 4, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2Sfan.OVR.Off = SwitchState

If mid(InBuffer, SWS + 5, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2OADmp.OVR.Opn = SwitchState

If mid(InBuffer, SWS + 6, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2OADmp.OVR.Cls = SwitchState

If mid(InBuffer, SWS + 7, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2RADmp.OVR.Opn = SwitchState




TOC

If mid(InBuffer, SWS + 8, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2RADmp.OVR.Cls = SwitchState

If mid(InBuffer, SWS + 9, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off FL4SADmp.OVR.Opn = SwitchState

If mid(InBuffer, SWS + 10, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off FL4SADmp.OVR.Cls = SwitchState

If mid(InBuffer, SWS + 11, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off FL4VAV.OVR.Opn = SwitchState

If mid(InBuffer, SWS + 12, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off FL4VAV.OVR.Cls = SwitchState

If mid(InBuffer, SWS + 13, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2EADmp.OVR.Opn = SwitchState

If mid(InBuffer, SWS + 14, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2EADmp.OVR.Cls = SwitchState If mid(InBuffer, SWS + 15, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2Rfan.OVR.On = SwitchState

If mid(InBuffer, SWS + 16, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH2Rfan.OVR.Off = SwitchState

If mid(InBuffer, SWS + 17, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off FL4RADmp.OVR.Opn = SwitchState

If mid(InBuffer, SWS + 18, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off FL4RADmp.OVR.Cls = SwitchState

If mid(InBuffer, SWS + 19, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off




TOC

Zone4.PRS = SwitchState

If mid(InBuffer, SWS + 20, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off Zone4.EXH = SwitchState

If mid(InBuffer, SWS + 21, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off STRWL.PRS = SwitchState

If mid(InBuffer, SWS + 22, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off Fault.Clear = SwitchState

If mid(InBuffer, SWS + 23, 1) = “A” then SwitchState = On Else ~ SwitchState = Off LampTest = SwitchState







If mid(InBuffer, SWS + 30, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off Zone3.PRS = SwitchState




TOC










If mid(InBuffer, SWS + 40, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1Sfan.OVR.On = SwitchState

If mid(InBuffer, SWS + 41, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1Sfan.OVR.Off = SwitchState

If mid(InBuffer, SWS + 42, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off




TOC

AH1OADmp.OVR.Opn = SwitchState

If mid(InBuffer, SWS + 43, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1OADmp.OVR.Cls = SwitchState

If mid(InBuffer, SWS + 44, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1RADmp.OVR.Opn = SwitchState

If mid(InBuffer, SWS + 45, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1RADmp.OVR.Cls = SwitchState

If mid(InBuffer, SWS + 46, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1EADmp.OVR.Opn = SwitchState

If mid(InBuffer, SWS + 47, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1EADmp.OVR.Cls = SwitchState

If mid(InBuffer, SWS + 48, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1Rfan.OVR.On = SwitchState

If mid(InBuffer, SWS + 49, 1) = “A” and Main.Key then ~ SwitchState = On Else SwitchState = Off AH1Rfan.OVR.Off = SwitchState



If mid(InBuffer, SWS + 52, 1) = “A” then SwitchState = On Else ~ SwitchState = Off Zone1.CON = SwitchState





TOC



If mid(InBuffer, SWS + 56, 1) = “A” then SwitchState = On Else ~ SwitchState = Off STRWL.CON = SwitchState

If mid(InBuffer, SWS + 59, 1) = “A” then SwitchState = On Else ~ SwitchState = Off Main.Key = SwitchState Endif Return

File Explanation:

This function sets the CX9200 numerics that represent the FSCS switches. It does this by searching through the InBuffer string that was received from the FSCS and turning the numeric ON if an “A” is found at the corresponding location. Otherwise the numeric is set to OFF.

The position of the character in the string corresponds to the Switch Addresses for that Switch. The Switch Adrress is determined by the internal FSCS wiring from the Switch to the I/O card. The FSCS manufacturer will supply you with the Switch Addresses.

A 2 position switch requires 1 input. The input is ON when the switch is in one position, the input is OFF when the switch is in the other position.

A 3-position switch requires 2 inputs. One input is ON when the switch is in the left position, the other input is ON when the switch is in the right position, and both inputs are OFF when the switch is in the center position.

For example, the Switch Addresses for this example are as follows:

Switch 0 --> SpareLamp (not used)Switch 1 --> AH3Sfan.OVR.On (AHU3 Sfan Overridden ON)Switch 2 --> AH3Sfan.OVR.Off (AHU3 Sfan Overridden OFF)Switch 3 --> AH2Sfan.OVR.On (AHU2 Sfan Overridden On)




TOC

. .Switch 59 --> Main.Key (MASTER KEY keyswitch)

The first three digits in the InBuffer string represent the address of the first switch. In this case, we are only using one input card, therefore this will always be “000” for Switch 0. If we had two input cards, the string from the second card would begin with “080” for Switch 80. A typical string would have 83 characters and look like the following:

InBuffer = “(000AARARRRRARARRARAAA...RAARRRR) ”

Wherever there is an “A” in the string the Switch has been activated, and wherever there is an “R” the Switch is released.

Also notice that some of the variables will not be turned on if MAIN.KEY is not ON. This prevents the FSCS overrides from being used unless the Master Key is turned ON. The Zoned Wiring inputs from the Fire Panel (if used), and the MAIN.KEY input MUST be updated even if the Master Key is turned OFF.

Refer to Appendix C for a complete discussion of the FSCS communications protocol.




TOC

FSCS_Interface

Type: ProgramFlowType: LoopingDescription: Controls the RS-232 interface between the CX9200 and the FSCS.

Code: Numeric Result, Timeout Begin_Prog: Timeout = 4 If COMM1 Mode = Raw then Goto Send_Request Else Goto ~ Open_Comm1 Open_Comm1: Result = Open(COMM1) Test_Open: If Result = Success then Goto Send_Request Else Goto ~ Found_Problem Send_Request: Print “(SPR)(?SBK1)”; to COMM1 Goto Wait_For_Print Wait_For_Print: If COMM1 PrintDone then Goto Read_Comm1 If TS > Timeout then Goto Found_Problem Read_Comm1: Result = read(COMM1, 100, InBuffer, 500, “)”) Test_Read: If COMM1 TimedOut then Goto Found_Problem If Result = Success then Goto Decode_Data Else Goto Found_Problem Decode_Data: DecodeSwitches() Goto Output_Lamp Output_Lamp: Print OutputLampString(); to COMM1 Goto Wait_For_Output Wait_For_Output: If COMM1 PrintDone then Status2 = Off




TOC

Goto Done Endif If TS > Timeout then Goto Found_Problem Found_Problem: Status2 = On Goto Close_Comm1 Close_Comm1: Result = Close(COMM1) Test_Close: If Result = Success then Goto Done If TS > Timeout then Goto Done Done: FSCSLinkActive = False

File Explanation:

This program communicates with the ADI FSCS panel using the Andover Data Interface protocol. Refer to Appendix C for a complete discussion of the FSCS communications protocol.

The sequence of operations are as follows:

• Open the Comm port to the FSCS (COMM1)

• Send the command for the FSCS to print out the Switch status data

• Read the switch data into the InBuffer string

• Call the DecodeSwitches function

• Print the string OutputLampString to COMM1 in order to set the LEDs on the FSCS

• Set the numeric FSCSLinkActive to FALSE

If any of the Comm port statements, such as Open or Read, are not successful, then the program will turn ON the Status2 indicator on the CX9200 and Close the Comm port. If any of the Print statements are not completed within 5 seconds (Timeout+1), then the program will turn ON the Status2 indicator on the CX9200 and Close the Comm port. The Status2 indicator signals an FSCS communications fault.




TOC

This program will not be Run again until the FSCSLinkActive numeric is set to FALSE.

The command for the FSCS to print out the status of the switches is:

Print “(SPR)(?SBK1)”; to COMM1

The “(SPR)” part tells the FSCS to suppress all switch activation messages until it is polled. The “(?SBK1)” part tells the FSCS to perform a Switch Status Block Transfer on I/O card 1. If you had a second switch I/O card, you would request it’s switch data by sending “(?SBK2)” to the FSCS.

The Read statement for reading the FSCS switch data from COMM1 into the string InBuffer is:

Result = read(COMM1, 100, InBuffer, 500, “)”)

This command tells the CX9200 to wait for 100 characters, OR 5 seconds, OR until it receives the right parenthesis. Under normal circumstances, it will receive the parenthesis first.




TOC

Prog rams for V eri fying Equipment Operat ion

NetStatus

Type: FunctionDescription: Checks the Comm status of the Infinet controllers.

Code: If AHU1 CommStatus is OnLine then CtlrTimer[1] = Time AHU1.Fail = ((Time - CtlrTimer[1]) > MaxCtlrTime) If AHU2 CommStatus is OnLine then CtlrTimer[2] = Time AHU2.Fail = ((Time - CtlrTimer[2]) > MaxCtlrTime) If AHU3 CommStatus is OnLine then CtlrTimer[3] = Time AHU3.Fail = ((Time - CtlrTimer[3]) > MaxCtlrTime) If SMKDMPRS CommStatus is OnLine then CtlrTimer[4] = Time SMKDMPRS.Fail = ((Time - CtlrTimer[4]) > MaxCtlrTime) If Flr2TCX CommStatus is OnLine then CtlrTimer[5] = Time FLR2TCX.Fail = ((Time - CtlrTimer[5]) > MaxCtlrTime) If Flr3TCX CommStatus is OnLine then CtlrTimer[6] = Time FLR3TCX.Fail = ((Time - CtlrTimer[6]) > MaxCtlrTime) If Flr4TCX CommStatus is OnLine then CtlrTimer[7] = Time FLR4TCX.Fail = ((Time - CtlrTimer[7]) > MaxCtlrTime) Return

File Explanation:

This function uses the DateTime array called CtlrTimer[ ] to keep track of how long each Infinet controller is OffLine. If the controller goes OffLine, CtlrTimer[n] no longer gets set to the system Time. If the controller is Offline for a period of time longer than MaxCtlrTime , then the expression “((Time - CtlrTimer[n]) > MaxCtlrTime)” will be TRUE, therefore the corresponding .Fail numeric is set TRUE.

In the MAIN Program, MaxCtlrTime is set to 10 seconds to allow Infinet to Reconfigure without the FSCS turning on a Fault alarm.




TOC

PlantFaultCheck

Type: FunctionDescription: Determines whether or not the fans and dampers have reached their desired state within the time allowed by NFPA 92A.

Code: ‘ Checks all fans and dampers to ensure that the status input follows ‘ the output within the allowable time, if not the fail flag will be set. ‘ PlantTimer[] is an Array holding the datetime of the last plant state change. ‘ Plant 1 If (AHU1 Sfan = AHU1 SfanSt) then PlantTimer[1] = Time AH1Sfan.Fail = (Time - PlantTimer[1]) > MaxFanTime ‘ Plant 2 If (AHU1 Rfan = AHU1 RfanSt) then PlantTimer[2] = Time AH1Rfan.Fail = (Time - PlantTimer[2]) > MaxFanTime ‘ Plant 3 If (AHU2 Sfan = AHU2 SfanSt) then PlantTimer[3] = Time AH2Sfan.Fail = (Time - PlantTimer[3]) > MaxFanTime ‘ Plant 4 If (AHU2 Rfan = AHU2 RfanSt) then PlantTimer[4] = Time AH2Rfan.Fail = (Time - PlantTimer[4]) > MaxFanTime ‘ Plant 5 If (AHU3 Sfan = AHU3 SfanSt) then PlantTimer[5] = Time AH3Sfan.Fail = (Time - PlantTimer[5]) > MaxFanTime ‘ Plant 6 If not (((AHU1 OADmp = On) and (AHU1 OADmp.Opn <> On)) or ((AHU1 OADmp = -On) and (AHU1 OADmp.Cls <> On))) then PlantTimer[6] = Time AH1OADmp.Fail = (Time - PlantTimer[6]) > MaxDamperTime ‘ Plant 7 If not (((AHU1 EADmp = On) and (AHU1 EADmp.Opn <> On)) or ((AHU1 EADmp = -On) and (AHU1 EADmp.Cls <> On))) then PlantTimer[7] = Time AH1EADmp.Fail = (Time - PlantTimer[7]) > MaxDamperTime




TOC

‘ Plant 8 If not (((AHU1 RADmp = On) and (AHU1 RADmp.Opn <> On)) or ((AHU1 RADmp = -On) and (AHU1 RADmp.Cls <> On))) then PlantTimer[8] = Time AH1RADmp.Fail = (Time - PlantTimer[8]) > MaxDamperTime ‘ Plant 9 If not (((AHU2 OADmp = On) and (AHU2 OADmp.Opn <> On)) or ((AHU2 OADmp = -On) and (AHU2 OADmp.Cls <> On))) then PlantTimer[9] = Time AH2OADmp.Fail = (Time - PlantTimer[9]) > MaxDamperTime ‘ Plant 10 If not (((AHU2 EADmp = On) and (AHU2 EADmp.Opn <> On)) or ((AHU2 EADmp = -On) and (AHU2 EADmp.Cls <> On))) then PlantTimer[10] = ~ Time AH2EADmp.Fail = (Time - PlantTimer[10]) > MaxDamperTime ‘ Plant 11 If not (((AHU2 RADmp = On) and (AHU2 RADmp.Opn <> On)) or ((AHU2 RADmp = -On) and (AHU2 RADmp.Cls <> On))) then PlantTimer[11] = ~ Time AH2RADmp.Fail = (Time - PlantTimer[11]) > MaxDamperTime ‘ Plant 12 If not (((SMKDMPRS Fl2.SASDmp = On) & (SMKDMPRS Fl2.SASDmp.Cls <> On)) or ((SMKDMPRS Fl2.SASDmp = Off) & (SMKDMPRS Fl2.SASDmp.Opn ~ <> On))) then PlantTimer[12] = Time FL2SADmp.Fail = (Time - PlantTimer[12]) > MaxDamperTime ‘ Plant 13 If not (((SMKDMPRS Fl2.RASDmp = On) & (SMKDMPRS Fl2.RASDmp.Cls <> On)) or ((SMKDMPRS Fl2.RASDmp = Off) & (SMKDMPRS Fl2.RASDmp.Opn ~ <> On))) then PlantTimer[13] = Time FL2RADmp.Fail = (Time - PlantTimer[13]) > MaxDamperTime ‘ Plant 14 If not (((SMKDMPRS Fl3.SASDmp = On) & (SMKDMPRS Fl3.SASDmp.Cls <> On)) or ((SMKDMPRS Fl3.SASDmp = Off) & (SMKDMPRS Fl3.SASDmp.Opn ~ <> On))) then PlantTimer[14] = Time




TOC

FL3SADmp.Fail = (Time - PlantTimer[14]) > MaxDamperTime ‘ Plant 15 If not (((SMKDMPRS Fl3.RASDmp = On) & (SMKDMPRS Fl3.RASDmp.Cls <> On)) or ((SMKDMPRS Fl3.RASDmp = Off) & (SMKDMPRS Fl3.RASDmp.Opn ~ <> On))) then PlantTimer[15] = Time FL3RADmp.Fail = (Time - PlantTimer[15]) > MaxDamperTime ‘ Plant 16 If not (((SMKDMPRS Fl4.SASDmp = On) & (SMKDMPRS Fl4.SASDmp.Cls <> On)) or ((SMKDMPRS Fl4.SASDmp = Off) & (SMKDMPRS Fl4.SASDmp.Opn ~ <> On))) then PlantTimer[16] = Time FL4SADmp.Fail = (Time - PlantTimer[16]) > MaxDamperTime ‘ Plant 17 If not (((SMKDMPRS Fl4.RASDmp = On) & (SMKDMPRS Fl4.RASDmp.Cls <> On)) or ((SMKDMPRS Fl4.RASDmp = Off) & (SMKDMPRS Fl4.RASDmp.Opn ~ <> On))) then PlantTimer[17] = Time FL4RADmp.Fail = (Time - PlantTimer[17]) > MaxDamperTime ‘ Plant 18 If not (((Flr2TCX VAVDmp = On) & (Flr2TCX VAVDmp.Opn <> On)) or ((Flr2TCX VAVDmp = -On) & (Flr2TCX VAVDmp.Cls <> On))) then ~ PlantTimer[18] = Time FL2VAV.Fail = (Time - PlantTimer[18]) > MaxDamperTime ‘ Plant 19 If not (((Flr3TCX VAVDmp = On) & (Flr3TCX VAVDmp.Opn <> On)) or ((Flr3TCX VAVDmp = -On) & (Flr3TCX VAVDmp.Cls <> On))) then ~ PlantTimer[19] = Time FL3VAV.Fail = (Time - PlantTimer[19]) > MaxDamperTime ‘ Plant 20 If abs(Flr4TCX Damper - Flr4TCX Damper Position) < 0.005 then PlantTimer[20] = Time FL4VAV.Fail = (Time - PlantTimer[20]) > MaxDamperTime ‘ Turn ON FSCS Fail LEDs for a Weekly Self Test Failure of a Dedicated Controller If AH3Sfan.ST.Fail then AH3Sfan.Fail = On If FL2SADmp.ST.Fail then FL2SADmp.Fail = On




TOC

If FL2RADmp.ST.Fail then FL2RADmp.Fail = On If FL3SADmp.ST.Fail then FL3SADmp.Fail = On If FL3RADmp.ST.Fail then FL3RADmp.Fail = On If FL4SADmp.ST.Fail then FL4SADmp.Fail = On If FL4RADmp.ST.Fail then FL4RADmp.Fail = On

File Explanation:

This function uses the DateTime array called PlantTimer[ ] to determine if the fans and dampers have reached their desired state in the time allowed by NFPA 92A:

Fans --> Within 60 seconds Dampers --> Within 75 seconds

If the feedback for the fan or damper does not equal the state of the output, PlantTimer[n] no longer gets set to the system Time. If the fans do not respond within the time allowed by MaxFanTime, then the expression “((Time - PlantTimer[n]) > MaxFanTime)” will be TRUE, therefore the corresponding .Fail numeric is set TRUE. If the dampers do not respond within the time allowed by MaxDamperTime, then the expression “((Time - PlantTimer[n]) > MaxDamperTime)” will be TRUE, therefore the corresponding .Fail numeric is set TRUE.

In the MAIN Program, MaxFanTime is set to 45 seconds and MaxDamperTime is set to 60 seconds. These numbers are 15 seconds less than the time allowed by NFPA 92A. This was done to allow some time for communications between the CX9200 and the Infinet controllers, and between the CX9200 and the FSCS.

At the end of this function there is a section of code that turns the .Fail numerics ON if the self-test fail numeric (.ST.Fail) for that piece of equipment is ON. Since this is a function, only the final value of the numeric will be used by the CX9200.




TOC

Prog rams for S moke Control

HornControl

Type: ProgramFlowType: FallthruDescription: Controls the state of the FSCS audible annunciator.

Code: Object CurrentPoint String NameStg Numeric TempHorn OpenPoints: If OpenList(“Numeric”, CurrentPoint) = Success then Goto ReadPoints Else Print “ ** Can Not Open Numeric List ** “ CloseList(CurrentPoint) Stop Endif ‘Check if name contains “.Fail”,“.OVRR” or “.ALM” ‘If ANY Failure, Override or Alarm is ON, then Turn ON Horn ReadPoints: TempHorn = Off While GetObject(CurrentPoint) = Success Print CurrentPoint Name to NameStg If search(NameStg, “.Fail”) or search(NameStg, “.OVRR”) or ~ search(NameStg, “.ALM”) then If CurrentPoint Value = On then TempHorn = On Endif Endif Endwhile ClosePointsList: If CloseList(CurrentPoint) <> Success then Print “ ** Can Not Close Numeric List. ** “ Endif SetHorn: Status1 = TempHorn If Main.Key = Off then Horn = TempHorn Else Horn = Off Stop




TOC

File Explanation:

This program determines whether the Horn numeric should be ON or OFF. The Horn numeric controls the state of the audible annunciator on the FSCS.

The program does this by looking at every numeric in the CX9200. If the numeric name ends with “.Fail” or “.OVRR” or “.ALM”, and the value of the numeric is ON, and the Master Key is OFF, then the Horn is turned ON. This will turn ON the Horn for all Failures/Faults, all Overrides, and all Alarms.

When the Master Key is turned ON, the audible annunciator will be turned OFF.

The Status1 indicator on the CX9200 will turn ON if there are any Faults, Overrides, or Alarms. The Master Key will not turn OFF the Status1 indicator.




TOC

ClearFaults

Type: ProgramFlowType: FallthruDescription: Clears all faults when the FSCS “MASTER KEY” is ON and the “CLEAR FAULTS” pushbutton is pressed.

Code: Object CurrentPoint String NameStg Numeric Count Begin_Prog: ‘Clear Proof Sensor Timers For Count = 1 to PlantTimer Size PlantTimer[Count] = Time Next Count ‘Clear INFINET offline Timers For Count = 1 to CtlrTimer Size CtlrTimer[Count] = Time Next Count ‘Clear SelfTest Fault Indicator Status4 = Off OpenPoints: If OpenList(“Numeric”, CurrentPoint) = Success then Goto ReadPoints Else Print “ ** Can Not Open Numeric List ** “ CloseList(CurrentPoint) Stop Endif ReadPoints: While GetObject(CurrentPoint) = Success Print CurrentPoint Name to NameStg If search(NameStg, “.Fail”) or search(NameStg, “.OVRR”) then Set CurrentPoint Value = Off Endif Endwhile ClosePointsList: If CloseList(CurrentPoint) <> Success then




TOC

Print “ ** Can Not Close Numeric List. ** “ Endif Stop

File Explanation:

This program clears all Faults caused by equipment failures, Infinet controllers being OffLine, or Self-Test failures.

The program sets the values in the DateTime arrays PlantTimer and CtlrTimer equal to the system Time, thereby resetting them.

The program clears the CX9200 Status4 Self-Test failure indicator.

The program then searches through all of the CX9200 numerics. If the numeric name ends in “.Fail” or “.OVRR”, it’s value is set to OFF. Since the Self-Test failures (“.ST.Fail”) end with “.Fail”, they will get cleared.

This program is called by MAIN program when the CLEAR FAULTS pushbutton on the FSCS is pressed. The CLEAR FAULTS pushbutton will only be acknowledged if the Master Key is ON, therefore the faults can only be cleared when the Master Key in ON.




TOC

FireAlarmCheck

Type: FunctionDescription: Determines whether or not, and in which zones, to perform smoke control. Sets the FSCS Alarm LEDs based on the inputs from the Fire Panel.

Code: ‘ Set .ALM Numerics in order to Update the FSCS LEDs Zone1.ALM, Zone2.ALM, Zone3.ALM, Zone4.ALM and ~ STRWL.ALM = Off If Zone1.EST then Zone1.ALM = On If Zone2.EST then Zone2.ALM = On If Zone3.EST then Zone3.ALM = On If Zone4.EST then Zone4.ALM = On If STRWL.EST then STRWL.ALM = On ‘ Set SMOKE.ALM and Stop SmokeSelfTest if any Zones are in ‘ Alarm SMOKE.ALM = Zone1.ALM + Zone2.ALM + Zone3.ALM + ~ Zone4.ALM + STRWL.ALM If SMOKE.ALM then Stop SmokeSelfTest ‘ Clear Smoke Control When the Alarm is Off If Zone1.ALM = Off then Zone1.SMK = Off If Zone2.ALM = Off then Zone2.SMK = Off If Zone3.ALM = Off then Zone3.SMK = Off If Zone4.ALM = Off then Zone4.SMK = Off If STRWL.ALM = Off then STRWL.SMK = Off ‘ Return if the System has already responded to the First Smoke ‘ Alarm FIRST.SMK = Zone1.SMK + Zone2.SMK + Zone3.SMK + ~ Zone4.SMK + STRWL.SMK If FIRST.SMK then Return ‘ Initiate Only One Smoke Control Strategy If Zone1.ALM then Zone1.SMK = On Else If Zone2.ALM then Zone2.SMK = On Else If Zone3.ALM then Zone3.SMK = On Else




TOC

If Zone4.ALM then Zone4.SMK = On Else If STRWL.ALM then STRWL.SMK = On Endif Endif Endif Endif Endif Return

File Explanation:

This function sets the “.ALM” numerics for the FSCS Alarm LEDs and the “.SMK” numerics that cause the system to begin performing smoke control in a particular zone.


• Set all Alarm LED numerics to OFF. Turn the Alarm LED numeric back ON if the Fire Panel shows that zone to be in an Alarm condition. Since this is a function, only the final value of the numeric will be used by the CX9200.

• If there are any alarms, turn the SMOKE.ALM numeric ON, which prevents the system from running a weekly self-test, and Stop the weekly self-test if it is currently running.

• Clear the Smoke Control numeric (“.SMK”), if the Alarm (“.ALM”) goes away. Therefore there is no need to reset the Infinity smoke control system. When the Alarm is cleared at the Fire Panel, it also resets the smoke control system.

• If any one of the Smoke Control numerics (“.SMK”) is ON, set the numeric FIRST.SMK to ON. If FIRST.SMK is ON, then the system is already performing smoke control in a zone, and the function ends due to the RETURN statement. NFPA 92A requires that the system only respond to the first alarm.

• If FIRST.SMK is OFF, then the function checks to see if any of the “ .ALM” numerics are ON. If so, then the corresponding “.SMK” numeric is turned ON, thus starting a smoke control strategy in that zone. Since this is performed using one “If-Then-Else” statement, the function will only react to the first Alarm, per NFPA 92A.




TOC

SmokeSelfTest

Type: ProgramFlowType: FallthruDescription: Runs a weekly self-test on the dedicated controllers.

Code: Begin_Prog: ‘Clear Self-Test Faults AH3Sfan.ST.Fail = Off FL2SADmp.ST.Fail = Off FL2RADmp.ST.Fail = Off FL3SADmp.ST.Fail = Off FL3RADmp.ST.Fail = Off FL4SADmp.ST.Fail = Off FL4RADmp.ST.Fail = Off RunTests: Print chr(7), “ **** SELF TESTING DEDICATED SMOKE CONTROL SYSTEM - SMOKE DAMPERS. **** “ to COMM3 StatusBar CloseDampersS: SMKDMPRS DefaultDmprPosn = On WaitForDampersSC: ‘ Wait for max damper plant time + 5 Secs to detect fault. If TS < (MaxDamperTime + 5) then Goto WaitForDampersSC ‘Latch Self-Test Failures If FL2SADmp.Fail then FL2SADmp.ST.Fail = On If FL2RADmp.Fail then FL2RADmp.ST.Fail = On If FL3SADmp.Fail then FL3SADmp.ST.Fail = On If FL3RADmp.Fail then FL3RADmp.ST.Fail = On If FL4SADmp.Fail then FL4SADmp.ST.Fail = On If FL4RADmp.Fail then FL4RADmp.ST.Fail = On OpenDampersS: SMKDMPRS DefaultDmprPosn = Off WaitForDampersSO: ‘ Wait for max damper plant time + 5 Secs to detect fault. If TS < (MaxDamperTime + 5) then Goto WaitForDampersSO




TOC

‘Latch Self-Test Failures If FL2SADmp.Fail then FL2SADmp.ST.Fail = On If FL2RADmp.Fail then FL2RADmp.ST.Fail = On If FL3SADmp.Fail then FL3SADmp.ST.Fail = On If FL3RADmp.Fail then FL3RADmp.ST.Fail = On If FL4SADmp.Fail then FL4SADmp.ST.Fail = On If FL4RADmp.Fail then FL4RADmp.ST.Fail = On Ctlr3Check: ‘ Test AHU3 Plant. Print chr(7), “ **** SELF TESTING DEDICATED SMOKE CONTROL SYSTEM - AHU3. **** “ to COMM3 StatusBar StartFans3: AHU3 DefaultFanPosn = On WaitForFans3St: ‘ Wait for max fan plant time + 5 Secs to detect fault. If TS < (MaxFanTime + 5) then Goto WaitForFans3St ‘Latch Self-Test Failures If AH3Sfan.Fail then AH3Sfan.ST.Fail = On StopFans3: AHU3 DefaultFanPosn = Off WaitForFans3Sp: ‘ Wait for max fan plant time + 5 Secs to detect fault. If TS < (MaxFanTime + 5) then Goto WaitForFans3Sp ‘Latch Self-Test Failures If AH3Sfan.Fail then AH3Sfan.ST.Fail = On Set_Status4: Status4 = Off If AH3Sfan.ST.Fail then Status4 = On If FL2SADmp.ST.Fail then Status4 = On If FL2RADmp.ST.Fail then Status4 = On If FL3SADmp.ST.Fail then Status4 = On If FL3RADmp.ST.Fail then Status4 = On If FL4SADmp.ST.Fail then Status4 = On If FL4RADmp.ST.Fail then Status4 = On TestComplete: Print “ Weekly Self Test Complete “, Time




TOC

SelfTested = True Stop

File Explanation:

This program runs a weekly self-test on the dedicated controllers in the system. In this example, the SCX920S smoke damper controller, SMKDMPRS, and the TCX853 stairwell fan controller, AHU3, are the only dedicated controllers.

Assumming the system is not performing smoke control, this program is run by the MAIN program at Midnight on Saturdays.


• Clear all self-test failure numerics (“.ST.Fail”).

• First the smoke dampers are tested in the Closed position by setting SMKDMPRS DefaultDmprPosn = ON. The program then waits for a period of time equal to MaxDamperTime + 5 seconds. If a “.Fail” numeric is set by the PlantFaultCheck function, then it’s corresponding self-test failure numeric (“.ST.Fail”) is turned ON. Turning on this numeric causes the self-test failure to be latched. The only way to clear it is to turn ON the Master Key and press CLEAR FAULTS.

• Next the smoke dampers are tested in the Open position by setting SMKDMPRS DefaultDmprPosn = OFF. Again the program waits for MaxDamperTime + 5 and sets the self-test failure numeric if it’s corresponding failure numeric is turned ON by PlantFaultCheck.

• Next the stairwell fan is tested in the ON state by setting AHU3 DefaultFanPosn = ON. The program waits for MaxFanTime + 5 and sets the self-test failure numeric if it’s corresponding failure numeric is turned ON by PlantFaultCheck.

• Next the stairwell fan is tested in the OFF state by setting AHU3 DefaultFanPosn = OFF. The program waits for MaxFanTime + 5 and sets the self-test failure numeric if it’s corresponding failure numeric is turned ON by PlantFaultCheck.

• If there are any self-test failures, turn ON the Status4 indicator.

• Print “Weekly Self Test Complete” and the Time to the Message window.

• Set the numeric SelfTested to TRUE, therefore the system will not perform another self-test until the following week.




TOC

Prog rams for C ontrol ling the Syste m

Main

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: The main sequencing program. This program determines what the entire system is doing by calling the other programs and functions.

Code:

Initialize: Zone1.SMK, Zone2.SMK, Zone3.SMK, Zone4.SMK and ~ STRWL.SMK = Off MaxDamperTime = 60 ‘Seconds MaxFanTime = 45 ‘Seconds MaxCtlrTime = 10 ‘Seconds FSCSLinkActive = False Horn = Off SelfTested = True Print “*** Smoke Control System Initialized at “ ; Time ; “ ***” Goto MainLoop MainLoop: FireAlarmCheck() NetStatus() PilotLights() PlantFaultCheck() ‘Run FSCS_Interface to Read Switches and Update LEDs If FSCSLinkActive is False then FSCSLinkActive = True Run FSCS_Interface Endif ‘Run HornControl If HornControl Status is not Active then Run HornControl ‘Run ClearFaults if Fault.Clear Button is Pushed If Fault.Clear and ClearFaults Status is not Active then Run ~ ClearFaults ‘ Check if time for Weekly self test. Run Self-Test if There are no




TOC

‘ Smoke Alarms and Time is Between 12PM and 4AM If (not SMOKE.ALM) and (Weekday < Saturday) and ~ (Hour <= 4) and (not SelfTested) and ~ (SmokeSelfTest Status is not Active) then Run SmokeSelfTest Endif If Weekday = Saturday then SelfTested = False ‘Print Time to Comm3 Statusbar when not running self-test If SmokeSelfTest Status is not Active then Print “ “ ; Time to COMM3 StatusBar Endif Goto Wait_MainLoop Wait_MainLoop: If TS >= 1 then Goto MainLoop

File Explanation:

This program is the main calling and sequencing program for the smoke control system. It determines which programs and functions are called, and in what order. This is an AutoStart program, so it will automatically start when the program has been loaded.


• Initialize some of the system numerics such as the Smoke Control flags (“.SMK”), MaxDamperTime, MaxFanTime, MaxCtlrTime, FSCSLinkActive, Horn, and SelfTested.

• Print “*** Smoke Control System Initialized at “;Time;” ***” to the Message window.

MainLoop:• Call the FireAlarmCheck function.

• Call the NetStatus function.

• Call the PilotLights function.

• Call the PlantFaultCheck function.

• If the FSCS_Interface program is not running (FSCSLinkActive is FALSE), Then set FSCSLinkActive to TRUE and Run the FSCS_Interface program.

• Run the HornControl program if it is not already running.




TOC

• Run the ClearFaults program if it is not already running, and the CLEAR FAULTS button on the FSCS is pressed.

• Run the weekly self-test program, SmokeSelfTest, if all of the following conditions are met:

— The SMOKE.ALM numeric is OFF, indicating that the system is not currently responding to an Alarm.

— The Weekday is Sunday Through Friday. If the system is not re-sponding to an Alarm, the self-test will occur when Weekday = Sunday.

— The Hour is between 0 and 4. If the system is not responding to an Alarm, the self-test will occur when Hour = 0.

— The SelfTested flag is OFF, indicating that the system has not been self-tested this week.

— The SmokeSelfTest program is not currently running.

• If Weekday is equal to Saturday, then set the SelfTested flag to FALSE. Therefore the system will be ready to perform a self-test the following week.

• Print the Time to the COMM3 Statusbar if the SmokeSelfTest program is not running.

• Delay for 1 second, then Goto MainLoop: and repeat the sequence again.




TOC

FirstAid

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Initializes the system when a System Error occurs, or when the System Time is changed.

Code: DateTime Timer1 Initialize: Timer1 = Time Goto CheckForErrors CheckForErrors: If Errors > 0 then Goto Restart If abs(DiffTime(Second, Time, Timer1)) > 4 then Goto Restart Timer1 = Time If Main State is Disabled then Goto Restart If Main Status is not Active then Goto Restart Goto WaitForErrors WaitForErrors: If TS > 2 then Goto CheckForErrors Restart: Enable HornControl Enable FSCS_Interface Enable ClearFaults Enable SmokeSelfTest Enable Main Run Main Errors = 0 Goto Initialize




TOC

File Explanation:

This program restarts the system if a the CX9200 System Variable ERRORS is greater than 0, the System Date and Time is changed by more then 5 seconds, the MAIN program is disabled, or the MAIN program is not Running. This is an AutoStart program, so it will automatically start when the program has been loaded.

In order to restart the system, this program Enables all of the programs in the CX9200, Runs the Main program, then sets ERRORS = 0.




TOC

Controlling th e Smoke Damper sSMKDMPRS (SCX920S)

The SCX920S named SMKDMPRS is responsible for controlling the smoke dampers on floor2, floor3, and floor4. Since these smoke dampers are not used for HVAC, this is a dedicated controller.

Table 5-2 lists the programs that are used by the SCX920S for this application.:

OVR_Check

Type: FunctionDescription: Checks the Outputs for an Override.Code: OverrideOn = Off If Fl2.SASDmp Override then OverrideOn = On If Fl2.RASDmp Override then OverrideOn = On If Fl3.SASDmp Override then OverrideOn = On If Fl3.RASDmp Override then OverrideOn = On If Fl4.SASDmp Override then OverrideOn = On If Fl4.RASDmp Override then OverrideOn = On Return

File Explanation:

This function turns ON the numeric OverrideON if any of the outputs are overridden. The OverrideOn flag is used by the CX9200 to turn on an Override Fault on the FSCS.

Table 5-2. SMKDMPRS Files


OVR_Check Function Checks the Outputs for an Override.

Damper_Control Program Controls the state of the Smoke Dampers.




TOC

DAMPER_Control

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Controls the state of the Smoke Dampers. Code: ‘ Note: Digital Outputs not Tristate. ‘ ON activates (Closes) the Dampers. Initialize: DefaultDmprPosn = Off Goto DamperControl

DamperControl: ‘ Floor (Zone) 2 Smoke Damper Control ‘ Supply Air Damper If INFINITY1 FL2SADmp.OVR.Cls then Fl2.SASDmp = On Else If INFINITY1 FL2SADmp.OVR.Opn then Fl2.SASDmp = Off Else If INFINITY1 Zone2.EXH then Fl2.SASDmp = On Else If INFINITY1 Zone2.PRS then Fl2.SASDmp = Off Else If INFINITY1 Zone2.SMK then Fl2.SASDmp = On Else If INFINITY1 Zone1.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then Fl2.SASDmp = Off Else Fl2.SASDmp = DefaultDmprPosn Endif Endif Endif Endif Endif Endif




TOC

‘ Return Air Damper If INFINITY1 FL2RADmp.OVR.Cls then Fl2.RASDmp = On Else If INFINITY1 FL2RADmp.OVR.Opn then Fl2.RASDmp = Off Else If INFINITY1 Zone2.EXH then Fl2.RASDmp = Off Else If INFINITY1 Zone2.PRS then Fl2.RASDmp = On Else If INFINITY1 Zone2.SMK then Fl2.RASDmp = Off Else If INFINITY1 Zone1.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then Fl2.RASDmp = On Else Fl2.RASDmp = DefaultDmprPosn Endif Endif Endif Endif Endif Endif ‘ Floor (Zone) 3 Smoke Damper Control ‘ Supply Air Damper If INFINITY1 FL3SADmp.OVR.Cls then Fl3.SASDmp = On Else If INFINITY1 FL3SADmp.OVR.Opn then Fl3.SASDmp = Off Else If INFINITY1 Zone3.EXH then Fl3.SASDmp = On Else If INFINITY1 Zone3.PRS then Fl3.SASDmp = Off Else If INFINITY1 Zone3.SMK then Fl3.SASDmp = On




TOC

Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then Fl3.SASDmp = Off Else Fl3.SASDmp = DefaultDmprPosn Endif Endif Endif Endif Endif Endif ‘ Return Air Damper If INFINITY1 FL3RADmp.OVR.Cls then Fl3.RASDmp = On Else If INFINITY1 FL3RADmp.OVR.Opn then Fl3.RASDmp = Off Else If INFINITY1 Zone3.EXH then Fl3.RASDmp = Off Else If INFINITY1 Zone3.PRS then Fl3.RASDmp = On Else If INFINITY1 Zone3.SMK then Fl3.RASDmp = Off Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then Fl3.RASDmp = On Else Fl3.RASDmp = DefaultDmprPosn Endif Endif Endif Endif Endif Endif ‘ Floor (Zone) 4 Smoke Damper Control ‘ Supply Air Damper




TOC

If INFINITY1 FL4SADmp.OVR.Cls then Fl4.SASDmp = On Else If INFINITY1 FL4SADmp.OVR.Opn then Fl4.SASDmp = Off Else If INFINITY1 Zone4.EXH then Fl4.SASDmp = On Else If INFINITY1 Zone4.PRS then Fl4.SASDmp = Off Else If INFINITY1 Zone4.SMK then Fl4.SASDmp = On Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK ~ or INFINITY1 Zone2.SMK or INFINITY1 ~ STRWL.SMK then Fl4.SASDmp = Off Else Fl4.SASDmp = DefaultDmprPosn Endif Endif Endif Endif Endif Endif ‘ Return Air Damper If INFINITY1 FL4RADmp.OVR.Cls then Fl4.RASDmp = On Else If INFINITY1 FL4RADmp.OVR.Opn then Fl4.RASDmp = Off Else If INFINITY1 Zone4.EXH then Fl4.RASDmp = Off Else If INFINITY1 Zone4.PRS then Fl4.RASDmp = On Else If INFINITY1 Zone4.SMK then Fl4.RASDmp = Off Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK ~ or INFINITY1 Zone3.SMK or INFINITY1 ~




TOC

STRWL.SMK then Fl4.RASDmp = On Else Fl4.RASDmp = DefaultDmprPosn Endif Endif Endif Endif Endif Endif ‘Call Override Check Function OVR_Check() Goto DamperControl

File Explanation:

This program controls the state of all six of the smoke dampers in this example --> supply and return dampers for floor2, floor3, and floor4.

Each damper is controlled by it’s own set of nested “if-then-else” statements. The “level” that the statement appears on determines the priority of for that action. The FSCS overrides must have the highest priority, then come the automatic smoke control modes, and the HVAC or self-test modes have the lowest priority.

Take the Floor2 Supply Air Damper portion of the code as an example:

‘ Floor (Zone) 2 Smoke Damper Control ‘ Supply Air Damper If INFINITY1 FL2SADmp.OVR.Cls then Fl2.SASDmp = On Else If INFINITY1 FL2SADmp.OVR.Opn then Fl2.SASDmp = Off Else If INFINITY1 Zone2.EXH then Fl2.SASDmp = On Else If INFINITY1 Zone2.PRS then Fl2.SASDmp = Off Else If INFINITY1 Zone2.SMK then




TOC

Fl2.SASDmp = On Else If INFINITY1 Zone1.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then Fl2.SASDmp = Off Else Fl2.SASDmp = DefaultDmprPosn Endif Endif Endif Endif Endif Endif

This algorithm will perform the following:

• If the FSCS override to close this damper (FL2SADmp.OVR.Cls) is ON, then close the damper (Fl2.SASDmp = ON), and skip the remaining nested If-then else statements.

• If the FSCS override to open this damper (FL2SADmp.OVR.Opn) is ON, then open the damper (Fl2.SASDmp = Off), and skip the remaining nested If-then else statements.

• If the FSCS override to exhaust Zone2 (Zone2.EXH) is ON, then close the damper and skip the remaining nested If-then else statements.

• If the FSCS override to pressurize Zone2 (Zone2.PRS) is ON, then open the damper and skip the remaining nested If-then else statements.

• If the automatic smoke control for Zone2 has been triggered (Zone2.SMK = ON), then close the damper in order to exhaust Zone2, and skip the remaining nested If-then else statements.

• If the automatic smoke control for any zone other than Zone2 has been triggered (Zone1.SMK or Zone3.SMK or Zone4.SMK or STRWL.SMK = ON), then open the damper in order to pressurize Zone2, and skip the remaining nested If-then else statements.

• If none of the above events have occurred, then set the state of the damper is set equal to the numeric DefaultDmprPosn. In this case, the SmokeSelfTest program in the CX9200 sets the value of DefaultDmprPosn in order to perform a weekly self-test.




TOC

The other five dampers are controlled the same way, except they are controlled by different numerics.




TOC

Controlling th e Air Handling UnitsAHU1 (SCX920S)

The SCX920S named AHU1 is responsible for controlling the fans and dampers in Air Handling Unit #1. AHU1 is used for floor1. Since AHU1 is used for HVAC and smoke control, it is a non-dedicated controller.


OVR_Check

Type: FunctionDescription: Checks the Outputs for an Override.Code: OverrideOn = Off If Sfan Override then OverrideOn = On If Rfan Override then OverrideOn = On If OADmp Override then OverrideOn = On If EADmp Override then OverrideOn = On If RADmp Override then OverrideOn = On Return

File Explanation:


Table 5-3. AHU1 Files



AHU_Control Program Controls the state of the Air Handling Unit’s Fans and Dampers.

HVAC Program Used to Simulate an HVAC program.




TOC

AHU_Control

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Controls the state of the Air Handling Unit’s Fans and Dampers.Code: FanControl: ‘ Supply Fan Control If INFINITY1 AH1Sfan.OVR.Off then Sfan = Off Else If INFINITY1 AH1Sfan.OVR.On then Sfan = On Else If INFINITY1 Zone1.EXH then Sfan = Off Else If INFINITY1 Zone1.PRS then Sfan = On Else If INFINITY1 Zone1.SMK then Sfan = Off ‘Exhaust Else If INFINITY1 Zone2.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then Sfan = On ‘pressurize Else Sfan = Default.Sfan ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif ‘ Return Fan Control If INFINITY1 AH1Rfan.OVR.On then Rfan = On Else If INFINITY1 AH1Rfan.OVR.Off then Rfan = Off Else




TOC

If INFINITY1 Zone1.EXH then Rfan = On Else If INFINITY1 Zone1.PRS then Rfan = Off Else If INFINITY1 Zone1.SMK then Rfan = On ‘Exhaust Else If INFINITY1 Zone2.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then Rfan = Off ‘ pressurize Else Rfan = Default.Rfan ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif Goto DamperControl DamperControl: ‘ Outside (Supply) Air Damper If INFINITY1 AH1OADmp.OVR.Cls then OADmp = -On Else If INFINITY1 AH1OADmp.OVR.Opn then OADmp = On Else If INFINITY1 Zone1.EXH then OADmp = -On Else If INFINITY1 Zone1.PRS then OADmp = On Else If INFINITY1 Zone1.SMK then OADmp = -On ‘ Exhaust Else If INFINITY1 Zone2.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then OADmp = On ‘ pressurize Else OADmp = DefaultDmpr.OA ‘ Normal HVAC Control




TOC

Endif Endif Endif Endif Endif Endif ‘ Exhaust Air Damper If INFINITY1 AH1EADmp.OVR.Opn then EADmp = On Else If INFINITY1 AH1EADmp.OVR.Cls then EADmp = -On Else If INFINITY1 Zone1.EXH then EADmp = On Else If INFINITY1 Zone1.PRS then EADmp = -On Else If INFINITY1 Zone1.SMK then EADmp = On ‘ Exhaust Else If INFINITY1 Zone2.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then EADmp = -On ‘ pressurize Else EADmp = DefaultDmpr.EA ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif ‘ Return’ Air Damper If INFINITY1 AH1RADmp.OVR.Opn then RADmp = On Else If INFINITY1 AH1RADmp.OVR.Cls then RADmp = -On Else If INFINITY1 Zone1.EXH then RADmp = -On ‘Close Else




TOC

If INFINITY1 Zone1.PRS then RADmp = -On ‘ Close Else If INFINITY1 Zone1.SMK then RADmp = -On ‘ Close Else If INFINITY1 Zone2.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then RADmp = -On ‘ Close Else RADmp = DefaultDmpr.RA ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif ‘Call Override Check Function OVR_Check() Goto FanControl

File Explanation:

This program controls the state of the Supply fan, Return fan, Outside Air damper, Exhaust Air damper, and Return Air damper for AHU1.

Each fan or damper is controlled by it’s own set of nested “if-then-else” statements. The nested “if-then-else” statements prioritize the control modes as follows:

• The FSCS overrides: ON-OFF, OPEN-CLOSE

• Automatic Smoke Control

• HVAC control

The HVAC control is performed by setting the default values for each fan or damper: Default.Sfan, Default.Rfan, DefaultDmpr.OA, DefaultDmpr.EA, DefaultDmpr.RA.

This program also calls the OVR_Check function.




TOC

HVAC

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Used to Simulate an HVAC program.Code: Set_Fans: Default.Sfan = On Default.Rfan = On Goto Outside_Air Outside_Air: DefaultDmpr.OA = 2 DefaultDmpr.EA = 2 DefaultDmpr.RA = -2 If TS > 2 then Goto Recirculate Recirculate: DefaultDmpr.OA = -2 DefaultDmpr.EA = -2 DefaultDmpr.RA = 2 If TS > 2 then Goto Set_Fans

File Explanation:

This program is for demonstration purposes only and is used to show how the smoke control modes have a higher priority than the HVAC modes. This program does not perform an HVAC function.




TOC

AHU2 (SCX920S)

The SCX920S named AHU2 is responsible for controlling the fans and dampers in Air Handling Unit #2. AHU1 is used for floor2, floor3, and floor4. Since AHU2 is used for HVAC and smoke control, it is a non-dedicated controller.


OVR_Check

Type: FunctionDescription: Checks the Outputs for an Override.Code: OverrideOn = Off If Sfan Override then OverrideOn = On If Rfan Override then OverrideOn = On If OADmp Override then OverrideOn = On If EADmp Override then OverrideOn = On If RADmp Override then OverrideOn = On Return

File Explanation:





AHU_Control Program Controls the state of the Air Handling Unit’s Fans and Dampers.





TOC

AHU_Control

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Controls the state of the Air Handling Unit’s Fans and Dampers.Code: FanControl: ‘ Supply Fan Control If INFINITY1 AH2Sfan.OVR.Off then Sfan = Off Else If INFINITY1 AH2Sfan.OVR.On then Sfan = On Else If INFINITY1 Zone2.PRS or INFINITY1 Zone3.PRS or ~ INFINITY1 Zone4.PRS then Sfan = On Else If INFINITY1 Zone2.EXH and INFINITY1 Zone3.EXH ~ and INFINITY1 Zone4.EXH then Sfan = Off ‘ Exhaust only Else If INFINITY1 Zone2.SMK and INFINITY1 Zone3.SMK ~ and INFINITY1 Zone4.SMK then Sfan = Off ‘Exhaust only all zones in smoke Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK ~ or INFINITY1 Zone3.SMK or INFINITY1 ~ Zone4.SMK or INFINITY1 STRWL.SMK then Sfan = On ‘Another zone is in smoke Else Sfan = Default.Sfan ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif ‘ Return Fan Control If INFINITY1 AH2Rfan.OVR.On then Rfan = On Else If INFINITY1 AH2Rfan.OVR.Off then




TOC

Rfan = Off Else If INFINITY1 Zone2.EXH or INFINITY1 Zone3.EXH or ~ INFINITY1 Zone4.EXH then Rfan = On ‘At least 1 zone needs exhausting Else If INFINITY1 Zone2.PRS and INFINITY1 Zone3.PRS ~ and INFINITY1 Zone4.PRS then Rfan = Off ‘ All zones pressurized turn off fan Else If INFINITY1 Zone2.SMK or INFINITY1 Zone3.SMK or ~ INFINITY1 Zone4.SMK then Rfan = On ‘Smoke detected on one of the floors Else If INFINITY1 Zone1.SMK or INFINITY1 STRWL.SMK ~ then Rfan = Off ‘ pressurize as Zone 1 or Stairs is in smoke Else Rfan = Default.Rfan ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif Goto DamperControl DamperControl: ‘ Outside (Supply) Air Damper If INFINITY1 AH2OADmp.OVR.Cls then OADmp = -On Else If INFINITY1 AH2OADmp.OVR.Opn then OADmp = On Else If INFINITY1 Zone2.PRS or INFINITY1 Zone3.PRS or ~ INFINITY1 Zone4.PRS then OADmp = On ‘ a zone in pressurization Else If INFINITY1 Zone2.EXH and INFINITY1 Zone3.EXH ~ and INFINITY1 Zone4.EXH then OADmp = -On ‘All zones in exhaust Else If INFINITY1 Zone2.SMK and INFINITY1 Zone3.SMK ~ and INFINITY1 Zone4.SMK then OADmp = -On ‘ Close Damper all zones in smoke




TOC

Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK ~ or INFINITY1 Zone3.SMK or INFINITY1 ~ Zone4.SMK or INFINITY1 STRWL.SMK then OADmp = On ‘ pressurize a zone is in smoke Else OADmp = DefaultDmpr.OA ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif ‘ Exhaust Air Damper If INFINITY1 AH2EADmp.OVR.Opn then EADmp = On Else If INFINITY1 AH2EADmp.OVR.Cls then EADmp = -On Else If INFINITY1 Zone2.EXH or INFINITY1 Zone3.EXH or ~ INFINITY1 Zone4.EXH then EADmp = On ‘Open damper exhaust required Else If INFINITY1 Zone2.PRS and INFINITY1 Zone3.PRS ~ and INFINITY1 Zone4.PRS then EADmp = -On ‘Close damper all zones being pressurized Else If INFINITY1 Zone2.SMK or INFINITY1 Zone3.SMK or ~ INFINITY1 Zone4.SMK then EADmp = On ‘ Exhaust, smoke on at least 1 floor Else If INFINITY1 Zone1.SMK or INFINITY1 STRWL.SMK ~ then EADmp = -On ‘ pressurize smoke in Zone 1 or Stairs Else EADmp = DefaultDmpr.EA ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif




TOC

‘ Return’ Air Damper If INFINITY1 AH2RADmp.OVR.Opn then RADmp = On Else If INFINITY1 AH2RADmp.OVR.Cls then RADmp = -On Else If INFINITY1 Zone2.EXH or INFINITY1 Zone3.EXH or ~ INFINITY1 Zone4.EXH then RADmp = -On ‘Close on any exhaust Else If INFINITY1 Zone2.PRS or INFINITY1 Zone3.PRS or ~ INFINITY1 Zone4.PRS then RADmp = -On ‘ Close on any pressurization Else If INFINITY1 Zone2.SMK or INFINITY1 Zone3.SMK or ~ INFINITY1 Zone4.SMK then RADmp = -On ‘ Close on any smoke detected Else If INFINITY1 Zone1.SMK or INFINITY1 STRWL.SMK ~ then RADmp = -On ‘ Adjacent zone smoke detected Else RADmp = DefaultDmpr.RA Normal HVAC Control Endif Endif Endif Endif Endif Endif ‘Call Override Check Function OVR_Check Goto FanControl

File Explanation:

This program controls the state of the Supply fan, Return fan, Outside Air damper, Exhaust Air damper, and Return Air damper for AHU2.

Each fan or damper is controlled by it’s own set of nested “if-then-else” statements. The nested “if-then-else” statements prioritize the control modes as follows:




TOC

• The FSCS overrides: ON-OFF, OPEN-CLOSE


• HVAC control

The HVAC control is performed by setting the default values for each fan or damper: Default.Sfan, Default.Rfan, DefaultDmpr.OA, DefaultDmpr.EA, DefaultDmpr.RA.

This program also calls the OVR_Check function.




TOC

HVAC

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Used to Simulate an HVAC program.Code: Set_Fans: Default.Sfan = On Default.Rfan = On Goto Outside_Air Outside_Air: DefaultDmpr.OA = 2 DefaultDmpr.EA = 2 DefaultDmpr.RA = -2 If TS > 2 then Goto Recirculate Recirculate: DefaultDmpr.OA = -2 DefaultDmpr.EA = -2 DefaultDmpr.RA = 2 If TS > 2 then Goto Set_Fans

File Explanation:





TOC

Controlling th e Stairwell FanAHU3 (TCX853)

The TCX853 named AHU3 is responsible for controlling the stairwell fan. Since the stairwell fan is not used for HVAC, this is a dedicated controller.

Table 5-5 lists the programs that are used by the TCX853 for this application.:

AHU_Control

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Controls the state of the Stairwell FanCode: Initialize: DefaultFanPosn = Off Goto FanControl FanControl: ‘ Supply Fan Control If INFINITY1 AH3Sfan.OVR.Off then Sfan = Off Else If INFINITY1 AH3Sfan.OVR.On then Sfan = On Else If INFINITY1 STRWL.PRS then Sfan = On Else If INFINITY1 STRWL.SMK then Sfan = Off ‘Stop Supply Fan as Zone in Fire Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK or ~ INFINITY1 Zone3.SMK or INFINITY1 Zone4.SMK then Sfan = On ‘pressurize Else



AHU_Control Program Controls the state of the Stairwell Fan




TOC

Sfan = DefaultFanPosn Endif Endif Endif Endif Endif Goto FanControl

File Explanation:

The stairwell fan is controlled by a set of nested “if-then-else” statements. The nested “if-then-else” statements prioritize the control modes as follows:

• The FSCS overrides: ON-OFF


• Weekly Self-Test

The SmokeSelfTest program in the CX9200 performs the weekly self-test by setting the value of DefaultFanPosn.




TOC

Controlling th e VAV TerminalsFlr2TCX (TCX840)

The TCX840 named Flr2TCX is responsible for controlling the VAV terminal for floor2. Since Flr2TCX is used for HVAC and smoke control, it is a non-dedicated controller.


VAV_Control

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Controls the VAV damper on Floor2Code: VAVDamperControl: If INFINITY1 FL2VAV.OVR.Opn then VAVDmp = On Else If INFINITY1 FL2VAV.OVR.Cls then VAVDmp = -On Else If INFINITY1 Zone2.EXH then VAVDmp = -On ‘Close VAV Else If INFINITY1 Zone2.PRS then VAVDmp = On ‘Open VAV Else If INFINITY1 Zone2.SMK then VAVDmp = -On ‘ Exhaust Zone Close VAV Else If INFINITY1 Zone1.SMK or INFINITY1 Zone3.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then VAVDmp = On ‘ pressurize Zone

Table 5-6. Flr2TCX Files


VAV_Control Program Controls the VAV damper on Floor2





TOC

Else VAVDmp = DefaultDmprPosn ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif Goto VAVDamperControl

File Explanation:

The VAV damper is controlled by a set of nested “if-then-else” statements. The nested “if-then-else” statements prioritize the control modes as follows:

• The FSCS overrides: OPEN-CLOSE


• HVAC control

The HVAC control is performed by setting the value of DefaultDmprPosn.




TOC

HVAC

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Used to Simulate an HVAC program.Code: Close_Damper: DefaultDmprPosn = -2 If TS > 2 then Goto Open_Damper Open_Damper: DefaultDmprPosn = 2 If TS > 2 then Goto Close_Damper

File Explanation:





TOC

Flr3TCX (TCX851)



VAV_Control

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Controls the VAV damper on Floor3Code: VAVDamperControl: If INFINITY1 FL3VAV.OVR.Opn then VAVDmp = On Else If INFINITY1 FL3VAV.OVR.Cls then VAVDmp = -On Else If INFINITY1 Zone3.EXH then VAVDmp = -On ‘Close VAV Else If INFINITY1 Zone3.PRS then VAVDmp = On ‘Open VAV Else If INFINITY1 Zone3.SMK then VAVDmp = -On ‘ Exhaust Zone Close VAV Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK ~ or INFINITY1 Zone4.SMK or INFINITY1 ~ STRWL.SMK then VAVDmp = On ‘ pressurize Zone Else VAVDmp = DefaultDmprPosn ‘ Normal HVAC Control Endif



VAV_Control Program Controls the VAV damper on Floor3





TOC

Endif Endif Endif Endif Endif Goto VAVDamperControl

File Explanation:




• HVAC control





TOC

HVAC

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Used to Simulate an HVAC program.Code: Close_Damper: DefaultDmprPosn = -2 If TS > 2 then Goto Open_Damper Open_Damper: DefaultDmprPosn = 2 If TS > 2 then Goto Close_Damper

File Explanation:





TOC

Flr4TCX (TCX861)



VAV_Control

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Controls the VAV damper on Floor4.Code: ‘ 0 --> Opens Damper 1 --> Closes Damper VAVDamperControl: If INFINITY1 FL4VAV.OVR.Opn then Damper = 0 Else If INFINITY1 FL4VAV.OVR.Cls then Damper = 1 Else If INFINITY1 Zone4.EXH then Damper = 1 ‘Close VAV Else If INFINITY1 Zone4.PRS then Damper = 0 ‘Open VAV Else If INFINITY1 Zone4.SMK then Damper = 1 ‘ Exhaust Zone Close VAV Else If INFINITY1 Zone1.SMK or INFINITY1 Zone2.SMK ~ or INFINITY1 Zone3.SMK or INFINITY1 ~



VAV_Control Program Controls the VAV damper on Floor4.


DamperFeedback Program Used to Read the Feedback of the Damper Position.

AutoLearn Program Used to perform a Learn of the Damper Position.




TOC

STRWL.SMK then Damper = 0 ‘ pressurize Zone Else Damper = DefaultDmprPosn ‘ Normal HVAC Control Endif Endif Endif Endif Endif Endif Goto VAVDamperControl

File Explanation:




• HVAC control


In this example, setting the output to 0 will open the damper, and setting the damper to 1 will close the damper.




TOC

HVAC

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Used to Simulate an HVAC program.Code: Close_Damper: DefaultDmprPosn = 0.6 If (Damper OverrideValue > 0.595) and (Damper OverrideValue < 0.605) then Goto Close_Wait Close_Wait: If TS > 4 then Goto Open_Damper Open_Damper: DefaultDmprPosn = 0.4 If (Damper OverrideValue > 0.395) and (Damper OverrideValue < 0.405) then Goto Open_Wait Open_Wait: If TS > 4 then Goto Close_Damper EndCodeEndObject

File Explanation:





TOC

DamperFeedback

Type: ProgramFlowType: LoopingAutoStart: TrueDescription: Used to Read the Feedback of the Damper Position.Code: ‘ 0 = OPEN, 1 = CLOSED

Feedback: If Damper OverrideValue < 0.005 then Damper.Opn = On Else Damper.Opn = Off Endif If Damper OverrideValue > 0.995 then Damper.Cls = On Else Damper.Cls = Off Endif

DamperPosition = Damper Overridevalue

File Explanation:

This program is used to read the feedback of the damper position using the on-board Hall-Effect sensor on the TCX861.

The Damper.Opn and Damper.Cls numerics are used by the CX9200 to set the FSCS OPEN and CLOSE LEDs. The DamperPosition numeric is used by the CX9200 PlantFaultCheck function to determine if the damper reaches it’s desired state within 75 seconds, per NFPA 92A.




TOC

AutoLearn

Type: ProgramFlowType: FallthruTrigger: PowerfailDescription: Used to perform a Learn of the Damper Position.Code: Damper LCDState = True Stop

File Explanation:

This program causes the TCX861 to perform a Learn of the damper position whenever the controller is power-up or reset.

The program is triggered by the Powerfail system variable on the TCX861.


TOC

Chapter 6

System OperationThis chapter provides operating instructions for an Infinity smoke control system. Since the equipment used in each system will be configured and programmed differently, and the FSCS will be custom-made for each system, these instructions will be somewhat generic.

The topics covered in this chapter are:

• FSCS Operation

• The Weekly Self-Test

• Controller Status Indicators

• Communicating with the System


System Operation


TOC

FSCS OperationThe FSCS that was used in Chapter 5 will be used as an example FSCS in this chapter. Your FSCS will not look identical to this one, but it will The FSCS Controls

The FSCS that was used in Chapter 5 will be used as an example FSCS in this chapter. Your FSCS will not look identical to this one, but it will be capable of performing the same functions.

The MASTER KEY

The MASTER KEY is an electrical keyswitch on the FSCS panel.

• When the MASTER KEY is turned OFF, the audible alarm is enabled and the FSCS manual overrides are disabled.

• When the MASTER KEY is turned ON, the audible alarm is silenced and the FSCS manual overrides are functional.

The MASTER KEY can only be removed when it is in the OFF position. This ensures that the system is left in the normal operating mode.

Consult the local authority having jurisdiction to determine who should receive one of the MASTER KEYs.

Fan Overrides and Indicato rs

Each fan that has a capacity in excess of 2000 cfm will be provided with Override capabilities, a STATUS indicator, and a FAIL indicator on the FSCS.

Figure 6-1 shows an example of the FSCS controls for a fan.

Figure 6-1. Fan Cont ro ls

AHU-1 SUPPLY FAN


Equipment Name

Green STATUS LED

Override Switch

Amber FAIL LED


System Operation


TOC

• The green STATUS LED indicates the current status of the fan, as determined by the fan’s differential pressure sensor. If the Status LED is ON, then the fan is ON.

• The amber FAIL LED indicates that there is a problem with the equipment. Either the equipment didn’t respond in time during a smoke control situation, or it failed the weekly self-test.

• The Override switch provides for manual control of the equipment. It allows the fire fighting personnel to override the automatic smoke control (AUTO) and either force the fan ON or OFF. This switch is functional only after the Master Key has been turned ON. This switch has the highest control priority in the system.

Damper Overrides and Indicato rs

Each damper will be provided with Override capabilities, an OPEN indicator, a CLOSED indicator, and a FAIL indicator on the FSCS. VAV terminals that serve a particular area or zone may be grouped together and all use the same set of indicators and the same override switch.

Figure 6-2 shows an example of the FSCS controls for a damper.

Figure 6-2. Damper Controls

• The green OPEN LED indicates if the damper is open, as determined by one of the end-limit switches on the damper.

• The yellow CLOSED LED indicates if the damper is closed, as determined by the other end-limit switch on the damper.

• The amber Fail LED indicates that there is a problem with the equipment. Either the equipment didn’t respond in time during a smoke control situation, or it failed the weekly self-test.

• The Override switch provides for manual control of the equipment. It allows the fire fighting personnel to override the automatic smoke control (AUTO) and either force the damper OPEN or CLOSED. This switch is functional only after the Master Key has been turned ON. This switch has the highest control priority in the system.

AHU-1 OA DAMPER

OPEN FAILAUTO

Equipment Name

Green OPEN LED

Override Switch

Yellow CLOSED LEDCLOSEDCLOSEDOPEN

Amber FAIL LED


System Operation


TOC

Zone Alarm Indicators

Each smoke control zone will have an ALARM indicator associated with it. You may also want to have an override switch for each zone.

Figure 6-3 shows an example of the FSCS controls for each zone.

Figure 6-3. Zone Controls

• The red ALARM LED indicates that an alarm has been reported by the Fire Panel.

• The Override switch provides a manual override for the entire zone. It allows the fire fighting personnel to override the automatic smoke control (AUTO) and either force the zone to be PRESSurized or to be EXHAUSTed. This switch is functional only after the Master Key has been turned ON. This switch will not override any of the individual equipment overrides.

Controller Status Indicators

Each Infinet controller will have a FAULT indicator. Controllers that have on-board HOA switches, such as the SCX920S, will also have an OVERRIDE indicator.

Figure 6-4 shows an example of the controller status indicators.

Figure 6-4. Controller Status Indicato rs

• The amber FAULT LED indicates that the CX9200 has lost communications with the Infinet controller.

ZONE 1

SMOKE ALARMAUTO

Zone Name

Red ALARM LED

Override Switch

EXHAUSTPRESS

AHU-1 CONTROLLERController Name

Areas Served

Amber FAULT LEDOVERRIDEFAULT

FLOOR 1Amber OVERRIDE LED


System Operation


TOC

• The amber OVERRIDE LED indicates that one of the Infinet controller’s on-board HOA override switches is not in the AUTO position.

Other FSCS Controls

• The FSCS has a CLEAR FAULTS momentary pushbutton. When the MASTER KEY is ON, this pushbutton will clear all of the FAIL or FAULT indicators on the FSCS. CLEAR FAULTS is primarily used to clear any weekly self-test failures.

• The FSCS has a LAMP TEST momentary pushbutton. This pushbutton is used to test all of the status indicators on the FSCS by turning them on for approximately 3 seconds. The status indicators will return to their previous state.

The FSCS Operatin g Instructio ns Sheet

The FSCS Operating Instructions Sheet on the following page is a summary of the indicators and controls on the FSCS. It should be removed from this manual, framed, and mounted adjacent to the FSCS.


FIREFIGHTER’S SMOKE CONTROL STATIONOPERATING INSTRUCTIONS

For Use by Authorized Personnel Only

LED INDICATORS:

RED - ALARM has been received for the ZoneAMBER - Equipment FAILURE

- Controller communications FAULT or OVERRIDEGREEN - FAN is ON

- DAMPER is OPENYELLOW - DAMPER is CLOSED

Press the LAMP TEST button to test all Indicators. Replace faulty Indicators.

Press the CLEAR FAULTS button to clear Equipment or Controller faults.The MASTER KEY must be ON in order to clear the faults.

THE MASTER KEY:

OFF - DISABLE Override Switches, ENABLE Audible AlarmON - ENABLE Override Switches, DISABLE Audible Alarm

All Override Switches should be in the AUTO position before turningthe MASTER KEY ON.

OVERRIDE SWITCHES:

AUTO - Equipment or Zone is under Automatic control

ON - Force the Fan to turn ONOFF - Force the Fan to turn OFF

OPEN - Force the Damper to OPENCLOSE - Force the Damper to CLOSE

PRESS - Pressurize the entire ZoneEXHAUST - Exhaust the entire Zone

In the event of trouble, contact your local service representative:Name: ___________________________________________________Address: _________________________________________________Telephone: _______________________________________________

These Instructions should be framed and placed adjacent to the FSCS for ready reference.


System Operation


TOC

The Weekly Self -TestA weekly self-test will be performed on all of the dedicated controllers in the smoke control system.

Non-dedicated controllers in the system do not get a weekly self-test. Their operation is verified by the “comfort level” in the areas that they serve.

In the example used in the previous chapter, the weekly self-test was performed when the following criteria were met:

• The system is not in a smoke control mode.

• The Weekday is Sunday through Friday.

• The Hour is between 0 and 4.

• The system has not already been self-tested this week.

Therefore, assumming the system is not in a smoke control mode, the weekly self-test will be performed just after midnight on saturday (weekday = sunday, time = 00:00).

If a piece of equipment fails the self-test, the failure will get latched, the FSCS fail indicator for that piece of equipment will turn ON, the FSCS audible annunciator will turn ON, and the Status4 (Self-Test Failure) indicator on the CX9200 will turn ON.

In order to clear the self-test failure, the MASTER KEY must be turned ON, and the CLEAR FAULTS button must be pushed.

The equipment that failed the self-test should be tested immediately to determine why it failed. Once the cause of the failure is determined, the equipment must be repaired.


System Operation


TOC

Cont roller Status Indicator sEach of the Infinity controllers in the smoke control system has a number of status indicators. The following is a brief summary of some of the more commonly used indicators. For more information, refer to the controller’s installation guide.

On the Door of the CX9200

SCAN - Flashes once for every scan of the controller.

ERROR - Turns on when a system error occurs.

Energynet - Turns on when Energynet is receiving data.

Programmable Status LEDs - There are eight programmable status LEDs on the front door of the CX9200. These LEDs are controlled through Plain-English programs by turning the system variables Status1 through Status8 OFF and ON. In our example system, the following Status LEDs were programmed:

• Status1 - Programmed to turn on when the FSCS audible annunciator is on. This occurs when there is an equipment fault, an Infinet controller is off-line, or an Infinet controller has an output overriden.

• Status2 - Programmed to turn on when there is a communications fault with the FSCS.

• Status4 - Programmed to turn on when there has been a self-test failure.

Insid e the CX9200

SCAN - Flashes once for every scan of the controller.

ERROR - Turns on when a system error occurs.

CPU - Flashes every 0.2 seconds to show that the CPU is operating properly.

Energynet LEDs- There are five LEDs inside the CX9200 that indicate the status of Energynet: RD, POL, TD, COL, TP.


System Operation


TOC

COMM Port LEDs - Each of the four COMM Ports has three indicators to show the status of the port. These indicators are useful when troubleshooting a communications problem. The COMM Port LEDs are as follows:

• TD - Turns on when the port is transmitting data.

• RD - Turns on when the port is receiving data.

• ONLINE - Turns on when the RS-232 RTS line is true, or when the RS-485 driver is enabled.

The SCX920S

The SCX920S has the following status indicators:


TD - Turns on when the Infinet port is transmitting data.

RD - Turns on when the Infinet port is receiving data.

OVERRIDE - Turns on when one of the HOA switches is not in the AUTO position.

+24V - Turns on when there is 24V DC at the expansion port.

Output Status - Each of the eight outputs has a status LED that turns on when the output is on.

The TCX840 Series

Each of the controllers in the TCX840 series has the following status indicators:


The TCX850 and TCX860 Series

Each of the controllers in the TCX850 series and the TCX860 series has the following status indicators:



System Operation


TOC

TD - Turns on when the Infinet port is transmitting data.

RD - Turns on when the Infinet port is receiving data.

The Infil ink 200 and Infil ink 210

The Infilink 200 and the Infilink 210 have the following status indicators:

Power - Indicates that power has been applied to the unit.

Port LEDs - Each Port has a RD LED and a TD LED to indicate the communications activity on that port.


System Operation


TOC

Communicating with the SystemOnce the smoke control system has been programmed and is running, you can check the status of the system, make changes to the system, or troubleshoot a problem by communicating with the system via the user port. This section provides a summary of some of the things you can do using the CX9200 user interface. For more information, refer to the following Andover Controls documentation:


The Command Window

The Command window is the top-level window in the Infinity system. From the Main Menu Bar, hit the F4 key to switch to the Command window. The cursor will now be at the R> prompt.

Most keywords can be used in the Command window. In the Plain English Language Reference manual, each keyword has a section labeled Modes Available In. If Command Line is listed, the keyword can be entered directly in the Command window.

The Command window will allow you to investigate system problems, assist in debugging programs, or allow you to save your programs for backup.

Prin ting Poin t Values

You can print the current value of any point, attribute of a point, or system variable by simply typing Print name <cr> at the R> prompt. You can also print several variables with one Print statement by seperating the variable names with commas.

For example:

R> Print AHU1.OVRRAHU1.OVRR = On

R> Print DateDate = April 15 1994 11:20:15


System Operation


TOC

R> Print Zone1.ALM,Zone2.ALM,Zone3.ALMZone1.ALM = OffZone2.ALM = OffZone3.ALM = Off

Modifyin g Poin t Values

You can also modify the value of a point from the Command window by typing name = value <cr>.

For example:

R> MaxCtlrTime = 8

R> MaxFanTime = 40

If a program or function is setting the value of the point, the value will get changed back by the program or function. See Disabling and Enabling Points or Files for information on how to override the program control.

Enablin g and Disab lin g Poin ts and Files

If you want to halt the execution of a program for debugging purposes, you can type Disable filename <cr> in the Command window. In order to re-start the program, type Enable filename <cr>.

For example:

R> Disable HornControl

R> Enable HornControl

If you want to prevent a program from updating a point value so you can modify the point, or you want to modify the value of an input or output point, you can type Disable name <cr> in the Command window. Type Enable name <cr> if you want the points to back under system control. This is very useful if you are debugging or testing a program and want to see how the program reacts to the points that are used in it.

For example:

R> Disable Zone4.PRS

R> Enable Zone4.PRS


System Operation


TOC

Prin ting or Modifying with Infin et Controllers

If you want to print, modify, enable or disable an Infinet controller point, you must tell the system the path name to the Infinet controller. There are two different methods for doing this. The first method is to type in the path name then the point name direcly in the CX9200 Command window.

For example:

R> Print AHU2 SfanINFINITY1 AHU2 Sfan = On

R> FLR3TCX DefaultDmprPosn = OFF

R> Disable AHU1 AHU_Control

The other method is to Connect to the Infinet controller. Once connected to the Infinet controller, all commands entered through the Command window are now directed towards the Infinet controller.

You connect to the Infinet Controller by selecting CONNECT from the Main Menu Bar. The system will then prompt you for the controller name that you wish to connect to. Once connected, the current path will be displayed at the top of the Command window.

Savin g and Loadin g

You can save and load any objects in the system. You will need a computer connected to the user port that is running a communications package that will capture the data coming from the CX9200, as well as load it back.

For example, if you wanted to save all of the files and points in your system you would type the following in the CX9200 Command window:

R> Save Site

The system would then prompt you to hit any key when ready. At this point you should set up your computer to capture the data into a file, then hit any key. The Infinity system will then transmit all of the programs, files, and other information that is contained in all of the controllers in the system.


System Operation


TOC

When the system has completed transmitting the data, instruct your communications software to turn off the capture function and close the file. You now have a backup of your Infinity system.

If there is ever a problem with your system, and you need to reload the programs, type in the following in the CX9200 Command window:

R> Load-o-m

The system will then wait for you to transmit the file that you had previously saved. At this point you should instruct your communications software to transmit the file. When the entire file has been loaded in, the system should be functional again. If you defined your programs as Autostart, they will start automatically.


System Operation


TOC

The View Pulldown Menu

The VIEW pulldown menu on the Main Menu Bar allows you to look at various aspects of the Infinity system.

Figure 6-5 shows the VIEW pulldown menu on the Main Menu Bar.

Figure 6-5. The VIEW Pulldown Menu

The following is a brief explanation of the VIEW pulldown menu selections.

• View Messages - Used to view the messages in the Message window. In the programming examples in the previous chapter, some system status messages were printed to the Message window, such as:

— The Date and Time the system is initialized

— The Date and Time when a weekly self test is performed

• View Points - Prints out the name, value, and state of all of the points in the controller that you are currently connected to.

• View Inputs - Prints out the name, value, and state of all of the Input points in the controller that you are currently connected to.



R>

View

InputsOutputsNumericsStringsSystem VariablesDate TimesFilesProgramsInfinet Controllers

PointsMessages

ControllersDisabled PointsDisabled System VariablesDisabled Files


System Operation


TOC

• View Outputs - Prints out the name, value, and state of all of the Out-put points in the controller that you are currently connected to.

• View Numerics - Prints out the name, value, and state of all of the Numeric points in the controller that you are currently connected to.

• View Strings - Prints out the name, value, and state of all of the Strings in the controller that you are currently connected to.

• View System Variables - Prints out the name, value, and state of all of the System Variables in the controller that you are currently con-nected to.

• View Date Times - Prints out the name, value, and state of all of the DateTime points in the controller that you are currently connected to.

• View Files - Prints out the name, description, type, and state of all of the Files in the controller that you are currently connected to.

• View Programs - Prints out the name, the current line, the length of time the program has been on this line, and state of all of the Programs in the controller that you are currently connected to.

• View Infinet Controllers - Prints out the name, port, model number, serial number, ID and status of all of the Infinet controllers that are connected to the CX9200.

• View Controllers - Prints out the name, model number, ID and status of all of the Energynet controllers on the network.

• View Disabled Points - Prints out a list of all of the Points that are currently disabled in the controller that you are connected to.

• View Disabled System Variables - Prints out a list of all of the System Variables that are currently disabled in the controller that you are connected to.

• View Disabled Files - Prints out a list of all of the Files that are cur-rently disabled in the controller that you are connected to.


TOC

Appendix A

Fire Panel Event TablesThis appendix lists the Event tables for the Fire Panels. In the left column is the CX9200 Numeric Xdriver Point value, and in the right column is the Fire Panel Event that corresponds to that value.

Refer to the Fire Panel manufacturer’s documentation for an explanation of the Events.

Table A-1 lists the Event values for a Simplex Fire Panel.

Table A-2 lists the Event values for an Edwards Systems Technology Fire Panel


Fire Panel Event Tables

A-2 Infinity Smoke Control Guide

TOC

Table A-1. Simplex Fire Panel Event Table

CX9200 Numeric Xdriver Value

Model 4020 Fire Panel Event

NotSet None - Initial CX Value

1 FIRE ALARM STATE - NORMAL

2 FIRE ALARM STATE - ABNORMAL

3 PRIORITY 2 STATE - NORMAL

4 PRIORITY 2 STATE - ABNORMAL

5 TROUBLE STATE - NORMAL

6 TROUBLE STATE - ABNORMAL

7 SUPERVISORY STATE - NORMAL

8 SUPERVISORY STATE - ABNORMAL

9 UTILITY MONITOR STATE - NORMAL

10 UTILITY MONITOR STATE - ABNORMAL

11 CONTROL STATE - NORMAL

12 CONTROL STATE - ABNORMAL

20 UNKNOWN STATE RECEIVED

21 UNKNOWN VALUE RECEIVED

Table A-2. EST Fire Panel Event Table


Model IRC-3 Fire Panel Event

NotSet None - Initial CX Value

1 FIRE ALARM

2 SECURITY ALARM

3 SUPERVISORY SHORT

4 SUPERVISORY OPEN

5 SUPERVISORY FAULT

6 EVENT

7 SENSOR ALERT

8 VERIFICATION


Fire Panel Event Tables

Andover Controls Corporation A-3

TOC

9 WATCHDOG FAULT

10 FIRE ALARM RESTORED

11 SECURITY RESTORED

12 SUPERVISED SHORT RESTORED

13 SUPERVISED OPEN RESTORED

14 SUPERVISED FAULT RESTORED

15 EVENT RESTORED

16 SENSOR ALERT RESTORED

17 UNKNOWN MESSAGE

Table A-2. EST Fire Panel Event Table


Model IRC-3 Fire Panel Event


TOC

Appendix B

Point s for Systemin This M anual

This appendix lists all of the points that were used in the example system that is described in Chapter 5. There is a separate Table for each controller. These Tables do not include system variables.


Example System Points

B-2 Infinity Smoke Control Guide

TOC

Table B-1. CX9200 Points


AH1EADmp.Cls Numeric AHU1 Exhaust Air Damper “CLOSED” LED on FSCS

AH1EADmp.Fail Numeric AHU1 Exhaust Air Damper “FAIL” LED on FSCS

AH1EADmp.Opn Numeric AHU1 Exhaust Air Damper “OPEN” LED on FSCS

AH1EADmp.OVR.Cls Numeric AHU1 Exhaust Air Damper “CLOSE” Override Switch on FSCS

AH1EADmp.OVR.Opn Numeric AHU1 Exhaust Air Damper “OPEN” Override Switch on FSCS

AH1OADmp.Cls Numeric AHU1 Outside Air Damper “CLOSED” LED on FSCS

AH1OADmp.Fail Numeric AHU1 Outside Air Damper “FAIL” LED on FSCS

AH1OADmp.Opn Numeric AHU1 Outside Air Damper “OPEN” LED on FSCS

AH1OADmp.OVR.Cls Numeric AHU1 Outside Air Damper “CLOSE” Override Switch on FSCS

AH1OADmp.OVR.Opn Numeric AHU1 Outside Air Damper “OPEN” Override Switch on FSCS

AH1RADmp.Cls Numeric AHU1 Return Air Damper “CLOSED” LED on FSCS

AH1RADmp.Fail Numeric AHU1 Return Air Damper “FAIL” LED on FSCS

AH1RADmp.Opn Numeric AHU1 Return Air Damper “OPEN” LED on FSCS

AH1RADmp.OVR.Cls Numeric AHU1 Return Air Damper “CLOSE” Override Switch on FSCS

AH1RADmp.OVR.Opn Numeric AHU1 Return Air Damper “OPEN” Override Switch on FSCS

AH1Rfan.Fail Numeric AHU1 Return Fan “FAIL” LED on FSCS

AH1Rfan.On Numeric AHU1 Return Fan “STATUS” LED on FSCS

AH1Rfan.OVR.Off Numeric AHU1 Return Fan “OFF” Override Switch on FSCS

AH1Rfan.OVR.On Numeric AHU1 Return Fan “ON” Override Switch on FSCS

AH1Sfan.Fail Numeric AHU1 Supply Fan “FAIL” LED on FSCS

AH1Sfan.On Numeric AHU1 Supply Fan “STATUS” LED on FSCS

AH1Sfan.OVR.Off Numeric AHU1 Supply Fan “OFF” Override Switch on FSCS

AH1Sfan.OVR.On Numeric AHU1 Supply Fan “ON” Override Switch on FSCS

AH2EADmp.Cls Numeric AHU2 Exhaust Air Damper “CLOSED” LED on FSCS

AH2EADmp.Fail Numeric AHU2 Exhaust Air Damper “FAIL” LED on FSCS

AH2EADmp.Opn Numeric AHU2 Exhaust Air Damper “OPEN” LED on FSCS

AH2EADmp.OVR.Cls Numeric AHU2 Exhaust Air Damper “CLOSE” Override Switch on FSCS

AH2EADmp.OVR.Opn Numeric AHU2 Exhaust Air Damper “OPEN” Override Switch on FSCS

AH2OADmp.Cls Numeric AHU2 Outside Air Damper “CLOSED” LED on FSCS

AH2OADmp.Fail Numeric AHU2 Outside Air Damper “FAIL” LED on FSCS



Andover Controls Corporation B-3

TOC

AH2OADmp.Opn Numeric AHU2 Outside Air Damper “OPEN” LED on FSCS

AH2OADmp.OVR.Cls Numeric AHU2 Outside Air Damper “CLOSE” Override Switch on FSCS

AH2OADmp.OVR.Opn Numeric AHU2 Outside Air Damper “OPEN” Override Switch on FSCS

AH2RADmp.Cls Numeric AHU2 Return Air Damper “CLOSED” LED on FSCS

AH2RADmp.Fail Numeric AHU2 Return Air Damper “FAIL” LED on FSCS

AH2RADmp.Opn Numeric AHU2 Return Air Damper “OPEN” LED on FSCS

AH2RADmp.OVR.Cls Numeric AHU2 Return Air Damper “CLOSE” Override Switch on FSCS

AH2RADmp.OVR.Opn Numeric AHU2 Return Air Damper “OPEN” Override Switch on FSCS

AH2Rfan.Fail Numeric AHU2 Return Fan “FAIL” LED on FSCS

AH2Rfan.On Numeric AHU2 Return Fan “STATUS” LED on FSCS

AH2Rfan.OVR.Off Numeric AHU2 Return Fan “OFF” Override Switch on FSCS

AH2Rfan.OVR.On Numeric AHU2 Return Fan “ON” Override Switch on FSCS









AH3Sfan.ST.Fail Numeric AHU3 Self-Test Fail Flag

AHU1.Fail Numeric AHU1 Controller “FAULT” LED on FSCS

AHU1.OVRR Numeric AHU1 Controller “OVERRIDE” LED on FSCS





Fault.Clear Numeric “CLEAR FAULTS” Pushbutton Input on FSCS

FIRST.SMK Numeric A Flag Indicating that the System has Already Responded to the First Alarm

FL2RADmp.Cls Numeric Floor2 Return Air Smoke Damper “CLOSED” LED on FSCS

FL2RADmp.Fail Numeric Floor2 Return Air Smoke Damper “FAIL” LED on FSCS

FL2RADmp.Opn Numeric Floor2 Return Air Smoke Damper “OPEN” LED on FSCS






TOC

FL2RADmp.OVR.Cls Numeric Floor2 Return Air Smoke Damper “CLOSE” Override Switch on FSCS

FL2RADmp.OVR.Opn Numeric Floor2 Return Air Smoke Damper “OPEN” Override Switch on FSCS

FL2RADmp.ST.Fail Numeric Floor2 Return Air Smoke Damper Self-Test Fail Flag

FL2SADmp.Cls Numeric Floor2 Supply Air Smoke Damper “CLOSED” LED on FSCS

FL2SADmp.Fail Numeric Floor2 Supply Air Smoke Damper “FAIL” LED on FSCS

FL2SADmp.Opn Numeric Floor2 Supply Air Smoke Damper “OPEN” LED on FSCS

FL2SADmp.OVR.Cls Numeric Floor2 Supply Air Smoke Damper “CLOSE” Override Switch on FSCS

FL2SADmp.OVR.Opn Numeric Floor2 Supply Air Smoke Damper “OPEN” Override Switch on FSCS

FL2SADmp.ST.Fail Numeric Floor2 Supply Air Smoke Damper Self-Test Fail Flag

FL2VAV.Cls Numeric Floor2 VAV Damper “CLOSED” LED on FSCS

FL2VAV.Fail Numeric Floor2 VAV Damper “FAIL” LED on FSCS

FL2VAV.Opn Numeric Floor2 VAV Damper “OPEN” LED on FSCS

FL2VAV.OVR.Cls Numeric Floor2 VAV Damper “CLOSE” Override Switch on FSCS

FL2VAV.OVR.Opn Numeric Floor2 VAV Damper “OPEN” Override Switch on FSCS



















TOC






















FLR2TCX.Fail Numeric Floor2 TCX Controller “FAULT” LED on FSCS

FLR2TCX.OVRR Numeric Floor2 TCX Controller “OVERRIDE” LED on FSCS





FSCSLinkActive Numeric Flag that tells the “Main” Program that the “FSCS_Interface” Program is Active

Horn Numeric Audible Annunciator Output on FSCS

LampTest Numeric “LAMP TEST” Pushbutton Input on FSCS

Main.Key Numeric “MASTER KEY” Keyswitch Input on FSCS






TOC

MaxCtlrTime Numeric Maximum Time that a Controller can be OFFLINE Before a Fault is Generated

MaxDamperTime Numeric Maximum Time for a Damper to Reach it’s Desired Position

MaxFanTime Numeric Maximum Time for a Fan to Reach it’s Desired State

SelfTested Numeric Flag that is Turned ON After the System has Completed it’s Weekly Self-Test

SMKDMPRS.Fail Numeric Smoke Damper Controller “FAULT” LED on FSCS

SMKDMPRS.OVRR Numeric Smoke Damper Controller “OVERRIDE” LED on FSCS

SMOKE.ALM Numeric Flag that is Turned ON when ANY of the Zones are in Alarm

SpareLamp Numeric Spare Outputs on FSCS

SpareSwitch Numeric Spare Inputs on FSCS

STRWL.ALM Numeric Stairwell “ALARM” LED on FSCS

STRWL.CON Numeric Stairwell Zoned Wiring Alarm Input on FSCS

STRWL.EST Numeric Stairwell Xdriver Alarm Input from the Fire Panel

STRWL.PRS Numeric Stairwell “PRESSURIZE” Override Switch on FSCS

STRWL.SMK Numeric Stairwell Smoke Control Sequence is Active

Zone1.ALM Numeric Zone1 “ALARM” LED on FSCS

Zone1.CON Numeric Zone1 Zoned Wiring Alarm Input on FSCS

Zone1.EST Numeric Zone1 Xdriver Alarm Input from the Fire Panel

Zone1.EXH Numeric Zone1 “EXHAUST” Override Switch on FSCS

Zone1.PRS Numeric Zone1 “PRESSURIZE” Override Switch on FSCS

Zone1.SMK Numeric Zone1 Smoke Control Sequence is Active





















TOC




CtlrTimer DateTime Infinet Controller OFFLINE Timer Array

PlantTimer DateTime Fan and Damper Proof Sensor Feedback Timer Array

InBuffer String Input String that is Read from the FSCS that Indicates the Position of all the Switches

LampWriteString String Output String that is Sent to the FSCS in order to set all of the LEDs






TOC

Table B-2. SCX920S SMKDMPRS Points


Fl2.SASDmp.Opn Input 1Digital

Floor2 Supply Air Smoke Damper OPEN Proof Sensor

Fl2.SASDmp.Cls Input 2Digital

Floor2 Supply Air Smoke Damper CLOSED Proof Sensor

Fl2.RASDmp.Opn Input 3Digital

Floor2 Return Air Smoke Damper OPEN Proof Sensor

Fl2.RASDmp.Cls Input 4Digital

Floor2 Return Air Smoke Damper CLOSED Proof Sensor

















Fl2.SASDmp Output 1Digital

Floor2 Supply Air Smoke Damper Control

Fl2.RASDmp Output 2Digital

Floor2 Return Air Smoke Damper Control









DefaultDmprPosn Numeric Damper Position when NOT Performing Smoke Control

OverrideOn Numeric Flag that Indicates that an Output is Overridden at the Controller




TOC

Table B-3. SCX920S AHU1 or AHU2 Points


SfanSt Input 1Digital

Supply Fan Differential Pressure Proof Sensor

RfanSt Input 2Digital

Return Fan Differential Pressure Proof Sensor

OADmp.Opn Input 3Digital

Outside Air Damper OPEN Proof Sensor

OADmp.Cls Input 4Digital

Outside Air Damper CLOSED Proof Sensor

EADmp.Opn Input 5Digital

Exhaust Air Damper OPEN Proof Sensor

EADmp.Cls Input 6Digital

Exhaust Air Damper CLOSED Proof Sensor

RADmp.Opn Input 7Digital

Return Air Damper OPEN Proof Sensor

RADmp.Cls Input 8Digital

Return Air Damper CLOSED Proof Sensor

Sfan Output 1Digital

Supply Fan Control

Rfan Output 2Digital

Return Fan Control

OADmp Output 3TriState

Outside Air Damper Control

EADmp Output 5TriState

Exhaust Air Damper Control

RADmp Output 7TriState

Return Air Damper Control

Default.Rfan Numeric Return Fan State when NOT Performing Smoke Control

Default.Sfan Numeric Supply Fan State when NOT Performing Smoke Control

DefaultDmpr.EA Numeric Exhaust Air Damper Position when NOT Performing Smoke Control

DefaultDmpr.OA Numeric Outside Air Damper Position when NOT Performing Smoke Control

DefaultDmpr.RA Numeric Return Air Damper Position when NOT Performing Smoke Control

OverrideOn Numeric Flag that Indicates that an Output is Overridden at the Controller




TOC

Table B-4. TCX840 FLR2TCX or TCX851 FLR3TCX Poin ts


VAVDmp.Opn Input 1Digital

VAV Damper OPEN Proof Sensor

VAVDmp.Cls Input 2Digital

VAV Damper CLOSED Proof Sensor

VAVDmp Output 4TriState

VAV Damper Control

DefaultDmprPosn Numeric VAV Damper Position when NOT Performing Smoke Control

Table B-5. TCX861 FLR4TCX Points


Damper Output 6Voltage

Motorized VAV Damper Control

Damper.Opn Numeric VAV Damper OPEN Indicator based on Hall-Effect Sensor Feedback

Damper.Cls Numeric VAV Damper CLOSED Indicator based on Hall-Effect Sensor Feedback

DamperPosition Numeric VAV Damper Position that is Equal to Damper Overridevalue

DefaultDmprPosn Numeric VAV Damper Position when NOT Performing Smoke Control

PowerFail SystemVariable

Power Indicator Flag used to Trigger the AutoLearn Program

Table B-6. TCX853 AHU3 Points


SfanSt Input 1Digital

Supply Fan Differential Pressure Proof Sensor

Sfan Output 1Digital

Supply Fan Control

DefaultFanPosn Numeric Supply Fan State when NOT Performing Smoke Control


TOC

Appendix C

FSCS ProtocolThis appendix describes the communications protocol for the FSCS. The FSCS uses a Q-Card processor board with the Andover Data Interface firmware.

General Infor mation

The CX9200 communicates with the Q-Card via an RS-232 port. The Andover Data Interface firmware allows the CX9200 to control the state of the LEDs and read the state of the switches on the FSCS.

You will receive information regarding the LED numbers and switch numbers from the FSCS manufacturer.

Refer to Chapter 3 for information regarding how to set the Q-Card baud rate on the and how to connect the field wiring to the FSCS.

Commun icatio ns Format

The format for the ASCII serial data is as follows:

8 Data bits1 Start bit1 Stop bitNo Parity

All commands to the FSCS and responses from the FSCS begin with a left parenthesis and end with a right parenthesis. If the data coming into the FSCS does not meet these requirements, it will be ignored. When sending a command to the FSCS, all carriage returns, line feeds, and space characters are automatically filtered out of the data stream without affecting the data.


FSCS Protocol

C-2 Infinity Smoke Control Guide

TOC

Active Sensing Message

The FSCS will transmit a ! character every time it receives a carriage return. This allows the CX9200 to supervise the RS-232 connection and verify that it is communicating properly with the FSCS.


FSCS Protocol

Andover Controls Corporation C-3

TOC

LED Command s

The LEDs can be controlled individually or using a block formatted command.

In order to ensure that LEDs are updated after a power failure or after an interruption of the communications link, the LEDs should be refreshed frequently by the CX9200. Therefore, Andover Controls recommends using the block formatted command and updating all of the LEDs on a regular basis.

The Block LE D Command

The block LED command consists of a left parenthesis, followed by up to 240 status characters, and ending with a right parenthesis. The first status character controls LED 0, the second controls LED 1, and so on.

The status characters are as follows:

X Turns the LED ONZ Turns the LED OFFF Causes the LED to FLASH

For example, the following command would cause LED 0 and LED 3 to turn ON, LED 1 and LED 2 to turn OFF, and LED 4 to FLASH:

(XZZXF)

Individual LED Commands

The LEDs can also be controlled individually. The led command consists of a left parenthesis, followed by the LED number, followed by the status character, and ending with the right parenthesis.

The LED number can be from one to three digits and any leading zeroes will be ignored. The status characters are the same ones that are used with the block LED command: X -> ON, Z -> OFF, F -> FLASH .

For example:

(1X) Turns ON LED 1(7Z) Turns OFF LED 7(3F) FLASHES LED 3(03F) FLASHES LED 3(003F) FLASHES LED 3


FSCS Protocol


TOC

Utility L ED Commands

The following LED commands are also available:

(CLR) Turns ALL of the FSCS LEDs OFF.

(TST) Turns ALL of the FSCS LEDs ON forapproximately 3 seconds, then resets them all totheir previous state.

LED Status Request Command

The CX9200 can request the status of any LED using the following command:

($nnn) Where nnn is the LED number

The FSCS would respond with one of the three following messages:

(Xnnn) LED nnn is ON(Znnn) LED nnn is OFF(Fnnn) LED nnn is FLASHING


FSCS Protocol

Andover Controls Corporation C-5

TOC

Switch Commands

The FSCS can be configured to transmit a message any time a switch changes state, or it can be configured to transmit the state of the switches only when it is polled. The switches can be polled individually or in a block format.

In order to cut down on the communications overhead, Andover Controls suggests suppressing the switch actuation messages and polling the switches in a block format.

Suppressing the Switch Actuation Messages

The following commands determine whether the switch states are to be polled, or change of state messages are to be generated:

(SPR) Commands the FSCS to suppress all switchactuation messages. The switches must be polled.

(SAM) Commands the FSCS to enable all switch actuationmessages. Therefore, pressing a switch causes animmediate tramsmisssion of it’s state.

When the switch actuation messages have been suppressed, the FSCS will latch the state of the switch whenever it changes state and unlatch the state of the switch when it is polled. This allows a momentary switch to be read without the switch having to remain actuated for a complete polling cycle.

When the switch actuation messages have been enabled, a switch changing state will cause one of the two followings messages to be sent:

(Annn) Switch nnn is Activated (ON)(Rnnn) Switch nnn is Released (OFF)

The switch states may be polled even though the switch actuation messages have been enabled. When the switch actuation messages have been enabled, and the switch is polled, the switch states are not latched and the FSCS will report an instantaneous value for the switch.


FSCS Protocol


TOC

The Block S wit ch Command

The CX9200 can request that all 80 switch states for a particular I/O card be reported using the following command:

(?SBKx) Where x is the number of the I/O card to be polled.For the first 80 switches, x = 1, for the second 80switches, x = 2, and so on.

The response from the FSCS would contain a 3 digit address for the first switch in the block, followed by 80 status characters. A typical string from the FSCS would be as follows:

(yyyAARRRA.....AR)

Where:

yyy Equals the first switch number in this block. For the first I/O card, yyy = 000, for the second I/Ocard, yyy = 080, and so on, in increments of 80.

A The Switch is Activated (ON)R The Switch is Released (OFF)

The first character represents switch yyy, the second character represents switch yyy + 1, and so on.

Indiv idual Switc h Status Request Command

The CX9200 can request the status of any switch using the following command:

(?nnn) Where nnn is the Switch number

The FSCS would respond with one of the two following messages:

(Annn) Switch nnn is Activated (ON)(Rnnn) Switch nnn is Released (OFF)


TOC

Appendix D

Manuals fo r the SmokeCont rol System

This appendix gives a complete list of the manuals you may require to install and program your smoke control system.


Smoke Control Manuals

D-2 Infinity Smoke Control Guide

TOC

Manual s

For information on how to install and program the controllers presented in this manual, you may also want to refer to the manuals listed in the table below.

Table D-1. Smoke Control Manuals and Their Versions

Book No. Book Title Version

30-3001-347 Infinity CX 9200 Installation Guide C

30-3001-170 SCX 920 Installation Guide C

30-3001-493 TCX 840 Family Installation Guide B

30-3001-173 TCX 850 Installation Guide D

30-3001-390 TCX 860 Installation Guide B

30-3001-497 TCX 865 Family Installation Guide A

30-3001-393 EnergyLink 2500 Installation Guide C

30-3001-394 InfiLink 210 Installation Guide C

30-3001-178 InfiLink 200 Installation Guide C

30-3001-196 DCX 250 Installation Guide D

30-3001-404 Infinity Modem Installation Guide and Command Reference C

30-3001-166 Infinity CX Programmer’s Guide 1.4

30-3001-446 Infinity Smoke Control Guide A


infinity smoke control guide - fire alarm resources

Documents