5100334-02 - Salwico Cargo Conventional - Service & Maintenance Manual - M - EN - 2018 - T

Salwico Cargo
Conventional
Fire Detection System
Service & Maintenance Manual
Consilium Marine & Safety AB
Fire & Gas Marine Division
Phone: +46 31 710 77 00
Fax: +46 31 710 78 00
E-mail: Service: service@consilium.se
Spares: spares@consilium.se

Consilium Marine & Safety AB
Navigation Division
Phone: +46 8 563 05 100
Fax: +46 8 563 05 199
E-mail: Service, APT: service-navigation@consilium.se
Spares: spares-navigation@consilium.se

The contents of this document are subject to revision without notice
due to continued progress in methodology, design and manufacturing.
Consilium assumes no legal responsibility for any error or damage
resulting from the usage of this document.

March 2018
Document no. 5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T
Part no. 5100334-02
© Copyright 2018, Consilium Marine & Safety AB

Table of contents
1 Introduction....................................................................................... 1
1.1 About this Manual ............................................................................ 1
1.2 Symbols used in the manual ............................................................. 1
1.3 Approvals........................................................................................... 2
2 General Description .......................................................................... 3

2.1 System Description............................................................................ 3
2.2 System Block Diagram...................................................................... 3
2.3 System data (EN 54).......................................................................... 4
2.4 Electrical Installation, Central Equipment...................................... 4
2.5 Example of a Detector Zone ............................................................ 5
2.5.1 Connection to Zone Module, type I/O M 70................................... 5
3 Testing................................................................................................ 7
3.1 Test Mode Overview .......................................................................... 7
3.2 Testing Fire-Detecting Zones ........................................................... 7
3.2.1 Testing a Fire-detecting Zone ......................................................... 7
3.2.2 Simulate a fire alarm in the system................................................. 8
3.2.3 Recommended Test Equipment ...................................................... 8
3.2.4 Heat Detectors................................................................................. 8
3.2.5 Smoke Detectors ............................................................................. 9
3.2.6 Flame Detectors .............................................................................. 9
3.3 Reset Test Mode................................................................................. 10

3.4 Test Fault Conditions........................................................................ 10
3.4.1 About Fault Conditions................................................................... 10
3.4.2 Removed Detector Fault ................................................................. 10
3.4.3 Battery Fault.................................................................................... 10
3.4.4 Earth Fault....................................................................................... 11
3.4.5 Loop Cable Break ........................................................................... 11
3.4.6 Power Supply .................................................................................. 11
3.4.7 Test the Loop Cable ........................................................................ 11
3.5 Test the Control Panel Display ......................................................... 11

3.6 Troubleshooting ................................................................................ 12
3.6.1 Earth Fault....................................................................................... 12
3.6.2 Muting Faults .................................................................................. 13
3.6.3 Reset Faults..................................................................................... 13
3.6.4 Installation Mode ............................................................................ 14
3.6.5 Save the System Log to a USB Memory Stick ............................... 14
3.6.6 How to report a fault ....................................................................... 14
4 Cleaning of Fire Detectors ............................................................... 17

4.1 Prior to Cleaning............................................................................... 17
Table of contents
4.2 Smoke Detector ................................................................................. 17

4.3 Heat Detector..................................................................................... 17
4.4 Flame Detector.................................................................................. 17
5 Replacing Batteries ........................................................................... 19
6 System Configuration ....................................................................... 21

6.1 Configuration Program .................................................................... 21
6.2 Downloading a configuration file to a USB Memory Stick ............ 21
6.3 Uploading a configuration file from the USB Memory Stick ......... 21
6.4 Update protocols in a Control M X with USB port.......................... 23
7 Using the Service Menu.................................................................... 25

7.1 Service menu - main screen.............................................................. 25
7.2 System details, submenu 1 ................................................................ 25
7.3 Centrals, submenu 2 ......................................................................... 26
7.4 Modules, submenu 3 ......................................................................... 27
7.5 Zones, submenu 4 ............................................................................. 28
7.6 Loops, submenu 5 ............................................................................. 29
7.7 Configuration, submenu 6................................................................ 32
7.8 Firmware, submenu 7 ....................................................................... 33
7.9 System Log, submenu 8 .................................................................... 33
7.10 I/O Lists, submenu 9 ......................................................................... 33
8 System Upgrade................................................................................. 35
8.1 Upgrade BIOS ................................................................................... 35
8.1.1 Upgrade BIOS for a CCP System from USB Stick ........................ 35
8.1.2 Upgrade BIOS in a Control Module via Ethernet (Control M X
without USB port)........................................................................... 36
8.2 Upgrade Firmware............................................................................ 37

8.2.1 Upgrade Firmware for a CCP System from USB Stick.................. 37
8.2.2 Upgrade Firmware for a CCP System from MicroSD Card ........... 40
8.2.3 Upgrade Firmware in a Control Module via Ethernet (Control M
X without USB port)....................................................................... 42
8.2.4 Troubleshooting for Firmware Update Tool ................................... 44
8.3 Upgrading Large Systems................................................................. 45

8.3.1 Upgrade strategy ............................................................................. 45
8.3.2 How to upgrade each control module ............................................. 45
8.3.3 Upgrade modules in the following order ........................................ 46
Table of contents
9 Appendix - Central Unit Terminal & Cabling Layout..................... 49

9.1 Central Unit Terminal & Cabling Layout ........................................ 49
10 Appendix - Termination .................................................................... 53

10.1 RS-485 Termination .......................................................................... 53
10.1.1 General Recommendations for Installation of RS-485................... 53
10.1.2 Application Examples for Installation of RS-485........................... 53
10.2 Additional Information for BBU Termination................................. 56

10.2.1 Basic Backup Signal, BBU ............................................................. 56
10.2.2 Application Example for Installation of BBU ................................ 57
10.2.3 Testing the BBU Installation........................................................... 60
11 Appendix - System Software Updater............................................... 61

11.1 System Software Updater .................................................................. 61
11.1.1 Setup ............................................................................................... 61
11.1.2 Startup ............................................................................................. 61
11.1.3 Prepare Update................................................................................ 62
11.1.4 Update ............................................................................................. 65
11.1.5 Menu ............................................................................................... 68
12 Appendix - Fault Code List............................................................... 69

12.1 Fault Code List.................................................................................. 69
13 Appendix - Definitions and Abbreviations....................................... 85

13.1 Definitions and Abbreviations .......................................................... 86
Index ................................................................................................. 92
Table of contents
Service & Maintenance Manual 1 Introduction
1 Introduction
1.1 About this Manual

This manual is for personnel who maintain and service the fire detection system.
NOTE!
This user guide has been revised based on system version 1.10.10 but is valid for
Control panel software versions beginning with version 1.0.0.
The General Description chapter gives an overview of the fire detection system.
The Testing chapter describes testing procedures for zones, detectors and the
control panel display. Cleaning instructions can be found in the Cleaning of Fire
Detectors chapter.
The Service menu in the control panel can be used for configuration, maintenance
and small updates as described in the Using the Service Menu chapter.
Figure 1. Salwico Cargo Fire Detection System, an example.
1.2 Symbols used in the manual

DANGER!
Risk of serious or fatal injury to the user, and/or severe damage to the product, if
the instructions are not followed.
5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T 1

1 Introduction Service & Maintenance Manual
WARNING!
Risk of personal injury and/or damage to the product if the instructions are not
followed.
CAUTION!
Risk of minor or moderate personal injury. Risk of equipment damage, loss of data,
extra work, or unexpected results, if the instructions are not followed.
NOTE!
Note symbols alert you to important facts and conditions.
Hint!
Hint symbols direct you to specific instructions, such as where to find additional
information and tell you how to perform a certain operation in an easier way.
1.3 Approvals
2 5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T

Service & Maintenance Manual 2 General Description
2 General Description
2.1 System Description

This Fire detection system is a state-of-the-art fire-detection system designed to
meet marine and industrial requirements. Special care is given to ergonomics and
user-friendliness with its logical and intuitive operator panel.
2.2 System Block Diagram

The following figure shows a typical system and its connected components, see
Definitions and Abbreviations, page 86 in the Appendix for explanation of terms
and abbreviations.
Figure 2. An example of a system block diagram.

2 General Description Service & Maintenance Manual
2.3 System data (EN 54)

Table 1. System data for the fire detection system.
System Data Specifications
Supply voltage 84–264 VAC /
90-350 VDC
Power consumption Depending on system
configuration
Internal system voltage 19–30 VDC
Central panel ingress protection Depending on cabinet
Number of loop units to indicate fire with steady light LEDs Max 4
The first 4, the rest with
blinking LEDs
Number of inputs/outputs per module, I/O M 700 8
Enclosed spaces in a detector zone with conventional Max 50
non-addressable loop units
Number of modules in one central (max 64 Loop M X) Max 125
RS485, 19200 Baud, Odd
Communication parameters for the external system channel
parity, 8 data bits
Number of individually defined effects (output expressions) Max 1000
per single central
NOTE!
System boot-time is kept to a minimum during normal operation, but it can be
extra-long after a new installation, commissioning or major maintenance work
(depending on the configuration of the data definition file).
NOTE!
A warning will be displayed on the menu screen as long as the system is not
running Cause/Effect, which is the two first minutes after the system has been
powered up
Hint!
For detailed requirements regarding system modules and loop units, refer to the
data sheets.
2.4 Electrical Installation, Central Equipment

Terminal layout
Since most systems are designed specifically for each customer, no standard for
connecting the different modules within the system exists.
Refer to Central Unit Terminal & Cabling Layout, page 49 for more information.
For other electrical installations, such as Printer and Basic Backup Signal (BBU),
refer to the specific project drawings.

Service & Maintenance Manual 2 General Description
Control Panel
If the Control Panel is placed outside of the central unit, connection is made via the
external Backbone Bus channel (BBE). Each cable should be routed seperately for
maximum safety.
2.5 Example of a Detector Zone

2.5.1 Connection to Zone Module, type I/O M 70
Figure 3. Example of a detector zone with conventional non-addressable loop units.
A zone should in any case include no more than 50 enclosed spaces.

2 General Description Service & Maintenance Manual

Service & Maintenance Manual 3 Testing
3 Testing
3.1 Test Mode Overview

The system has a special test mode function which makes the testing easier.
When a zone is in test mode:
• External alarm devices and controls are by default not activated in case of a fire.
Hint!
This functionality can be turned off if controls are to be tested while the
tested zone is in test mode.
(Menu » 3 Disablements » 1 New Disablement » 3 External Controls)
NOTE!
Fire alarm from zones not in test mode will be handled normally by the fire
detection system.
The zone in test mode will automatically return to normal operation after two
hours.
3.2 Testing Fire-Detecting Zones

3.2.1 Testing a Fire-detecting Zone
The functions of the FDS shall be tested at the interval stated in each application
specific documentation.
CAUTION!
During system start-up the smoke detectors perform a 15 minutes calibration
according to the level of particles in the air. No tests should be done during this
period.
1 Put the zone into test mode under: Menu » Access level 2B is required.
3 Disablements » 1 New disablement » 5
Test Mode .
2 Select a zone and confirm by pressing the The Disablements, Test, and
key. Zone/Unit indicators light to
confirm that they are in test
mode.
Each detector, manual call point and input in this fire zone can be tested during the
next two hours. Refer to Test Mode Overview, page 7 for further information
about a zone in test mode.
All alarms are listed under: Menu » 7 History » 1 Fire History List .
To return the tested zone to its normal condition, refer to Reset Test Mode, page
10.

3 Testing Service & Maintenance Manual
CAUTION!
If the system previously had been put into regular fire detection service, a zone in
test mode should be manually monitored, e.g. by a fire watch in order to maintain a
tolerable risk level.
NOTE!
Use appropriate test equipment.
See section Recommended Test Equipment, page 8.
3.2.2 Simulate a fire alarm in the system

The “Set in fire” function can only be activated for addressable loop units.
1 Add a disablement for a selected loop unit

in Menu » 3 Disablement » 1 New
disablement
2 Choose the relevant loop in Menu » 6
Service Menu » 5 Loops and find that
particular loop unit.
3 Press OK for details.
4 Push 2 to activate the “Set In Fire” Despite the existing
function. disablement the system will
sound the alarm.
3.2.3 Recommended Test Equipment

Table 2. List of recommended test equipment for Fire detection systems
Product Description
Testifire Multi-stimulus detector tester for smoke and
heat detectors
Salwico Solo 330 Smoke detector tester
Smoke Sabre Aerosol smoke detector tester
Salwico SOLO 461 Heat detector tester
Salwico IR Test lamp IR flame detector tester
Salwico UV Test lamp UV flame detector test lamp
W8066 UV test lamp
Test key for manual call point A test key is supplied with each call point
For detailed information, please refer to the data sheets for the products.
3.2.4 Heat Detectors

NOTE!
Use appropriate test equipment, available at your authorised dealer. This is
especially important when testing a heat detector in an hazardous (Ex-classified)
location/area.
For test equipment see section Recommended Test Equipment, page 8.

CAUTION!
For testing a heat detector in a hazardous (Ex-classified) location/area, please
contact an authorized service office for consultation.
1 To test the heat detector, apply heat to the sensing element until the
indicator lights.
CAUTION!
Other test equipment, for example, a cigarette lighter or a heating gun should not
be used. This could damage the detector.
3.2.5 Smoke Detectors

