ZENN
iO
AVANCE Y TECNOLOGÍA
vwww.zennio.com
21
21
Upper limit
”. In the case of parameterizing a value other than 0 for this field, it will be as well
necessary to configure the parameters mentioned below, which define the behaviour of the
upper limit monitoring.
When over limit, send:
allows setting the value
(“0” or “1”) that will be written to the
object
“[Cx] Over-consumption Alarm” when the instant power becomes greater than the value
defined for the upper limit, making the user aware of this over-consumption situation in the
system.
Send Object when under Limit?:
this parameter allows specifying whether the object
“[Cx] Over-consumption Alarm” should send or not the inverted value (i.e., “0” if the above
parameter is set to “1”) once the instant power is back again under the upper limit (or under
the upper limit minus the
deadband
or margin configured through the parameter explained
below), making the user aware of the end of the over-consumption situation.
Send on value change:
this parameter can be used to avoid consecutive over-
consumption alarms every time the instant power
–after having exceeded the upper limit and
having activated the alarm
– is no longer higher than the limit and then exceeds it again. By
configuring a certain margin with a value other than 0 (in tens of a watt), every time the over-
consumption alarm is triggered, it will be necessary that the measured power decreases to
upper limit minus margin
before further over-consumptions trigger the alarm again. See figure
2.1 (Section 2.3).
For the lower limit:
Initial value:
allows setting (in tens of a watt) the value that, at least in the beginning, the
Energy Saver will assume as the lower limit while measuring power.
If the value “0” is set,
KES will not consider monitoring power in relation to a particular lower limit. The value of the
lower limit, however, can be modified in runtime through the communication object
“[Cx]
Lower limit
”. In the case of parameterizing a value other than 0 for this field, it will be as well
