FG5000

FG5000
Fire Detection System

CCP System description &
Application examples
Consilium Säkerhet Syd AB
Telefon: 040-36 50 60

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.

May 2015
Document no. 5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C
Part no. 5100501
© Copyright 2015, Consilium Säkerhet

Table of contents
1 System Description............................................................................ 1
1.1 Overview ............................................................................................ 1
1.2 System software ................................................................................. 2
1.2.1 Presentation layer............................................................................ 2
1.2.2 Control/Process layer ...................................................................... 2
1.2.3 Module/Field layer.......................................................................... 3
1.2.4 Access levels................................................................................... 3
1.2.5 Disablements................................................................................... 3
1.3 CCP System Modules ........................................................................ 4

1.3.1 Main groups of CCP modules......................................................... 4
1.3.2 Control Modules, information and control/process level ............... 4
1.3.3 Managed modules, Field layer........................................................ 6
2 Single Central System (SCS) ............................................................ 9

2.1 General .............................................................................................. 9
2.2 Backbone Bus.................................................................................... 11
2.2.1 Backbone Bus communication ....................................................... 11
2.2.2 Basic Backup Signal, BBS.............................................................. 12
2.2.3 GA-Morse (only in BBI)................................................................. 13
2.2.4 RS-485 communication, BBI.......................................................... 14
2.2.5 Power supply, BBI .......................................................................... 14
2.2.6 Backbone Bus Internal (BBI).......................................................... 14
2.2.7 Backbone Bus External (BBE) ....................................................... 14
2.2.8 Extension Bus ................................................................................. 17
2.2.9 Ethernet Communication ................................................................ 17
2.2.10 Protocols, overview......................................................................... 17
2.3 Power supply ..................................................................................... 17

2.4 Zones.................................................................................................. 21
2.5 Input/Output Interfaces .................................................................... 21
2.5.1 General............................................................................................ 21
2.5.2 Patterns............................................................................................ 22
2.5.3 Output override ............................................................................... 23
2.5.4 Synchronization of outputs ............................................................. 24
2.5.5 Two relay outputs with a special behaviour.................................... 24
2.6 I/O 70 type contacts........................................................................... 25

2.6.1 General............................................................................................ 25
2.6.2 I/O 70 Defined as an input for Conventional detectors .................. 26
2.6.3 I/O 70 Defined as an Output ........................................................... 27
2.6.4 I/O 70 Defined as an Input.............................................................. 27
2.7 I/O 700 type contacts......................................................................... 30

2.7.1 General............................................................................................ 30
2.7.2 Controlling alarm devices ............................................................... 31
2.7.3 I/O 700 controlling Magnets........................................................... 32
2.7.4 I/O 700 used as input ...................................................................... 32
2.7.5 I/O 700 used as Power output ........................................................ 32
3 Multi Central System (MCS) ............................................................ 35

Table of contents
3.1 System Bus ........................................................................................ 35
4 CCP Modules Descriptions............................................................... 37

4.1 Control modules ................................................................................ 37
4.1.1 Overview......................................................................................... 37
4.1.2 Control modules in control mode, Addressing rules ...................... 37
4.1.3 Control M 4.3.................................................................................. 38
4.1.4 Control M 2.2.................................................................................. 39
4.1.5 Control M X.................................................................................... 40
4.1.6 Repeater M 4.3................................................................................ 41
4.2 Connection interface modules .......................................................... 43

4.2.1 BusCon M 10 .................................................................................. 43
4.2.2 BusCon M 20 .................................................................................. 44
4.2.3 Surge Prot M ................................................................................... 45
4.2.4 Bus Isolator M................................................................................. 46
4.2.5 Terminal M...................................................................................... 47
4.3 Communication modules .................................................................. 48

4.3.1 Ethernet Switch M 8 ....................................................................... 48
4.4 Power supply modules....................................................................... 48

4.4.1 PSU M AC/DC 5A ......................................................................... 48
4.4.2 PSU M DC/DC 10A ....................................................................... 48
4.4.3 Charger M ....................................................................................... 49
4.5 Power switch modules....................................................................... 52

4.5.1 Change Over M X........................................................................... 52
4.5.2 Change Over M Ext ........................................................................ 53
4.6 Input/Output modules ....................................................................... 54

4.6.1 I/O M 70.......................................................................................... 54
4.6.2 I/O M 700........................................................................................ 55
4.6.3 MUX M 16...................................................................................... 56
4.6.4 Relay M 8........................................................................................ 56
4.6.5 NMEA 6 Input M............................................................................ 57
4.7 Loop modules .................................................................................... 58

4.7.1 Loop M X........................................................................................ 58
5 Loop devices ...................................................................................... 59
6 Configuration program..................................................................... 61
6.1 Overview ............................................................................................ 61
6.2 Description ........................................................................................ 62
6.3 The Salwico language....................................................................... 63
7 Application Examples ....................................................................... 65

7.1 Application example Industrial ........................................................ 66
8 Appendix............................................................................................ 77
Table of contents
8.1 Consilium Solution to Fulfil "Safe Return To Port"

Requirements..................................................................................... 77
8.1.1 Technical Solution .......................................................................... 77
8.1.2 Limitations of SRTP Loop .............................................................. 79
8.1.3 Final Startup of SRTP Loop............................................................ 79
8.2 Alarm Delay, Special function for Industrial applications ............. 81

8.3 Group Activation of Buzzers............................................................. 82
8.3.1 Overview......................................................................................... 82
8.3.2 Configuration .................................................................................. 82
8.3.3 Overall functionality ....................................................................... 83
8.3.4 Functionality in the Loop M X ....................................................... 83
8.3.5 Summary ......................................................................................... 85
8.4 Definitions of Terms.......................................................................... 86
Index ................................................................................................. 92
Table of contents
CCP System description & Application examples 1 System Description
1 System Description
1.1 Overview
The Salwico Fire Detection System is a state-of-the-art, analogue-addressable
control and supervision system designed to meet marine, industrial and transport
requirements. It consists of different modules and software together with a number
of Loop devices. The modules from the CCP Platform are used to build supervision
systems and the software determines how the system will react in case of a fire
indication from the Loop devices or from an input that can generate alarms. The
software continually supervises the system and will alert in case of any
malfunction.
NOTE!
The system description includes all modules that are designed for CCP regardless
of which certificates are available for the different modules. Check with marketing
or product manager which markets the specific modules are approved for.
NOTE!
This description is based on the software release 1.5.0 of the CCP.
Thanks to the modular design both large and small systems can be designed
without sacrificing the simplicity for the user.
5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C 1

1 System Description CCP System description & Application examples
Figure 1. Some Control Panels, Modules, Loop devices and Alarm devices in the CCP System.
1.2 System software

The system software has three main levels, four access levels and many
disablement possibilities.
1.2.1 Presentation layer

The control and supervision of the system is done by a Human/Machine Interface
(HMI) which eliminates the difference in the physiological topology and makes the
differences between a single central system and a multi central system hardly
noticeable. This layer serves, controls and formats the data for communication with
the user.
1.2.2 Control/Process layer

This is the Control and Supervision part that realizes the control and supervision
functions needed for a fire detection system. It communicates with other systems,
for example graphical presentation systems. Some functions are decentralized to
modules depending of the function of the module.
2 5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C

1.2.3 Module/Field layer

This is the link between the Loop devices (for example detectors), alarm devices
and magnet valves for sprinklers and the Process level. The system is flexible and
supports both Single Central System (SCS) and Multi Central System (MCS).
Figure 2. Module/Field level
1.2.4 Access levels

From the Control Panel M 4.3 and Control Panel M 2.2 the user has access to the
system, but to prevent un-authorized operation of the system, four access levels
protect the different functions of the system. To access levels 2, 3 or 4 the user has
to login to the system with different password for each level. For Control Panel M
4.3 there is also an option to use a key to unlock access level 2.
Hint!
For more information about access levels, please refer to the User Guide.
1.2.5 Disablements
There are times when it is necessary to be able to disable the system, or parts of it,
for various reasons, i.e. maintenance. The CCP system has four different
disablements available: Permanent disablement, Timer disablement, Clock
disablement and Periodic disablement. To perform a disablement the user must
have access level 2 or higher. It is possible to disable different devices attached to
the system, such as zones, detectors, manual call points, alarm devices, external
control devices and loops. All disablements will be presented in a disablement list.
An indication on the control panel will indicate when at least one disablement is
activated in the system and the indication will be active until all disablements are
reconnected.
Hint!
Instructions on how to enter a disablement is described in the User Guide.

1.3 CCP System Modules

1.3.1 Main groups of CCP modules
All CCP addressable modules must be given an unique technical address in order
to make it possible for the software to identify the modules. Instructions on how to
set the address are found on the data sheets for each module.
Hint!
The function for every module has to be configured in the Configuration program,
please refer to the Configuration Manual.
There are three main groups of CCP modules:
• Control modules.
A Controller module can act as a Primary or Secondary master controller or be
set in Managed mode controlled by a master controller. A controller stores all
events in the system whether they work as a Primary or Secondary master or
they work in managed mode.
NOTE!
Module Address 1 and 2 are reserved for primary and secondary master.
• Managed modules.
ll addressable modules except the primary and secondary master module belong
to this group.
NOTE!
Address range for managed modules is 3-125.
• Non-addressable modules.
This group includes modules such as the PSU, Change over M, Isolator M,
BusCon M10/20 and Surge Prot M.
Hint!
All CCP addressable modules have built-in FLASH Memory that can be updated
when new firmware is released. Instructions on how to update the firmware is
described in the Installation Manual.
Figure 3. Some examples of CCP modules.
1.3.2 Control Modules, information and control/process

level
In the CCP system there are different types of controllers. There can be a maximum
of eight controllers in a Single Central system.

• The Control M 4.3 has a 4.3 inch display and has the possibility to act as a
controller of the system.
• Control M 2.2 has a 2.2 inch display and has the possibility to act as a controller
of the system.
• Control M X has no display but the possibility to act as a controller.
• Repeater M 4.3 has a 4.3 inch display but cannot act as a controller. If
connected to the Backbone bus it will occupy a controller place.
Figure 4. Control Modules
1.3.2.1 A Controller in Primary or Secondary master mode

The system works on the principle of master/slave, where the master controls the
communication and monitoring. The primary master is normally responsible for
this task and the secondary master is ready to take over in real time (hot standby).
After a fault where the secondary master has taken over, the control will always
returns to the primary master when the error has been corrected. This applies to the
Backbone Bus communication within a single central system (SCS). See Multi
Central System (MCS), page 35in terms of primary and secondary master role
on the system bus that connects SCS to a multi-central system.
The system is event driven which means that any status change that is separated
from the normal value, create an event that is sent to the system.
NOTE!
The secondary master is optional.
A master controller is able to and/or responsible for the following:
• Store and disseminate the definition file to all controllers.

• Initialize all managed modules with current definitions.
• Monitor all managed modules.
• Controlling communication.
• Control and monitor I/O based on the Cause/Effect.
• Store all events in the system.
• Store history.
• Protocol conversion for optional protocols such as NMEA and Modbus.

• Communication with presentation and monitoring systems.

• Control and monitor the extension bus (14 pcs Repeater 4.3).
• Write alarm and history to a printer.
• Firmware updates of all addressable modules with the exception of the control
modules.
1.3.2.2 A Controller in Managed mode

A Managed controller is able to and/or responsible for the following:
• Store the definition file.

• Store all events in the system.
• Protocol conversion for optional protocols such as NMEA and Modbus.
• Communication with presentation and monitoring systems.
• Control and monitor the extension bus (14 pcs Repeater 4.3).
• Write alarm and history to a printer.
• Update firmware for all addressable modules with the exception of the control
modules.
1.3.3 Managed modules, Field layer

All modules in this layer are connected to Backbone Bus and they have no
connection/knowledge to the other managed modules connected to the bus with the
exception of “Basic Backup Signal” and “GA-Morse signal”. It should be noted
that the I/O-portion of a controller is treated as a virtual module and has the same
characteristics as other modules in this group!
In principle, all decisions relating to alarm, fault and status of the inputs is
decentralized to this layer. The output is controlled from the control layer by
Cause/Effect and the definitions. There are exceptions for making decisions on
whether an output should be active or not, and it is GA-Morse and Basic Backup
signals. See the description in Basic Backup Signal, BBS, page 12 and
GA-Morse (only in BBI), page 13. Also see Output override, page 23, dealing
with the priority order!
All Managed modules will be initiated with the current configuration when the
system starts up and store the configuration in its non-volatile memory. There are
some rules relating boot of Managed modules which is important to be aware of!
The boot is based on an implementation model as depicted below.

