2.0 Alarm menu ......................................................................................................................................................................................................................................... 2
2.1 List of alarms ..................................................................................................................................................................................................................................... 2
2.3 Selecting Status ............................................................................................................................................................................................................................... 2
2.4 Specifying Event Text ..................................................................................................................................................................................................................... 3
2.6 Selecting Place ................................................................................................................................................................................................................................. 3
2.7 Selecting Object Number .............................................................................................................................................................................................................3
2.8 Sorting the list of alarms ...............................................................................................................................................................................................................3
2.9 Alarm on sensors ............................................................................................................................................................................................................................. 4
2.10 ECL System Alarms .......................................................................................................................................................................................................................6
2.11 OPR10 System Alarms .................................................................................................................................................................................................................7
2.12 Communication alarms ..............................................................................................................................................................................................................8
2.13 M-bus meter alarms ..................................................................................................................................................................................................................... 8
By clicking on the Alarms menu a list of alarms will be shown.
The contents in the list of alarms depend on the selected filtering
criteria. These criteria are Priority, Status, Event text, Source and
Place. Each of these criteria is explained below.
It is possible to see the priority, time stamp, customer name and
controller ID, place, object number, event text, status and accept
status. Each of these information is explained below.
The buttons on the lower right side of the window makes it possible to show History of alarms for a specific period of time or to
quickly Accept All alarms in the list. The list can also be exported to
a CSV file.
2.2 Selecting Priority
Figur 1 shows the Alarms window accessible via the Alarms menu.
The alarms which can be generated by DECS 2.0 each have a predefined priority. In this way the alarms can i.e. be filtered to have
only the highest priority alarms (1 – 601) shown in the list.
By selecting a Priority in the dropdown list then only alarms with
that priority or higher will be shown in the list.
Alarms of highest priority are defined as ‘1 – 601’ and lowest priority as ‘5 – 201’.
The predefined priority of each alarm is shown in the lists of supported alarms.
2.3 Selecting Status
When an alarm is triggered then the status of that alarm will be set
to On. This happens when the trigger condition for that alarm is
fulfilled, i.e. a sensor is disconnected.
If or when the trigger condition for that alarm is no longer fulfilled
then the status of that alarm will be set to Off, i.e. if the sensor is
reconnected.
The trigger conditions are described in the lists of supported
alarms.
In the Status dropdown list it is possible to select only to show
alarms with a particular Status in the list. If ‘None’ is selected then
no Status filter is applied.
Figur 2 shows how to select Priority in the filter conditions.
Figur 3 shows how to select Status in the filter conditions.
The other options in the dropdown list provide filter criteria which
depends on both the current status of the alarm (On/Off) and
whether or not the alarm has been accepted by a user (Accepted/
Unaccepted). For example, select ‘On Unaccepted’ to show only
the alarms which are currently On and which have not yet been
accepted by a user. Alternatively, select the ‘On Off Unaccepted’
option to show all unaccepted alarms regardless if Status is On or
Off.
Each alarm supported by DECS 2.0 has a predefined Event Text
which is shown in the ‘Event Text’ column in the list of alarms.
By specifying a filter criteria to be alarms with a specific Event Text
then only alarms which have this Event Text will be shown in the
list.
It is possible to specify all of the Event Text or just the initial part
of the Event Text, i.e. by specifying “Reachability”, then all alarms
starting with that Event Text will be shown. The filter is not casesensitive.
The predefined Event Text of each alarm is shown in the lists of
supported alarms.
2.5 Selecting Source
DECS 2.0 supports ECL Comfort 296 / 310, OPR20 and OPR10 controllers as source of alarms.
By selecting a source as a filter criteria then only the alarms from
that specific source will be shown in the list of alarms. If ‘All’ is
selected then alarms from any of the sources will be shown in the
list.
The alarms supported by each source are shown in the lists of supported alarms.
Figur 4 shows how to specify an Event Text in the filter conditions.
Figur 5 shows how to select a specific Source in the filter conditions.
2.6 Selecting Place
One or more Places can be created in the General Settings available in the Administrator menu.
Each of these places is selectable in the Place dropdown list. Only
the alarms from that specific Place will be shown in the list of
alarms.
Figur 6 shows how to select a specific Place in the filter conditions.
2.7 Selecting Object Number
You can set a filter for the object number to find only the alarms
from that one.
If you want to see the controller overview of a controller, which
have an active or inactive alarm, then you have to click on the
object number of that controller. This is a hyperlink and the system
will jump to the controller overview display of the controller, on
which the alarm appeared.Figur 7 shows how to select object number.
2.8 Sorting the list of alarms
The list of alarms can be sorted ascending or descending based on
any of the columns shown in the list of alarms.
Click on the title of the column to be used for sorting the list. By
clicking the same column again it will be sorted in reversed order.
The column used for sorting is indicated by an arrow-down (descending) or arrow-up (ascending).
AQ173386472022en-010501
Figur 8 shows how to sort the list of alarms.
Place the mouse pointer on a field in the list of alarms to see
the complete contents of that field.
The ECL controller can be configured to monitor one or more sensor inputs and then trigger an alarm if a sensor is short circuited or
disconnected.
It is described in the installation guide for the application key
installed in the ECL controller how to configure it.
To make the ECL controller monitor an input then it must be activated via the Raw Input Overview menu in the controller.
The ECL controller will then show a magnifying glass next to the
sensor input. Only sensor inputs used by the application itself can
be monitored for alarms.
The sensor input has a measuring range from -60 ... 150 ° C. If the
input is exceeding these limits then the alarm is triggered.
The ECL controller can be configured to monitor one or more
system alarms. It is described in the installation guide for the application key installed in the ECL controller how to configure it, i.e.
the Temperature Monitor.
In case a P330 application key is installed then the Flow Temperature Monitor feature in the ECL controller monitors the flow
temperature of the master circuit (PNU 1040) and circuit 1-4 (PNU
1041-1044). However, only the circuits supported by the sub ap-
plication (P330.1-15) are monitored.
It depends on the application key installed in the ECL controller
which types of system alarms are supported. It can be seen in the
installation guide for the application key and/or in the Alarm Overview menu in the ECL controller.
If the conditions for triggering a system alarm are fulfilled, i.e. a
flow temperature exceeds the limits specified in the ECL control-
ler, the Status of that corresponding alarm is set to On. If/when
the conditions for that alarm are no longer fulfilled then the ECL
DECS 2.0 reads the status of the first 5 types of system alarms in
the ECL controller (PNU 1040-1044).
Event TextPrioritySourceTrigger condition
Alarm PNU10402ECLAlarm status goes On if the conditions for the alarm specified in the controller are exceeded. When
the conditions are no longer exceeded the Status automatically switches back to Off. The alarm
conditions are monitored by the controller.
Alarm PNU10412ECLAlarm status goes On if the conditions for the alarm specified in the controller are exceeded. When
the conditions are no longer exceeded the Status automatically switches back to Off. The alarm
conditions are monitored by the controller.
Alarm PNU10422ECLAlarm status goes On if the conditions for the alarm specified in the controller are exceeded. When
the conditions are no longer exceeded the Status automatically switches back to Off. The alarm
conditions are monitored by the controller.
controller automatically cancels the alarm, meaning the Status of
the alarm is set back to Off.
Alarm PNU10432ECLAlarm status goes On if the conditions for the alarm specified in the controller are exceeded. When
the conditions are no longer exceeded the Status automatically switches back to Off. The alarm
conditions are monitored by the controller.
Alarm PNU10442ECLAlarm status goes On if the conditions for the alarm specified in the controller are exceeded. When
the conditions are no longer exceeded the Status automatically switches back to Off. The alarm
conditions are monitored by the controller.
Flow temperature monitor, master circuit
Flow temperature monitor, circuit 1
Flow temperature monitor, circuit 2
Flow temperature monitor, circuit 3
Flow temperature monitor, circuit 4
(Not supported)
Flow temperature monitor, all circuits
(Not supported)
(Not supported)
(Not supported)
(Not supported)
Flow temperature monitor, circuit 1
Flow temperature monitor, circuit 2
(Not supported)
(Not supported)
(Not supported)
Flow temperature monitor, circuit 1
Flow temperature monitor, circuit 2
Flow temperature max monitor, circuit 1
(Not supported)
(Not supported)
Flow temperature monitor, circuit 1
Flow temperature monitor, circuit 2
Flow temperature monitor, circuit 3
(Not supported)
2.11 OPR10 System Alarms
The OPR10 controller can be configured to monitor one or more
system alarms. It is described in the installation guide for the controller how to configure it.
Event TextPrioritySourceTrigger condition
OPR0010 system
alarm (1)
OPR0010 system
alarm (2)
2OPR10Alarm status goes On if the conditions for the alarm specified in the controller are exceeded. When
the conditions are no longer exceeded the Status automatically switches back to Off. The alarm conditions are monitored by the controller.
2OPR10Alarm status goes On if the conditions for the alarm specified in the controller are exceeded. When
the conditions are no longer exceeded the Status automatically switches back to Off. The alarm conditions are monitored by the controller.
If the conditions for triggering a system alarm are fulfilled the Status
of that corresponding alarm is set to On. If/when the conditions for
that alarm are no longer fulfilled then the controller automatically
cancels the alarm, meaning the Status of the alarm is set back to Off.
The communication between DECS 2.0 and the controllers is constantly monitored by DECS 2.0.
If DECS 2.0 cannot reach the controller via the data communication interface, i.e. Modbus-TCP or Modbus-RS485, then it will try
again at next polling cycle. If the controller cannot be reached
after 5 consecutive polling cycles the Reachability status is set to
False and the Communication alarm is triggered.
Event TextPrioritySourceTrigger condition
Reachability of
controller
Date/time controller
(At least 15 minutes
different from server
time)
1ECL
OPR10
OPR20
Alarm status goes On if the controller cannot be reached via the data communication interface after
5 consecutive polling cycles. The reachability of the controller is monitored by DECS 2.0.
2OPR20Alarm status goes On if the time difference between the controller and DECS 2.0 server time is more
than 15 minutes. The time difference is monitored by DECS 2.0.
2.13 M-bus meter alarms
If an m-bus meter is connected to the controller then DECS 2.0 will
monitor if an error is reported by the meter or if the consumption
value read from the meter is corrupt.
In this situation DECS 2.0 will wait 3 hours until it tries to reach the
controller again. If the controller then is reachable again the Communication alarm is set back to Off.
The interval between each polling cycle depends on the amount of
controllers registered to DECS 2.0 as well as the usage of DECS 2.0,
but is typically 15 minutes.
It also depends on the meter what the conditions are for the error
to be triggered. These details must be found in the documentation
for that specific type of meter.
The meters are monitored at each polling cycle. The interval
between each polling cycle depends on the amount of controllers
registered to DECS 2.0 as well as the usage of DECS 2.0, but is typically 15 minutes.
It depends on the meter which types of error it can report to DECS
2.0 and also in which format the error is reported.
The error from the meter is reported to DECS 2.0 as an integer
value. This value is then shown in the list of alarms. Please consult
the documentation for the meter to learn about the conversion between the error shown in the display of the meter and the integer
value reported to DECS 2.0. See examples of errors supported by
Danfoss energy meters on the next page.
Alarm status goes On if heat meter 1 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if heat meter 2 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if heat meter 3 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if heat meter 4 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if heat meter 5 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if heat meter 6 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if heat meter 7 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if heat meter 8 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if heat meter 9 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
ERROR Heatmeter 10 1OPR10
OPR20
ERROR Heatquantity 12ECL, OPR10,
OPR20
ERROR Heatquantity 22ECL, OPR10,
OPR20
ERROR Heatquantity 32ECL, OPR10,
OPR20
ERROR Heatquantity 42ECL, OPR10,
OPR20
ERROR Heatquantity 52ECL, OPR10,
OPR20
ERROR Heatquantity 62OPR10
OPR20
ERROR Heatquantity 72OPR10
OPR20
ERROR Heatquantity 82OPR10
OPR20
Alarm status goes On if heat meter 10 reports a non-zero error code to DECS 2.0. The m-bus
meter alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 1 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 2 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 3 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 4 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 5 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 6 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 7 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 8 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
ERROR Heatquantity 92OPR10
OPR20
ERROR Heatquantity 102OPR10
OPR20
AQ173386472022en-010501
Alarm status goes On if the consumption value read from energy meter 9 is lower than previous readout. The consumption alarm is monitored by DECS 2.0.
Alarm status goes On if the consumption value read from energy meter 10 is lower than
previous readout. The consumption alarm is monitored by DECS 2.0.
Error codes supported by Danfoss energy meters are shown in the
table below.
The figures 0-255 are the possible error codes that can be shown
in DECS. 2.0.
The codes in the grey row and the grey column are the possible
error codes that can be shown in the meter display.
DECS 2.0 shows the error code 146 for a Danfoss heat meter.
Find the figure 146 in the table.
Follow the column vertically to the grey area and you will find E-8.
Hereafter follow the row horizontally to the grey area and you will
find E-7 + E-6.
This means that the error codes E-6, E-7 and E-8 are active in the
heat meter.
You can find an explanation of the possible error codes in the table
on the next page.
-) Temperature range outside [-19,9°C ... 199,9°C]
-) sensor short circuit
-) sensor break
E-3Temperature sensors reversed in hot and cold lines
E-4Hardware error in ultrasonic measurement
-) transducer or control defective
-) short circuit
E-5Reading too frequently
E-6Wrong direction of flow
E-7No meaningful ultrasonic receive signal
-) air in the measuring path
E-8No primary voltage (only if mains unit used)
-) supply via backup battery
E-9Warning: Battery nearly exhausted
C-1Basic parameter error in flash or RAM
2.14 ECL Application Alarms
DECS 2.0 supports application specific alarms for some application
keys, i.e. A333.
The conditions for such alarms to be triggered are specified in the
Administrator menu.
Event TextPrioritySourceTrigger condition
Alarm on Sensor 14
- Pump
Flow temperature too
high
Return temperature
too high
2ECLAlarm status goes On if the specified digital sensor input is High/Active. When the input is Low/Inac-
tive the Status automatically switches back to Off. The alarm conditions are monitored by DECS 2.0.
2ECLAlarm status goes On if the flow temperature is higher than the specified limit. When the flow tem-
perature is below the limit the Status automatically switches back to Off. The alarm conditions are
monitored by DECS 2.0.
2ECLAlarm status goes On if the return temperature is higher than the specified limit. When the flow
temperature is below the limit the Status automatically switches back to Off. The alarm conditions are
monitored by DECS 2.0.
DECS 2.0 monitors the corresponding sensor values and detects
if the specified limits are exceeded. If the limit is exceeded then the
Status of that alarm goes On and switches back to Off when the
value is no longer exceeding the limit.
Disposal note
This symbol on the product indicates that it may not be disposed of as household waste.
It must be handed over to the applicable take-back scheme for the recycling of electrical and electronic equipment.
• Dispose of the product through channels provided for this purpose.
• Comply with all local and currently applicable laws and regulations.