quick start manual zeus 5.0

Zeus 5.0 Quick Start Manual Siemens Building TechnologiesP/N 315-033875-11 Fire Safety

Quick-Start Manual for Zeus 5 .0 Programming Tool


Copyright20012007, Siemens Building Technologies, Inc.

FireFinder XLS is a trademark of Siemens Building Technologies, Inc.Microsoft Windows, Windows Explorer and Internet Explorer are trademarks of Microsoft Corporation.Install Shield is a trademark of Sterling Technologies, Inc. and Installation Software Technologies, Inc.


TABLE OF CONTENTS

Chapter Title Page

1 INTRODUCTION AND OVERVIEW .......................................................................................1What This Manual Covers .................................................................................................1Getting Additional Help....................................................................................................1What is Zeus?...................................................................................................................1Definitions of Important Terms.........................................................................................2Conventions Used in this Manual......................................................................................2

2 INSTALLING AND RUNNING ZEUS......................................................................................3Installing Zeus ................................................................................................................. 3Starting a Zeus Session ....................................................................................................3Ending a Zeus Session...................................................................................................... 3

3 STEP-BY-STEP EXAMPLE....................................................................................................4PHASE 1: Fire-Only System for Acme Manufacturing Co. ...................................................4

Part 1-1: Start a New Zeus Project ...................................................................... 5Part 1-2: Set Up Hardware in the Physical View ...................................................6Part 1-3: Set Up Groups in the Geographic View.................................................11Part 1-4: Assign Elements to Logic Functions .....................................................13Part 1-5: Check and Compile the System............................................................16

PHASE 2: Add Voice to Fire System for Acme Manufacturing Co. ......................................17Part 2-1: Add Voice Components (Physical View) ...............................................17Part 2-2: Group Voice Elements (Geographic View)............................................21Part 2-3: Set Up Voice Controls (Control View) ...................................................22Part 2-4: Program Voice Functions (Function View)............................................24Part 2-5: Check and Compile the Project ............................................................24

PHASE 2a: Using Bulk Amplification for Voice ..................................................................25PHASE 3: Adding Fan Control..........................................................................................27PHASE 4: Networking Multiple Systems ...........................................................................29

Part 4-1: Add Fire Finders XLS Node (Physical View)...........................................29Part 4-2: Add Finance Building FireFinder XLS Node ...........................................30Part 4-3: Setup Groups in Geographic View........................................................33Part 4-4: Setup Logic Functions for Node 2 ........................................................34Part 4-5: Setup Inter-panel Logic Functions........................................................36Part 4-6: Adding Other Siemens Systems ...........................................................38

PHASE 5: Connecting FireFinder XLS to a Central or Remote Station .................................39PHASE 6: Global PMI.......................................................................................................41

4 USER INTERFACE .............................................................................................................46Main Screen ...................................................................................................................46View Windows................................................................................................................47Title Bar ..........................................................................................................................48Menu Bar .......................................................................................................................48Toolbar ..........................................................................................................................48Status Bar.......................................................................................................................48Help Menu Commands....................................................................................................49Help Screen Tabs ............................................................................................................49Help Window Controls ....................................................................................................51File Menu Commands .....................................................................................................52Edit Menu Commands.....................................................................................................53View Menu Commands ...................................................................................................54Insert Menu Commands ..................................................................................................55Build Menu Commands ...................................................................................................55Tools Menu Commands...................................................................................................56


5 CONCEPTS AND OPERATIONS....................................................................................... 57Comparison of Zeus and Microsoft Windows Explorer ...................................................57Elements, Links and Sources........................................................................................ 57FireFinder XLS Communications Protocols.................................................................... 58Understanding the View Windows ............................................................................... 58

LIST OF NUMBERED FIGURES

Figure Title Page

2-1 Zeus Shortcut (Desktop Icon) 32-2 User Login Dialog 32-3 Zeus Main Screen 3

3-1 ACME Manufacturing Co. Layout 4

4-1 Zeus Main Screen 434-2 Tree View Example 444-3 Multiple View Windows 444-4 Title Bar 454-5 Menu Bar 454-6 Toolbar Buttons 454-7 Status Bar 454-8 Help Menu and Sub-menu 464-9 Help Tabs 464-10 Help Window Controls 474-11 File and Edit Menus 484-12 View Menu and Sub-menus 494-13 Examples of Insert Menu Selections 504-14 Build Menu and Sub-menu 504-15 Tools Menu and Sub-menus 51

5-1 Link/Source Example 575-2 Detail View Tabs 585-3 Function View Example 59

Zeus 5.0 Quick-Start Manual 1 Siemens Building TechnologiesP/N 315-033875-11 Fire Safety

CHAPTER 1 INTRODUCTION AND OVERVIEW

What This Manual Covers

This manual provides basic operating information for the Zeus software package, which is used to program SiemensFireFinder XLSfire detection systems. The manual supplements the comprehensive instructions found in the ZeusInstallation Manual (Siemens P/N 315-034686) and the online Help feature of the Zeus software itself.

This manual consists of the following chapters:

Chapter 1: Introduction and Overview General information about Zeus and this manualChapter 2: Installing and Running Zeus Getting in and out of ZeusChapter 3: Step-By-Step Example A short example of developing and configuring a systemChapter 4: User Interface An overview of the Zeus menus and graphic interfaceChapter 5: Concepts and Operations Important concepts and operations for using Zeus

Getting Additional Help

The Zeus online Help feature provides more comprehensive information than this manual. See the Help Menusection of Chapter 4 for a general description of this feature. To access Help while the software is running:- Open the Help Menu and select a command such as Contents, Index or Search, or- Select a screen feature and press the F1 key, or- Click the Whats This? Button on the Toolbar, then click the screen feature you want to identify.Updated information is available through the Internet at www.sbt.siemens.com/FIS/technicalsupport/.Live support is available at 1-800-248-7976 Monday to Friday, 8 a.m. to 6 p.m. US Eastern time.For complete software installation and setup procedures, refer to the separate Zeus Installation Manual.

What is Zeus?

Zeus is a software application used to plan and configure installations of the FireFinder XLS fire detection system.With Zeus, you can: Graphically design a system configuration. View multiple system interrelationships, such as hardware or logical connectivity. Assign devices to convenient, intuitive groups by location or other criteria. Visually program system behavior. Compile and transfer the completed configuration to a FireFinder XLS control panel. Record wave-format sound files and assemble Voice files for XLS Voice systems Generate:

Reports on system configuration differences Walk test results History Log records System power and battery requirements calculations Equipment lists

Zeus features and capabilities include:

Drag and Drop Operation: Zeus provides a graphical user environment similar to that of Microsoft WindowsExplorer. You can construct and modify the system configuration simply by dragging and dropping elementsrepresenting components, hardware groups, logic functions, etc.

Multiple Views: Zeus allows you to configure and examine a systems interrelationships through a series of side-by-side display windows (Views) that give you information on distinct aspects of the system.


Definitions of Important TermsChild An element in a tree view connected to, but on a lower level than, another element. A subordinate element.

Compile Condense a Project File (.zdb) that Zeus can manipulate into a Configuration File (.hrc) that can betransferred to a FireFinder XLS panel.

Configuration The electronic represent ation of a system developed by Zeus, as saved to a compiled Configuration File(.hrc format). This is the file format stored in a FireFinder XLS panel.

Decompile Expand a compiled Configuration File (.hrc) into a Project File (.zdb) that Zeus can manipulate.

Element An item represented by an icon and label in a tree view. A Zeus element may represent a device,a logic function, a geographic grouping, etc.

Installation (noun) The physical fire system and its geographic setting.

Node A FireFinder XLS central processing unit and the devices it operates.

Parent An element in a tree view with other elements on lower levels connected to it. A superior element.

Project The electronic representation of a system developed by Zeus, stored to memory, shown on-screen orsaved to a Project File (.zdb format). This is the file format that Zeus can manipulate.

Properties Settings that accompany an element, such as the elements label, device settings, etc. Properties areadjusted by editing fields in the Detail View window.

Link An icon representing an element created in another place in the configuration.

Source An element to which links are made elsewhere in the configuration.

System A Node element and the collection of devices and their interconnections (physical, logical, etc) under it.Multiple Nodes connected together via communications links would imply multiple systems.

Transfer Copy a Configuration File (.hrc) from a host computer to a FireFinder XLS panel, or vice versa.

Views Windows displaying distinct aspects of the system. The five Views are Detail, Physical, Geographic,Control and Function.

Zone Coding An alarm method by which an event code is conveyed by pulsing the audibles such that thebeats can be counted by listeners to determine the codes digits.

Conventions Used in this Manual[Menu] > [Command] Click the menu and select the command from the resulting drop-down list.

Example: File > Open means select the Open command from the File Menu.

Underlined Text Refer to the adjoining figure used in Chapter 3 (Step by Step Example).

Ctrl+(key) Hold down Ctrl (control) on the keyboard while pressing the specified key.

Click A single click of the left-hand button on the mouse.

Double-Click Two clicks, in rapid succession, of the left-hand button on the mouse.

Right-Click A single click of the right-hand button on the mouse.

Drag and Drop Click an item, hold down the left-hand mouse button, and move the mouse to move the itemacross the screen. Release the button to put the selection in the new location.


CHAPTER 2 INSTALLING AND RUNNING ZEUS

Installing Zeus

Zeus is a Siemens-proprietary software package that requires a series of password-exchange procedures to beinstalled and activated at a site or with an authorized agent, set up and installed on individual workstations.Refer to the Zeus Installation Manual for details on these procedures.