Figure 5. I/O Module Boot.
• If the master does not send a valid configuration within 15 minutes and the
module has a valid non-volatile configuration, the module shall enter isolated
mode where it monitors fire inputs and issues fire alarms on its own I/O and
using the X-Fire backbone signal.
• After the configuration has been received and verified it will be stored in
non-volatile memory (if changed) and the present output state shall be set on the
physical pins. This ends the boot mode.
• If an I/O module is operating in normal mode and the master does not poll the
module for 75 seconds, the module shall enter isolated mode where it monitors
fire inputs and issues fire alarms on its own I/O and using the X-Fire backbone
signal.


CCP System description & Application examples 2 Single Central System (SCS)
2 Single Central System (SCS)
2.1 General
A Single Central System (SCS) is a complete system that can operate
autonomously; monitor its detectors and inputs, activate its outputs and display its
faults and alarms.
If connected to other centrals, it exchanges information with the other centrals via
the System Bus, thus allowing all centrals to act as one System.
All CCP modules in an SCS system communicates and is powered via a bus called
the Backbone Bus. Each central can only have one Backbone Bus.
The Backbone Bus is designed for usage in two different environments:
• Backbone Bus Internal (BBI)

The main bus inside a Central cabinet used for communication between
Modules. It consists of two redundant RS-485 channels, two 24 VDC power
lines and the Basic Backup Signal (BBS) and GA-Morse Signal.
• Backbone Bus External (BBE)
The main bus outside a Central cabinet used for communication between
Modules and stretched central parts. It consists of two redundant RS-485
channels, two 24 VDC power lines and the Basic Backup Signal (BBS).
An important difference of Backbone Bus Internal (BBI) and Backbone Bus

External (BBE) is that BBE is designed to withstand electrical environment outside
of a cabinet and that it isolates the BBE and BBI from each other so that short
circuits and other errors do not affect the internal bus (BBI).
It is possible to stretch a central. A stretched Central is physically distributed to

two or more physical locations. The stretched centrals must be connected with the
Backbone Bus External (BBE) in order to act as if they were in the same cabinet.
One location may or may not supply power to another location (segmented) and
two locations may or may not have isolated communication lines.
In a Single Central System (SCS) there must always be one Primary Master
Controller. As an option it is possible to connect a Secondary Master Controller for
redundancy. The Secondary Master Controller will react as a Hot Standby and
work in parallel with the Primary Master Controller and store all events in the
system. It has the same configuration definitions as the Primary Master Controller,
and will take control of the system in case of any malfunction in the Primary
Master Controller.
In a Single Central System there can be up to 125 addressable modules on one

common Backbone Bus. There are limitations on the number of controls and loops
that may be included in a single central system and that is: Max 8 controllers and
64 loop modules.

2 Single Central System (SCS) CCP System description & Application examples
NOTE!
In addition a central can have up to 14 Repeater panels connected to an Extension
Bus, a bus without redundancy dedicated for repeater panels.
These repeaters on the Extension Bus are not counted as Controllers!
The number of Extension busses is only limited by the availability RS 485 ports on
the controllers in the central!
Figure 6. Example of Single Central System.

Figure 7. Example of Single Central System.
2.2 Backbone Bus

2.2.1 Backbone Bus communication
The Backbone Bus Topology used in the CCP system is a centralized network
topology in which a number of CCP modules are attached to a bus called the
Backbone Bus. All messages sent on the backbone bus hold a destination address
to the receiving module. Each module is identified by an individual address and
will only receive messages with a proper address. This system is very flexible as
new modules can be added on easily.
Each module has built-in protection to prevent internal faults in the modules to
affect the bus. This together with redundant communication and power supply
makes the system fault tolerant. If a module is damaged, the rest of the system will
continue without interference.

The protocol used for communication in the CCP system is developed by

Consilium and called CSP/CSTP. The messages are sent on two communication
channels in the Backbone Bus.
Communication parameters for BBI and BBE:
• Baud rate: 38400

• Data bits: 8
• Stop bits: 1
• Parity: non
The Backbone Bus (BBI) consists of ten conductors; the Basic Backup Signal
(BBS), the GA-Morse signal, two redundant RS-485 channels and two 24VDC
power lines.
Figure 8. Backbone Bus connections to modules.
Table 1. Backbone Bus connections to modules.

1 Basic Backup Signal, BBS (X-Fire)
2 GA-Morse (only in BBI)
3 RS-485 Communication Channel 1 D+
BBI 1
4 RS-485 Communication Channel 1 D-
5 RS-485 Communication Channel 2 D+
BBI 2
6 RS-485 Communication Channel 2 D-
7 24 VDC Power Supply 1 +
8 24 VDC Power Supply 1 -
9 24 VDC Power Supply 2 +
10 24 VDC Power Supply 2 -
2.2.2 Basic Backup Signal, BBS

The Basic Backup Signal, also known as X-Fire, is a signal in the Backbone Bus
that is used for transmitting the Central's alarm status. The BBS is only used when
a module in Managed mode loses communication with its Controller Module.

The outputs supporting the Basic Backup Signal have an X-Fire property that can
be set in the Configuration Program.
Modules not having full contact with the controller act upon the Basic Backup
Signal.
NOTE!
The pre-alarm level does not affect the Basic Backup Signal.
There are some rules for X-Fire:
• Modules that can act as a Controller are able to generate a 2.0 V Surveillance
Voltage on the Basic Backup Signal. At present only the Control Modules can
act as a Master.
• Only one Module within each Central may generate the 2.0 V Surveillance
Voltage on the Basic Backup Signal.
• All Modules that can generate alarms is able to generate the 6.0-28 V Fire
Voltage signal on the Basic Backup Signal. At present Modules with an
addressable detector loop (Loop M X) and conventional Zone ( I/O 70 M) can
generate alarms.
• If an I/O module is operating in normal or quarantine mode and the master does
not poll the module for 75 seconds, the module shall enter isolated mode where
it monitors fire inputs and issues fire alarms on its own I/O and using the Basic
Backup Signal according to their pre-stored configuration.
• Modules that can be configured to handle X-Fire Alarm shall supervise the
Basic Backup Signal for faults. At present this only excludes the Bus Isolator
Module.
Figure 9. Signal levels Basic Backup Signal
2.2.3 GA-Morse (only in BBI)

GA or General Alarm is a common activation of alarm devices with a signal
pattern generated manually via the GA button.
Charger M has a specially designed supervised input for a GA button. The Charger
module provides a HW-coupled driver circuit that supplies 24 VDC nominal for the
GA-Morse signal in the backbone.
The state of the GA-input is illustrated in the figure below.

Figure 10. GA-input states
Typical inactive resistance is 10 kΩ and typical active resistance is <4 kΩ.
The outputs supporting GA-Morse Signal have a GA-Morse property that can be
set in the Configuration Program.
GA-Morse signal is not currently supervised but have hardware that supports
supervision, the same model as Basic Backup has today.
NOTE!
GA-Morse is designed only for a common BBI in a cabinet and may not be
connected between stretched parts of the backbone bus.
2.2.4 RS-485 communication, BBI

The main bus communication consists of two redundant RS-485 channels. If the
bus is split into more than one segment in a central, the RS-485 bus shall be
terminated in both ends with a 120 Ω resistor. See separate description in terms of
termination.
A two-wire connection shall be used if the modules have common ground (-).
It is possible to split the BBI in to separate galvanically isolated segments in a

central, but then the Bus Isolator M must be used between the galvanic segments
and a loss of the direct connection for the signal GA-Morse will appear. In this
case, a three-wire connection shall be used for RS-485.
2.2.5 Power supply, BBI

The power supply consists of two redundant 24V DC lines with a maximum
current of 8A per channel. Note that the channels are redundant which gives the
result that the maximum current shared, counted on both channels, may not exceed
8A.
2.2.6 Backbone Bus Internal (BBI)

The main bus inside a Central Cabinet is used for communication between
Modules.
2.2.7 Backbone Bus External (BBE)

The main bus outside a Central cabinet used for communication between Modules
and stretched central parts. It consists of two redundant RS485 channels, two 24
VDC power lines and the Basic Backup Signal (BBS).
When there are more modules outside the cabinet, i.e. if the central is a stretched
central that consists of two or more cabinets, they must be connected to the same

Backbone Bus. This is achieved by connecting a cable from the terminals on

modules BusCon M 10, Surge Prot M or Bus Isolator M. This cable connection is
then called the Backbone Bus External (BBE).
Bus Isolator M, BusCon M 10 and Surge Prot M have built-in repeater functions
and will amplify the signal intensity and make it possible to increase the length 700
meters further. Another advantage of the built-in repeater function is that the BBI
and the BBE will be separated so if the BBE becomes short-circuit it will not
influence the BBI.
If the modules outside the central have a separate power supply it is strongly
recommended to use two Bus Isolator M modules to galvanic isolate the different
segments in order to prevent interference caused by ground current or other
sources.
By mounting additional Bus Isolator M or BusCon M 10 or Surge Prot M modules

on the Backbone Bus Internal it is possible to get up to 10 Backbone Bus External
branches (RS 485 segments) with a maximal length of 700m each from one Single
Central System (SCS), see One BusCon M 10 and one Surge Prot M H modules on
the same BBI., page 16 and Two Bus Isolator M H modules on the same BBI.,
page 16.
2.2.7.1 RS-485
RS-485 is used for the communication between modules in a stretched system.
RS-485 is a worldwide industry standard defining the electrical characteristics of
drivers and receivers for use in digital multipoint systems. The interface is
balanced and relatively insensitive to interference. There are some general
recommendations for installation of RS-485:
• Twisted pair wires should be used.

• Shielded cables must be used.
• Star networks in a RS-485 segment are not permitted.
• Termination shall be made at each end of the bus with a 120 Ω resistor to
prevent reflections in the cable.
• Max 700m cable in one communication segment.
• Two-wire connection shall be used when nodes have common ground (-).
• Three-wire connection shall be used when nodes have different grounding (-),
for example between Bus Isolator M modules.
The connections must be done with the correct polarity, in relation to each other. A
polarity error means that the equipment will interpret the data incorrectly. In the
CCP system the signals are marked with D+ and D-.

2.2.7.2 Block diagram for Bus Isolator M, Surge Prot and

BusCon M10
Figure 11. One BusCon M 10 and one Surge Prot M H modules on the same BBI.
Figure 12. Two Bus Isolator M H modules on the same BBI.
NOTE!
The channel selector inside the Bus Isolator M must be set to 1 in one module and
to 2 in the other module.
The 0.5A power output is NOT galvanic isolated.

2.2.8 Extension Bus

Extension Bus is an additional (RS485) bus. The Extension Bus is typically for
connecting Repeater Modules (that does not require redundant communication and
power) and should not be confused with the Backbone Bus.
When redundancy is not required, i.e. connecting a Repeater M 4.3, the connection
can be made by a cable with fewer conductors, only one RS485 and one Power
supply is required!
Every Extension bus can have up to 14 Repeater Panels connected. They are
included in and addressed according to the rules for Single Central System
(Address 3-125).
2.2.9 Ethernet Communication

See Multi Central System (MCS), page 35 for information.
2.2.10 Protocols, overview

All Control Modules are supporting the following protocols for communication
with external devices via RS-232, RS-422, RS-485 or Ethernet: System log printer,
NMEA 0183, MODBUS and ESPA 4.4.4.
All Control Modules supports the following protocols for communication with
external devices via Ethernet: SMS and SMIG.
Please contact Consilium support for an updated list of supported protocols and the
conditions that apply for the different types of protocols.
It is possible to supervise the status for all point detectors via the MODBUS
interface:
• Alarms status (1, 2 or pre, muted yes/no)

• Fault status (yes/no, muted yes/no)
• Disablement status (yes/no)
Hint!
For more information about Modbus protocols refer to document “6300705 CCP
Gas Modbus protocol.doc”.
2.3 Power supply

For systems with very small power consumption, up to 5A, it is sufficient to have
just one Power Supply Unit and a back-up battery for redundancy. The Power
Supply Unit (PSU) transforms the 110-230 VAC to 28 VDC. The Charger M
Delivers 19-28 VDC to the two power supply channels in the Backbone Bus
Internal (BBI) and keeps the battery fully charged. If the 28 VDC from the PSU is
lost the Charger M will switch to the power from the battery. It will also send an
alarm signal to the Control module that the mains power is missing. The PSU has
no connection to the Backbone Bus Internal. Please see the figure below.

Figure 13. Power supply from one Mains and a back-up battery.
For systems with greater power consumption needs, up to 10A, it is necessary to

use an additional Power Supply unit, see the figure below.
Figure 14. Two power supplies used when more current is needed.
In the figure above both PSUs are fed from Mains, see alternative 1, but it is
possible to connect one of the PSUs to another power supply instead, see
alternative 2. Alternative 1 will supply the system with 10A as long as there is
power from Mains, but if the Mains power is lost it will only get power from the
battery. Alternative 2 will supply the system with 10A if there is power from both
Mains and Emergency, but if anyone is lost the system will only get 5A. Only if
both external power supplies are lost the system will rely on power from the
battery.
Another way to have redundancy is to use a Change Over module to switch to the
emergency power supply if the Mains is lost, please see the figure below. If a
second PSU is used, see the alternative, the system will be supplied with 10A as
long as there is power on either Mains or Emergency.

