Pulse Barrier; Instantaneous Value; Time Basis; Setting The Real Time Clock - Baer DLX User Manual

3.5.9

Pulse barrier

With pulse barrier enabled all pulses arriving in a time window around the
end of registration period are buffered. These are forwarded in the next reg-
istration period, synchronizing all following devices. This is done to accom-
plish identical figures at main and control measurement.
Note: This can cause pulses appear as packets at pulse outputs and summation
registers.
Features:
•
individually configurable for every input
• time range: ± 9.9 s around end of registration period
•
settable in steps of 100 ms
3.5.10

Instantaneous value

For special calculation (e.g. fill level, fluid level, temperature) at the end of
registration period it is possible to activate the measuring for the last minute
in every registration period. This function can be activated only for pulses
and for registration period MP1/Tm1 (Buffer 1).
3.6

Time basis

The registration and calculation of demand values has to happen in a de-
fined time frame. In order to calculate the correct tariff-related values, the
internal real time clock must be programmed to the valid official time (e.g.
CET = Central European Time or CEST = Central European Summer
Time).
3.6.1

Setting the real time clock

The integrated real time clock is buffered by a "GoldCap" capacitor, which
provides power for a minimum of 7 days in the event of a power failure.
Should the power failure last longer than the capacity of the "GoldCap",
then the clock (the system time) will be set 59 minutes and 10 seconds af-
ter the date and time of the last stored value of the main registration period
Tm1 once the power supply returns.
The time can be set via the keypad, via the service interface or by means of
the SCTM message in the case of remote data retrieval (if this feature was
enabled during the setting of parameters). Please note that if summertime
switching is activated, the clock cannot be set or synchronized during the
time period of the "double" hour, due to the ambiguity of that period. During
this period the unit will ignore the command. In order to not affect time
management, the clock should not be set via more than one interface at the
same time.
26