Use appropriate test equipment, available at your authorised dealer. See section
Recommended Test Equipment, page 8.
1 Spray test gas on the detector for 0.5

seconds.
2 Wait 10 seconds. Check if the alarm has been
activated (the indicators are
lit), if not continue to the next
step.
3 If the alarm indicator is not lit, spray the
detector for 1 second.
4 Repeat steps 2-3 until the detector’s alarm
indicator lights red.
CAUTION!
If other test methods or test equipment are used, make sure not to damage the
detector.
3.2.6 Flame Detectors

NOTE!
Use appropriate test equipment, available at your authorised dealer. This is
especially important when testing a detector in an Ex-classified location/area.
For test equipment see section Recommended Test Equipment, page 8.
For instructions how to use the test equipment, refer to the data sheet.
DANGER!
Open flame (cigarette lighter) should not be used for testing in explosive areas.

3.3 Reset Test Mode

NOTE!
After testing is completed, return the tested zone to its normal condition.
Before exiting test mode, make sure there are no detectors or manual call points in
alarm condition.
The tested zone will automatically return to normal operation after two hours if no
manual reset have been performed.
To reset test mode:
1 The zones in test mode are listed in the Disablement List, found under:
Menu » 3 Disablements » 2 List disablements.
2 Choose the zone in the disablement list and then press .
3.4 Test Fault Conditions

3.4.1 About Fault Conditions
The Fire detection central continuously monitors the system components and
reports any fault condition on the control panel with both visual and audible
indicators.
It is possible to test fault alarm indications by following the procedures below:
NOTE!
The fault condition may be reset only after the cause of the fault has been
remedied.
Hint!
Please follow the recommendations for remedy in the Fault code list.
3.4.2 Removed Detector Fault

1 Remove a detector.
2 Verify that the fault is indicated on the control panel (this may take up to
100 seconds).
3 Reinsert the detector.
4 Reset the fault condition on the control panel.
3.4.3 Battery Fault

1 Remove the battery cables.
100 seconds).
3 Reattach the battery cables.

3.4.4 Earth Fault

1 Connect one of the loop cables to earth via a 2.7 kOhm resistor.
100 seconds).
3 Remove the earth connection.
3.4.5 Loop Cable Break

1 Open up the loop cable.
100 seconds).
3 If the detector loop is double fed: verify that each of the two branches can
detect fire alarms by testing a detector on each branch.
4 Close the loop cable.
3.4.6 Power Supply

Test the back up power supply (emergency power VAC or batteries).
1 Remove the main power supply.

2 Verify that the fault or warning is indicated on the control panel (this may
take up to 1 minute). The system is now running on emergency or battery
power.
3 Reconnect the disconnected power supply.
4 Reset the fault condition(s) on the control panel. A warning does not need
to be reset, it disappears automatically.
3.4.7 Test the Loop Cable

3.4.7.1 Prerequisites for Testing the Loop Cable
The loop cable should be tested for proper function after all the loop units are
connected and before the cable is connected to the loop module in the central unit.
3.4.7.2 Test for Earth Failure

CAUTION!
When loop units are connected, it is not allowed to use an insulation tester with a
voltage exceeding 30 V.
Measure between the + and - pole and earth to detect an earth fault.
3.5 Test the Control Panel Display

With the function Test display it is possible to verify the functionality of:

• The display
• All indications on the control panel
NOTE!
The user has to verify that the display and all indications are working properly.
This function will not generate a fault alarm in case something is faulty.
1 To test the control panel display, use: Menu » 5 Settings » 4 Test display.
2 Verify that the display momentarily shows a test image.
3 Verify that all system indicators and operational keys momentarily lights
up.
3.6 Troubleshooting
3.6.1 Earth Fault
CAUTION!
An earth fault on a loop cable has to be located and corrected as soon as possible in
order to secure the functionality of the complete fire detection system.
The control panel displays which loop or central has the earth fault.
1 Examine the faulty loop to locate the earth

fault.
Measure the resistance

CAUTION!
When loop units are connected, it is not allowed to use an insulation tester with a
voltage exceeding 30 V.
Figure 4. Test for earth failure

1 Measure between the + and - pole and earth The measured value should be
to detect an earth fault. more than 50 kOhm for a
• Connect the ohmmeter between the cable with a maximum length
+ pole and earth. of 3 km. Values below 8
kOhm (±2 kOhm) will be
• Measure and repeat the procedure for
indicated as earth fault.
the - pole.
If the earth fault still remains after this step, examine the cables to all other devices
connected to the Fire detection system.
3.6.2 Muting Faults

1 Simultaneously mute all the faults by
pressing the Mute key.
2 The fault alarm light stops flashing and The fault is put in a fault list
changes to a steady yellow light. under Menu » 1 Fault Alarms
» 1 Fault List.
3.6.3 Reset Faults

NOTE!
The cause of the problem must be corrected before a fault can be reset.
The faults are reset from the Fault list under Menu » 1 Fault Alarms » 1 Fault List.
• Select the fault and confirm by pressing the reset key.
The fault is reset
1 The fault is reset and it disappears from the fault list.
The fault is not reset
1 The fault is not reset and the reason for this

is displayed.
2 Check and correct the problem. See the Fault code list in the
manual for more information.
3 Attempt to reset the fault by pressing the
reset key.

3.6.4 Installation Mode

In order to avoid unnecessary faults like 'present not configured', 'configured not
present' and 'no answer' during installation and commissioning, zones and loops
can be set to 'Installation Mode'.
1 For zones use Menu » 6 Service Menu » 4 Installation Mode can be

Zones. activated for loops and zones
For loops use Menu » 6 Service Menu » 5 containing addressable loop
Loops. units.
2 Press 5 to activate the function Installation A zone or loop set to
Mode. Installation Mode are handled
as a disablement.
3.6.5 Save the System Log to a USB Memory Stick

If you want to check the information saved in the system log you can download it
from the central unit. The system log files contain information generated for
evaluating the system, such as lists of system components, system software and key
events.
Table 3. The following lists are included in the log

Centrals list Key events
Disablement list Modules list
Fault list Periodic disablement list
Fire alarm list Pre alarm list
History list Warning list
The system log files can be downloaded using an approved USB memory stick
(available from an authorised dealer).
CAUTION!
Do not remove the USB memory stick until the download is finished.
1 Connect the USB memory stick to the USB port on the Control M 4.3
panel.
2 Choose Menu » 6 Service Menu » 8 System Log » 1 Save syslog.
3 Press OK to save the systems log files to the USB memory stick.
4 The system will now download the system log files. Wait until this process
is complete!
5 Disconnect the USB memory stick and copy the system log files to a PC.
File name example: sysLog_no_YYYY-MM-DD-xxxxxx
3.6.6 How to report a fault

In case it is not possible to troubleshoot and solve a specific problem, please follow
these guidelines when contacting an authorized service office.
• Describe the fault symptom, be specific

• Describe how the fault situation can be generated

• Attach a system log file (instructions for download from the Fire detection
system can be found in section Save the System Log to a USB Memory Stick,
page 14)
• Attach the configuration file (instructions for download from the Fire detection
system can be found in the Service & Maintenance manual or in the
Configuration manual)
• Attach the backbone log if applicable
• Add your contact information


Service & Maintenance Manual 4 Cleaning of Fire Detectors
4 Cleaning of Fire Detectors
4.1 Prior to Cleaning

The need for cleaning the detectors is determined by visual inspection.
The method for cleaning a detector depends on the type of detector as described in
the following sub-sections.
4.2 Smoke Detector

1 Clean the detector with a vacuum cleaner or by blowing high-pressure
instrument air on it.
NOTE!
The high-pressure air must be of the instrument type (clean, not
containing oil, etc.)
Be careful not to damage the detector.
2 Clean the detector house with a damp cloth.
4.3 Heat Detector

The heat detector’s sensor rarely requires cleaning.
1 Clean the detector housing using a damp cloth.
4.4 Flame Detector

1 Clean the protective glass over the sensor using a grease solvent such as
soap or alcohol.
2 Clean the detector housing using a damp cloth.

4 Cleaning of Fire Detectors Service & Maintenance Manual

Service & Maintenance Manual 5 Replacing Batteries
5 Replacing Batteries
NOTE!
Replacement batteries shall be of the same type as the originals.
Disconnect the cables from the batteries.
1 Use a small blade screwdriver to remove terminal row plug 41-44 on

Charger M (4).
The battery connection to the system is now broken. If the system remains
on ‘Battery cable/fuse fault (158)’ and ‘Cable break/short circuit (159)’ is
generated after about 60-90 seconds. Mute the faults and proceed with the
next step.
2 Disconnect the + battery cable (red) from the uppermost battery pole (1)
and the - battery cable (black) from the lowermost battery pole (6).
3 Disconnect the jumper cable (3) that connects both batteries in series.
4 Unscrew the nuts from the uppermost battery bracket (2) and remove it.
5 Push the battery upwards, take hold of the lower battery end and carefully
wriggle it out of the cabinet with a downward motion.
6 Unscrew the nuts from the lowermost battery bracket (5) and remove the
second battery as the previous one.

5 Replacing Batteries Service & Maintenance Manual
Replace the batteries with the new ones.
1 Take hold of the lower battery end and carefully wriggle it into the cabinet
with an upward motion, releasing it into position. Note that the battery
poles should face away from the cabinet side, + pole upwards and - pole
downwards. Be careful not to snag the earth cables, trapping them beneath
the battery.
2 Put the battery bracket (5) back and secure the nuts.
3 Insert the second battery in the same way and let it slide down on top of the
lowermost one. Put the battery bracket (2) back and secure the nuts.
4 Reconnect the jumper cable (3) that connects both batteries in series.
5 Reconnect the - battery cable (black) to the lowermost battery pole (6) and
the + battery cable (red) to the uppermost battery pole (1).
6 Reconnect terminal row plug 41-44 on Charger M (4).
The battery connection to the system is reestablished.
7 Verify that the voltage is between 19 and 30 VDC* at the battery terminals.
8 Reset the battery fault alarm at the control panel.
* With battery charge enabled, acceptable voltage range is 27.8-28.2 VDC.

Service & Maintenance Manual 6 System Configuration
6 System Configuration
6.1 Configuration Program

The system is delivered pre-programmed with a standard configuration file. See the
separate Configuration Manual for information on how to create a new
configuration file or update an existing file.
CAUTION!
You must have appropriate knowledge on how to use the Configuration Program to
make a System Configuration.
In doubtful cases, do not hesitate to contact an authorized service office.
6.2 Downloading a configuration file to a USB

Memory Stick
When you want to view or make changes in an existing configuration file you can
download it from the fire alarm central.
The configuration file can be downloaded using an approved USB memory stick
(available from an authorized dealer).
CAUTION!
Do not remove the USB memory stick until the download is finished.
1 Connect the USB memory stick to the USB port.

2 Choose Menu » 6 Service menu » 6 Configuration » 3 Save configuration
to USB memory.
3 Choose the current configuration file from the list and press OK.
Supported files are “.ccp”, “espa.bin”, “modbus.bin” and
“modbus1.bin”-“modbus30.bin”.
4 The system will now download the configuration file. Wait until this
process is complete!
5 Disconnect the USB memory stick and copy the configuration file to a PC.
6.3 Uploading a configuration file from the USB

Memory Stick
When you have finished a configuration file it is time to upload it to the fire
detection system. Supported files are “.ccp”, “espa.bin”, “modbus.bin” and
Note that old versions of the definition program may affect the upload or system
operations. Use a program version of the CCP Configuration program compatible
with the system version used in your fire detection system.

6 System Configuration Service & Maintenance Manual
NOTE!
The system will use the latest version of the file (with the last date and time).
The configuration file can be uploaded using an approved USB memory stick
(available from an authorized dealer).
CAUTION!
Do not remove the USB memory stick until the upload is finished.
1 Connect the USB memory stick to the USB port.

2 Choose Menu » 6 Service menu » 6 Configuration » 2 Load configuration
from USB Memory.
3 A list of the available configuration files on the USB memory stick will be
presented. Supported files are “.ccp”, “espa.bin”, “modbus.bin” and
Choose the appropriate configuration file from the list and press OK.
4 The new configuration file is uploaded to the fire detection system. The old
configuration file is automatically renamed by the system (as a back-up file
with the file extension “.bak”) and saved on the USB memory stick.
5 Disconnect the USB memory stick.
6 To synchronise the configuration files between the control modules and
repeaters in the system choose Menu » 6 Service menu » 6 Configuration »
6 Synchronise system configuration
7 Reboot the system by choosing Menu » 6 Service menu » 6 Configuration »
7 Reboot system (this module excluded).
There will be a delay on 15 seconds before the system restarts.
8 Update the system with the new configuration file by choosing Menu » 6
Service menu » 6 Configuration » 1 Reload Configuration/Reboot this
module.
9 The Control M 4.3 restarts and loads the new configuration file.
NOTE!
The recommended way to load a configuration to a Control M X without USB-port
is by synchronizing the configuration from a USB equipped Control Module. This
is only possible if the Control M X resides on the same backbone as the USB
equipped Control Module (but it does not have to be in the configuration).
Another way of loading a configuration to a Control M X without USB-port is to
put its CCB in a USB equipped Control Module and load it as usual, then putting it
back in the Control M X.
NOTE!
In case of softcode changes on the entire system it is necessary to zero/reboot all
Loop M X modules.

Service & Maintenance Manual 6 System Configuration
6.4 Update protocols in a Control M X with USB