Figure 15. Change Over module and an optional Power Supply.
There are two types of Change Over modules available, M X and M Ext, and both
have extra 110-230 VAC outputs that can be used for i.e. a printer. The Change
Over M Ext also has some programmable outputs that can be used to control
devices such as sirens, magnets, flashlights, alarms and ventilation fans. Neither of
the Change Over modules are connected to the power supply 1 or 2 in the
Backbone Bus Internal. To supervise the Change Over M X it must be connected to
Charger M terminals, but the Change Over M Ext is connected to Charger M via
the Backbone Bus.
If more power is needed it is possible to connect even more Power Supply Units. In
the figure below the modules on the upper DIN rail is supplied with 5A and the
modules on the lower DIN rail is supplied with 10A. In this example two batteries
are used, see Figure 16. It is also possible to use only one battery, see Figure 17.
When using only one battery, the battery supervision and the battery charge MUST
be disabled in the configuration program for one of the Charger M modules.

Figure 16. Power Supply with three PSU and two Batteries.
Figure 17. Power Supply with three PSU and one Battery.

2.4 Zones
In the Configuration program it is possible to define up to 9999 zones. The
advantage of using zones is that it is possible to combine loop devices belonging to
different loops to the same zone. In the configuration program the zones can be
given an explanatory text for identification, i.e. stair-well, reception etc. This will
make it easier for the user to identify the location of an activated loop device or to
disable all loop devices in a geographic area for maintenance work.
Figure 18. Module Loop M X with 2 loops.
2.5 Input/Output Interfaces

NOTE!
The information in this chapter is only valid for System modules. For Loop
modules, please see the Data sheet and the Configuration manual.
2.5.1 General
A number of I/O types are defined in the CCP system and each module has a
combination of these I/O’s. This document is only treating the most common
interfaces in the CCP, which is I/O 70, I/O 700 and relay output.
Each input that can generate an alarm shall be associated with a Zone. The zone
number shall be configured via the Configuration Program.
Normally the outputs are controlled from the Cause/Effect and definitions, but
there are exceptions whether an output should be active or not and it is GA-Morse
and Basic Backup Signals. See description in Basic Backup Signal, BBS, page
12 and GA-Morse (only in BBI), page 13. Also see Output override, page
23 dealing with the priority order!
The system includes a number of predefined groups for outputs. When the system
is defined, it is possible to associate an output to one of the groups and gives it a
feature that makes it possible to disconnect the output from the Control Panel
except for the Firm Output Group.

Predefined Output Groups:
• General output:
The I/O is used as a digital output and can be programmed from the
Cause/Effect.
• Door Output:
The I/O is used as a door output and can be programmed from the Cause/Effect.
• Bell Output:
The I/O is used as a bell output and can be programmed from the Cause/Effect.
• Fire Output:
The I/O is used as a Fire output and can be programmed from the Cause/Effect.
• Fault Output:
The I/O is used as a Fault output. A fault appears when the output is Activated.
• Ventilation Out:
The I/O is used as a output for control of fans for fire smoke evacuation and can
be programmed from the Cause/Effect.
• Indication out:
The I/O is used as a output for indication and can be programmed from the
Cause/Effect.
• Alarm Trans. output:
A supervised output for signalling that a fire has occurred.
• Firm. Output:
The I/O is Used as a general output and can be programmed from the
Cause/Effect and cannot became interlocked from a manoeuvre in the Control
Panel.
The system includes a number of predefined groups for Inputs. When the system is
defined, it is possible to associate an input to one of the groups.
Predefined Input Groups:
• Zone:
Input for a Conventional Fire Alarm Zone.
• General Input:
The I/O is used as a digital input and can be programmed from the
Cause/Effect.
• Fault input:
The loop is used as a digital input. A fault appears when the input is Activated.
2.5.2 Patterns
I/O of types I/O 70, I/O 700 and relay output is supporting patterns. It is possible to
run patterns via Cause/Effect on the I/O types supporting patterns. The patterns
shall run according to:
• Pattern mode:
One of several predefined patterns.

• Inverted pattern:
Enable/disable. Only symmetrical patterns.
• Type:
“Repeated Cyclically” or “Single Shot”.
• All I/O types supporting patterns shall run according to:
• Synchronization:
System Clock.
All I/O types supporting patterns supports the predefined patterns:
1. 7 short 1 long (GA auto).

2. 1s on, 1s off (Flash).
3. 1.5s on 1.5s off (1/3).
4. 2s on, 1s off (Finland).
5. 0.5s on, 0.5s off, 0.5s on, 1.5s off (Gas).
6. 1.5s on, 1.5s off, 1.5s on, 1.5s off, 3.5s on, 1.5s off (Poland).
7. 0.5s on, 1.5s off (Pre-alarm).
8. 1.5s on, 1,5s off, 6s on, 1.5s off.
9. 6s on, 3s off.
10.1s on, 1s off, 4s on, 1s off.
11.1s on, 1s off, 2s on, 1s off.
12.5s on, 30s off (Canada).
2.5.3 Output override

Outputs in the system are normally set via Cause/Effect (or PLC) commands but
they can have properties that override the behaviour dictated by the Cause/Effect.
Outputs supporting GA Morse, X-Fire or Patterns are set according to the figure
below.

Figure 19. Output override.
2.5.4 Synchronization of outputs

All modules that support signal pattern are synchronized. Synchronization is
handled by the master module in the central via the backbone communication. All
outputs with the same pattern originating from one module are synchronized with
each other, even if no external pattern synchronization signal is available.
2.5.5 Two relay outputs with a special behaviour

NOTE!
These two relays are designed to be the system's sum of Fire and Fault output
The two relay outputs on each controller module (Control M X, Control M 4.3 and
Control M 2.2) have the following behaviour:
• If the module software is running correctly they shall be controlled fully by

software.

• If software is not running (e.g. due to checksum fault, missing configuration or

watchdog reset) one relay, “FAULT” shall be active and the other relay, “FIRE”,
shall be controlled by the backbone signal X-Fire.
Behaviour of relay 1 on Control Modules:
• Relay 1 on Control Modules shall be activated by fault alarms if there is no

valid configuration on the Control Module.
• The relay shall be “active low”.
• The default behaviour of relay 1 on Control Modules shall be activation on fault
(active low) when configuring the system with the Configuration Program.
• Activation of relay 1 on Control Modules activation shall be configurable via
the Cause/Effect definitions in the Configuration Program
Behaviour of relay 2 on Control Modules:
• It shall be activated by fire and gas alarms if there is no valid configuration on

the Control Module
• The default behaviour of relay 2 on Control Modules shall be activation on fire
for fire centrals when configuring the system with the Configuration Program.
• The default behaviour of relay 2 on Control Modules shall be activation on gas
for gas centrals when configuring the system with the Configuration Program.
• Activation of relay 2 on Control Modules activation shall be configurable via
the Cause/Effect definitions in the Configuration Program.
2.6 I/O 70 type contacts

2.6.1 General
The main purpose of I/O type 70 is to monitor conventional detectors, digital inputs
and inductive sensors. The maximum output current is 70mA per channel. The I/O
is also used to control low power devices, e.g. buzzers and relays, an Input/Output
type providing a different function depending on the configuration of the system.
The programmable functions are:
• Not used
• Zone
• General Input
• Fault Input
• General output
• Door Output
• Bell Output
• Fire Output
• Ventilation Out.

• Indication out.
• Alarm Trans. output
• Firm. Output
Max voltage and current must be set in the definition for modules with I/O70
terminals, setting applies to all the I/O terminals on the module. It is important to
set up these limits so that power consumption and heat generation are kept as low
as possible. The system allows for a mix of inputs and outputs in the same module,
and maximum current and voltage must be adjusted for the most demanding
device.
2.6.2 I/O 70 Defined as an input for Conventional

detectors
When I/O 70 is configured as an input for Conventional detectors it is possible to
set threshold values for the following properties:
• Fault Alarm Current (default 1 mA).

Default 1 mA. Consilium/Salwico traditional fault alarm limit when 10 kΩ used
as end-of-line resistor.
• Alarm Current level 1.
Default 17 mA. Consilium/Salwico traditional alarm limit.
• Alarm Current level 2 (default 58 mA).
Alarm limit for detecting if there are alarms in more than one detector or in a
single Manual call point. Note that the detectors and alarm buttons must match
the settings to get the desired function! This means that a detector in the alarm
must not draw more than 58 mA if default values should be used. Indicators that
are connected to the detector can also increase the alarm current in the detector.
Also ensure that the Manual call point uses more than 58 mA in alarm current.
If you do not want to use this feature, set the limit to 99 mA.
• Short Circuit Fault threshold.
Default “Loop resistance < 50 Ω”.
If the above default values are used for the zone, the input will be compatible with
Salwico C300/C308/C316/CS3000-GSK centrals in terms of threshold values for
alarm and fault.
• Current below 1 mA will generate a Fault Alarm.

• Currents from 17 to 58 mA will generate Fire Alarm level 1.
• Currents above 58 mA will generate Fire Alarm level 2 (MCP).
• Loop resistance < 50 Ω will give a Short circuit fault.
• EOL resistor should be 10 kΩ (giving a nominal current of 3 mA).
There are some rules when I/O 70 is defined as a input for conventional detectors
which may be of interest to know:

• Supervision of short circuit fault is inhibited when the Conventional Zone is in

the fire state (zones in the fire condition shall never move to the short circuit
condition without resetting the fire conditions first).
• The Fire Alarm Current (see above) shall be above the threshold limit for 100 -
200 ms before generating the Fire Alarm 1/2.
• The input is disconnected for 2 seconds (no voltage out) when attempting to
reset the fire condition. The reason for this is that most conventional detectors
are locked in the fire condition until power is removed.
2.6.3 I/O 70 Defined as an Output

When I/O 70 is configured as an output, the output is always Short supervised
when it is active. It is possible to configure the following properties for I/O type
70 when it is used as output:
• Active high or active low.

• Enable/disable of GA Morse.
• Enable/disable of X-Fire
NOTE!
It is not possible to supervise connected devices or an end of line resistor! And it is
not possible to short supervise the cable or device when the output is deactivated.
NOTE!
The threshold limit for Short supervised or overload is the same as “Max Current
for each Terminal (mA)” according to the definition program!
2.6.4 I/O 70 Defined as an Input

When an I/O 70 is configured as an input it is possible to set the current limit for
active and deactivated input. (Alarm1 = current limit, Alarm 2 is not used) It is also
possible to set the current level for Break supervision and the resistance level for
Short supervision.
If the I/O70 input is not supervised the state of the input is illustrated in the figure
below.
Figure 20. Signal levels, no Supervise.
If the I/O70 input is break supervised, the state of the input is illustrated in the
figure below.

Figure 21. Signal levels, Break Supervised.
If the I/O70 input is “break supervised” and “short circuit supervised”, the state of
the input is illustrated in the figure below.
Figure 22. Signal levels, Break and Short circuit Supervised.
Please see the Configuration manual for details.
2.6.4.1 Dry Contacts

When an I / O 70 is configured as an input and dry contacts shall be used, we
recommend the following settings:
• Without serial resistor (type 1 in the figure below)

Set at least the maximum current to: 6 mA
Current level (Alarm 1 (mA)): 5mA
Short-circuit monitoring is not possible!
• With serial resistor (type 2 in the figure below)
Short-circuit monitoring is possible !
• Supervision of cable break without serial resistor (type 3 in the figure below)
Set at least the maximum current to: 6 mA.
Break Level: 1 mA End of Line resistance: 10 kΩ
Short-circuit monitoring is not possible!
• Supervision of cable break with serial resistor (type 4 in the figure below)
Break Level: 1 mA End of Line resistance: 10 kΩ
Short-circuit monitoring is possible!

Figure 23. Dry contacts.
2.6.4.2 Inductive proximity switch, 2/3 wire

When an I/O 70 is configured as an input and proximity switches shall be used, we
recommend the following settings:
The recommended settings are dependent on the switches electrical properties.

Following example assumes that two wire sensors have a voltage range that is at
least 19-30 VDC and that the No-load supply current < 2 mA (standby current
non-active) and for three wire sensor a voltage range that is at least 19-30 VDC and
No-load supply current is in the range of 8-15 mA.
Recommended settings with a serial resistance of 1,5 kΩ, without cable break
supervision:
• Type 1 in the figure below:

Current level (Alarm 1 (mA)): 5 mA
Short-circuit monitoring is possible !