Starting a Zeus SessionTo run Zeus after setup, simply double-click the Zeus desktop icon (Figure 2-1) and enter the appropriate username and password in the User Login Dialog (Figure 2-2). Zeus will open to its main screen (Figures 2-3, 4-1).

Ending a Zeus SessionTo exit Zeus, click File, and then Exit from the resulting drop-down menu (File > Exit). You can also click thebutton marked X in the upper right corner of the window. If the currently open file has unsaved changes, youare prompted to save the file before exiting. The time that has elapsed during your session is displayed in thelower right corner of the Zeus window.

Figure 2-1Zeus Shortcut (Desktop Icon) Figure 2-2 User Login Dialog

Figure 2-3 Zeus Main Screen (See also Figure 4-1, Chapter 4.)


CHAPTER 3 STEP-BY-STEP EXAMPLEThe fastest and easiest way to introduce you to Zeus is to show you step-by-step how to configure a simpleproject. Refer to Chapters 4 and 5 herein, and the Help feature in Zeus, for more detail about the features andoperations presented here.

NOTE: This project is a highly simplified example provided only to illustrate Zeus operations. It is notintended to represent a practical or code-compliant fire system.

Phase 1: Fire-Only System for Acme Manufacturing Co.

Figure 3-1 ACME Manufacturing Co. Layout

Functionality Required:One HFP-11 detector, one HMS-S Pull station for each room.All HFP-11 detectors use Intelligent Environmental Compensation (IEC) and Application Specific Detection (ASD).An event on first floor of the Main Building or in the Annex, at a detector or pull station, triggers the following:

- A steady audible Evacuation level alarm on that floor, accompanied by synchronized strobes.- A temporal audible Alert level alarm on the other floors of the building of incident and other buildings,

accompanied by synchronized strobes.The detectors and devices in the Annex are connected to the Main Building 1st-floor device loop.The XLS control panel, located in the Main Building Lobby, includes Function Keys (programmable buttons) for:

- Alarm testing / fire drill simulating an event on each floor of the Main building and Annex.- Recall signal of 30 pulses per minute march tone, which always sounds throughout the complex.System Status Displays with control are used to monitor and acknowledge events in the Annex and on the Main

Building 2nd floor.Alarm events activate a dialer to local authorities; trouble events activate a dialer to maintenance personnel.A single printer, located in the Main Building Lobby, is used to print out all system events.

General Approach:Although there are a number of approaches, heres how youll build this configuration in the following exercise:

1) Start a new project.2) Set up the system hardware by inserting and deleting hardware elements in the Physical View.3) Assign hardware elements to appropriate location groupings in the Geographic View.4) Set up the system behaviors by assigning devices and groups to logic elements in the Function View.5) Perform a check to find errors, and then compile the project into a configuration file that can be

transferred to the system control panel.

Note: Normally, one would begin the design process by sketching a system in terms of components, locations andlogic before programming in Zeus. For illustration purposes, we will explain the system as we build it here.


Part 1-1: Start a New Zeus Project

NOTE: Underlining refers to a figure on the rightside of the page.

1) On the Windows Desktop, double-click the ZeusShortcut.

2) In the resulting Login dialog, enter a valid username and password. Click OK.

3) Open the File Menu and start a new project: ClickFile> New.. Or click the new button on the ZeusToolbar .

4) In the New Project dialog that pops up, fill in theproject name. This example project is called Acme.As you type, notice that Acme is added to the folderaddress listed in the Location field below. Zeus addsthe extra folder to keep files for the same projecttogether. For this exercise, use the default directory:C:\Program Files\Siemens FireFinder XLS \Zeus5.0\Acme. Click OK when you are done.

5) The Zeus screen appears, with the gray Detail Viewwindow on the right, and at least one other Viewwindow on the left. (Refer to Figure 2-3.) If thePhysical View window is not displayed somewhereto the left of the Detail View, click the PhysicalView button, , on the Toolbar. For now, we wantonly the Physical and Detail Views to be displayed.If other View windows are open, close them.

6) In the Physical View, select the Project element(single-click the icon so it becomes highlighted).

7) At the top of the Detail View, click the PropertiesTab. The fields that appear are properties associatedwith the selected element in this case, identifyinginformation on the project itself. You can enter thisprojects data in these fields. If the system is not anXNET system, the XNET Networked Configurationin Project Properties must be unchecked. Click theproperty NFPA System Type. From the resultingmenu, select Local (NFPA 72A). Of particularnote, the Contact Name and Contact Phone fieldentries will be displayed in the Alarm DetailsScreen of the control panel (PMI) during an event.

8) As you construct this project, you may need to re-size the Physical View window to see all thedetails. You can quickly make the windows thesame width by clicking the Arrange button, , onthe Zeus Toolbar. You can also move the cursorover the Physical View windows right border,where it will become a double arrow. With thissymbol active, click, hold and drag to move theborder.


Part 1-2: Set Up Hardware in the Physical View

1) With the Project element selected, insert aFireFinder XLS Node under it by clicking Insert >FireFinder XLS.

2) Select the FireFinder XLS Node element in thePhysical View. Click the Properties tab in the DetailView window. Click the property field BaseLanguage Cust. Message, type Acme ManufacturingCo., and press the Enter key. This becomes theNode elements label in the Physical View, and thetitle shown on the PMI control panel during systemstartup.

3) Toward the bottom of the Detail View, set BatteryCapacity Factor to Total Amp x 4 Hours, andBattery Capacity Reserved to 25%.

4) Click the box next to the Node property FireFinderXLS Map Names. The resulting dialog allows you toselect the floor plans that can be shown on theNodes PMI (control panel), to display eventlocations. Select the three Acme example mapsalready in Zeus Acme 1st Floor, 2nd Floor, Annex and click Add to make these files available to thisNode. Close the dialog.

5) Note the properties On Site Contact Name / Phone.This information is prominently displayed on thePMI when the user requests event details.

6) Expand the Node element by clicking the smallplus sign next to it. The elements History Log andSystem Flags, which are part of the Node element,appear. Click History Log and press the F1 Key toview help topics on this important element and itsproperties. The System Flags element will beexplained when it is used a little later, in theFunction View section of this tutorial

7) Select the FireFinder XLS Node again and clickInsert > CAB-1. A CAB-1 (one-row enclosure) isinserted as a child of the Node element.

8) Lets look at correcting a mistake. The specificationcalls for using a double-row CAB-2, not a CAB-1.You can either undo the insertion operation, ordelete the element you just inserted. To undo theinsertion, you can either click Undo, , on theToolbar, press Ctrl +Z, or click Edit > Undo. Todelete the CAB-1 element, first select it. Then youcan either click Delete, , on the Toolbar, pressthe Delete key, or click Edit > Delete. Use one ofthese methods to remove the CAB-1 element.


9) Select the FireFinder XLS Node element and insert thenew CAB-2 element under it (replacing the CAB-1):Insert > CAB-2. Change the CAB-2 element in theDetail View to read 1st Flr Enclosure Lobby.

10) The system uses a PSC-12 power supply card. Fourrelays are packaged with the PSC. Two are fixed-use: they connect to the systems common alarmand trouble buses. Two others, which we will notuse here, are programmable.

Zeus has already inserted a PSC-12 under the CAB-2;click the small plus sign to the left of the CAB toshow the PSC. Click the small plus sign to the leftof the PSC to expand it. The two fixed PSC Relaysare already under the PSC. Label the PSC PowerSupply - 1st Flr CAB, and the PSC relays 1)Common Alarm - 1st Flr CAB, and 2) CommonTrouble - 1st Flr CAB. Set the property Battery Sizeto 31 AH.

11) Select the CAB-2 and insert its inner door: Insert >Inner Door. (Notice that the Insert menu haschanged with the new selection.)

12) Select the Inner Door and click Insert > PMI to adda control panel/central processor (a PMI Person-Machine Interface). Label the PMI Control Panel -Lobby. Its default HNet Address, 253, is reservedfor a Nodes PMI only.

13) The project requires five Function Key operationsfor manual system testing. On the PMI screen,these keys are listed on the Function Key Screen; auser will press these graphical buttons on thetouch screen to run and stop tests.

Right-click the PMI, and select Insert > FunctionKey from the resulting pop-up menu. A FunctionKey is inserted as a child of the PMI. Add fourmore, and label the Function Keys Test 1st Floor,Test 2nd Floor, Test Annex, Recall Signal andSTOP. You will set up the logic to program thesekeys a little later.

14) Select the PMI again. Click the box next to thePMIs PMI Event Map Name 1 property. Theresulting dialog allows you to mark the PMIsposition on one or more of the map files selectedfor this Node. For Select Bitmap, choose the Acme1st Floor map. Drag the blue dot to the desiredlocation, in this the Lobby. When a 1st-floor eventmap is displayed on the PMI, a You Are Here iconis added at this mark. Note that you can click anddrag it to adjust its position.


15) Select the 2nd Floor map for PMI Event Map 2 (youcan do this by setting Position to 2 in the dialog),and the Acme Annex map for Position 3. Do not marka position on these other two maps, since the PMIis located on the 1st Floor, Click OK when done.

16) Use these properties to set the PMIs display:Group Level Displayed to Device/Primitive toshow individual devices, Display Type to DisplayWith Control, and MORE INFO View to Map so agraphical map will be first displayed when MOREINFO is pressed.

17) The main enclosure requires a card cage intowhich circuit cards will plug. Add a five-slot CC-5card cage as a child under the CAB-2 enclosure.Change the CC-5 custom message to Fire SystemCards 1st Flr. (The Inner Door and PSC areshown collapsed for clarity. Note that they are onthe same tree branch / level as the CC-5.)