port
This instruction describes how to update protocols in a Control M X using a USB
memory stick.
Hint!
Files can also be transferred from a PC running System Software Updater to the
CCP System. Instructions for the System Software Updater program can be found
in the Appendix System Software Updater.
NOTE!
The protocol autoupdate and autoremoval functionality is valid from CCP software
version 1.10.0 and is supported for Control M X, Control M 4.3, and Control M 2.2
modules with USB port.
Prerequisites
• Computer running Windows 7/8/10
• Empty USB memory stick (bootable)
• Protocol cross reference file (.bin file)
NOTE!
Ensure there is no cm_firmware or cm_bios file on the USB memory stick.
A. Add or update protocols in a Control M X with USB port
1 Create a folder named autoupdate in the

USB root directory.
2 Copy the protocol .bin file to the
autoupdate folder on the USB stick.
3 Insert the USB memory stick into the USB
port on the Control M X module.
4 When the PS LED on the Control M X is NOTE!
turned off, remove the USB memory stick. The module restarts
soon after having read
the command so make
sure to remove the
USB memory stick,
otherwise it will
continue to update the
module.
5 Wait for the PS LED to be turned on (if not
turned on in 3 minutes, do a manual restart
as described below).
6 A fault will appear indicating that the
Control M X has been restarted (in Control
M 4.3 and/or Control M 2.2).

6 System Configuration Service & Maintenance Manual
All protocol .bin files will be backed up to the USB memory.
B: Remove protocols in a Control M X with USB port
1 Create a folder named autoremove in the

USB root directory.
2 Insert the USB memory stick into the USB
port on the Control M X module.
3 When the PS LED on the Control M X is NOTE!
turned off, remove the USB memory stick. The module restarts
soon after having read
the command so make
sure to remove the
USB memory stick,
otherwise it will
continue to update the
module.
4 Wait for the PS LED to be turned on (if not
turned on in 3 minutes, do a manual restart
as described below).
5 A fault will appear indicating that the
Control M X has been restarted (in Control
M 4.3 and/or Control M 2.2).
All protocol .bin files will be removed from the Control M X and backed up to the
USB memory.
NOTE!
If both the autoupdate folder and the autoremove folder exist on the USB root
directory at the same time, this will trigger an autoupdate when the USB stick is
inserted.
Hint!
Manual restart:
If the Control M X does not restart automatically during the autoupdate or
autoremoval procedure, it has to be restarted manually. To perform a manual restart
the Control M X can be removed from its slot and then inserted again, or the entire
system can be powered off and on. A fault will appear indicating that the
Control M X has been restarted (in Control M 4.3 and/or Control M 2.2).

Service & Maintenance Manual 7 Using the Service Menu
7 Using the Service Menu
7.1 Service menu - main screen

The Service menu is used to configure the system for the commissioning phase,
troubleshoot, and make small updates when the system is in operation. Loading and
saving information to and from the USB memory is run through the Service menu.
The main screen displays a list of the 9 service submenu alternatives, which are
described within this chapter.
(Use access level 2 for basic functions, but access level 4 is needed to perform
advanced service options.)
1. System details, submenu 1, page 25

2. Centrals, submenu 2, page 26
3. Modules, submenu 3, page 27
4. Zones, submenu 4, page 28
5. Loops, submenu 5, page 29
6. Configuration, submenu 6, page 32
7. Firmware, submenu 7, page 33
8. System Log, submenu 8, page 33
9. I/O Lists, submenu 9, page 33
How to navigate the menu system

• Navigate in the menu alternatives with the and arrow keys. It is also
possible to choose a menu alternative by entering the menu number.
• Select a menu alternative with the arrow key or the key.
• Use the arrow key to go back to the previous menu.
In the lower part of the display the different options available for each individual
menu are shown.
The numerical keypad is used to enter information, e.g., zone and detector number.
The button erases the last character.
7.2 System details, submenu 1

The first four lines display basic data about the installation. The data originates
from the configuration file (Options module).
• “SG Number”

7 Using the Service Menu Service & Maintenance Manual
• “Name of shipyard + number of build”

• “IMO Number”
• “Ship name”
The remaining information also concerns the configuration:
Servicepack The servicepack version

Created The time the configuration was created
Created by The person who created the configuration
Build Number of times that the configuration file has been
changed
File Name Name of the configuration file
Program The configuration program version used to create the file
• Press 1 to print a list with system details.

• Press 2 (Program versions) to see the software and hardware versions of the
system modules.
7.3 Centrals, submenu 2

Centrals main screen
The Centrals screen lists the centrals in the system:
CENTRAL x x is the central number where the central is placed

CENTRAL y y is the address of the central
• Press OK to monitor details about the selected central. (See OK=Details

below.)
• Press 1 to send a list with centrals to a connected printer.
• Press 2 to open the module list (similar to Modules main screen described in
section Modules, submenu 3, page 27).
OK=Details screen
Details about the central:
HW Hardware version
SW Software version
Timestamp Config Time and date of configuration
Modules found / configured Number of found and configured modules
System bus System bus configuration
Communication errors Number of reported communication errors in the last
65535 tries
• Press OK to go back to list view.

• Press 1 to send a list with details for the selected central to a connected printer.
• Press 2 to open the module list (similar to Modules main screen described in
section Modules, submenu 3, page 27).
7.4 Modules, submenu 3

Modules Main Screen
The Module screen lists the modules in the system:
CENTRAL x x is the number of the central where the module is placed

MODULE name x name is the module type and x is the address of the
module
(MODULE OK / BOOTING / Module status
CONFIG NOT FOUND)
• Press OK to monitor details about the selected module. (See OK=Details

below.)
• Press 0 to disable the selected module; all I/Os on the module will be disabled
and the fault associated with the module will disappear from the fault list.
• Press 1 to send a list with modules to a connected printer.
• Press 2 to monitor and manipulate the inputs of the selected module. (See
2=Inputs below.)
• Press 3 to monitor and manipulate the outputs of the selected module. (See
3=Outputs below.)
• Press 4 to monitor the loops of the selected module (if the module is a loop
module). The loop screens are explained in section Loops, submenu 5, page
29.
OK=Details screen
Details about system module:
HW Hardware version
SW Software version
Timestamp Config Time and date of configuration
No of loops Number of loops on the module
No of inputs/outputs Number of inputs and outputs on the module
Communication errors Number of reported communication errors in the last
65535 tries

• Press 0 to disable the selected module; all I/Os on the module will be disabled
and the fault associated with the module will disappear from the fault list.
• Press 1 to send a list with details for the selected module to a connected printer.

• Press 2 to monitor and manipulate the inputs of the selected module. (See
2=Inputs below.)
• Press 3 to monitor and manipulate the outputs of the selected module. (See
3=Outputs below.)
• Press 4 to monitor the loops of the selected module (if the module is a loop
module). The loop screens are explained in section Loops, submenu 5, page
29.
2=Inputs screen
Inputs of the module:
BOARD x x is the module address where the input is placed

INPUT x x is the input number
SET / CLEAR Indicates if the input is active (SET) or inactive (CLEAR)
• Press 0 to disable.
• Press 1 to send a list with inputs to a connected printer.
• Press 2 to set inputs of the selected module.
• Press 3 to clear inputs of the selected module.
3=Outputs screen
Outputs of the module:
BOARD x x is the address of the module that the output belongs to

OUTPUT GRP x / X Output category (OUTPUT GRP = General output, X
OUTPUT x could be FIRE, FAULT, DOOR, etc.) and x is the output
number
SET / CLEAR Indicates if the output is active (SET) or inactive (CLEAR)
• Press 0 to disable.
• Press 1 to send a list with outputs to a connected printer.
• Press 2 to set outputs of the selected module.
• Press 3 to clear outputs of the selected module.
7.5 Zones, submenu 4

Zone Main Screen
The Zone screen lists the zones in the system:
ZONE x x is the zone number

XXX (first row) Any text describing the zone, entered in the Zone module
in the configuration program as “Text 1”
XXX (second row) Any text describing the zone, entered in the Zone module
in the configuration program as “Text 2”

• Press OK to monitor details about the selected zone. (See OK=Details below.)
• Press 0 to disable the selected zone.
• Press 1 to print a list with zones.
• Press 2 to monitor and manipulate the loop units in the selected zone. (See
2=Loop Units below.)
• Press 5 to activate the function Installation Mode. For instructions, see
Installation Mode, page 14.
OK=Details screen
Details about zones:
Units defined Number of loop units in the zone

Units located on Loop The logical loop/loops where the loop units are placed

• Press 1 to print a list with details for the selected zone.
2=Loop Units screen

NOTE!
This section is only applicable for addressable systems.
Loop units:
LOOP x x is the logical loop number

SMOKE / MCP / SCI x Detector type (MCP = Manual call point, SCI = Short
Circuit Interruption) and logical address x
• Press OK to monitor details about the selected loop unit.

• Press 0 to disable the selected loop unit.
• Press 1 to print a list with loop units.
• Press 2 (Set in fire) to simulate a fire alarm in the system. For instructions, see
Simulate a fire alarm in the system, page 8.
• Press 3 (Erase) to remove the loop unit from the configuration.
• Press 4 to change the supplementary text of the loop, which is shown in the
display in case of an alarm (also visible in the Details list, reached using the OK
button).
7.6 Loops, submenu 5

Loop Main Screen
NOTE!
The Loop screen lists the loops in the system:

LOOP Loop name and logical loop number

XXX (first row) Any text describing the loop, entered in the Loop board in
the configuration program as “Text 1”
XXX (second row) Any text describing the loop, entered in the Loop board in
the configuration program as “Text 2”
• Press OK to monitor details about the selected loop. (See OK=Details below.)
• Press 0 to disable the logical loop; the loop will be disconnected galvanically
• Press 1 to print a list with loops.
• Press 2 to monitor and manipulate the logical loop. (See 2=Loop Units below.)
• Press 3 to add a logical loop. (See 3=Add Unit below.)
• Press 4 to scan for new or changed loop units, for example, detectors. (See
4=Scan Loop below.)
• Press 5 to activate the function Installation Mode. For instructions, see
Installation Mode, page 14.
OK=Details screen
NOTE!
Details about loops:
System Address (crd.subCrd) Address of the loop; crd = Board address, subCrd =
number of physical loop
Loop Units Number of found/expected loops
Communication errors Number of reported communication errors in the last 1000
tries
Current consumption Current electrical consumption of the loop
Fire Alarms Number of active fire alarms at the moment
Fault Alarms Number of active fault alarms at the moment
Disablements Number of disablements at the moment

• Press 1 to print a list with details for the selected loop.
2=Loop Units screen

NOTE!
Details about the loop units:
Detector type and logical SMOKE HEAT / LOOP DEVICE / MCP x

address x

Comm. Stat Communication status. The unit answers on side A

(primary) and side B (secondary); when looking for a short
circuit or a cable break this information is useful for
locating the break or short circuit
• Press OK to monitor details and manipulate the selected loop unit

Alternatives for Loop Units submenu screen:
• Press 0 to print a list with details for the selected loop unit.
• Press 1 to disable the selected loop unit.
• Press 2 (Set in fire) to simulate a fire alarm in the system. For instructions, see
Simulate a fire alarm in the system, page 8.
• Press 3 (Erase) to remove the loop unit from the configuration.
• Press 0 to print a list with details for the selected loop unit.
• Press "1 Update list" to update the answering side status when A/B list shows
OK (?/?).
3=Add Unit screen

NOTE!
Add loop units:
UP/DOWN Press UP/DOWN to navigate the rows.

Value Use the numerical keypad to give the selected loop unit an address.
OK Press OK to add the selected loop unit with the specified address. Note
that all the entered information must be valid before a loop unit can be
added.
4=Scan Loop screen

NOTE!
The system will clear the EEPROM of the loop module, then restart and rescan the
loop. Any changes, for instance function IDs in loop units, will be recognized and
saved.
WARNING!
The loop is disabled during the scan.
Scan loop:
• Press OK to perform the scan.

7.7 Configuration, submenu 6

Hint!
For further instructions, refer to Downloading a configuration file to a USB
Memory Stick and Uploading a configuration file from the USB Memory Stick,
page 21.
The following alternatives can be found in the Configuration submenu:
1 Reload configuration/Reboot this module

Reload the configuration when a new updated configuration file has been
downloaded to the system. The operation will reboot this Control Module only.
NOTE!
In case of softcode change on the entire system it is necessary to zero/reboot all
Loop M X modules.
2 Load configuration from USB Memory

Download a new configuration file from a suitable USB memory stick.
3 Save configuration to USB Memory

Copy the existing configuration file to a suitable USB memory stick.
4 Save changes to configuration

CAUTION!
A backup of the old configuration file should be saved on a USB memory stick
(see Downloading a configuration file to a USB Memory Stick, page 21) before
saving changes to the configuration.
The Save changes to configuration screen is used to keep the changes made to the
system configuration from the control panel.
NOTE!
The changes are not permanently saved in the configuration file until this
command is performed.
5 Remove configuration
Select and remove files from a list of configuration files in the system.
6 Synchronize system configuration

CAUTION!
It is highly recommended to backup the configuration file before continuing.
Use this command to synchronise the configuration files in the system.
7 Reboot system (this module excluded)

The operation will reboot the system with this Control Module excluded.

7.8 Firmware, submenu 7

Use this menu to download firmware to modules, load or backup service pack, and
to start or stop an automatic update.
1. Download firmware to modules

