Consilium Tablero c i

FG5000

Fire Detection System

Configuration Manual

Consilium Säkerhet Syd ABTelefon: 040-36 50 60 Consilium Säkerhet Väst ABTelefon: 031-710 79 00 Consilium Säkerhet Öst ABTelefon: 08-563 052 00 Innehållet i det här dokumentet är föremål för förändring utanförvarning på grund av ändrad metodik, design och tillverkning.Consilium kan aldrig hållas ansvarig för fel eller skador som på någotsätt har ett samband med användandet av det här dokumentet. December 2012Document no. 5100355_FG5000_Configuration Manual_I1_EN_2012_CPart no. 5100355

© Copyright 2012, Consilium Säkerhet

Table of contents

1 Introduction ...................................................................................... 1

1.1 About this manual ............................................................................ 1

1.2 Symbols used in the manual ............................................................ 1

1.3 Introduction to the Configuration program .................................... 2

2 Configuration Program Installation ............................................... 3

2.1 Chapter Overview ............................................................................. 3

2.2 System Requirements ....................................................................... 3

2.3 Installing the Configuration program ............................................. 3

2.4 Running the Configuration program .............................................. 3

2.5 Exit the Configuration program ...................................................... 4

3 How to make a System Configuration ............................................. 5

3.1 Chapter overview .............................................................................. 5

3.2 Functional Description .................................................................... 53.2.1 Section overview ............................................................................ 53.2.2 The Fire Detection System ............................................................. 53.2.3 The Configuration Program ........................................................... 5

3.3 The Program Main Window ............................................................ 63.3.1 About the Main window ................................................................ 63.3.2 Main menu ..................................................................................... 73.3.3 File menu ....................................................................................... 83.3.4 Edit menu ....................................................................................... 93.3.5 Command menu ............................................................................. 93.3.6 Help menu ...................................................................................... 103.3.7 Tool bar .......................................................................................... 10

3.4 Options Window ............................................................................... 10

3.5 User Access Window ........................................................................ 133.5.1 About the User Access Window .................................................... 133.5.2 Adding a new user ......................................................................... 133.5.3 Modifying an existing user ............................................................ 143.5.4 Deleting a user ............................................................................... 14

3.6 Zones Window .................................................................................. 14

3.7 Show/Control Window ..................................................................... 15

3.8 System Bus Settings Window ........................................................... 18

3.9 Cause/Effect Window ....................................................................... 19

3.10 Modbus TCP/IP Window ................................................................. 20

3.11 Central .............................................................................................. 223.11.1 About the Central Window ............................................................ 223.11.2 Adding a Central ............................................................................ 22

Table of contents

3.11.3 Adding Modules ............................................................................. 243.11.4 Salwico Language window ............................................................ 253.11.5 Configuring the Power Control Module - ChangeOver M Ext ...... 263.11.6 Configuring the Power Control Module - Charger M ................... 283.11.7 Configuring the Control Module - Control M 4.3 ......................... 323.11.8 Configuring the Control Module - Control M 2.2 ......................... 433.11.9 Configuring the Control Module - Control M X ........................... 443.11.10 Configuring the Input Analogue Module 0-20 - IAM020 ............. 443.11.11 Configuring the I/O Module - I/O M 70 ........................................ 443.11.12 Configuring the I/O Module - I/O M 700 ...................................... 453.11.13 Configuring the Output Solenoid Module M 14 - OSM14 ............ 493.11.14 Configuring the Loop Module - Loop M X ................................... 493.11.15 Configuring the Loop Module - Loop M X Slave ......................... 533.11.16 Configuring the Multiplexer Module 16 - MuxM16 ..................... 543.11.17 Configuring the I/O Module - Relay M 8 ...................................... 553.11.18 Configuring the Repeater Module - RM ........................................ 573.11.19 Configuring the Mini Repeater Module - MN400 ......................... 60

3.12 Importing Configuration Information from Excel ......................... 613.12.1 Introduction .................................................................................... 613.12.2 Importing Loop Module Information ............................................. 613.12.3 Description of the columns in the Loop Board template ............... 62

3.13 Defining Extended Panel Text ......................................................... 633.13.1 Introduction .................................................................................... 633.13.2 Prepare an Excel file with Extended Panel Texts .......................... 633.13.3 Description of the columns in the Extended Panel Text template . 643.13.4 Importing the Excel file with Extended Panel Texts ..................... 653.13.5 Verification of Extended Panel Text .............................................. 65

3.14 Downloading a configuration file from the fire detection system .. 653.14.1 Downloading a configuration file to a USB Memory Stick .......... 65

3.15 Uploading a configuration file to the fire detection system ........... 663.15.1 Uploading a configuration file from the USB Memory Stick ........ 66

4 The Salwico Language ..................................................................... 69

4.1 About the Salwico Language ........................................................... 694.1.1 Introduction .................................................................................... 694.1.2 General Syntax ............................................................................... 694.1.3 The order of evaluation in expressions .......................................... 734.1.4 Explanatory Text ............................................................................ 73

4.2 Command Overview ......................................................................... 734.2.1 Command Tree ............................................................................... 734.2.2 Command Reference ...................................................................... 76

4.3 Inputs ................................................................................................ 764.3.1 Summary Input Commands ........................................................... 764.3.2 Input Command Description .......................................................... 79

4.4 Timers ............................................................................................... 934.4.1 Summary Timer Commands .......................................................... 934.4.2 Timer Command Description ......................................................... 94

4.5 Outputs ............................................................................................. 984.5.1 Summary Output Commands ......................................................... 984.5.2 Output Command Description ....................................................... 99

Table of contents

4.6 Application Examples ...................................................................... 1124.6.1 Section Overview ........................................................................... 1124.6.2 Fire Alarm Outputs ........................................................................ 1124.6.3 Surveillance .................................................................................... 1134.6.4 Management of External Controls ................................................. 1134.6.5 Management of Detectors from Input ............................................ 1154.6.6 Other Examples .............................................................................. 116

5 The CCP Workbench ....................................................................... 117

5.1 About the CCP Workbench .............................................................. 1175.1.1 Introduction .................................................................................... 1175.1.2 General Syntax and semantics Overview ...................................... 117

5.2 Workflow of configuration ............................................................... 1195.2.1 Description ..................................................................................... 119

5.3 Starting CCP Workbench ................................................................. 1205.3.1 Projects ........................................................................................... 1205.3.2 Create a new CCP Workbench project ........................................... 120

5.4 Start program PLC code .................................................................. 1235.4.1 Create a program in your CCP Workbench project ....................... 1235.4.2 Explanation of a FBD diagram ...................................................... 123

5.5 Making application code .................................................................. 1245.5.1 Output Files .................................................................................... 125

5.6 Going online with the CCP Workbench .......................................... 125

5.7 Simulate the project in the CCP Workbench .................................. 126

5.8 Performance tricks ........................................................................... 126

5.9 Execution order ................................................................................ 126

5.10 Backup .............................................................................................. 126

5.11 Other sources of documentation ..................................................... 126

5.12 RAQ – Rarely asked questions ........................................................ 1275.12.1 Ooops… I need an old version of my CCP Workbench project? .. 1275.12.2 I need support what files to enclose? ............................................. 1275.12.3 I am desperately low on disk space!? ............................................ 1275.12.4 I have arrived at a system without any configuration files!? ......... 127

5.13 Predefined CCP blocks .................................................................... 1285.13.1 General ........................................................................................... 1285.13.2 CCP Disablements section ............................................................. 1295.13.3 CCP Fault alarm section ................................................................ 1335.13.4 CCP Fire alarm section .................................................................. 1365.13.5 CCP IO section .............................................................................. 1395.13.6 CCP Miscellaneous section ............................................................ 1445.13.7 CCP Pre-alarm section ................................................................... 1505.13.8 CCP Warning-alarm section ........................................................... 1515.13.9 Migrate from Salwico language to PLC ........................................ 152

Index ................................................................................................. 156

Table of contents

Configuration Manual 1 Introduction

5100355_FG5000_Configuration Manual_I1_EN_2012_C 1

1 Introduction

1.1 About this manualThis manual consists of a functional description of the configuration program,where the emphasis is put on how to work with the different program windows andhow to program the external controls using the Salwico language.

Chapter Introduction to the Configuration program, page 2 gives a briefintroduction to the configuration program.

Chapter Configuration Program Installation, page 3 helps you through theprogram installation.

Chapter How to make a System Configuration, page 5 describes how to make asystem configuration using the configuration program.

In chapter The Salwico Language, page 69 you will find a complete descriptionof the Salwico language commands and examples on how to use them.

In chapter The CCP Workbench, page 117 you will find a description of the CCPWorkbench and how to use it.

Section Predefined CCP blocks, page 128 describes the predefined CCP blocksdelivered as standard with the CCP fire alarm system.

We also recommend that you read the Fire detection system User Guide.

This manual has been reviewed for program version 1.6.0.

1.2 Symbols used in the manualDANGER!Risk of serious or fatal injury to the user, and/or severe damage to the product, ifthe instructions are not followed.

WARNING!Risk of personal injury and/or damage to the product if the instructions are notfollowed.

CAUTION!Risk of minor or moderate personal injury. Risk of equipment damage, loss of data,extra work, or unexpected results, if the instructions are not followed.

NOTE!Note symbols alert you to important facts and conditions.

Hint!Tip symbols direct you to specific instructions, such as where to find additionalinformation and tell you how to perform a certain operation in an easier way.

1 Introduction Configuration Manual

2 5100355_FG5000_Configuration Manual_I1_EN_2012_C

1.3 Introduction to the Configuration programThe configuration program is especially designed for creating a systemconfiguration file for a fire detection system. Before a fire detection system can beused, it must be both physically and functionally configured.

The configuration program is designed to run on a computer that can supportMicrosoft Windows NT, XP, 2000, Vista or Windows 7.

Update all software to the latest version to ensure correct function.

Configuration Manual 2 Configuration Program Installation


2 Configuration Program Installation

2.1 Chapter OverviewThis chapter describes the system requirements for using the program, installingthe configuration program, and running the program.

2.2 System RequirementsMinimum system requirements:

• Pentium 200

• Windows NT, XP, 2000, Vista or Windows 7

• 128 MB RAM

• 20 MB available hard disk space

• CD drive(CD drive only required if a program disc is used during installation. The setupfiles for the configuration program can also be downloaded.)

• USB or Ethernet port(Ethernet only required when configuring Control M X)

2.3 Installing the Configuration programTo install the configuration program, start Microsoft Windows and follow thisprocedure:

1 Obtain the program and locate the CCP Tools setup file.

2 Run the installer program and follow the instructions.

2.4 Running the Configuration programTo start the configuration program, follow the procedure below:

1 Start the program from the shortcut in either the start meny or on thedesktop.

2 The program starts and the window, as shown in the figure below, opens.

2 Configuration Program Installation Configuration Manual


Figure 1. Start window

The Configuration program and all application windows are explained in chapterHow to make a System Configuration, page 5.

2.5 Exit the Configuration program

1 Choose File in the main menu.

2 Select Exit in the file menu.

3 If you have changed a parameter in theConfiguration program, the program willask you to save the changes (unless theyhave already been saved). The savedconfiguration file will have the extension.ccp.

Do not use a filename withmore than 64 characters. Thisis due to restrictions of thetransfer protocol which doesnot allow large filenames. Thefile name will be concatenatedif the length is above 64characters.

Configuration Manual 3 How to make a System Configuration


3 How to make a System Configuration

3.1 Chapter overviewThis chapter describes creating a system configuration and downloading theconfiguration file to a fire detection system. The basic structure of theconfiguration program is the six main application windows: Options, User Access,Zones, Show/Control, System Bus, Cause/Effect and Central module tree. Whenmaking a configuration file, you can interrupt at any time, save the configuration tofile and continue later.

3.2 Functional Description

3.2.1 Section overviewIt is easier to work with the Configuration program once you know how thedetection system functions. The following section gives you a brief description ofthe system functions and the configuration program function.

3.2.2 The Fire Detection SystemA fire detection system is defined before it is used.

• PhysicalWhich kind of modules, detectors, etc. does the system consist of? The physicalconfiguration is defined to achieve fault supervision of the different systemcomponents such as zones, loop units, modules, etc. The system configurationmust be changed if the physical configuration is changed.

• FunctionalHow do you want the system to function? Is it an industrial or a marine system?Which zone will each detector belong to?

• Supplementary textEach system unit can be assigned descriptive text that explains the unit'slocation. Descriptive text is displayed on the control panel.

• I/ODefines how the inputs and outputs of the system react. For example: “Bells ondeck 3 are activated when there is a fire alarm in zone 4”.

3.2.3 The Configuration ProgramThe configuration program is divided into six functionally and well-defined mainapplication windows; Options, User access, Zones, Show/Control, System Bus,Cause/Effect and Central module tree. These windows are used to define the firedetection system both physically and functionally. After the configuration has beenperformed, theMain menu is used to manage a configuration file, to load a fileinto the program, and to save a configuration file update.

The modules are defined by entering different settings. Modules are defined one ata time. Information about the modules can be found later in this chapter.

3 How to make a System Configuration Configuration Manual


The Options window includes information about the current configuration file andtext fields in which the name and reference of the project is entered. Give theinstallation a specific name to make it easier to document each installation. Anumber of other global system settings can be set from the options window: marineor industrial installation, language, revision history, etc.

The User Access window is used to handle new and existing users of the firedetection system.

In the Zones window, there is a list of all zones defined in the system. It is possibleto name the zones.

In the Show/Control window, modules and zones are dedicated to groups, andgroup status for the control modules is defined.

The System Bus window is used to change the system bus settings.

The Cause/Effect window is used to switch between Salwico Language and PLC.

In the Central window, the centrals are defined physically and functionally.Modules and Salwico Language programs are added and defined in the central.

The physical configuration handles the definition of centrals, serial communicationports, zones, loops and loop units, and supplementary texts.

The functional configuration defines how the inputs and outputs of the systemshould react. The commands are written in the Salwico language, as described inthe chapter The Salwico Language, page 69.

When creating the configuration file, the system is built up “from the inside out”.Below is a rough description of the order in which to perform the configuration:

1 Add the central.

2 Add the modules and define them.

3 Complete the Zone window.4 Fill in the Salwico Language window including Salwico commands.

5 Perform the grouping in the Show/Control window.

3.3 The Program Main Window

3.3.1 About the Main windowThe main window, as shown in the figure below, is displayed when you start theprogram and it is from here that you select the application windows you want towork with. Use the main window when you want to update, load or save aconfiguration file.



Figure 2. The main window

The name of the current configuration file is displayed at the top of the window.

The parts in the main window are:

• The main menu

• The toolbar

• The module tree view

• The space for module editor boxes

Below is a brief description of each part.

3.3.2 Main menuThe main menu provides commands to save a configuration file and copy texts inthe configuration program.

Figure 3. The main menu

The main menu includes:

• The File menu

• The Edit menu

• The Command menu

• The Help menu



3.3.3 File menu

Figure 4. The file menu

New: Create a new configuration file.

Open: Open an existing configuration file.

Save: Save the current configuration file.

Save as: Save the current configuration file under a new name.

Import from Excel: Import loop configuration data from an Excel file. For moreinformation, refer to Importing Loop Module Information, page 61.

NOTE!The imported data replaces loop information already entered into the configurationprogram.

Extended Panel Text: Extended panel text can be used to define custom texts forindividual panels in the CCP Fire Detection System. For more information, refer toDefining Extended Panel Text, page 63

• Export to Excel

• Import from Excel

• Remove All Texts

Recently used file list: Displays up to eight of the most recently usedconfiguration files.

Exit: Closes the current configuration file and exits the programme.



3.3.4 Edit menu

Figure 5. The edit menu

Undo: Undo the latest command.

Cut: Cut out marked text and add it to the clipboard.

Copy: Copy marked text to the clipboard.

Paste: Paste text from the clipboard into the selected field.

Delete Module: Delete the selected central, module or Salwico Language sheetfrom the module tree.

3.3.5 Command menu

Figure 6. The command menu

Verify Configuration: The program will verify the entire configuration file toensure that there are no faults or conflicts. If any faults are discovered, an errormessage is generated, as shown in the figure below.

Figure 7. Example error message

Launch CCP Workbench: The menu alternative becomes available if CCPWorkbench PLC, and a project directory has been chosen in the Cause/Effectwindow.



3.3.6 Help menu

Figure 8. The help menu

About: Displays the version number of the configuration program.

3.3.7 Tool bar

Figure 9. The tool bar

The tool bar buttons are short cuts to commands found in theMain menu.

The New, Open and Save commands are found in the File menu.

The Delete Module, Cut, Copy, Paste and Undo commands are found in the Editmenu. These commands can also be executed through keyboard short cuts, asshown in figure The edit menu.

The Verify Configuration and Launch CCP Workbench commands are found inthe Command menu.

3.4 Options WindowIn the options application window, as shown in the figure below, specify basic dataabout the installation, such as the installation name and reference number.



Figure 10. The options window for marine installations

Figure 11. The options window for industrial and tranport installations



Configuration file information:

Revision history is a free text field used to enter revision history information, suchas date of original installation, installer company, date of updates, changes made inthe configurations and by whom, etc. Please enter all data you think is ofsignificance for engineers.

Saved in format: Information about the format that the configuration file is savedin.

Created by: Information about who or which company that created theconfiguration.

Saved at: Information about the time and date of the latest update of theconfiguration file.

Build: A running number telling you how many times the file has been updated(e.g. saved).

Global system settings:

Makers label: Select a label or write an optional text that will be shown in thecontrol panel’s text display.

Installation type: Choose whether the installation is a marine, industrial ortransport type. This affects how the system will function to comply with thedifferent regulations for marine, industrial and transport applications.

Language: Choose from available languages: English, Swedish, Danish, EnglishNon Fire, Norwegian and Chinese. The English Non Fire alternative implies thatthe system is used for patient alarms instead of fire alarms.

Time Zone: Select the desired geographical time zone or GMT time zone from thedrop down list.

NMEA update interval: Specify the time interval with which the systemautomatically sends a total system status update on all serial-ports defined withNMEA protocol.

The detailed configuration of serial outputs is made under each module in thecentral.

Max disablement time: By entering a time value in this field, the alternative“permanent disablement” in the control panel under menu » 3. Disablements willbe replaced by an alternative with the entered disablement time.

NOTE!TheMax disablement time setting affects permanent disablements for 'Zones' ,'Detectors & Manual Call Points' and 'Alarm Delay'.No other disablements are affected (such as Alarm Transfer, Alarm Device,External Controls or commands entered in Cause/Effect sheets).

Buzzer:When the checkbox is ticked, the buzzer in the panel is turned off whenthe door/lock is open.



WARNING!When the checkbox is ticked, the central will not comply with the EN-54 firestandard.

Customer Ranges: Select the desired cusomer ranges for loop devices from thedrop down list.

Customer Logo: Selects a logo that will be displayed on the standby home viewscreen. This function requires a security code to be unlocked.

3.5 User Access Window

3.5.1 About the User Access WindowSystem users are managed in the user access window, as shown in the figure below.System users can be listed, added and deleted.

Figure 12. The User Access window

3.5.2 Adding a new userClick in the fields and enter the following information:

1 Enter the name of the user.

2 Choose a unique 4-digit password.

3 Enter an access level for that user.Detailed information about the available access levels are found in the UserGuide.

4 Press Enter.

The new user is added to the user list.



3.5.3 Modifying an existing userJust click in the field you want to edit.

3.5.4 Deleting a user

Figure 13. User list: Delete user

1 Click on the grey field to the left of the useryou want to delete, as shown in the figureabove.

2 Press Delete. A dialogue box opens.

3 Confirm by clicking OK in the dialoguebox.

3.6 Zones WindowIn the zones window, as shown in the figure below, you will find a list of alldefined zones in the fire detection system. Zones are defined in the Centraldescribed later in this chapter. From here it is possible to add text that names anddescribes the zones.



Figure 14. The Zones window

Description of columns and buttons in the Zones window:

Zone: The number of the zone shown in the control panel in case of a fire.

Text 1: Free text field (max. 37 characters - word spaces are counted ascharacters). This text will be shown at the control panel below the fire zoneinformation in case of a fire.

Text 2: Additional free text field (max 37 characters - word spaces are counted ascharacters). Shown in the same way as Text 1.

Information Window:When you click on one of the zones in the zone list, theinformation window will show in which central and on which module and addressthe zone is defined.

3.7 Show/Control WindowEach module and zone in a fire detection system can be dedicated to one or severalgroups. For each control module, it is possible to define which groups it shouldcontrol and/or display.

If any control module in the system is missing or broken for some reason, all theother control modules and repeater modules will automatically get full access toeverything.



Figure 15. The Show/Control window

Description of fields and buttons in the Show/Control window:

Groups

In the Groups field it is possible to add and delete groups, and to determine whichzones and modules should belong to each group.

Number: Choose which group to handle.

Text: Free text field (max 37 characters - word spaces are counted as characters)that describes the group.

New: Create a new group. As shown in the figure below, specify the group numberin the dialogue box (only vacant numbers are available in the list) and describe thegroup in the Text field.

Figure 16. New Group dialogue box

Delete: Delete the group with group number specified in the Number field.



Edit: Edit a group. As shown in the figure below, specify a new group number inthe dialogue box if desired (only vacant numbers are available in the list) or givethe group a new description in the Text field.

Figure 17. Edit Group dialogue box

Zones defined in system: Lists all zones in the system.

Modules defined in system: Lists all modules in the system.

Zones in group: Lists the zones in the group selected in the Number field.

Modules in group: Lists the modules in the group selected in the Number field.

Add -> (Two buttons with similar function): Adds a zone or a module to the groupselected in the Number field. The zone or module must be marked in theZones/Modules defined in system list.

<- Remove (Two buttons with similar function): Removes a zone or a module fromthe group selected in the Number field. The zone or module must be marked in theZones/Modules in group list.

Group Management

In the Group Management field it is possible to set whether the groups should becontrolled or only presented, or neither controlled nor presented on the controlmodules.

Select Control Module: Choose which control module to handle.

All groups: Shows all groups defined in the system. Click the group or groups youwant to handle.

• The Present button puts the selected groups in the Groups presented only list(and removes it from the Groups controlled list if present in that list).

• The Control button puts the selected group in the Groups controlled list (andremoves it from the Groups presented only list if present in that list).

• The Delete button deletes the selected group or groups from the system.

Groups presented only: A list of the groups that will be presented but notcontrolled from the specified control module in the Select Control Module field.Click the group you want to handle.

• The Control button puts the selected group in the Groups controlled list andremoves it from the Groups presented only list.



• The Remove button removes the selected group from the Groups presentedonly list.

Groups controlled: A list of the groups that will be controlled from the controlmodule specified in the Select Control Module field. Click the group you want tohandle.

• The Present button puts the selected group in the Groups presented only listand removes it from the Groups controlled list.

• The Remove button removes the selected group from the Groups controlledlist.

Guidelines for Group Management

By default (as determined by the configuration program), all modules and zonesbecome dedicated to all groups that exist in the moment that the module or zone isadded. Group 1 is created automatically when the first module is added.

1. Read section Description of fields and buttons in the Show/Control windowabove.

2. Create a group using the New button.

3. Use the Add or Remove buttons to specify the content of zones and modules inthe selected group.

4. In the Group Management field, select a Control module to handle.

5. Choose which groups to be presented or controlled by the selected controlmodule.

NOTE!Only zones in a group can be set up in group management to present/control alarmsfrom the zone.Only modules in a group can be set up in group management to present/controlfaults from the module (not zones).

3.8 System Bus Settings WindowSystem Bus is the communication bus used for connecting multi-central systems. Aprimary and secondary System Bus can be configured.



Figure 18. The System bus settings window

Description of fields and buttons in the System bus settings window:

Systembus type: Choose the system bus type for the primary and secondary side.Choose from None, Ethernet, Serial channel 3 or Serial channel 4.

NOTE!If a serial channel is used all control modules on the same side must have the sameserial channel configured as system bus in their serial port settings

Broadcast address: Set the broadcast address for the primary and secondary side.

Broadcast port: Set the port number for the primary and secondary side.

3.9 Cause/Effect WindowSwitch between Salwico Language and CCP Workbench PLC in the Cause/Effectwindow.

For CCP Workbench PLC the following options are available:

Launch CCP Workbench: This option starts CCP Workbench, which is a separateprogram that comes with the installation of CCP Tools, to create PLC controllersfor the system. These parameters are then included in the configuration file when itis saved. When the CCP Workbench is started, it will automatically load theprojects chosen in the selected project directory. (If there are no projects in thedirectory you get the question if you want to create a new project.)



Hint!Please refer to the CCP Workbench Handbook found in the CCP Workbenchprogram Help menu.

Export project files from configuration: This is a so-called advanced operationand requires that you have saved the PLC controllers in a configuration file onceand then re-opened it in the CCP Configuration program. Use the LaunchWorkbench button to extract a project file for the CCP Workbench based on theexisting configuration file, which is then copied to the chosen directory path.

NOTE!The Salwico Language is specified central wise while PLC is specified systemwise.

Figure 19. Cause/Effect window

