19 Eventlog
18.1
Signalising due Service Message
Due service messages are signalised as follows
•
Flashing of the entire display
Flashing ends immediately upon touching th
•
Automatic jump to the menu - . ! *
Note: The menu ! ;
time as follows:
"
$
! ;
•
Acoustic alarm signal
(Provided the function <
activated in the menu <
!
The acoustic alarm signal ends immediately
touchscreen.
Note:
Due service processes are signalised at
corresponding day.
18.2
Re.scheduling service messages
When re'scheduling, PoolManager
service message by adding the configured s
current date.
Example:
•
For pH calibration, a service interval of 3 mo
•
On 6 December 2012, it will be re'schedule
The new due date is 6 March 2013.
Service messages are re'scheduled in the follow
•
Change to the service interval in the menu
•
Acknowledgement of a due service messag
•
Successful calibration
(for calibration messages only)
•
Calling up the function > 8 " '
menu ! ;
;
19
Eventlog
The ;
is called up as follows:
u "
$
&;
The eventlog is a record of all import
®
PoolManager
with date and time. PoolManage
to 500 events. When that number is met,
overwritten with new ones.
The eventlog is an important tool in controlling
swimming pool system and analysing potential p
ages
ws:
g the touchscreen.
#
can als
also be called up at any
!
! ;
is
)
tely upon touching the
at 8:00 a.m. on the
ges
®
recalculat
ulates the due date of a
d service interval to the
months is configured.
uled.
llowing cases:
nu ! ;
+
;
sage
;
in the
ortant events involving
®
ager
has memory for up
t, the oldest events are
ng proper operation of the
ial problems.
19.1
Events
The following events are logged in
d individually in the eventlog:
•
PoolManager
®
power on and
nd off
•
Alarms (start and end)
•
Calibration with detailed calibr
libration data
•
Parameter changes with old a
ld and new value
•
O2 dosings and average temp
mperature values
•
Manual dosings
•
Dosed product volumes
•
Remote access
•
Software updates
•
Access code reset
•
Reset to default values
PoolManager
®
displays all entries
ries in the eventlog in an easy'to'follow
manner. That is why there is no d
o detailed presentation of the individual
events in this manual.
19.2
Information displayed
yed
For each event, the following sup
supplemental information is stored and
displayed in the eventlog:
•
Date and time
•
User
(Provided a user can be alloca
located to the event, e.g. parameter
changes, calibrations, manual
ual dosing, etc.)
•
Type of access
•
Local operation (
,
•
Remote access from the
he local network (C<()
•
Remote access from the
he Internet (0 ,
19.2.1
Event display
Here is a detailed explanation of
of how an event is displayed using the
example of a parameter change:
1
Symbol (depending on type
pe of event)
2
Consecutive number of the
he event
3
Date
4
Time
5
User name and access leve
vel, e.g. ! ;
6
Type of access
(
A C<( A 0 )
7
Designation of changed par
parameter
8
Old parameter value (prior t
or to change)
9
New parameter value
*C ;
,
47