2. Load service pack from USB memory
3. Backup service pack to USB memory
4. Start automatic update
5. Stop automatic update
Hint!
For further instructions, refer to Upgrade Firmware, page 37.
7.9 System Log, submenu 8

1 Save Syslog
The Upload syslog to USB memory menu is used to save a system log with service
information to the USB memory stick. This system log can then be sent to an
authorised service office for technical assistance. (For instructions refer to Save the
System Log to a USB Memory Stick, page 14.)
2 Reset Service Intervals

If appropriate use this menu to reset service interval.
3 BIST Log
This log presents the results of the Periodic BIST (Built-In-Self-Test). This menu
alternative is intended for SIL classified systems only.
7.10 I/O Lists, submenu 9

I/O lists with sub-menus Input list and Output list. Use these menus for inspecting
or disable active inputs and outputs.
1 Input list
2 Output list
1. All active outputs
2. Manually activated outputs
3. Automatically activated outputs


Service & Maintenance Manual 8 System Upgrade
8 System Upgrade
8.1 Upgrade BIOS

8.1.1 Upgrade BIOS for a CCP System from USB Stick
This instruction describes how to upgrade BIOS in a CCP System using a USB
stick.
Follow all steps below:

A. Prepare the USB memory stick
B. Upgrade BIOS in a Control M 4.3, Repeater M 4.3 or Control M 2.2
C. Upgrade BIOS in a Control M X with USB port
D. Upgrade BIOS in a complete Fire Detection System
Prerequisites
• Computer running Windows 7, 8, or 10.
• BIOS release
A. Prepare the USB memory stick
1 Copy the file cm_bios_v_xx to the root catalogue of the USB memory stick
(where xx is the version number).
NOTE!
The above file naming convention is only applicable from BIOS
version 2e onward. For BIOS versions earlier than 2e the file shall
be named cm_bios.
2 Reboot the control module.
B. Upgrade BIOS in a Control M 4.3, Repeater M 4.3 or Control M 2.2
1 Insert the USB memory stick into the control module.

3 Wait for the module to display the message BIOS update OK.
4 Remove the USB stick.
C. Upgrade BIOS in a Control M X with USB port
1 Insert the USB memory stick into the control module.

2 Wait for update.

8 System Upgrade Service & Maintenance Manual
D. Upgrade BIOS in a complete Fire Detection System
1 Repeat step B.1-B.4 for all the Control M 4.3, Repeater M 4.3 and Control
M 2.2 in the system.
2 Remove the BIOS file from the USB stick.
8.1.2 Upgrade BIOS in a Control Module via Ethernet

(Control M X without USB port)
This instruction describes how to upgrade BIOS in a CCP System via Ethernet.
NOTE!
Primarily, use a USB memory stick to upgrade BIOS in a Control M 4.3, Repeater
M 4.3, Control M 2.2 or Control M X with USB port.
To Control M X without USB port you have to use the Ethernet connection.

A. Prepare the physical connection
B. Start the Firmware update tool
C. Select network adapter
D. Establish connection with target
E. Update the firmware
Prerequisites
• Computer running Windows 7/8/10 and an Ethernet cable.
• BIOS release
1 Connect the Ethernet cable between your CAUTION!

computer and the module you wish to You have to connect
update. the cable point to
point directly to the
module. If you
connect to a network,
the tool may serve all
the centrals and other
clients with
unexpected results.
1 Execute the firmware update tool CAUTION!

“firmware_updater.exe” as administrator. You have to run the
• Start firmware_updater.exe and you will tool as administrator,
be prompted to login as administrator otherwise the tool will
automatically. not be able to establish
proper communication
with the target.
2 When the file dialog opens, select the BIOS
file you wish to download and select Open.

1 Go to Tools » Options.
2 Select manual configuration.
3 In the drop down list. Select the network adapter that you connect your
cable to.
4 Select OK to confirm your selection.
1 The tool should now automatically attempt to establish connection with the
target and print out detected Central and Card address together with current
flashed firmware version.
2 The tool should now be ready to download new firmware.
1 Press the Program Firmware button and This may take some time to
wait. complete.
2 Target will reboot. If the target hardware has a
version before 1.2.0 you may
still be able to program it by
manually rebooting the target
when requested by the tool. (If
the bootloader supports
booting over Ethernet.)
3 Target will then re-establish connection
with the tool and start downloading the new
firmware.
4 Target will be reflashed.
5 Target will reboot and start the new
firmware.
8.2 Upgrade Firmware

8.2.1 Upgrade Firmware for a CCP System from USB
Stick
This instruction describes how to upgrade firmware in a CCP System to Service
Pack 1.3.0 and later.
Hint!
Recommendations for centrals containing many control modules/repeaters and/or
distributed centrals can be found in section Upgrading Large Systems, page 45.

Hint!
CCP System using SSH and SCP protocols. Please refer to the System Software
Updater instructions which can be found in the Appendix section of the Service &
Maintenance Manual.
Hint!
Go to the Service Menu, in order to check if the firmware or BIOS upgrade has
been successful.
NOTE!
NOTE!
It is essential to use the same version of the configuration software as the firmware
in the system. Otherwise there might be a conflict and major functions be set out of
order.

A. Back up the configuration file
B. Prepare the USB memory stick
C. Upgrade the firmware in a Control M 4.3, Repeater M 4.3, Control M 2.2 or Control M
X with USB port
D. Upgrade the firmware in the Control M X without USB port
E. Upgrade the firmware in the remaining CCP modules
Prerequisites
• CCP software release
• Computer running Windows 7/8/10 and an Ethernet cable (necessary for
Control M X without USB-port)
• BIOS version R2n or later already installed for a Control M X with USB port
1 Make sure the configuration software installed on the computer matches the
new firmware version.
2 Download valid configuration from Control M 4.3 (or Control M 2.2) to
USB memory stick.
3 Resave the configuration file (.ccp) using the CCP configuration sw version
that match the firmware version.
B. Prepare the USB memory stick
1 Copy the file cm_firmware to the root catalogue of the USB memory stick.

C. Upgrade the firmware in a Control M 4.3, Repeater M 4.3, Control

M 2.2 or Control M X with USB port
NOTE!
Control M X with USB interface is supported by firmware release 1.8.50 or later
1 Insert the prepared USB memory stick into File name: cm_firmware
the control module.
3 The control module will now boot from the The text CCP is shown for a
USB cm_firmware and write a new Linux few minutes (on a Control
installation to the built-in FLASH Memory. M 4.3, Repeater M 4.3 or
Control M 2.2) until the
uImage has booted.
4 Firmware update of the application starts. The text "Firmware update
started..." is shown on the
screen. (The Control M X
restarts when finished.) Upon
completion the module is
automatically restarted.
6 Reboot the control module with the reset
key or by turning the power off-on.
D. Upgrade the firmware in the Control M X without USB port
1 Use the CCP Firmware Update Tool to See section Upgrade

update this module via the Ethernet Firmware in a Control Module
connector. via Ethernet (Control M X
without USB port), page 42
for details.
E. Upgrade the firmware in the remaining CCP modules
1 Select Menu » 6 Service Menu » 7 NOTE!

Firmware » 1 Download firmware to Access Level 4 is
modules in the Control M 4.3. required to upgrade
firmware in the
system. You may be
required to login with
correct credentials
during the firmware
upgrade process.
2 Wait for the system to compare firmware A list of centrals is displayed.
versions in the Service Pack with the
firmware versions in the modules found by
the system.
3 Select the central you want to upgrade with
firmware and press 2 to get a list of
modules found in that central.

4 Select the module you want to upgrade and

press 0 to start the upgrade.
5 Wait until the firmware download counter
has progressed to 100%.
6 Repeat steps 4 and 5 for all the modules Explanation of icons:
you want to upgrade. • = Invalid firmware
It is recommended to upgrade modules
• = Upgrade available
marked with and .
• = Firmware OK
• = Service Pack or
Module missing –
firmware download not
available
8.2.2 Upgrade Firmware for a CCP System from

MicroSD Card
This instruction describes how to upgrade firmware in a CCP System v. 1.5.0 or
later to Service Pack 1.8.0 or later.
Hint!
Recommendations for centrals containing many control modules/repeaters and/or
distributed centrals can be found in section Upgrading Large Systems, page 45.
Hint!
CCP System using SSH and SCP protocols. Please refer to the instructions for the
System Software Updater program.
NOTE!
NOTE!
It is essential to use the same version of the configuration software as the firmware
in the system. Otherwise there might be a conflict and major functions be set out of
order.

B. Prepare the microSD memory card
C. Upgrade firmware in a Control M X
D. Upgrade firmware and synchronise configuration in a Control M 4.3 or Control M 2.2
Prerequisites
• USB memory stick
• MicroSD memory card

• CCP software release

• Computer running Windows 7/8/10
• BIOS version R2h or later already installed for the Control M 4.3, Control
M 2.2 and Repeater M 4.3 modules
• BIOS version R2n or later already installed for a Control M X with USB port
1 Make sure the configuration software installed on the computer matches the
new firmware version.
2 Download valid configuration from Control M 4.3 (or Control M 2.2) to
USB memory stick.
3 Resave the configuration file (.ccp) using the CCP configuration sw version
that matches the firmware version.
B. Prepare the microSD memory card
1 Copy the file cm_firmware to the root

catalogue of the microSD memory card.
2 Copy the configuration file (.ccp) to the
root catalogue of the microSD memory
card.
3 Copy the service pack file (.out) to the root NOTE!
catalogue of the microSD memory card. This step is optional.
4 Copy the protocol configuration file (.bin) NOTE!
to the root catalogue of the microSD This step is optional.
memory card.
C. Upgrade firmware in a Control M X
1 Insert the prepared microSD memory card

into the memory card holder.
2 Reboot the module. The module will now boot
from the SD memory.
3 The Control M X restarts when finished.
D. Upgrade firmware and synchronise configuration in a Control M 4.3

or Control M 2.2
1 Insert the prepared microSD memory card

into the memory card holder.

2 Reboot the Control Module via Menu » 6 NOTE!

Service Menu » 6 Configuration » 1 Reload Automatic function
configuration/Reboot this module. reading the microSD
memory card will
upgrade the Contol
M 4.3 (or Control
M 2.2) with firmware
and the configuration
stored on the microSD
memory card.
3 Synchronise the configuration file via
Menu » 6 Service Menu » 6 Configuration
» 6 Synchronise system configuration.
4 Reboot the other Control Modules in the
system via Menu » 6 Service Menu » 6
Configuration » 7 Reboot system (this
module excluded).
5 Reset the reported faults when all modules
are operational.
8.2.3 Upgrade Firmware in a Control Module via

Ethernet (Control M X without USB port)
This instruction describes how to upgrade the firmware in a CCP Control Module
via Ethernet using the CCP Firmware Update Tool.
NOTE!
If the firmware version is 1.8.0 or later, and the control module has an SD card, the
CCP Firmware Update Tool can not be used. In this case the control module must
be upgraded via System Software Updater instead. Instructions can be found in
the Appendix section of the Service & Maintenance Manual.
NOTE!
Primarily, use a USB memory stick to upgrade firmware in in a Control M 4.3,
Repeater M 4.3, Control M 2.2 or Control M X with USB port.
To Control M X without USB port you have to use the Ethernet connection.

Prerequisites
• Computer running Windows 7/8/10 and an Ethernet Cable.
• CCP software release image file (i.e. cm_firmware).
• The Control Module must have at least Firmware 1.2.0 in order to support
update via Ethernet.

1 Connect the Ethernet cable between your CAUTION!

computer and the module you wish to You have to connect
update. the cable point to
point directly to the
module. If you
connect to a network,
the tool may serve all
the centrals and other
clients with
unexpected results.
1 Execute the firmware update tool CAUTION!

“firmware_updater.exe” as administrator. You have to run the
• Start firmware_updater.exe and you will tool as administrator,
be prompted to login as administrator otherwise the tool will
automatically. not be able to establish
proper communication
with the target.
2 When the file dialog opens, select the
image you wish to download and select
Open.
1 Go to Tools » Options.
2 Select manual configuration.
3 In the drop down list. Select the network adapter that you connect your
cable to.
4 Select OK to confirm your selection.
1 The tool should now automatically attempt to establish connection with the
target and print out detected Central and Card address together with current
flashed firmware version.
2 The tool should now be ready to download new firmware.
1 Press the Program Firmware button and This may take some time to
wait. complete.

2 Target will reboot. If the target hardware has a

version before 1.2.0 you may
still be able to program it by
manually rebooting the target
when requested by the tool. (If
the bootloader supports
booting over Ethernet.)
3 Target will then re-establish connection
with the tool and start downloading the new
firmware.
4 Target will be reflashed.
5 Target will reboot and start the new
firmware.
8.2.4 Troubleshooting for Firmware Update Tool

If the tool runs but the firmware has not been updated
• Check that there is no cm_firmware file present on the SD card mounted in the
control module.
If the tool stops while attempting to start servers

• Check that you are running the tool with administrator rights
• Check that you have selected the correct Ethernet interface in Tools » Options
• Check that the target module is running (i.e. turned on)
If the tool stops while scanning for target hardware

• Check the physical cable connection
• Check that the target has U-boot 1.3.4 and firmware release at least 1.1.1
• Check that the target is running (i.e. turned on)
If the tool stops while establishing TFTP connection