3.10 Modbus TCP/IP WindowConsilium fire detection system has the capability of becoming a Modbus RTUSlave. The external device must be configured as a master.

The function is activated by setting serial channel 3 or 4 on any type of controlmodule to ‘MODBUS RTU’ in the Serial tab. Please refer to Serial Tab, page 33.

Serial channel 3 or 4 on the control module is running RS232 or RS485 dependingon how they are connected physically and what type of control module that is used.

NOTE!Modbus TCP/IP needs to be enabled from the Network tab for those controlmodules that should run Modbus. Select checkbox “Enable Modbus TCP/IP” asdescribed in Network Tab, page 41.



Figure 20. Modbus TCP/IP window, disabled

Switch between Disabled and Enabled in the Modbus TCP/IP window.

Figure 21. Modbus TCP/IP window, enabled

Every device on a loop has at least one zone number and address. Loop devices aredetectors, short circuit isolators, timers and digital inputs (address units, controlmodules). The Modbus module holds the status of the devices and prepares themfor Modbus interpretation using a cross reference translation table created andcompiled by the Consilium service engineer using “ComtesterLT.exe” and thendownloaded to the fire detection system.

Specification of CCP Modbus RTU Protocol and the cross reference file aredescribed in separate documents.

CAUTION!If a cross reference file for Modbus exists, the cross reference file overrides thedefault configuration and the default configuration is disabled!



3.11 Central

3.11.1 About the Central WindowIn the Central Window, as shown in the figure below, the central is physically andfunctionally defined. The physical configuration is where central modules, serialcommunication ports, zones, loops and loop units, and supplementary texts aredefined. The functional configuration defines how the inputs and outputs of thesystem should react. They are set in the Salwico Language window with theSalwico language described in chapter The Salwico Language, page 69, or in theThe CCP Workbench, page 117, (depending on the option selected in theCause/Effect window).

Figure 22. The Central Window

3.11.2 Adding a Central3.11.2.1 Adding a CentralWhen starting the program, a central called “Central 1” is added per default. If thecentral is removed or more centrals are required, add a new central following theinstructions below:

1 Place the cursor on Options, User Access, Zones, Show/Control, SystemBus or Cause/Effect in the module tree and click with the right mousebutton.

2 A dialog window Add central unit is shown. Click this.

3 A new central is added in the module window below the last central in thelist.

4 Enter information in the fields described below.



NOTE!There must always be a central with address 1 in a CCP System.

3.11.2.2 Description of the fields and buttons in the CentralwindowAddress: Give the central a unique address between 1-30. The program is preparedto handle several centrals.

Description: A free text field (max 37 characters) describing the central. The textwill be shown in the fault list when a “central no answer” fault is reported from thiscentral.

VIO Tab

Use the tab to handle custom faults and alarms for Central VIO. Salwicoexpressions can activate a particular central VIO which in turn can be used totrigger an associated alarm or fault according to the configuration.

The Central VIO defined here is used as input conditions for monitoring. Forexample, if an input is active, you can activate a Central VIO which then in turngenerates either a fault or an alarm. The condition of a Central VIO cannot bemonitored from another central as Central VIOs only communicates within thecentral there they are defined. But generated faults or alarms are spread throughoutthe system.

Figure 23. The Central VIO tab

Address: Select the Central VIO address (range 1-1000).

Type: Choose type Fault or Alarm for the Central VIO.

Text 1:A free text field (max 37 characters) describing the VIO. This text will beshown in case of a generated fault or alarm.

Text 2: Additional text field (max 37 characters) describing the VIO. Shown in thesame way as Text 1.

Summary Tab

Figure 24. The Central Summary tab

The Current consumption approximation field shows a current consumptionapproximation for the selected central.



Idle condition: The program automatically calculates expected working current innormal condition for the configured central. This value is approximate.

Alarm condition: The program automatically calculates expected working currentduring a fire alarm for the configured central. This value is approximate.

NOTE!Note that the assumptions are based solely on the number of modules in theconfiguration and that each module is assumed to have the below described setup.Idle condition: Control Modules consumes from 62 to 110mA depending onmodel, all other modules except Loop M consumes 20mA and finally the Loop Mis assumed to have 100 detectors resulting in a consumption of 75mAAlarm condition: Same consumtion as in idle condition with the followingadditions; Control Modules and Repeater Modules are assumed to have one activeoutput at 70mA, Relay M, IOM70 and IOM700 are assumed to have four activeoutputs, each consuming 80, 70 and 200mA respectively. Finally Loop M isassumed to have 33 active detectors consuming in total 10mA.

3.11.3 Adding ModulesAdd modules such as Control M X, Control M 4.3, Charger M, etc. according tothe procedure below. Configuration of the modules is described later in thischapter.

1 Click on the central you want to add modules to.

2 Use the right mouse button to get a list of the available modules to add.

3 Select the module you want to add.(The Mini Repeater M (MN400) can’t be added directly to the central, ithas to be added to a control module. For information see About MiniRepeater - MN400, page 60)

The modules is added in the module window under the central chosen in step 1.The modules will be given different default addresses. The default address dependson the module type, as listed in the table below. If the default address is alreadyoccupied, the module receives the next available address.

Table 1. Default addresses for modules

Module type: Default address:Control M 4.3Control M 2.2 1 - 8

Control M X 3 - 8ChangeOver M Ext 9 - 10Loop M XLoop M X Slave 11 - 49

I/O M 70 50 - 63I/O M 700 64 - 71Relay M 8 72 - 89Charger M 90 - 95Mux M 16 96 - 99



Module type: Default address:Repeater MMini Repeater MN400 100 - 115

Output Solenoid M 14 116 - 122Input Analogue M 0-20 122 - 125

3.11.4 Salwico Language window3.11.4.1 About the Salwico Language windowThe function of all inputs and outputs in the system are defined in the SalwicoLanguage window, as shown in the figure below. This section describes how toenter the commands into the editor. All information about the commands isprovided in The Salwico Language, page 69.

Figure 25. The Salwico Language window

3.11.4.2 Description of buttons and checkbox in the SalwicoLanguage windowAdd new Program: Creates a new Salwico Language statement sheet. It ispossible to add several Salwico Language sheets, for example to separate fire andsprinkler configurations. Each program can be individually named. See AddingSalwico Language sheets, page 26 later in this chapter for more information.

Compile All Programs: Compiles all Salwico Language sheets for the selectedcentral. The program will verify if the syntax is correct and that there are noconflicts if you have added more than one Salwico Language sheet (e.g., that thesame output has been used twice).



3.11.4.3 Adding Salwico Language sheets

1 Click the Add new Program button. A new Salwico Language sheet isadded in the module window. The Salwico Language sheet receives adefault name - the first sheet is named SL1.

2 Click on the sheet name and enter the Salwico Language information usingthe Salwico language commands as decribed in The Salwico Language.There is no limitation on how many characters you can print in one row.The sheet can be renamed by entering a new name in the Name field in theSalwico Language editor box.

3 When you have entered all commands, click on the Compile button in theSalwico Language editor box to verify that the syntax is correct (spelling,usage of intervals, etc.).

4 To add more Salwico Language sheets, click on Salwico Language in themodule tree window. Then repeat the procedure from step 1.

5 The Salwico Language sheets are saved in the document when you leavethe Salwico Language editor box and they are saved to the configurationfile when you exit the configuration program.

Figure 26. The Salwico Language editor box (with some example settings)

3.11.5 Configuring the Power Control Module -ChangeOver M Ext3.11.5.1 About ChangeOver M ExtThe ChangeOver M Ext is used to provide the fire detection system with power,monitor the supply sources and switch between them upon failure.



Figure 27. ChangeOver M Ext editor box

Description of the fields in the ChangeOver M Ext editor box:

Address: Enter an address for the ChangeOver M Ext. Each module in a fire alarmcentral should have a unique address between 1-125. Default address depends onmodule type. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the ChangeOver M Ext. Thistext will be shown in the fault list if a fault is reported from the ChangeOver MExt.

3.11.5.2 Outputs TabThe ChargeOver M Ext is equipped with 4 outputs. They are configured from theoutputs tab in the ChangeOver M Ext editor box, as shown in the figure below.

Figure 28. The outputs tab in the Change Over M Ext editor box

Hint!For information about output configuration, see Outputs Tab, page 34 inConfiguring the Control Module - Control M 4.3.



3.11.5.3 Supervision Tab

Figure 29. The Supervision tab in the ChangeOver M Ext editor box

Description of the fields in the Supervision tab:

Mains Input: Disable or enable fault generation from the Mains input if a powerloss occurs.

Emergency Input: Disable or enable fault generation from the Emergency input ifa power loss occurs.

Secondary backbone channel (B): Disable or enable fault generation from thesecondary backbone channel (B). Disable the fault generation if only the primarybackbone channel (A) is connected to this module.

3.11.6 Configuring the Power Control Module - ChargerM3.11.6.1 About Charger MThe Charger M is the power supply module in the fire detection system.



Figure 30. Charger M editor box

Description of the fields in the Charger M editor box:

Address: Enter an address for the Charger M. Each module in a fire alarm centralshould have a unique address between 1-125. Default address depends on moduletype. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the Charger M. This text willbe shown in the fault list if a fault is reported from the Charger M.


Figure 31. The Supervision tab in the Charger M editor box



Description of the Options field in the Supervision tab

Charger M monitors the voltages and current levels of all the power flows in andout of the module.

Disable battery Supervision: If there are no batteries connected to the Charger M,select this alternative to avoid the display of messages concerning a missingbattery.

Disable battery charge: Select this alternative if you do not have any batteriesconnected to the Charger M. Also used if an external 24VDC supply is connected.

No earth fault supervision: Inhibits generation of earth-fault.

Net absent generates a warning: Define if a defective 220VAC power supply willgenerate a warning.

Net absent fault generation time X min: You can enter a time here after whichthe system should give a fault indication. If set to 0 the fault indication is disabled.

Battery circuit resistance: This unitless value is proportional to the internalresistance of the battery. The corresponding value of the internal resistance of thebattery is measured twice an hour and compared to the entered value. If themeasured value is greater than the entered value a battery fault will be generated. Ifset to 0 the internal resistance measurement is disabled.

NOTE!Normally the default value for Battery circuit resistance should not be changed.

Max input current (A): The maximum current input in total that the moduleshould deliver to the system. This includes both backbone channels, the battery(when charging) and the output. If exceeded a power limit fault will be generated.

Example for Max input current (A):

• If one PSU M AC/DC 5A module is used, choose 5A

• If two PSU M AC/DC 5A modules are used in pair, choose 10 A.

Max battery size (Ah): Choose the max battery size.

Description of the Power Management field in the Supervision tab

PSU 1: Enable or disable PSU 1 and choose the type of monitoring, None, PSU orChange Over.

PSU 2: Enable or disable PSU 2 and choose the type of monitoring, None, PSU orChange Over.



Figure 32. Charger M can be set to supervise PSU or Change Over modules

Description of the Secondary backbone channel field in theSupervision tab


3.11.6.3 Outputs TabThe Charger M is equipped with one output. It is configured from the outputs tab inthe Charger M editor box, as shown in the figure below.

NOTE!If DIP switch 10 is used the output will always be active. In this case the outputmust be set to "not used" in the configuration to avoid a configuration fault in thesystem.

NOTE!If the DIP switch 10 is used, the output shall not be used in the control program!

Figure 33. The outputs tab in the Charger M editor box

Max Output Current (mA) andMax Backbone Current (mA): Defines themaximum current consumption allowed on the output and on both backbonechannels. If exceeded a power limit warning will be generated.




3.11.7 Configuring the Control Module - Control M 4.33.11.7.1 About Control M 4.3The Control M 4.3 is the control and/or display unit in the fire detection system.

Figure 34. Control M 4.3 editor box

Description of the fields in the Control M 4.3 editor box:

Address: Enter an address for the Control M 4.3. Each module in a fire alarmcentral should have a unique address between 1-125. Default address depends onmodule type. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the Control M 4.3. This textwill be shown in the fault list if a fault is reported from the Control M 4.3.

3.11.7.2 Logging Tab

Figure 35. The Logging tab in the Control M 4.3 editor box

Description of the fields in the Logging tab:



Select events to print: Select which events that will be sent to the printerconnected to this Control M 4.3.

Hint!Printers are defined in the Serial tab.

3.11.7.3 Serial TabThe Control M 4.3 is equipped with four serial communication ports, where thefirst two ports are dedicated to the backbone and the other two ports areconfigurable, as shown in the figure below.

Figure 36. The Serial tab in the Control M 4.3 editor box

Description of the columns in the Serial tab:

No: Fixed number for the serial communication ports.

Type: This column describes the type of serial communication port and is noteditable. The type is always one or a combination of RS232, RS422 and/or RS485.

Protocol: Select the applicable serial protocol for the communication ports byclicking in the Protocol column, as shown in the figure below.

Figure 37. A list of the available serial protocols

Protocol alternatives:

• Not used: The port is not used.

• Extension bus: Internal communication between the modules on the extensionbus connected to this control module.

• System bus: Communication between centrals. For further information of serialchannel 3 and 4, see System Bus Settings Window, page 18

• Printer: Communication to the printer.

• MiniPrinter: Communication to the Miniprinter.

• NMEA: NMEA protocol. The protocol is described in a separate document.

• ESPA444: ESPA444 protocol for paging systems. The protocol is described in aseparate document.



• MiniRepeater (MN400): The channel will be used for MN400 modulesconnected to this control module.

• Modbus RTU: Protocol for supervision and control of the system. The protocolis described in a separate document.

• CSProt6: A Consilium specific protocol. The protocol is described in a separatedocument.

• EMU350/EMU798/ChangPing/Sardinia/Dalian: Train-specific protocols usedon trains. The protocols are described in separate documents.

• Aquasys: Aquasys system sensor protocol.

• Clocksync (UTC)/Clocksync (Local): Protocols to activate Ship ClockSynchronisation.

Baud: Choose the applicable baud rate for the communication port by clicking inthe baud column, as shown in the figure below.

Figure 38. A list of the available baud rates

Setup: Choose the applicable setup for the communication port by clicking in thesetup column, as shown in the figure below.

Figure 39. The setup list

Text 1: A free text field (max 37 characters) describing the communication port.This text will be shown in the fault list in case of a fault on the communicationport.

Text 2: Additional text field (max 37 characters) describing the communicationport. Shown in the same way as Text 1.

3.11.7.4 Outputs TabThe Control M 4.3 is equipped with two outputs. They are configured from theoutputs tab in the Control M 4.3 editor box, as shown in the figure below.



Figure 40. The Outputs tab in the Control M 4.3 editor box

Description of the columns in the Output tab:

No.: A fixed number for the outputs on the Control M 4.3.

Type: Select an appropriate category for each defined output by clicking in thecategory column, as shown in the figure below. The categorization allows thesystem operator to disconnect whole categories of outputs with one singlecommand.

NOTE!If you choose category “Firm output”, select “Not used” in the Active column.

Figure 41. The list showing output categories

Active: Choose one of the three alternatives by clicking in the Active column, asshown in the figure below.

Figure 42. The list for selecting activation method

Active alternatives:

• Not used: The fire detection system will not use this output.

• Active high: The output is normally inactive and will be activated uponactivation.

• Active low: The output is normally active and will be inactivated uponactivation, e.g., used with failure outputs. If the system goes down the outputwill be triggered.

Setup: Choose the applicable setup for the communication port by clicking in thesetup column, as shown in the figure below.



Figure 43. The setup list

Text 1: A free text field (max 37 characters) describing the output. This text will beshown in the fault list in case of a fault on the output.

Text 2: Additional text field (max 37 characters) describing the output. Shown inthe same way as Text 1.

3.11.7.5 Custom Keys TabThe Control M 4.3 is equipped with three programmable custom shortcuts, F1-F3.They are configured from the custom keys tab in the Control M 4.3 editor box, asshown in the figure below. The configuration of the LED indications on the customshortcuts is performed in the Salwico Language sheet.

Use the command: CU x.y LED z, to define LEDs for shortcuts. Each custom keyis reflected in a SYSTEM VIO which you then can use as input conditions tocontrol the LEDs with the command: CU x.y LED z.

Figure 44. The Custom keys tab in the Control M 4.3 editor box

Key: Choose which custom shortcut F1, F2 or F3 to configure. All three shortcutscan be configured independently of each other.

Function: Select how the three customer-defined buttons on the Control M 4.3should perform.

Function alternatives:

• Not used: The custom shortcut will not have any function.

• Set: The custom shortcut will activate the programmed action associated withthis custom shortcut. The action will only be performed once. The configurationof the user buttons is performed in the Salwico Language module.

• Maintained: When the custom shortcut is pressed, the pre-programmed actionassociated with this user button will be performed and will stay active until theuser button is pressed again.

• Menu: When the custom shortcut is pressed, a customer-specific menu is shownin the text display. The customer-specific menu is configured in the User Menufield displayed when Menu is selected.



Menu Text: This text is shown in the customer-specific menu defined for theselected custom shortcut.

Access level: Select which access level the user must have in order to use thecustom shortcuts. Individually programmable for each custom shortcut.

Copy setup from: Choose a module to copy the setup from.

3.11.7.6 Configuring the User MenuConfigure the menu, which will be shown in the text display if the custom shortcutis pressed. The User Menu field, as shown in the figure below, is only displayed ifthe Function is set to Menu.

Figure 45. The User Menu

Each row marked as Used in the User Menu will be associated with a SYSTEMVIO x statement in the Salwico language. It is possible to have up to 1000 VIOs inone fire detection system. For example, if VIO is set to 2 and the Used checkbox isenabled, the VIO 2 statement in the Salwico language will be associated with thisUser Menu row. Further, the menu text to be shown in the custom menu isspecified by the Text – VIO inactive and Text – VIO active columns. The actionthat should be triggered when the User Menu row is selected from the custommenu is configured in the Salwico Language module described previously in thischapter.

Description of the columns in the User Menu:

Menu row: The row number.

Used: Indicates if the menu row should be displayed if the custom shortcut ispressed.

VIO: Selects which SYSTEM VIO to use.

Text – VIO inactive (default): Defines the texts to be shown in the menu when theSYSTEM VIO is cleared.

Text – VIO active: Defines the texts to be shown in the menu when the SYSTEMVIO is set.

Indication only: Tick the checkbox to de-activate the buttons. It is then notpossible to change status from the menu.



3.11.7.7 I/O Tab

Figure 46. The I/O tab in the Control M 4.3 editor box

Description of fields and columns in the I/O tab:

Output Voltage: Set the voltage on the two outputs.

Max Current for each Terminal: Set the maximum current on the outputs inorder to protect external equipment.

No: A fixed number for the two loops on Control M 4.3.

Type: Select the type of input or output by clicking in the type column.

Figure 47. The list showing Type categories

There are several input/output categories, as shown in the figure above. Select anappropriate category for each input/output you define. The categorization allowsthe system operator to disconnect whole categories of input/outputs with a singlecommand.

• Not used: The loop is not used.

• Zone: Normal operation with fire alarms.

• General Input: The loop is used as a digital input and can be programmed fromthe Cause/Effect module.

• Fault input: The loop is used as a digital input. A fault appears when the loop isactivated.

• General output: The loop is used as a digital output and can be programmedfrom the Cause/Effect window.

• Door output

• Bell output

• Fire output

• Fault output: The loop is used as a digital output. A fault appears when the loopis activated.

• Ventilation output



• Indication output

• Alarm Trans. output: A supervised output for signalling that a fire has occurred.

• Firm output

Zone: Select which zone the input shall belong to. This value is only used if Typeis set to “Zone”. The zone number specified appears in the Zones window, wheretexts describing the zones can be added.

The zone numbers should be in the interval of 1-65534. The zone number will bedisplayed at the control panel if a fire or fault is reported from the loop. The zonenumber must be unique.

Alarm 1: Enter the lower level for the Alarm 1 interval (in mA), as shown in thefigure below. When the current passes this value, the input status changes frominactive to active.

Alarm 2: Enter the lower level for the Alarm 2 interval (in mA), as shown in thefigure below. This is also the upper level for the Alarm 1 interval. Note: Alarm 2 isonly active if Type is set to “Zone”.

Break Level: Set the current level under which a cable break fault will begenerated. To avoid cable break fault messages, set the value to 0. For 1 or 2 mAthe suitable resistance level is 10 kOhm.

Short level: A limit for short circuit error. The current output from the zone will belimited to the value specified in theMax Current for each Terminal field. Ifmany alarms are triggered, causing the current to reach theMax Current for eachTerminal value, the voltage on the input will decrease. Based on this voltagedecrease, the system calculates a fictive current value, which is compared with theShort level value. A fault signal is sent if the fictive value exceeds the Short levelvalue.

This is also the upper level for the Alarm 2 interval, if Type is set to “Zone”, asshown in the figure below. For “Zone” the Short level can be adjusted (defaultvalue 50 ohm).

Figure 48. Schematic diagram over conventional loop current (default values) when Type is set to“Zone”.

If Type is set to “General Input” or “Fault Input” there is no Alarm 2, as shown inthe figure below. The Short level for “General Input” and “Fault Input” is 50 ohm.If you want to avoid short circuit error at closed input, set the Short CircuitCurrent to 70 mA.



Figure 49. Schematic diagram over conventional loop current (default values) when Type is not set to“Zone”.

Additional Settings: For each input/output there are six additional options, wheremore than one option can be selected, as shown in the figure below.

Figure 50. The list for additional settings

Setup options:

• Anti-phase: The output will be in anti-phase in relation to the synchronizationpulse, if such a pulse is available.

• Synchronized: The output will follow the synchronization pulse, if such a pulseis available.

• Break Supervised: Activates the cable break supervision. Signals a fault in caseof a break.

• Short Supervised: Activates the short circuit supervision. Signals a fault in caseof short circuit.

• GA-morse: If activated, this output will be active when the ’GeneralAnnouncement’ signal is activated. The latter is a hardware signal activated viaCharger M.

• X-fire: If activated, this output will be active when the ‘X-Fire” signal isactivated. The latter is a hardware signal used as a last resort if a module detectsan alarm condition and is unable to communicate with any other modules.

Text 1: A free text field (max 37 characters) describing the location of the loopunit. This text will be shown in the fault list if a fault is reported from the loop unit.If Type is set to “Zone”, this text must be entered in the Zones window, at thecorresponding zone number. Otherwise, it can be entered directly in the Text 1field.

Text 2: An additional free text field (max 37 characters) describing the location ofthe loop unit. Shown in the same way as Text 1. If Type is set to “Zone”, this textmust be entered in the Zones window, at the corresponding zone number.Otherwise, it can be entered directly in the Text 2 field.



3.11.7.8 Network Tab

Figure 51. The Network tab in the editor box

Interface information field

Name: Choose from the available interface names.

Type: Choose the type of interface.

Interface settings field

Adress: Set the IP-network address.

Netmask: Set the netmask.

Gateway: Set the gateway.

NOTE!All three address fields must be set in order to activate the static IP.

VNC field

Enable Remote Access: Enable the ability to remotely log in to the module usingVNC. A server is started on the control module that allows connections fromremote clients.

Debug IP field

Enable Debug IP: Check the box to enable Debug IP.

CAUTION!For advanced users only and should normally be activated. The debug IP address isderived from the module's hardware address.

Modbus TCP/IP field

Enable Modbus TCP/IP: Check the box to enable Modbus TCP/IP (as describedin Modbus TCP/IP Window, page 20).




Figure 52. The Supervision tab in the editor box



3.11.7.10 kProt TabThere are some prerequisites on the Fire detection system for kProt (KongsbergProtocol) to work:

• kProt is only supported in single-central Fire detection system.

• kProt is only supported by the Control panel M 4.3, Control panel M 2.2 andControl M X modules. (Note that control modules in the Fire detection systemalways act as kProt slaves and that equipment connected to the Fire detectionsystem always acts as kProt masters.)

• A kProt slave can communicate with a maximum of five kProt masters.

NOTE!No more than 3 Loop M X modules can be used in the same system if the kProtprotocol itself shall support SIL-2 according to IEC61508 with regard tocommunication.

The kProt communication protocol is described in a separate document.

Figure 53. The kProt tab in the editor box



Enabling kProt

Select the box called ‘Enable’ in order to activate the protocol.

The kProt configuration requires a slave port and at least one master.

Configuring a kProt Slave Port

The Slave Port defines the port the kProt slave uses for incoming messages andshall be used by all masters in order to communicate with the slave. Valid portnumbers are within the range 1024-65536. (28101 is the default kProt Slave Port.)

Configuring a kProt master

To add a master to the configuration, click the first row of the list and fill data inthe following order. (Press Enter after each line.)

Slave ID: The ID that the slave will use when communicating with the master.

Master ID: The ID that the master will use when communicating with the slave.

Master IP Address: The column must contain the IP-address of the kProt master.This address is used by the kProt slave when it responds to queries from the master.Dynamic IP addresses are not supported; each master must be assigned a staticIP-address.

Master Port: The column must contain the port of the kProt master.

Each master must have a unique ID while the Slave ID can be unique or the samefor all masters. It is possible to add masters with the same IP address but if in thatcase different port numbers must be used in order to assure that the master addressis unique.