18) Select the CC-5 and insert a NIC-C (HNet) under it. TheNIC will communicate with the other enclosures inthe system. Label the NIC Network Interface Card 1st Flr. In the Detail View Properties tab, makesure CAN Bus Enabled is NOT checked. This system willuse its DACs, not NICs, to host CAN bus devices.

19) The 1st floor requires three output circuits to drive1st floor audibles, 1st floor strobes, and theseparate any-alarm default audible required byregulation. Insert a ZIC-4A Zone Indication Cardunder the CC-5. Label the ZIC-4A Notification Apps 1st Flr. Insert three Out Ckts under the ZIC. Labelthese 1st Flr Audibles, 1st Floor Strobes and 1stFlr Default Audible.

20) In the Out Ckt Detail Views, set the property ZICCircuit Usage to NACCoded for the Audibles andDefault Audible circuits, and Strobe Synch for theStrobe circuit. (You will code the audibles later.)On all Out Ckts, check the Silenceable box and setWiring Type to Class A. Set Total Current drawn to2.0 amps each. This last property allows Zeus todetermine whether there is an adequate powersupply to operate the system as designed.

21) We need another ZIC under the CC-5, this time forthe Annex. You can create this quickly by copyingand modifying the 1st Flr ZIC. Select the 1st Flr ZIC;copy it (use Edit > Copy, press click Ctrl + C, orclick ). Select the CC-5 element. Paste thecopied ZIC (Edit > Paste, Ctrl + V, or ). Deletethe Default Audible Out Ckt and change all theother labels from 1st Flr to Annex.


22) Insert a DLC (Device Loop Card) under the CC-5.Label it 1st Flr Device Loop. Select the DLC, insertan HMS-S pull station and label this 1st FlrStairwell Pull Sta.

23) Under the DLC, insert and label an HMS pull station1st Flr Stairwell Pull Sta. Then insert and label anHFP-11 detector (1st Flr Detector) and anotherHMS pull station (1st Flr Pull Sta.). Duplicatingthese two new elements will populate the deviceloop. All HFPs will use Intelligent EnvironmentalCompensation (IEC), so make sure that property ischecked on this HFP. Also, most of the detectorswill have an Application Specific Detection (ASD)setting of Office, so set that property on this HFPas well.

24) Click the HFP, hold down the Shift key, and clickthe second HMS to select both devices. Copy theseelements to the Windows Clipboard. (Use Ctrl+C,Edit > Copy, or .) Select the DLC. Click Edit >Paste Special. In the resulting dialog, set MultiplePaste to 8 and click Paste. Eight more HFP / HMSpairs are inserted under the DLC, one pair for eachroom on the Main Building 1st floor and theAnnex.

25) Select the DLC. In the Detail View Elements tab,use the table to change the elements as shown,filling in the Base Language Custom Message withthe individual Zones. Note the amount of workthat has been saved by using Paste Special togenerate and label repetitious elements.

26) You will now set up the 2nd floor enclosure simplyby copying, pasting and modifying the 1st floorenclosure. Select the 1st floor CAB-2, copy it andpaste it. A duplicate of the entire 1st floor setup isadded to the system. Move one of the CABs so thecopy (Enclosure 2) is below the original.

27) Select the copied CAB, and then click (or Edit >Find/Replace Text or Ctrl + F). In the resultingdialog (next page), enter 1st for Find What and2nd for Replace With. Click Replace All, and thenClose. Fully expand the CAB. Note that for the CABand all elements under it, 1st Flr becomes 2ndFlr. In the CAB label, change Lobby to Hallway.Modify the CAB children as follows:

28) Delete the PMI from under the Inner Door.

29) Delete the default audible Out Ckt on the first ZIC,and the entire second (Annex) ZIC.


30) Taking advantage of the similar layouts of the 1stand 2nd floors, select the DLC and useFind/Replace Text to replace all occurrences ofLobby to Office, Shipping to Test Lab, Shopto QA Room.

31) Delete the copied Annex loop devices i.e., thedevices at addresses 14 through 19.

32) Select the first HMS in the device loop (Stairwell).Click Edit > Find/Replace Tree Node (Ctrl + H). Inthe resulting dialog, select HFP for Replace With,then Replace. In the next dialog, set up the 2ndfloor Stairwell detector: Device Address 1, 2nd FlrStairwell Detector, IEC checked, ASD Applicationof Lobby. Click OK and Close, and the HMS fromthe bottom stairwell landing becomes the detectorat the top landing. The 2nd floor device loop iscomplete.

33) Select the Node element and insert two SSDs(System Status Displays). Note that Zeus appliesHNet Address 9 to the first SSD, filling the gap leftby the deleted ZIC at that address. Label the SSDs2nd Flr Display - Hallway and Annex Display -Annex Office. For PSC Power Supply Address, setthe 2nd floor SSD to 6 (the HNet address of the2nd floor CABs PSC) and the Annex SSD to 1 (the1st floor CABs PSC).

34) Again select the Node element, and insert aRemote Printer Module (RPM) that willcommunicate with a PAL-1 printer to makeprintouts of system events and histories. Label theRPM System Printer Interface. Set the propertyPSC Power Supply Address to 1, which is the HNetaddress of the PSC in Enclosure 1. The RPM andprinter will be located near this CAB, in the MainBuildings Lobby.

35) Expand the RPM and label its Parallel Port SystemPrinter 1st Flr Lobby. Set the property Print Levelto Device/Primitive so the event details will beprinted out at the individual device level, asopposed to a higher Group Level.

36) Select the Nodes PMI (under the 1st flr CABdoor). Set the property Report RPM Address to theRPMs HNet address (12), and Report RPM Port toParallel Port. Set Group Level Displayed toDevice/Primitive to match the RPM.

37) Save the project by clicking File > Save, or onthe Toolbar.


Part 1-3: Set Up Groups in the Geographic View

1) Click the Geographic View button, , to insert thatView. Keep the Physical View open.

You will now organize the devices in the PhysicalView into Groups Which are used in creatingsystem logic (Function View) and Voice controls(Control View) and determining what graphics andmessages the PMI displays during an event.

2) Select the Project element in the GeographicView, and look at its Properties Tab in the DetailView. The five Group levels (1-5) and their defaultnames (Campus, Building, Floor, Area, Zone) aredisplayed. Note that you can change the names ofthe Group levels here, to best suit your particularproject. Keep these default labels for this exampleproject.

3) Insert three Floor (Level 3) elements under theGeographic Views Project element. Label theseelements 1st Floor, 2nd Floor and Annex.

4) Under the 1st Floor, insert 7 Zones (Level 1), onefor the stairwell and each room. Label theseaccordingly: Stairwell - 1st Flr, Lobby, Hallway, etc.

5) Assign the 1st Floor devices in the Physical View totheir corresponding Groups. For example, selectthe Lobby devices, then drag and drop these ontothe Zone Lobby. Note that links of the elementsare placed under the Zone; the device icons arereplaced by light-yellow boxed arrows. Try usingthe right mouse button to make some of theassignments. When you release the button, amenu prompts you to Assign to Here, or Cancel;Move and Copy are unavailable, since assignmentis the only action possible. Click Assign to Here foreach link.

6) Add and label one more Zone under the 1st Floor:1st Flr Components. This Group will allow you towork separately with such system components asthe power supply and electronics cards. This Groupwill enable the PMI to display detailed messagesand maps when a card or module is activated or isin a trouble state.

7) To this last Zone, assign the HNet-addressableelectronic components located on the 1st Floor:PSC, PMI, cards and modules. Note that thesemodule links are white, not light yellow asbefore. This indicates that the links are used onlyto set PMI display information, and do not affectany other kind of system functionality.


8) Select a Zone on the 1st Floor, and examine itsproperties. Many of these determine whatinformation will be displayed on the PMI during anevent. On the PMIs Alarm Details Screen, theproperties Base Language Detail Message, FireService Equipment Icon Names, and Hazards /People Icon Names are shown. On the PMIs MapScreen, the Group Event Map Name graphic, andmarked position on that graphic specified by GroupLocation, is displayed.

The Zone Coding properties determine at whatGroup level and with what response an event inthis Zone will sound, when Zone Coding is used ina system. Acme will not use these.

9) Select each of the Zones under the 1st FloorGroup, and click the button on the right of theGroup Event Map Name field. In the resultingdialog, use Select Bitmap to select the 1st Floormap for each 1st Floor Zone. This time, mark eachZones position on the map by clicking in the roomthe current Group represents.

The blue dot will show up on the PMI as an alarmicon (flame) or trouble icon (lightning bolt) whenthe map is called up and displayed during anevent. You can click and drag the dot to move it.(The position of the dot on the map, in pixels, isshown in the property Group Location, which inturn can be used to adjust that position.)

Note that without closing this dialog, you canmove from Zone to Zone by clicking the treegraphic on the right side. Note also that if you clickDisplay All on the right, all the marked positions onthe Acme 1st Floor map are shown.

10) Back in the Detail View, clicking on the buttonsnext to Fire Service Equipment Icon Names andHazards / People Icon Names brings up a similardialog that allows you to select icons that will bedisplayed in the PMIs Alarm Details Screen, whichwill aid firefighters in determining resources andhazards in the affected Zone. The Hazards / Peopledialog includes a feature for generating custom 3-digit HazMat icons. You can press the F1 Key to getthe Zeus Help feature, which will provide moredetails.

