7.1.5.9
Automation events: input/output association
Each relay actuator is provided with two inputs (controlled by buttons or switches) to:
•
control the respective outputs locally;
•
control one or more outputs of different relay actuators by means of events (of the inputs).
In the first case, staircase light control is a typical example in which it may be useful to have a local output
control. According to the previous paragraphs, the "Door Opening" topological event, which activates an
output on the relay actuator, can be used to turn on the staircase lights, for example. Similarly, using a
button located in the entrance hall and connected to the input of the same actuator, it is possible to switch
the staircase lights on locally in the same way.
For the second case, instead, the outputs (one or more of several relay actuators) are controlled by events
associated with the single input of a relay actuator, which can be configured in bistable mode (switch) or
monostable mode (button). In the latter case it is also necessary to define the button pressure time. If it is
assumed that in case of switch the pressure time is zero, the possible events are shown in the table below.
Mode
Bistable (t= 0)
Monostable (t> 0)
The operating mode of the input can be set in the Relay Actuator input configuration page (see
A: Configuration parameters of IPerCom
Again, on the Relay Actuator configuration page you can deselect the "Output linked to input" option,
which selected by default. In this way, the output is controlled only by the rules which will be defined on
the Automation page and will be locally disconnected from the input.
The inputs can be set as normally closed or normally open (default choice) to meet different installation
needs.
To program the inputs and outputs of the Relay Actuator, follow the instructions on the device
configuration page (see
The correct approach to create automation rules (input/output association) is to firstly identify the
combinations of commands to be imparted by the system (relay output activation), then to create a rule for
each combination of commands with the respective event. The following example shows the procedure.
MT124-032N
Table
11: Automation rules to be implemented
devices).
APPENDIX A: Configuration parameters of IPerCom
Event 1
ON
Short press
Event 2
OFF
Long press
APPENDIX
devices).
299
Need help?
Do you have a question about the IPerCom 3.1.0 and is the answer not in the manual?
Questions and answers