Zennio MINiBOX 45v2 User manual

➢
MINiBOX 45 v2 / MINiBOX 25 v2
Multifunction Actuator with 4 or 5 Outputs and 5 Inputs
ZIOMN45V2
USER MANUAL
ZIOMN25V2
Application program version: [1.1]
User manual edition: [1.1]_a
www.zennio.com

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
2
CONTENTS
Contents........................................................................................................................................ 2
1 Introduction .......................................................................................................................... 3
1.1 MINiBOX 25 v2 / MINiBOX 45 v2 ..................................................................................... 4
1.2 Installation........................................................................................................................ 6
1.3 Start-Up and Power Loss.................................................................................................. 7
2 Configuration......................................................................................................................... 8
2.1 General............................................................................................................................. 8
2.2 Inputs ............................................................................................................................. 11
2.2.1 Binary Input............................................................................................................ 11
2.2.2 Temperature Probe................................................................................................ 11
2.2.3 Motion Detector .................................................................................................... 11
2.3 Outputs........................................................................................................................... 13
2.4 Logic Functions............................................................................................................... 14
2.5 Thermostats ................................................................................................................... 15
2.6 Master Light ................................................................................................................... 16
2.7 Scene Temporisation...................................................................................................... 19
2.8 Manual Control .............................................................................................................. 21
ANNEX I. Communication Objects............................................................................................... 26

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
3
DOCUMENT UPDATES
Version
Changes
Page(s)
[1.1_a]
Changes in the application program of MINiBOX 45 / 25 v2:
•Internal optimisation.
-

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
4
1INTRODUCTION
1.1 MINiBOX 25 v2 / MINiBOX 45 v2
MINiBOX 45 v2 and MINiBOX 25 v2 from Zennio are two versatile KNX actuators
featuring a wide variety of functions, being both of them entirelyequivalent except for the
number of individualbinary outputs available (four in MINiBOX 45 v2 and two in MINiBOX
25 v2) and by the incorporation of the functional block fancoil in the MINiBOX 45 v2.
The most outstanding features are:
4 / 2 relay outputs, respectively, configurable as:
➢Up to 4 / 2 individual ON/OFF output,
➢Up to 2 / 1 independent shutter channels (with or without slats),
➢Up to 1 two-pipe fan coil modules where both the fan speed control and
the valve control are performed through relays,
➢A combination of the above.
5 multi-purpose inputs, configurable as:
•Temperature probes, (with the possibility to parameterize a personalized
probe),
•Binary inputs (i.e., pushbuttons, switches, sensors),
•Motion detectors.
10 customisable, multi-operation logic functions.
4 independent thermostats.
Scene-triggered action control, with an optional delay in the execution.
Master light control 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.

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
5
Manual operation / supervision of the 2 or 4 relay outputs through the on-
board pushbuttons and LEDs.
Heartbeat or periodical “still-alive”notification.
Relay Switches Counter.

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
6
1.2 INSTALLATION
MINiBOX 45 / 25 v2 connects to the KNX bus through the on-board KNX connector.
Once the device is provided with power from the KNX bus, both the individual address
and the associated application program may be downloaded.
This device does not need any additional external power since it is entirely powered
through the KNX bus.
Figure 1. MINiBOX 45 v2. Elements
Note: the above element diagram is slightly different for MINiBOX 25 v2, although
entirely analogous.
The main elements of the device are described next.
Test/Prog. Pushbutton (6): a short press on this button sets the device into
the programming mode, making the associated LED (5) light in red.
Note: if this button is held while plugging the device into the KNX bus, the
device will enter into safe mode. In such case, the LED will blink in red every
0.5 seconds.
Outputs (7): output ports for the insertion of the stripped cables of the systems
being controlled by the actuator (see section 2.3). Please secure the
connection by means of the on-board screws.
1. Output Control Pushbutton.
2. Output LED Indicator.
3. Analogue-Digital Inputs.
4. KNX Bus Connector.
5. Prog./Test LED.
6. Prog./Test Pushbutton.
7. Relay Outputs.
1
2
3
4
5
6
7

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
7
Inputs (3): input ports for the insertion of the stripped cables of external
elements such as switches / motion detectors / temperature probes, etc. One
of the two cables of each element need to be connected to one of the slots
labelled “1” to “6”, while the other cable should be connected to the slot labelled
as “C”. Note that all the external input devices share the “C” slot for one of the
two cables. Please secure the connection by means of the on-board screws.
To get detailed information about the technical features of this device, as well as on the
installation and security procedures, please refer to the corresponding Datasheet,
bundled with the original package of the device and also available at www.zennio.com.
1.3 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 output 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, while the individual outputs and fan coil contacts will
switch to the specific state configured in ETS (if any).

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
8
2CONFIGURATION
2.1 GENERAL
After importing the corresponding database in ETS and adding the device into the
topology of the project, the configuration process begins by entering the Parameters tab
of the device.
ETS PARAMETERISATION
The only parameterisable screen that is always available is General. From this screen it
is possible to activate/deactivate all the required functionality.
Figure 2. Default screen
Inputs [disabled/enabled]
1
: enables o disables the “Inputs” tab on the left
menu. See section 2.2 for more details.
Outputs [disabled/enabled]: enables o disables the “Outputs” tab on the left
menu. See section 2.3 for more details.
Logic Functions [disabled/enabled]: enables o disables the “Logic Functions”
tab on the left menu. See section 2.4 for more details.
1
The default values of each parameter will be highlighted in this document, as follows:
[default/rest of options].

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
9
Thermostats [disabled/enabled]: enables o disables the “Thermostats” tab
on the left menu. See section 2.5 for more details.
Master Light [disabled/enabled]: enables o disables the “Master Light” tab on
the left menu. See section 2.6 for more details.
Scene Temporization [disabled/enabled]: enables o disables the “Scene
Temporization” tab on the left menu. See section 2.7 for more details.
Manual Control [disabled/enabled]: enables o disables the “Manual Control”
tab on the left menu. See section 2.8 for more details.
Sending of Indication Objects (0 and 1) on Bus Voltage Recovery
[disabled/enabled]: this parameter lets the integrator activate two new
communication objects (“Reset 0” and “Reset 1”), 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.
Figure 3. Sending of Indication objects on bus voltage recovery
Heartbeat (Periodical 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).
Figure 4. Heartbeat (Periodical Alive Notification).

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
10
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.
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”)

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
11
2.2 INPUTS
MINiBOX 45 / 25 v2 incorporates five analogue/digital inputs, each configurable as a:
Binary Input, for the connection of a pushbutton or a switch/sensor.
Temperature Probe, for the connection of a temperature sensor from Zennio.
Motion Detector, for the connection of a motion detector (models ZN1IO-
DETEC-P and ZN1IO-DETEC-X from Zennio).
Important: older models of the Zennio motion detector (e.g., ZN1IO-DETEC
and ZN1IO-DETEC-N) will not work properly with MINiBOX 45 / 25 v2.
2.2.1 BINARY INPUT
Please refer to the specific user manual “Binary Inputs”, available in the MINiBOX 45 /
25 v2 product section, at the Zennio website (www.zennio.com).
2.2.2 TEMPERATURE PROBE
Please refer to the specific user manual “Temperature Probe”, available in the MINiBOX
45 / 25 v2 product section, at the Zennio website (www.zennio.com).
2.2.3 MOTION DETECTOR
It is possible to connect motion detectors (models ZN1IO-DETEC-P and ZN1IO-DETEC-
Xfrom Zennio) to the input ports of MINiBOX 45 / 25.
Please refer to the specific user manual “Motion Detector”, available in the MINiBOX
45 / 25 v2 product section, at the Zennio website (www.zennio.com) for detailed
information about the functionality and the configuration of the related parameters.
Notes:
The ZN1IO-DETEC-P motion detector is compatible with a variety of Zennio
devices. However, depending on the device it is actually being connected to,

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
12
the functionality may differ slightly. Therefore, please refer specifically to the
corresponding product section to obtain the aforementioned document.
Motion detectorswith references ZN1IO-DETECand ZN1IO-DETEC-N are not
compatible with MINiBOX 45 / 25 v2 (may report inaccurate measurements if
connected to this device).
When connected to MINiBOX 45 / 25 v2, the rearmicro-switch of modelZN1IO-
DETEC-P should be set to position “Type B”.

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
13
2.3 OUTPUTS
The MINiBOX 45 v2 / MINiBOX 25 v2 actuators incorporate 4 / 2 relay outputs
respectively, each configurable as a:
Individual binary outputs, which allows an independent control of loads (it is
possible to control up to 4 / 2 different loads, respectively).
Shutter channels, which allow controlling the motion of shutters or blinds (it is
possible to control up to 4 / 2 independent shutter channels, respectively).
Fan Coil modules, which allow the control of the fan and the valve of two-pipe
fan coil units (it is possible to control one independent fancoil block only in
MINiBOX 45 v2).
For detailed information about the functionality and the configuration of the related
parameters, please refer to the following specific manuals, all of them available in the
MINiBOX 45 / 25 v2 product section at the Zennio website (www.zennio.com):
Individual outputs.
Shutter channels.
‘Relays’ Fan Coil. Note that these devices only support two-pipe fan coils
with On/Off valves. Therefore, any references to four-pipe fan coils and 3-
Point valves do not apply to them.

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
14
2.4 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.
MINiBOX 45 / 25 v2 can implement up to 10 different and independent functions,
each of them entirely customisable and consisting in up to 4 consecutive operations
each.
The execution of each function can depend on a configurable condition, which will be
evaluated every time the function is triggered through specific, parameterizable
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”user manual (available in the MINiBOX
45 / 25 v2 product section at the Zennio homepage, www.zennio.com) for detailed
information about the functionality and the configuration of the related parameters.

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
15
2.5 THERMOSTATS
MINiBOX 45 v2 /MINiBOX 25 v2 implements four Zennio thermostats which can be
enabled and configured independently.
Please refer to the specific “Zennio Thermostat” user manual (available in the MINiBOX
45 / 25 v2 product section at the Zennio homepage, www.zennio.com) for detailed
information about the functionality and the configuration of the related parameters.

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
16
2.6 MASTER LIGHT
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:

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
17
Figure 5. Master Light
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.

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
18
➢Scaling [disabled/enabled]: if checked, object “[ML] General Switch-off:
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).

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
19
2.7 SCENE TEMPORISATION
The scene temporisation allows imposing delays over the scenes of the outputs.
These delays are defined in parameters, and can be applied to 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
individual output or shutter channel, in case of receiving an order to execute one of them
when a previous temporisation is still pending for that output or that channel, 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 someof the outputs.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 6.
Figure 6. Scene temporisation
Enabling a certain Scene Number n[disabled/enabled] 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 outputs where it has been configured.

MINiBOX 45 v2/MINiBOX 25 v2
http://www.zennio.com Technical Support: http://support.zennio.com
20
Figure 7. Configuration of the scene temporisation
Therefore, parameter “Scene m. 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 individual output, shutter channel or fan coil module).
Note: In the configuration of a scene of an output / shutter channel / fan coil 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 behaviour 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.