11) Repeat the setup process for the 2nd floor and forthe Annex. The Annex does not currently containits own equipment, so no Annex ComponentsGroup is needed.

12) Save the project: File > Save, or .


Part 1-4: Assign Elements to Logic Functions

1) Click the Function View button, , to open thatwindow. If the Physical and Geographic Views areclosed, open them as well. Click the Arrangebutton, , to make all Views the same width.

2) Expand the Function View project element to seethe automatically added link, Logic Functions forFireFinder XLS Node. All the logic of this single-Node installation will be listed under this link. EachNode of a multiple-Node installation would haveits own Logic for Node link.

3) This links properties include three Audible ControlFunction Priority Action fields. These set theresponses for NAC Coded ZIC output circuits. Asyoull see, they also correspond to the three inputsof all Audible Control Functions for this Node. TheZone Coding properties listed after these fields arenot used in this project.

For Priorities 1-3 respectively, select SteadyAudibles, Temporal / Uniform and March Time30 SPM. These settings correspond to the requiredproject alarm, alert and recall states.

4) The first logic function to be created will be theAudible Control Function for the default audible,on the third output circuit of the 1st Floor ZIC.Select the Logic Functions for Node element andinsert an Audible Control Function. Select thisfunction element. In the Detail View, enterDEFAULT AUDIBLE for the property FunctionLabel, and 1st Flr Lobby for Comment.

Expand the function and note the light-yellowinputs Priority 1-3, and the light-blue output. Onthis function, each input can have a single device,Group, System Flag or Function linked to it. Thestate of the linked element determines the state ofthe input. Each Priority input corresponds to adifferent audible output, as you set up in the Logicfor Node link earlier.

5) From the Physical View, drag and drop thegeneric System Flags element (directly under theNode) onto the functions Priority 1 input in theFunction View. Select the resulting link. Set theproperty Flag Name to Any Alarm.

6) Drag and drop the ZIC Out Ckt Default Audiblefrom the Physical View to the Audible ControlFunctions output. When an alarm occursanywhere in this system, this Audible ControlFunction will cause the default audible on the 1stfloor ZIC to produce a steady tone, as you selectedin the Logic Functions for Node link.


7) Now you will create the logic for the PMIs FunctionKeys (touch screen graphical buttons). A FunctionKey produces a short pulse output when the screenis touched, but well want a panel user to be ableto momentarily touch the key, and have theresulting operation latch on or off. Therefore,youll use D Latch functions to connect theFunction Keys to the system logic.

8) Insert a D Latch under the Logic Functions forNode element. Label it TEST 1ST FLOOR /Toggle/Latch.

9) This D Latch will be used as the Test 1st FloorFunction Keys toggling latch, with the outputbecoming and staying true with the first screentouch. For this role, the D Latch requires its outputto be inverted (changed to the opposite state) andthen fed back to its own Data input.

To set this up, drag the D Latch itself to its ownData input list. Select the resulting yellow functionlink, and in the Detail View check the Invert box.The yellow links F turns red to indicate that it isan inverted input.

10) Drag the Function Key Test 1st Floor from thePhysical View onto the Clock input. This FunctionKey will now cause the output to become true atthe first touch, then to toggle between false (off)and true (on) for additional touches.

11) A Clear input resets the D Latch output to false(off). We will use the Function Key STOP to dothis. Drag and drop this Function Key from thePhysical View onto the Clear input. The TEST 1STFLOOR toggle/latch is complete.

You have not assigned any links to the blue DLatch output, because the D Latch will be assignedto the input to another function. Zeus allowsfunctions to be assigned to the inputs of otherfunctions, but not their outputs. You assign onefunction to the input of another by dragging theinput function itself, not its output.

12) Insert three more D Latches for the TEST 2NDFLOOR, TEST ANNEX and RECALL functions.Format as before: STOP Key on Clear, invertedoutput of each D Latch itself on its own Data input,and the respective Function Key on Clock.

13) Three different audible tones are required: EVAC,Alert and Recall. The only way to activate the recalltone is to press the Recall Function Key.However, multiple conditions an alarm or aFunction Key press will sound EVAC in onefacility location, and Alert in the others.

D Latch in Toggle/Latch Application:


To program this behavior, insert six OR functionsunder the Logic for Node link and set them up:

OR Function Label Inputs1ST FLR EVAC Group: 1st Floor

D Latch: TEST 1ST FLOOR1ST FLR ALERT Group: 2nd Floor

Group: AnnexD Latch: TEST 2ND FLOORD Latch: TEST ANNEX

2ND FLR EVAC Group: 2nd FloorD Latch: TEST 2ND FLOOR

2ND FLR ALERT Group: 1st FloorGroup: AnnexD Latch: TEST 1ST FLOORD Latch: TEST ANNEX

ANNEX EVAC Group: AnnexD Latch: TEST ANNEX

ANNEX ALERT Group: 1st FloorGroup: 2nd FloorD Latch: TEST 1ST FLOORD Latch: TEST 2ND FLOOR

Note that the OR allows multiple links on its input.An ORs output becomes true when one or more ofthe links on its input become true. Here, ORs willbe used to activate the proper response from theaudibles and strobes from the true input of aparticular Function Key or Group.

Select one of the inputs Group links, and in theDetail View examine the property Input Criterion.You can select different criteria to make the Groupinput true. Keep the Active default setting for allthe input Group links.

14) Insert three new Audible Control functions, fullyexpand them, and name them 1ST FLRAPPLIANCES, 2ND FLR APPLIANCES, and ANNEXAPPLIANCES.

15) Drag the EVAC OR functions to their respectiveAudible Control Priority 1 Inputs for example, 1STFLR EVAC to the 1ST FLR APPLIANCES AudibleControl Function input Priority 1. Assign the AlertORs to the Priority 2 Inputs, and the RECALL DLatch to all Priority 3 Inputs.

16) From the Physical View, assign the 1st Floor ZICAudibles and Strobes Out Ckts to the 1st FloorAudible Control Function output. Repeat for the2nd Floor and the Annex. Save the project.

You should note two things. Although the strobesare lumped in with the audibles, the ZIC will drivethe strobe circuits in a non-coded way. Also, as analternative, the Out Ckts could have been assignedto their respective Floor Groups, and those Groupscould have gone on the function outputs insteadof the circuits themselves.


Part 1-5: Check and Compile the System

1) In the Physical View, select the 2nd Floor SSD.Change its HNet Address from 11 to 9, the same asthe Annex SSD. This is an intentional error.

2) You will now check the project for errors beforecompiling it into a configuration file to be loadedinto the systems PMI. Click Build > Check, .

3) If you configured the system as outlined in thesesteps, you will see one error message in theresulting Check Result window for the intentionalerror we just introduced. Double-click on themessage; the 2nd floor SSD is highlighted in grayin the Physical View. Select that SSD and change itsHNet address back to 11.

4) Re-run the check. You should now receive no erroror non-fatal warning messages.

5) To compile this project, first save it. Click Build >Compile, . The FireFinder XLS Compiled (.hrc)version of the system is saved to the projectdirectory along with the Zeus Database (.zdb)version. Zeus adds HdbNode01 to the .hrc filename to indicate that this is the compiled file forNode 1, and therefore is to be transferred to thephysical PMI for Node 1.

If this example used multiple nodes, there wouldbe multiple .hrc files, each to be transferredseparately to the different nodes. You might alsohave used the Compile All command instead ofCompile to create those files.

In this case, the compiled .hrc file is larger than the.zdb file, but that is because the projects graphicsand audio files are included in the compilation,while the original files are stored in anotherdirectory.

The file etuser.lst is the record of the projectelapsed time, the total amount of time the projecthas been open, which is displayed in the bottomright corner of the Zeus main screen.

6) To transfer the Acme configuration to its physicalcontrol panel, you would connect a cable from theserial port of a host computer to the Upload jack ofthe Nodes control panel. You would then run Zeusand use Build > Transfer, , to upload thecompiled file to the panel, with the option oftransferring the panels current history data to thehost computer.


Part 2-1: Add Voice Components (Physical View)

1) Open the completed Acme fire-only system. Closeall Views except the Physical. Select the Nodeelement. Set the DNet Wiring Style (bottom of theDetail View Properties Tab) to Style 4.

2) Select the Inner Door on the 1st floor CAB. Insert andlabel an FMT as Firefighter Master Tel - 1st Flr, anLVM as Live Voice Module - 1st Flr, and an SCM asSwitch Control Module - 1st Flr. Ignore the CANAddress of ^0 on these devices for now. Expand theFMT and label its Master Phone as Master Phone -1st Flr Lobby. Expand the LVM a nd label itsMicrophone as Page Mike - 1st Flr. Expand the SCM.

3) The multiple switches under the LVM and SCM willbe used for such functions as selecting thechannels and speakers to which pages will bedirected; requesting, granting and denyingtransfers of control from one Voice CommandStation to another; and enabling Warden Pages.

Label and set up the LVM switches as follows:

Switch Device Usage Label1 Request Access 1st Flr Request Acc2 Grant Access 1st Flr Grant Acc3 Deny Access 1st Flr Deny Acc4 All Call 1st Flr All Call5 Page to Evac 1st Flr to All Evac6 Page to Alert 1st Flr to All Alert9 Microphone Page Mike - 1st Flr

Switches 1-3 will enable control transfers to andfrom this station; 4-6 will direct pages to theEmergency Page, Evacuation and Alert channels.You will soon set up these Voice functions. For allswitches, check the property Active. For the MIC,set Cough Delay the pause between un-keyingthe mike and the end of a page to 5 seconds.