Figure 24. Inductive proximity switch, 2/3 wire.
2.7 I/O 700 type contacts

2.7.1 General
The main purpose of I/O type 700 is to monitor, to control or to supply power
devices like alarm devices, magnets, repeater panels etc. The maximum output
current is 700mA per channel.
NOTE!
It is very important to have control over the total load in a system. A bus segment
of BBI can handle up to 8 A and the total current of the modules that are connected
to a single segment must not exceed this limit.
It is especially important to specify the correct maximum current for the modules
which contains I/O 700 types such as for the I/O 700 M where the maximum
current for the entire module has to be specified.
The I/O type 700 can be defined with functions to control, supervise and
voltage-feed different devices. It is also possible to give an output properties as
synchronizing, anti-phase activation, inverted output and supervision of
short-circuit or cable break. An output can also be defined to function as an input.
There are different signal characteristics stored that can be activated and
programmed from the configuration program. Supervision is done by the principle
of reverse polarity so all devices that shall be short supervised must be internally
polarized or have a diode connected in series.
An Input/Output type provides a different function depending on the configuration

of the system. The programmable functions are:
• Not used
• General Input
• Fault input

• Fire input
• General output
• Door Output
• Bell Output
• Fire Output
• Ventilation Out.
• Indication out.
• Alarm Trans. output
• Firm. Output
2.7.2 Controlling alarm devices

2.7.2.1 Supervised break and short-circuit in cable
All connected devices must be polarity dependent and the last device must have a
30 kΩ resistor. In the Configuration program:
• Check the box “Break Supervised”.

• Check the box “Short Supervised”.
2.7.2.2 Cable interruption

Connected devices does not need to be polarity dependent and the cable will be
supervised up to the first device which is not polarity dependent. In this mode of
operation the supervision of short-circuit is doubtful and shall not be activated. In
the Configuration program:

• Uncheck the box “Short Supervised”.
2.7.2.3 Supervision of One device

If just one device shall be supervised it must not be polarity dependent. In this
mode of operation the supervision of short-circuit is doubtful and shall not be
activated. In the Configuration program:

2.7.2.4 Anti-phase activation

The purpose of anti-phase activation is to reduce the current consumption. All
outputs within a module with the same signal characteristics are automatically
synchronized and will activate all outputs at the same time. By activate anti-phase
activation some outputs can be set to be activated when other outputs are
de-activated. This functionality should be avoided if there is cross-induction
between rooms. If more devices are connected to a common synchronizing signal
the anti-phase activation is valid for these to.

In the Configuration program:
• Check the box “Anti-phase”.
NOTE!
This function shall only be used when the signal characteristics are symmetric.
2.7.2.5 Inverted output

This function is normally not used when alarm devices are connected to the output,
but may be used. The output will be alive until it is activated. In the Configuration
program:
• Check the box “Active low”.
2.7.3 I/O 700 controlling Magnets

An electromagnet may be connected to a relay output or to an I/O 700 contact.
When connected to an I/O 700 contact it is suitable to invert the output so it is
normally powered and not powered when the output is activated.
In the Configuration program:
• Check the box “Active low”.

NOTE!
The Short supervision must be de-activated.
2.7.4 I/O 700 used as input

I/O 700 outputs can in the configuration program be defined individually as digital
supervised inputs and be given properties as general input, fault input or alarm
input.
I/O 700 contacts is a low power input limited to 700 µA and the cable length
between central and sensor shall be less than 50 meters and it is designed for dry
contacts.
The state of the input is illustrated in the figure below.
Figure 25. Typical inactive resistance is 30 kΩ and typical active resistance is < 4 kΩ.
2.7.5 I/O 700 used as Power output

I/O 700 outputs can in the configuration program be defined with the property
"Active low" and be assigned to the group "Firm. Output" and this will give one
output that has a fixed output voltage. There are some disadvantages with such an

output and it should not be used for controllers or repeaters, because the output is
activated first when the local module's CPU is running and it may give some
start-up problems.
In the module I/O 700 M is it possible to activate the output as a power supply
even if the CPU in the module is not running. See I/O M 700, page 55 for more
details.
It is possible to connect up to three outputs in parallel, if the power demand is

greater than 700 mA.


CCP System description & Application examples 3 Multi Central System (MCS)
3 Multi Central System (MCS)
A Multi Central System (MCS) can cover a larger area than a Single Central
System (SCS) and is only limited by the System Bus. It can consist of up to 30
Single Central Systems connected in a network.
The SCS with the Central number 1 will act as a System Bus Controller and
handles all communication on the System Bus between all SCS in the MCS. All
messages from one SCS to another SCS will be sent on the System Bus to the
System Bus Controller who will re-direct it to the SCS in question.
It is always SCS 1 that will act as the System Bus Controller.
If the Master Controller in Central 1 malfunctions, the Secondary Master

Controller in Central 1 will take over the control of the System Bus. If the
Secondary Master Controller likewise malfunctions, all SCS in the MCS will
operate separately and cannot communicate with each other.
Figure 26. Example of a Multi Central System.
3.1 System Bus

The communication bus used for connecting Single Central Systems to form a
Multi Central System is called the System Bus. It is used for inter-central
communication. If inter-central communication redundancy is required, the system
bus must consist of a Primary System Bus and a Secondary System Bus.

3 Multi Central System (MCS) CCP System description & Application examples
In a Multi Central System the primary and secondary System Bus is controlled by
the Primary master and secondary master in SCS central no 1.
The communication on the system bus is the CSprot protocol delivered on RS-485
or Ethernet. When Ethernet is used the CSprot protocol is embedded in the TCP/IP
protocol.
If a multi-central system has redundant inter-central communication, the following

system bus scenarios are supported:
• Two independent Ethernet buses (primary + secondary).

• Two independent RS-485 buses (primary + secondary).
• One Ethernet plus one RS-485 (either of them shall be used as the primary bus,
the other will be secondary).

CCP System description & Application examples 4 CCP Modules Descriptions
4 CCP Modules Descriptions
NOTE!
The system description includes all the modules that are designed for CCP
regardless of which certificates are available for the different modules. Check with
marketing or product manager which markets the specific modules are approved
for.
4.1 Control modules

4.1.1 Overview
In the CCP system there are three modules that can act as Control modules and one
Repeater module. The three control modules have the same control possibilities,
but different HMI functions.
All Control modules can be set in Controller mode as a Primary or Secondary

master controller or be set in Managed mode controlled by a master controller.
4.1.2 Control modules in control mode, Addressing

rules
There are some addressing rules for Control modules in control mode (Dip switch
8 On) that must be followed when configuring a system:
Unit Dip switch SW2 Function Backbone Bus

settings Address
No. 1-5 No. 6 No. 8
(Central
number)
Single Central System (SCS)
Control 1 On On Primary Master 1
modules 1 Off On Secondary Master 2
Multi Central System (MCS) containing 3 SCS
Control 1 On On Primary System bus Controller 1
modules and Primary Master in SCS 1
1 Off On Secondary System bus 2
Controller (option) and
Secondary Master in SCS 1
2 On On Primary Master in SCS 2 1
2 Off On Secondary Master in SCS 2 2
3 On On Primary Master in SCS 3 1
3 Off On Secondary Master in SCS 3 2
If the Control module is set to Managed mode, Dip switch 8 Off, the address can be
set to 3-125.

4 CCP Modules Descriptions CCP System description & Application examples
4.1.3 Control M 4.3
The Control M 4.3 is a Control module with a 4.3" graphical colour display. It
communicates with other modules on the redundant bus system. It can also be
connected to other systems via high-speed interfaces such as Ethernet 10/100 Mb/s,
RS-485, RS-422 or digital I/O. It can act either as a Primary Master Controller, as a
Secondary Master Controller, or as a Managed module depending on the setting of
DIP-switches.
Control M 4.3 can be delivered in a cabinet for flush or surface mount installation,
or flush mounted in a larger cabinet together with other CCP modules.
The Control M 4.3 is equipped with an USB host for USB flash drive to load or
save a configuration file and update firmware.
In the Configuration program the Control M 4.3 can be set to any address between
1 and 125. The default value will be 1 if it is the first module of this type to be
added, otherwise it will get a higher number as default.
Control M 4.3 provides:
• Two programmable I/O 70 channels, see I/O 70 type contacts, page 25 for
details.
• Two programmable Relay contacts, see Two relay outputs with a special
behaviour, page 24 for details.
• USB, Host.
• One Ethernet 10/100 Mbit (RJ-45), autosense.
• Backbone Bus Interface, BBI or BBE depending on the connection board.
• One isolated RS-422/RS-485 interface.
Control M 4.3 has no terminals for installation cables, but there are three CCP
modules that are designed specifically for this purpose. These modules are
connected to the Control M 4.3 via 10/20 pin ribbon cable and has the following
properties:

• BusCon M 20
Connects the Control M 4.3 to the backbone bus (BBI) and provides connection
terminals for functions from Control M 4.3.
• BusCon M 10
Terminal board for functions in Control M 4.3 and Terminal board for
Backbone Bus External BBE (Two RS485 Repeaters are built-in).
• Terminal M
Provides terminals for all functions integrated into the Control M 4.3 and
terminals for a complete backbone bus external (BBE).
See the section for the individual modules for details!
NOTE!
The software in a Control M 4.3 cannot be updated centralized. Each controller
must therefore be updated via an USB flash drive.
4.1.4 Control M 2.2
The Control M 2.2 is a DIN-rail mounted Control Panel with a 2.2”graphical

colour display that manages and supervises a system. It communicates with other
modules on the redundant bus system. It can also be connected to other systems via
high-speed interfaces such as Ethernet 10/100 Mb/s, RS-485, RS-422 or digital I/O.
It can act either as a Primary Master Controller, a Secondary Master Controller, or
as a Managed module depending on the setting of DIP-switches.
The Control M 2. is equipped with an USB host for USB flash drive to load or save
a configuration file and update firmware.
In the Configuration program the Control M 2.2 can be set to any address between
1 and 125. The default value will be 1 if it is the first module of this type to be
Control M 2.2 provides:
• Two programmable I/O 70 channels, see I/O 70 type contacts, page 25 for
details.

• Two programmable Relay contacts, see Two relay outputs with a special
behaviour, page 24 for details.
• USB, Host.
• One Ethernet 10/100 Mbit (RJ-45), autosense.
• Backbone Bus Interface, BBI.
• One isolated RS-485 interface.
NOTE!
The software in a Control M 2.2 cannot be updated centralized. Each controller
must therefore be updated via a USB flash drive.
4.1.5 Control M X
The Control M X can serve as Bus Masters, i.e., operate in Controller Mode or in
Managed Mode, for example repeaters and protocol converters. One control
module per central shall be set in Controller Mode. If the system shall be redundant
it is required to have a second control module, also set in Controller Mode. Modes
for Managed and Controller are set with DIP switches. It can be connected to other
systems via high-speed interfaces such as Ethernet 10/100 Mb/s, RS-485, RS-422
or digital I/O.
This module provides:
• two programmable Relay contacts, see Two relay outputs with a special
behaviour, page 24 for details
• a USB Host
• one Ethernet 10/100 Mbit (RJ-45), autosense
• a Backbone Bus Interface
• one isolated RS-422/RS-485 interface
• one isolated RS-232 interface

NOTE!
The software in a Control M X cannot be updated centralized. Each Control M X
must therefore be updated via a Ethernet with a special software. Please see the
service documentation for more details!
In the Configuration program the Control M X can be set to any address between 3
and 10. The default value will be 3 if it is the first module of this type to be added,
otherwise it will get a higher number as default.
4.1.6 Repeater M 4.3
The Repeater M 4.3 is a Repeater Panel with a 4.3" graphical colour display used
to indicate system status. Repeater M 4.3 can be mounted on any flat surface or
flush mounted. It is connected to the backbone bus or Ethernet and can therefore be
independently mounted from the central module.
The repeater can operate in three different modes and the functionality depends on
systems application. Configuration is done individually in each unit via a menu
system where the following settings must be made:
• Central number.
• Backbone bus address.
• Operational mode.
The following operating modes are available:
• Local Presentation, three list version. (Config. = “marine”).

Indicate system status for fire alarms, faults and disablements.
Handling of a built-in local buzzer.

Figure 27. Overlay, three list version.
• Local Presentation, single list version. (Config. = “fire”)

Indicate system status for fire alarms.
Handling of a built-in local buzzer.
Figure 28. Overlay, single list version.
• Alarm Organisation, Swedish Industrial market (Config. = “larmorg”).

Indicate system status for fire alarms and is a member of the delay function for
“Alarm Organisation”. See Alarm Delay, Special function for Industrial
applications, page 81 for more details!
Figure 29. Overlay, Swedish Industrial market.
Repeater M 4.3 provides:
• Backbone Bus Interface, BBE or Extension bus (No support for X-Fire).
• Three programmable Outputs, 24 VDC, 40 mA.
• Two inputs for dry contacts.

