geminox THI 2-17 B 120, Technical Instructions

Page: 14 / 24

- 14 -
OPERATING FAULTS
Every cause can be individually activated or deacti-
vated by entering the associated limits.
- Burner hours run :
Burner hours run maintenance is activated by
setting parameter "BetrStdWartGrenz" (QAA 73
setting : 625) to a value other than "0".
This value represents the target number of hours
run. When this limit is reached, a maintenance
alarm will be delivered (interval since last service
visit).
- Number of startups:
Startup maintenance is activated by setting para-
meter "InbetrSetzWartGrenze" (QAA 73 setting :
626) to a value other than "0".
This value represents the target number of star-
tups. When this limit is reached, a maintenance
alarm will be delivered (interval since last service
visit).
- Months (service):
Service maintenance is activated by setting para-
meter "MonatWartGrenze" (QAA 73 setting :
627) to a value other than "0".
This value represents the target number of
months. When this limit is reached, a maintenan-
ce alarm will be delivered (interval since last ser-
vice unit).
Note :
- The month counter is only active when the device
is connected to power.
The acknowledgement sets the internal error code
"b0" and the fault statut message to "0", but the
maintenance code still gives the precise reason for
the maintenance alarm.
2.6.1 - Acknowledgement via QAA 73
For the parameter "WartungsQuittierung" (QAA 73
setting : 629) (defaut value: 0), to acknowledge the
maintenance alarm the heating engineer (or the en-
duser) enters the value of "1".
If no repetition is required, all maintenance alarms
after this acknowledgement will be locked, even if
other reasons for maintenance occur. In that case,
parameter "WartungsQuittierung" remains cons-
tantly at 1.
2.6.2 - Activation of the repetition after ack-
nowledgement
If required, a timer (duration of repetition) can be
started, that is, the maintenance alarm will reappear
on the display after a certain period of time. An ack-
nowledgement can also be made then. This period
of time starts after each acknowledgement.
The repetition can be set via parameter «War-
tungsRepetitionsDauer» (QAA 73 setting 633).
Contents of parameter «WartungsRepetitions-
Dauer» is the desired period of time (in days) until
the maintenance alarm appears again.
If a value other than «0» is entered there, a repeti-
tion is made within the entered duration of the repe-
tition time.
During this period of time, no more
maintenance alarms will appear, even if
other reasons for maintenance occur.
Resetting can take place at any time, and after ack-
nowledgement or during the repetition sequence.
A reset can be made in 1 of 2 ways:
- Total reset :
Here, all maintenance alarms can be reset at the
same time. If, in parameter «WartungsEinstellun-
gen» (QAA 73 setting 630), «1» is entered, all
maintenance counters will be set to «0» when the
parameter is saved.
The maintenance counters of the hours run, star-
tups and months maintenance alarms will be
newly started.
- Individual resert of a certain maintenance
alarm :
Individual maintenance alarms can also be reset.
In that case, parameter «WartungsEinstellun-
gen» (QAA 73 setting : 630) will again be ad-
dressed bit by bit.
There is a bit available for each maintenance
alarm via which this maintenance alarm can be
reset (section 2.4 - page 13 - chapter III - OPE-
RATING FAULTS - SERVICING). It is thus possi-
ble to also reset other reasons for maintenance
although they have not yet occurred.
When resetting the maintenance alarm, the mainte-
nance code and the internal error code (b0) will
automatically also be reset.
Note : Only the QAA 73 can the maintenance alarms
be activated, the reasons for the maintenan-
ce alarms be checked and a reset via para-
meter be made.
2.5 - Activation of the individual
maintenance alarm
2.6 - Acknowledgement of maintenance
alarms
2.7 - Resetting the maintenance alarms
!