MAXinBOX 66 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.
1. Analogue/Digital Inputs.
2. Upper Outputs.
3. Output LED Indicator.
4. Manual Control Pushbutton.
5. Test/Prog. LED.
6. Lower Outputs.
7. KNX Bus Connector.
8. Test/Prog. Pushbutton.
Figure 1. MAXinBOX 66. Elements
The main elements of the device are described next.
Test/Prog. Pushbut ton (8): a short press on this button set s 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 (2 and 6): 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.
Inputs (1): 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 needs 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 onboard 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 MAXinBOX 66 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, MAXinBOX 66 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 will switch to the specific state
configured in ETS (if any).
After importing the corresponding database in ETS and adding the device into the
topology of t he desired project, the configuration process begins by right-clicking into
the device and selecting Edit parameters.
ETS PARAMETERISATION
The only parameterisable scr een available by default is General. From this screen it is
possible to activate/deactivate all the required functionality.
Figure 2. General screen
Once activated, Inputs, Outputs, Logical Functions, Thermostats and
Master Light bring additional tabs to the menu on the left. These functions
and their parameters will be explained in later sections of this document.
Sending of Indication Objects (0 and 1) on Bus Voltage Recovery: 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 to this sending (0
to 255 seconds).
MAXinBOX 66 incorporates 6 analogue/digital inputs, each configurable as a:
Binary Input, for the connection of a pushbutton or a switch/sensor.
Temperature Probe, to connect a temperature sensor (model ZN1AC-
NTC68 S/E/F from Zennio).
Motion Detector, to connect a motion detector (models ZN1IO-DETEC-P
and ZN1IO-DETEC-X from Zennio).
Notes:
Older models of the Zennio motion detector (e.g., ZN1IO-DETEC and
ZN1IO-DETEC-N) will not work properly with MAXinBOX 66.
2.2.1BINARY INPUT
Please refer to the specific user manual “Binary Inputs in MAXinBOX 66”.
2.2.2TEMPERATURE PROBE
Please refer to the specific user manual “Temperature Probe in MAXinBOX 66”.
2.2.3MOTION DETECTOR
It is possible to connect motion detectors (models ZN1IO-DETEC-P and ZN1IO-DETEC-X from Zennio) to the input ports of MAXinBOX 66. This brings the device with
the possibility of monitoring motion and presence in the room, as well as the light level.
Depending on the detection, different response actions can be parameterised.
Please refer to the specific user manual “Motion Detector in MAXinBOX 66”
(available at the Zennio homepage, 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,
the functionality may differ slightly. Therefore, please refer specifically to the
aforementioned user manual “Zennio Motion Detector for MAXinBOX 66”.
Motion detectors with references ZN1IO-DETEC and ZN1IO-DETEC-N are
not compatible with MAXinBOX 66 (may report inaccurate measurements if
connected to this device).
When connected to MAXinBOX 66, the rear micro-switch of model ZN1IO-
MAXinBOX 66 incorporates 6 relay outputs, each configurable as a:
Individual binary output, that allow an independent control of a load (up to 6
different loads can be controlled by a MAXinBOX 66).
Shutter channel, that allow to control the motion of one blind (up to 3 blinds
can be controlled by a MAXinBOX 66).
For detailed information about the functionality and the configuration of the related
parameters, please refer to the following specific manuals, all of them available at the
Zennio homepage (www.zennio.com):
Individual outputs in MAXinBOX 66.
Shutter channels in MAXinBOX 66.
2.3.1MANUAL CONTROL
MAXinBOX 66 allows manually switching the state of its output relays through the
respective pushbuttons on the top of the device. A specific pushbutton is therefore
available per 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 swit ched 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.
Test Off Mode
Under the Test Off Mode, the outputs 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 output will behave as if an order had been
received through the corresponding communication object, depending on whether the
output is configured as an individual output or as a shutter channel.
Individual output: a sim ple press (short or long) will make the output switch
its on-off state, which will be reported to the KNX bus through the
corresponding status object, if enabled.
Shutter Channel: when the button is pressed, the device will act over the
output according to the length of the button press and to the current state.
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 t he 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. I n case of not
being the shutter in motion, pressing the button does not cause any action,
unless slats/lamellas have been parameterized – 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.
Disabled output: outputs disabled by parameter will not react to button
Regarding the lock, timer, alarm and scene functions, the device will beha ve under the
Test Off mode as usual. Button presses during this m ode 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 outputs t hrough
the on-board pushbuttons. Orders received through communication objects will be
ignored, with independence of the channel or the output they are addressed to.
Depending on whether the output has been parameterised as an individual output or as
part of a shutter channel, the reactions to the button presses will differ.
Individual output: short or long pressing the button will commute the on-off
state of the relay.
Shutter channel: 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.
Note: after leaving the Test On mode, the status objects will recover the
values they had prior to enter ing 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 move-down order, or by calibrating the
shutter position in the Test On mode u ntil it matches the status objects.
Disabled output: under the Test On mode, short and long presses will cause
the same effect for disabled outputs as for individual outputs (i.e., the relay
will switch its state).
The lock, timer, alarm and scene funct ions will not work while the de vice is under the
Test On mode. Status objects will not be sent to the bus, either.
Important: the device is factory delivered with all the output channels configured as
shutters (without slats), and with both manual modes (Test Off and Test On) enabled.
The Manual Control is conf i gured from the Configuration tab itself under Outputs.
The only two parameters are:
Figure 3. Manual Control
Manual Control: options are “Disabled”, “Only Test Mode Off”, “Only Test
Mode On” and “Both Test Mode Off and On” (default). 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 long-pressing the Prog/Test button.
Lock Manual Control: unless the above parameter has been “Disabled”, th e
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: 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: sets how the manual control should remain after the device
start-up (after an ETS download or a bus power failure): “Unlocked”,
“Locked” or “Last Value” (default; on the very first start-up, this will be
Unlocked).
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 66 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, 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 module in MAXinBOX 66” user manual
(available at the Zennio homepage, www.zennio.com) for detailed information about
the functionality and the configuration of the related parameters.
MAXinBOX 66 implements four Zennio thermostats which can be enabled and
configured independently.
Please refer to the specific “Zennio Thermostat in MAXinBOX 66” user manual
(available at the Zennio homepage, www.zennio.com) for detailed information about
the functionality and the configuration of the related parameters.
The Master Light function brings the option to monitor the state of up to 12 light
sources –or any other functionally-similar element whose state is transmitted through a
binary object– and, depending on those st ates, 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 neces sarily 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.
ETS PARAMETERISATION
Once the Master Light function has been enabled, a specific t ab will be included in the
menu on the left. This new parameter screen (Figure 25) contains the following options:
Number of State Objects: defines the number of 1-bit status objects
required. The minimum (and default) value is “1”, and the maximum is “12”.
These objects are called “[ML] Status Object n”.
Trigger Value: sets the value (“0”, “1” or “0/1”, being the latter the default
option) that will trigger, when received through “[ML] Trigger”, the master
action (the general switch-off or the courtesy switch-on).
General Switch-Off.
Delay: def ines a certain delay (once the t rigger has been received) before
the execution of the general switch-off. The allowed range is 0 to 255
seconds.
Binary Value: if checked, object “[ML] General Switch-off: Binary
Object” will be enabled, which will send one “0” whenever the general
switch-off takes o ff.
Scaling: if checked, object “[ML] General Switch-off: Scaling” will be
enabled, which will send a percentage value (configurable in “Value”)
whenever the general switch-off takes o ff.
Scene: if checked, object “[ML] General Switch-off: Scene” will be
enabled, which will send a scene run / save order (configurable in “Action”
and “Scene Number”) whenever the general switch-off takes off
HVAC: if checked, object “[ML] General Sw itch-off: HVAC mode” will be
enabled, which will send an HVAC thermostat mode value (configurable in
“Value”, being the options “Auto”, “Comfort”, “Standby”, “Economy” and
“Building Protection”) whenever the general switch-off takes o ff
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]
“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 partic ular meani ng
because of the specifications or restrictions from both the KNX standard or the application program itself.