FG5000
Fire Detection System
Consilium Säkerhet Väst AB Telefon: 031-710 79 00 Consilium Säkerhet Öst AB Telefon: 08-563 052 00
Innehållet i det här dokumentet är föremål för förändring utan förvarning på grund av ändrad metodik, design och tillverkning. Consilium kan aldrig hållas ansvarig för fel eller skador som på något sätt har ett samband med användandet av det här dokumentet.
December 2012
Document no. 5100355_FG5000_Configuration Manual_I1_EN_2012_C Part no. 5100355
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 ... 5
3.2.1 Section overview ... 5
3.2.2 The Fire Detection System ... 5
3.2.3 The Configuration Program ... 5
3.3 The Program Main Window ... 6
3.3.1 About the Main window ... 6
3.3.2 Main menu ... 7 3.3.3 File menu ... 8 3.3.4 Edit menu ... 9 3.3.5 Command menu ... 9 3.3.6 Help menu ... 10 3.3.7 Tool bar ... 10 3.4 Options Window ... 10
3.5 User Access Window ... 13
3.5.1 About the User Access Window ... 13
3.5.2 Adding a new user ... 13
3.5.3 Modifying an existing user ... 14
3.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 ... 22
3.11.3 Adding Modules ... 24
3.11.4 Salwico Language window ... 25
3.11.5 Configuring the Power Control Module - ChangeOver M Ext ... 26
3.11.6 Configuring the Power Control Module - Charger M ... 28
3.11.7 Configuring the Control Module - Control M 4.3 ... 32
3.11.8 Configuring the Control Module - Control M 2.2 ... 43
3.11.9 Configuring the Control Module - Control M X ... 44
3.11.10 Configuring the Input Analogue Module 0-20 - IAM020 ... 44
3.11.11 Configuring the I/O Module - I/O M 70 ... 44
3.11.12 Configuring the I/O Module - I/O M 700 ... 45
3.11.13 Configuring the Output Solenoid Module M 14 - OSM14 ... 49
3.11.14 Configuring the Loop Module - Loop M X ... 49
3.11.15 Configuring the Loop Module - Loop M X Slave ... 53
3.11.16 Configuring the Multiplexer Module 16 - MuxM16 ... 54
3.11.17 Configuring the I/O Module - Relay M 8 ... 55
3.11.18 Configuring the Repeater Module - RM ... 57
3.11.19 Configuring the Mini Repeater Module - MN400 ... 60
3.12 Importing Configuration Information from Excel ... 61
3.12.1 Introduction ... 61
3.12.2 Importing Loop Module Information ... 61
3.12.3 Description of the columns in the Loop Board template ... 62
3.13 Defining Extended Panel Text ... 63
3.13.1 Introduction ... 63
3.13.2 Prepare an Excel file with Extended Panel Texts ... 63
3.13.3 Description of the columns in the Extended Panel Text template . 64 3.13.4 Importing the Excel file with Extended Panel Texts ... 65
3.13.5 Verification of Extended Panel Text ... 65
3.14 Downloading a configuration file from the fire detection system .. 65
3.14.1 Downloading a configuration file to a USB Memory Stick ... 65
3.15 Uploading a configuration file to the fire detection system ... 66
3.15.1 Uploading a configuration file from the USB Memory Stick ... 66
4
The Salwico Language ... 69
4.1 About the Salwico Language ... 69
4.1.1 Introduction ... 69
4.1.2 General Syntax ... 69
4.1.3 The order of evaluation in expressions ... 73
4.1.4 Explanatory Text ... 73
4.2 Command Overview ... 73
4.2.1 Command Tree ... 73
4.2.2 Command Reference ... 76
4.3 Inputs ... 76
4.3.1 Summary Input Commands ... 76
4.3.2 Input Command Description ... 79
4.4 Timers ... 93
4.4.1 Summary Timer Commands ... 93
4.4.2 Timer Command Description ... 94
4.5 Outputs ... 98
4.5.1 Summary Output Commands ... 98
4.6 Application Examples ... 112
4.6.1 Section Overview ... 112
4.6.2 Fire Alarm Outputs ... 112
4.6.3 Surveillance ... 113
4.6.4 Management of External Controls ... 113
4.6.5 Management of Detectors from Input ... 115
4.6.6 Other Examples ... 116
5
The CCP Workbench ... 117
5.1 About the CCP Workbench ... 117
5.1.1 Introduction ... 117
5.1.2 General Syntax and semantics Overview ... 117
5.2 Workflow of configuration ... 119
5.2.1 Description ... 119
5.3 Starting CCP Workbench ... 120
5.3.1 Projects ... 120
5.3.2 Create a new CCP Workbench project ... 120
5.4 Start program PLC code ... 123
5.4.1 Create a program in your CCP Workbench project ... 123
5.4.2 Explanation of a FBD diagram ... 123
5.5 Making application code ... 124
5.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 ... 127
5.12.1 Ooops… I need an old version of my CCP Workbench project? .. 127
5.12.2 I need support what files to enclose? ... 127
5.12.3 I am desperately low on disk space!? ... 127
5.12.4 I have arrived at a system without any configuration files!? ... 127
5.13 Predefined CCP blocks ... 128
5.13.1 General ... 128
5.13.2 CCP Disablements section ... 129
5.13.3 CCP Fault alarm section ... 133
5.13.4 CCP Fire alarm section ... 136
5.13.5 CCP IO section ... 139
5.13.6 CCP Miscellaneous section ... 144
5.13.7 CCP Pre-alarm section ... 150
5.13.8 CCP Warning-alarm section ... 151
5.13.9 Migrate from Salwico language to PLC ... 152
1 Introduction
1.1 About this manual
This manual consists of a functional description of the configuration program, where the emphasis is put on how to work with the different program windows and how to program the external controls using the Salwico language.
ChapterIntroduction to the Configuration program, page 2gives a brief introduction to the configuration program.
ChapterConfiguration Program Installation, page 3helps you through the
program installation.
ChapterHow to make a System Configuration, page 5describes how to make a
system configuration using the configuration program.
In chapterThe Salwico Language, page 69you will find a complete description
of the Salwico language commands and examples on how to use them.
In chapterThe CCP Workbench, page 117you will find a description of the CCP
Workbench and how to use it.
SectionPredefined CCP blocks, page 128describes the predefined CCP blocks
delivered 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 manual
DANGER!Risk of serious or fatal injury to the user, and/or severe damage to the product, if the instructions are not followed.
WARNING!
Risk of personal injury and/or damage to the product if the instructions are not followed.
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 additional information and tell you how to perform a certain operation in an easier way.
1.3 Introduction to the Configuration program
The configuration program is especially designed for creating a system
configuration file for a fire detection system. Before a fire detection system can be used, it must be both physically and functionally configured.
The configuration program is designed to run on a computer that can support Microsoft Windows NT, XP, 2000, Vista or Windows 7.
2 Configuration Program Installation
2.1 Chapter Overview
This chapter describes the system requirements for using the program, installing the configuration program, and running the program.
2.2 System Requirements
Minimum 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 setup files 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 program
To install the configuration program, start Microsoft Windows and follow this procedure:
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 program
To start the configuration program, follow the procedure below:
1 Start the program from the shortcut in either the start meny or on the
desktop.
Figure 1. Start window
The Configuration program and all application windows are explained in chapter How 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 the
Configuration program, the program will ask you to save the changes (unless they have already been saved). The saved configuration file will have the extension .ccp.
Do not use a filename with more than 64 characters. This is due to restrictions of the transfer protocol which does not allow large filenames. The file name will be concatenated if the length is above 64 characters.
3 How to make a System Configuration
3.1 Chapter overview
This chapter describes creating a system configuration and downloading the configuration file to a fire detection system. The basic structure of the
configuration program is the six main application windows: Options, User Access,
Zones, Show/Control, System Bus, Cause/Effect and Central module tree. When
making a configuration file, you can interrupt at any time, save the configuration to file and continue later.
3.2 Functional Description
3.2.1 Section overview
It is easier to work with the Configuration program once you know how the detection system functions. The following section gives you a brief description of the system functions and the configuration program function.
3.2.2 The Fire Detection System
A fire detection system is defined before it is used. • Physical
Which kind of modules, detectors, etc. does the system consist of? The physical configuration is defined to achieve fault supervision of the different system components such as zones, loop units, modules, etc. The system configuration must be changed if the physical configuration is changed.
• Functional
How do you want the system to function? Is it an industrial or a marine system? Which zone will each detector belong to?
• Supplementary text
Each system unit can be assigned descriptive text that explains the unit's location. Descriptive text is displayed on the control panel.
• I/O
Defines how the inputs and outputs of the system react. For example: “Bells on deck 3 are activated when there is a fire alarm in zone 4”.
3.2.3 The Configuration Program
The configuration program is divided into six functionally and well-defined main application windows; Options, User access, Zones, Show/Control, System Bus, Cause/Effect and Central module tree. These windows are used to define the fire detection system both physically and functionally. After the configuration has been performed, the Main menu is used to manage a configuration file, to load a file into the program, and to save a configuration file update.
The modules are defined by entering different settings. Modules are defined one at a time. Information about the modules can be found later in this chapter.
The Options window includes information about the current configuration file and text fields in which the name and reference of the project is entered. Give the installation a specific name to make it easier to document each installation. A number of other global system settings can be set from the options window: marine or industrial installation, language, revision history, etc.
The User Access window is used to handle new and existing users of the fire detection system.
In the Zones window, there is a list of all zones defined in the system. It is possible to name the zones.
In the Show/Control window, modules and zones are dedicated to groups, and group 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 communication ports, zones, loops and loop units, and supplementary texts.
The functional configuration defines how the inputs and outputs of the system should react. The commands are written in the Salwico language, as described in the chapterThe 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 window
The main window, as shown in the figure below, is displayed when you start the program and it is from here that you select the application windows you want to work with. Use the main window when you want to update, load or save a configuration 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 menu
The main menu provides commands to save a configuration file and copy texts in the 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 more
information, refer toImporting Loop Module Information, page 61.
NOTE!
The imported data replaces loop information already entered into the configuration program.
Extended Panel Text: Extended panel text can be used to define custom texts for
individual panels in the CCP Fire Detection System. For more information, refer to Defining 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 used
configuration files.
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 sheet
from the module tree.
3.3.5 Command menu
Figure 6. The command menu
Verify Configuration: The program will verify the entire configuration file to
ensure that there are no faults or conflicts. If any faults are discovered, an error message is generated, as shown in the figure below.
Figure 7. Example error message
Launch CCP Workbench: The menu alternative becomes available if CCP
Workbench PLC, and a project directory has been chosen in the Cause/Effect window.
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 the Main 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 Edit
menu. These commands can also be executed through keyboard short cuts, as
shown in figureThe edit menu.
The Verify Configuration and Launch CCP Workbench commands are found in the Command menu.
3.4 Options Window
In the options application window, as shown in the figure below, specify basic data about the installation, such as the installation name and reference number.
Configuration file information:
Revision history is a free text field used to enter revision history information, such
as date of original installation, installer company, date of updates, changes made in the configurations and by whom, etc. Please enter all data you think is of
significance for engineers.
Saved in format: Information about the format that the configuration file is saved
in.
Created by: Information about who or which company that created the
configuration.
Saved at: Information about the time and date of the latest update of the
configuration 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 the
control panel’s text display.
Installation type: Choose whether the installation is a marine, industrial or
transport type. This affects how the system will function to comply with the different regulations for marine, industrial and transport applications.
Language: Choose from available languages: English, Swedish, Danish, English
Non Fire, Norwegian and Chinese. The English Non Fire alternative implies that the system is used for patient alarms instead of fire alarms.
Time Zone: Select the desired geographical time zone or GMT time zone from the
drop down list.
NMEA update interval: Specify the time interval with which the system
automatically sends a total system status update on all serial-ports defined with NMEA protocol.
The detailed configuration of serial outputs is made under each module in the central.
Max disablement time: By entering a time value in this field, the alternative
“permanent disablement” in the control panel under menu » 3. Disablements will be replaced by an alternative with the entered disablement time.
NOTE!
The Max 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 when
WARNING!
When the checkbox is ticked, the central will not comply with the EN-54 fire standard.
Customer Ranges: Select the desired cusomer ranges for loop devices from the
drop down list.
Customer Logo: Selects a logo that will be displayed on the standby home view
screen. This function requires a security code to be unlocked.
3.5 User Access Window
3.5.1 About the User Access Window
System 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 user
Click 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 User Guide.
4 Press Enter.
3.5.3 Modifying an existing user
Just 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 user you want to delete, as shown in the figure above.
2 Press Delete. A dialogue box opens.
3 Confirm by clicking OK in the dialogue
box.
3.6 Zones Window
In the zones window, as shown in the figure below, you will find a list of all defined zones in the fire detection system. Zones are defined in the Central described later in this chapter. From here it is possible to add text that names and describes 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 as
characters). This text will be shown at the control panel below the fire zone information in case of a fire.
Text 2: Additional free text field (max 37 characters - word spaces are counted as
characters). Shown in the same way as Text 1.
Information Window: When you click on one of the zones in the zone list, the
information window will show in which central and on which module and address the zone is defined.
3.7 Show/Control Window
Each module and zone in a fire detection system can be dedicated to one or several groups. For each control module, it is possible to define which groups it should control and/or display.
If any control module in the system is missing or broken for some reason, all the other control modules and repeater modules will automatically get full access to everything.
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 which zones 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 number
in the dialogue box (only vacant numbers are available in the list) and describe the group in the Text field.
Figure 16. New Group dialogue box
Edit: Edit a group. As shown in the figure below, specify a new group number in
the dialogue box if desired (only vacant numbers are available in the list) or give the 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 group
selected in the Number field. The zone or module must be marked in the
Zones/Modules defined in system list.
<- Remove (Two buttons with similar function): Removes a zone or a module from
the group selected in the Number field. The zone or module must be marked in the
Zones/Modules in group list. Group Management
In the Group Management field it is possible to set whether the groups should be controlled or only presented, or neither controlled nor presented on the control modules.
Select Control Module: Choose which control module to handle.
All groups: Shows all groups defined in the system. Click the group or groups you
want 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 (and removes 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 not
controlled 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 and removes it from the Groups presented only list.
• The Remove button removes the selected group from the Groups presented
only list.
Groups controlled: A list of the groups that will be controlled from the control
module specified in the Select Control Module field. Click the group you want to handle.
• The Present button puts the selected group in the Groups presented only list and removes it from the Groups controlled list.
• The Remove button removes the selected group from the Groups controlled list.
Guidelines for Group Management
By default (as determined by the configuration program), all modules and zones become dedicated to all groups that exist in the moment that the module or zone is added. Group 1 is created automatically when the first module is added.
1. Read section Description of fields and buttons in the Show/Control window above.
2. Create a group using the New button.
3. Use the Add or Remove buttons to specify the content of zones and modules in the 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 control
module.
NOTE!
Only zones in a group can be set up in group management to present/control alarms from the zone.
Only modules in a group can be set up in group management to present/control faults from the module (not zones).
3.8 System Bus Settings Window
System Bus is the communication bus used for connecting multi-central systems. A primary 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 same serial 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 Window
Switch between Salwico Language and CCP Workbench PLC in the Cause/Effect window.
For CCP Workbench PLC the following options are available:
Launch CCP Workbench: This option starts CCP Workbench, which is a separate
program that comes with the installation of CCP Tools, to create PLC controllers for the system. These parameters are then included in the configuration file when it is saved. When the CCP Workbench is started, it will automatically load the projects chosen in the selected project directory. (If there are no projects in the directory you get the question if you want to create a new project.)
Hint!
Please refer to the CCP Workbench Handbook found in the CCP Workbench program Help menu.
Export project files from configuration: This is a so-called advanced operation
and requires that you have saved the PLC controllers in a configuration file once and then re-opened it in the CCP Configuration program. Use the Launch Workbench button to extract a project file for the CCP Workbench based on the existing configuration file, which is then copied to the chosen directory path.
NOTE!
The Salwico Language is specified central wise while PLC is specified system wise.
Figure 19. Cause/Effect window
3.10 Modbus TCP/IP Window
Consilium fire detection system has the capability of becoming a Modbus RTU Slave. The external device must be configured as a master.
The function is activated by setting serial channel 3 or 4 on any type of control module to ‘MODBUS RTU’ in the Serial tab. Please refer toSerial Tab, page 33. Serial channel 3 or 4 on the control module is running RS232 or RS485 depending on 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 control modules that should run Modbus. Select checkbox “Enable Modbus TCP/IP” as described inNetwork 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 are detectors, short circuit isolators, timers and digital inputs (address units, control modules). The Modbus module holds the status of the devices and prepares them for Modbus interpretation using a cross reference translation table created and compiled by the Consilium service engineer using “ComtesterLT.exe” and then downloaded to the fire detection system.
Specification of CCP Modbus RTU Protocol and the cross reference file are described in separate documents.
CAUTION!
If a cross reference file for Modbus exists, the cross reference file overrides the default configuration and the default configuration is disabled!
3.11 Central
3.11.1 About the Central Window
In the Central Window, as shown in the figure below, the central is physically and functionally defined. The physical configuration is where central modules, serial communication ports, zones, loops and loop units, and supplementary texts are defined. The functional configuration defines how the inputs and outputs of the system should react. They are set in the Salwico Language window with the Salwico language described in chapterThe Salwico Language, page 69, or in the The CCP Workbench, page 117, (depending on the option selected in the
Cause/Effect window).
Figure 22. The Central Window
3.11.2 Adding a Central
3.11.2.1 Adding a Central
When starting the program, a central called “Central 1” is added per default. If the central is removed or more centrals are required, add a new central following the instructions below:
1 Place the cursor on Options, User Access, Zones, Show/Control, System
Bus or Cause/Effect in the module tree and click with the right mouse
button.
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 the
list.
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 Central
window
Address: Give the central a unique address between 1-30. The program is prepared
to handle several centrals.
Description: A free text field (max 37 characters) describing the central. The text
will be shown in the fault list when a “central no answer” fault is reported from this central.
VIO Tab
Use the tab to handle custom faults and alarms for Central VIO. Salwico expressions can activate a particular central VIO which in turn can be used to trigger an associated alarm or fault according to the configuration.
The Central VIO defined here is used as input conditions for monitoring. For example, if an input is active, you can activate a Central VIO which then in turn generates either a fault or an alarm. The condition of a Central VIO cannot be monitored from another central as Central VIOs only communicates within the central there they are defined. But generated faults or alarms are spread throughout the 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 be
shown in case of a generated fault or alarm.
Text 2: Additional text field (max 37 characters) describing the VIO. Shown in the
same way as Text 1.
Summary Tab
Figure 24. The Central Summary tab
The Current consumption approximation field shows a current consumption approximation for the selected central.
Idle condition: The program automatically calculates expected working current in
normal condition for the configured central. This value is approximate.
Alarm condition: The program automatically calculates expected working current
during 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 the configuration and that each module is assumed to have the below described setup.
Idle condition: Control Modules consumes from 62 to 110mA depending on
model, all other modules except Loop M consumes 20mA and finally the Loop M is assumed to have 100 detectors resulting in a consumption of 75mA
Alarm condition: Same consumtion as in idle condition with the following
additions; Control Modules and Repeater Modules are assumed to have one active output at 70mA, Relay M, IOM70 and IOM700 are assumed to have four active outputs, each consuming 80, 70 and 200mA respectively. Finally Loop M is assumed to have 33 active detectors consuming in total 10mA.
3.11.3 Adding Modules
Add modules such as Control M X, Control M 4.3, Charger M, etc. according to the procedure below. Configuration of the modules is described later in this chapter.
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, it has to be added to a control module. For information seeAbout Mini Repeater - 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 depends on the module type, as listed in the table below. If the default address is already occupied, the module receives the next available address.
Table 1. Default addresses for modules
Module type: Default address:
Control M 4.3 Control M 2.2 1 - 8 Control M X 3 - 8 ChangeOver M Ext 9 - 10 Loop M X Loop M X Slave 11 - 49 I/O M 70 50 - 63 I/O M 700 64 - 71 Relay M 8 72 - 89 Charger M 90 - 95 Mux M 16 96 - 99
Module type: Default address:
Repeater M
Mini Repeater MN400 100 - 115
Output Solenoid M 14 116 - 122
Input Analogue M 0-20 122 - 125
3.11.4 Salwico Language window
3.11.4.1 About the Salwico Language window
The function of all inputs and outputs in the system are defined in the Salwico
Language window, as shown in the figure below. This section describes how to
enter the commands into the editor. All information about the commands is
provided inThe Salwico Language, page 69.
Figure 25. The Salwico Language window
3.11.4.2 Description of buttons and checkbox in the Salwico
Language window
Add new Program: Creates a new Salwico Language statement sheet. It is
possible to add several Salwico Language sheets, for example to separate fire and
sprinkler configurations. Each program can be individually named. SeeAdding
Salwico Language sheets, page 26later in this chapter for more information.
Compile All Programs: Compiles all Salwico Language sheets for the selected
central. The program will verify if the syntax is correct and that there are no conflicts if you have added more than one Salwico Language sheet (e.g., that the same 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 is
added in the module window. The Salwico Language sheet receives a default name - the first sheet is named SL1.
2 Click on the sheet name and enter the Salwico Language information using
the Salwico language commands as decribed inThe 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 the Salwico Language editor box.
3 When you have entered all commands, click on the Compile button in the
Salwico 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 the
module tree window. Then repeat the procedure from step 1.
5 The Salwico Language sheets are saved in the document when you leave
the Salwico Language editor box and they are saved to the configuration file 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 Ext
3.11.5.1 About ChangeOver M Ext
The 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 alarm
central should have a unique address between 1-125. Default address depends on module type. Please refer to list of modules in sectionAdding Modules, page 24.
Text: A free text field (max 37 characters) describing the ChangeOver M Ext. This
text will be shown in the fault list if a fault is reported from the ChangeOver M Ext.
3.11.5.2 Outputs Tab
The ChargeOver M Ext is equipped with 4 outputs. They are configured from the outputs 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, seeOutputs Tab, page 34in Configuring 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 power
loss occurs.
Emergency Input: Disable or enable fault generation from the Emergency input if
a power loss occurs.
Secondary backbone channel (B): Disable or enable fault generation from the
secondary backbone channel (B). Disable the fault generation if only the primary backbone channel (A) is connected to this module.
3.11.6 Configuring the Power Control Module - Charger
M
3.11.6.1 About Charger M
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 central
should have a unique address between 1-125. Default address depends on module type. Please refer to list of modules in sectionAdding Modules, page 24.
Text: A free text field (max 37 characters) describing the Charger M. This text will
be shown in the fault list if a fault is reported from the Charger M.
3.11.6.2 Supervision Tab
Description of the Options field in the Supervision tab
Charger M monitors the voltages and current levels of all the power flows in and out 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 missing battery.
Disable battery charge: Select this alternative if you do not have any batteries
connected 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 will
generate a warning.
Net absent fault generation time X min: You can enter a time here after which
the 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 internal
resistance of the battery. The corresponding value of the internal resistance of the battery is measured twice an hour and compared to the entered value. If the
measured value is greater than the entered value a battery fault will be generated. If set 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 module
should 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 or Change Over.
PSU 2: Enable or disable PSU 2 and choose the type of monitoring, None, PSU or Change Over.
Figure 32. Charger M can be set to supervise PSU or Change Over modules
Description of the Secondary backbone channel field in the Supervision tab
Secondary backbone channel (B): Disable or enable fault generation from the
secondary backbone channel (B). Disable the fault generation if only the primary backbone channel (A) is connected to this module.
3.11.6.3 Outputs Tab
The Charger M is equipped with one output. It is configured from the outputs tab in the 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 output must be set to "not used" in the configuration to avoid a configuration fault in the system.
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) and Max Backbone Current (mA): Defines the
maximum current consumption allowed on the output and on both backbone channels. If exceeded a power limit warning will be generated.
Hint!
For information about output configuration, seeOutputs Tab, page 34in Configuring the Control Module - Control M 4.3.
3.11.7 Configuring the Control Module - Control M 4.3
3.11.7.1 About Control M 4.3
The 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 alarm
central should have a unique address between 1-125. Default address depends on module type. Please refer to list of modules in sectionAdding Modules, page 24.
Text: A free text field (max 37 characters) describing the Control M 4.3. This text
will 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
Select events to print: Select which events that will be sent to the printer
connected to this Control M 4.3.
Hint!
Printers are defined in the Serial tab.
3.11.7.3 Serial Tab
The Control M 4.3 is equipped with four serial communication ports, where the first two ports are dedicated to the backbone and the other two ports are
configurable, 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 not
editable. The type is always one or a combination of RS232, RS422 and/or RS485.
Protocol: Select the applicable serial protocol for the communication ports by
clicking 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 extension bus connected to this control module.
• System bus: Communication between centrals. For further information of serial
channel 3 and 4, seeSystem 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 a
• MiniRepeater (MN400): The channel will be used for MN400 modules connected to this control module.
• Modbus RTU: Protocol for supervision and control of the system. The protocol is described in a separate document.
• CSProt6: A Consilium specific protocol. The protocol is described in a separate document.
• EMU350/EMU798/ChangPing/Sardinia/Dalian: Train-specific protocols used on trains. The protocols are described in separate documents.
• Aquasys: Aquasys system sensor protocol.
• Clocksync (UTC)/Clocksync (Local): Protocols to activate Ship Clock Synchronisation.
Baud: Choose the applicable baud rate for the communication port by clicking in
the 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 the
setup 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 communication port.
Text 2: Additional text field (max 37 characters) describing the communication
port. Shown in the same way as Text 1.
3.11.7.4 Outputs Tab
The Control M 4.3 is equipped with two outputs. They are configured from the outputs 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 the
category column, as shown in the figure below. The categorization allows the system operator to disconnect whole categories of outputs with one single command.
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, as
shown 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 upon activation.
• Active low: The output is normally active and will be inactivated upon activation, e.g., used with failure outputs. If the system goes down the output will be triggered.
Setup: Choose the applicable setup for the communication port by clicking in the
Figure 43. The setup list
Text 1: A free text field (max 37 characters) describing the output. This text will be
shown in the fault list in case of a fault on the output.
Text 2: Additional text field (max 37 characters) describing the output. Shown in
the same way as Text 1.
3.11.7.5 Custom Keys Tab
The 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, as shown in the figure below. The configuration of the LED indications on the custom shortcuts is performed in the Salwico Language sheet.
Use the command: CU x.y LED z, to define LEDs for shortcuts. Each custom key is reflected in a SYSTEM VIO which you then can use as input conditions to control 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 shortcuts
can be configured independently of each other.
Function: Select how the three customer-defined buttons on the Control M 4.3
should perform. Function alternatives:
• Not used: The custom shortcut will not have any function.
• Set: The custom shortcut will activate the programmed action associated with this custom shortcut. The action will only be performed once. The configuration of the user buttons is performed in the Salwico Language module.
• Maintained: When the custom shortcut is pressed, the pre-programmed action associated with this user button will be performed and will stay active until the user button is pressed again.
• Menu: When the custom shortcut is pressed, a customer-specific menu is shown in the text display. The customer-specific menu is configured in the User Menu field displayed when Menu is selected.
Menu Text: This text is shown in the customer-specific menu defined for the
selected custom shortcut.
Access level: Select which access level the user must have in order to use the
custom 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 Menu
Configure the menu, which will be shown in the text display if the custom shortcut is pressed. The User Menu field, as shown in the figure below, is only displayed if the Function is set to Menu.
Figure 45. The User Menu
Each row marked as Used in the User Menu will be associated with a SYSTEM VIO x statement in the Salwico language. It is possible to have up to 1000 VIOs in one fire detection system. For example, if VIO is set to 2 and the Used checkbox is enabled, the VIO 2 statement in the Salwico language will be associated with this
User Menu row. Further, the menu text to be shown in the custom menu is
specified by the Text – VIO inactive and Text – VIO active columns. The action that should be triggered when the User Menu row is selected from the custom menu is configured in the Salwico Language module described previously in this chapter.
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 is
pressed.
VIO: Selects which SYSTEM VIO to use.
Text – VIO inactive (default): Defines the texts to be shown in the menu when the
SYSTEM VIO is cleared.
Text – VIO active: Defines the texts to be shown in the menu when the SYSTEM
VIO is set.
Indication only: Tick the checkbox to de-activate the buttons. It is then not
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 in
order 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 an appropriate category for each input/output you define. The categorization allows the system operator to disconnect whole categories of input/outputs with a single command.
• 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 from the Cause/Effect module.
• Fault input: The loop is used as a digital input. A fault appears when the loop is activated.
• General output: The loop is used as a digital output and can be programmed from 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 loop is activated.
• 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 Type
is set to “Zone”. The zone number specified appears in the Zones window, where texts describing the zones can be added.
The zone numbers should be in 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. The zone number must be unique.
Alarm 1: Enter the lower level for the Alarm 1 interval (in mA), as shown in the
figure below. When the current passes this value, the input status changes from inactive to active.
Alarm 2: Enter the lower level for the Alarm 2 interval (in mA), as shown in the
figure below. This is also the upper level for the Alarm 1 interval. Note: Alarm 2 is only active if Type is set to “Zone”.
Break Level: Set the current level under which a cable break fault will be
generated. To avoid cable break fault messages, set the value to 0. For 1 or 2 mA the suitable resistance level is 10 kOhm.
Short level: A limit for short circuit error. The current output from the zone will be
limited to the value specified in the Max Current for each Terminal field. If many alarms are triggered, causing the current to reach the Max Current for each
Terminal value, the voltage on the input will decrease. Based on this voltage
decrease, the system calculates a fictive current value, which is compared with the
Short level value. A fault signal is sent if the fictive value exceeds the Short level
value.
This is also the upper level for the Alarm 2 interval, if Type is set to “Zone”, as shown in the figure below. For “Zone” the Short level can be adjusted (default value 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 in the 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 Circuit
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, where
more 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 synchronization pulse, if such a pulse is available.
• Synchronized: The output will follow the synchronization pulse, if such a pulse is available.
• Break Supervised: Activates the cable break supervision. Signals a fault in case of a break.
• Short Supervised: Activates the short circuit supervision. Signals a fault in case of short circuit.
• GA-morse: If activated, this output will be active when the ’General
Announcement’ signal is activated. The latter is a hardware signal activated via Charger M.
• X-fire: If activated, this output will be active when the ‘X-Fire” signal is activated. The latter is a hardware signal used as a last resort if a module detects an 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 loop
unit. 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 the corresponding zone number. Otherwise, it can be entered directly in the Text 1 field.
Text 2: An additional free text field (max 37 characters) describing the location of
the loop unit. Shown in the same way as Text 1. If Type is set to “Zone”, this text must be entered in the Zones window, at the corresponding zone number.
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 using
VNC. A server is started on the control module that allows connections from remote 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 is derived from the module's hardware address.
Modbus TCP/IP field
Enable Modbus TCP/IP: Check the box to enable Modbus TCP/IP (as described
3.11.7.9 Supervision Tab
Figure 52. The Supervision tab in the editor box
Description of the fields in the Supervision tab:
Secondary backbone channel (B): Disable or enable fault generation from the
secondary backbone channel (B). Disable the fault generation if only the primary backbone channel (A) is connected to this module.
3.11.7.10 kProt Tab
There are some prerequisites on the Fire detection system for kProt (Kongsberg Protocol) 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 and Control M X modules. (Note that control modules in the Fire detection system always act as kProt slaves and that equipment connected to the Fire detection system 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 kProt protocol itself shall support SIL-2 according to IEC61508 with regard to communication.
The kProt communication protocol is described in a separate document.
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 and shall be used by all masters in order to communicate with the slave. Valid port numbers 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 in the 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 static IP-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 same for all masters. It is possible to add masters with the same IP address but if in that case different port numbers must be used in order to assure that the master address is unique.
CAUTION!
The kProt slave follows the configuration strictly, messages will be dropped by the slave if other IDs than the ones specified are used and messages will be sent to the wrong 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.2
3.11.8.1 About Control M 2.2
The 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 Control M 4.3 but has otherwise the same type of functionality.
Refer to the sectionConfiguring the Control Module - Control M 4.3, page 32 for details on how to configure a control module.
3.11.9 Configuring the Control Module - Control M X
3.11.9.1 About Control M X
The Control M X is a control unit in the fire detection system, in some ways similar to the Control M 4.3. Control M X only has two output channels (no input channels) and lacks custom keys compared to Control M 4.3 but has otherwise the same type of functionality.
Refer to the sectionConfiguring the Control Module - Control M 4.3, page 32
for details on how to configure a control module.
3.11.10 Configuring the Input Analogue Module 020
-IAM020
3.11.10.1 About Input Analogue Module 0-20
This module is currently not implemented.
3.11.11 Configuring the I/O Module - I/O M 70
3.11.11.1 About I/O M 70
The I/O M 70 is a connection module for up to eight conventional detector zones. It can also be used for digital input.
Figure 54. I/O M 70 editor box
Address: Enter an address for the I/O M 70. Each module in a fire alarm central
should have a unique address between 1-125. Default address depends on module type. Please refer to list of modules in sectionAdding Modules, page 24.
Text: A free text field (max 37 characters) describing the I/O M 70. This text will
be 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 toI/O Tab, page 38for Control M 4.3.
3.11.11.3 Supervision Tab
Figure 56. The Supervision tab in the editor box
Description of the fields in the Supervision tab:
Secondary backbone channel (B): Disable or enable fault generation from the
secondary backbone channel (B). Disable the fault generation if only the primary backbone channel (A) is connected to this module.
3.11.12 Configuring the I/O Module - I/O M 700
3.11.12.1 About I/O M 700
The I/O M 700 has eight programmable I/O channels that can be used as either inputs 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 central
should have a unique address between 1-125. Default address depends on module type. Please refer to list of modules in sectionAdding Modules, page 24.
Text: A free text field (max 37 characters) describing the I/O M 700. This text will
be shown in the fault list if a fault is reported from the I/O M 700.
3.11.12.2 I/O Tab
NOTE!If DIP switch 8 is used output 5-8 will always be active. In this case output 5-8 must be set to "not used" in the configuration to avoid a configuration fault in the system.
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 an appropriate type for each input/output you define. The categorization allows the system operator to disconnect whole categories of input/outputs with a single command.
Hint!
For a detailed description of each type seeI/O Tab, page 38for Control M 4.3.
Active: There are three alternatives to choose from by clicking in the active
column.
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 upon activation.
• Active low: The output is normally active and will be de-activated upon activation (e.g., used with failure outputs). If the system goes down the output will be triggered.
Setup: For each input/output there are six additional options, where more than one