• Try to re-run the program procedure from start, or
• Try to switch to another Ethernet adapter.
If the tool stops while requesting target reboot

• A target reboot may take some time, please be patient and wait awhile before
proceeding.
The tool should continue when a response is received from the target.
• The target hardware may be lacking a BIOS, or have a BIOS with an incorrect
version name. This prevents target reboot.
For instructions on how to solve this, refer to Upgrade BIOS, page 35.
• The target hardware may be running a firmware before 1.1.1 and therefore can
not respond.
In this case you can try and reboot the target manually.

8.3 Upgrading Large Systems

8.3.1 Upgrade strategy
NOTE!
The following procedure is recommended for centrals containing many control
modules/repeaters and/or distributed centrals.
Hint!
Before following the instructions below it might be a good idea to understand the
basics of what the instructions are trying to achieve in order to avoid excessive
master/slave switches and to minimize the traffic that occurs when the system is
trying to synchronize its state between all control modules.
To accomplish less traffic due to the configuration synchronization upgrade the

firmware and configuration at the same time for each control module using the
USB stick (repeaters must still be synchronized at the last step).
In order to reduce the number of master/slave switches the ordering of the upgrade
is to start with the control modules on the primary system bus and then proceed
with the control modules on the secondary system bus.
To further reduce traffic on extension buses. Upgrade and restart the control
modules owning an extension bus before the repeaters on the extension bus.
Finally, for really large systems (more than 5000 loop units) it will further reduce
the traffic to disconnect the system buses completely at 1.1 and 1.2 during the
upgrade.
8.3.2 How to upgrade each control module

Preparation
Prepare a USB memory stick with the desired controlm_firmware file and
configuration file.
Upgrade for control panel modules (Control M 4.3 and Control M 2.2)
Hint!
Further information can be found in section C. Upgrade the firmware in a Control
M 4.3, Repeater M 4.3, Control M 2.2 or Control M X with USB port, page 39.
1 Insert the USB memory stick into the

control module.
2 Reboot the control module. Update starts. Wait until the
firmware update is finished.
3 Remove the USB memory stick.
4 Restart the control module. Wait until the control module
has restarted.
5 Insert the USB memory stick.

6 Copy the configuration file to the control Choose Menu » 6 Service

module via the menu system. menu » 6 Configuration » 2
Load configuration from USB
Memory.
7 Remove the USB memory stick.
8 Restart the control module again.
Upgrade for Control M X modules without USB port
1 Connect an Ethernet cable to the Control M For instructions to use CCP

X and use the firmware updater software Firmware Update Tool, please
(CCP Firmware Update Tool). refer to Upgrade Firmware in
a Control Module via Ethernet
(Control M X without USB
port), page 42
2 When the module is upgraded and restarted
use WinSCP (or similar) to copy the
configuration file to /app/rw.
3 Restart the module again.
8.3.3 Upgrade modules in the following order

NOTE!
Make sure to read How to upgrade each control module above before attempting to
follow these instructions!
1 Disconnect power to all control

modules/repeaters in the system.
For really large systems (more than 5000
loop units) also disconnect the system
buses at 1.1 and 1.2.
2 Reconnect power and upgrade the modules This means 1.1, 2.1, 3.1, ...,
connected to the primary system bus. x.1. The ordering is not
important.
3 Reconnect power and upgrade the modules This means 1.2, 2.2, 3.2, ...,
connected to the secondary system bus. x.2. The ordering is not
important.
4 Now reconnect power and upgrade all other Since it is not possible to copy
control modules/repeaters within each the configuration file directly
central. to repeater modules it will be
If a control module has an extension bus synchronized later on.
with repeaters on it then make sure that the
control module itself is first upgraded
before upgrading its extension bus
modules.

5 All control modules/repeaters should now If the system buses were

be upgraded. disconnected at the first step
then reconnect them - starting
at the primary side - and wait
a couple of minutes for the
system to synchronize.
6 If repeater modules are present on
backbone or extension bus then go to 1.1
and synchronize the configuration via the
menu system, else the upgrade of repeater
modules are complete.
7 Upgrade all other system modules within For instructions, see section E.
each central. Upgrade the firmware in the
remaining CCP modules, page
39.


Service & Maintenance Manual 9 Appendix - Central Unit Terminal & Cabling Layout
9 Appendix - Central Unit Terminal &

Cabling Layout
9.1 Central Unit Terminal & Cabling Layout

Description of System Modules
The Fire detection system is based on standard modules. Below is a list of some
common modules:
Control M 4.3
A Control panel with a 4.3” display that manages and supervises a system and
can act as bus master or slave.
Repeater M 4.3
A Repeater panel with 4.3” display that can act as bus slave.
Control M 2.2
A Control panel with a 2.2” display that manages and supervises a system and
can act as bus master or slave.
Control M X
A Control module without display that can act as bus master or slave. It is used
for providing additional communication channels in the system.
Loop M X
A module that supplies one addressable Loop.
I/O M 70
A module that provides 8 I/Os of type I/O 70. Each I/O can be programmed for
use as: an input (max 70 mA), an output for buzzers, relays etc (max 70 mA) or
a conventional detector zone.
I/O M 700
A module that provides 8 I/Os of type I/O 700. Each I/O can be programmed for
use as: an input or an output for magnets, power supply etc (max 700 mA).
Relay M 8
A module that provides 8 potential free contacts.
Surge Prot M
A module that provides surge protected power inputs for the BBI, terminal
board for BBE and electronic short circuit protected outputs for Control or
Repeater panels.
Charger M
A module that supervises and controls the power and battery functions.
Change Over M Ext

A change-over module that monitors mains and emergency power inputs.
Bus Isolator M
This module is used for dividing the system backbone bus into segments. It can
provide power to Control Panel M 4.3 and Control M 2.2.
PSU M AC/DC 5A
A 5 ampere 115/230 VAC/VDC Power Supply.
PSU units can be used in pairs to supply 5+5 A.
For complete information, see the data sheet for each module.

9 Appendix - Central Unit Terminal & Cabling Layout Service & Maintenance Manual
An example of a central unit terminal layout with cabling

Since all Fire detection systems are tailored to each customer installation, no
standard exists for how the different modules are to be connected in the system.
However, in the figure below you will find an example with one module of each
type showing the connection terminals.

Service & Maintenance Manual 9 Appendix - Central Unit Terminal & Cabling Layout
Figure 5. An example of a central unit terminal layout with cabling for a marine installation.

9 Appendix - Central Unit Terminal & Cabling Layout Service & Maintenance Manual

Service & Maintenance Manual 10 Appendix - Termination
10 Appendix - Termination
10.1 RS-485 Termination

10.1.1 General Recommendations for Installation of
RS-485
General recommendations for RS-485 installation:
• Twisted pair wire should be used

• Shielded cables
• Star networks are not permitted
• Termination shall be made at each end of the bus with a 120 ohm resistor
• Max 700 m cable in one communications segment
• Two-wire connection shall be used when nodes have a common ground (-)
• Three-wire connection shall be used when nodes have a different ground (-), for
example between Bus Isolator M.
10.1.2 Application Examples for Installation of RS-485

Activate the built-in terminator (120 ohm).
=
See datasheet for location of the DIP switch.
= Terminator 120 ohm
10.1.2.1 Terminating of BBE and Extensions bus

10 Appendix - Termination Service & Maintenance Manual

10.1.2.2 Terminating of BBE example 1
10.1.2.3 Terminating of BBE example 2

10.1.2.4 Terminating of modules (BBI) mounted on single DIN

rail
10.1.2.5 Terminating of modules (BBI) mounted on more than

one DIN rail
10.2 Additional Information for BBU Termination

10.2.1 Basic Backup Signal, BBU
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 BBU 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 are 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 6. Signal levels Basic Backup Signal
10.2.2 Application Example for Installation of BBU

10.2.2.1 Connections
Figure 7. Two Bus Isolator M Figure 8. Terminal drawing of two

Bus Isolator M
CAUTION!
A 2 kΩ resistor is pre-fitted between terminals 31 and 32.
• Remove the resistor if the Basic Backup (BBU) output is being used.
• Ensure the resistor remains fitted if the terminals are not in use. If the resistor
is missing when the BBU signal is activated (fire alarm), it will not be
possible to reset the alarm.
Figure 9. Example of BBE connection between two (or more) backbone segments in one spur
NOTE!
Only one of the Basic Backup (BBU) channels shall be connected.

Figure 10. Example of BBE connection between three (or more) backbone segments (1, 2, 3, n) in
several spurs
BBE = Backbone External, BBI = Backbone Internal, = 120 ohm resistor. Use twisted
pair cables for the BBE connections. See Figure 9. regarding the BBE, BBU and resistor
specific connections.

10.2.3 Testing the BBU Installation

1 Make sure that the system is connected to an external power supply.
2 Place a temporary jumper between terminals 31 and 41 to make a short
circuit which will trigger an alarm in the system.
3 Wait until the short circuit fault has generated an alarm in the system
4 Remove the temporary jumper between terminals 31 and 41.
5 • If the alarm can be reset the BBU installation is OK.
• If the alarm cannot be reset check for any missing 2 kΩ resistor between
unused terminals 31 and 32

Service & Maintenance Manual 11 Appendix - System Software Updater
11 Appendix - System Software Updater
11.1 System Software Updater

11.1.1 Setup
System Software Updater is compatible with Windows 7, 8, 8.1 (both 32 and 64 bit
versions), and Windows 10. Installation of System Software Updater requires one
of these operating systems.
System Software Updater is included in CCP Tools. To install System Software

Updater, start Microsoft Windows and follow this procedure:
1 Obtain the CCP Configuration Program and locate the CCP Tools setup
file.
2 Run the installer program and follow the instructions.
Files can be transferred from the PC running System Software Updater to the Fire
Detection System using SSH and SCP protocols. To enable this, a connection
between the PC and the system needs to be setup using a network adapter.
To connect with the system, the PC needs a static IP address in the range from
192.168.200.0 to 192.168.200.255 with subnet mask 255.255.255.0. To change the
IP address and subnet mask, follow this procedure in Microsoft Windows:
1 Choose Properties for the network adapter that connects the PC with the
Fire Detection System.
2 Choose Properties for Internet Protocol version 4 (TCP/IPv4).
3 Choose Use the following IP address.
4 Set IP address to an address in the range from 192.168.200.0 to
192.168.200.255.
5 Set subnet mask to 255.255.255.0.
11.1.2 Startup
The figure below shows the System Software Updater program at startup. From
here you can update software for Control Modules.

11 Appendix - System Software Updater Service & Maintenance Manual
NOTE!
If Windows Firewall is active, the Windows Security Alert dialog will open the
first time System Software Updater is run. Click Allow access to continue.
11.1.3 Prepare Update

There are two ways to select the Control Module(s) to update, either by manually
specifying the type and IP-address or by loading a Configuration file (.ccp). If the
system is not configured, it is necessary to manually specifying the type and
IP-address. Otherwise, it is preferable to load a Configuration file.
To manually select the Control Module(s) to update, specify the type and
IP-address of the Control Module in the corresponding text fields and press Add.
To load a Configuration file, press Open and specify the correct Configuration file
in the window as shown below.
NOTE!
The version of the .ccp files shall correspond to the firmware version of the system.

To load a firmware or service pack, press Open next to the corresponding option
and specify the correct file in the window as shown below.

To transfer extra files (i.e. espa.bin or modbus.bin), mark a Control Module in the
list and press Add next to Extra files:. Specify the correct file in the window as
shown below.
The version numbers of the selected Firmware, Service Pack and Configuration file
is shown in the top left corner of the program. Control Modules with extra files are
indicated with an icon in the Extra files field of the Control Module list.

When a Control Module is added to the list the program notes the Control Module's
current software version in the SW version field of the Control Module list. After a
successful update the information in this field changes to reflect the new software
version.
11.1.4 Update
To perform an update a preparation is needed, see Prepare Update. With a correct
preparation in place press Update to view information about the update to be
performed.

If the update information is correct, press OK to start the update. Press Cancel to
make changes prior to the update.
A rotating arrows symbol indicates that the update is in progress. An individual

progress bar indicates the update status for each Control Module, the bar is shown
under Progress in the Control Module list. A log of the update is shown at the right
side of the program, under Status:.

When the update is finished a prompt informs the user about the result of the
update, press OK to close the prompt.
If an error has ocurred, see the log under Update: for more information.

Figure 11. Example of an error message.
To reboot a Control Module, mark its checkbox in the Reboot field of the Control
Module list and press Reboot.
11.1.5 Menu
To view the version of the System Software Updater press About in the Help
menu.
The Backup Files button executes a backup of unit files (configuration files,
firmware, etc) to the SD-card in the unit.
Under Status a filtered log is shown. Press Show full log in the Help menu to
show the complete log.
To save the complete log to disc press Save log file as in the File menu.
To stop an ongoing update press Abort in the Update menu.

Service & Maintenance Manual 12 Appendix - Fault Code List
12 Appendix - Fault Code List
12.1 Fault Code List
WARNING!
In case of remedy “replace the unit” or “replace the module” – this has to be
carried out as soon as possible in order to secure the functionality of the fire
detection system.
Listed in the table below are all fault codes generated by system modules1 and loop units2 ,
their causes, and how an operator with knowledge of the system can classify and solve the
problem.
A fault generated by a system module is often identified as:
“CENTRAL nn Unit type nn Fault description , FAULT nnn”
A loop unit fault is often identified as:
“ZONE nn Unit type nn Fault description , FAULT nnn”
Hint!
Instructions for troubleshooting and replacement can be found in the Installation
manual or the Service & Maintenance manual.
1) Central components and control/repeater panels.

