Zennio ZIOMBSH4V3 4 Channel 8Channel Shutter Actuator User Manual
- June 16, 2024
- Zennio
Table of Contents
MAXinBOX SHUTTER 4CH / 8CH v3
4-Channel / 8-Channel Shutter Actuator with KNX Secure
ZIOMBSH4V3
ZIOMBSH8V3
Application program version: [1.10] User manual edition: [1.10]_a
www.zennio.com
INTRODUCTION
1.1 MAXinBOX SHUTTER 4CH / 8CH v3
MAXinBOX SHUTTER 4CH v3 and MAXinBOX SHUTTER 8CH v3 from Zennio are KNX Secure
specific actuators (of 4 or 8 channels, respectively) for controlling
motorised shutter / blind systems.
The most outstanding features are:
8 / 16 relay outputs, configurable as up to 4 / 8 independent shutter channels
(with or without slats).
20 customisable, multi-operation logic functions.
2 master light control modules for an easy, out-of-the-box control of a set of
luminaires (or functionally equivalent devices) one of which acts as a general
lamp and the others as secondary lamps.
Scene-triggered action control, with an optional delay in the execution.
Manual operation / supervision of the shutter channels through the onboard
pushbuttons and LEDs.
Heartbeat or periodic “still-alive” notification.
Relay Switches Counter.
KNX Security.
For detailed information about the functionality and configuration of KNX security, consult the specific user manual “KNX Security”, available in the product section of the Zennio web portal (www.zennio.com).
1.2 START-UP AND POWER LOSS
During the start-up of the device, the Test/Prog. LED will blink in blue
colour for a few seconds before the device is ready. External orders will not
be executed during this time, but afterwards.
Depending on the configuration, some specific actions will also be performed
during the start-up. For example, the integrator can set whether the shutter
channels should switch to a particular state and whether the device should
send certain objects to the bus after the power recovery. Please consult the
next sections of this document for further details.
On the other hand, when a bus power failure takes place, the device will
interrupt any pending actions, and will save its state so it can be recovered
once the power supply is restored.
For safety reasons, all shutter channels will be stopped (i.e., the relays
will open) if a power loss takes place.
CONFIGURATION
2.1 GENERAL
After importing the corresponding database in ETS and adding the device into
the topology of the desired project, the configuration process begins by
entering the Parameters tab of the device.
ETS PARAMETERISATION
The only parameterisable screen available by default is General. From this
screen it is possible to activate/deactivate all the required functionality.
Scenes after Download [Configured by Parameters/Keep Saved Scenes]:
allows defining whether the value of the scenes is the configured by parameter
or whether the previously saved value is kept after download.
Note: if “Keep Saved Scenes” option has been configured, but it is the
first download of the device or a different version from the current one, the
values configured by parameter will be adopted. If new scenes are added in
successive downloads, it will be necessary to perform a download by checking
the option “Configured by Parameters” to ensure the correct operation of these
scenes.
Outputs [disabled/enabled]1: enables o disables the “Outputs” tab on the left
menu. See section 2.2 for more details.
Logic Functions [disabled/enabled]: enables o disables the “Logic Functions”
tab on the left menu. See section 2.3 for more details.
Master Light [disabled/enabled]: enables o disables the “Master Light” tab on
the left menu. See section 2.4 for more details.
Scene Temporization [disabled/enabled]: enables o disables the “Scene
Temporization” tab on the left menu. See section 2.5 for more details.
Manual Control [disabled/enabled]: enables o disables the “Manual Control” tab
on the left menu. See section 2.6 for more details.
Heartbeat (Periodic Alive Notification) [disabled/enabled]: this parameter
lets the integrator incorporate a one-bit object to the project (“[Heartbeat]
Object to Send ‘1’”) that will be sent periodically with value “1” to notify
that the device is still working (still alive).
Note: The first sending after download or bus failure takes place with a
delay of up to 255 seconds, to prevent bus overload. The following sendings
match the period set.
Device Recovery Objects (Send 0 and 1) [disabled/enabled]: this parameter
lets the integrator activate two new communication objects (“[Heartbeat]
Device Recovery”), which will be sent to the KNX bus with values “0” and “1”
respectively whenever the device begins operation (for example, after a bus
power failure). It is possible to parameterise a certain delay [0…255] to this
sending.
Note: after download or bus failure, the sending takes place with a delay of up to 6,35 seconds plus the parameterised delay, to prevent bus overload.
Show Relay Switches Counter Objects [disabled/enabled]: enables two communication objects to keep track of the number of switches performed by each of the relays (“[Relay X] Number of Switches”) and the maximum number of switches carried out in a minute (“[Relay X] Maximum Switches per Minute”).
2.2 OUTPUTS
MAXinBOX SHUTTER 4CH / 8CH v3 incorporates 8 or 16 relay outputs,
respectively, configurable as up to 4 or 8 independent shutter channels, each
of which will operate one motorised shutter system.
For detailed information about the functionality and the configuration of the
parameters related to the shutter channels, please refer to the specific
manual “Shutters”, available in the MAXinBOX SHUTTER 4CH / 8CH v3 product
section at the Zennio homepage (www.zennio.com).
2.3 LOGIC FUNCTIONS
This module makes it possible to perform numeric and binary operations to
incoming values received from the KNX bus, and to send the results through
other communication objects specifically enabled for this purpose.
MAXinBOX SHUTTER 4CH / 8CH v3 can implement up to 20 different and independent
functions, each of them entirely customisable and consisting in up to 4
consecutive operations each one.
The execution of each function can depend on a configurable condition, which
will be evaluated every time the function is triggered through specific,
parameterisable communication objects. The result after executing the
operations of the function can also be evaluated according to certain
conditions and afterwards sent (or not) to the KNX bus, which can be done
every time the function is executed, periodically or only when the result
differs from the last one.
Please refer to the specific “Logic Functions in MAXinBOX SHUTTER” user manual
(available in the MAXinBOX SHUTTER 4CH / 8CH v3 product section at the Zennio
homepage, www.zennio.com) for detailed information
about the functionality and the configuration of the related parameters.
2.4 MASTER LIGHT
MAXinBOX SHUTTER 4CH / 8CH v3 implements two Master Light which can be enabled
and configured independently.
The Master Light function brings the option to monitor the state of up to 12
light sources (or even more, if the Master Light controls from multiple Zennio
devices are linked together) or of any other elements whose state is
transmitted through a binary object and, depending on those states, perform a
master order every time a certain trigger signal (again, a binary value) is
received through a specific object.
Such master order will consist in:
A general switch-off order, if at least one of the up to twelve status objects
is found to be on.
A courtesy switch-on order, if none of the up to twelve status objects is
found to be on.
Note that the above switch-off and switch-on orders are not necessarily a
binary value being sent to the bus – it is up to the integrator the decision
of what to send to the KNX bus in both cases: a shutter order, a thermostat
setpoint or mode switch order, a constant value, a scene… Only the trigger
object and the twelve status objects are required to be binary (on/off).
The most typical scenario for this Master Light control would be a hotel room
with a master pushbutton next to the door. When leaving the room, the guest
will have the possibility of pressing on the master pushbutton and make all
the lamps turn off together. Afterwards, back on the room and with all the
lamps off, pressing on the same master pushbutton will only make a particular
lamp turn on (e.g., the closest lamp to the door) – this is the courtesy
switch-on. Besides, it is possible to concatenate two or more Master Light
modules by means of a specific communication object which represents the
general state of the light sources of each module. Thereby, it is possible to
expand the number of light sources by considering the general state of one
module as an additional light source for another.
ETS PARAMETERISATION
Once the Master Light function has been enabled, a specific tab will be
included in the menu on the left. This new parameter screen contains the
following options:
Number of State Objects [1…12]: defines the number of 1-bit status objects
required. These objects are called “[ML] Status Object n.”
In addition, the general status object (“[ML] General status”) will always be
available in the project topology. It will be sent to the bus with a value of
“1” whenever there is at least one of the above state objects with such value.
Otherwise (i.e., if none of them has a value of “1”), it will be sent with a
value of “0”.
Trigger Value [0 / 1 / 0/1]: sets the value that will trigger, when received
through “[ML] Trigger”, the master action (the general switch-off or the
courtesy switch-on).
General Switch-Off.
➢ Delay [0…255] [x 1 s]: defines a certain delay (once the trigger has been
received) before the execution of the general switch-off. The allowed range is
0 to 255 seconds.
➢ Binary Value [disabled/enabled]: if checked, object “[ML] General Switch-
off: Binary Object” will be enabled, which will send one “0” whenever the
general switch-off takes off.
➢ Scaling [disabled/enabled]: if checked, object “[ML] General Switchoff:
Scaling” will be enabled, which will send a percentage value (configurable in
Value [0…100]) whenever the general switch-off takes off.
➢ Scene [disabled/enabled]: if checked, object “[ML] General Switch-off:
Scene” will be enabled, which will send a scene run / save order (configurable
in Action [Run / Save] and Scene Number [1…64]) whenever the general switch-
off takes off
➢ HVAC [disabled/enabled]: if checked, object “[ML] General Switch-off: HVAC
mode” will be enabled, which will send an HVAC thermostat mode value
(configurable in Value [Auto / Comfort / Standby / Economy / Building
Protection) whenever the general switch-off takes off.
Note: the above options are not mutually exclusive; it is possible to send values of different nature together.
Courtesy Switch-On:
The parameters available here are entirely analogous to those already
mentioned for General Switch-Off. However, in this case the names of the
objects start with “[ML] Courtesy Switch-On (…).” On the other hand, sending
scene save orders is not possible for the courtesy switch-on (only orders to
play scenes are allowed).
Note: object “[ML] Courtesy Switch-On: Binary Object” sends the value “1”
(when the courtesy switch-on takes place), in contrast to object “[ML] General
Switch-Off: Binary Object”, which sends the value “0” (during the general
switch- off, as explained above).
2.5 SCENE TEMPORISATION
The scene temporisation allows imposing delays over the scenes of the shutter
channels. These delays, defined in parameters, are applied on the execution of
one or more scenes that may have been configured.
Please bear in mind that, as multiple delayed scenes can be configured for
each shutter channel, in case of receiving an order to execute one of them
when a previous temporisation is still pending in that channel, the channel
will interrupt such temporisation will be interrupted and only the delay and
the action of the new scene will be executed.
ETS PARAMETERISATION
Prior to setting the scene temporisation, it is necessary to have one or more
scenes configured in some of the channels. When entering the Configuration
window under Scene Temporization, all configured scenes will be listed,
together with a few checkboxes to select which of them need to be temporised,
as shown in Figure 5.
Enabling a certain scene number n brings a new tab with such name to the menu on the left, from which it is possible to configure the temporisation of that scene for each of the channels where it has been configured.
Therefore, parameter “Scene m. Shutter Channel Z Delay” [0…3600 [s] / 0…1440
[min] / 0…24 [h]], defines the delay that will be applied to the action
defined in Z for the execution of scene m (where Z may be a specific shutter
channel).
Note: in the configuration of a scene of a shutter channel it is possible
to parameterize several scenes with the same scene number. This means that
several delay parameters associated with the same output appear in the
configuration tab of the delays of that scene. With this parameterization,
the behavior will be as follows: the action and delay of the first scene
parameterized with the same scene number will always prevail, where the
highest priority scene is 1 (the first in the scene configuration tab) and
the lowest priority is the last.
2.6 MANUAL CONTROL
MAXinBOX SHUTTER 4CH / 8CH v3 allows commanding orders through the pushbuttons
on the top of the device to move the shutter up or down. Two specific
pushbuttons are provided per channel (i.e., one per relay output).
Manual operation can be done in two different ways, named as Test On Mode (for
testing purposes during the configuration of the device) and Test Off Mode
(for a normal use, anytime). Whether both, only one, or none of these modes
should be accessible needs to be parameterised in ETS. Moreover, it is
possible to enable a specific binary object for locking and unlocking the
manual control in runtime.
Note:
The Test Off mode will be active (unless it has been disabled by parameter)
after a download or a reset with no need of a specific activation – the
pushbuttons will respond to user presses from the start.
On the contrary, switching to the Test On mode (unless disabled by parameter)
needs to be done by long-pressing the Prog/Test button (for at least three
seconds), until the LED is no longer red and turns yellow. From that moment,
once the button is released, the LED light will remain green to confirm that
the device has switched from the Test Off mode to the Test On mode. After
that, an additional press will turn the LED yellow and then off, once the
button is released. This way, the device leaves the Test On mode.
Note that it will also leave this mode if a bus power failure takes place or
if a manual control lock is sending from KNX bus.
Test Off Mode
Under the Test Off Mode, the shutter channels can be controlled through both
their communication objects and the actual pushbuttons located on the top of
the device.
When one of these buttons is pressed, the shutter will behave as if an order
had been received through the corresponding communication object, and will
also send the status objects when required.
This behaviour depends on the length of the button press:
A long press makes the shutter start moving (upwards or downwards, depending
on the button being pressed). The LED will light in green until the end of the
motion. If the button gets pressed being the shutter already at the top or
bottom positions, nothing will happen (the LED will not light).
A short press will make the shutter drive stop (if in motion), as it normally
does when a step/stop order is received from the KNX bus. In case of not being
the shutter in motion, pressing the button does not cause any action, unless
slats/lamellas have been parameterised – in such case, a step movement
(up/down, depending on the button pressed) will take place. The status objects
will be sent to the bus when corresponding.
Regarding the lock, timer, alarm and scene functions, the device will behave under the Test Off mode as usual. Button presses during this mode are entirely analogous to the reception of the corresponding orders from the KNX bus.
Test On Mode
After entering the Test On mode, it will only be possible to control the
shutters through the on-board pushbuttons. Orders received through
communication objects will be ignored, with independence of the channel they
are addressed to.
Pressing the button will make the shutter drive move upward or downward
(depending on the button) until the button is released again, thus ignoring
the position of the shutter and the parameterised times. The LED will light in
green while the button is being hold.
For safety reasons, the device does not allow the activation of the two
outputs of a shutter channel at the same time. If the button of one of the
outputs is held while the other output is active, the device will first
deactivate it and afterwards perform the required action on the output
associated to the button pressed.
Note: after leaving the Test On mode, the status objects will recover the
values they had prior to entering Test On. As the device is never aware of the
actual position of the shutter (as the shutter drive does not provide any
feedback), these values may not show the real position. This can be solved by
performing a complete move-up or movedown order, or by calibrating the
shutter position in the Test On mode until it matches the status objects.
As described previously if the device is in Test On mode, any command sent from the KNX bus to the actuator will not affect the channel and no status objects will be sent (only periodically timed objects such as Heartbeat or logic functions will continue to be sent to the bus) while Test ON mode is active. However, in the case of the “Alarm” and “Block” objects, although in Test ON mode the actions received by each object are not taken into account, the evaluation of their status is carried out when exiting this mode, so that any change in the alarm status or blocking of the outputs while Test ON mode is active is taken into account when exiting this mode and is updated with the last status detected.
Important: the device is delivered from factory with the channel disabled, and with both manual modes (Test Off and Test On) enabled by default.
ETS PARAMETERISATION
The manual control is configured from the Configuration tab, under Manual
Control.
The only two parameters are:
Manual Control [Disabled / Only Test Off Mode / Only Test On Mode / Test Off
Mode + Test On Mode]. Depending on the selection, the device will permit using
the manual control under the Test Off, the Test On, or both modes.
Note that, as stated before, using the Test Off mode does not require any
special action, while switching to the Test On mode does require longpressing
the Prog/Test button.
Manual Control Lock [disabled/enabled]: unless the above parameter has been
“Disabled”, the Lock Manual Control parameter provides an optional procedure
for locking the manual control in runtime. When this checkbox is enabled,
object “Manual Control Lock” turns visible, as well as two more parameters:
➢ Value [0 = Lock; 1 = Unlock / 0 = Unlock; 1 = Lock]: defines whether the
manual control lock/unlock should take place respectively upon the reception
(through the aforementioned object) of values “0” and “1”, or the opposite.
➢ Initialization [Unlocked / Locked / Last Value]: sets how the lock state of
the manual control should remain after the device start-up (after an ETS
download or a bus power failure). “Last Value” (default; on the very first
start-up, this will be Unlocked.
ANNEX I. COMMUNICATION OBJECTS
Functional range” shows the values that, with independence of any other values permitted by the bus according to the object size, may be of any use or have a particular meaning because of the specifications or restrictions from both the KNX standard or the application program itself.
Note: some of the numbers in the first column are only applicable to MAXinBOX SHUTTER 8CH v3.
Join and send us your inquiries
about Zennio devices:
https://support.zennio.com
Zennio Avance y Tecnología S.L.
C/ Río Jarama, 132. Nave P-8.11
45007 Toledo (Spain).
Tel. +34 925 232 002
www.zennio.com
info@zennio.com
References
Read User Manual Online (PDF format)
Read User Manual Online (PDF format) >>