CAUTION!The kProt slave follows the configuration strictly, messages will be dropped by theslave if other IDs than the ones specified are used and messages will be sent to thewrong destination if incorrect IP-addresses or ports are filled in.

An additional IP-address

It is also possible to configure the Control Module with an additional IP-address.

To set an additional IP-address:

1. Select tab Network for the control module.

2. Fill in the static IP-address, subnet mask and default gateway.

3.11.8 Configuring the Control Module - Control M 2.23.11.8.1 About Control M 2.2The Control M 2.2 is a control and/or display unit in the fire detection system,similar to the Control M 4.3. Control M 2.2 lacks custom keys compared to ControlM 4.3 but has otherwise the same type of functionality.



Refer to the section Configuring the Control Module - Control M 4.3, page 32for details on how to configure a control module.

3.11.9 Configuring the Control Module - Control M X3.11.9.1 About Control M XThe Control M X is a control unit in the fire detection system, in some wayssimilar to the Control M 4.3. Control M X only has two output channels (no inputchannels) and lacks custom keys compared to Control M 4.3 but has otherwise thesame type of functionality.

Refer to the section Configuring the Control Module - Control M 4.3, page 32for details on how to configure a control module.

3.11.10 Configuring the Input Analogue Module 0-20 -IAM0203.11.10.1 About Input Analogue Module 0-20This module is currently not implemented.

3.11.11 Configuring the I/O Module - I/O M 703.11.11.1 About I/O M 70The I/O M 70 is a connection module for up to eight conventional detector zones. Itcan also be used for digital input.

Figure 54. I/O M 70 editor box

Description of the fields in the I/O M 70 editor box:



Address: Enter an address for the I/O M 70. Each module in a fire alarm centralshould have a unique address between 1-125. Default address depends on moduletype. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the I/O M 70. This text willbe shown in the fault list if a fault is reported from the I/O M 70.

3.11.11.2 I/O Tab

Figure 55. The I/O tab in the I/O M 70 editor box

For description of fields and columns in the I/O tab, refer to I/O Tab, page 38 forControl M 4.3.





3.11.12 Configuring the I/O Module - I/O M 7003.11.12.1 About I/O M 700The I/O M 700 has eight programmable I/O channels that can be used as eitherinputs or outputs.



Figure 57. I/O M 700 editor box

Description of the fields in the I/O M 700 editor box:

Address: Enter an address for the I/O M 700. Each module in a fire alarm centralshould have a unique address between 1-125. Default address depends on moduletype. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the I/O M 700. This text willbe shown in the fault list if a fault is reported from the I/O M 700.

3.11.12.2 I/O TabNOTE!If DIP switch 8 is used output 5-8 will always be active. In this case output 5-8must be set to "not used" in the configuration to avoid a configuration fault in thesystem.

Figure 58. The I/O tab in the I/O M 700 editor box



Description of fields and columns in the I/O tab:

Max Total Current:Maximum allowed total current output from the module.

No.: A fixed number for the inputs or outputs on the I/O M 700.

Type: Select the type of input/output by clicking in the Type column.

Figure 59. The list showing output type

NOTE!If the DIP switch 8 is used, output 5-8 shall not be used in the control program!

There are several input/output categories, as shown in the figure above. Select anappropriate type for each input/output you define. The categorization allows thesystem operator to disconnect whole categories of input/outputs with a singlecommand.

Hint!For a detailed description of each type see I/O Tab, page 38 for Control M 4.3.

Active: There are three alternatives to choose from by clicking in the activecolumn.

Figure 60. The list for selecting activation method

Active alternatives, as shown in the figure above:

• Active high: The output is normally inactive and will be activated uponactivation.

• Active low: The output is normally active and will be de-activated uponactivation (e.g., used with failure outputs). If the system goes down the outputwill be triggered.

Setup: For each input/output there are six additional options, where more than oneoption can be selected, as shown in the figure below.



Figure 61. The list for selecting setup

Setup options:

• Anti-phase: The input/output will be in anti-phase in relation to thesynchronization pulse, if such a pulse is available.

• Synchronized: The input/output will follow the synchronization pulse, if such apulse is available.

• Break Supervised: Activates the cable break supervision. Signals a fault in caseof a break.

• Short Supervised: Activates the short circuit supervision for an output. Signals afault in case of short circuit.

• GA-morse

• X-fire

NOTE!Only option Break Supervised is available if you selected an Input in the Typecolumn.

Text 1: A free text field (max 37 characters) describing the input/output. This textwill be shown in the fault list in case of a fault on the input/output.

Text 2: Additional text field (max 37 characters) describing the input/output.Shown in the same way as Text 1.







3.11.13 Configuring the Output Solenoid Module M 14 -OSM143.11.13.1 About Output Solenoid Module M 14This module is currently not implemented.

3.11.14 Configuring the Loop Module - Loop M X3.11.14.1 About Loop M XThe Loop M X is the connection module for an analogue addressable detector loop,as shown in the figure below.

As an option, it is possible to let the customer enter the Loop information in anExcel template and import this information into the configuration program. Theloop tab is then completed. For more information, see Introduction, page 61.

Figure 63. Loop M X editor box

Description of the fields in the Loop M X editor box:

Address: Enter an address for the Loop M X. Each module in a fire alarm centralshould have a unique address between 1-125. Default address depends on moduletype. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the Loop M X. This text willbe shown in the fault list if a fault is reported from the Loop M X.

3.11.14.2 Loop TabThe loop tab, as shown in the figure below, shows an overview of the loopconnected to this Loop M X.



Figure 64. The Loop tab in the Loop M X editor box

Description of the columns in the loop tab:

No.: A fixed number for the loop on this Loop M X.

Logical: Give the loop a unique number between 1-65534.

Connection: Choose one of the two alternatives by clicking in the Connectioncolumn.

Connection alternatives:

• Loop: Select this alternative if the detector loop is double fed, i.e. connected inboth ends to the Loop M X.

• Spur: Select this alternative if the detector loop is single fed, i.e. connected inone end only.

Text 1: A free text field (max 37 characters) describing the loop. This text will beshown in the fault list if a fault is reported from the Loop.

Text 2: An additional free text field (max 37 characters) describing the loop.Shown in the same way as Text 1.

3.11.14.3 Configuring the loop units

Click to display the loop unit as shown in the figure below.

Figure 65. Loop unit list

Description of the columns in the loop unit list:

No.: Address set on each loop unit.

Used: Select if the address is used or not.

Zone: Select which zone the loop unit shall belong to. The zone numbers should bein the interval of 1-65534. The zone number will be displayed at the control panel



if a fire or fault is reported from the loop unit. The zone numbers are freelyprogrammable and may contain loop units from one or several loops.

Logical: Possibility to give the loop unit a unique number between 1-65534. Theloop unit will be presented with that number at the control panels. By default, thenumber is set to the same as the physical address number.

Type: Select type of loop unit by clicking in the Type column.

Table 2. Type alternatives in alphabetical order. (For units marked with '*', see SCI below.)

Address device Input deviceAny type IS interfaceBell device: EV-SDR_BCN * Loop device (non-fire)Bell device: Generic Manual call point: GenericDetector Manual call point: MCP-2 *Door device Manual call point: MCP-A *Fire alarm device Output deviceFlame detector: EV-BI * SamplingFlame detector: Generic Short circuit isolator **Guard device Smoke detector: EV-PS *Heat detector Smoke detector: GenericI/O device: CN-AIOI *(SCI functional for address ID1 and ID11)

Smoke/heat detector

I/O device: CM21 damper Sprinkler deviceI/O device: CM21 inv. damper Timer deviceI/O device: CM2X control Ventilation deviceI/O device: CM4X controlI/O device: FDU-AE2 v1I/O device: FDU-AE2 v2I/O device: Generic

SCI: Click the check-box in column ‘SCI’ to enable the SCI functions for unitswith built-in SCI’s (Short Circuit Isolators). See valid SCI-units marked with ‘*’ inthe above list under Type.

NOTE!The check-box can only be used for valid SCI-units. In this case the fieldsurrounding the check-box turns white.** An exception is “Short circuit isolator” whose check-box always is checked andgreyed out. It can not be changed because it is by definition a short circuitprotection.

Text 1: A free text field (max 37 characters) describing the location of the loopunit. This text will be shown in the fault list if a fault is reported from the loop unit.

Text 2: An additional free text field (max 37 characters) describing the location ofthe loop unit. Shown in the same way as Text 1.



Setup: Select detector sensitivity against fire conditions by clicking in the Setupcolumn.

Setup alternatives:

• High Sense: The detector will have extra high sensitivity.

• Low Sense: The detector will have extra low sensitivity.

• Dual Heat 80C: Alarm temperature will be 80°C.

• Auto Reset: Automatic removal of reported fires.

• Aspiration Box: For detectors with an aspiration box. Reports a fault if the fanstops working.





3.11.14.5 Advanced Tab

Figure 67. The Advanced tab in the Loop M X editor box

Description of the fields in the Advanced tab:

NS-AOHS: Choose Enable Alarm Blink to make the fire indication LED on allNS-AOHS (including IS versions) on the loop blink – instead of being steady litwhen the detectors are activated. This function should be enabled for examplewhen there are many IS detectors and Isolator-A on the loop.

XFire: Click the check-box Disable standby voltage supervision to disablesupervision of XFire for the Loop M X.

Supervision of standby voltage on the Basic Backup Signal (XFire) are used inorder to verify redundant reporting of the fire condition. This may cause problemswhen upgrading already installed systems that do not have the XFire signalconnected to all modules. The XFire signal is supervised by modules with



XFire-related functionality, i.e. outputs configured for XFIRE activation or inputsconfigured as conventional zones. The backbone master is responsible fordelivering the standby voltage and must therefore also be connected.

3.11.15 Configuring the Loop Module - Loop M X Slave3.11.15.1 About Loop M X SlaveThe Loop M X Slave is connected to a Loop M X and receives the sameconfiguration.

Figure 68. Loop M X Slave editor box

Description of the fields in the Loop M X Slave editor box:

Address: Enter an address for the Loop M X Slave. Each module in a fire alarmcentral should have a unique address between 1-125. Default address depends onmodule type. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the Loop M X Slave. Thistext will be shown in the fault list if a fault is reported from the Loop M X Slave.

3.11.15.2 LoopSlave TabThe LoopSlave tab, as shown below, is used to choose which Loop M X to connectthe Loop M X Slave to.



Figure 69. The LoopSlave tab in the Loop M X Slave editor box

Select partner loop module: Choose which of the available Loop M X units toconnect the Loop M X Slave to.





3.11.16 Configuring the Multiplexer Module 16 -MuxM163.11.16.1 About Multiplexer - MuxM16The multiplexer unit has 256 outputs dedicated for programmable LEDs andinputs/outputs for buzzer, lamp test, buzzer mute, LED-dimmer and LED sync. Themultiplex function can be used for mimics.



Figure 71. Multiplexer editor box

Description of the fields in the Multiplexer editor box:

Address: Enter an address for the Multiplexer. Each module in a fire alarm centralshould have a unique address between 1-125. Default address depends on moduletype. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the Multiplexer. This textwill be shown in the fault list if a fault is reported from the Multiplexer.





3.11.17 Configuring the I/O Module - Relay M 83.11.17.1 About Relay M 8The Relay M 8 has eight programmable relay contacts.



Figure 73. Relay M 8 editor box

Description of the fields in the Relay M 8 editor box:

Address: Enter an address for the Relay M 8. Each module in a fire alarm centralshould have a unique address between 1-125. Default address depends on moduletype. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the Relay M 8. This text willbe shown in the fault list if a fault is reported from the Relay M 8.

3.11.17.2 Outputs TabThe Relay M 8 is equipped with eight outputs that are configured from theOutputs tab, as shown in the figure below.

Figure 74. The Outputs tab in the Relay M 8 editor box

NOTE!DIP switch 8 on module Relay M 8 shall always be set to OFF in a fire detectionsystem.For instructions on how to set DIP-switches on the modules, refer to thecorresponding data sheets.








3.11.18 Configuring the Repeater Module - RM3.11.18.1 About Repeater Module - RMThe Repeater M is a repeater panel used to indicate fire alarm system status. It canbe added to a control unit (see About Mini Repeater - MN400, page 60) or as astandalone unit directly under the central.

Figure 76. Repeater M editor box

Description of the fields in the Repeater M editor box:



Address: Enter an address for the Repeater M. Each module in a fire alarm centralshould have a unique address between 1-125. Default address depends on moduletype. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the Repeater M. This textwill be shown in the fault list if a fault is reported from the Repeater M.

3.11.18.2 Input TabThe Repeater M is equipped with two inputs. They are configured from the inputtab in the Repeater M editor box, as shown in the figure below.

Figure 77. The Input tab in the Repeater M editor box

Description of the columns in the Input tab:

No.: A fixed number for the input on the Repeater M.

Type: Select the type of input by clicking in the type column.

Input type alternatives:

• General input: Input used to activate an action defined in the Cause/Effectconfiguration in the central module.

• Fault input: When activated, this input generates a fault message in the firedetection system, displaying the text defined in Text 1 and Text 2.

• Fire input: When activated, this input generates a fire alarm in the system,displaying the text defined in Text 1 and Text 2.

Active: The value is not editable. It is set to Active high, implying that the systemwill perform the action defined in the Salwico Language configuration.

Break Level: Set the current level under which a cable break fault will begenerated. To avoid cable break fault messages, set the value to 0.

Text 1: A free text field (max 37 characters) describing the input. This text will beshown in the fault list in case of a fault on the input.

Text 2: Additional text field (max 37 characters) describing the input. Shown in thesame way as Text 1.

3.11.18.3 Outputs TabThe Repeater M is equipped with three outputs. They are configured from theoutputs tab in the Repeater M editor box, as shown in the figure below.



Figure 78. The outputs tab in the Repeater M editor box

Enable output monitoring: Tick the box to enable output monitoring.

Hint!For more information about output configuration, see Outputs Tab, page 34 inConfiguring the Control Module - Control M 4.3.

3.11.18.4 Network Tab

Figure 79. The Network tab in the editor box

CAUTION!The network settings for Repeater M are only intended for development.


Figure 80. The Supervision tab in the Repeater M editor box


Secondary power supply (PSU2): Disable or enable fault generation from theSecondary power supply (PSU2) if a power loss occurs. Disable this setting if the10-pin power connector is used on this module.




NOTE!The Secondary backbone channel field can only be found in the tab when therepeater is used as a standalone unit.

3.11.19 Configuring the Mini Repeater Module - MN4003.11.19.1 About Mini Repeater - MN400A repeater panel can show information but not affect the Central (or System) theybelong to. The Mini Repeater M (MN400) can’t be added directly to the central, ithas to be added to a control module (i.e Control M 4.3, Control M 2.2, Control MX). Right click on the control module and choose Add MiniRepeater M (MN400)to add it to the central.

Figure 81. How to add a Mini Repeater

Hint!For information about configuration of the serial communication ports on theconnected control module, see Serial Tab, page 33 in Configuring the ControlModule - Control M 4.3.

When the Mini Repeater module is configured to be added to a control module, usethe protocol MiniRepeater (MN400).



Figure 82. Mini Repeater editor box

Description of the fields in the Mini Repeater editor box:

Address: Enter an address for the Mini Repeater. Each module in a fire alarmcentral should have a unique address between 1-125. Default address depends onmodule type. Please refer to list of modules in section Adding Modules, page 24.

Text: A free text field (max 37 characters) describing the Mini Repeater. This textwill be shown in the fault list if a fault is reported from the Mini Repeater.

3.12 Importing Configuration Information fromExcel

3.12.1 IntroductionIt is possible to import system information such as zones and loop units from anExcel file.

WARNING!All previous entered loop and zone data will be replaced by the informationimported from the Excel file.

An Excel template is available where the customer can add information; a Loopmodule information template.

3.12.2 Importing Loop Module InformationImporting the Loop Board template will add most of the configuration informationto the Loop modules for which information is specified in the template (in theCard Add. column). Proceed as follows:



1 Complete the Loop Board template, available from Consilium, according tothe description below.

2 Add all Loop modules to which information will be imported (seeaddresses given in column Card Add. in the template).

3 Click the File menu to expand it and select Import from Excel.4 Click Import Loop(s).

Figure 83. Loop Board template

3.12.3 Description of the columns in the Loop BoardtemplateCentral Address: The number of the central that the information will be importedto.

Card Address: Enter the module number to which the information will beimported.

Loop Address: The logical loop number 1-9 to which the information will beimported (Logical on the Loop tab).

Zone No: The zone to which the detector belongs (Zone in the loop unit list underLoop tab).

Physical Address: Address set on the detector (Address in the loop unit list underLoop tab).

Logic Address: Logical address that will be presented in case of alarm or fault inthe unit (Logical in the loop unit list under the Loop tab).

Detector type: Type of device that is automatically set to Any Type (Type in theloop unit list under Loop tab). See tab Detector Types in this template for moreinformation.



SCI Enabled: Use '1' for enabled and '0' if not. See tab Detector Types in thistemplate for more information.

Description text 1: Additional text describing the location of the loop unit (Text 1in the loop unit list under Loop tab).

Description text 2: Additional text describing the location of the loop unit (Text 2in the loop unit list under Loop tab).

Hint!See template tab Detector Types. The tab contains a list of strings for availabledetector types and also information if it is possible to enable a short circuit isolatoror not.

3.13 Defining Extended Panel Text

3.13.1 IntroductionExtended panel text can be used to define custom texts for individual panels in theCCP Fire Detection System.

The following options are available from the File menu:

• Export to Excel. (Please refer to Prepare an Excel file with Extended PanelTexts, page 63 and Description of the columns in the Extended Panel Texttemplate, page 64.)

• Import from Excel. (Please refer to Importing the Excel file with ExtendedPanel Texts, page 65 and Verification of Extended Panel Text, page 65.)

• Remove All Texts. All Extended Panel Texts will be removed from theconfiguration.

3.13.2 Prepare an Excel file with Extended Panel Texts1 Use option Export to Excel from the File menu to generate an empty Excel

file the first time export is requested.

2 Select file name and location in the Save As dialog window.

3 Fill in the open columns in the Excel template.• Use columns Row 1 and Row 2 for Extended Panel texts.

• Use column Show on Panel for the addresses.NOTE!Only panels from the locked fields "Shown on panel" and"Control on panel" can be used.

For further explanation of the generated Excel sheet refer to Description ofthe columns in the Extended Panel Text template, page 64.

4 Save the file.



3.13.3 Description of the columns in the ExtendedPanel Text templateThe following information can be found in the empty Excel file generated fromoption Export to Excel (described in Prepare an Excel file with Extended PanelTexts, page 63).

Figure 84. Excel template for Extended Panel Text

System information:

The header shows generated system information only. All fields are locked.

Valid RM Panels lists the valid repeaters (RM4.3) in the system.

Valid CM Panels list the valid controllers (CM4.2, CM2.2, CMX) in the system.

Columns for system units (locked for editing):

Central The central the loop unit is located in.Loop Unit A listing of all detectors sorted in order of central then zone then

address.Loop Unit Type The loop unit type is written if known.Shown on panel The panels the loop unit is shown on, informational only.Control on panel The panels the loop unit can be controlled from, informational

only.Text The text number (1-3), informational only.

Columns for Extended Panel Text:

Row 1 Supplementary text 1 on the panelRow 2 Supplementary text 2 on the panel.



Show on Panel Fields to define which panel addresses a text shall be shown on.NOTE!Only panels from the locked field “Shown on panel” canbe used.

3.13.4 Importing the Excel file with Extended PanelTextsNOTE!Importing data from Exel will replace all Extended Panel Texts in the presentconfiguration with the texts specified in the Excel file.

1 Use option Import from Excel from the File menu to import the Excelsheet prepared accordingly to Prepare an Excel file with Extended PanelTexts, page 63.

2 Select the file in the Open dialog window.

3 The import function creates a file (e.g. extended_text.xml) that is savedinternally in the configuration file structure. Any file already present willbe deleted.

4 A dialog box shows the result of the import.

In case of a not valid Extended Panel Texts file the reasons for failure are listedwith possible fault messages. For more information about verification proceed toVerification of Extended Panel Text, page 65.

3.13.5 Verification of Extended Panel TextVerification of Extended Panel Text is done when the configuration is verified.

In case of a not valid Extended Panel Texts file the reasons for failure are listedwith possible fault messages.

Reasons for fault messages could be changes done to the configuration after import(for example a new detector address) or importing an old extended text file.

1 Export a new Extended Panel Text file.

2 Modify Extended Panel Text file if necessary.

3 Import the Extended Panel Text file.

4 Save the configuration.

3.14 Downloading a configuration file from thefire detection system

3.14.1 Downloading a configuration file to a USBMemory StickWhen you want to view or make changes in an existing configuration file you candownload it from the fire alarm central.



The configuration file can be downloaded using an approved USB memory stick(available from an authorized dealer).

CAUTION!Do not remove the USB memory stick until the download is finished.

1 Connect the USB memory stick to the USB port on the control panel.

2 Choose Menu » 6 Service menu » 6 Configuration » 3 Save configurationto USB memory.

3 Choose the current “.ccp” configuration file from the list and press OK.4 The system will now download the configuration file. Wait until this

process is complete!

5 Disconnect the USB memory stick and copy the configuration file to a PC.

3.15 Uploading a configuration file to the firedetection systemNOTE!Note that a Control M X does not have a USB port and at the writing of thismanual the recommended way to load a configuration to that module is bysynchronizing the configuration from a USB equipped Control Module. This isonly possible if the Control M X resides on the same backbone as the USBequipped Control Module (but it does not have to be in the configuration).Another way of loading a configuration to a Control MX is to put its CCB in aUSB equipped Control Module and load it as usual, then putting it back in theControl MX.

3.15.1 Uploading a configuration file from the USBMemory StickWhen you have finished a configuration file it is time to upload it to the firedetection system. The configuration file must have the file extension “.ccp”.

Note that old versions of the definition program may effect the upload or systemoperations. Use a program version of the CCP Configuration program compatiblewith the system version used in your fire detection system.

NOTE!The system will use the latest version of the file (with the last date and time).

The configuration file can be uploaded using an approved USB memory stick(available from an authorized dealer).

CAUTION!Do not remove the USB memory stick until the upload is finished.

1 Connect the USB memory stick to one of the USB ports on the controlpanel.



2 Choose Menu » 6 Service menu » 6 Configuration » 2 Load configurationfrom USB Memory.

3 A list of the available “.ccp” files on the USB memory stick will bepresented. Choose the appropriate “.ccp” configuration file from the listand press OK.

4 The new configuration file is uploaded to the fire detection system. The oldconfiguration file is automatically renamed by the system (as a back-up filewith the file extension “.bak”) and saved on the USB memory stick.

5 Disconnect the USB memory stick.

6 To synchronise the configuration files between the modules in the systemchoose Menu » 6 Service menu » 6 Configuration » 5 Synchronise systemconfiguration

7 Reboot the system by choosing Menu » 6 Service menu » 6 Configuration »6 Reboot system (this module excluded).

8 Update the system with the new configuration file by choosing Menu » 6Service menu » 6 Configuration » 7 Reboot this module.

9 The Control M 4.3 restarts and loads the new configuration file.

NOTE!Note that a Control M X does not have a USB port and at the writing of thismanual the recommended way to load a configuration to that module is bysynchronizing the configuration from a USB equipped Control Module. This isonly possible if the Control M X resides on the same backbone as the USBequipped Control Module (but it does not have to be in the configuration).Another way of loading a configuration to a Control MX is to put its CCB in aUSB equipped Control Module and load it as usual, then putting it back in theControl MX.

Configuration Manual 4 The Salwico Language


4 The Salwico Language

4.1 About the Salwico Language

4.1.1 IntroductionAn essential part of configuring a fire detection system is to specify its reaction forcertain events, for example what will happen when a manual call point is pressed.To help you make these configurations we have developed the Salwico languagethat consists of a set of commands and a well-defined syntax. The commands areentered in Cause/Effect sheets located under each Central module in the moduletree window.

4.1.2 General Syntax4.1.2.1 Syntax OverviewLet us examine the nature of the programming language. The language is based onthe general form:

Input [: Timer] => Output;

With the Input commands you determine and control the activities of the Outputs,i.e., the function of the system. The Input is evaluated by the system and the resultcan be true or false.

The corresponding Output expression is activated if the Input is true. You may adda time condition (a timer) to the Input. The Output expression is then activated ifthe Input expression is still true when the time condition has elapsed. Otherwise,the Output expression is not activated since the Input condition is false when thetime condition has elapsed.

The arrow sign => is a punctuation mark between Input and Timer on one side andOutput on the other side. If a Timer expression is added, it must be preceded by acolon (:). The Output must always be terminated by a semicolon (;). If there ismore than one Output, these must be separated by a comma (,).

Throughout this manual, brackets are used in the following way:

[ ] Encloses an optional expression, such as Timer in the general form above

{} Encloses an expression that must contain one and only one of the givenparameters

Syntax example:

ZONE 1 : TIMER 60 S => OUT 1.3.1;