PHASE 2: Add Voice to Fire System for Acme Manufacturing Co.

The Acme fire system will now be upgraded to include Fire Finder XLS Voice components. The additional requirementsfor this upgrade are as follow:

Voice stations on both Main Bldg floors and in the Annex, with control transferable between all three stations. Three Voice channels for emergency pages, evacuation messages, and alert messages. Voice stations are capable of paging to any of these channels. Pre-recorded Evac and Alert messages will be broadcast from the 1st-floor enclosure, with backup message

files stored in the 2nd floor enclosure. These messages will be the same for all locations. For example, thesame Evac message plays in any location in the facility that is in an Evacuation state. Emergency telephone system with master phone at the Lobby enclosure, using separate circuits for Main Bldg

1st and 2nd Floors and the Annex. Emergency phones plug into jacks located along each circuit, in all rooms. Voice system will use existing enclosures (CABs), with an additional Remote Box (REMBOX) used for the Annex

components. Annex Voice service will be hosted by the 1st floor enclosure.


4) The eight switches under the SCM will be used tocomplete the capabilities needed at this station.Label and set up these switches as follows:

Switch Device Usage Label1 Speaker Group 1st Flr to 1st Flr2 Speaker Group 1st Flr to 2nd Flr3 Speaker Group 1st Flr to Annex4 Telephone Group 1st Flr to 1st Flr5 Telephone Group 1st Flr to 2nd Flr6 Telephone Group 1st Flr to Annex7 Warden Page Warden Page -

1st Flr8 Lamp Test 1st Flr Lamp Test

Switches 1-3 will allow the user to page to thespeaker circuits that you will soon add to theGroups 1st Floor, 2nd Floor and Annex. Switches 4-6 will connect emergency phone circuits to theMaster Phone on the FMT. Switch 7 will allow theuser to make a Warden Page, a page from thefirefighter telephone system. Switch 8 will be usedto test the panel LEDs. For all switches, theproperty Active must be checked.

5) Select the 1st-floor CAB-2, and insert a second CC-5Card Cage under it. Label this CC-5 Voice SystemCards - 1st Flr.

6) Insert a DAC-NET (DAC) under the new CC-5. Labelit Digital Audio Card - 1st Flr. In the Detail View,check the property First DAC because this is thefirst DAC in the system.

Note: DACs accept HNet addresses of only 1through 99. A good practice for Nodes with manyDACs (up to 32 are allowed) is to reserve the lowerHNet addresses for them.

7) In the Detail View, uncheck the DAC property UseDefault PMFs, so that the properties Tones FileName and Message File Name become available.

For each of these properties, you select a PMF file,with the extension .pmf, that contains a collectionof pre-recorded tones or messages. The individualtones or messages in these .pmf collections arestandard wave (.wav) files. Once a PMF isselected, its .wav files are available to this DAC.(The default PMFs is selected in the Nodeelements Detail View.)

8) With the DAC still selected, click the button to theright of Tones File Name. In the resulting dialog,click System Folder for the field Look In, andselect the Default Tones PMF. Similarly, select anappropriate Default Message PMF for the propertyMessage File Name.


9) Insert three Prerecorded Messages under the DAC.These are .wav messages that will be selected fromthe .pmfs stored in the DAC. Label theseEmergency Page Tone, Evac MSG - Primary, andAlert Msg - Primary. They are primary becausethis DAC will be the primary source of thesemessages for the system.

10) Select the PreRecorded Message for the EmergencyPage channel. Click the button at the right of itsproperty Audio Source Wave Filename. In theresulting dialog, note that the two .pmf files youchose earlier for the DAC are available in theTones/Message File field: default tones and defaultmessages. Select the default tones .pmf to list itsindividual .wav files below. For the EmergencyPage Tone, select 900 Hz from the Default Tones.pmf. This tone will play at the start of a page onthe Emergency Page channel. Select the Evacmessage, and use the same process to assign oneof the Evac1. wavs (male or female) from theMessages .pmf. Repeat this process for the AlertMessage.

11) Insert a Local Page Board (LPB) under the DAC, andlabel it Local Page Board - 1st Flr. The LPB isrequired for the LVM and FMT to operate.

12) All within the Physical View drag the FMT, LVM andSCM to the DAC. Links are created under the DACindicating that it will host these Control AreaNetwork (CAN) modules. (The ^ in the elementlabels indicate CAN addresses.)

13) Insert the following components under the VoiceCC-5: ZAC-40 (Zone Amp Card - 1st Flr), ZAC-40(Bkup) (ZAC Backup - 1st Flr) and TZC-8B(Telephone Zone Card). Drag these to the DAC tocreate CAN links. Note that a dialog will askwhether these cards will be assigned to the DAC,or simply placed above it on the branch under theCard Cage. Select assign in each case.

14) Select the ZAC-40. This will be a distributed-amplifier system; make sure that the property BulkAmplification Riser Channel is set to Not Used.Repeat this step for the ZAC Backup.

15) Drag the ZAC Backup to the ZAC-40. The resultinglink assigns this ZAC Backup to this ZAC-40. (Note:The ZACs cannot be backup-linked until after theyare both linked to the DAC.)

16) Expand the ZAC-40 and label its Amplifier Circuit1st Flr Speakers. Enter 40 for the circuitsproperty Speaker Wattage (40 Watts). Zeus will usethis information at compile time to determinewhether the configuration includes sufficientpower supply capacity.


17) Expand the TZC and label its first three TelephoneCircuits 1st Flr Tel Ckt, 2nd Flr Tel Ckt andAnnex Tel Ckt. For each circuit, set the propertyDevice Usage to Telephone Circuit. The remainingcircuits will not be used.

18) A second ZAC and ZAC Backup are needed in the1st floor enclosure to support the Annex Voicecomponents, since the Annex will not have a fullenclosure (CAB) of its own. Select the 1st floorCAB-2. Insert and label a CC-2 Card Cage, VoiceSystem Cards - Annex. Under the CC -2, insertanother ZAC-40 (Zone Amp Card - Annex) andZAC-40 Backup (ZAC Backup - Annex). Again, BulkAmplification Riser Channel must be Not Used onboth. Drag both ZAC-40s to the 1st floor DAC fortheir CAN links. Assign the Annex ZAC Backup tothe Annex ZAC. Expand the Annex ZAC-40 andlabel its Amp Ckt Annex Speakers. Set SpeakerWattage to 20.

19) The Annex LVM / SCM pair will be mounted in a 2-place Remote Box. Select the Node element. Inserta REMBOX-2; it will appear at the bottom of thePhysical View. Label it Annex REMBOX AnnexOffice. For its property Power Supply PSC Address,enter 1, the HNet Address of the 1st Floor PSCwhich will power the REMBOX components.

20) To save effort, you will copy the 1st floor LVM andSCM for the Annex. Select the 1st Floor LVM andSCM, hold down the Ctrl key, and drag them to theREMBOX Inner Door to copy them. Select theREMBOX and use Find/Replace Text to change theAnnex component labels from 1st Flr to Annex.Afterward, change the first SCM Switch label toAnnex to 1st Flr.

21) The Telephone Group switches on the Annex SCMare not applicable, since there is no FMT in theAnnex. Change the Telephone Group switchUsages and labels to Annex Alarm ACK, AnnexSupervisory ACK and Annex Trouble ACK. TheseAcknowledgement switches will be useful, since anAnnex user will not have a PMI with which toperform these functions.

22) The Annex LVM and SCM require CAN hosting by aDAC, which cannot be mounted in a REMBOX.Assign the LVM and SCM to the 1st floor DAC toassign CAN addresses to them. To do this over thelong distance in the Physical View, select bothelements, copy them (Ctrl + C, ), right-click theDAC, and select Assign To in the menu.

Note: Communication between the DAC and theREMBOX is enabled by the RNI Remote NetworkInterface under the REMBOX.


23) Taking advantage of the floor plan similarities, youwill now add Voice to the Main Building 2nd Floorby copying the Annex Voice elements. Delete thecurrent Inner Door on the 2nd Floor CAB. Selectthe REMBOX Inner Door, hold down the Ctrl key,and drag it to the 2nd Floor CAB. Select the copieddoor, and use Find/Replace to change alloccurrences of Annex to 2nd Flr.

24) Expand the SCM. Similar to the Annex SCM,change and re-label its Telephone Group switchesto Alarm, Supervisory and Trouble Ack. Change theSwitch 3 label to 2nd Flr to Annex.

25) Copy the 1st Floor Voice Card Cage (CC-5) to the2nd Floor CAB. Expand the copied Card Cage anddelete the TZC, since only one telephone systemhost is required. Select the Card Cage, and useFind/Replace to change all occurrences of 1st to2nd and Primary to Backup.

26) Assign the LVM, SCM, and ZACs to the 2nd FloorDAC. Assign the ZAC Backup to the ZAC.

27) Select the 2nd Floor DAC. Uncheck the propertyFirst DAC and check Last DAC, since this is thesecond and last DAC on the DAC network. (This isnecessary for this Style 4-wired system, but not forStyle 7.) For the properties Tones File Name andMessage File Name, selected the same PMFs asused for the 1st floor DAC.

28) Delete the Emergency Page PreRecorded Message,since page-type channels do not have backupsources. Change the Evac and Alert Messageaddresses to 1 and 2. Select the same .wav files forAudio Source Wave Filename as for the 1st floor.These Messages will become the backup sourcesfor their respective channels.

Part 2-2: Group Voice Elements (Geographic View)

1) Open and fully expand the Geographic View,while leaving the Physical View open as well.