2) Units connected to the loop line, e.g. detectors and manual call points.

12 Appendix - Fault Code List Service & Maintenance Manual
Unit or
Fault Code Cause Remedy Failure classification
Module
One module has
been replaced by
Switch to the correct module. • Minor fault if
another type of
module. redundant system
and only one
One module address
module in the
has been changed to
redundant function.
the same address as
another module on Check address of the modules. • Major fault if
System the same backbone redundant system
modules (a secondary fault and one or more
appears). modules in the
redundant function.
Defect module. Replace the module.
Cable break, short • Major fault if one or
circuit or wrong more modules in a
Locate the cable break, short non-redundant
electrical connection
circuit or check the electrical system.
of the internal
connections.
communication bus
NO ANSWER (BBI to BBE).
Explanation: Lost
The loop unit has
communication.
electrically been
128 The system has Connect the loop unit.
disconnected from
recognized a
the loop.
unit/module but
lost contact. The loop unit has Check that the correct loop unit
been replaced by is installed.
another type of loop
unit, or the loop unit Check that the ID switch for an • Minor fault if only
ID has been I/O ICxx unit is set correct. one detector within
changed. an area covered by
other detectors.
One loop unit 1. Check address of the units.
Loop units
address has been set • Major fault if two or
2. Rescan or restart the loop.
to the same address more detectors
as another loop unit within the same
on the same loop (a area.
secondary fault
appears).
Defect unit. Replace the unit.
Cable break or short
circuit in a loop (a Locate the cable break or short
secondary fault circuit.
appears).

Unit or
Module
The detector has a
faulty sensor Replace the unit.
element.
The smoke detector Protect the detector from the
is exposed to strong airflow or consider repositioning
airflow. the detector.
• Check the device on the
129 SENSOR FAULT Loop units Input on a sub-loop sub-loop. Major fault
has a removed or
faulty device, an • Check the end of line
open circuit, or a component.
cable break. • Locate the cable break.
There are two loop 1. Check address of the units.

units with the same
address on the loop.
Minor fault (or Service
fault).
The fault code is
presented before the
The detector has a
Smoke contamination level
130 DIRTY SENSOR dirty (contaminated) Replace the detector.
detectors becomes critical for the
sensor element.
risk of spurious alarm
or no alarm. The
remedy shall still be
performed.
Fewer loop units Check the loop configuration
found than and electrical connections.
configured. Loop
units not correctly 1. Check address of the units. Major fault.
TOO FEW
Detector association
131 LOOP UNITS Loop M X installed or 2. Rescan or restart the loop.
addressed. missing for internal
FOUND
control.
Missing answer Check the address (possible
from one or more double address).
units. Otherwise replace the unit.
More loop units
Check the loop configuration
found than Major fault.
TOO MANY and electrical connections.
configured. Detector association
132 LOOP UNITS Loop M X
1. Check address of the units. missing for internal
FOUND Loop units not control.
correctly installed. 2. Rescan or restart the loop.
Loop I/O Check that the cable between Major or Minor fault
IN1 CABLE There is a cable
133 units with input and end of line resistor is depending on project
BREAK break on input 1.
inputs complete. specific function.
Loop I/O Check that the cable between Major or Minor fault
IN2 CABLE There is a cable
134 units with input and end of line resistor is depending on project
BREAK break on input 2.
inputs complete. specific function.

Unit or
Module
Charger M 1. Measure the voltage from the
power source.
• If voltage OK, change
External 24V power
loop unit.
Loop units source missing or
135 EXT 24V FAIL with the local power • If voltage NOT OK, Major fault.
external supply unit is change the DC/DC.
power defective.
2. If problem not solved contact
an authorized service office.
There is a fault in
the feedback
Check the cable for the feedback
between the loop
from the connected device to the
Loop I/O unit and the Major or Minor fault
FEEDBACK loop unit, for instance the
136 units with externally connected depending on project
FAULT door/damper.
inputs device (for example, specific function.
a door or a damper).
External load is Check the cable and the external
missing. load.
Loop I/O A supervised unit
Major or Minor fault
POSITION units with (for example, a door
137 Check for abnormal conditions. depending on project
FAULT specific or damper) is in the
specific function.
IDs wrong position.
• Major fault if no
short circuit
isolators on the
A short circuit in the
CM 4.3 loop.
detector loop cable
CM 2.2 Locate the short circuit.
or conventional • Major fault if loop
I/O M 70
LOOP SHORT zone. with short circuit
138 but not for
CIRCUIT
non-affected areas.
Loop unit
with short A short circuit in the
Locate the short circuit. Major fault.
circuit detector loop cable.
isolator
short circuit
isolators on the
Short circuit on the loop.
LOOP A SHORT
139 Loop M X A-side of a detector Locate the short circuit.
CIRCUIT • Major fault if loop
loop.
with short circuit
but not for
non-affected areas.

Unit or
Module
short circuit
isolators on the
Short circuit on the loop.
LOOP B SHORT
140 Loop M X B-side of a detector Locate the short circuit.
CIRCUIT • Major fault if loop
loop.
with short circuit
but not for
non-affected areas.
• Minor fault if in no
combination with
A cable break on the
other faults.
CABLE BREAK positive conductor
141 Loop M X Locate the cable break.
POSITIVE on the Loop M X • Major fault if in
has been detected. combination with
other faults.
combination with
A cable break on the
other faults.
CABLE BREAK negative conductor
142 Loop M X Locate the cable break.
NEGATIVE on the Loop M X • Major fault if in
has been detected. combination with
other faults.
1. Check the connection

between the module and the
CM 4.3 A serial protocol has other end connected via the
CM 2.2 communication serial protocol.
CM X problems.
2. Contact an authorized service • Minor fault if in no
COMMUNICATI office. combination with
ON ERROR other faults
Explanation: The Faulty loop unit. Replace the loop unit.
143 • Major fault if in
communication 1. Locate interference source.
Interference on loop combination with
with a loop unit is
cable or loop unit 2. If not possible to solve the other faults i.e.
deficient.
from external problem, contact an Fault 128.
Loop units
source. authorized service office.
There are two loop 1. Check address of the units.

units with the same
address on the loop.
The type of loop
1. Change configuration.
unit found in the
loop is different 2. Contact an authorized service
LOOP UNIT from the original office.
144 TYPE Loop units type configured. Major fault.
CHANGED A loop unit has been
1. Check address of the units.
incorrectly
addressed during a 2. Rescan or restart the loop.
replacement.

Unit or
Module
UNKNOWN The Loop M X
TYPE OF LOOP cannot identify the
Replace the unit.
UNIT FOUND type of the affected
Explanation: The loop unit.
145 type of loop unit Loop units Major fault.
found is not Wrong type of 1. Install the correct type.
corresponding to detector has been
the configuration 2. Rescan or restart the loop.
installed.
file.
A timer loop unit Major or Minor fault
Loop based
146 TIMER STUCK has been active for Check the status of the loop unit. depending on project
timers
more than 12 hours. specific function.
CM 4.3 Short circuit has
CM 2.2 1. Locate the short circuit.
been detected on an
I/O M 70 output to the 2. Reset the fault.
SHORT I/O M 700 affected module.
149 Major fault.
CIRCUIT Short circuit has
been detected on Locate the short circuit on the
Loop units
external cabling to external cabling to the loop unit.
the loop unit.
Loop I/O 1. Open the valve.
External equipment Major or Minor fault
units with
150 VALVE CLOSED indicates that the 2. Contact an authorized service depending on project
specific
valve is closed. office. specific function.
IDs
1. Check the address of the
system module.
The affected system
System module is not in the 2. Check the system
modules system configuration file.
configuration file. 3. Contact an authorized service
office.
PRESENT NOT
152 Minor fault.
CONFIGURED 1. Check the address of the loop
unit.
The affected loop
unit is not in the 2. Check the system
Loop units configuration file.
system
configuration file. 3. Contact an authorized service
office.
There is an earth
Charger M
fault on the positive Locate the earth fault.
Loop M X
conductor.
EARTH FAULT A power loop unit
155 Minor fault.
POSITIVE has detected an earth Locate the earth fault on the
Loop units fault on the positive external power supply to the
conductor from the loop unit.
power supply.

Unit or
Module
There is an earth
Charger M
fault on the negative Locate the earth fault.
Loop M X
conductor.
EARTH FAULT A power loop unit
156 Minor fault.
NEGATIVE has detected an earth Locate the earth fault on the
Loop units fault on the negative external power supply to the
conductor from the loop unit.
power supply.
ChangeOv A fuse has been
Replace the fuse.
er M Ext blown.
157 FUSE FAULT Minor fault.
A fuse in a power Contact an authorized service
Loop unit
loop unit has blown. office.
A battery fuse has
been blown, or a
Charger M Replace fuse or restore the cable.
cable to the battery
BATTERY is broken. Major or Minor fault
158 CABLE/FUSE 1. Check the connection to the depending on project
FAULT There is a problem specific function.
battery.
with the battery
Loop units
connected to the 2. Consider replacing the
power loop unit. battery.
CM 4.3
CM 2.2
RM 4.3 A cable break or
Charger M short circuit has Restore the cable.
CABLE I/O M 70 been detected.
159 BREAK/SHORT I/O M 700 Major fault.
CIRCUIT Loop M X
• Check the end of line
Loop I/O Input on a loop unit
component.
units with has an cable break
inputs or short circuit. • Locate the cable break.
Too high current on

I/O M 700 Check external load.
the output.
Too high current on Contact an authorized service
CABLE Loop M X
160 the loop line. office. Major fault.
OVERLOAD
The loop unit is
Loop units reporting too high Check external load.
current.
1. Check the connection
There is a problem between the loop unit and the
with the power power supply.
161 POWER FAULT Loop units depending on project
supply to the power
2. Contact an authorized service specific function.
loop unit.
office
Charger M
ChangeOv Emergency power Major or Minor fault
EMERGENCY Check the emergency power
162 depending on project
POWER FAULT er M Ext has been lost. supply.
specific function.
Loop units

Unit or
Module
The battery charger
BATTERY (Charger M) is The battery charger (Charger M)
164 Charger M Minor fault.
CHARGER unable to charge the is unable to charge the battery.
battery.
EXTERNAL
CM 4.3
FAULT
CM 2.2
Can be generated Major or minor fault.
RM 4.3 External equipment
165 by customized Check the external equipment. See project specific
Charger M is indicating a fault.
defined fault. See system description.
I/O M 70
Custom text for the
I/O M 700
particular fault.
CHECKSUM
EEP
The booting
Only applicable
sequence was not
167 for a redundant Loop M X Rescan or restart the loop. Minor fault.
completed in a
controlled loop
correct way.
with two Loop M X
modules
If restarts happen repeatedly
System The module has
168 RESTARTED without known reason, contact Minor fault.
modules restarted.
an authorized service office.
The module has
1. Restart the module.
been in the
TOO LONG System
169 validating or 2. Contact an authorized service Minor fault.
BOOT TIME modules
configuring states office.
for too long.
CM 4.3 There is too high
EXTERNAL Check the load and reduce if
170 CM 2.2 external load on a Major fault.
LOAD possible.
I/O M 70 conventional zone.
EXTERNAL CM 4.3 Unexpected voltage
171 POWER CM 2.2 detected in a Located and remove the source. Major fault.
SOURCE I/O M 70 conventional zone.
1. Measure the voltage from the
power source.
Low voltage on the module.
primary 28VDC
LOW POWER • If voltage NOT OK,
172 Charger M power supply to the Major fault.
SUPPLY PSU 1 change or adjust the
internal system
DC/DC.
modules.
2. Contact an authorized service
office.

Unit or
Module
power source. • Minor fault if power
• If voltage OK, change sources are
Low voltage on the module. redundant and not
secondary 28VDC from the same
LOW POWER • If voltage NOT OK,
173 Charger M power supply to the source.
SUPPLY PSU 2 change or adjust the
internal system
DC/DC. • Major fault if power
modules.
from the same
2. Contact an authorized service power source.
office.

power source.
module.
The incoming 24
LOW POWER
VDC supply to the • If voltage NOT OK,
175 SUPPLY Loop M X Major fault.
internal circuit change or adjust the
OPERATING
boards is too low. DC/DC.

office.
The configuration
file is corrupt. 1. Download the configuration
file again.
An error has
occurred during 2. Contact an authorized service
downloading of the office.
CM 4.3
SYSTEM configuration file.
CM 2.2
176 CONFIGURATI Open configuration file in the Major fault.
CM X
ON FAULT The configuration correct version of CCPConf and
RM 4.3
file is saved in an resave the configuration file.
incompatible Which version of CCPConf used
version of the depends on the version of the
CCPConf. firmwares installed in the CCP
modules.
Loop I/O
External equipment Major or Minor fault
LOW units with Check the pressure on the
177 indicates low depending on project
PRESSURE specific supervised unit.
pressure. specific function.
IDs
Charger M
The main power
180 MAINS POWER ChangeOv Check the main power supply. Major fault.
supply is lost.
er M Ext

