hager HZI855, Инструкция по эксплуатации, Страница: 30 / 65

6LE007317A 30
Starting time&date: that’s the date&hour where this periodic program will start (for example, starting on January 5th at 1pm). (date and
hour when first TEST will take place)
Ending time&date: that’s the date&hour where the program will stop (for example, May 12th at 4pm) (after this date, this program will
not execute a TEST).
HZI855
*Example:
- Type: ON LOAD
- Periodicity: Monthly
- Test duration: 15min
- Starting time & date: January 5th at 1pm
- Ending time & date: May 12th at 4pm
The exerciser program will do the following:
Exerciser will carry on a full test on load (starting genset if any, counting timers and operating the switch and transferring loads from
priority source to alternate source) on Jan 5th at 1pm for 15 minutes. This will be repeated every month at the same time (1pm) for
the following months until May, when the last exerciser will take place on May 12th at 1pm). After May12th 4pm, the exerciser is over
(ending date & time).
In the case of overlapping several exerciser/scheduler programs, the priority one (lower custom number) will take place and not the others.
Examples:
TON Custom 1 : Duration 30 minutes
TON Custom 2 : Duration 50 minutes
Current Behaviour : Problem when 2 or more Custom exerciser of same type (TON or TOF) overlap
Custom 1
starts
Custom 2 starts
15 minutes
after first
started
Custom 2 ends 35 minutes after it started.
We actually merge both test : 15 minutes of
custom 1 plus 35 minutes of custom 2 -> 50
minutes
TON Custom 1 : Duration 50 minutes
TON Custom 2 : Duration 30 minutes
Custom 2
starts 35
minutes after
first started
Custom 2 stops immediately. We actually
merge both tests. Since we already did 35
minutes of the custom 1, we assume that
we fulfilled Custom 2 test duration of 30
minutes
Custom 1
starts
Proposal : Ignore any incoming custom test of same type of current running test
TON Custom 1
TON Custom 2
Custom 2 is
ignored because
Custom 1 is
running
Custom 1
starts
Custom 1 ends
properly after its
original duration
TON Custom 2
TON Custom 1
In case the start time is the same for 2 or
more Custom tests, the lowest number
takes over. Therefore here, Custom 1
starts
Same
Start
Time
Custom 1 ends
properly after its
original duration
è
Longest test duration not respected
Loss of data.
è
Longest test duration respected
But wrongly scheduled (mixed of both test)
TON Custom 1 : Duration 30 minutes
TON Custom 2 : Duration 50 minutes
Current Behaviour : Problem when 2 or more Custom exerciser of same type (TON or TOF) overlap
Custom 1
starts
Custom 2 starts
15 minutes
after first
started
Custom 2 ends 35 minutes after it started.
We actually merge both test : 15 minutes of
custom 1 plus 35 minutes of custom 2 -> 50
minutes
TON Custom 1 : Duration 50 minutes
TON Custom 2 : Duration 30 minutes
Custom 2
starts 35
minutes after
first started
Custom 2 stops immediately. We actually
merge both tests. Since we already did 35
minutes of the custom 1, we assume that
we fulfilled Custom 2 test duration of 30
minutes
Custom 1
starts
Proposal : Ignore any incoming custom test of same type of current running test
TON Custom 1
TON Custom 2
Custom 2 is
ignored because
Custom 1 is
running
Custom 1
starts
Custom 1 ends
properly after its
original duration
TON Custom 2
TON Custom 1
In case the start time is the same for 2 or
more Custom tests, the lowest number
takes over. Therefore here, Custom 1
starts
Same
Start
Time
Custom 1 ends
properly after its
original duration
è
Longest test duration not respected
Loss of data.
è
Longest test duration respected
But wrongly scheduled (mixed of both test)