2) Add a Zone, Annex Components, under theAnnex Floor-level Group, with the DetailMessage Annex Voice components supportedby 1st Flr Enclosure. Select the Annex map forthe Zones Group Event Map Name.

3) Assign these elements to their respectiveComponents Zones: DACs, Amp Ckts, Tel Ckts.The other Voice elements (CAN modules) cannot be added to Groups.

4) Save the project.


Part 2-3: Set Up Voice Controls (Control View)

1) Open the Control View, , leaving the Physical andGeographic displayed as well.

2) Select the Project element in the Control View, andinsert the element System Audio Channels. Itsproperty Audio Distr. Topology must be set toDistributed, since this is a distributed-amplifiersystem using ZACs.

3) For this 3-channel Voice system, insert three AudioChannels under System Audio Channels. Set thesechannels up as follows:

ChannelID

ChannelType

ChannelQuality

EmergencyPage

SystemChannel

Improve, 11 kHz(8 BW)

Evac1 SystemChannel

Standard, 11 kHz(4 BW)

Alert1 SystemChannel

Standard, 11 kHz(4 BW)

The Channel Quality BW figures representbandwidth, the amount of resources the channel willconsume. A total of 16 BW is available.

For each channel, set Channel Type to SystemChannel. The tones and messages for this systemwill come from the 1st floor DAC, with similar PMFsand .wavs stored in the 2nd floor DAC as Evac andAlert channel backups. If Local Channel wereselected, each floor would use the messages in itsown DAC.

4) Drag the Prerecorded Messages, under the 1st- and2nd-floor DACs, from the Physical View to theirrespective Audio Channels in the Control View. Forexample, assign the Evac messages (primary andbackup) to the Evac1 channel. Page-type channelsdo not allow backups; therefore, assign only themessage Emergency Page Tone on the 1st floorDAC to the Emergency Page channel.

5) Select each of these Prerecorded Message links(Device Audio Sources). Check the property boxBack Up Audio Source for each backup source.Make sure it is unchecked for each primary source.That is, each Prerecorded Message on the backupDAC on the 2nd floor must be checked as a backupsource. The Emergency Page channel source,Emergency Page Tone, is a primary source andtherefore unchecked.

6) From the Physical View, drag the Node elementto the Project element in the Control View, tocreate the Control for FireFinder XLS Node 1 link.


7) Select the Control for Node link. In the Detail View,check Telephone Tones Enabled so that emergencyphone users will hear call-status tones. SetEmergency Page Pre Tone Duration to 3 so thePrerecorded Message Emergency Page Tone willplay for 3 seconds before a live page starts.Convenience Page Duration can be left at 0, andVoice Zone Coded System must be unchecked,since both are not used. Check Telephone ThroughReset so that panel resets will not cut offconversations. Check all Strobe During boxes sothat strobes will flash during Voice operation.(Note that strobes will flash when an EmergencyPage is made, even without an Evac or Alert state.)Set Speaker Group Default to Emergency Page sopages play over those speakers receiving theEmergency Page channel, when no channel isactivated. Uncheck all Auto Page properties sothat the user is required to select the Evac or Alertchannel before a page will play over that channel.

8) Select the Control for Node link. Insert and label aCommand Station, 1st Flr CMD Sta Lobby.Command Stations are sets of Voice, Fan and/orDamper controls. This Command Station will bemade up of the FMT phone, LVM mike, and theLVM and SCM switches on the 1st floor CAB door.

9) Drag all three Floors from the Geographic View tothe Command Station. The Groups include Voiceelements that this station will operate.

10) Select the 1st flr Command Station. Check theproperty Master Command Station so that thisstation by default has system access, and a user atanother station must initially request access fromthe station in control by pressing the requestbutton on the requesting station.

11) Copy, paste and re-label this Command Station tocreate the 2nd floor and Annex stations. For allstations, check Access Control Required, as well asthe Access Required properties that apply to thissystem: Access Reqd for Emergency Page, Evac,Alert and Telephone.

12) Drag each Speaker Group SCM Switch from thePhysical View to the Control View, to its respectiveFloor under its respective Command Station.Repeat this process for the Telephone Group SCMSwitches (1st floor Command Station only). Eachswitch will activate the Group items that match itsUsage, and ignore all others.

13) For each floor, drag all LVM switches and allremaining SCM switches directly to that FloorsCommand Station. These switches applydirectly to the operation of the CommandStation itself.


14) Drag each LVMs MIC from the Physical View tothe Control View, directly to its respectiveCommand Station. For the 1st floor CommandStation, assign the Master Phone as well.

15) Save the project. Manual Voice controls arecomplete. (Previous page; the Annex station, notshown, is similar to the 2nd floor station.)

Part 2-4: Program Voice Functions (Function View)

1) Automatic Voice operations will now be added.Open the Function View, with the Geographic andPhysical Views open as well.

2) The system must be programmed so that during anEvac-level condition, the Evac message automaticallyplays over the affected speaker zone, or an Alertmessage automatically plays during an Alertcondition. This is readily set up using the SpeakerControl Function.

Insert and label a Speaker Control Function underthe Logic Functions for Node element, 1ST FLRSPEAKERS. Drag the OR function 1ST FLR EVAC tothe Evac 1 input, the 1ST FLR ALERT OR to Alert 1,and the 1st Floor Group to the output. When theEVAC OR is true, the Evac1 channel will play theEVAC message. The Alert1 channel will worksimilarly, unless the higher-priority Evac1 channelis active. The Emergency Page channel (Local EmgPage input) is strictly manual and hence not usedhere.

3) Set up similar Speaker Control Functions for the2nd Floor and the Annex. Save the project.

Part 2-5: Check and Compile the Project

1) Click to run a compile-check of the project.This should result in the following error: the 1stFloor CAB-2 requires additional power to drive thenew Voice components.

2) Select the CAB-2. Insert and label a PSX, PowerSupply Extender - 1st Floor, to supplement thePSC. (Only one PSC is allowed per enclosure, with amaximum of three PSXs.)

3) Another check will show the 1st flr CAB-2 is nowtoo small for the additional components. Select theCAB-2. Change it to a CAB-3 using Edit >Find/Replace Tree Node. You will need to re-enterthe label, 1st Flr Enclosure - Lobby.

4) Run the check again. There should be no furthererrors. The project can now be compiled.


1) Open the Physical View. In the 1st floor CAB-3,delete the 2 ZACs and 2 ZAC Backups, move theTZC and DAC to the CC-2 card cage, and deletethe Voice CC-5 card cage. Change the CC-2 labelto read Voice System Cards - 1st Flr.

2) In the 2nd floor CAB-2, delete the ZAC and ZACBackup. Move the DAC to the Fire CC-5 cardcage. Delete the Voice CC-5. Change the Fire CC-5 label to Fire and Voice Cards - 2nd Flr.

3) Select the Node and insert a CAB-1. Change theEnclosure Number to 2 and label it 2nd FlrEnclosure - Hallway. Delete the PSC in this CAB -1.Expand the original 2nd flr CAB-2 and move itscomponents to the CAB-1. Delete the CAB-2.This completes the system consolidation.

4) Select the 1st floor CAB. Insert and label a ZAMand ZAM Backup, Channel A Zone Amp Moduleand Channel A ZAM Backup. Insert anotherZAM/ZAM Backup pair, labeled Channel B.

5) Drag the ZAMs and ZAM Backups to the 1st floorDAC for their CAN links. Drag the ZAM Backupsto the ZAMs for the backup links.

6) Set property Bulk Amplification Channel Riser toChannel A on the Channel A ZAM and ZAMBackup. Use Channel B for the other pair.

7) Expand the ZAMs and label their Amp CktsChannel A Speakers and Channel B Speakers.For each, set the property Speaker Wattage to100, the combined wattages of the 1st floor,2nd floor and Annex speakers.

PHASE 2a: Using Bulk Amplification for Voice

The Voice setup just presented consisted of a Distributed amplification system, in which each amplifier (ZAC)was dedicated to a speaker zone. For a system larger than this simple example, this approach can provide greatflexibility, but also may require a significant amount of hardware.

A Bulk Amplification setup allows the use of only one or two amplifiers to drive speakers over multiple zones.The tradeoff is that only one or two channels can be played at the same time within that system. While all AudioChannels can be accessed, if the system is so designed, only the two highest priority channels will play if threeor more channels are requested. For example, if a two-channel bulk system is broadcasting over the Evac1 andAlert1 channels, and an Emergency Page is made, the Alert1 broadcast will be suspended during the page.

In a two-channel Bulk Amplification setup, speakers are connected to two risers, Channel A and B. Each amplifier(ZAC or ZAM Zone Amplification Module) is associated with a ZIC Output Circuit in order to be switched in andout of its riser. In the Zeus Geographic View, each ZAMs Amplifier Circuit is linked multiple times, once to theeach applicable Group in the system, along with the specific ZIC Output Circuit for that Group.

The following procedure shows the steps relevant to converting the Acme Voice setup, which uses two ZACs in aDistributed Amplification scheme, to a Bulk Amplification scheme using two ZAMs, two ZAM Backups and onededicated ZIC in the Lobby enclosure. The system will be consolidated to minimize enclosure sizes and thenumber of components.


8) The ZAMs will be physically wired to a newZIC, which will perform the switching of theZAMs into the Channel A and B risers.

Insert and label this ZIC, Speaker Circuits,under the CC-5 in the 1st floor CAB.

9) Insert four Out Ckts under the new ZIC. Label thefirst three 1st Flr Speakers, 2nd Flr Speakersand Annex Speakers. For all four, set theproperty ZIC Circuit Usage to 25V Speaker.