Unit or
Module
The connection
between the main
processor and the
CM 4.3
processor handling
the keyboard input
has been lost.
The module is
leaking power. The
INTERNAL Charger M supply and Contact an authorized service
181 Major fault.
FAULT consumption differ office.
greatly.
The Loop M X has
failed to schedule a
loop unit it
Loop M X considers to be in
working condition
for more than 30
minutes.
combination with
The module has
NO ANSWER other faults.
System stopped answering Contact an authorized service
183 CH 1
modules on channel 1 on the office. • Major fault if in
BACKBONE
backbone bus. combination with
other faults.
combination with
The module has
NO ANSWER other faults.
System stopped answering Contact an authorized service
184 CH 2
modules on channel 2 on the office. • Major fault if in
BACKBONE
backbone bus. combination with
other faults.
The module hasn’t

CM 4.3 received any
NO POLL CM 2.2 communication Check system status for the
185 Major fault.
FROM MASTER CM X from the backbone configured master.
RM 4.3 master in the last 30
seconds.
A short circuit or
cable break has been Check the line or device
188 CABLE FAULT Loop units depending on project
detected on an I/O connected to the I/O port.
specific function.
port on a loop unit.
The protocol version
The fault is resettable once all
of a module (slave
incompatible modules have
INCOMPATIBL System and/or controller) is
196 reported a compatible version. Major fault.
E MODULES modules not compatible with
Alternatively they must be
the central master
removed or disabled.
version.
The type of loop
WRONG TYPE 1. Change the loop unit.
unit found is
209 OF LOOP UNIT Loop units Minor fault.
different from the 2. Rescan or restart the loop.
FOUND
type configured.

Unit or
Module
CM 4.3
CAUSE/EFFECT Fault detected in the Contact an authorized service
210 CM 2.2 Major fault.
ERROR configuration file. office.
CM X
The system fails to
SYNCHRONISA System Contact an authorized service
212 synchronize with the Major fault.
TION SIGNAL modules office.
affected module.
The configuration
file in the system is Synchronise the configuration
not the same in all file between all panel.
CM 4.3 modules.
CM 2.2 Central X Module Y
CM X settings in
CONFIG NOT RM 4.3 configuration file Check configuration and
213 SYNCHRONIZE Major fault.
compared to DIP-settings.
D
DIP-settings are not
OK.
The DIP-settings of
the Charger M are Check configuration and
Charger M
incorrect compared DIP-settings.
to configuration file.
The Charger M is
delivering a higher
current than the
maximum allowed
current limit to the
CURRENT affected Bus/Output. 1. Check the number of
modules configured.
214 LIMIT Charger M The Charger M is Major fault.
EXCEEDED consuming a higher 2. Check the external load.
current than the
maximum allowed
current limit from
the affected
PSU/Battery.
The battery
connected to the
CHARGING
affected Charger M Charge the battery with an
215 CURRENT Charger M Major fault.
is charged with a external charger.
EXCEEDED
higher current than
allowed.
The firmware in a 1. Try to reset the fault.
Charger M
module does not 2. If not possible to reset try to
ChangeOv
comply with the update firmware again.
er M Ext
INCOMPATIBL modules hardware (Might demand for system
216 I/O M 70 Major fault.
E FIRMWARE version. reboot.)
I/O M 700
The fault might
Mux M 16 3. Contact an authorized service
occur during
Relay M 8 office.
firmware update.

Unit or
Module
power source.
The voltage module.
delivered from PSU
HIGH • If voltage NOT OK,
217 Charger M 1 to the affected Major fault.
VOLTAGE PSU 1 change or adjust the
Charger M module
DC/DC.
is too high.
office.

power source. • Minor fault if power
• If voltage OK, change sources are
The voltage module. redundant and not
delivered from PSU from the same
HIGH • If voltage NOT OK,
218 Charger M 2 to the affected source.
VOLTAGE PSU 2 change or adjust the
Charger M module
DC/DC. • Major fault if power
is too high.
from the same
2. Contact an authorized service power source.
office.
1. Check the fuse.

• If fuse OK, change
module.
The fuse protecting • If fuse NOT OK, change
FUSE FAULT
219 Charger M the PSU 1 voltage the fuse (or change the Major fault.
PSU 1
input is broken. module if LRU).

office.
1. Check the fuse.

• Minor fault if power
• If fuse OK, change
sources are
module.
redundant and not
The fuse protecting • If fuse NOT OK, change from the same
FUSE FAULT
220 Charger M the PSU 2 voltage the fuse (or change the source.
PSU 2
input is broken. module if LRU).
• Major fault if power
from the same
power source.
office.
A PSU is connected 1. Check the electrical

to the PSU 1 input connections according to the
on the affected drawings.
PSU1 PRESENT Charger M module,
2. Check the configuration file.
221 NOT Charger M but the Charger M Minor fault.
CONFIGURED module is not 3. Contact an authorized service
configured to have a office.
PSU connected to
PSU 1 input.

Unit or
Module
A PSU is connected 1. Check the electrical
to the PSU 2 input connections according to the
on the affected drawings.
PSU2 PRESENT Charger M module,
2. Check the configuration file.
222 NOT Charger M but the Charger M Minor fault.
CONFIGURED module is not 3. Contact an authorized service
configured to have a office.
PSU connected to
PSU 2 input.
The voltage level
internally in the
Charger M is at least
1 volt below the
voltage delivered
from the PSUs.
INTERNAL Contact an authorized service
223 Charger M Without battery Major fault.
VOLTAGE LOW office.
charge, the system
shuts down at 18.5
VDC. With battery
charge, the system
shuts down at 21
VDC.
The voltage level
internally in the
Charger M is at least
1 volt above the
voltage delivered
INTERNAL from the PSU:s.
Contact an authorized service
224 VOLTAGE Charger M Without battery Major fault.
office.
HIGH charge, the system
starts up at 20.0
VDC. With battery
charge, the system
starts up at 25.5
VDC.
CM 4.3
CM 2.2
When the affected
CM X
module measures 1. Check backbone signals for
Charger M
the X-Fire signal in cable breaks.
ChangeOv
225 XFIRE SIGNAL the backbone, the Major fault.
er M Ext 2. Contact an authorized service
voltage level of the
I/O M 70 office.
signal is below 4
I/O M 700
volts.
Loop M X
Relay M 8
No activity has been
• Minor fault if
registered on the 1. Check the electrical
communication is
primary system bus connections according to the
CM 4.3 redundant.
PRIMARY within 30 seconds drawings.
226 CM 2.2
SYSTEM BUS by the master • Major fault if
CM X 2. Contact an authorized service
(module with communication is
office.
address 1) in the not redundant.
affected central.

Unit or
Module
No activity has been
• Minor fault if
registered on the 1. Check the electrical
communication is
secondary system connections according to the
CM 4.3 redundant.
SECONDARY bus within 30 drawings.
227 CM 2.2
SYSTEM BUS seconds by the slave • Major fault if
CM X 2. Contact an authorized service
(module with communication is
office.
address 2) in the not redundant.
affected central.
1. Check the electrical
The affected module connections according to the
has not responded drawings.
CM 4.3
NO ANSWER within 30 seconds
228 CM 2.2 2. Replace the module. Major fault.
SYSTEM BUS on
CM X
primary/secondary 3. Contact an authorized service
system bus. office.
1. Check cabinet and battery

temperature.
The battery or
229 OVERHEATED Charger M Charger M is too 2. Check the battery condition. Major fault.
hot. 3. Contact an authorized service
office.
CM 4.3 1. Measure the voltage from the

CM 2.2 power source.
CM X • If voltage OK, change
RM 4.3 module.
Too low voltage
LOW VOLTAGE ChangeOv
detected on the • If voltage NOT OK,
230 CH 1 er M Ext Major fault.
backbone bus power change or adjust the
BACKBONE I/O M 70
supply, channel 1. DC/DC.
I/O M 700
Loop M X
Mux M 16
office.
Relay M 8
CM 4.3 1. Measure the voltage from the
CM 2.2 power source.
CM X • If voltage OK, change
RM 4.3 module.
Too low voltage
LOW VOLTAGE ChangeOv
detected on the • If voltage NOT OK,
231 CH 2 er M Ext Major fault.
backbone bus power change or adjust the
BACKBONE I/O M 70
supply, channel 2. DC/DC.
I/O M 700
Loop M X
Mux M 16
office.
Relay M 8

Unit or
Module
The bootloader in 1. Try to reset the fault.
the affected module 2. If not possible to reset try to
Charger M cannot start the update firmware again.
ChangeOv application due to a (Might demand for system
er M Ext corrupted firmware. reboot.)
INVALID I/O M 70 This fault might
232 occur during a 3. Contact an authorized service Major fault.
APPLICATION I/O M 700
firmware upgrade. office.
Loop M X
Mux M 16
The module has a The fault is resettable once the
Relay M 8
higher protocol module is downgraded.
version than the
central master.
A relay is broken or
in a state that
damages the relay.
233 RELAY Relay M 8 Replace the module. Major fault.
(The voltage over
the relay coil is too
high.)
The affected module 1. Check for cable breaks on
NO ANSWER is not answering on the extension bus. Major or Minor fault
RM 4.3
234 EXTENSION the extension bus depending on project
MN400 2. Contact an authorized service
BUS where it is specific function.
office.
connected.
1. Check the address of the
The type of module module according to
WRONG TYPE
System found is different electrical drawings.
236 OF MODULE Major fault.
modules from the type
FOUND 2. Contact an authorized service
configured.
office.
Check the power supply to the

aspiration detector. (Green
control LED inside aspiration
box shall be lit when power
No external power OK.)
to the aspiration • If voltage OK and Fan not
(ASP) unit. running, see "Fan broken"
below.
• If voltage NOT OK, change
Aspirating or adjust the DC/DC.
238 FLOW FAULT smoke Major fault.
detector The fan in an
aspiration detector Check in the aspiration box if a
does not work red LED is lit at the same time
correctly. as the green.
(Fault generated by • If yes, change the aspiration
the Loop M X). box.
NOTE: Critical
• If no, change the smoke
error which can
detector inside the aspiration
cause the detector to
box.
not detect a fire
alarm.

Unit or
Module
The voltage level of
the GA signal in the
backbone is below 4
CM 4.3 volts.
CM 2.2 (Fault generated by 1. Check that Charger M puts
CM X modules which have out a monitoring voltage on
RM 4.3 GA-morse the backbone
239 GA FAULT Major fault.
Charger M configured for any
I/O M 70 of its outputs)
office.
I/O M 700 NOTE: Critical
Relay M 8 error which can
cause the GA
functionality from
working.
A write operation
DEVICE WRITE into the loop unit’s
241 Loop units Replace the loop unit. depending on project
FAULT internal EEPROM
specific function.
memory failed.
CM 4.3 The system has not
Contact an authorized service
242 SERVICE TIME CM 2.2 been serviced for a Major fault.
office.
CM X period of time.
System
modules Internal system Contact an authorized service
255 ILLEGAL Major fault.
error. office.
Loop units

Service & Maintenance Manual 13 Appendix - Definitions and Abbreviations
13 Appendix - Definitions and

Abbreviations

13 Appendix - Definitions and Abbreviations Service & Maintenance Manual
13.1 Definitions and Abbreviations