If there is one or more alarms on zone 1, then output 1 on system module 3 oncentral 1 is activated after a time delay of 60 seconds. Output 1 on system module3 remains passive if the alarm on zone 1 is reset within 60 seconds.

4 The Salwico Language Configuration Manual


4.1.2.2 InputThe input commands can be divided into four groups according to theirfunctionality:

• Inputs

• System status inputs

• System module generated inputs

• Zone generated inputs

Inputs

The input commands control the output of one central unit. They specify whichinput or input interval that must be true for the corresponding output expression tobe active. The input commands are CU DOOR and IN.

System status inputs

The system status input commands, for example BATTERY FAULT, FIRE INSYSTEM and NET FAULT, can only read the status of a function.

System module generated inputs

The module status input commands, for example DISC, can only read the status ofa system module.

Zone generated inputs

The Salwico language includes several zone-generated inputs that specify detectorsand external devices for different zones, which may indicate fire alarms, forexample ZONE ALL and ZONE HEAT.

4.1.2.3 TimerThe timer commands are very useful when you want to time delay activation of theoutputs or configure a condition that will only activate the outputs if it is true afterthe delay time has elapsed. There are three timer commands:

• ALARM DELAY (can only be used in a marine installation)

• ALARM HOLD (can only be used in an industrial installation)

• TIMER

A total of 196 timer expressions are allowed in the system.

NOTE!The Timer expression must be preceded by a colon (:).

4.1.2.4 OutputThe Salwico language includes several output commands, for example MESSAGEALARM DELAY ON. The Output expressions (see zone Output list) are activatedif the corresponding Input expression is true.



NOTE!All Output commands must be terminated by a semicolon (;).

4.1.2.5 MacroTo facilitate the programming of long expressions, you may use the FLAG x /SYSTEM VIO x commands to create macros. These commands can be used forinputs as well as for outputs. Instead of printing a long expression repeatedly, youcan configure the expression once and then redirect it to the FLAG x / SYSTEMVIO x commands. A total of 255 macros can be configured in each central.

Macro example 1:

ZONE 1 | ZONE 2 | ZONE 9 | ZONE 14 => FLAG 1;

FLAG 1 => OUT 1.3.1;

In this example, FLAG 1 is set equal to the fire zones 1, 2, 9 and 14. FLAG 1 willbe true as long as there are one or more fire alarms in any of the zones and it willbe false when there are no fire alarms in any of the zones. Output 1 on systemmodule 3 in central 1 will be activated as long as FLAG 1 is true and it will bedeactivated when it is false.

It is also possible to add functionality to the FLAG command with the SET FLAGx and RESET FLAG x commands. In Example 1 above, the FLAG commandfollows the alarm status in the fire zone. If you want FLAG to change status ondifferent events, use the SET FLAG and RESET FLAG commands.

SET Can only make the expression trueRESET Can only make the expression false

WARNING!It is possible to set the FLAG to false with the RESET FLAG command as long asthe input expression used with the SET FLAG command is valid.

Warning example

SET FLAG 1;

FLAG 1 => OUT 1.2.3;

RESET FLAG 1;

FLAG 1 => OUT 1.2.3;

WARNING!Avoid multiple settings for the same output as in the example above. The effect onthe system is overload.

Macro example 2

ZONE 1 | ZONE 2 | ZONE 9 | ZONE 14 => SET FLAG 1, FLAG 2;

NOT FLAG 2 & IN 1.1.2 => RESET FLAG 1;

FLAG 1 => OUT 1.4.1;



FLAG 1 will be set to true if there are one or more fire alarms in any of thespecified zones. FLAG 1 will remain true even if the fire alarms in the zone arereset. FLAG 1 will change status to false when input 2 on module 1 in central 1 isactivated. FLAG 2 will ensure that it is not possible to RESET the FLAG as longas there are one or more fire alarms in the zones. Output 1 on system module 4 incentral 1 will be activated as long as FLAG 1 is true and it will be deactivatedwhen it is false.

4.1.2.6 Logical OperatorsIn the Salwico language, you can compare the three input groups "logically". Whenthe Salwico language evaluates a comparison, it returns a value of true or false. The+ operator also returns a sum.

The logical operators are:

NOT

& (And)

| (Or)

+ (Only used in conjunction with the “> greater than” command)

> no. (Greater than the specified number “no.”)

Examples:

NOT IN 1.1.2

True if input 2 on system module 1 in central 1 is not active.

ZONE 2 | ZONE 3

True if there is a fire alarm in zone 2 OR in zone 3.

ZONE 4 & IN 1.1.2

True if there is a fire alarm in zone 4 AND input 2 on system module 1 in central 1is active.

ZONE 1 DET 2 - 3 & ZONE 2 DET

True if there is a fire alarm in zone 1 from any detector in the interval 2 - 3 AND ifthere is a fire alarm from any detector in zone 2.

ZONE 1 DET 2 - 3 | ZONE 2 DET

True if there is a fire alarm in zone 1 from any detector in the interval 2 - 3 OR ifthere is a fire alarm from any detector in zone 2.

ZONE 1 DET 1 - 3 + ZONE 2 DET > 1=> OUT 1.1.2;

The addition operator is used to express detector dependencies and it is only usedin conjunction with the greater than command. The expression adds up the firealarms and if the sum is greater than the specified value, the expression is true. The



expression is true if there are two or more alarms from any of the specifieddetectors.

4.1.3 The order of evaluation in expressionsAn expression is a valid combination of inputs, timers, outputs and logicaloperators that evaluates to a single result. The result represents a true or a falsecondition.

The language evaluates the expressions in the following order: operators shown onthe same line are evaluated left to right within the expression. Parentheses are usedto force the evaluation in a certain order. The following two examples show howyou can use parentheses:

Example 1:

IN 1.1.1 & (ZONE 1 DET 1 | ZONE 1 DET 2)

This expression is true if input 1 on module 1 is active AND if there is a fire alarmfrom detector 1 OR detector 2 in zone 1.

Example 2:

(IN 1.1.1 & ZONE 1 DET 1) | ZONE 1 DET 2

This expression is true if input 1 on module 1 is active at the same time as there is afire alarm from detector 1 in zone 1, OR if there is a fire alarm from detector 2 inzone 1.

4.1.4 Explanatory TextNOTE!You can use a slash (/) and an asterisk (*) to insert explanatory text into theconfiguration. This text is not evaluated by the system.

Example:

ZONE 1 /* Your comment */ => OUT 1.1.3;

This expression is true if any detector in zone 1 is active and that will activateoutput 3 on system module 1. Your explanatory text is not evaluated by the system.

WARNING!Don’t end the configuration code with an explanatory text comment! This willgenerate a syntax error.

4.2 Command Overview

4.2.1 Command Tree4.2.1.1 Section OverviewEvery command allowed in the Salwico Language can be found in one of threecommand trees. The commands are listed in alphabetical order within the trees:Input tree, Timer tree and Output tree.



4.2.1.2 Input TreeTable 3.ALARM DELAY ON (For description, see page 79)ALARM TRANSFER OFF (For description, see page 80)BATTERY FAULT (For description, see page 80)CENTRAL VIO (For description, see page 84)CONTROLS OFF (For description, see page 80)CU z.x DOOR (For description, see page 81)

DISCADDCHDREM

(For description, see page 81)

DISC ZONE x ADDRESS y (For description, see page 82)EXTALARM OFF (For description, see page 82)FAULT IN SYSTEM (For description, see page 83)[UNMUTED] FIRE IN SYSTEM (For description, see page 83)FLAG x (For description, see page 84)IN z.x.y (For description, see page 85)LARMORG MUTE (For description, see page 101)MINI[REPEATER] RESET (For description, see page 86)MUTE MINI[REPEATER] (For description, see page 86)NET FAULT (For description, see page 86)OUT z.x.y (For description, see page 86)PRE-ALARM IN SYSTEM (For description, see page 87)SYSTEM VIO x (For description, see page 87)TCMS_STATUS x.y (For description, see page 87)TCMS_STATUS_BYTE 0xYYYYYYYY (For description, see page 87)UNMUTED FAULT (For description, see page 87)UNMUTED MINI[REPEATER] (For description, see page 88)WARNING IN SYSTEM (For description, see page 89)

[UNMUTED] ZONE

ADDRESSALLDETFDHDM.CALLSDSDHDSPR


FAULT [FAULT TYPE]

[UNMUTED] ZONE x

ADDRESS [y[-z]]ALL [y[-z]]DET [y[-z]]FD [y[-z]]HD [y[-z]]M.CALL [y[-z]]SD [y[-z]]SDHD [y[-z]]SPR [z]


FAULT [FAULT TYPE]



[UNMUTED] ZONE x-y

ADDRESSALLDETFDHDM.CALLSDSDHDSPR


FAULT [FAULT TYPE]

ZONE x IN y.z (For description, see page 93)

NOTE!If desired, the word ZONE in the ZONE commands can be exchanged for SEC.

4.2.1.3 Timer TreeNOTE!If a Timer expression is added, it must be preceded by a colon (:).

Table 4.AD [x S] [, Conditions] (For description, see page 94)AH [x] S, [y] S, Input [,Conditions] (For description, see page 96)

TIMER [x S] [, Conditions] (For description, see page 97)

4.2.1.4 Output TreeNOTE!All the Output commands must be terminated by a semicolon (;).

Table 5.[SET/RESET] CU z.x LED y [COLOR] (For description, see page 99)[SET/RESET] FLAG x (For description, see page 101)LARMORG MUTE (For description, see page 101)MESSAGE(For description, see page 101) ALARM DELAY

TRANS

ONOFFON/OFF

(For description, see page 102) ZONE x TYPE y-z ON/OFF

(For description, see page 103) SD y-z

HIGH SENSENORMAL SENSENORMAL/HIGH SENSENORMAL/LOW

MESSAGE BOARD z.x.y TEMP UPDATE (For description, see page 104)MINI[REPEATER] RESET (For description, see page 104)MUTE_ALL [FIRE/FAULT] (For description, see page 104)NEWCMPROFILE [CENTRAL].[CARD] [SHOWMASK] [CONTROL MASK] (For description, see page 105)

RESET_ALL [FIRE/FAULT] (For description, see page 108)RESOUND_ALL [FIRE/FAULT] (For description, see page 108)SET PARAMETER ZONE x SD y-z AAASENSE (For description, see page 109)PARAMETER ZONE x SD y-z NORMAL/AAASENSE (For description, see page 109)[SET/RESET] PARAMETER ZONE x [TYPE][y-z] ALIMIT a ROR r (For description, see page 109)PARAMETER ZONE x [TYPE] [y-z] ALIMITa ROR r (For description, see page 110)



[SET/RESET] OUT z.x.y [PATTERN] (For description, see page 105)[SET/RESET] SYSTEM VIO x (For description, see page 110)ZONE x OUT y.z [MSK n] (For description, see page 111)

NOTE!If desired, the word ZONE in the ZONE commands can be exchanged for SEC.

4.2.2 Command Reference4.2.2.1 Section OverviewIn the following sub-sections you can find descriptions for each command allowedin the Salwico language for the fire detection system. The commands are groupedinto the categories Inputs, Timers and Outputs separately and will be described inalphabetical order under each heading.

4.2.2.2 ConventionsThe general command syntax follows the command name, for example:

AD [x S] [Input]

When you type a command, you must include all the items in the syntax command,including those that are formatted in italic. Italic formatting indicates argumentnames. Replace the argument names with specific values. The acceptablearguments for each command are listed in a table following the syntax example foreach command. Items enclosed in square brackets are optional. Do not type thebrackets when including an optional item.

For example, you can use any of the following forms of the AD command:

AD

AD 30 S

AD 30 S IN 1.1.1

Some syntax examples do not include optional arguments:

CU z.x DOOR

Type the text and supply a specific value for the variable formatted in italic, as inthe following example:

CU 1.7 DOOR

4.3 Inputs

4.3.1 Summary Input Commands4.3.1.1 Section OverviewThis is a brief description of all the input conditions. For further information oneach command, see Input Command Description, page 79.



4.3.1.2 InputsCU z.x DOOR

Specifies if the door is open on panel z.x.

IN z.x.y

Specifies input number y on system module with address x on central z.

4.3.1.3 System Status InputsALARM DELAY ON

Command is true only if alarm delay is disabled in the central that contains theSalwico code, because alarm delay is central dependent.

ALARM TRANSFER OFF

True if output category alarm transfer is disabled.

BATTERY FAULT

The command is true if there is a battery fault in the system.

CONTROLS OFF

The command is true if one or more outputs of the types General, Door, Fire, Fault,Ventilation or Indication are switched off.

CU z.x SYSTEM VIO y

The command is true if button number y on the control panel with address z.x isactivated.

EXTALARM OFF

The command is true if one or more outputs of the type Alarm device (bell) areswitched off.

FAULT IN SYSTEM

Reads the fault status in the system. The command is true if one or more faults arepresent in the system.

FIRE IN SYSTEM

Reads the fire alarm status in the system. The command is true if there is one ormore fire alarms in the system.

FLAG x

The command is a macro command. You can use the FLAG command to replacelong expressions of input commands.

NET FAULT

The command is true if there is a net fault in the system.



OUT z.x.y

This expression is true when output number y on module with address x on centralz is active.

PRE-ALARM IN SYSTEM

The command is true if a pre-alarm exists in the system.

SYSTEM VIO x

The command is a macro command used when programming the custom shortcuts.True if menu x is activated in a custom menu.

UNMUTED FAULT

Reads the fault status of the system. The command remains true until all faults inthe system are muted.

WARNING IN SYSTEM

The command is true if a warning exists in the system.

4.3.1.4 System Module Generated InputsDISC [ORDER]

True when there is a disablement (disconnection) of in the system.

LARMORG MUTE

This input is only available in industrial applications and is true if all Repeatermodules running in LARMORG mode are muted.

MINI RESET alt MINIREPEATER RESET

When used as input follows output MINI RESET.

MUTE MINI alt MUTE MINIREPEATER

True for 20 seconds when a mini repeater that has control privileges is muted.

UNMUTED MINI alt UNMUTED MINIREPEATER

True for 20 seconds if a reset order fails on a mini repeater.

4.3.1.5 Zone Generated InputsNOTE!If desired, the word ZONE in the ZONE commands can be exchanged for SEC.

[UNMUTED] ZONE [TYPE]

The command is true when there is a fire on a detector with a matching TYPE.

[UNMUTED] ZONE x [TYPE] [y[-z]]



The command is true when there is a fire on a detector with a matching TYPEwithin the detector interval y-z in zone x.

[UNMUTED] ZONE x-y [TYPE]

The command is true when there is a fire on a detector with matching TYPE withinthe zone interval x-y.

[UNMUTED] ZONE [TYPE] FAULT [FAULT TYPE]

The command is true when there is a fault with a matching FAULT TYPE on adetector with a matching TYPE.

ZONE x [TYPE] [y[-z]] FAULT [FAULT TYPE]

The command is true when there is a fault with a matching FAULT TYPE on adetector with a matching TYPE within the detector interval y-z in zone x.

ZONE x-y [TYPE] FAULT [FAULT TYPE]

The command is true when there is a fault with a matching FAULT TYPE on adetector with matching TYPE within the zone interval x-y.

ZONE x IN y.z

The command reads the input status of a control module. The command is truewhen input z on loop unit with address y in zone x is active.

4.3.2 Input Command Description4.3.2.1 ALARM DELAY ONReads the status of the alarm delay function on the control panel. This descriptionis only valid for a marine installation.

Syntax:

ALARM DELAY ON

Comments:

- Alarm delay is central dependent.

- Default: In marine applications, the alarm delay function is by default set to on. Inindustrial applications, the alarm delay function is by default set to off.

- The control panel: In marine applications, the ALARM DELAY indicator on thecontrol panel is lit when the alarm delay is set to off. In industrial applications, theALARM DELAY indicator on the control panel is lit when the alarm delay is set toon.

- To set alarm delay: The alarm delay is set on the control panel. For systems withonly one control unit the unit number is omitted. For more information about thealarm delay function, see the User's Guide.

Examples:



ALARM DELAY ON => OUT 1.1.2;

Output 2 on system module 1 is activated if the alarm delay function is true, i.e. theALARM DELAY indicator is not lit. Output 2 is not active if the ALARM DELAYindicator is lit.

Related Commands:

Table 6.

AD [x S] [, Conditions] Specifies the alarm delay function for a marineinstallation.

MESSAGE ALARM DELAY {ON, OFF,ON/OFF} Is used to change status of alarm delay function.

AH [x] S, [y] S, Input [, Condition] Specifies the alarm delay function for an industrialinstallation.

4.3.2.2 ALARM TRANSFER OFFThe command is true if outputs of type alarm transfer are disconnected.

Example:

ALARM TRANSFER OFF => OUT 1.1.2;

4.3.2.3 BATTERY FAULTThe BATTERY FAULT command is true if there is a battery fault in the system.

Syntax:

BATTERY FAULT

Example:

BATTERY FAULT => OUT 1.3.1;

Output 1 on system module 3 is active as long as there is a battery fault in thecurrent central.

Related Commands:

Table 7.NET FAULT Is true if there is a net fault in the system.

4.3.2.4 CONTROLS OFFThe CONTROLS OFF command is true if one or more outputs of the typesGeneral, Door, Fire, Fault, Ventilation or Indication hatch are switched off in thecurrent central.

Syntax:

CONTROLS OFF

Example:

CONTROLS OFF => OUT 1.3.4;



Output 4 on system module 3 is active as long as there are outputs of the typesGeneral, Door, Fire, Fault, Ventilation or Indication hatch switched off.

Related Commands:

Table 8.

EXTALARM OFF Is true if one or more outputs of the type Alarm device (bell) areswitched off.

4.3.2.5 CU z.x DOORSpecifies if the door is open on panel x. The input CU z.x DOOR is true if the doorof the specified panel is open.

Syntax:

CU z.x DOOR

Parameters:

Table 9.z Specifies a central address.x Specifies a panel address.

Examples:

CU 1.5 DOOR => OUT 1.3.2;

In this example, the command is true if the door is open on the panel in central 1configured as 5.

4.3.2.6 DISC [ORDER]The DISC command is true when there is a disablement (disconnection) in thesystem.

• DISC ADD is true for a short while when any disablement is added.

• DISC CHD is true for a short while when any disablement is added or removed.

• DISC REM is true for a short while when any disablement is removed.

Syntax:

DISC

DISC ADD

DISC CHD

DISC REM

Example 1:

DISC CHD => SET FLAG 8;

FLAG 8 : TIMER 5 S => RESET FLAG 8;



FLAG 8 => OUT 1.4.1;

In this example, output 1 on system module 4 is activated for 5 seconds if adisablement is added or removed.

Example 2:

DISC => OUT 1.4.1

In this example, output 1 on system module 4 is activated as long as there is adisablement in the system.

4.3.2.7 DISC ZONE x ADDRESS ySyntax:

DISC ZONE x ADDRESS y

Any disablement activated with the command on the same zone where “ADDRESSy” belongs to activates the output.

NOTE!The instruction DISC ZONE x ADDRESS y should never be called with the samearguments more than once. If doing so the result may become verynondeterministic. If the result is needed more than once, FLAG should be used.

However, you can of course use the same instruction with different inputcommands several times, such as:

DISC ZONE 12 ADDRESS 5 =>

DISC ZONE 12 ADDRESS 6 =>

CAUTION!Due to the complexity of the instruction DISC ZONE x ADDRESS y the systemwill suffer a lot of processing power if too many are used. This slowdown will benoticed whenever a disablement is either added or removed. It is thereforerecommended to not have more than 200 instances of this instruction in theconfiguration.

Example:

DISC ZONE 159 ADDRESS 30 => OUT 1.55.7;

In this example, command ADDRESS 30 is a smoke/heat detector; however adisablement of MCP(s) in the same zone (ZONE 159) will activate the output.

4.3.2.8 EXTALARM OFFThe EXTALARM OFF command is true if one or more outputs of the type Alarmdevice (bell) are switched off in the current central.

Syntax:

EXTALARM OFF



Examples:

EXTALARM OFF => OUT 1.3.2;

Output 2 on system module 3 is active as long as there are outputs of the typeAlarm device (bell) switched off.

Related Commands:

Table 10.

CONTROLS OFF Is true if one or more outputs of the types General, Door, Fire,Fault, Ventilation or Indication hatch are switched off.

4.3.2.9 FAULT IN SYSTEMReads the fault status in the system. The FAULT IN SYSTEM command is true ifone or more faults are present in the system. The command is true until all faultshave been reset.

Syntax:

FAULT IN SYSTEM

Examples:

FAULT IN SYSTEM => OUT 1.1.2;

Output 2 on system module 1 is active if a fault is present in the system.

Related Commands:

Table 11.UNMUTED FAULT Reads the unmuted fault status in the system.

4.3.2.10 FIRE IN SYSTEMReads the fire alarm status in the system. The FIRE IN SYSTEM command is trueif there are one or more fire alarms in the system. The command remains true untilall fire alarms have been reset.

Syntax:

FIRE IN SYSTEM

Example 1:

FIRE IN SYSTEM & NOT OPEN DOOR => OUT 1.3.7;

In this example, output 7 on system module 3 is activated if a fire alarm is detectedand no panel door is open. This output may, for example, be connected to the firebrigade.

Example 2:

FIRE IN SYSTEM > 1 => OUT 1.3.8;



In this example output 8 on system module 3 is activated if there is at least two firealarms in the system. Useful for example when making “2-detector dependency”commands.

Related Commands:

Table 12.ZONE x-y [Type] Reads the status of the fire alarms in zone/zones.

4.3.2.11 FLAG x / SYSTEM VIO xThe FLAG command is a macro command. You can use the FLAG command toreplace long expressions of input commands. A total of 255 different FLAGconfigurations can be present at the same time.

SYSTEM VIO is used to configure menus connected to customer shortcuts on thepanels. See user menu under Custom Keys Tab, page 36 for more info.

CENTRAL VIO is used to define custom faults and alarms within a central. SeeVIO tab under Description of the fields and buttons in the Central window, page23 for more info.

Syntax:

FLAG x

[SYSTEM] VIO x

CENTRAL VIO x

Parameters:

Table 13.x Select a number between 1 and 255.

Examples FLAG:

ZONE 1 DET 1-17 & ZONE 2 DET 5-19 & ZONE 3 DET 6-36 =>

FLAG 35;

In this example, FLAG 35 is used to define a fire zone, consisting of several zones.

ZONE 4 | FLAG 35 => OUT 1.3.3;

ZONE 5 | FLAG 35 => OUT 1.3.9;

The FLAG 35 is then used to activate output 3 on system module 3 in central 1 if afire alarm is detected in zone four or in the defined fire zone. The FLAG is alsoused to activate output 9 on system module 3 in central 1 if a fire alarm is detectedin zone 5 or in the configured fire zone.

Example SYSTEM VIO:

SYSTEM VIO 1 => OUT 1.5.2;



When custom shortcut 1 on Control Panel M 4.3 is pressed, user menu 1 isdisplayed. If row 1 in the user menu is pressed, output 2 on system module 5 willbe activated (VIO 1 is set, as shown in the figure below).

Example CENTRAL VIO:

CENTRAL VIO 3 => OUT 1.1.2;

An expression with command CENTRAL VIO is used in the same way asSYSTEM VIO.

Related Commands:

Table 14.

RESET FLAG x It is possible to add functionality to the macro command FLAGwith this command. Used only as an output command.

SET FLAG x It is possible to add functionality to the macro command FLAGwith this command. Used only as an output command.

Comments:

- VIO can also be controlled in the Cause/Effect sheets, to give indications in theuser menu. In this case, Indication only (refer to the figure above) must be selected.

4.3.2.12 IN z.x.yCAUTION!It is only allowed to use this command to control module outputs on the samecentral, and should never be used to control other central’s outputs.

True if input y on system module x on central z is activated.

Syntax:

IN z.x.y

Parameters:

Table 15.

z, x, y z specifies the central, x specifies system module address, y specifies inputnumber.

Example:



IN 1.4.1 => OUT 1.5.2

Output 2 on system module 5 on central 1 is active if input 1 on system module 4on central 1 is active.

Related Commands:

Table 16.ZONE x IN y.z The command reads the input status of a control module.

4.3.2.13 MINI RESET alt MINIREPEATER RESETThis input follows the status of the output mini reset.

Example:

MINI RESET => OUT 1.1.6;

Output 6 on module 1 in central 1 is activated if output in mini reset is true.

4.3.2.14 MUTE MINI alt MUTE MINIREPEATERTrue for 20 seconds when a mini repeater that has control privileges is muted.

Example:

FIRE IN SYSTEM & MUTE MINIREPEATER => SET FLAG 2

Sets flag 2 when fire in system and minirepeater with control privileges are muted.

4.3.2.15 NET FAULTThe command NET FAULT is true if there is a net fault in the current central.

Syntax:

NET FAULT

Examples:

NET FAULT => OUT 1.4.4;

Output 4 on system module 4 in central 1 is active as long as there is a netdisturbance in the system.

Related Commands:

Table 17.BATTERY FAULT Is true if there is a battery fault in the current central.