NOTE!
Repeater M 4.3 is a member of the family of controllers in CCP and therefore it
also stores the configuration file and uses the supplementary text when it displays
Alarm, Fault and Disablements! The Repeaters will be updated with the correct
configuration file from either the primary or secondary master.
NOTE!
The software in a Repeater M 4.3 cannot be updated centralized. Each repeater
must therefore be updated via a USB flash drive.
4.2 Connection interface modules

4.2.1 BusCon M 10
BusCon M 10 has two major functions that can be used together or individually:
• Terminal board for Backbone Bus External BBE (Two RS485 Repeaters are
built-in)
• Terminal board for functions in Control M 4.3.
NOTE!
In order to use the functions in Control M 4.3 the flat 10-conductor cable must be
connected between the Control M 4.3 and the BusCon M 10.
The unit has no address in the system.

Figure 30. Block diagram for BusCon M 10.
4.2.2 BusCon M 20
The BusCon M 20 connects the Control M 4.3 to the backbone bus internal (BBI)
and provides connection terminals for functions from Control M 4.3.

Figure 31. Block diagram for BusCon M 20.
4.2.3 Surge Prot M
The Surge Prot M has three major functions:
• Surge protected power inputs for the Backbone Bus Internal, BBI.
• Terminal board for the Backbone Bus External, BBE (two RS-485 Repeaters
are built-in).
• Electronic short circuit protected power outputs for Control or Repeater panels.
Note! This output is not supervised.
These functions can be used together or individually.
The module is designed to be used where there are no requirements for electrical
isolation between devices. The module has built-in terminators for BBI and BBE.

Figure 32. Block diagram for Surge Prot M.
4.2.4 Bus Isolator M
The Bus Isolator M divides the system backbone bus into segments. Its dual
functionality isolates communications and basic backup signals between the
stretched system parts and provides power to the control panel (e.g. Control M
4.3).
NOTE!
Each Bus Isolator M has a built-in electrically isolating repeater for one RS-485
channel and for the X-Fire signal (BBS).
Bus Isolator M is strongly recommended when extracting the system backbone bus
using separate power sources for the different segments in order to prevent
interference caused by ground currents or others sources.
The Bus Isolator M has only one communications channel, so two modules are
needed to create one BBE-bus. Select the appropriate channel with the channel
selector.

CAUTION!
Only one of X-Fire signals may be connected when two Isolators work in pairs.
NOTE!
BBS and the RS-485 channels on a single module has a common signal ground, so
only one wire for signal ground needs to be installed between the modules.
Figure 33. Block diagram for two Bus Isolator M modules on the same BBI.
NOTE!
The channel selector inside the Bus Isolator M must be set to 1 in one module and
to 2 in the other module.
The 0.5A power output is not galvanic isolated.
4.2.5 Terminal M
Terminal M provides terminals for all functions integrated into the Control M 4.3
and terminals for a complete backbone bus external (BBE).

4.3 Communication modules

4.3.1 Ethernet Switch M 8
An Ethernet Switch for 8 channels.
4.4 Power supply modules

4.4.1 PSU M AC/DC 5A
The PSU M AC/DC 5A powers the system. It is short-circuit proof and can be used
in pairs to supply 5+5 A.
This unit has no address in the system.
4.4.2 PSU M DC/DC 10A

PSU M DC/DC 10A powers the system.

4.4.3 Charger M
The CM-1 provides distribution of system power:
• Power is received from one or two PSUs, or from a battery if both PSU supplies
are lost.
• Power can be supplied to either one or both backbone power feeds, to a standby
battery (for recharging), or to a separately controllable power output.
Charger M monitors the voltage and current levels of all the power flows in and out
of the module. Multiple levels of overload protection are providing. The maximal
current to the output and to the backbone bus is configurable.
The Charger M also supports the following functionality by connection of external

equipment:
• Status monitoring of two separate main supplies.

• Connection of a General Alarm button.
• Connection of a remotely located battery temperature sensor.
It is possible to connect two charger modules on the same bus, feeding the system
modules from both sides. When this power method is used, one of the power lines
out from the charger module is disabled making each charger module feed one of
the two bus power lines. This gives a power redundancy on the bus in those cases
the charger module itself breaks down.
The Charger M has a built in intelligent battery charger for handling of battery
power source of the system. The charger module supports seamless gating between
power from the PSU and the BAT.
For more details about Charger M and power supply for the system, see Power
supply, page 17.
Charger M provides:
• Two power supply inputs, max 10 A for each input.

The sum of backbone 1, backbone 2, programmable output and battery charging

current shall be less than 10 A (nominally).
• One battery input.
• Two inputs for supervision of main and emergency power supply.
The inputs are designed to be connected to either one Changeover M, or directly
to one PSU M AC/DC 5A.
• One programmable high current output , max 8 A and 28 VDC.
• One NTC Thermistor input, for Temperature Measurement.
• One supervised input for a General Alarm Button (10 kΩ EOL).
For details about this input, see GA-Morse (only in BBI), page 13.
The programmable output can be associated with the following groups:
• General output.
• Door output.
• Bell output.
• Fire output.
• Fault output.
• Ventilation output.
• Indication output.
• Alarm Trans. output.
• Firm. output.
And it is possible to give the outputs the following properties:
• Active High or Active Low.

• Enable/disable GA-Morse.
• Enable/disable X-Fire.
For details of these groups, see Input/Output Interfaces, page 21.
The inputs for power supply and battery are protected with a 15 A fuse. This fuse
will blow on a damaging over-current or when a power source is connected with
the wrong polarity.
When DIP-switch pole 10 is set to ON the high current output is constantly active
as long as the module is powered (on condition that output NOT USED is set in the
Configuration).
Charger M adjusts its charging parameters depending on ambient temperature

which is monitored by the NTC resistor. This allows full capacity of rechargeable
batteries in a wide temperature range with optimal performance ensured between
-5ºC and 40ºC.

NOTE!
Batteries connected to the Charger M must be of the type Valve regulated lead acid
batteries (AGM).
NOTE!
The Charger M is not designed to charge batteries that have been discharged too
deeply. In this case, replace the battery or charge it separately with a charger
designed for this purpose.
NOTE!
When battery charging is enabled, the Charger M outputs will be shut off if the
battery voltage falls below 21 VDC (+/- 0.5 V) during the absence of power to
PSU 1 or 2. However, the Charger M will stay in standby mode and require
approximately 25mA which will slowly drain the battery further.
NOTE!
If the Charger M stays in standby mode for more than 1 hour, physical battery
disconnection becomes mandatory. This prevents draining the batteries to a voltage
level too low to recharge them when main/emergency power is reestablished.
NOTE!
Charger M can handle up to 8 A total of all outputs. This includes the power to the
Backbone bus. The current for the two backbone power outputs on the Charger M
shall be added and handled as one output when calculating the current (IBB) on the
backbone bus.
NTC Thermistor properties
The default sensor type is connected directly to the connection terminals. It is used
whenever the batteries are built into the central unit. The second sensor can be used
when the batteries are remotely located, and when temperature compensation of the
charging voltage is required.
1. Default: VISHAY 10 kΩ NTC, 238164064103 (default).

2. TEMPATRON/CAREL 10 kΩ Stainless Steel Sheathed NTC, CAREL
NTC015W (Farnell Order Code: 940021).
The NTC thermistor resistance when the temperature is 25°C is 10 kΩ +/- 1% .
It is possible to emulate 22°C with a resistor of 11 kΩ with an accuracy of 1%.

4.5 Power switch modules

4.5.1 Change Over M X
The Change Over M X can switch automatically between two power sources,
mains and emergency, with preference towards mains power if both sources are
operational.
The Change Over M X is used to connect to the Power Supply Unit module in a
system, and is also provided with one extra power supply outlet (which can be used
for example to a printer or to a secondary PSU). The PSU is a separate module
without any contact with the backbone bus.
Change Over M X provides:
• One input for mains 100-240 VAC.

• One Input for emergency 100-240 VAC.
• Two Output 100-240 VAC, 3A (PSU or printer).
• One output, power monitoring mains (Designed for be connected to the Charger
M).
• One output, power monitoring emergency (Designed for be connected to the
Charger M).

4.5.2 Change Over M Ext
Change Over M Ext monitors mains and emergency power inputs and gives fault
indication if either supply is lost. The power input status is indicated by the front
panel LEDs.
Change Over M Ext provides two separate controllable 230 VAC outputs, OUT 3
and 4, protected by separate front mounted fuses. There are also two separate
programmable change over relays, OUT 5 and 6.
OUT 3-6 are used to control devices such as sirens, magnets, flashlights, alarms
and ventilation fans.
Change Over M X provides:
• One input for mains 100-240 VAC.

• One input for emergency 100-240 VAC.
• Two output 100-240 VAC, 3A (PSU or printer).
• Two separate programmable Relay contacts, No, C, Nc 100-240 VAC 5A.
• Two separate programmable outputs 100-240 VAC, Fuse with 2A, Fast 5x20
mm.
The programmable Relay contacts and the programmable outputs can be associated
with following groups:
• General output.
• Door output.
• Bell output.
• Fire output.
• Fault output.


• Firm. output.

For details of this groups, see Input/Output Interfaces, page 21.
In the Configuration program the Change Over M Ext can be set to any address
between 3 and 125. The default value will be 9 if it is the first module of this type
to be added, otherwise it will get a higher number as default.
4.6 Input/Output modules

4.6.1 I/O M 70
The main purpose for the I/O M 70 module is to monitoring conventional detectors,
digital inputs, inductive sensors and control low-power devices, such as buzzers
and relays.
I/O 70 M provides:
• Eight programmable I/O 70 channels. See I/O 70 type contacts, page 25 for
details.
Max voltage and current shall be set in the definition for the module. Setting
applies to all the I/O terminals on the module. It is important to set up these limits
so that power consumption and heat generation are kept as low as possible. The
system allows a mix of inputs and outputs in the same module and maximum
current and voltage must be adjusted for the most demanding device.

NOTE!
We recommend to always put the voltage level to the max (27 VDC), unless
special reasons exist to reduce it to a lower level.
In the Configuration program the I/O M 70 can be set to any address between 3 and
125. The default value will be 50 if it is the first module of this type to be added,
otherwise it will get a higher number as default.
4.6.2 I/O M 700
The main purpose of the I/O M 700 is to control and supervise different types of
control devices such as sirens, alarm bells, magnets and flash lights. It is possible
to use the outputs as inputs and thus make them available for general purpose
control. With the DIP address switches it is possible to set the outputs in groups of
four to function as fixed power outlets, independent of the status of the CPU on the
printed circuit board (PCB) in the module.
I/O 700 M provides:
• Eight programmable I/O 700 channels. See I/O 700 type contacts, page 30 for
details.
NOTE!
When DIP-switch pole 8 is set to ON power outputs 5 to 8 is constantly active as
long as the module is powered (on condition that output 5 to 8 is set to NOT USED
in the Configuration).
NOTE!
The maximum allowed current for the entire module must be specified in the
configuration. Maximum 4 A is allowed, do not specify too large current!
Remember that Backbone bus can handle up to 8 A and that other modules also
consumes power from the bus. If the needs of current in a bus exceeds 8 A, the bus
must be split into different power segments with the help of multiple Charger M.
NOTE!
If current consumption exceeds the maximum allowed for I/O 700 M, outputs will
be deactivated one by one until the current falls below what is set to be the
maximum current.

In the Configuration program the I/O M 700 can be set to any address between 3
and 125. The default value will be 64 if it is the first module of this type to be
4.6.3 MUX M 16
The MUX M 16 is a multiplexer with 255 outputs, dedicated for programmable

LEDs. The multiplex function can for example be used for mimics etc.
There are also inputs/outputs for buzzer, lamp test, buzzer mute, LED dimmer and
LED sync.
The module is connected via the system’s Backbone Bus.
In the Configuration program the MUX M 16 can be set to any address between 3
4.6.4 Relay M 8
The main purpose of the Relay M 8 is to control devices such as sirens, magnets,
flashlights, alarms and ventilation fans.
Relay M 8 provides:

• Eight programmable relay contacts.

Each of these relay contacts provide a potential free change-over contact.
The programmable Relay contacts and the programmable outputs can be associated
with following groups:
• General output.
• Door output.
• Bell output.
• Fire output.
• Fault output.
• Firm. output.

In the Configuration program the Relay M 8 can be set to any address between 3
4.6.5 NMEA 6 Input M

A Module used for receiving 6 NMEA channels.

4.7 Loop modules

4.7.1 Loop M X
Loop M X includes one addressable detector loop interface handling up to 254