The fourth Out Ckt is not used directly. However,Speaker-usage Out Ckts must be set in pairs,Circuits 1 and 2 or Circuits 3 and 4. If Circuit 4were not inserted and set to Speaker usage, anerror would result during Check or Compile.

10) Open the Geographic View and leave thePhysical View open. Expand the Projectelement until the Zone Groups are visible.

11) From the Physical View, drag the Amp Ckts underthe ZAMs to all three Components Zones in theGeographic View. Do this so that the 1st Flr, 2ndFlr and Annex Components Zones each includelinks to both the Channel A and B Amp Ckts.

(Note: The Amp Ckt is the only element that canbe assigned to multiple Groups in the GeographicView. This is done only for Bulk Amplification.)

12) From the Physical View, drag each of thefirst 3 Out Ckts under the Speaker CircuitsZIC to its respective Components Zone in theGeographic View. Do this so that the OutCkt labeled 1st Flr Speakers is assigned tothe 1st Flr Components Zone, etc. Do notassign the fourth Out Ckt.

13) Open the Control View. Expand the Projectelement. Select System Audio Channels. In theDetail View, set Audio Distribution Topology toBulk and Bulk Amplification Channel Count toTwo. Close the Control View. The FunctionView does not need modification.

14) Run Check, . If errors or warnings appear,make the necessary corrections.

15) Save the project.


1) In the Physical View, select the Inner Door of the1st floor CAB. Insert and label an FCM, FanControl Module - 1st Flr. Expand the FCM, andlabel its first 3 switches 1st Flr AHU Off, 2ndFlr AHU Off and Annex AHU Off. The otherswitches are not used. Drag the FCM to the 1stfloor DAC for its CAN link.

2) Make sure each FCM switch property Device Usageis set to Fan so the switches operate fans only,and the switch LEDs to properly indicate fan status.Make sure the property Active is checked.

3) Repeat this process for the 2nd floor CAB andthe Annex REMBOX. For the Annex FCM, use the1st floor DAC for the CAN link.

4) Select the 1st floor DLC. Insert and label an HTRI-R,1st Flr AHU Control. The HTRI-R consists of asupervised switch input and a separate relay.The input will indicate AHU fan operation (via aswitch on the fan itself) to the 1st floor FCM. Therelay controls the power to the AHU fan.

5) For the HTRI-R property Switch 1 Base LanguageCustom Message (label), enter 1st Flr AHUMonitor Switch. For the Relay label, enter 1stFlr AHU Actuation Relay. These items and labelsdo not appear in the Physical View tree, but maybe displayed on the PMI. Set the Switch 1 DisplayCategory to Fan.

6) Set Switch 1 Usage to Fan Monitor On andRelay Usage to Fan Actuator Off.

7) Copy and paste this HTRI-R under the same DLC(1st Flr). Change the element, switch and relaylabels from 1st Flr to Annex. Paste anothercopy of the HTRI under the 2nd flr DLC. Changeits labels from 1st Flr to 2nd Flr. (In each case,Find/Replace Text can be used to quickly changeall three labels: element, switch and relay.)

8) Open the Geographic View. Assign each HTRI-Rfrom the Physical View to its respectiveComponents Zone.

PHASE 3: Adding Fan Control

This section shows how fan control would be added to the original Acme fire/voice system. Both manual fancontrols, using a Fan Control Module at each Command Station, and automatic controls are shown.

The requirements for this addition are as follows:

- The Main Building floors and the Annex each have an air handler unit (AHU) with fan and indication switch.- Each AHU is actuated and monitored using an HTRI-R Addressable Interface with Relay on existing device loops.- An alarm on a Main Building floor or in the Annex shuts down its AHU.- AHUs may also be shut down manually at each Command Station, using Fan Control Modules (FCMs).- Access control is required for manual fan control.


9) Keep the Physical View open. Open theControl View.

10) In the Control View, select each CommandStation and check its property AccessRequired for Fans.

11) Under the 1st floor Command Station,assign each switch from the 1st floor FCMto the respective Group it will control. TheFCM switches now address the HTRI-Rscontrolling the AHU fans.

12) Repeat this process for the 2nd floorCommand Station and FCM, then for theAnnex. Manual fan control is now set up.

13) Close the Control View. Open the FunctionView and the Geographic View.

14) Select the Logic Functions for Node link. Insertand label an OR Function, 1ST FLR AHU.

15) From the Geographic View, drag the 1stFloor Group to the OR input. Select the newinput link. Set the property Input Criterionto Active. The OR will become true whenany part of the 1st floor goes into alarm.Invert must be unchecked.

16) Drag the 1st Floor Components Zone to theOR output. Select the new output link. Setthe property Output Selector to Fan. Whenthe OR becomes true, the Fan-usagecomponents on the 1st floor (the HTRI-R)will be activated.

17) Repeat this process for the 2nd floor andAnnex. An alarm on a floor or in the Annexwill automatically shut down the AHU fanfor that zone. The automatic fan controlsare now programmed.

18) A compile check should indicate no errors.Save the project.


Part 4-1: Add FireFinder XLS Node (Physical View)

1) Open the completed Acme FireFinder Voicesystem configuration (for the Main Building andAnnex). Close all views except the Physical view.Select the project. Make sure that the XNetNetworked Configuration is checked at thebottom of the Detail View Properties Tab.

2) Select the Node element. Set the XNet Address(Top of the Detail View Properties Tab) to 1. Thiswill be the First Node in the Multiple SystemConfiguration.

Note: Set the XNet address to 1 on the PMI(Person Machine Interface) using the addressswitch. Set Switch 4 of S17 to ON; set Switches1-3 of S17 to OFF. Refer to the PMI InstallationInstructions, P/N 315-033070, for furtherinformation on setting the PMI to XNet Mode.

3) Insert a CC-5 card cage. Move the SpeakerCircuits ZIC-4A from the first CC-5 and themodules from the CC-2 to the new CC-5. Labelthe new CC-5 as Voice System Cards 1st Flr.Delete the CC-2.

4) Select the CC-5 Fire System card cage underCAB-3 1st Floor Enclosure Lobby. Insert and labela NIC-C (XNet) as Ntwrk Interface (XNet) MainBldg. This NIC-C Card will communicate to otherSiemens systems using XNet.

5) Select the Node element. Insert and label aPseudo Module as Pseudo Module Main Bldg.Insert 3 Pseudo Devices to the Pseudo Moduleand label them Pseudo Alarm Main Bldg. 1stFlr, Pseudo Alarm Main Bldg. 2nd Flr, PseudoAlarm Main Bldg. Annex, respectively. Change theusage of each Pseudo device to Status Only.

Note: Pseudo modules and Pseudo devices arenot physical modules and devices. They aregenerally used for logic function purposes only.

PHASE 4: Networking Multiple Systems

This section shows how multiple Fire Finder XLS Nodes and other Siemens systems would be added to and networkedwith the original Acme fire/voice system.

The requirements for this addition are as follows:

A third building (Finance Building) is added to the fire protection plan. A FireFinder XLS Node is added to the Finance building. The Finance buildings shipping area currently has an

MXL-V for Fire and Voice protection. Network the new FireFinder XLS and the existing MXL-V to the MainBuildings XLS-V. Events in the Main building must send Alert signal to the Finance building. Events in the Finance building will trigger an Alert message in the Main building and the Annex.


Part 4-2 Add Finance Bldg. FireFinder XLS Node

1) With the Project element selected, insert aFireFinder XLS Node under it by clicking Insert >FireFinder XLS Node.

2) Select the FireFinder XLS Node element in thePhysical View. Click the Properties tab in theDetail View window. Click the property field BaseLanguage Cust. Message, type Acme Mfg Co.Finance Bldg., and press the Enter key. Thisbecomes the Node elements label in thePhysical View, and the title shown on the PMIcontrol panel.

3) With the Detail View Properties still selected,notice that Zeus has already assigned XNetAddress 2 for the newly inserted XLS in our XNetsystem. Toward the bottom of the Detail View,set Battery Capacity Factor to Total Amp x 24Hours, and Battery Capacity Reserved to 25%.

4) Click the box next to the node propertyFireFinder XLS Map Names. The resulting dialogallows you to select the floor plans that can beshown on the Nodes PMI (control panel) todisplay event locations. Select the Acmeexample maps already in Zeus Acme Floor 1,Floor 2, Annex and Finance and click Add tomake these files available to this Node. Close thedialog.

5) Note the property On Site Contact Name/Phone.This information is prominently displayed on thePMI when the user requests event details. This issimilar to what was done in the previous FireSystem for the Main Building.

Note: Expand the Node element by clicking thesmall plus sign next to it. The elements HistoryLog and System Flags, which are part of theNode element, appear.

6) Select the FireFinder XLS Node element andinsert the new CAB-2 element under it. Insert >CAB-2. Change the CAB-2 base language custommessage to read Finance Bldg Lobby.

7) Zeus has already inserted a PSC-12 under theCAB-2; Expand the CAB-2 by clicking the smallplus sign to the left of the CAB once to show thePSC. Expand the PSC. The two fixed PSC Relaysare already under the PSC. Label the PSC PowerSupply - Finance Bldg, and the PSC relays 1)Common Alarm - Finance Bldg and 2)Common Trouble - Finance Bldg Set theproperty Battery Size to 31 AH.


8) Select the CAB-2 and insert its inner door: Insert >Inner Door.