Definitions and abbreviations for the fire detection system.
Active high By active high it means that the output is normally not energized in normal condition
and when system is not energized. By active high on input it means that the input is
normally not energized. This is the NO contact on a relay.
Active low By active low it means that the output is normally energized in normal condition and
system running. By active low on input it means that the input is normally energized.
This is the NC contact on a relay.
Alarm condition The state of the system when a fire or gas has been 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, for example audible and optical alarms like
bells, sirens and flashlights.
Alarm Transfer Output A supervised output for signalling that a fire has occurred. The Alarm Transfer Output
is usually used in onshore systems for alerting the fire brigade.
APF Application Program File.
Application program file A file holding the application parameters for the FDS.
ASP detector Aspiration detector.
Backbone Bus External The main bus outside a central cabinet used for communication between modules and
(BBE) stretched central parts. It consists of two redundant RS485 channels, two 24 VDC
power lines and the Basic Backup (BBU) signal and Synchronisation Signal (SYNC).
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 (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 (BBU) A signal in the Backbone bus that is used for transmitting the central's alarm status.
The signal is only used when a module in managed mode loses communication with its
controller module.
BER Bit Error Rate
BusCon M 20 A Bus Connector with 20 connectors in the flat-cable. This unit is used to connect the
Control M 4.3 to the backbone bus and also has the common fire and fault outputs.
Cause/Effect The Cause/Effect program defines how the inputs and outputs of the system should act.
CCP Consilium Common Platform. General modules which create a system for Consilium
products.
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.
Charger M The Charger Module. Can connect two PSU’s and a battery and feeds the power
channels on the backbone bus.

Compact central Central cabinet including basic functionality of Fire 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.
Configuration File A file holding the configurable parameters for the FDS.
Control module The Control M 4.3, 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 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
within a central. Control modules can also be in managed mode, that is 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.
Control M 2.2 A Control Panel with a 2.2” graphical colour display used to manage and supervise a
system.
Control M 4.3 Control Module with a 4.3” display, a keyboard and all the mandatory indications
required to comply with EN 54.
Control M X Control Module, a control module without a display, keyboard or mandatory
indications.
CR It is a heat detector class. The C means fixed alarm temperature at 84ºC. The R means
it also gives alarm for RoR.
CS Heat detector classification in EN 54-7; ‘C’ class indicates a static response
temperature of 84°C and ‘S’ that the detector will not respond below 80°C.
DCS Distributed Central System (see also Stretched central).
Detector A device capable of detecting smoke, heat, flames or gas.
DIP switch Dual in-line package switch. Used to set address etc. on loop units and modules.
Disablement Disablement of devices such as a Zones or Detectors. Alarms from disabled devices
will be inhibited.
EMC Electromagnetic Compatibility.
EMI Electromagnetic Interference.
EN 54 The European product standard for fire detection and fire alarm systems.
ESD System Emergency Shut Down System, embedded system taking care of safety procedures in
case of emergency, for example shut down of fire doors, ventilation etc.
Ex Ex can mean different things depending on when it is mentioned. Examples: ‘Ex
proof’ means ‘Explosion Proof’, ‘Ex area’ means ‘Hazardous Area’ which is an area
where the atmosphere might be explosive. ‘Ex certified’ means both ATEX and IECEx
certification.
Ex-classification The protection type used in a hazardous area; e.g. Ex d.
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 Communication to external entities is called external communication, using for
example MODBUS, NMEA or TCMS protocols.
External control Outputs used to control external equipment, for example fire doors.
Fault condition The state of the system when a fault is detected.

FDS Fire Detection System.

Firmware Embedded software.
FSK Frequency Shift Keying.
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.
GA General Alarm, common activation of alarm devices and activation of the PA system.
GDS Gas Detection System.
GRP Glass-Reinforced Plastic.
Heavy duty manual call point A heavy duty manual call point is made of GRP, metal or similar material and it has a
high level of corrosion resistance.
Hot Standby mode Controller modules in Hot Standby mode can take over the responsibilities of the
Controller module managing a central.
I/O Input/output.
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 (24 VDC/70 mA)
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 (24 VDC/700 mA)
I/O Module A module with inputs and/or outputs. I/O modules always run in Managed mode, that
is 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.
IDA The IDA communication protocol.
Inter-central communication Communication between centrals is called inter-central communication.
Interface channel A communication channel used to interface the systems with external devices.
Interface channels can be configured to communicate on different protocols.
Internal power supply Output power from PSU.
Intra-central communication Communication within a central is called intra-central communication. This
communication is between modules.
IP Ingress Protection - rating used to specify the environmental protection (enclosure) of
electrical equipment.
IS Intrinsically Safe.
Isolator M Isolator Module; used to distribute a part of a FDS.
ISS Integrated Safety System.
Loop The same as a loop-line.
Loop cable A cable which the FDS uses to power and communicate with the loop units. The loop
begins and ends in the loop module in the FDS.

Loop module The piece of hardware within the FDS which powers and communicates with the loop
units connected to its loop-line.
Loop unit Fire detectors, gas detectors, manual call points and other devices that can be
connected to the Loop.
Loop-line A common name for the cable, loop devices and other equipment connected to a loop
module.
Loop-line IS A part of the loop-line protected by a galvanic isolator.
LRU A Line-Replaceable Unit (LRU) is a modular component that is designed to be
replaced quickly at an operating location.
Managed mode The opposite of Controller mode. All modules that are managed by a Controller
module are in Managed mode.
MCP Manual Call Point.
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, where it 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.
N/A Not Applicable.
OEM Original Equipment Manufacturer.
PA Public Addressing.
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 like a smouldering fire.
Programmable output Output which signal behaviour is configurable via the Configuration program.
PSU Power Supply Unit.
Rate of Rise Rate of Rise functionality by using C/E commands for setting of a different alarm
threshold and temperature rise threshold for heat detectors.
Redundancy Refers to the quality or state of being redundant, that is exceeding what is necessary or
normal. In the system the term is used to describe backup functionality like in Hot
Standby Controller modules.
Redundant loop Redundant loop means loop module redundancy on one single loop-line between two
loop 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.

RS-485 Serial communication interface used for external communication and BackBone bus.
Is a standard defining the electrical characteristics of drivers and receivers for use in
balanced digital multipoint systems.
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.
Salwico Language A text based interpreting language for making logical cause effect expressions
developed by Consilium.
SCI Short Circuit Isolator.
SCM Software Configuration Management.
SCS Single Central System.
SMig system Salwico Safety Management interactive graphics, a PC-based software package
providing graphical presentation and control of the system.
Spur Branch from a loop-line without return.
Stretched central (DCS) A central that is physically distributed to two or more physical locations. One location
may or may not supply power to another location (segmented) and two locations may
or may not have isolated communication lines.
Sub-loop It is possible to connect sub-loop units to some loop units using a sub-loop cable. The
cable is however not a loop. One end is connected to the loop unit and the other end is
connected to the sub-loop unit.
Sub-loop unit A device which cannot be connected directly to the loop. A sub-loop unit can be a
switch or a relay contact will be used to send a fire or fault alarm to the FDS.
Synchronization signal A signal in the Backbone bus that is used for transmitting synchronization signal used
by system modules to synchronize there behaviour.
System A system consists of a number of loop units and 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.
TBD To Be Done, To Be Decided/Determined.
Terminal A Terminal is a physical point of connection, compare I/O pin.
Test condition Detectors put in the Test condition (or test mode) are inhibited from generating the
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, for example in case of a lightly contaminated
detector.
Zone A group of detectors located in a geographical area.


Index
Index
A H
Add loop unit screen, Service menu ...................... 31 Heat detector, Cleaning.......................................... 17
Heat detectors, Testing........................................... 9
B
Backup service pack to USB memory, Service I
menu....................................................................... 33 I/O M 70................................................................. 49
Basic Backup Signal .............................................. 57 I/O M 70, Connection to ........................................ 5
Batteries, Replacing ............................................... 19 I/O M 700............................................................... 49
Battery fault, Test fault conditions......................... 10 Input list, Service menu ......................................... 33
BBU ....................................................................... 57
BIOS, Upgrade for a CCP System......................... 35 L
BIOS, Upgrade in a control module via Ethernet .. 36
Load configuration from USB memory screen,
Bus Isolator M........................................................ 49
Service menu.......................................................... 32
Load service pack from USB memory, Service
C menu....................................................................... 33
Central details screen, Service menu ..................... 26 Loop M X............................................................... 49
Central main screen, Service menu........................ 26 Loop cable break, Test fault conditions ................. 11
Central unit terminal layout with cabling .............. 50 Loop details screen, Service menu......................... 30
Change Over M Ext ............................................... 49 Loop main screen, Service menu ........................... 29
Charger M .............................................................. 49 Loop units screen, Service menu ........................... 30
Control M 2.2......................................................... 49
Control M 4.3......................................................... 49 M
Control M X........................................................... 49
Module details screen, Service menu..................... 27
Control panel display, Testing................................ 11
Module inputs screen, Service menu ..................... 28
Control panels, Electrical installation .................... 5
Module main screen, Service menu ....................... 27
Module outputs screen, Service menu ................... 28
D Muting faults, Troubleshooting.............................. 13
Disablement list ..................................................... 10
Download firmware to modules, Service menu..... 33 O
Download system log file ...................................... 14
Output list, Service menu....................................... 33
Download configuration file .................................. 21

E P
Power supply, Test fault conditions ....................... 11
Earth fault, Test fault conditions ............................ 11
Protocols, Remove in a Control M X .................... 23
Earth fault, Troubleshooting .................................. 12
Protocols, Update for a Control M X..................... 23
PSU M AC/DC 5A ................................................ 49
F
Fault list ................................................................. 13 R
Fault report............................................................. 14
Reboot system screen, Service menu..................... 32
Fault list ................................................................. 13
Relay M 8............................................................... 49
Fire detection system, System description............. 3
Reload configuration/Reboot this module screen,
Fire history list ....................................................... 7
Service menu.......................................................... 32
Fire detection system, System data........................ 4
Remove configuration screen, Service menu......... 32
Firmware screen, Service menu............................. 33
Removed detector fault, Test fault conditions ....... 10
Firmware Update Tool, Troubleshooting............... 44
Repeater M 4.3....................................................... 49
Firmware, Upgrade from microSD card ................ 40
Report a fault.......................................................... 14
Firmware, Upgrade from USB stick ...................... 37
Reset faults, Troubleshooting ................................ 13
Firmware, Upgrade in a control module via
Reset test mode ...................................................... 10
Ethernet .................................................................. 42
RS485 Termination ................................................ 53
Flame detector, Cleaning ....................................... 17
RS485, Application examples for installation ....... 53
Flame detectors, Testing ........................................ 9


Index
S Zone main screen, Service menu ........................... 28

Save changes to configuration screen, Service Zone, text mode ..................................................... 7
menu....................................................................... 32
Save configuration to USB memory screen,
Service menu.......................................................... 32
Scan loop screen, Service menu............................. 31
Service menu, Screen details ................................. 25
Smoke detector, Cleaning ...................................... 17
Start automatic update, Service menu.................... 33
Start the Firmware updater tool ............................. 36
Start the Firmware updater tool ............................. 42
Stop automatic update, Service menu.................... 33
Surge Prot M .......................................................... 49
Synchronise system configuration screen, Service
menu....................................................................... 32
System log files...................................................... 14
System log, Service menu...................................... 33
System details screen, Service menu ..................... 25
System modules, Description................................. 49

T
Terminal layout, Electrical installation .................. 4
Test Equipment ...................................................... 8
Test for earth failure............................................... 11
Test for earth failure............................................... 13
Test mode overview ............................................... 7
Test the control panel display ................................ 11
Testing a fire-detecting zone .................................. 7

U
Upgrade BIOS in Control M 4.3, Repeater M 4.3
or Control M 2.2 from USB .................................. 35
Upgrade BIOS in Control M X with USB port...... 35
Upgrade BIOS in Control M X without USB port 36
Upgrade firmware in Control M 4.3, Repeater M
4.3 or Control M 2.2 from USB............................. 37
Upgrade firmware in Control M X with USB port 37
Upgrade firmware in Control M X without USB
port ......................................................................... 37
Upgrade firmware in Control M4.3 or Control
M2.2 from microSD card....................................... 40
Upgrade firmware in remaining CCP modules...... 37
Upgrade for control modules i large systems ........ 45
Upgrade modules in the following order in large
systems................................................................... 46
Upgrade strategy large systems ............................. 45
Upload syslog to USB memory, Service menu...... 33
Upload configuration file....................................... 21

X
X-Fire..................................................................... 56

Z
Zone details screen, Service menu......................... 29
Zone loop units screen, Service menu ................... 29

FOR ALL THOSE MOMENTS
WHEN SAFETY MATTERS
Consilium is a producer of safety and safety-related technologies for the marine, oil and gas,
transport and building sectors. Our commitment goes beyond the products: We protect the
lives of mothers and fathers, sisters and brothers, colleagues and friends. With representation in
more than 25 countries in all time zones, we are always close to you.
www.consilium.se

5100334-02 - Salwico Cargo Conventional - Service & Maintenance Manual - M - EN - 2018 - T

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

5100334-02 - Salwico Cargo Conventional - Service & Maintenance Manual - M - EN - 2018 - T

Uploaded by

Copyright:

Available Formats

Salwico Cargo

© Copyright 2018, Consilium Marine & Safety AB

2 General Description .......................................................................... 3

3.3 Reset Test Mode................................................................................. 10

3.5 Test the Control Panel Display ......................................................... 11

4 Cleaning of Fire Detectors ............................................................... 17

4.2 Smoke Detector ................................................................................. 17

5 Replacing Batteries ........................................................................... 19

6 System Configuration ....................................................................... 21

7 Using the Service Menu.................................................................... 25

8.2 Upgrade Firmware............................................................................ 37

8.3 Upgrading Large Systems................................................................. 45

9 Appendix - Central Unit Terminal & Cabling Layout..................... 49

10 Appendix - Termination .................................................................... 53

10.2 Additional Information for BBU Termination................................. 56

11 Appendix - System Software Updater............................................... 61

12 Appendix - Fault Code List............................................................... 69

13 Appendix - Definitions and Abbreviations....................................... 85

1.1 About this Manual

Figure 1. Salwico Cargo Fire Detection System, an example.

1.2 Symbols used in the manual

5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T 1

2 5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T

2.1 System Description

2.2 System Block Diagram

Figure 2. An example of a system block diagram.

5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T 3

2.3 System data (EN 54)

2.4 Electrical Installation, Central Equipment

4 5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T

2.5 Example of a Detector Zone

Figure 3. Example of a detector zone with conventional non-addressable loop units.

A zone should in any case include no more than 50 enclosed spaces.

5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T 5

6 5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T

3.1 Test Mode Overview

When a zone is in test mode:

3.2 Testing Fire-Detecting Zones

5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T 7

3.2.2 Simulate a fire alarm in the system

1 Add a disablement for a selected loop unit

3.2.3 Recommended Test Equipment

3.2.4 Heat Detectors

8 5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T

3.2.5 Smoke Detectors

1 Spray test gas on the detector for 0.5

3.2.6 Flame Detectors

5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T 9

3.3 Reset Test Mode

To reset test mode:

3.4 Test Fault Conditions

It is possible to test fault alarm indications by following the procedures below:

3.4.2 Removed Detector Fault

3.4.3 Battery Fault

10 5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T

3.4.4 Earth Fault

3.4.5 Loop Cable Break

3.4.6 Power Supply

1 Remove the main power supply.

3.4.7 Test the Loop Cable

3.4.7.2 Test for Earth Failure

3.5 Test the Control Panel Display

5100334-02_Salwico Cargo Conventional_Service & Maintenance Manual_M_EN_2018_T 11