addressable detectors or other loop devices.
Module activity can easily be monitored on the fault and alarm indicators on the
front panel as well as on the display of the Central module. A maximum of 64
Loop M X modules can be connected to one central module. The loop interfaces
are using FSK modulation which is extremely robust making cable length up to
3000 meters possible, with no particular requirements on the cable properties.
The cable with its detectors and other loop devices are continuously monitored for
possible faults and disturbances providing the highest possible safety.
In the Configuration program the Loop M X can be set to any address between 1
In order to decrease current consumption on the loop the number of detectors with
steady light LEDs are restricted to four.
If more than four detectors on the loop detects fire, only the first four detectors will
indicate fire with steady light LEDs and the rest will indicate fire with blinking
LEDs.
The Loop M X module remembers in which order the detectors detected fire, so if
a fire alarm in a detector is reset the next detector that detected fire will switch
from blinking light to steady light.

CCP System description & Application examples 5 Loop devices
5 Loop devices
All types of fire detectors, gas detectors, manual call points and other devices that
can be connected to a loop are called Loop devices. There are two types of loop
devices; conventional loop and addressable loop devices.
When a conventional loop device is activated it is not possible for the system to
identify which loop unit that is activated, only to which loop the loop device
belongs. As there may be up to 50 conventional loop devices in one loop it can be
difficult to identify the location of the activated loop device. If a conventional loop
device is connected to an Address unit, it is possible to integrate it to a loop with
addressable loop devices.
When using addressable loop devices every device is given an unique technical
address between 1-254 to make it possible for the system to distinguish the loop
devices. The technical address is set during the installation either with a DIP switch
on the device or with a special address programming tool. In the Configuration
program every single addressable loop device can then be given an individual
explanatory address and assigned to a geographical zone. This makes it easy to
identify the exact location of an activated loop device.
Figure 34. Some Loop devices.

5 Loop devices CCP System description & Application examples

CCP System description & Application examples 6 Configuration program
6 Configuration program
6.1 Overview
Before the system can be used, it must be both physically and functionally
configured. The configuration program is especially designed for creating a system
configuration file for a system. The configuration program is designed to run on a
computer that can support Microsoft Windows NT, XP, 2000, Vista or Windows 7.
Hint!
For more information about the configuration program, see the separate
Configuration Manual.
Once the configuration file is created it must be downloaded to the control panel in
the system. This is done by using an approved USB memory stick. The
configuration file must have the file extension “.ccp”. If the configuration later has
to be modified it is possible to make minor modifications from the control panel. It
is not necessary to use a computer for making minor modifications, but it is
possible to download the current configuration file from the system to the
computer, modify the file and upload it again to the control panel in the system.
When the system is started, the master controller initiates all modules in the system
with the specific data from the configuration file. If one or more modules are not
initiated after 15 minutes the previous approved definition is used for the local
functions on those modules.

6 Configuration program CCP System description & Application examples
6.2 Description
Figure 35. The Start screen when opening a new configuration.
In the configuration program there are seven main modules:
• The Options module includes information about the current configuration file.
• The User Access module is used to handle new and existing users of the
system.
• In the Zones module there is a list of all zones defined in the system. It is
possible to name the zones.
• In the Show/Control module, system modules and zones are dedicated to
groups, and group status for the control modules is defined.
• The System Bus module is used to change the system bus settings.
• The Cause/Effect module is used to switch between Salwico Language and
PLC for programming in the Central module. The PLC is not yet implemented
in the program.
• In the Central module the centrals are defined physically and functionally. The
physical configuration handles the definition of central modules, serial
communication ports, zones, loops and loop devices and supplementary texts.
The functional configuration defines how the inputs and outputs of the system
should react.

CCP System description & Application examples 6 Configuration program
Hint!
For more information about the configuration program, please refer to the
Configuration Manual.
6.3 The Salwico language

An essential part of configuring a system for control and supervision is to specify
its reaction for certain events, for example what will happen if a sensor is activated.
To simplify the configuration of the system, Consilium has developed the Salwico
language. It consists of a set of commands and a well-defined syntax. The
commands are entered in Cause/Effect sheets located under the 'Salwico
Language' branch in the module tree window.
Hint!
The Salwico language is described in detail in the Configuration Manual.

6 Configuration program CCP System description & Application examples

CCP System description & Application examples 7 Application Examples
7 Application Examples
On the following pages there are application examples for:
• Industrial application
• Transport application (to be added later)
• Marine application (to be added later)

7 Application Examples CCP System description & Application examples
7.1 Application example Industrial











CCP System description & Application examples 8 Appendix
8 Appendix
8.1 Consilium Solution to Fulfil "Safe Return To

Port" Requirements
Consilium Marine and Safety AB offers principal technical solutions fulfilling the
Safe Return To Port requirement published in SOLAS 2010.
8.1.1 Technical Solution

Basic principles used in this solution are:
• Hot-Standby CPU Redundancy.

• Double-fed Loops.
8.1.1.1 Single Central Block Diagram
Figure 36. Single Central Block Diagram.
8.1.1.2 Hot-Standby CPU Redundancy

The Main Central, e.g. Control M 4.3, in the figure above is a unit polling and
controlling other modules and their devices (connected to one and the same
Backbone Bus). There is an equivalent unit installed in the Sub Central as a
Hot-Standby backup Control Module. These two centrals and all the modules are
connected using one and the same Backbone Bus connection.
The Control Panel controls, presents, stores and distributes all events from an entire
Single Central system with the use of external protocols. The database tracking
these events is synchronised in real-time with the database of its Hot-Standby
backup unit.
Both Control panels are at all times available show their status and control all
events.

8 Appendix CCP System description & Application examples
In case of a fatal failure on primary Control M 4.3, the malfunction causes

secondary Control M 4.3 to become the poll master, insuring continuous function
of the system.
For this functionality, equivalent units to Control M 4.3 are Control M X and
Control M 2.2.
8.1.1.3 Double-fed Loops

Loop M units are, independently from CPU units, linked in two ways:
1. Communicating on Backbone Bus.

2. Handling the loop and all the devices using the loop cable.
The function of these Loop Ms is principally bistable. Any Loop Ms will

immediately become the master if malfunction of the Master Loop M is recognised
by any connection means (i.e. backbone bus or loop cable connection). Events
from the loop Unit are further reported to the Control Modules handled by them
and from there.
8.1.1.4 Common Fault States

8.1.1.4.1 Backbone Bus Single Channel Communications Break
In a case of single channel break the normal operation of the system is insured by
the secondary Backbone Bus channel.
8.1.1.4.2 Backbone Bus Dual Channel Communications Break

In this case both of the control modules become primary masters and runs each
central separately. Device status and events are available from each control module
for each central respectively.
Loop modules continue to run the loops and to keep track of the loop devices
without interruption. Events, such as fire alarm, from two different loops can be
reported from two different control panels depending on which one of loop
modules happened to run the loop at the moment of the communication break.
8.1.1.4.3 Earth Fault on the Loop Cable

A single earth fault on the loop cable does not obstruct normal operation of the
system.
8.1.1.4.4 Short Circuit on the Loop Cable

In case of short circuit on the loop cable, the voltage drop is recognised by both
loop modules running the loop. An investigation process will be started from both
sides identifying the position of the short circuit. The area between two short
circuit isolators where a short circuit is identified is isolated. The operation of the
loop on both sides of the isolation are established by each Loop M respectively.
Control panels will operate normally. Information about all operating loop units is
available on both control panels.

8.1.1.4.5 Cable Break on the Loop Cable

A cable break on the loop cable will result in the loop being operated by both loop
modules, one on each side of the cable break. Events, such as fire alarm, and status
of loop units are synchronised by the control modules. Information, status and
events of loop units are presented on both control panels.
A cable break of intermittent nature can cause the loop modules to handle the cable
break as a short circuit and isolate a relevant part of the loop by means of short
circuit isolators. In this case, a failure will be handled in the same way as short
circuit on the loop cable.
8.1.1.5 Multi Central

Using the method mentioned above, the system is designed in such a way that a
single central covers a single Main Fire Zone of the vessel. The solution is the
multiplied and up to 30 centrals are connected in a single system. A global
database of device status is established in each control module that is connected to
the system bus. Consequently information, status and events of loop units can be
available on basically any control panel. This information is also distributed to
external systems by protocols available to the system.
8.1.2 Limitations of SRTP Loop

Some limitations for the SRTP solution are:
• An SRTP loop must be connected to one and the same Backbone Bus.
• The first and last detectors of an SRTP loop must have short circuit isolation.
• Line drop will occur if voltage falls below 27 VDC on an SRTP loop with
maximum load. The voltage on an SRTP loop depends on the number of
detectors and length of the cables.
NOTE!
Careful projecting of the SRTP loop is needed to ensure sufficient
voltage levels.
• The SRTP loop needs to be configured correctly prior to startup.
8.1.3 Final Startup of SRTP Loop

To function properly the SRTP loop must complete a startup without any faults or
warnings.
Prerequisites
• The installation of all loop units and cables in the entire SRTP loop is
completed.
• The fire alarm system is running firmware version 1.7.20 or newer.
(With older firmware the primary Loop M must restart and complete its first
loop scan before the secondary Loop M is connected and restarted.)

Verification
1 Verify that all loop units and the loop Preferably perform the
cables are installed correctly. verification with a SE3000+
test device. In this case both
the primary and the secondary
Loop M shall be disconnected
from the loop.
2 Verify that the physical installation matches
the SRTP loop configuration in the fire
alarm system configuration file.
3 Verify that the correct system configuration
file is downloaded and running in the fire
alarm system.
Startup
1 Reset both the primary and secondary Loop

M*.
2 Restart the primary and secondary Loop M If the Loop Ms are too far
simultaneously. apart to perform this, start the
primary LoopM first. Start the
secondary LoopM as soon as
possible after this, the primary
Loop M must not have
completed its first loop scan
when the secondary Loop M
is started.
* The reset of the Loop M memory is necessary since the loop setup information is
saved there after the very first loop scan. This feature makes future restarts faster.
In a system with firmware older than version 1.8.50 a service engineer can reset the
primary and secondary Loop M by e.g. downloading a new configuration file with
an altered new loop configuration or using the Loop M dongle and a debug
command. It is also possibly to reset the memory by changing the Loop M address
DIP switch settings to zero.
In a system with firmware version 1.8.50 or newer the reset of the primary and
secondary Loop M can also be performed from the Control M 4.3 service menu.

8.2 Alarm Delay, Special function for Industrial

applications
Figure 37. Informational graph that visualize Alarm delay 1 (kvitteringstid) and Alarm delay 2
(undersökningstid).
Alarm delay (Swedish "larmorganisation") is a special function which gives the

personnel a chance to examine whether it is a real alarm or not before the alarm
goes to the fire department. This is a standard feature and is used in
medicine/elderly care, but also occurs in some industries in which unnecessary
alarms occur frequently. Only smoke alarms may be stored and the alarm delay is
built around repeater panels with the ability to acknowledge and reset alarms.
If alarm delay is enabled, alarms from delayable sensors (“larmlagrat don”) shall
be delayed during AlarmDelay1 unless:
1. An alarm from a direct sensor (“icke larmlagrat don”) is generated.

2. The alarm is successfully reset in the main central.
Note that it is not possible to press RESET on the alarm delay panel before
pressing ACKNOWLEDGE.
If alarm delay is enabled and ACKNOWLEDGE is pressed before alarm delay 1

has timed out, the alarm shall be delayed during AlarmDelay2 unless:
1. An alarm from a direct sensor (“icke larmlagrat don”) is generated.

2. The alarm is successfully reset (by pressing RESET).
In the second case, the alarm shall be removed and thus, the alarm devices is not to
be activated.
Alarms from direct sensors (“icke larmlagrat don”) shall directly activate the alarm
devices.
Alarm delay shall be disabled (industry) at power on and it may be enabled/by:

1. A user logged in at EN-54 authorization level 2 or higher.

2. A schedule (time and day of year).
3. A digital input via Cause/Effect.
It is possible to change state in the alarm delay state machine using Cause/Effect
expressions.
It is possible to change the time for alarm delay 1 and alarm delay 2 from the
control panels if logged in at authorization level 3 or higher.
If alarm delay is active it will be indicated at control panels.
8.3 Group Activation of Buzzers

8.3.1 Overview
The purpose of the functionality called “Group Activation of Buzzers” (connected
to detector’s remote indication output) or “Buzzer Broadcasts” is to turn on/off a
group of buzzers at the same time. Instead of sending a message to each detector
saying it should turn on its buzzer, all buzzers in a zone can be turn on with a single
C/E expression. The advantages with controlling them all together compared to
controlling them individually are:
• The buzzers are turn on/off at the same time.

• Not as much C/E needs to be written and it means fewer errors in controls.
• Only a single message per loop on the backbone and a single message out on
the loop are needed to turn on all buzzers in a zone.
Limitation: The Buzzer Broadcasts functionality is limited to CN- and EV-Series