9) Select the Inner Door and Click Insert > PMI to add aPMI (PMI Person-Machine Interface). Label the PMIControl Panel Lobby Finance Bldg.

Set the PMIs Display Group Level Display property toDevice/Primitive, and MORE INFO View to Map soa graphical map will be first displayed when MOREINFO is pressed.

10) The project requires two Function Key operations formanual system testing. On the PMI screen, thesekeys are listed on the Function Key Screen; a user willpress these graphical buttons on the touch screen torun and stop tests.

Right-click the PMI, and select Insert > Function Keyfrom the resulting pop-up menu. A Function Key isinserted as a child of the PMI. Add one more functionkey, and label the Function Keys Test Finance Bldgand STOP. You will set up the logic to programthese keys a little later.

11) Select the PMI again. Click the box next to the PMIsPMI Event Map Name 1 property. The resulting dialogallows you to mark the PMIs position on one or moreof the map files selected for this Node. For SelectBitmap, choose the Acme Finance map. Drag theblue dot to the desired location in the Lobby. When aFinance Building event map is displayed on the PMI, aYou Are Here icon is added at this mark. Note thatyou can click and drag it to adjust its position.

12) Add a five-slot CC-5 card cage as a child under theCAB-2 enclosure. Change the CC-5 custom messageto Finance Building.

13) Select the CC-5 and insert a NIC-C (XNet) under it.The NIC will communicate with the other Node in thesystem. Label the NIC Finance Bldg.

14) The Finance Building requires three output circuits todrive audibles, strobes, and the separate any-alarmdefault audible required by regulation. Insert a ZIC-4A Zone Indication Card under the CC-5. Insert threeOut Ckts under the ZIC. Label these Finance BldgAudibles, Finance Bldg Strobes and Finance BldgDefault Audible.


15) In the Out Ckt Detail View, set the property ZICCircuit Usage to NACCoded for the Audiblesand Default Audible circuits, and Strobe Synchfor the Strobe circuit. (You will code the audibleslater.) On all Out Ckts, check the Silenceable boxand set Wiring Type to Class A.

16) Insert a DLC (Device Loop Card) under the CC-5.Label it Device Loop Finance Bldg. Select theDLC, insert an HFP detector and label this LobbyDetector Finance Bldg. Under the DLC, insertand label an HMS-S pull station (Lobby Pull Sta.Finance Bldg.). Check the property IntelligentEnvironmental Compensation (IEC) for the HFP-11 and set the Application Specific Detection(ASD) setting to Office.

17) Duplicating these two new elements (HFP-11and HMS-S) will populate the device looprequired for our example. Click the HFP, holddown the Shift key, and click the HMS to selectboth devices. Copy these elements to theWindows Clipboard. (Use Ctrl + C, Edit > Copy,or .) Select the DLC. Click Edit > PasteSpecial. In the resulting dialog, set MultiplePaste to 4 and click OK. Four more HFP / HMSpairs are inserted under the DLC, one pair foreach room on the Finance Building protected byXLS Node 2.

18) Select the DLC. In the Detail View Elements tab,use the table to change the elements as shown,filling in the Base Language Custom Messagewith the individual names. Note the amount ofwork that has been saved by using Paste Specialto generate and label repetitious elements.

19) Insert a CDC-4 (Conventional Detector Card) andlabel it Conventional Det. Card Finance. TheCDC-4 is a module that allows conventionalsmoke detectors to be used with the Fire Finder-XLS system. Notice that when a CDC-4 card isinserted into a card cage, all 4 CDC zones will beautomatically inserted under the module.

Only the First two Zones will be used in ourexample. Label them Finance Bldg Lobby andFinance Bldg Hall.

20) Select FireFinder XLS Node 2 and insert a PseudoModule at module address 6. Insert a PseudoDevice at address 1 under the Pseudo Module.Change the devices Base Language Cust.Message property to Pseudo Alarm FinanceBldg. Set Device Usage to Status Only. ThisPseudo Device will be used for logic in Part 4-4.


Part 4-3: Set Up Groups in the Geographic View

1) Click the Geographic View button, , to insertthat View. Keep the Physical View open.

You will now organize the devices in the PhysicalView of Node 2 into Groups that are used forcreating system logic (Function View) anddetermining what graphics and messages thePMI displays during an event.

2) Select the Project element in the GeographicView, and look at its Properties Tab in the DetailView. The five Group levels (1-5) and theirdefault names (Campus, Building, Floor, Area,Zone) are displayed. Note that you can changethe names of the Group levels here to best suityour particular project. Keep these default labelsfor this example project.

3) Insert a Floor (Level 3) element under theGeographic Views Project element. Label thiselement Finance Bldg. Under the FinanceBuilding insert 6 Zones (Level 1), one for theCDC Zones and for each room. Label these CDCZones Finance Bldg., Lobby Finance Bldg.,Hall Finance Bldg., MensRm Finance Bldg.,WomensRm Finance Bldg, and CnfRm FinanceBldg.

4) Assign the Finance Building devices in thePhysical View to their corresponding Groups. Forexample, select the Lobby devices, then dragand drop these onto the Zone Lobby. Note thatlinks of the elements are placed under the Zone;the device icons are replaced by light-yellowboxed arrows. Try using some of the features wediscussed in previous sections like clicking theright mouse button to make some of theassignments. Click Assign to Here for each link.

5) Select a Zone on the Finance Building andexamine its properties. Many of these determinewhat information will be displayed on the PMIduring an event. On the PMIs Alarm DetailsScreen, the properties Base Language DetailMessage, Fire Service Equipment Icon Names,and Hazards / People Icon Names are shown. Onthe PMIs Map Screen, the Group Event MapName graphic and marked position on thatgraphic specified by Group Location is displayed.If you need information or help on any of thissection, select that section and press the F1 keyfor Zeus Help.


6) Select each of the Zones under the FinanceBuilding Group and click the button on the rightof the Group Event Map Name field. In theresulting dialog, use Select Bitmap to select theAcme Finance map for each zone. Mark eachZones position on the map by clicking in theroom the current Group represents.

7) Setup Fire Service Equipment Icon Names andHazards / People Icons in the Detail View. Thatallows you to select icons that will be displayedin the PMIs Alarm Details Screen, which will aidfirefighters in determining resources andhazards in the affected Zone. The Hazards /People dialog includes a feature for generatingcustom 3-digit HazMat icons. You can press theF1 Key to get the Zeus Help feature, which willprovide more details.

Part 4-4: Setup Logic Functions For Node 2

1) Click the Tool bar button, to open the Functionview window. If the Physical and Geographic Viewsare closed, open them as well. Click the Arrangebutton, , to make all Views the same width.

2) Expand the Function View project element tosee the automatically added link, LogicFunctions for FireFinder XLS Node 2. Notice thatthere is one Logic Function link for eachFireFinder XLS Node installed in the Physical tree.

3) For the Logic Function for FireFinder XLS Node2, we will need to set up the default systemaudible similar to Part 1-4, steps 1-3.

First, we will select the sounds for NAC audibles. Clickon Logic Function for FireFinder XLS Node 2 onthe Function view, select Steady Audibles,Temporal / Uniform and March Time 30 SPMfor the properties Audible Control FunctionPriority 1, Audible Control Function Priority 2,Audible Control Function Priority 3, respectively.These settings correspond to the requiredproject alarm, alert and recall states.

4) To create the default audible, insert an AudibleControl Function under the Logic function forFireFinder XLS Node 2. Label this functionDefault Audible Finance Bldg. Enter AudibleControl Function for the Comment property. Fromthe Physical View of FireFinder XLS Node 2, dragand drop the System Flag element (directlyunder the Node) onto the functions Priority 1input in the Function View. Select the resultinglink. Set the property Flag Name to Any Alarm.


Drag and drop the ZIC Out Ckt at address 2:3-3Notification Apps Finance Bldg. from FireFinderXLS Node 2 in the Physical View to the output listof this function. With this logic, any alarm eventin the Finance Building will cause the ZIC-4Adefault audible to produce a steady tone.

5) Similar to the logic for Node 1, we will also usethe PMIs touch screen graphical buttons to testthe logic for Node 2. We will use function key F1to test the logic of the function EVAC FinanceBldg.

6) Insert a D-Latch to Logic Functions for Node 2.Label it Test Finance Bldg. Click on the TestFinance Bldg D-Latch and drag it to the Datainput. Select the resulting link, move the focusto the Detail view and check the Invert property.

Drag the Function key Test Finance Bldg. fromthe Physical View of FireFinder XLS Node 2 ontothe clock input. This Function Key will now causethe D-Latch output to become true at the firsttouch, then toggle between false (off) and true(on) with additional touches.

Insert Function Key Stop from FireFinder XLSNode 2 to the Clear input of D-Latch. At the keypress it will reset the D-latch output to false(off).

7) We will also set up this system so that an Alarmor Function Key press will sound an Evacuationsignal at one location and an Alert at anotherlocation.

To program this behavior, insert an OR Functionunder Logic functions for FireFinder XLS Node 2.Label it Evac Finance Bldg. Enter Priority 1Finance Bldg. for the comment. Drag and dropthe following inputs to the input of this function:Finance Building and Test Finance Building.Leave the output list empty as this function willbe the Priority 1 input of the next AudibleControl function that we are going to add to thisnode.

D Latch in Toggle/Latch Application:

Zeus 5.0 Quick-Start Manual 36 Siemens Building TechnologiesP/N 315-033875-11 Fi

quick start manual zeus 5.0

Documents

zeus session

running zeus

new zeus project

manual covers

voice components physical

voice controls control

windows explorer

microsoft windows