4.3.2.16 OUT z.x.ySpecifies the output y on system module x on central z.

Syntax:

OUT z.x.y



Parameters:

Table 18.

x, y, z x specifies system module address, y specifies output number, z specifies thecentral.

Example:

OUT 1.4.1 => CU 1.7 LED 4

LED 4 on panel 7 is lit if output 1 on module 4 in central 1 is activated.

Related Commands:

Table 19.ZONE x OUT y.z [MSK n] The command reads the output status of a control module.

4.3.2.17 PRE-ALARM IN SYSTEMThe PRE-ALARM IN SYSTEM command is true if one or more pre-alarms arepresent in the system. The command is true until all pre-alarms are removed.

Syntax:

PRE-ALARM IN SYSTEM

Examples:

PRE-ALARM IN SYSTEM => OUT 1.1.2;

Output 2 on system module 1 in central 1 is active if a prealarm is present in thesystem.

4.3.2.18 TCMS_STATUS x.yInput specific for train protocols.

Syntax:

TCMS_STATUS x.y

4.3.2.19 TCMS_STATUS_BYTE 0xYYYYYYYYInput specific for train protocols.

Syntax:

TCMS_STATUS_BYTE 0xYYYYYYYY

4.3.2.20 SYSTEM VIO xSee FLAG x, page 101.

4.3.2.21 UNMUTED FAULTReads the fault status of the system. The UNMUTED FAULT command remainstrue until all faults in the system are muted.



Syntax:

UNMUTED FAULT

Examples:

UNMUTED FAULT : TIMER 60 S => OUT 1.4.1;

In this example output 1 on system module 4 is activated if the fault is not mutedduring the time delay.

Related Commands:

Table 20.FAULT IN SYSTEM Reads the fault status in the system.

4.3.2.22 UNMUTED FIRE IN SYSTEMLike FIRE IN SYSTEM but only true if one or more fire alarms in the system areunmuted.

Syntax:

UNMUTED FIRE IN SYSTEM

4.3.2.23 UNMUTED MINI alt UNMUTED MINIREPEATERTrue for 20 seconds if a reset order fails on a mini repeater.

Example:

(NOT FIRE IN SYSTEM | UNMUTED MINIREPEATER) & FLAG 2 => RESET FLAG2;

If flag 2 is set, it is reset if there is no fire in the system or a reset on a minirepeaterfails.

4.3.2.24 UNMUTED ZONE [Type]Like ZONE [Type] but only true when there is at least one unmuted fire alarm ofthe specified detector type.

Syntax:

UNMUTED ZONE [Type]

4.3.2.25 UNMUTED ZONE x [Type] [y[-z]]Like ZONE x [Type] [y[-z]] but only true when there is at least one unmuted firealarm of the specified Type within the address interval y-z in zone x.

Syntax:

UNMUTED ZONE x [Type][y[-z]]



4.3.2.26 UNMUTED ZONE x-y [Type]Like ZONE x-y [Type] but only true when there is at least one unmuted fire alarmof the specified Type within the zone interval x-y.

Syntax:

UNMUTED ZONE x-y [Type]

4.3.2.27 WARNING IN SYSTEMThe WARNING IN SYSTEM command is true if one or more warnings are presentin the system. The command is true until all warnings are removed.

Syntax:

WARNING IN SYSTEM

Examples:

WARNING IN SYSTEM => OUT 1.1.2;

Output 2 on system module 1 is active if a warning is present in the system.

4.3.2.28 ZONE [Type]Specifies detector types that may indicate fire alarm. The ZONE command is truewhen there is a fire alarm of the specified type.

Syntax:

ZONE [Type]

Parameters:

Table 21.

Type Specifies the detector type. One of the following types can be used:Type ExplanationADDRESSALLDETFDHDM.CALLSDSDHDSPR

All fire detectors, including manual call points.All fire detectors, including manual call points.All automatic fire detectors, excluding manual call points.Flame detectors.Heat detectors, both maximal and rate-of-rise.Manual call points.Smoke detectors.Smoke/heat detectors.Sprinklers.

Comments:

- Default values: The default value for Type is ALL.

- Type: The functions of the types ALL and ADDRESS are identical.



NOTE!Items enclosed in square brackets are optional. Do not type the brackets whenincluding an optional item.

Example:

ZONE => OUT 1.4.3;

All alarms from all zones in the central make output 3 on system module 4 incentral 1 active.

4.3.2.29 ZONE x [Type] [y[-z]]Specifies detectors in different zones that may indicate fire alarm. The ZONEcommand is true when there is a fire alarm of the specified Type within the addressinterval y-z in zone x.

Syntax:

ZONE x [Type][y[-z]]

Parameters:

Table 22.

x The zone number. All zones in one central unit are specified if you omit the zonenumber. The zone number is a number between 1- 65534.



y, z Specifies a single detector address or a detector address interval. y and z can be setto any number between 1-65534.

Comments:

- No parameters: The command reacts on all alarms on all zones in the central unitif you do not specify any parameter.

- Default values: The default value for x is all zones. The default value for Type isALL.

- Type: The function of the types ALL and ADDRESS are identical.




Examples:

ZONE 3 => OUT 1.4.8;

All alarms from zone 3 makes output 8 on system module 4 active.

ZONE 3 SD 2 => OUT 1.4.11;

A fire alarm on smoke detector 2 in zone 3 makes output 11 on system module 4 incentral 1 active.

ZONE 3 DET 2-8 => OUT 1.4.7;

An alarm from any automatic detector in the interval 2-8 in zone 3 makes output 7on system module 4 in central 1 active.

4.3.2.30 ZONE x-y [Type]Specifies different zones where detectors may indicate fire alarm. The ZONEcommand is true when there is a fire alarm of the specified Type within the zoneinterval x-y.

Syntax:

ZONE x-y [Type]

Parameters:

Table 23.

x, yThe a single zone number or a zone number interval. All zones in one central unitare specified if you omit the zone number. The zone number is a number between1- 65534.



Comments:

- No parameters: The command reacts to all alarms in all zones in the central unit ifyou do not specify any parameter.

- Default values: The default value for x is all zones. The default value for Type isALL.

- Type: The functions of the types ALL and ADDRESS are identical.




4.3.2.31 ZONE [Type] FAULT [FAULT TYPE]Specifies faults. The command is true when a fault of the specified FAULT TYPEis present on a detector of the specified Type.

Syntax:

ZONE [Type] FAULT [FAULT TYPE]

Parameters:

See table for the ZONE [Type] parameters.

Comments:

See comments for the ZONE [Type].

Example:

ZONE FAULT => OUT 1.4.7

Output 7 on system module 4 is activated when any fault is reported from anyzone.

4.3.2.32 ZONE x [Type] [y-[z]] FAULT [FAULT TYPE]Specifies faults. The command is true when a fault of the specified FAULT TYPEis present on a detector of the specified Type in the address interval y-z in zone x.

Syntax:

ZONE x [Type] [y[-z]] FAULT [FAULT TYPE]

Parameters:

See table for the ZONE x [Type][y[-z]] parameters.

Comments:

See comments for the ZONE x [Type][y[-z]].

Examples:

ZONE 8 FAULT 128 => OUT 1.4.7

Output 7 on system module 4 is activated when fault no. 128 “no answer” isreported from any unit in zone 8.

ZONE 7 ALL 9-9 FAULT => OUT 1.5.2

Output 2 on system module 5 is activated when a fault is reported from loop unit 9in zone 7.



4.3.2.33 ZONE x-y [Type] FAULT [FAULT TYPE]Specifies faults. The command is true when a fault of the specified FAULT TYPEis present on a detector of the specified Type in the zone interval x-y.

Syntax:

ZONE x-y [Type] FAULT [FAULT TYPE]

Parameters:

See table for the ZONE x-y [Type] parameters.

Comments:

See comments for the ZONE x-y [Type].

4.3.2.34 ZONE x IN y.zThe command reads the input status of a control module.

Syntax:

ZONE x IN y.z

Parameters:

Table 24.

xSpecifies the zone number. All zones in one central unit are specified ifyou omit the zone number. The zone number is a number between 1-65534 depending on the configuration of the central unit.

y, z Specifies a single input address, y can be 1-65534 and z 1-8.

Examples:

ZONE 1 IN 1.5.1 => OUT 1.4.1;

Output 1 on system module 4 in central 1 is activated if input address 5.1 on zone 1is set.

Related Commands:

Table 25.IN z.x.y Specifies the input y on system module x in central z.ZONE x OUT y.z [MSK n] Sets an output on a control module.

4.4 Timers

4.4.1 Summary Timer CommandsThis is a brief description of all the timer conditions. For further information oneach command, see Timer Command Description, page 94.

A total of 196 timer expressions are allowed in the system.



NOTE!Timer expressions must be preceded by a colon (:).

AD [x S] [Conditions] - Marine installation

Specifies an alarm delay time for the last inputs specified before the AD command.Each usage of the AD command consumes one of the 32 timer expressions percentral that are allowed. Can be overridden by a Manual Call Point.

AH [x] S, [y] S, Input [, Conditions] - Industrial Installation

Specifies an alarm mute and reset time for the inputs before the AH command.Each usage of the AH command consumes two of the 32 timer expressions percentral that are allowed.

TIMER [x S] [, Conditions]

Specifies an alarm delay time for the inputs before the TIMER command. Eachusage of the TIMER command consumes one of the 32 timer expressions percentral that are allowed.

4.4.2 Timer Command Description4.4.2.1 AD [x S] [, Conditions] - Marine InstallationSpecifies an alarm delay time for the last inputs specified before the AD command.The time delay acts on the inputs specified before the AD command. The functionof this command is closely related to the setting of the alarm delay function on thecontrol panel of the central. The delay time of the AD command is ignored if theALARM DELAY indicator on the control panel is lit. The AD command is ignoredif a manual call point is activated in any zone of the central unit.

The time delay function may be overruled if you specify an input in the ADcommand and this input becomes true during the time delay or by activation of amanual call point. The output is then activated immediately because the inputpreceding the AD command is true.

If no time delay is entered in the menu, the system will use the default value 2minutes. This value is adjustable from the system menu.

Each usage of the AD command consumes one of the 32 timer expressionsallowed.

NOTE!The delay time should be configured in increments not exceeding 1 minute up to amaximum of 10 minutes.

Syntax:

: AD [x S] [, Conditions]

Parameters:



Table 26.

[x S]Specifies the alarm delay time in seconds. Do not forget to write acapital S (seconds) when a time is specified. System settings fordefault time will be used, if the variable x is omitted.

Conditions Specifies any input.

Comments:

- ALARM DELAY on the control panel: The alarm delay function is ignored if theALARM DELAY indicator on control panel is lit.

- Manual call points: The AD command is ignored if a manual call point isactivated in any zone of the central unit.

- Default time: The default time is 30 seconds, if no time is specified.

- If no time is specified, it is possible to set the time delay from a control panel.Time is then set in increments of 1 minute.

Hint!Limits: Only one Input command can be specified. However, flags can be used.


Examples:

In the following examples, the ALARM DELAY indicator on the control panel isnot lit.

ZONE : AD => OUT 1.3.5;

Control of all outputs in the system are time delayed for 30 seconds, default time(ignored for a manual call point).

ZONE : AD 90 S => OUT 1.2.13;

Control of all outputs in the system are time delayed for 90 seconds (ignored for amanual call point).

ZONE 4 : AD 45 S, IN 1.2.3 => OUT 1.5.2;

Control of all outputs in zone 4 are time delayed for 45 seconds (ignored for amanual call point). If input IN 1 becomes true during the time delay the outputOUT 2 on system module 5 in central 1 is activated immediately.

Related Commands:

Table 27.

AH [x] S, [y] S, Input [,Conditions]

Specifies the alarm delay function for an industrialinstallation.

ALARM DELAY ON Reads the status of the alarm delay function on thecontrol panel for a marine installation.



MESSAGE ALARM DELAY {ON, OFF,ON/OFF} Will disable or enable alarm delay in own central.

TIMER [x S] [, Conditions]Specifies the alarm delay time for the inputs. Norelation with the alarm delay function on the controlpanel.

If you want the manual callpoint to override the alarm delay, see the last examplein TIMER [x S] [, Conditions], page 97.

4.4.2.2 AH [x] S, [y] S, Input, Conditions - Industrial InstallationSpecifies an alarm mute and reset time for the inputs. The mute time acts on theinputs specified in front of the AH command. The ALARM HOLD function isignored if the indicator ALARM DELAY on the control panel is not lit.

Each usage of the AH command consumes two of the 32 timer expressionsallowed.

Syntax:

: AH [x] S, [y] S, Input, Conditions

Parameters:

Table 28.

[x] S(Mute time)

Specifies the mute time in seconds. Do not forget to write acapital S (seconds) when the mute time is specified. Systemsettings for default time will be used, if the variable x is omitted.If the x time has elapsed (not muted) then the timer commandbecomes true.

[y] S(Reset time)

Specifies the time to investigate and reset the fire alarm. Do notforget to write a capital S (seconds) when the reset time isspecified. System settings for default time will be used, if thevariable x is omitted.

Input Specifies the mute input.

Conditions

Specifies the input conditions that will interrupt the time delayand activate the expression that is specified immediately beforethe AH command. A Condition is an expression that may consistof Inputs, System Status Inputs, Zone Generated Inputs andlogical operators.

Comments:

- The time y can only be specified if the time x is specified.

- ALARM HOLD indicator: The ALARM HOLD function is ignored if theindicator ALARM DELAY on the control panel is not lit.

- Limits: Only one mute input can be specified.

- Default time: If no time is specified, the default mute time is 30 seconds and thedefault reset time is 180 seconds. If no time is specified, it is possible to set thetime delay from a control panel. Time is then set in increments of 1 minute.




Example:

FIRE IN SYSTEM : AH 53 S , 600 S, IN 1.1.2, ZONE M.CALL | ZONE HEAT=> OUT 1.4.11;

In this example, output 11 on system module 4 is activated if you do not mute thealarm by using input 2 on system module 1 in central 1 during the mute time (53seconds). If the alarm is muted, you will have 10 minutes to investigate the causeof the alarm and to reset it. Output 11 on system module 4 in central 1 is activatedif the alarm is not reset during the reset time. If there is an alarm from a manualcall point or a heat detector during the mute time or the reset time, Output 11 onsystem module 4 in central 1 is activated immediately and both the mute time andthe reset time are disregarded.

Related Commands:

Table 29.AD [x S] [, Conditions] Specifies the alarm delay function for a marine installation.

MESSAGE ALARM DELAY {ON,OFF, ON/OFF}

Is used to to enable or disable alarm delay. Repeater settingsis controlled by CE.

TIMER [x S] [, Conditions] Specifies the alarm delay time for the inputs. This has norelation to the alarm delay function on the central panel.

ALARM DELAY ON Reads the status of the alarm delay function on the controlpanel for a marine installation.

4.4.2.3 TIMER [x S] [, Conditions]Specifies an alarm delay time for the inputs. The inputs specified before theTIMER command are time delayed.

The time delay function may be overruled if you specify an input in the TIMERcommand and this input becomes true during the time delay. Since the inputpreceding the TIMER command also is true the output is activated immediately.

Each usage of the TIMER command consumes one of the 32 timer expressionsallowed.

Syntax:

: TIMER [x S] [, Conditions]

Parameters:

Table 30.

[x S] Specifies the alarm delay time in seconds. Always type S when atime is specified.

Conditions Immediately specifies the input conditions that will interrupt thetime delay and control the output.

Comments:



- Default time: The default time for x is 30 seconds.


Examples:

ZONE 3 : TIMER 90 S, IN 1.3.1 => OUT 1.4.1;

In this example a setting of the output in zone 3 is time delayed for 90 seconds.However, if input 3.1 is active, out 4.1 is activated immediately.

ZONE 3 : TIMER 100 S => FLAG 1;

ZONE 3 & NOT FLAG 1 => OUT 1.4.5;

If there is a fire alarm in zone 3 then output 5 on system module 4 is activated for100 seconds.

ZONE 3 : TIMER 120 S, NOT ALARM DELAY ON => OUT 1.4.6;

If you only want the delay when alarm delay is active.

Related Commands:

Table 31.

AD [x S] [, Conditions] Specifies the alarm delay function for a marineinstallation.

AH [x] S, [y] S, Input [,Conditions]

Specifies the alarm delay function for an industrialinstallation.

4.5 Outputs

4.5.1 Summary Output CommandsThis is a brief description of all output conditions. For further information on eachcommand, see Output Command Description, page 99.

NOTE!All Output commands must be terminated by a semicolon (;).

CU z.x LED y

The command is used to set LEDs on the panels.

FLAG x

The command is a macro command. You can use the FLAG command to replacelong expressions of input commands.

MESSAGE ALARM DELAY [x] {ON, OFF, ON/OFF}

Activates or deactivates the ALARM DELAY function.



MESSAGE ALARM TRANS [x] {ON, OFF, ON/OFF}

Activates or deactivates the ALARM TRANS function.

MESSAGE ZONE x TYPE y-z ON/OFF

Reconnects or disconnects an interval of detectors in a zone.

MESSAGE ZONE x SD y-z [ORDER]

Sets smoke detector sensitivity in an interval of a zone.

MESSAGE BOARD x.y TEMP UPDATE

The command activates transmission of temperature for all heat detectors on theselected loop.

MINI RESET alt MINIREPEATER RESET

Remove control privileges from a minirepeater.

OUT x.y

Specifies the outputs in the central unit. The specified outputs are controlled by theactive inputs.

RESET FLAG x / SYSTEM VIO x

It is possible to add functionality to the macro command FLAG/VIO with thiscommand. Used only as an output command.

SET FLAG x / SYSTEM VIO x

It is possible to add functionality to the macro command FLAG/VIO with thiscommand. Used only as an output command.

SYSTEM VIO x

SYSTEM VIO is used to configure menus connected to customer keys on thepanels.

ZONE x OUT y.z [MSK n]

The command sets an output on a control module.

4.5.2 Output Command Description4.5.2.1 CU z.x LED yThe CU z.x LED y command is used to set LEDs on the panels.

Syntax:

[SET/RESET] CU z.x LED y [COLOR] [FLASH]

Parameters:



Table 32.z Central addressx Panel address

y LED number (1-4).(LED no. 4 only available on industrial panel).

COLOUR(only on industrial panel)

LED number 1-3. RED (blank=red), YELLOWLED number 4. RED (blank=red)

FLASH FLASH

Examples:

FIRE IN SYSTEM => CU 2 LED 1;

LED 1 at panel 2 is set as long as there is a fire in the system.

FIRE IN SYSTEM => CU 2 LED 3 YELLOW FLASH;

LED 3 at panel 2 is flashing with a yellow light (green & red parts of the LED arelit at the same time) as long as there is a fire in the system.

LED locations:

The LEDs are located on the control panels. See illustrations below.

LED 1 = LED in the top custom shortcut

LED 2 = LED in the middle custom shortcut

LED 3 = LED in the lower custom shortcut

LED 4 = LED for Alarm transmitter activated “Larmsändare aktiverad” (industrialpanel only)

Figure 85. LED 1-3 on a control panel for marine applications



Figure 86. LED 1-4 on a control panel for industrial applications

4.5.2.2 FLAG xThe FLAG command can be used both as input and output command. Fordescription and examples, see FLAG x / SYSTEM VIO x, page 84.

4.5.2.3 LARMORG MUTEThe command is only available in industrial applications and will mute allconnected Repeater modules running in LARMORG mode.

Example:

IN 1.1.2 => LARMORG MUTE;

All LARMORG Repeater modules will be muted as soon as input 1.1.2 isactivated.

4.5.2.4 MESSAGE ALARM DELAY [x] {ON, OFF, ON/OFF}The message alarm delay ON/OFF is used to activate or deactivate the alarm delayfunction.

Syntax:

MESSAGE ALARM DELAY [x] {ON, OFF, ON/OFF}

Parameters:

x x has to be a central number. If none is supplied the function will be disabled inthe entire system.

Comments:

The commands that include ON/OFF function as follows:

• If the input condition is true, the first argument is valid (ON).

• If the input condition is false, the second argument is valid (OFF).

Example 1:



IN 1.1.3 => MESSAGE ALARM DELAY 9 ON;

When input 3 on module 1 is active the alarm delay function is activated in central9.

Example 2:

NOT IN 1.1.3 => MESSAGE ALARM DELAY 9 OFF;

When input 3 on module 1 is turned off the alarm delay function is deactivated incentral 9.

4.5.2.5 MESSAGE ALARM TRANS [x] {ON, OFF, ON/OFF}The message alarm trans ON/OFF is used to disable or enable outputs of categoryalarm transfer.

Syntax:

MESSAGE ALARM TRANS [x] {ON, OFF, ON/OFF}

Parameters:

x x has to be a central number. If none is supplied the function will be disabled inthe entire system.

Comments:

The commands that include ON/OFF function as follows:


• If the input condition is false, the second argument is valid (OFF).

Example:

IN 1.1.3 => MESSAGE ALARM TRANS 7 ON;

When input 3 on module 1 is active the outputs of category alarm transfer areenabled in central 7.

4.5.2.6 MESSAGE ZONE x TYPE y[-z] ON/OFFThe command is used to reconnect or disconnect an interval of detectors in a zone.

Syntax:

MESSAGE ZONE x TYPE y-z ON/OFF

Parameters:

Table 33.x Specifies a zone between 1 and 65534.y Specifies a detector between 1 and 65534.z Specifies a detector between 1 and 65534.





y, z Specifies a single detector address or a detector address interval. y and z can be setto any number between 1-65534.

Comments:

The ON/OFF command functions as follows:


• - If the input condition is false, the second argument is valid (OFF).


Example:

IN 1.4.2 => MESSAGE ZONE 1 DET 1-5 ON/OFF;

Detectors 1-5 in zone 1 are switched off as long as input 2 on system module 4 isactivated.

4.5.2.7 MESSAGE ZONE x SD y-z [ORDER]The command is used to set smoke detector sensitivity in an interval of a zone.

Syntax:

MESSAGE ZONE x SD [y[-z]] NORMAL SENSE

MESSAGE ZONE x SD [y[-z]] HIGH SENSE

MESSAGE ZONE x SD [y[-z]] NORMAL/HIGH SENSE

Parameters:

Table 34.x Specifies a zone between 1 and 65534.y Specifies a detector between 1 and 65534.z Specifies a detector between 1 and 65534.

Comments:



The NORMAL/HIGH command functions as follows:

• If the input condition is true, then the first argument is valid (NORMAL).

• If the input condition is false, then the second argument is valid (HIGH).


Examples:

IN 1.4.1 => MESSAGE ZONE 1 SD 5-10 NORMAL SENSE;

NOT IN 1.4.1 => MESSAGE ZONE 1 SD 5-10 HIGH SENSE;

Smoke detectors 5-10 will have normal sensitivity as long as input 1 on systemmodule 4 is active.

IN 1.4.2 => MESSAGE ZONE 5 SD NORMAL/HIGH SENSE;

All smoke detectors in zone 5 will have normal sensitivity as long as input 2 onsystem module 4 is active.

4.5.2.8 MESSAGE BOARD z.x.y TEMP UPDATEThe command activates transmission of temperature for all heat detectors on theselected loop.

Example:

FLAG 1 | NOT FLAG 1 => MESSAGE BOARD 1.11.1 TEMP UPDATE;

Activates the temperature update from all heat detectors on loop 1 on module 11 incentral 1.

4.5.2.9 MINI RESET alt MINIREPEATER RESETThe command removes control privileges from minirepeater.

Example:

FIRE IN SYSTEM & NOT CU 1.7 DOOR => MINIREPEATER RESET;

4.5.2.10 MUTE_ALL [FIRE/FAULT]Based on input expression the system performs a mute operation on all items in thespecified list, FIRE or FAULT list. Mute is always performed on a root user level,all fault or fires are affected, no show/control rights are checked.

Syntax:

MUTE_ALL [FIRE/FAULT]

Examples:

IN 1.20.1 => MUTE_ALL FIRE



IN 1.20.2 => MUTE_ALL FAULT

4.5.2.11 NEWCMPROFILE [CENTRAL].[CARD] [SHOW MASK][CONTROL MASK]CAUTION!It is only allowed to use this command for system changes on the same central, andshould never be used to change rights for other centrals.

Based on input expression the system changes the show and control masks of theCM with address [CENTRAL].[CARD]. The address [CENTRAL].[CARD] mustbe the address of a configured CM may not be a broadcast/group address. The[SHOWMASK] and [CONTROL MASK] are numbers in either decimal orhexadecimal. For hexadecimal numbering use the prefix '0x'(ex. 0xABCDEF). The[SHOWMASK] and [CONTROL MASK] numbers are used as bitmasks, wherebit identifies a group specified in the CCP Conf program. A set bit indicates thatthe mask includes the group.

There are a maximum of 32 groups in the system. The group number from CCPConf identifies the bit position representing the group.

To create a mask including groups 1,7,8,20 and 27 use the approach below:

Group number Corresponding 32 bit binary valueGroup 1: 0000 0000 0000 0000 0000 0000 0000 0001Group 7: 0000 0000 0000 0000 0000 0000 0100 0000Group 8: 0000 0000 0000 0000 0000 0000 1000 0000Group 20: 0000 0000 0000 1000 0000 0000 0000 0000Group 27: 0000 0100 0000 0000 0000 0000 0000 0000

Sum of all: 0000 0100 0000 1000 0000 0000 1101 0001

CorrespondingHexadecimal: 0 4 0 8 0 0 D 1

Mask value to use in C/E rule: 0x040800D1

Syntax:

NEWCMPROFILE [CENTRAL].[CARD] [SHOW MASK] [CONTROL MASK];

Examples:

IN 1.20.5 => NEWCMPROFILE 1.1 0x040800D1 0x040800D1;

IN 1.20.6 => NEWCMPROFILE 1.2 67633361 67633361;

4.5.2.12 OUT z.x.y [PATTERN]Specifies the outputs on the system modules. The specified outputs are controlledby the active inputs.

Syntax:



[SET/RESET] OUT z.x.y [PATTERN]

Parameters:

Table 35.z, x, y z = central address, x = system module address, y = output number

PATTERN

GA71 seven short, 1 longFLASH 1s on, 1s offPATTERN 1 HZ 0.5s on 0.5s offPATTERN 1 THIRD 1.5s on 1.5s offPATTERN FINLAND 2s on, 1s offPATTERN GAS 0.5s on, 0.5s off, 0.5s on, 1.5s off

PATTERN POLAND 1.5s on, 1.5s off, 1.5s on, 1.5s off, 3.5s on,1.5s off

PATTERN PRE-ALARM 0.5s on, 1.5s offPATTERN 10 1.5s on, 1,5s off, 6s on, 1.5s offPATTERN 11 6s on, 3s offPATTERN 12 1s on, 1s off 4s on, 1s offPATTERN 13 1s on, 1s off, 2s on, 1s offPATTERN CANADA 5s on, 30s offPATTERN PULSE 5s on, 1s offAll patterns repeat forever with the exception:PATTERN PULSE only one time

Comments:


Examples:

FIRE IN SYSTEM & NOT OPEN DOOR => OUT 1.4.11;

If there is a fire in the system and there are no open doors then output 11 on systemmodule 4 in central 1 is activated.

UNMUTED FAULT & NOT OPEN DOOR => OUT 1.4.12;

If there is an unmuted fault in the system and there are no open doors then output12 on system module 4 in central 1 is activated.

UNMUTED FAULT => OUT 1.4.12;

If there is an unmuted fault in the system then output 12 on system module 4 incentral 1 is activated.

IN 1.1.3 => SET OUT 1.2.3;

NOT IN 1.1.3 & IN 1.1.4 => SET OUT 1.2.3 FLASH;



NOT (IN 1.1.3 | IN 1.1.4) => RESET OUT 1.2.3;

If input 3 on system module 1 in central 1 is activated then output 3 on systemmodule 2 in central 1 remains on. However, if input 4 on system module 1 incentral 1 is activated and input 3 on system module 1 in central 1 is inactive thenoutput 3 on system module 2 in central 1 is activated with an intermittent signal (1sec. on, 1 sec. off).

If neither input is activated the output is reset.

FIRE IN SYSTEM => OUT 1.3.8 GA71;

If there is a fire in the system, output 8 on system module 3 in central 1 will be setwith the pattern 7 short (1.5 sec. on, 1.5 sec. off) and 1 long (7 sec.)

ZONE 1 ADR 8 => OUT 1.3.147;

If address 8 in zone 1 is activated, output 147 (= LED 147) on system module 3 incentral 1 (in this case a ZB with MUX software). The LED number can be in theinterval of 1-254.

Related Commands:

Table 36.ZONE x OUT y.z [MSK n] Sets an output on a control module.

4.5.2.13 Rate of Rise C/E rulesRate of Rise functionality allows for setting of a different alarm threshold andtemperature rise threshold for heat detectors. By using C/E commands it is possibleto vary the temperature threshold between 30 - 84 deg Celcius and set the alarm totrigger when the temperature rise is between 3 to 7 deg Celcius per minute.

CAUTION!Maximum limit to be set for heat rise is 7 degree Celsius per minute.

Detector Support

The following detectors are supported by this function:

• CN/EV-H

• CN/EV-PH

• NS-AH

• NS-AOHS

C/E Rules

The Rate of Rise rule is defined as follows:

Syntax:

[EXPRESSION] => [/SET/RESET] PARAMETER ZONE [#Z] [TYPE] [#ADR-#ADR]ALIMIT [#ALIMIT] ROR [#ROR_LIMIT];



CAUTION!Take care not to define overlapping rules!!If this is done, the system may become choked by setting and clearing Rate of Riserules each C/E run. This will result in caotic/unpredictable system behaviour.

Parameters:

[EXPRESSION] Your regular C/E expression to control the Rate of Riseexpression.

[/SET/RESET]

This argument is optional and can be left out. If the argument isleft out the Rate of Rise settings will follow the [EXPRESSION].If [EXPRESSION] evaluates to true then the Rate of Rise rulewill be set.If [EXPRESSION] evaluates to false the Rate of Rise rule will becleared.If the argument is "SET" then the Rate of Rise rule will beexplicitly set when the [EXPRESSION] argument evaluates totrue.If the argument is "RESET" then the Rate of Rise rule will beexplicitly cleared when the [EXPRESSION] argument evaluatesto true.

[#Z] Zone number[TYPE] Detector type "HEAT", "SMOKE" etc.[#ADR-#ADR] Address range, detector address #from - #to.[#ALIMIT] Heat alarm threshold in tenths of degrees Celcius.[#ROR_LIMIT] Heat rise alarm threshold in tenths of degrees Celcius.

For more examples, please see [SET/RESET] PARAMETER ZONE x [TYPE][y-z] ALIMIT a ROR r, page 109.

4.5.2.14 RESET_ALL [FIRE/FAULT]Based on input expression the system performs a reset operation on all items in thespecified list, FIRE or FAULT list. Reset is always performed on a root user level,all fault or fires are affected, no show/control rights are checked.

Syntax:

RESET_ALL [FIRE/FAULT]

Examples:

IN 1.20.3 => RESET_ALL FIRE

IN 1.20.4 => RESET_ALL FAULT

4.5.2.15 RESOUND_ALL [FIRE/FAULT]Broadcasts a resound all fire alarms or fault messages in the system.

Syntax:

RESOUND_ALL [FIRE/FAULT]

Examples:



VIO 1 => RESOUND_ALL FIRE;

VIO 2 => RESOUND_ALL FAULT;

4.5.2.16 SET PARAMETER ZONE x SD y-z AAA SENSESets the sensitivity value for smoke devices in specified zone and address range.Note that SET must be specified and that no reset of the sensitivity value will bemade unless adding another sensitivity expression.

Syntax:

SET PARAMETER ZONE x SD y-z AAA SENSE

Parameters:

x Zone numbery-z Address range, to-fromAAA Sensitivity level; LOW, NORMAL or HIGH

4.5.2.17 PARAMETER ZONE x SD y-z NORMAL/AAA SENSESwitches the sensitivity value between NORMAL and AAA for smoke devices inspecified zone and address range. Note that specifying SET or RESET is notpossible since it is a two-state rule following the result of the evaluated input.

Syntax:

PARAMETER ZONE x SD y-z NORMAL/AAA SENSE

Parameters:

x Zone numbery-z Address range, to-fromAAA Inactive sensitivity level; LOW or HIGH

4.5.2.18 [SET/RESET] PARAMETER ZONE x [TYPE] [y-z] ALIMITa ROR rSET PARAMETER ZONE x [TYPE] [y-z] ALIMIT a ROR r

Set parameter rule will set the Rate of Rise and Heat alarm thresholds when theinput expression is true. The setting will not be cleared at any time by this rule.

RESET PARAMETER ZONE x [TYPE] [y-z] ALIMIT a ROR r

Reset parameter rule will clear the Rate of Rise and Heat alarm thresholds whenthe input expression is true. The setting will not be set at any time by this rule.

Parameters:

x Zone numberTYPE Detector type, ”HEAT”, ”SMOKE” etc.y-z Address range, to-from



a Alarm level for heat alarm (1/10 degCelcius)

r Alarm level for rate of rise alarm (1/10 degCelcius per minute)

For more explanation, see Rate of Rise C/E rules, page 107

4.5.2.19 PARAMETER ZONE x [TYPE] [y-z] ALIMIT a ROR rRule will clear the Rate of Rise and Heat alarm thresholds when the inputexpression is true. The setting will not be set at any time by this rule.

Syntax:

PARAMETER ZONE x [TYPE] [y-z] ALIMIT a ROR r

Parameters:

x Zone numberTYPE Detector type, ”HEAT”, ”SMOKE” etc.y-z Address range, to-froma Alarm level for heat alarm (1/10 deg

Celcius)r Alarm level for rate of rise alarm (1/10 deg

Celcius per minute)

For more explanation, see Rate of Rise C/E rules, page 107

4.5.2.20 SET/RESET FLAG x / SYSTEM VIO xIt is possible to add functionality to the macro command FLAG or SYSTEM VIOwith the SET and RESET FLAG/VIO commands. If you want FLAG to changestatus on different events, use the SET FLAG/VIO and RESET FLAG/VIOcommands (the commands run parallel to each other).

The command SET will lock the FLAG/VIO in a true condition. It will stay trueuntil a RESET command has been performed.

Syntax:

SET FLAG x

RESET FLAG x

SET [SYSTEM] VIO x

RESET [SYSTEM] VIO x

Parameters:

Table 37.x Select a number between 1 and 255.

Examples:



ZONE 1 | ZONE 2 | ZONE 9 | ZONE 14 => SET FLAG 1, FLAG 2;

NOT FLAG 2 & IN 1.3.1 => RESET FLAG 1;

FLAG 1 => OUT 1.3.1;

FLAG 1 will be set to true if there are one or more fire alarms in the zones 1, 2, 9or 14. FLAG 1 will remain true even if the fire alarms in the zone are reset.

FLAG 1 will change status to false when input 1 on system module 3 is activated.FLAG 2 will ensure that it is not possible to RESET the FLAG as long as there areone or more fire alarms in the zones. Output 1 on system module 3 will beactivated as long as FLAG 1 is true and it will be deactivated when it is false.

Related Commands:

Table 38.

FLAG x You can use the FLAG command to replace long expressions ofinput commands.

4.5.2.21 SYSTEM VIO xThe SYSTEM VIO command can be used both as an input and an outputcommand. For description and examples, see FLAG x / SYSTEM VIO x, page84.

4.5.2.22 ZONE x OUT y.z [MSK n]The command sets an output on a control module.

Syntax:

ZONE x OUT y.z [MSK n]

Parameters:

Table 39.

x Specifies the zone number. The zone number is a number between 1-65534 depending on the configuration of the central unit.

y, z Specifies a single output address, y can be 1-65534 and z 1-8.

MSKMSK can onlybe used for thefollowing loopunits:

EV-ABS Sounder mask = 0x18Beacon mask = 0x20

EV-SB Sounder mask = 0x8FBeacon mask = 0x20

EV-SB-DSCI Sounder mask = 0x8FBeacon mask = 0x20

n n can be 0x1-0xFF.

Example:

FIRE IN SYSTEM => ZONE 7 OUT 8.2 MSK 254;

If there is a fire in the system then output 2 on address 8 on zone 7 is activated.

Related Commands:



Table 40.OUT x.y x = system module address, y = output numberZONE x IN y.z Reads the input status of one or more control modules.

4.6 Application Examples

4.6.1 Section OverviewThis section includes a description of some common problems and how you maysolve these problems when configuring the system.

4.6.2 Fire Alarm OutputsExample 1:

When a fire alarm occurs anywhere in the system, the outputs remain active if theyhave not been muted.

UNMUTED FIRE IN SYSTEM => OUT 1.4.9;

A fire alarm makes output 9 on system module 4 in central 1 active, and the outputremains active until all fire alarms are muted.

Example 2:

This is the same problem as in Example 1, but you need some time to investigatethe alarm before the output should be activated, although the output should bemade active immediately if a manual call point is activated.

UNMUTED FIRE IN SYSTEM : AD 120 S => OUT 1.4.4;

If a detector alarm, from anywhere in the system, is not muted within 120 secondsoutput 4 on system module 4 in central 1 is activated, and it remains active until thefire alarm is muted. The output is not activated at all if the fire alarm is mutedwithin 120 seconds. Output 4 on system module 4 in central 1 is activatedimmediately if a manual call point is activated.

Example 3:

The same problem as in Example 1, but you need some time to investigate thealarm before the output is activated. The output should not be made active if amanual call point is activated.

UNMUTED FIRE IN SYSTEM : TIMER 120 S, NOT ALARM DELAY ON => OUT1.4.4;

If a fire alarm anywhere in the system is not muted within 120 seconds, output isactivated. It remains active until the fire alarm is muted. The output is not activatedat all if the fire alarm is muted within 120 seconds. Output 4 on system module 4 incentral 1 is activated immediately if the ALARM DELAY indicator on the controlpanel is lit. Output 4 on system module 4 in central 1 is not activated if a manualcall point is activated.

Example 4:



It is possible to let the audible alarm sound with different patterns, for exampleFLASH or GA (seven short-one long).

IN 1.1.3 => SET OUT 1.2.3;

NOT IN 1.1.3 & IN 1.1.4 => SET OUT 1.2.3 FLASH;

NOT (IN 1.1.3 | IN 1.1.4) => RESET OUT 1.2.3;

If input 3 on system module 1 in central 1 is activated then output 3 on systemmodule 2 in central 1 remains on. However, if input 4 on system module 1 incentral 1 is activated and input 3 on system module 1 in central 1 is inactive thenoutput 3 on system module 2 in central 1 is activated with an intermittent signal (1sec. on, 1 sec. off).

If neither input is activated the output is reset.

4.6.3 SurveillanceExample 5:

/* FAULT OUTPUT VIA RELAY ON CM-MODULE */

NOT FAULT IN SYSTEM => ZONE 34 OUT 19.1;

If there is no fault in the system, output 1 on control module address 19 in zone 34will be activated.

Example 6:

The Salwico language can be used to replace a relay circuit.

UNMUTED FIRE IN SYSTEM : AD 60 S => FLAG 1;

( FLAG 1 ¦ FLAG 2 ) & FIRE IN SYSTEM => FLAG 2;

FLAG 2 => OUT 1.4.4;

If a detector alarm, anywhere in the system, is not muted within 60 seconds output4 on system module 4 in central 1 is made active, and it remains active until thedetector alarm is reset. The output is not activated if the fire alarm is muted within60 seconds. If a manual call point is made active output 4 on system module 4 incentral 1 is activated immediately. FLAG 2 becomes true when FLAG 1 becomestrue. FLAG 2 is true as long as FLAG 1 and FIRE IN SYSTEM are true.

Example 7:

Outputs initiated by system faults.

ZONE 2 SPR 50 FAULT 159 => OUT 1.4.6;

Output 6 on module 4 in central 1 will be activated if fault 159 (cable break) isreported from sprinkler address 50 in zone 2.

4.6.4 Management of External ControlsExample 8:



/* DOOR CLOSING GROUP 2 */

ZONE 51 SD 2 | ZONE 51 ALL 4-34 => OUT 1.2.2;

If there is a fire at detector 2 (at the smoke part) or address 4 to 34 (of any type) onzone 51, then output 2 on module 2 in central 1 will be activated.

Example 9:

/* FAN STOP ACCO */

ZONE 1 & ZONE 2 => OUT 1.4.5;

If there is a fire in zone 1 and in zone 2, then output 5 on module 4 in central 1 willbe activated.

Example 10:

If there is a fire alarm from the selected zones the outputs shall only be active aslong as the outputs are not muted.

(UNMUTED ZONE 1 | UNMUTED ZONE 2 ) => OUT 1.4.2;

A fire alarm in zone 1 or 2 makes output 2 active, and the output remains activeuntil all fire alarms are muted.

Example 11:

The output shall be active as long as there is a fire in the selected zones.

ZONE 3 | ZONE 4 => OUT 1.4.5;

A fire alarm in zone 3 or 4 makes output 5 on system module 4 in central 1 active,and the output remains active until all fire alarms are reset.

Example 12:

An output is made active after a specified time if the alarm is not muted.

UNMUTED ZONE 19 ADDRESS 22-30 : AD 60 S => OUT 1.4.6;

Output 6 on system module 4 in central 1 is activated if a detector alarm from zone19 address 22 - 30 is not muted within 60 seconds, and the output remains activeuntil the fire alarm is muted. The output is not activated if the detector alarm ismuted within 60 seconds. Output 6 on system module 4 in central 1 is activatedimmediately if a manual call point is activated.

Example 13:

An output is activated when a manual call point is activated anywhere in thesystem.

ZONE M.CALL => OUT 1.4.5;

Output 5 on system module 4 in central 1 is made active when a manual call pointis activated from anywhere in the system.



Example 14:

An output is activated when a detector, anywhere in the system, indicates a firealarm.

ZONE DET => OUT 1.4.6;

Output 6 on system module 4 in central 1 is made active when there is a fire alarmfrom any detector in the system (manual call points excluded).

Example 15:

An output is activated when one manual call point in a group of addresses isactivated.

ZONE 1 M.CALL 1-15 => OUT 1.4.5;

Output 5 on system module 4 in central 1 is made active when one of the manualcall points in the address interval is activated.

Example 16:

An output is activated when there is a fire alarm from one of the detectors in agroup of addresses.

ZONE 1 DET 1-15 => OUT 1.4.6;

Output 6 on system module 4 in central 1 is activated when one of the detectors inthe address interval is activated (manual call points excluded).

Example 17:

The output shall only be active when there are two or more detectors in alarm. Theoutput should not be active if there is only one detector in alarm.

ZONE 2 ADDRESS 5-20 > 1 => OUT 1.4.6;

Two or more detector alarms from zone 2 address 5 - 20 activate output 6 onsystem module 4 in central 1.

4.6.5 Management of Detectors from InputExample 18:

/* INHIBIT OF SMOKE DETECTORS ON CAR DECK 3 */

IN 1.4.1 => MESSAGE ZONE 2 SD 70-78 ON/OFF;

IN 1.4.1 => MESSAGE ZONE 2 SD 80-124 ON/OFF;

If input 1 on system module 4 is active then smoke detectors with addresses from70-78 and 80-124 in zone 2 are inhibited. When the input goes back to inactivestatus the smoke detectors become active again.



4.6.6 Other ExamplesExample 19:

/* IN 1.2.1 IS PRIORITY FOR GA-SIGNAL */

NOT IN 1.2.1 & UNMUTED FIRE IN SYSTEM : AD 120 S => OUT 1.4.4;

NOT IN 1.2.1 & UNMUTED FIRE IN SYSTEM :AD 240 S =>OUT 1.4.5;

Example 20:

/* NET FAULT OR BATTERY FAULT NORMALLY ACTIVATED */

NOT NET FAULT & NOT BATTERY FAULT => OUT 1.4.8;

Configuration Manual 5 The CCP Workbench


5 The CCP Workbench

5.1 About the CCP Workbench

5.1.1 IntroductionAn essential part of configuring a fire detection system is to specify its reaction forcertain events, for example what will happen when a manual call point is pressed.

To help you make these configurations we have developed the CCP Workbench.The CCP Workbench uses FBD (Function Block Diagram) which is a language forlogic supported by standard IEC 61131-3 for PLC (Programmable LogicController). The PLC can be chosen in Cause/Effect.

CAUTION!CCP Workbench has to be considered a special tool; you have to have this firstbefore you could do any changes to the configuration. In general to run the systembus on a public network will always be a great security threat and should beavoided. If a public network is used please consider a VPN solution or similar.

5.1.2 General Syntax and semantics OverviewLet us examine the nature of the FBD (Function Block Diagram) language. Thelanguage is based on the general form:

A function block diagram is a diagram that describes a function between inputvariables and output variables. A function is described as a set of elementaryblocks. Input and output variables are connected to blocks by connection lines. Anoutput of a block may also be connected to an input of another block:

Inputs and outputs of the blocks are wired together with connection lines, or links.Single lines may be used to connect two logical points of the diagram:

• A variable and an input of a block.

• An output of a block and an input of another block.

• An output of a block and a variable.

5 The CCP Workbench Configuration Manual


The connection is oriented, meaning that the line carries associated data from theoutput to the input.

The output of a block may have several connection lines attached, an input canonly have one.

Example

In this example we would like to read the state of a board input in the system. Weuse the pre-defined function: IsInputState, page 140. Assuming this is central 1,board 11 and input 3. If the input is active, the output parameter is TRUE,otherwise it's FALSE.



5.2 Workflow of configuration

Figure 87. Workflow of configuration.

The CCP Configuration program is used to define what boards, units etc arepresent and how they are connected in the system.

The CCP Workbench program is used to define the behaviour of the system i.e.which outputs should be activated under which circumstances.

The output from the CCP Configuration program is a .ccp file which contains thecomplete setup and is downloaded to all centrals in the system.

Both programmes runs on a PC in Windows environment.

5.2.1 DescriptionStart with the CCP Configuration program and describe “physically” the systemi.e. what boards, detectors, centrals etc. are present in the system and how they areconnected.



After this use the CCP Workbench program. Inside the CCP Configurationprogram it is possible to start the CCP Workbench program via a direct link in thecause/effect folder. After that the programming is done in the CCP Workbench;however the CCP Configuration program always generates the output for thesystem.

5.3 Starting CCP WorkbenchThe CCP Workbench is normally started from inside the CCP Configurationprogram.

It is also possible to start it from the “CCP Tools | CCP Workbench” programgroup in Windows.

5.3.1 ProjectsEach CCP Workbench project is stored under a project folder. In this folder theCCP Workbench stores all files connected to the project. The project folder has thesame name as the project name.

We recommend using the directory C:\Projects for your CCP projects. In this foldercreate a folder for each CCP project. Then in this directory save the file from theCCP Configuration program (.ccp) as well as your CCP Workbench project(directory).

Figure 88. Example directory.

In this example there are three CCP projects “Proj_1”, “Proj_2” and “Proj_3”.Under “Proj_1” the configuration file ( .ccp ) generated by the configurationprogram is saved. Here also the CCP Workbench project is stored in folderPLC_Proj_1.

NOTE!We strongly recommend using the hierarchy previously described, this because theCCP Configuration program uses files from the CCP Workbench. And the CCPWorkbench needs the CCP Configuration file.

5.3.2 Create a new CCP Workbench projectThere are several ways to start a new CCP Workbench project. Create an emptyone or base a new one on an existing project. In both cases it is assumed that theCCP Configuration file (.ccp) exist.



5.3.2.1 Create an empty project from the CCP ConfigurationprogramIn the CCP Configuration program under the Cause/Effect tab select PLC and thedirectory for the PLC Workbench project. Then select “Launch Workbench” ifthere is no project found at the selected path, CCP Configuration program offers tocreate a empty program.

Figure 89. The start screen.

Hint!An example project with a lot of different types of functions is installed togetherwith the program in C:\projects\CCP_Example, both for inspirational andcut-and-paste purposes.

Hint!It's possible to cut and paste (with Windows standard commands ctrl+c and ctrl+v)parts of one project to another. Just don't forget to also copy the variables.

5.3.2.2 Create an empty project from the CCP WorkbenchTo create an empty project from the CCP Workbench, follow the procedure below:

1 In Windows, start the CCP Workbench from the “CCP Tools | CCPWorkbench” program group.

2 When the program starts there is a dialog, select the “Create an emptyproject” and press OK.

3 When the Project Wizard is shown, select an empty project.

4 For the “Destination folder” select the same folder as where the .ccp file islocated.



5 Enter a project name, normally the same name as the for the .ccp filebeginning with an additional “PLC_”.

6 Press Next and the project is created and opened in the CCP Workbenchready for editing.

5.3.2.3 Create a new project based on an existing oneThis could be done in two different ways: From inside the CCP Workbench or inWindows file system.

5.3.2.3.1 From inside the CCP Workbench

1 In Windows, start the CCP Workbenchfrom the “CCP Tools | CCP Workbench”program group.

2 When the program starts there is a dialog,select the “Open a recent project” if theproject you want to base it on is in the list(if not press cancel), select it and press OK.

If cancel was selected, choose“File | Open Project | FromDisk” and open the projectyou want the new project tobe based on.

3 Choose “File | Save Project | As” to savethe current project (the one the new projectshould be based on) under a second name.

4 Select save as “Project”.

5 For the “Destination” select the same folderas where the .ccp file is located.

6 Enter a project name normally the samename as the for the <name>.ccp filebeginning with an additional “PLC_”.

7 Press OK and the project is created andopened in the CCP Workbench ready forediting.

5.3.2.3.2 From Windows file system

1 Copy the old CCP Workbench program <PLC_Proj_old> including all filesand subdirectories to the new CCP Project.

2 Change the name to the new project name <PLC_Proj_new> and start theCCP Workbench program from the CCP Configuration program.

NOTE!In most cases above; after closing the CCP Workbench the CCP Configurationprogram needs to be updated with the link to the new CCP Workbench project.

NOTE!When coping projects the build number (used mainly for version control) continuesfrom its current position.



5.4 Start program PLC code

5.4.1 Create a program in your CCP Workbench project1 Select “File | New Program”.

2 Enter a program name, description andselect “FBD – Functional block diagram”.

FBD is the program languagesupported in CCP.

3 Press OK. The new program is nowshown to the left in a treeview of the “Workspace”window.

4 Double click on the program name in the“Workspace” window.

The program opens and isnow ready for editing in thecentre window.

Figure 90. Start new program window.

All functions are entered as blocks into the program. CCP has a number of specificblocks that are found in the “Block Selection” window to the right. The CCPblocks are grouped into groups named CCP IO, CCP Fire etc.

To enter a block in the editor window from the “Block Selection” list, mark theblock in the list and drag and drop it into the wanted position in the editor window.

5.4.2 Explanation of a FBD diagram

Figure 91. FBD diagram.



The example above contains two blocks, IsFireType, page 137 and SetOutput,page 142. The “IsFireType” and its parameters TYPE_SMOKE andSEL_UNMUTED means that the “IsFireType” block will search for a fire alarm oftype “Smoke” that are un-muted in the system. If one (or several) alarm(s) of thistype are found, it will return true on the Q output. The Q output is then connectedto the condition input on the “SetOutput” block.

The “SetOutput” and its parameters 1, 5, 7, PATTERN_STEADY and Q (Cond)means that an output will be activated/deactivated in central 1 on board withaddress 5 and output number 7. Activation or deactivation depends on Q (Cond).There will be no pattern on output since PATTERN_STEADY is used, the outputwill be solely on or off. The Q output on the “SetOutput” block is not used but hasto be connected to a dummy variable in order to avoid compiler errors.

5.5 Making application codeWhen all changes are made, it is necessary to generate the application code for theproject. This is done by selecting the menu “Project | Build Project”.

All programs in the projects are now compiled. If there is an error in thecompilation process this is shown in the “build window”. For most errors it ispossible to double-click on the message and go to the place, i.e. program – blockwhere the error was generated.

When the compilation process is error free the program asks if it should perform acheck for double defined outputs (i.e. two blocks writing to the same output), andthat the used outputs are defined in the system.

Figure 92. Output check window.

If yes is chosen, the program needs to know which .ccp file to check against. Forthis to work it is necessary that there have been a file saved in the CCPConfiguration program that have the correct link to the CCP Workbench project.

Any double defined output or usages of undefined outputs are shown as warningsin the build window. Even if there are warnings there is an output generated.However please consider twice before running it, undefined outputs are generallyok to have in the program but double defined should definately be fixed.

Hint!Due to the very structure of a PLC language, like a parameter to a block could bechanged at runtime. These checks never cover all cases but for normal usage theyare very helpful.



5.5.1 Output FilesInformation for the advanced user:

The output files after a successful compilation are stored in <PLC_Proj>\CCP.There are two files created, t5.cod which is the compiled PLC code and the t5.xmlwhich is a copy of the complete project. These files are then used by the CCPConfiguration program when building the .ccp file which is the final output to bedownloaded to the system.

5.6 Going online with the CCP WorkbenchCAUTION!CCP Workbench has to be considered a special tool. In general to run the systembus on a public network will always be a great security threat and should beavoided. If a public network is used please consider a VPN solution or similar.

The CCP Workbench has a very powerful debug function. To use this feature it isnecessary to go online with a network connection to the fire alarm panel. Thesimplest way to do this is to have an USB-Ethernet adapter. (D-link has oneDUB-E100 that works with most Windows versions). Set up this adapter to use theIP-adress (computer side) 192.168.200.160 and mask 255.255.255.0.

It is of course also possible to use any built in network adapter in the PC. Howeveryou have to change the settings every time you want to connect to a differentnetwork. In some versions of windows there is also the possibility to set up analternative IP-address that could be used.

The master fire alarm central normally have the IP address 192.168.200.161 but itcould have been set up differently in the CCP Configuration program. Enter the IPaddress of the fire alarm central to connect to, in the CCP Workbench. It is done inthe menu “Tools | Communication parameters” and select it. The selected IPaddress is now shown in the status bar in the bottom right of the CCP Workbench.Connect a network cable from the fire alarm panel (connector at the back) to theUSB-Ethernet adapter (or network adapter).

Press (On line) in the CCP Workbench to go online.

NOTE!When doing online changes it is only the central and board (CM) connected thatreceives the changes. So please carefully consider this. Normally it is logical toconnect to a board that is master and “owns” the outputs currently debugged. Ifyou are debugging a central which has a redundancy CM installed it could be agood idea to turn this CM of during the debug phase.

NOTE!When ready with online changes, the CCP Configuration program has to beupdated and a new .ccp file saved and downloaded to the system. If this is not doneall changes will be lost after the next restart.



5.7 Simulate the project in the CCP WorkbenchThere is no simulation possibility for the CCP blocks in the CCP Workbench.However it is possibly to compile a CCP project error free for the Workbenchsimulator. Thereby it is possible to simulate all logic around the CCP blocks i.e.most PLC standard blocks.

Press (Simulation) in the CCP Workbench to start simulation.

5.8 Performance tricksIn very large systems with many centrals performance could be slightly improvedby some simple considerations.

Any output in the system is in reality only activated by the central that physically“owns it” (physically connected to). All centrals in the system are running the samePLC code. It is therefore in some centrals not necessary to run the PLC code forcertain outputs.

There is a CCP block, ThisCentral, page 149, that returns the central numberwhere the PLC code currently is executed. A suggestion is to write a PLC“sub-program” for each central. Then in the beginning of each “sub-program” testif “ThisCentral” is equal to the central where the outputs are “located”, if not stopexecution of this “sub-program” and continue with next. To achieve this, use"jump" and "label".

5.9 Execution orderIn most PLC programs the execution order (i.e. in what order blocks, variables etc.are evaluated) is of low importance. If something is not done in the currentprogram loop it will be done the next time the program runs. However there aresituations where both the response time and/or the function of the program arecrucially depending upon the execution order.

Generally you could say that a FBD program is evaluated left to right, top tobottom. To help the user determine the execution order there is a tool in the toolbarin the FDB editor.

Press (Show execution order) in the toolbar on the left side of the editorwindow and the numbered execution order are shown in the FDB editor.

5.10 BackupIf you follow the previous instructions and default locations you need only to makea backup of “C:\Projects” and all of its contents. A daily backup procedure isstrongly recommended.

5.11 Other sources of documentationThe CCP workbench has a thorough online documentation. Press F1 in the CCPWorkbench to access the help. Besides this there are numerous of books and



documents about PLC (IEC 61131-3) programming. A good starting point could behttp://www.plcopen.org/.

5.12 RAQ – Rarely asked questions

5.12.1 Ooops… I need an old version of my CCPWorkbench project?Every time the project is built without compiler errors a copy of the current projectis saved in the <PLC_proj>\Backup folder. The complete project is saved in .xmlfile format. At the end of each file name a build number is also added.

If you want to open an old backup copy please select “File | New Project | XMLimport” from the CCP Workbench.

NOTE!You have to create a new project (with a new name (or place)) from the backupfile. Please see Create a new project based on an existing one, page 122 for moreinformation.

5.12.2 I need support what files to enclose?Please enclose the current .ccp file together with your email request describing theproblem in detail. If the project do not compile error free do an .xml export “Tools |Export | Project XML” and enclose it.

5.12.3 I am desperately low on disk space!?Simply remove the contents of the <PLC_proj>\Backup folder. Of course after thisthere is no possibility to open older versions of your project.

5.12.4 I have arrived at a system without anyconfiguration files!?Download the current .ccp file from the system with the help of an USB stick.Place the .ccp file on your PC in a project folder and open it as shown below.

1 In the CCP Configuration program under the Cause/Effect tab select PLCand the directory for the PLC Workbench project.

2 Select “Extract project files from configuration” and the necessary files areextracted.

3 Select “Launch Workbench” and the Workbench is started with theextracted files.

NOTE!Before leaving the system create backups and distribute them.



5.13 Predefined CCP blocks

5.13.1 GeneralThis chapter describes the basic function of the predefined CCP blocks delivered asstandard with the CCP fire alarm system.

5.13.1.1 Input parametersIf nothing else is stated.

Table 41. Input parameters

Parameter Range ExplanationCent: 1-30 Central addressBoard: 1-125 Board address within a centralIO: 1-255 Input number/ Output numberType: 0-255 See defined device types in CCP WorkbenchFlag: 1-999 Flag numberFault: 0-255 See defined fault codes in CCP WorkbenchWarn: 0-255 Follows basically the fault codesZone: 0-64999 The logical zone numberZoFr: 1-64999 The logical zone number from (and including)ZoTo: 1-64999 The logical zone number to (and including)Adr: 0-9999 The logical loop unit addressAdrFr: 1-9999 The logical loop unit address from (and including)AdrTo: 1-9999 The logical loop unit address to (and including)Sel: 1-3 1 = Select unmuted alarms (SEL_UNMUTED)

2 = Select muted alarms (SEL_MUTED)3 = Select all alarms (SEL_ALL)

Cond: True/False This is the switch for enable/disable outputsdisablements etc.

When 0 is a valid expression, it's treated as a wildcard, covering the whole range.

5.13.1.2 Output parametersIf nothing else is stated.

Table 42. Output parameters

Parameter Range Explanation

Q: True/False Function resultNo: 1-64999 Number of counted alarms etc.

5.13.1.3 Functions vs. function blocksThere are two kinds of blocks: 1. Functions and 2. Function blocks.



1. A function calculates a result according to the current value of its inputs. Unlikea function block, a function has no internal data and is not linked to declaredinstances. A function has only one output: the result of the function.

2. To use a function block, you have to declare an instance of the block as avariable, identified by a unique name. Each instance of a function block has itsown set of private data and can be called separately. A call to a function blockinstance processes the block algorithm on the private data of the instance, usingthe specified input parameters.

The user also has the possibility to create user defined blocks in the CCPWorkbench. These blocks could contain a subset of the predefined CCP blocks.Please refer to the workbench online manual for more information about this underthe section: “IEC 61131-3 Programming Environment -> Libraries -> Libraries ofsub-programs and UDFBs”

5.13.2 CCP Disablements sectionIf for example a search key of “TYPE_ALL” is used and there is a disablement inthe list of type “TYPE_SMOKE” this will not return a match.

However if example a search key of “TYPE_SMOKE” is used and there is adisablement in the list of type “TYPE_ALL” this will return a match. The functionis done in this way to make sure when there is a match that the unit is disabled.

5.13.2.1 DisaCeBoIoDisable a board output.

Function name: DisaCeBoIoInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: IOInput parameter: BOOL: CondOutput parameter: BOOL: Q

Output parameter follows the condition input.

NOTE!Please take care that the selected IO is defined as an output in the configurationprogram.

Related command: IsDisaCeBoIo, page 131

5.13.2.2 DisaCentTypeDisable a type on a central level.

Function name: DisaCentTypeInput parameter: UINT: CentInput parameter: UINT: TypeInput parameter: BOOL: Cond



Function name: DisaCentTypeOutput parameter: BOOL: Q


Example of “Type” parameter: TYPE_ALARM_DELAY

NOTE!Currently only one type is implemented.

Related command: IsDisaCentType, page 131

5.13.2.3 DisaTypeDisable board output(s) of a certain type in the entire system.

Function name: DisaTypeInput parameter: UINT: CentInput parameter: UINT: TypeInput parameter: BOOL: CondOutput parameter: BOOL: Q


Valid "Type" parameters:TYPE_OUTPUT_GRP:TYPE_OUTPUT_DOOR:TYPE_OUTPUT_FIRE:TYPE_OUTPUT_FAULT:TYPE_OUTPUT_VENT:TYPE_OUTPUT_INDICATION:TYPE_OUTPUT_BELL:TYPE_OUTPUT_ATRANS:TYPE_OUTPUT_FIRM

NOTE!A central must be selected where the action is performed. However thedisablement is global and distributed to all centrals.

Related command: IsDisaType, page 131

5.13.2.4 DisaZoAdAdTyDisable loop unit(s) of a certain type within an address interval.

Function name: DisaZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: Type



Function name: DisaZoAdAdTyInput parameter: BOOL: CondOutput parameter: BOOL: Q


Related command: IsDisaType, page 131

5.13.2.5 IsDisaCeBoIoReads disablements for a board output.

Function name: IsDisaCeBoIoInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: IOOutput parameter: BOOL: Q

Output parameter returns true if the output is disabled.

NOTE!If the IO parameter is equal to zero there is a search for a disablement of acomplete board only.

Related command: DisaCeBoIo, page 129

5.13.2.6 IsDisaCentTypeChecks if there are disablements for a “type”. This is done on a central level.

Function name: IsDisaCentTypeInput parameter: UINT: CentInput parameter: UINT: TypeOutput parameter: BOOL: Q

Output parameter returns true if the type is disabled in the central.

Example of “Type” parameter: TYPE_ALARM_DELAY

NOTE!Currently only one type is implemented.

Related command: DisaCentType, page 129

5.13.2.7 IsDisaTypeReads disablements for a type.

Function name: IsDisaTypeInput parameter: UINT: TypeOutput parameter: BOOL: Q



Output parameter returns true if there is the type is disabled.

NOTE!If type TYPE_OUTPUT_GRP is used, the function will return true ifTYPE_OUTPUT_GRP is disabled (controls off) and/or if any of the followingcategories are disabled; TYPE_OUTPUT_DOOR, TYPE_OUTPUT_FIRE,TYPE_OUTPUT_FAULT, TYPE_OUTPUT_VENT orTYPE_OUTPUT_INDICATION.

Related command: DisaType, page 130

5.13.2.8 IsDisaZoAdAdTyReads disablements for a type within an address interval in a zone.

Function name: IsDisaZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeOutput parameter: BOOL: Q

Output parameter returns true if the whole specified interval is disabled.

Since the whole interval must be covered it can sometimes be a good idea to dividethe search into several separate blocks.

Related command: DisaZoAdAdTy, page 130

5.13.2.9 IsDisaZoTypeReads disablements for a type within a zone.

Function name: IsDisaZoTypeInput parameter: UINT: ZoneInput parameter: UINT: TypeOutput parameter: BOOL: Q

Output parameter returns true if at least one unit of the correct type in the zone isdisabled.

NOTE!There is no related command such as “DisaZoZoType”. If needed to disable severalzones, several calls to example “DisaZoAdAdTy” has to be made.

Related command: DisaZoAdAdTy, page 130

5.13.2.10 NoDisaZoAdAdTyReads the number of disablements in the system for a type within a zone and withan address interval.



Function name: NoDisaZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeOutput parameter: UINT: No

Output parameter returns the number of matched disablements in the system.

NOTE!When all in parameters are set to zero the output parameter will return the totalnumber of disablements in the system.

Related commands: ---

5.13.2.11 SensZoAdAdTySets sensitivity for detector(s) of a certain type within in an address interval in azone.

Function name: SensZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeInput parameter: UINT: SensOutput parameter: BOOL: Q


Example of “Sens” parameter: CMD_HIGH_SENSITIVITY_AUTO

NOTE!This function will override the sensitivity set in the Configuration program.

Related command: ---

5.13.3 CCP Fault alarm sectionIn general for all search operations for the fault alarms (Is….. blocks). There is thepossibility to set the “Fault” input to zero. This is then treated as a wildcard andwill match all fault types in the system.

5.13.3.1 FaultMuteGlobalMutes all un-muted fault alarms in the system.

Function block name: FaultMuteGlobalInput parameter: BOOL: MuteOutput parameter: BOOL: Q



This is done once when the “Mute” input is activated (positive flank). The functionis enabled again after the “Mute” input has been low for at least one PLC cycle.

The output parameter is not used.

Related command: FaultUnMuGlobal, page 134

5.13.3.2 FaultResGlobalResets all resettable faults in the system.

Function block name: FaultResGlobalInput parameter: BOOL: ResetOutput parameter: BOOL: Q

This is done once when the “Reset” input is activated (positive flank). The functionis enabled again after the “Reset” input has been deactivated for at least one PLCcycle.



5.13.3.3 FaultUnMuGlobalUn-mutes all muted fault alarms in the system.

Function block name: FaultUnMuGlobalInput parameter: BOOL: UnMuteOutput parameter: BOOL: Q

This is done once when the “UnMute” input is activated (positive flank). Thefunction is enabled again after the “UnMute” input has been low for at least onePLC cycle.


Related command: FireMuteGlobal, page 136

5.13.3.4 IsFaultCeBoIoChecks for a fault on a board.

Function name: IsFaultCeBoIoInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: IOInput parameter: UINT: FaultInput parameter: UINT: SelOutput parameter: BOOL: Q

Output parameter returns true if there is a matching fault in the system.



With IO set to 0 the function checks the whole board for the specified fault. If Faultis set to 0 it checks for any fault.


5.13.3.5 IsFaultTypeChecks for a fault on a specific unit type in the system.

Function name: IsFaultTypeInput parameter: UINT: TypeInput parameter: UINT: FaultInput parameter: UINT: SelOutput parameter: BOOL: Q


The parameter "Type" can be set to 0. In that case it checks every unit type in thesystem. The parameter "Fault" can also be set to 0, in that case it checks for anykind of fault. Setting both to 0 means that the function will detect any fault in thesystem, similar to the "FAULT IN SYSTEM" function in the Salwico language.


5.13.3.6 IsFaultZoAdAdTyChecks for a fault on a specific unit type within an address interval.

Function name: IsFaultZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeInput parameter: UINT: FaultInput parameter: UINT: SelOutput parameter: BOOL: Q



5.13.3.7 IsFaultZoZoTypeChecks for a fault on a specific unit type within an address interval.

Function name: IsFaultZoZoTypeInput parameter: UINT: ZoFrInput parameter: UINT: ZoToInput parameter: UINT: TypeInput parameter: UINT: FaultInput parameter: UINT: Sel



Function name: IsFaultZoZoTypeOutput parameter: BOOL: Q



5.13.4 CCP Fire alarm section5.13.4.1 FireMuteGlobalMutes all un-muted fire alarms in the system.

Function block name: FireMuteGlobalInput parameter: BOOL: MuteOutput parameter: BOOL: Q

This is done once when the “Mute” input is activated (positive flank). The functionis enabled again after the “Mute” input has been low for at least one PLC cycle.


NOTE!One and only one instance of this function block is allowed in a system.

NOTE!This is a function block and needs a variable to hold its status.

Related command: FireUnMutGlobal, page 137

5.13.4.2 FireResetGlobalResets all resettable fire alarms in the system.

Function block name: FireResetGlobalInput parameter: BOOL: ResetOutput parameter: BOOL: Q

This is done once the “Reset” input is activated (positive flank). The function isenabled again after the “Reset” input has been deactivted for at least one PLCcycle.



NOTE!This is a function block and needs a variable to hold its status.




5.13.4.3 FireUnMutGlobalUn-mutes all muted fire alarms in the system.

Function block name: FireUnMutGlobalInput parameter: BOOL: UnMuteIOutput parameter: BOOL: Q

This is done once when the “UnMute” input is activated (positive flank). Thefunction is enabled again after the “UnMute” input has been low for at least onePLC cycle.

Output parameter is not used.


NOTE!This is a function block and needs a variable to hold its block status.

Related command: FireMuteGlobal, page 136

5.13.4.4 IsFireTypeChecks for fire alarms from a specific unit type.

Function name: IsFireTypeInput parameter: UINT: TypeInput parameter: UINT: SelOutput parameter: BOOL: Q

Output parameter returns true if there is a matching fire in the system.

NOTE!Parameter “Type” equal to zero (0) is a special case. The function will then detectany fire in the system. Similar to the “FIRE IN SYSTEM” function in the Salwicolanguage.

Related command: NoFireType, page 138

5.13.4.5 IsFireZoAdAdTyChecks for fire alarms from a specific unit type within an address interval.

Function name: IsFireZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeInput parameter: UINT: SelOutput parameter: BOOL: Q




Related command: NoFireZoAdAdTy, page 138

5.13.4.6 IsFireZoZoTypeChecks for fire alarms from a specific unit type within a zone address interval.

Function name: IsFireZoZoTypeInput parameter: UINT: ZoFrInput parameter: UINT: ZoToInput parameter: UINT: TypeInput parameter: UINT: SelOutput parameter: BOOL: Q


Related command: NoFireZoZoType, page 139

5.13.4.7 IsFireXCentralChecks for any fireX alarm in the system. FireX also known as the Basic Alarm isthe hardware alarm function in the backbone bus.

Function name: IsFireXCentralInput parameter: UINT: CentInput parameter: UINT: SelOutput parameter: BOOL: Q

Output parameter returns true if there is a FireX alarm in the system.

NOTE!The input parameter “Cent” is not used (it could be any value). It is only forcompatibility reasons. FireX always search any fireX alarm in the system.


5.13.4.8 NoFireTypeChecks the number of fire alarms from a specific unit type.

Function name: NoFireTypeInput parameter: UINT: TypeInput parameter: UINT: SelOutput parameter: UINT: No

Output parameter returns the number of alarms.

Related command: IsFireType, page 137

5.13.4.9 NoFireZoAdAdTyReads the number of fire alarms for a specific unit type within an address interval.



Function name: NoFireZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeInput parameter: UINT: SelOutput parameter: UINT: No


Related command: IsFireZoAdAdTy, page 137

5.13.4.10 NoFireZoZoTypeReads the number of fire alarms for a specific unit type within a zone addressinterval.

Function name: NoFireZoZoTypeInput parameter: UINT: ZoFrInput parameter: UINT: ZoToInput parameter: UINT: TypeInput parameter: UINT: SelOutput parameter: UINT: No


Related command: IsFireZoZoType, page 138

5.13.5 CCP IO section5.13.5.1 IsCentralVIOReads the value of a central VIO flag.

Function name: IsCentralVIOInput parameter: UINT: CentInput parameter: UINT: FlagOutput parameter: BOOL: Q

Output parameter returns the status of the corresponding central VIO flag.

NOTE!The statuses of the central VIO flags are distributed within each central only.Therefore it is possible to read a central VIO flag only in the same central as whereit has been set.

Related command: SetCentralVIO, page 141

5.13.5.2 IsGlobalVIOReads the value of a global VIO flag.



Function name: IsGlobalVIOInput parameter: UINT: FlagOutput parameter: BOOL: Q

Output parameter returns the status of the corresponding global VIO flag.

NOTE!GlobalVIO is the VIO type that the custom keys in the panels use.

NOTE!The status of the global VIO flags are distributed to all centrals in the system.

Related command: SetGlobalVIO, page 142

5.13.5.3 IsInputStateReads the state of a board input in the system.

Function name: IsInputStateInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: IOOutput parameter: BOOL: Q

Returns true if the input is active.


5.13.5.4 IsKeyActivatedReads the state of the key input on a control panel.

Function name: IsKeyActivatedInput parameter: UINT: CentInput parameter: UINT: BoardOutput parameter: BOOL: Q

Returns true if the key is turned.

NOTE!Only used in industrial applications.


5.13.5.5 IsLoopInputReads the state of a loop unit input in the system.

Function name: IsLoopInputInput parameter: UINT: ZoneInput parameter: UINT: Adr



Function name: IsLoopInputInput parameter: UINT: IOOutput parameter: BOOL: Q

Returns true if the input is active.


5.13.5.6 IsLoopOutputStaReads the state of a loop unit output in the system.

Function name: IsLoopOutputStaInput parameter: UINT: ZoneInput parameter: UINT: AdrInput parameter: UINT: IOOutput parameter: BOOL: Q

Returns true if the output is active.

NOTE!After changing the status of a loop output. There could be several PLC cyclesbefore “IsLoopOutputSta” reflects the same status. This due to the time needed forloop communication.

Related command: SetLoopZoAdTy, page 142

5.13.5.7 IsOutputStateReads the state of a board output in the system.

Function name: IsOutputStateInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: IOOutput parameter: BOOL: Q

Returns true if the output is active.

Related command: SetOutput, page 142 and SetOutputInt, page 143

5.13.5.8 SetCentralVIOSets a central VIO flag.

Function name: SetCentralVIOInput parameter: UINT: CentInput parameter: UINT: FlagInput parameter: BOOL: CondOutput parameter: BOOL: Q



Output follows the condition input.

NOTE!The statuses of the central VIO flags are distributed within each central only.Therefore it is possible to read a central VIO flag only in the same central as whereit has been set.

Related command: IsCentralVIO, page 139

5.13.5.9 SetGlobalVIOSets a global VIO flag.

Function name: SetGlobalVIOInput parameter: UINT: CentInput parameter: UINT: FlagInput parameter: BOOL: CondOutput parameter: BOOL: Q

Output follows the condition input.

NOTE!GlobalVIO is the VIO type that the custom keys in the panels use.

NOTE!The status of the global VIO flags are distributed to all centrals in the system.

Related command: IsGlobalVIO, page 139

5.13.5.10 SetLoopZoAdTyActivates a loop unit output of a certain type.

Function name: SetLoopZoAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrInput parameter: UINT: SubInput parameter: UINT: MaskInput parameter: UINT: TypeInput parameter: BOOL: CondOutput parameter: BOOL: Q

Valid “Type” parameter: TYPE_LOOP_IO:


Related command: IsLoopOutputSta, page 141

5.13.5.11 SetOutputActivates a board output.



Function name: SetOutputInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: IOInput parameter: UINT: PattInput parameter: BOOL: CondOutput parameter: BOOL: Q


Related command: IsOutputState, page 141

5.13.5.12 SetOutputIntActivates an interval of board outputs.

Function name: SetOutputIntInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: IoFrInput parameter: UINT: IoToInput parameter: UINT: PattInput parameter: BOOL: CondOutput parameter: BOOL: Q


NOTE!Maximum eight (8) outputs in an interval.

Related command: IsOutputState, page 141

5.13.5.13 SetPanelLEDActivates a LED on a control panel CM 4.3.

Function name: SetPanelLEDInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: LEDInput parameter: BOOL: RedInput parameter: BOOL: YellInput parameter: BOOL: FlashInput parameter: BOOL: CondOutput parameter: BOOL: Q

Input parameters LED 1 - 4.





5.13.6 CCP Miscellaneous section5.13.6.1 AlarmLimitRoRSets the Alarm limit and the rate of rise derivation on some specific detectors.

Function block name: AlarmLimitRoRInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeInput parameter: UINT: AlimInput parameter: UINT: RoRInput parameter: UINT: CondOutput parameter: BOOL: Q

Description

Rate of Rise functionallity allows for setting of a different alarm threshold andtemperature rise threshold for heat detectors. By using AlarmLimitRoR blocks it ispossible to vary the temperature threshold between 30 - 84 deg Celcius and set thealarm to trigger when the temperature rise is between 3 to 7 deg Celcius perminute.

CAUTION!Maximum limit to be set for heat rise is 7 degree Celsius per minute.

Detector Support

The following detectors are supported by this function:

• CN/EV-H

• CN/EV-PH

• NS-AH

• NS-AOHS

Input parameters

Alim - Heat alarm threshold in tenths of degrees Celcius (300 – 840).

RoR - Heat rise alarm threshold in tenths of degrees Celcius (30 – 70).

Block function

The new parameters are loaded on “Cond” positive flank. The old parameters areloaded back again on “Cond” negative flank.

NOTE!Change of input values are only allowed when “Cond” is false.



NOTE!Take care not to define overlapping intervals between different AlarmLimitRoRblocks. If this is done, the system may become choked by setting and clearing Rateof Rise rules each PLC run. This will result in chaotic/unpredictable systembehaviour.


5.13.6.2 BuzzerLocalOffNOTE!This function is not implemented name is only reserved for future use.

Table 43.

Function block name: BuzzerLocalOffInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: BOOL: CondOutput parameter: BOOL: Q

NOTE!This function is not implemented name is only reserved for future use.

Related command: BuzzerOff, page 145

5.13.6.3 BuzzerOffNOTE!This function is not implemented name is only reserved for future use.

Function name: BuzzerOffInput parameter: UINT: CentInput parameter: BOOL: CondOutput parameter: BOOL: Q


Related command: BuzzerLocalOff, page 145

5.13.6.4 CcpStatusThis block is only used in combination with customer specific protocols.

Function name: CcpStatusInput parameter: UINT: RegNrInput parameter: UINT: BitNrInput parameter: BOOL: BitStOutput parameter: BOOL: Q

Please refer to separate train protocols documentation for usage of this block.



Related command: CcpStatusByte, page 146

5.13.6.5 CcpStatusByteThis block is only used in combination with customer specific protocols.

Function name: CcpStatusByteInput parameter: UINT: RegNrInput parameter: UINT: RegValOutput parameter: BOOL: Q


Related command: CcpStatus, page 145

5.13.6.6 GetAdTimesGets the changeable alarm delay times from a central.

Function block name: GetAdTimesInput parameter: UINT: CentInput/Output parameter: TIME: MuteInput/Output parameter: TIME: ResetOutput parameter: BOOL: Q

Output always returns true.

NOTE!The Mute and Reset parameters must be connected to a variable before connectedto any other block.

Related command: DisaCentType, page 129

5.13.6.7 IsCentralBootedNOTE!This function is not implemented name is only reserved for future use.

Function block name: IsCentralBootedInput parameter: UINT: CentOutput parameter: BOOL: Q

Output returns true if all boards in configuration within central are up and running(booted) else false.



5.13.6.8 IsMasterCheck if the running board is master.



Function name: IsMasterOutput parameter: BOOL: Q

Output parameter returns true if the running board (Control M) is master.

NOTE!One and only one Control M board within a central is master at a time.

NOTE!This function is mainly to check if the board you have connected to is the master.

Related command: ThisCentral, page 149 and ThisBoard, page 149

5.13.6.9 MiniRepeaterHandles the MiniRepeaters of type RepeaterM. Often used in combination with thealarm delay function.

Function name: MiniRepeaterInput parameter: UINT: CentInput parameter: BOOL: BlockInput parameter: BOOL: SpareOutput parameter: BOOL: MutBut

At a fire alarm the mini-repeaters will display the alarm and sound the buzzer.When the user mutes the alarm, the output “MutBut” will be activated. At any timeit is possible to block the mini-repeater by activating the “Block” input. When the“Block” input is activated it is no longer possible to reset any alarms from theRepeaterM and the Larmorg Transfer button lights up. Spare is not used.


5.13.6.10 MiniRepeaterMNHandle the MiniRepeaters of type MN30X0. Often used in combination with thealarm delay function.

Function name: MiniRepeaterMNInput parameter: UINT: CentInput parameter: BOOL: BlockInput parameter: BOOL: SpareOutput parameter: BOOL: MutBut

At a fire alarm the mini-repeaters will display the alarm. When the user mutes thealarm the output “MutBut” will be activated.

At any time it is possible to block the mini-repeater by activating the “Block”input. When the “Block” input is activated it is no longer possible to reset anyalarms from the MN30X0.

For the MN30X0 most outputs have to be set by the PLC specifically as follows;



Output MN3000 MN3010x.y.1 Operational Operational----- More alarms More alarmsx.y.3 Muted ------------x.y.4 Fire brigade called ------------x.y.5 Out 1 Out 1x.y.6 Out 2 Out 2x.y.7 Out 3 + internal buzzer (1 Hz) Out 3 + internal buzzer (1 Hz)


5.13.6.11 NewCmProfileChanges the show/control privileges on a specific control module.

Function name: NewCmProfileInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UDINT: ShowInput parameter: UDINT: ContInput parameter: BOOL: CondOutput parameter: BOOL: Q

The system changes the default show and control masks of the control module(CM) with address [Cent] and [Board]. The address [Cent] and [Board] must be anaddress of a configured CM.

The [Show] and [Cont] are numbers in either decimal or hexadecimal. Forhexadecimal numbering use the prefix '0x' (i.e.. 0xABCDEF). The [Show] and[Cont] numbers are used as bitmasks, where a bit identifies a group specified in theCCP Conf program. A set bit indicates that the mask includes the group.

There are a maximum of 32 groups in the system. The group number from CCPConf identifies the bit position representing the group.

To create a mask including groups 1, 7, 8, 20 and 27 use the approach below:

Group number Corresponding 32 bit binary valueGroup 1: 0000 0000 0000 0000 0000 0000 0000 0001Group 7: 0000 0000 0000 0000 0000 0000 0100 0000Group 8: 0000 0000 0000 0000 0000 0000 1000 0000Group 20: 0000 0000 0000 1000 0000 0000 0000 0000Group 27: 0000 0100 0000 0000 0000 0000 0000 0000

Sum: 0000 0100 0000 1000 0000 0000 1101 0001Hex: 0 4 0 8 0 0 D 1



Use value [Show = 0x040800D1] and [Cont = 0x040800D1] for making the CMwith address [Cent] and [Board] have show and control privileges in groups 1, 7, 8,20 and 27.

The new show and control masks are in use when "Cond" is true. When the “Cond”is false the show and control masks defined in configuration are set.

5.13.6.12 TcmsStatusThis block is only used in combination with customer specific protocols.

Function name: TcmsStatusInput parameter: UINT: RegNrInput parameter: UINT: BitNrOutput parameter: UINT: BitSt


Related command: TcmsStatusByte, page 149

5.13.6.13 TcmsStatusByteThis block is only used in combination with customer specific protocols.

Function name: TcmsStatusByteInput parameter: UINT: RegNrOutput parameter: UINT: RegVal


Related command: TcmsStatus, page 149

5.13.6.14 ThisBoardGet the running boards address.

Function name: ThisBoardOutput parameter: UINT: Board

Output parameter returns the board address for the board running the PLC.

Related command: ThisCentral, page 149

5.13.6.15 ThisCentralGet the central address where the CM board is running the PLC.

Output parameter returns the central adress where the PLC runs.

Function name: ThisCentralOutput parameter: UINT: Cent

Related command: ThisBoard, page 149



5.13.7 CCP Pre-alarm section5.13.7.1 IsPreTypeReads the pre alarms for a specific unit type.

Function name: IsPreTypeInput parameter: UINT: TypeOutput parameter: BOOL: Q

Output parameter returns true if there is a matching pre alarm in the system.

Related command: NoPreType, page 150

5.13.7.2 IsPreZoAdAdTyReads pre alarms for a specific unit type within an address interval.

Function name: IsPreZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeOutput parameter: BOOL: Q


Related command: NoPreZoAdAdTy, page 151

5.13.7.3 IsPreZoZoTypeReads pre alarms for a specific unit type within a zone address interval.

Function name: IsPreZoZoTypeInput parameter: UINT: ZoFrInput parameter: UINT: ZoToInput parameter: UINT: TypeOutput parameter: BOOL: Q


Related command: NoPreZoZoType, page 151

5.13.7.4 NoPreTypeReads the number of pre alarms for a specific unit type.

Function name: NoPreTypeInput parameter: UINT: TypeOutput parameter: UINT: No

Output parameter returns the number of pre alarms.



Related command: IsPreType, page 150

5.13.7.5 NoPreZoAdAdTyReads the number of pre alarms for a specific unit type within an address interval.

Function name: NoPreZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeOutput parameter: UINT: No


Related command: IsPreZoAdAdTy, page 150

5.13.7.6 NoPreZoZoTypeReads the number of pre alarms for a specific unit type within a zone addressinterval.

Function name: NoPreZoZoTypeInput parameter: UINT: ZoFrInput parameter: UINT: ZoToInput parameter: UINT: TypeOutput parameter: UINT: No


Related command: IsPreZoZoType, page 150

5.13.8 CCP Warning-alarm section5.13.8.1 IsWarnCeBoIoReads warnings for a board IO.

Function name: IsWarnCeBoIoInput parameter: UINT: CentInput parameter: UINT: BoardInput parameter: UINT: IOInput parameter: UINT: WarnOutput parameter: BOOL: Q

Output parameter returns true if there is a matching warning in the system.


5.13.8.2 IsWarnTypeReads warnings for a specific unit type in system.



Function name: IsWarnTypeInput parameter: UINT: TypeInput parameter: UINT: WarnOutput parameter: BOOL: Q



5.13.8.3 IsWarnZoAdAdTyReads warnings for a specific unit type within an address interval.

Function name: IsWarnZoAdAdTyInput parameter: UINT: ZoneInput parameter: UINT: AdrFrInput parameter: UINT: AdrToInput parameter: UINT: TypeInput parameter: UINT: WarnOutput parameter: BOOL: Q



5.13.8.4 IsWarnZoZoTypeReads if there is a specific warning for a unit type, within an address interval.

Function name: IsWarnZoZoTypeInput parameter: UINT: ZoFrInput parameter: UINT: ZoToInput parameter: UINT: TypeInput parameter: UINT: WarnOutput parameter: BOOL: Q



5.13.9 Migrate from Salwico language to PLCThis is a list that could be helpful when migrating from the Salwico language to theCCP Workbench PLC.

Inputs

Salwico language expression Primary Workbench function Secondary Workbench functionsFIRE IN SYSTEM IsFireType IsFireZoAdAdTy

IsFireZoZoType



Salwico language expression Primary Workbench function Secondary Workbench functionsUNMUTED FIRE IN SYSTEM IsFireType IsFireZoAdAdTy

IsFireZoZoTypeMUTE ALARM FireMuteGlobalUNMUTED FAULT IsFaultType IsFaultCeBoIo

IsFaultZoAdAdTyIsFaultZoZoType

PRE-ALARM IN SYSTEM IsPreType IsPreZoAdAdTyIsPreZoZoType

WARNING IN SYSTEM IsWarnType IsWarnCeBoIoIsWarnZoAdAdTyIsWarnZoZoType

FLAG xCENTRAL VIO X IsCentralVIOVIO x or SYSTEM VIO X IsGlobalVIODISC IsDisaTypeDISC [EVENT]ZONE IsFireZoZoType IsFireZoAdAdTy

IsFireTypeUNMUTED ZONE IsFireZoZoType IsFireZoAdAdTy

IsFireTypeZONE x IsFireZoZoType IsFireZoAdAdTyZONE TYPE IsFireZoZoType IsFireZoAdAdTy

IsFireTypeZONE x TYPE IsFireZoZoType IsFireZoAdAdTyZONE x TYPE y IsFireZoZoType IsFireZoAdAdTyZONE x TYPE y-z IsFireZoZoType IsFireZoAdAdTyZONE x-y TYPE IsFireZoZoType IsFireZoAdAdTyZONE x-y IsFireZoZoType IsFireZoAdAdTyZONE x IN y.z IsLoopInput IsFireZoAdAdTyCU x.y DOOR IsKeyActivatedIN x.y.z IsInputStateFAULT IN SYSTEM IsFaultTypeBATTERY FAULT IsFaultTypeNET FAULT IsFaultTypeALARM DELAY ON IsDisaCentTypeCONTROLS OFF IsDisaTypeEXTALARM OFF IsDisaTypeALARM TRANSFER OFF IsDisaTypeOUT x.y.z IsOutputStateMINI RESET (block the minirepeater)

MiniRepeaterMN

MUTE MINI MiniRepeaterMNUNMUTED MINILARMORG MUTE MiniRepeater



Salwico language expression Primary Workbench function Secondary Workbench functionsLARMORG TRANSFER MiniRepeaterZONE FAULT [FAULT-TYPE] IsFaultZoZoType IsFaultZoAdAdTyZONE TYPE FAULT [FAULT-TYPE] IsFaultZoZoType IsFaultZoAdAdTyZONE TYPE y-z FAULT[FAULT-TYPE]

IsFaultZoZoType IsFaultZoAdAdTy

ZONE x FAULT [FAULT-TYPE] IsFaultZoZoType IsFaultZoAdAdTyZONE x TYPE FAULT[FAULT-TYPE]


ZONE x TYPE y-z FAULT[FAULT-TYPE]


BOARD FAULT [FAULT-TYPE] IsFaultCeBoIo IsFaultTypeBOARD x.y.z FAULT[FAULT-TYPE]

IsFaultCeBoIo IsFaultType

TCMS_STATUS x.y TcmsStatusTCMS_STATUS_BYTE0xYYYYYYYY

TcmsStatusByte

Outputs

Salwico language expression Primary Workbench function Secondary Workbench functionsMESSAGE ALARM DELAYON/OFF

DisaCentType

MESSAGE ALARM TRANSON/OFF

DisaType

MESSAGE CARD x.y.z SENDTEMPERATUREMESSAGE CARD x.y.z ORDER SensZoAdAdTyMESSAGE ZONE x SD y-z ORDERreplaced by PARAMETERSET PARAMETER ZONE x SD y-zSENS AAA

SensZoAdAdTy

PARAMETER ZONE x SD y-z SENSAAA/BBB

SensZoAdAdTy

SET PARAMETER ZONE x [TYPE][y-z] ALIMIT a ROR rPARAMETER ZONE x [TYPE] [y-z]ALIMIT a ROR rRESET PARAMETER ZONE x[TYPE] [y-z] ALIMIT a ROR rMESSAGE ZONE x TYPE yON/OFF

DisaZoAdAdTy

MESSAGE ZONE x TYPE y-zON/OFF

DisaZoAdAdTy

ZONE x OUT y.z SetLoopZoAdTyZONE x OUT y.z MSK g SetLoopZoAdTyUFLAG x replaced by VIOFLAG x



Salwico language expression Primary Workbench function Secondary Workbench functionsVIO x SetGlobalVIONEWCMPROFILE x.y [show][control]

NewCmProfile

MUTE_ALL FIRE FireMuteGlobalMUTE_ALL FAULT FaultMuteGlobalRESET_ALL FIRE FireResetGlobalRESET_ALL FAULT FaultResGlobalRESOUND_ALL FIRE FireUnMutGlobalRESOUND_ALL FAULT FaultUnMutGlobalMINI RESET MiniRepeaterMNLARMORG MUTE MiniRepeaterBUZZER OFF BuzzerOff BuzzerLocalOffCU x.y LED z [COLOR] [FLASH] SetPanelLedCU x.y LOCAL MUTE BuzzerLocalOffOUT x.y.z [PATTERN] SetOutput SetOutputIntCCP_STATUS x.y CcpStatusCCP_STATUS_BYTE 0xYY 0xZZ CcpStatusByteAHAD

Index


IndexAAdd Salwico Language sheet, Salwico Languagemodule.................................................................... 26Add central, central module................................... 22Add module, central module.................................. 24Advanced tab, Loop M X....................................... 52 CCause/Effect module .............................................. 19Central Window ..................................................... 22ChangeOver M Ext ................................................ 26Charger M .............................................................. 28Command menu, configuration program............... 9Configure loop units, Loop M X............................ 50Configure user menu, Control M 4.3 ..................... 37Control M 4.3......................................................... 32Control M 2.2......................................................... 43Control M X........................................................... 44Custom keys tab, Control M 4.3 ............................ 36 DDelete system user, user access module................. 14Download configuration file .................................. 65 EEdit menu, configuration program......................... 9Excel, importing configuration information ......... 61Excel, Loop Board template .................................. 62Exit, configuration program................................... 4Export to Excel ...................................................... 63Extended Panel Text .............................................. 63 FFile menu, configuration program ......................... 8Fire detection system, definition............................ 5Fire alarm outputs, application examples .............. 112Function AlarmLimitRoR...................................... 144Function BuzzerLocalOff ...................................... 145Function BuzzerOff ............................................... 145Function CcpStatus ................................................ 145Function CcpStatusByte......................................... 146Function DisaCeBoIo............................................. 129Function DisaCentType ......................................... 129Function DisaType ................................................. 130Function DisaZoAdAdTy....................................... 130Function FaultMuteGlobal..................................... 133Function FaultResGlobal ....................................... 134Function FaultUnMuGlobal................................... 134Function FireMuteGlobal....................................... 136Function FireResetGlobal ...................................... 136Function FireUnMutGlobal ................................... 137Function GetAdTimes............................................ 146Function IsCentralBooted ...................................... 146Function IsCentralVIO........................................... 139

Function IsDisaCeBoIo.......................................... 131Function IsDisaCentType....................................... 131Function IsDisaType .............................................. 131Function IsDisaZoAdAdTy.................................... 132Function IsDisaZoType.......................................... 132Function IsFaultCeBoIo......................................... 134Function IsFaultType ............................................. 135Function IsFaultZoAdAdTy................................... 135Function IsFaultZoZoType .................................... 135Function IsFireType ............................................... 137Function IsFireXCentral ........................................ 138Function IsFireZoAdAdTy..................................... 137Function IsFireZoZoType ...................................... 138Function IsGlobalVIO ........................................... 139Function IsInputState ............................................. 140Function IsKeyActivated ....................................... 140Function IsLoopInput............................................. 140Function IsLoopOutputSta..................................... 141Function IsMaster .................................................. 146Function IsOutputState .......................................... 141Function IsPreType ................................................ 150Function IsPreZoAdAdTy...................................... 150Function IsPreZoZoType ....................................... 150Function IsWarnCeBoIo ........................................ 151Function IsWarnType............................................. 151Function IsWarnZoAdAdTy .................................. 152Function IsWarnZoZoType .................................... 152Function MiniRepeater .......................................... 147Function MiniRepeaterMN.................................... 147Function NewCmProfile ........................................ 148Function NoDisaZoAdAdTy.................................. 132Function NoFireType ............................................. 138Function NoFireZoAdAdTy................................... 138Function NoFireZoZoType .................................... 139Function NoPreType .............................................. 150Function NoPreZoAdAdTy.................................... 151Function NoPreZoZoType ..................................... 151Function SensZoAdAdTy ...................................... 133Function SetCentralVIO ........................................ 141Function SetGlobalVIO ......................................... 142Function SetLoopZoAdTy ..................................... 142Function SetOutput ................................................ 142Function SetOutputInt............................................ 143Function SetPanelLED........................................... 143Function TcmsStatus.............................................. 149Function TcmsStatusByte ...................................... 149Function ThisBoard ............................................... 149Function ThisCentral ............................................. 149Functions vs. function blocks ................................ 128 HHelp menu, configuration program........................ 10

Index


II/O M 70................................................................. 44I/O M 700............................................................... 45I/O tab, Control M 4.3............................................ 38I/O tab, I/O M 70 ................................................... 45I/O tab, I/O M 700 ................................................. 47Import from Excel.................................................. 65Import loop module information............................ 61Input Analogue Module 0-20................................. 44Input parameters..................................................... 128Input tab, Repeater M ............................................ 58Installation, configuration program ....................... 3 LLogging tab, Control M 4.3 ................................... 32Loop Board template, Excel .................................. 62Loop tab, Loop M X .............................................. 49Loop M X............................................................... 49Loop M X Slave..................................................... 53LoopSlave tab, Loop M X Slave............................ 53 MMain menu, configuration program ....................... 7Main window, configuration program ................... 6Management of detectors from input, applicationexamples ................................................................ 115Management of external controls, applicationexamples ................................................................ 113Mini Repeater M (MN400).................................... 60Modbus TCP/IP Window....................................... 20Modify system user, user access module ............... 14Multiplexer unit ..................................................... 54MuxM .................................................................... 54 NNetwork tab............................................................ 41 OOptions window..................................................... 10Output parameters.................................................. 128Output Solenoid Module M 14 .............................. 49Outputs tab, Relay M 8 .......................................... 56Outputs tab, ChangeOver M Ext............................ 27Outputs tab, Charger M.......................................... 31Outputs tab, Control M 4.3 .................................... 34Outputs tab, Repeater M ........................................ 58 RRelay M 8............................................................... 55Repeater M............................................................. 57

SSalwico Language editor box, Salwico Languagemodule.................................................................... 26Salwico Language window.................................... 25Salwico Language, application examples .............. 112Salwico Language, command overview ................ 73Salwico Language, inputs ...................................... 76Salwico Language, outputs .................................... 98Salwico Language, syntax overview...................... 69Salwico Language, timers...................................... 93Serial tab, Control M 4.3........................................ 33Show/Control window ........................................... 15Starting, configuration program............................. 3Supervision tab, ChangeOver M Ext .................... 28Supervision tab, Charger M ................................... 30Supervision tab, different modules ........................ 42Supervision tab, different modules ........................ 45Supervision tab, different modules ........................ 48Supervision tab, different modules ........................ 52Supervision tab, different modules ........................ 54Supervision tab, different modules ........................ 55Supervision tab, different modules ........................ 57Supervision tab, Repeater M ................................. 59Surveillance, application examples........................ 113System requirements.............................................. 3System bus setting window.................................... 18System users........................................................... 13 TTool menu, configuration program ........................ 10 UUpload configuration file....................................... 66User access window............................................... 13 ZZones window........................................................ 14

Consilium Säkerhet - vår erfarenhet, din säkerhet!Consilium Säkerhet är marknadsbolag inomConsiliumkoncernen. Tillsammans marknadsför och säljervi brand- och gaslarm utvecklade av Consilium. Consilium utvecklar och marknadsför produkter ochsystem för säkerhet, miljö och navigation. Consilium ärvärldsledande inom brandlarm på den marina marknaden. Consilium Säkerhet, med kontor i Malmö, Göteborgoch Stockholm, kan erbjuda allt från projektering ochförsäljning till installation och service. Kundanpassad serviceVi på Consilium Säkerhet kan erbjuda dig som kundflertalet olika lösningar för service och avtal med allt frånlöpande service, inplanerad underhållsservice ellerfullservice samt givetvis akut service. Utöver detta kan viäven erbjuda månads- och kvartalsprov för automatiskabrandlarmsystem enligt SBF 110:6.

Som certiferad anläggarfirma kan vi garantera att samtligaleveranser och installationer utförs enligt fastställdamyndighets-, kvalitets- och säkerhetsnormer. Så oavsett om du behöver ett enklare brandskydd ellerett stort integrerat brand- och gaslarmsystem, är vårt målalltid detsamma, att förse dig som kund med en lösningefter ditt behov, uppbackad av vår engagerade ochvälutbildade personal!

Consilium Säkerhet Syd AB040-36 50 60

Consilium Säkerhet Väst AB031-710 79 00

Consilium Säkerhet Öst AB08-563 052 00

Consilium Tablero c i

Documents

Transcript of Consilium Tablero c i