(not EV-PP/XXX) of detectors, since it is only that detector type (NoseX) that
supports broadcasts on the loop line.
8.3.2 Configuration
The configuration of Buzzer Broadcasts is done in the CCP configuration tool.
Each loop is configured as usual; checking used addresses, assigning each detector
a zone, check if the detector is a SCI and so on. But to enable buzzer broadcasts in
a zone, the alternative called “Buzzer Broadcasts” needs to be enabled under the
tab called “Zones” in the column called “Settings”. The maximum number of zones
per loop that can be configured with buzzer broadcasts is eight. The limitation lies
in the CN- and EV-Series (not EV-PP/XXX) of detectors, which only support to be
divided into eight different groups.
After the checkbox for buzzer broadcasts has been checked, everything is set up to
send broadcasts to the loop units. The trigger for turning on/off buzzers is done in
C/E. The Cause/Effect expression that is used to control buzzers is the following:
MESSAGE ZONE x BUZZER ON/OFF
A C/E example to turn on all buzzers in zone 10 when there is an unmuted fire in
the system would look like this:

FIRE IN SYSTEM AND NOT MUTE ALARM => MESSAGE ZONE 10 BUZZER ON/OFF;
8.3.3 Overall functionality

As described in previous section, the buzzer broadcasts are configured zone-wise.
When the configuration is loaded into the system, the controller module knows
which zones that have buzzer broadcasts turned on and in the configuration sent to
the Loop M X modules, it also says which zones have buzzer broadcasts turned on.
When the system is up and running and a C/E expression for buzzer broadcasts is
executed, the controller module checks which Loop M X module that have this
zone configured and sends an activation message of buzzers to all those Loop M X
modules that also have the buzzer broadcasts enabled. In case of an SRTP loop, the
activation message is sent to both the SRTP master and the SRTP slave. Since the
loop line could be broken or the SRTP master could fail, it is important that both of
them are updated with the current status.
8.3.4 Functionality in the Loop M X

Configuration
At startup, just after the Loop M X has received its configuration, it starts assigning
groups to zones. Each zone is assigned (at least) one group, such that each zone is
controllable from C/E. If there are eight zones configured with buzzer broadcasts,
then each zone gets one group. In the other case, when there are less than eight
groups, the spare groups can be assigned to zones with large numbers of detectors.
As long as there are spare groups left, a zone will be assigned an extra group if the
number of detectors divided with the number of groups assigned to that zone is
larger than 65. When all groups are assigned to a zone or each zone has less than
65 detectors in each group, the detectors are assigned group numbers based on their
configured zone. If the zone only has one group, all detectors belonging to that
zone will be assigned that group number. If more groups are assigned to a zone, the
detectors of that zone are evenly divided into the groups.
The group number is written into the detector's EEPROM memory when the Loop
M X is talking to the detector the first time. Since the assignment of group numbers
is done as soon as the Loop M X has received its configuration, everything is setup
when the Loop M X starts polling the loop units. The group number is also
validated if a detector is cold started or later on lost due to a replacement or cable
break to ensure that the detector is listening to the right broadcast messages. Along
with the group number an output mask is also written to the EEPROM. This mask
says what output should be set/reset when a broadcast matching the group number
is received. This output is set to the default output for tone and remote on the
detector based on the detector type.
In SRTP, both the master and the slave runs the code to assign groups to zones and
groups to detectors, but it is only master that writes the group number into the
detector’s EEPROM. Since it is a requirement that a SRTP loop needs one
complete startup before it is considered to be up and running, the master will write
the group number correctly before the slave will take over the line the first time.
But the slave still runs the group assignment to be able to know the mapping
between zones and groups to send broadcasts to the correct group. Since the same
configuration is sent to both the master and the slave, both of them will build up
the same mapping.

In Operation
When the loop (/SRTP) has started up correctly and everything is up and running,
the loop is ready to send buzzer broadcasts to the detectors. When a buzzer
activation expression is executed in C/E, an activation message is sent from the
controller module to the Loop M X. The Loop M X has a representation for each
buzzer broadcast group and when it receives a message that says to activate all
buzzers in a specific zone, all groups that were assigned to that zone during
configuration are flagged as “should be activated”.
In the Loop M X, there is a component called “Current Supervisor”, which has the
responsibility to supervise the current consumption and along with that information
activate/deactivate buzzer broadcast groups that are flagged as “should be
activated” without violating the maximum allowed current consumption on the
line. When a buzzer broadcast group is flagged as should be activated, it is placed
in a list of all of these buzzer groups. The current supervisor continuously loops
over this list and checks whether all of the groups have their buzzers activated. If
all groups have their buzzers activated, the state of all buzzer groups is OK. If the
current supervisor finds a group in the list that does not have its buzzers activated,
it checks whether it is okay to activate the buzzers of that group without violating
the maximum current consumption of the line. The check is based on the
momentarily current consumption plus the consumption of the group. The
consumption of the group is recorded every time a broadcast activation is sent to
the group, and before the group has been activated the first time it has a large
default value. If it is okay to activate the group, a broadcast is sent to the loop that
activates all buzzers in that group. However, if there is a risk of violating the
maximum current consumption by activating the group, the group is skipped for
the moment and the groups are now in an anti-phase situation. In an anti-phase
situation, as many groups as possible will be activated as long as the maximum
current consumption is not violated. The buzzers in those groups will be activated
for 1 second, the buzzers are deactivated and then other groups in the list will have
their buzzers activated. This process is running continuously and when the end of
the list has been reached, groups from the beginning will have their buzzers
activated again. The groups will be in an anti-phase situation as long as all groups
cannot be activated at the same time. If some buzzer group is later on deactivated
from C/E, the anti-phase situation will be exited if all buzzers in all groups can be
activated at the same time with respect to current consumption.
To not get stuck in a state where no buzzer groups are activated, because they are
considered to cause an overcurrent, always one group is activated even if it is a risk
of violating the maximum current consumption. If a group always causes an
overcurrent of the line, the group will be blocked after 10 violations.
In SRTP, the Loop M X that controls the line is responsible for sending broadcasts
for activating buzzer groups. However, if there is cable break or for another reason
both the master and the slave are controlling part of the line, both will be sending
broadcasts to their part. Since all activations/deactivations from C/E is sent to both
the master and the slave, both of them are aware of which groups that should be
activated. But, in an anti-phase situation, the master and the slave are not synced in
such a way that group x will be activated at the same time from both the master and
the slave side. It could also be the case such that from the master’s side all groups
can be activated at the same time, but from the slave side it could be in an
anti-phase situation and vice versa.

NOTE!
The maximum current mentioned above is set to 250 mA. However, a buzzer group
is not activated if the group’s current consumption plus momentarily current
consumption of the line is above 190 mA. All current consumptions recorded for
the buzzer broadcast groups are also given a margin of 10 %.
In order to further decrease current consumption on the loop the number of

detectors with steady light LEDs are restricted to three.
If more when three detectors on the loop detects fire, only the first three detectors
will indicate with steady light LEDs and the rest indicate with flashing LEDs.
The Loop M X module remembers in which order the detectors detected fire, so if
a fire alarm in a detector are reset the next detector that detected fire will switch
from flashing light to steady light.
Faulty Situations
When the Loop M X is initializing a detector, it compares the group value and the
output mask saved in the detector with the value and the mask it wants the detector
to have. If it is not matching the Loop M X tries to write the new values to the
detector’s EEPROM, but at most three times. If the Loop M X has tried to write the
values three times without the EEPROM value has changed, a device write fault
will be generated and the Loop M X stops to write those values to that detector.
When the fault is reset, the Loop M X tries again to write the value and the mask to
the detector.
When the current consumption of the loop line is above 250 mA, the Loop M X
immediately tries to turn off buzzer broadcast groups to avoid losing detectors due
to this overcurrent situation. If the overcurrent situation is not solved within 30
seconds or three or more overcurrent situations have occurred during that time, an
overcurrent fault is generated. If the current consumption is above 300 mA and the
over consumption was caused by an activation of a buzzer group, a counter is
incremented to keep track of number of overcurrent situation this buzzer group has
caused. When a buzzer broadcast group has caused 10 overcurrent situations above
300 mA, that group will be blocked and an overcurrent fault is generated. As long
as the fault is not reset this buzzer group will be blocked.
8.3.5 Summary
• The Broadcast Buzzers functionality is limited to CN- and EV-Series (not
EV-PP/XXX) of detectors, since it is the only detector type that supports
broadcasts on the loop line.
• Max 8 Groups per loop.
• Max 65 detectors per group.
• If not all groups can be activated at the same time without violating maximum
current consumption of 190 mA, as many groups as possible is turned on for 1
second, then turned off and other groups are turned on, and so on.
• An overload fault is generated if the current consumption is above 250 mA for
30 seconds or during the same time the maximum current consumption of the
line is violate three times or more.

• If a broadcast group is causing an overload above 300 mA more than 10 times,

the group is blocked from being activated again and an overload fault is
generated. The block for the group is removed when the fault is reset.
• The group number is registered in a detectors internal EEPROM on the Loop´s
first startup, if this fails fault code 241 ”DEVICE WRITE FAULT” is generated.
• The number of detectors with steady light LEDs are restricted to three.
8.4 Definitions of Terms

Definitions of terms for CCP Platform.
Alarm Condition The state of the system when a fire or gas alarm is detected.
Alarm Delay When activated the activation of Alarm Devices will be delayed
for a preset time (normally 2 minutes).
Alarm Device Device that is activated in case of fire or gas, i.e. audible and
optical alarms like bells, sirens and flashlights.
Alarm Transfer A supervised output for signalling that a fire has occurred. The
Output Alarm Transfer Output is usually used in onshore systems for
alerting the Fire Brigade.
Alien communication Communication that does not relate to the system in any way, i.e.
Systems device is neither transmitter nor intended receiver of the
communication.
Backbone Bus The main bus outside a Central cabinet used for communication
External (BBE) between Modules and stretched central parts. It consists of two
redundant RS485 channels, two 24 VDC power lines, the Basic
Backup (BBU) signal and Synchronisation Signal (SYNC).
Backbone Bus The main bus inside a Central cabinet used for communication
Internal (BBI) between Modules. It consists of two redundant RS485 channels,
two 24 VDC power lines, the Basic Backup (BBU) signal and
Synchronisation Signal (SYNC).
Backbone Segment A Backbone Bus may be split in several Segments. Power feeding
can be separate for each segment by using one Charger M per
segment. Communication can be isolated between segments by
using Isolator Modules.
Basic Backup Signal A signal in the Backbone Bus that is used for transmitting the
(BBS) Central’s alarm status. The signal is only used when a module in
Managed mode loses communication with its Controller Module.
Cause/Effect The Cause/Effect program defines how the inputs and outputs of
the system should react.
CCP Platform An umbrella name for all the Modules and Devices that can be
connected together, e.g. ‘the Control M 4.3 module is a member of
the CCP Platform’.
Central A central is a complete system that can operate autonomously;
monitor its detectors and inputs, activate its outputs and display its
faults and alarms. If connected to other centrals, it exchanges
information with the other centrals via the System Bus, thus
allowing all centrals to act as one System. Each central can only
have one Backbone Bus.
Central Cabinet Enclosure to contain a complete or part of a central.

CIS Control & Indication System.

Compact Central Central Cabinet including basic functionality of Detection System
such as: Control Panel, Power supply, Battery backup, Basic I/Os
and at least one analogue addressable loop. The Cabinet supplies
limited expansion possibilities.
Control Module The Control M 4.3, the Control M Gas, the Control M 2.2 and the
Control M X can all act as Controller Modules, i.e. be in
Controller Mode.
Control Panel The Control M 4.3, the Control M Gas and Control M 2.2 can act
as a Control Panel, i.e. they have an HMI and the rights to
manipulate and supervise the System.
Controller Mode Control Modules can run in Controller Mode, i.e. being Master or
Hot Standby Master (slave) within a central. Control Modules can
also be in managed mode, i.e. being a module that is managed by
the master. All other modules are always running in managed
mode.
Controller Module A control module that is in Controller mode (master or hot
standby) in a Central or System.
DCS Distributed Central System (see also stretched central).
Detector A device capable of detecting Fire or Gas Alarms.
Disablement Disablement of devices such as a Zones or Detectors. Alarms from
disabled devices will be inhibited.
ESD system Emergency Shut Down System, embedded system taking care of
safety procedures in case of emergency, e.g. Shut down of fire
doors, ventilation etc.
Extension Bus An additional (RS485) bus used inside a central for intra-central
communication. The Extension Bus is typically used for
connecting Repeater Modules (that does not require redundant
communication and power) and should not be confused with the
Backbone Bus.
External Communication to external entities is called external
Communication communication, using e.g. a MODBUS, NMEA Protocol.
External Control Outputs used to control external equipment.
Fault Condition The state of the system when a fault is detected.
FDS Fire Detection System.
GA General alarm, common activation of alarm devices and activation
of the PA system.
GA-auto Automatically generated signal according to a pre-defined pattern
(e.g. 7 short 1 long signal) for alarm devices or the PA system.
GA-Morse Signal pattern generated manually via the GA button.
GDS Gas Detection System.
Hot Standby Mode Controller Modules in Hot Standby Mode can take over the
responsibilities of the Controller Module managing a Central.
I/O 70 An Input/Output type providing a different function depending on
the configuration of the system. The programmable functions are:-
General Input- Fault Input- Conventional Fire Alarm Zone -
Output (24VDC/70mA)

