smartDEN Opener
User Manual
24 Apr 2018
- 65 -
On the
Figure 10.20
example, Digital Input 1 named "DI1" controls Main Controlled Device
(Main) on Any Alarm (LOW ALARM EVENT and HIGH ALARM respectively). On each alarm
notification is sent and emails are sent on LOW ALARM EVENT and log messages are written on
HIGH ALARM.
As shown on the graphics DI1, first makes transition from HIGH to LOW level and then
generates LOW ALARM EVENT. In "Open"
Control Mode,
when the Main Controlled Device was
closed, it starts
OPENING
and reaches
OPENED
state. Before the next alarm occurs,
smartDEN
Opener
receives
CLOSE
command from the web server and starts
CLOSING
. When high alarm
is generated, Main Controlled Device stops and goes to
STOPPED
state. On the next LOW
ALARM EVENT, it starts
OPENING
again.
If "Close"
Control Mode is
chosen, when the
Main Controlled
Device
was
CLOSED,
it
receives
OPEN
command and starts
OPENING
. Then goes to state
OPENED
after
Open/Close
time
expires. On next alarm, it starts
CLOSING
. When
CLOSED,
it receives another alarm which
should
CLOSE
it, but does not take effect because it is already
CLOSED
.
If
Control Mode
is "Stop", then on
Any Alarm
(in our example) the Main Controlled Device will
go to
STOPPED
state. As shown on
Figure 10.20,
Main is
CLOSED
and receives
STOP
command and then it changes its state to
STOPPED
. Then an
OPEN
command is sent and the
Main Controlled Device starts
OPENING
. When reaches
OPENED
state, HIGH ALARM is
generated and Main goes to
STOPPED
state again. A new
OPEN
command is received and Main
starts
OPENING
. Before
Open/Close time
expires, a new alarm is generated and the Main
Controlled Device goes to
STOPPED
state.
If "Toggle"
Control Mode
is selected, the Main Controlled Device will switch over
OPENED
and
CLOSED
state on
Any Alarm
(in our example). The Main Controlled Device is in
CLOSED
state
and receives an
OPEN
command from the web server. Main starts
OPENING
and then a
CLOSE
(the opposite of
OPEN
) command is generated on LOW ALARM EVENT. This makes the state of
the Main Controlled Device
STOPPED
. On next generated HIGH ALARM, a
CLOSE
command is
sent (because the state before
STOPPED
was
OPENING
) and Main Controlled Device starts
CLOSING
. It reaches
CLOSED
state and after a while, a LOW ALARM EVENT is generated
again. Then an
OPEN
command is sent and Main start
OPENING
.
In "NO Sensor"
Control Mode
as described earlier LOW ALARM EVENT will
OPEN
the Main
Controlled Device and HIGH ALARM will
CLOSE
it. On first LOW ALARM EVENT an
OPEN
command is sent and Main starts
OPENING
. After a while, when reached
OPENED
state, a
STOP
command is sent from the web server and Main goes to
STOPPED
state. On the HIGH ALARM
the Main Controlled Device starts
CLOSING
and goes to
CLOSED
state. On the next LOW
ALARM EVENT, again an
OPEN
command is sent and Main starts
OPENING
.
In "NC Sensor"
Control Mode
as described earlier LOW ALARM EVENT will
CLOSE
the Main
Controlled Device and HIGH ALARM will
OPEN
it. On first LOW ALARM a
CLOSE
command is
sent, but Main is already in
CLOSED
state. On the HIGH ALARM an
OPEN
command is sent and
the Main Controlled Device starts
OPENING
. On next LOW ALARM EVENT again a
CLOSE
command is sent and Main starts
CLOSING
.