I/O 700 An Input/Output type providing a different function depending on

the configuration of the system. The programmable functions are:-
General Input- Fault Input- Output (24VDC/700mA)
I/O Module A Module with inputs and/or outputs. I/O Modules always run in
Managed Mode, i.e. they must be managed by a Controller
Module.
I/O Pin or I/O Signal An I/O Pin or an I/O Signal is a logical signal, compare to
Terminal.
Inter-central Communication between centrals is called inter-central
communication communication.
Interface Channel A Communication Channel used to interface the systems with
external devices. Interface Channels can be configured to
communicate on different protocols.
Intra-central Communication within a central is called intra-central
communication communication. This communication is between modules.
Loop A common name for the cable, Loop Devices and other equipment
connected to a Loop Module.
Loop Device Fire Detectors, Gas Detectors, Manual Call Points and other
devices that can be connected to the Loop.
Loop Module A Module supplying power and is in charge of communication to
the loop devices.
Managed Mode The opposite of Controller Mode. All modules that are managed
by a Controller Module are in Managed Mode.
MCCS A Multi Centrals system or Single Central System connected to a
Server System.
MCS Multi Central System. A System consisting of more than one
Central.
MFZ Main Fire Zone.
Mode of operation Modules in the System can take on different roles. Connected to
the Backbone Bus they can be in:
• Central Controller Mode (Master or Hot Standby)
• Central Managed Mode
Modules connected to the System Bus can be in:
• System Controller Mode (Master or Hot Standby)
• System Managed Mode
Module A module that is a part of the Platform i.e. can be used to build
Centrals. Modules within the platform generally supply a
Backbone Bus interface. Controller Modules also have a System
Bus Interface.
Module Address Module Addresses are set via DIP switches on the Modules.
Mute Acknowledge and silence the local buzzer and in some cases the
alarm devices.
PA Public Addressing.
PCB Printed Circuit Board.
PLC Programmable Logic Control.
Power Output Output providing power supply, normally used to power external
devices.

Pre-Alarm Condition A condition preceding the Alarm Condition to give early warning
for potentially dangerous situations.
Programmable Output which signal behaviour is configurable via the
Output Configuration Program.
PSU Power Supply Unit.
Redundancy Refers to the quality or state of being redundant, i.e. exceeding
what is necessary or normal. In the System the term is used to
describe back-up functionality like in Hot Standby Controller
Modules.
Relay Electrically operated switch output, normally providing C/NO/NC
contacts for connection of signal receiver.
Repeater Panel The main attribute for Repeater Panels is that they can show
information but not affect the Central (or System) they belong to.
The Repeater M 4.3 is a Repeater Panel.
Safe State Modules enter 'safe state' when they detect system faults. Modules
in Safe State put their I/O in a predefined state and stop all
communication in order to avoid disturbing system integrity.
SCS Single Central System.
SD Secure Digital, a standardized flash memory card that can be
easily replaced.
Slave Mode (Hot Control Units can run in Slave Mode. Control Units in Slave Mode
Standby Mode) can take over the responsibilities of the Control Unit managing a
Central. Slave Mode has been renamed to Hot Standby Mode and
shall no longer be used.
SMig system Salwico Safety Management interactive graphics, a PC-based
software package providing graphical presentation and control of
the System.
SMS system Safety Management System, a PC-Based software package
providing Graphical presentation and control of the System.
Stretched central A central that is physically distributed to two or more physical
(DCS) locations. One location may or may not supply power to another
location (segmented) and two locations may or may not have
isolated communication lines.
Synchronization A signal in the Backbone Bus that is used for transmitting
Signal synchronization signal used by system Modules to synchronize
their behaviour.
System A System consists of one or more Centrals.
System Bus The communication bus used for connecting multi-central
systems. The System Bus is used for inter-central communication
but can also be used for external communication. If inter-central
communication redundancy is required, the system bus will consist
of a primary and a secondary System Bus.
Terminal A Terminal is a physical point of connection, compare I/O pin.
Test Condition Detectors put in the Test Condition (or Test Mode) do not activate
outputs when in Alarm Condition but the alarms are displayed on
the Control Panels to prove that the tested Detectors are
operational.
USB Universal Serial Bus, a communications bus that may be used to
connect flash memories, keyboards, mice or other devices.

Warning Condition The state of the system when a warning is detected. Warnings are
not as serious as faults and only of informative nature, e.g. that a
Gas Detector is in need of calibration.
Zone A group of detectors located in a geographical area.


Index
Index
A
Additional Power Supply ...................................... 18 H
Address programming tool .................................... 59 Hot standby ............................................................ 5
Addressable loop device ........................................ 59 Hot Standby ........................................................... 9
Alarm delay............................................................ 81 Human/Machine Interface (HMI) .......................... 2
Alarm Organisation................................................ 42
I
B I/O Module............................................................. 7
Backbone Bus ........................................................ 9 Input interfaces....................................................... 21
Basic Backup Signal .............................................. 13 Inter-Central communication ................................. 35
BBE........................................................................ 9 Internally polarized ................................................ 30
BBI......................................................................... 9 Isolated mode ......................................................... 7
BBI Power supply .................................................. 14
BBI RS-485 Communication................................. 14
BBS ........................................................................ 9
L
BBS ........................................................................ 13 Loop devices .......................................................... 59
Built-in protection.................................................. 11
Bus Isolator M........................................................ 46 M
Magnets.................................................................. 19
C Managed mode....................................................... 6
Cable Break on the Loop Cable ............................. 79 Managed mode....................................................... 37
Cause/Effect ........................................................... 6 Master/slave ........................................................... 5
CCP system............................................................ 1 Modbus .................................................................. 5
Channel selector..................................................... 16 MODBUS .............................................................. 17
Common fault states .............................................. 78 MODBUS ............................................................. 17
Common ground .................................................... 15
Configuration file................................................... 61 N
Control M X .......................................................... 40 NMEA.................................................................... 5
Controller in Primary master mode........................ 5 NMEA.................................................................... 17
Controller in Secondary master mode.................... 5
Controller mode ..................................................... 37
Conventional loop device ...................................... 59
O
CSP/CSTP.............................................................. 12 Output interfaces ................................................... 21

D P
Different grounding ............................................... 15 Predefined Input Groups ........................................ 22
DIN rail .................................................................. 19 Predefined Output Groups ..................................... 22
Disablement ........................................................... 3 Predefined patterns................................................. 23
Double-fed Loops .................................................. 78 Primary Master Controller ..................................... 9
Printer..................................................................... 6

Proximity switch .................................................... 29
E PSU M AC/DC 5A ................................................ 48
Earth Fault on the Loop Cable ............................... 78
ESPA 4.4.4 ............................................................. 17
Ethernet .................................................................. 36
R
Redundancy communication.................................. 35

Redundancy, power................................................ 17
F Reflection............................................................... 15
Firmware ................................................................ 4 Repeater function ................................................... 15
FLASH Memory .................................................... 4 Resistor .................................................................. 15
Flashlights .............................................................. 19 Resistor 30 kΩ ....................................................... 31
RS-232 ................................................................... 17
G RS-422 ................................................................... 17
Galvanic isolation .................................................. 15 RS-485 ................................................................... 15
GA-Morse .............................................................. 9

Index
RS-485 ................................................................... 17
RS-485 Communication, BBI ............................... 14

S
Salwico Fire Detection System.............................. 1
Secondary Master Controller ................................. 9
Short circuit on the Loop Cable ............................. 78
Sirens...................................................................... 19
Slave, see Secondary Master Controller ................ 9
SMIG ..................................................................... 17
SMS ....................................................................... 17
Software release ..................................................... 1
Star networks ......................................................... 15
Stretched Central.................................................... 9
Surge Prot M .......................................................... 45

T
TCP/IP protocol ..................................................... 36
Technical address ................................................... 59
Termination ............................................................ 15
Three-wire connection ........................................... 15
Twisted pair wires .................................................. 15
Two-wire connection ............................................. 15

U
USB host ................................................................ 38

V
Virtual module ....................................................... 6

X
X-Fire..................................................................... 12


Consilium Säkerhet - vår erfarenhet, din säkerhet!

Consilium Säkerhet är marknadsbolag inom Som certiferad anläggarfirma kan vi garantera att
Consiliumkoncernen. Tillsammans marknadsför och samtliga leveranser och installationer utförs enligt
säljer vi brand- och gaslarm utvecklade av Consilium. fastställda myndighets-, kvalitets- och säkerhetsnormer.
Consilium utvecklar och marknadsför produkter och Så oavsett om du behöver ett enklare brandskydd eller
system för säkerhet, miljö och navigation. Consilium är ett stort integrerat brand- och gaslarmsystem, är vårt mål
världsledande inom brandlarm på den marina alltid detsamma, att förse dig som kund med en lösning
marknaden. efter ditt behov, uppbackad av vår engagerade och
Consilium Säkerhet, med kontor i Malmö, Göteborg välutbildade personal!
och Stockholm, kan erbjuda allt från projektering och
försäljning till installation och service.

Kundanpassad service
Vi på Consilium Säkerhet kan erbjuda dig som kund
flertalet olika lösningar för service och avtal med allt
från löpande service, inplanerad underhållsservice eller
fullservice samt givetvis akut service. Utöver detta kan
vi även erbjuda månads- och kvartalsprov för
Consilium Säkerhet Syd AB
automatiska brandlarmsystem enligt SBF 110:6. 040-36 50 60
Consilium Säkerhet Väst AB
031-710 79 00
Consilium Säkerhet Öst AB
08-563 052 00

FG5000 - CCP System Description Application Examples

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

FG5000 - CCP System Description Application Examples

Uploaded by

Copyright:

Available Formats

Fire Detection System

© Copyright 2015, Consilium Säkerhet

1.3 CCP System Modules ........................................................................ 4

2 Single Central System (SCS) ............................................................ 9

2.3 Power supply ..................................................................................... 17

2.6 I/O 70 type contacts........................................................................... 25

2.7 I/O 700 type contacts......................................................................... 30

3 Multi Central System (MCS) ............................................................ 35

3.1 System Bus ........................................................................................ 35

4 CCP Modules Descriptions............................................................... 37

4.2 Connection interface modules .......................................................... 43

4.3 Communication modules .................................................................. 48

4.4 Power supply modules....................................................................... 48

4.5 Power switch modules....................................................................... 52

4.6 Input/Output modules ....................................................................... 54

4.7 Loop modules .................................................................................... 58

5 Loop devices ...................................................................................... 59

7 Application Examples ....................................................................... 65

8.1 Consilium Solution to Fulfil "Safe Return To Port"

8.2 Alarm Delay, Special function for Industrial applications ............. 81

8.4 Definitions of Terms.......................................................................... 86

5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C 1

1.2 System software

1.2.1 Presentation layer

1.2.2 Control/Process layer

2 5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C

1.2.3 Module/Field layer

Figure 2. Module/Field level

1.2.4 Access levels

5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C 3

1.3 CCP System Modules

There are three main groups of CCP modules:

Figure 3. Some examples of CCP modules.

1.3.2 Control Modules, information and control/process

4 5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C

Figure 4. Control Modules

1.3.2.1 A Controller in Primary or Secondary master mode

A master controller is able to and/or responsible for the following:

• Store and disseminate the definition file to all controllers.

5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C 5

• Communication with presentation and monitoring systems.

1.3.2.2 A Controller in Managed mode

• Store the definition file.

1.3.3 Managed modules, Field layer

The boot is based on an implementation model as depicted below.

6 5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C

Figure 5. I/O Module Boot.

5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C 7

8 5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C

2 Single Central System (SCS)

The Backbone Bus is designed for usage in two different environments:

• Backbone Bus Internal (BBI)

An important difference of Backbone Bus Internal (BBI) and Backbone Bus

It is possible to stretch a central. A stretched Central is physically distributed to

In a Single Central System there can be up to 125 addressable modules on one

5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C 9

Figure 6. Example of Single Central System.

10 5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C

Figure 7. Example of Single Central System.

2.2 Backbone Bus

5100501_FG5000_CCP System description & Application examples_I1_EN_2015_C 11

The protocol used for communication in the CCP system is developed by