MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
2
CONTENTS
Contents ........................................................................................................................................ 2
Document Updates ....................................................................................................................... 3
1 Introduction .......................................................................................................................... 4
1.1 MINiBOX 40 v2 ................................................................................................................. 4
1.2 Installation ........................................................................................................................ 5
1.3 Start-Up and Power Loss .................................................................................................. 6
2 Configuration......................................................................................................................... 7
2.1 General ............................................................................................................................. 7
2.2 Outputs............................................................................................................................. 9
2.3 Logic Functions ............................................................................................................... 10
2.4 Scene Temporisation ...................................................................................................... 11
2.5 Manual Control .............................................................................................................. 13
ANNEX I. Communication Objects............................................................................................... 18
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
4
1 INTRODUCTION
1.1 MINiBOX 40 v2
MINiBOX 40 v2 from Zennio is a versatile KNX actuator featuring a wide variety of
functions and four relay outputs for a variety of applications, such as controlling shutter
drives or a fan coil unit.
The most outstanding features are:
4 relay outputs, configurable as:
➢ Up to 2 independent shutter channels (with or without slats),
➢ Up to 4 individual ON/OFF outputs,
➢ Up to 1 two-pipe fan coil module where both the fan speed control and
the valve control are performed through relays,
➢ A combination of the above.
10 customisable, multi-operation logic functions.
Scene-triggered action control, with an optional delay in the execution.
Manual operation / supervision of the 4 relay outputs through the on-board
pushbuttons and LEDs.
Heartbeat or periodical “still-alive” notification.
Relay Switches Counter.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
5
1.2 INSTALLATION
MINiBOX 40 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 programme may be downloaded.
This device does not need any additional external power since it is entirely powered
through the KNX bus.
Figure 1. MINiBOX 40 v2. Elements
The main elements of the device are described next.
Prog./Test Pushbutton (4): 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 (1): output ports for the insertion of the stripped cables of the
systems being controlled by the actuator (see section 2.2). 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.
A1 A2
M
N
L
A1 A2
N
L
L1
L2
A1 A2
N
L1
L1
L2
L2
A1 A2
N
L
B1 B2
B2B1
1
4
2
3
6
5
1. Upper Outputs.
2. Prog./Test LED.
3. KNX Connector.
4. Prog./Test button.
5. Output Control button.
6. Output status LED indicator.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
6
1.3 START-UP AND POWER LOSS
During the start-up of the device, the Prog./Test 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 the fan coil outputs will switch
to the specific state configured in ETS (if any).
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
7
2 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 that is always available is General. From this screen
it is possible to activate/deactivate all the required functionality.
Figure 2. General
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.
Scene Temporization [disabled/enabled]: enables o disables the “Scene
Temporization” tab on the left menu. See section 2.4 for more details.
1
The default values of each parameter will be highlighted in blue in this document, as follows:
[default/rest of options].
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
8
Manual Control [disabled/enabled]: enables o disables the “Manual Control”
tab on the left menu. See section 2.5 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 (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).
Figure 4. Heartbeat (Periodical Alive Notification).
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 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
9
2.2 OUTPUTS
MINiBOX 40 v2 incorporates 4 relay outputs, each configurable as a:
Individual binary outputs, which allows an independent control of loads.
Shutter channels, which allow controlling the motion of shutters or blinds.
One fan coil module, which allows the control of the fan and the valve of
two-pipe fan coil units.
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 40 v2 product section at the Zennio homepage (www.zennio.com):
Individual outputs.
Shutter channels.
‘Relays’ fan coil. Note that MINiBOX 40 v2 is only compatible with two-pipe
fan coils and On/Off valves. Therefore, any references to four-pipe fan coils
and 3-Point valves do not apply to this device.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
10
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.
MINiBOX 40 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, 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 “Logic Functions” user manual, available within the MINiBOX 40
v2 product section at the Zennio homepage, www.zennio.com, for detailed information
about the functionality and the configuration of the related parameters.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
11
2.4 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 / shutter channel / fan coil module, in case of receiving an order to
execute one of them when a previous temporisation is still pending for that output /
channel / module, 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 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 5.
Figure 5. Scene temporisation
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 outputs where it has been configured.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
12
Figure 6. 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 / fancoil 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.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
13
2.5 MANUAL CONTROL
MINiBOX 40 v2 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.
Notes:
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 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 either an individual output, as a shutter channel or as a fan coil.
Individual output: a simple press (short or long) will make the output switch
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
14
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 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 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.
Fan Coil module: the behaviour will depend on whether a fan-labelled or
a valve-labelled button is pressed:
➢ Fan: for this type of buttons, it must be taken into account that there are
two types of control for the fan speed:
• Switching control: a short or long press will switch the relays to set the
selected speed, unless it matches the current speed – in such case all
the relays will be opened (speed 0). The associated LEDs will indicate
the state of the fan speed control relays (on = relay closed; off = relay
open).
• Accumulation control: a short or long press switch to the selected
speed, closing the relay associated with that speed, and also the relays
assigned to the lower speeds, unless it matches the current speed – in
such case all the relays will be opened (speed 0). The associated LEDs
will indicate the state of the fan speed control relays (on = relay closed;
off = relay open).
Note: the behaviour of the relays will depend on the parameterisation, i.e.,
on the number of fan speeds, and on the delay between switches.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
15
➢ Valve: a short or long press will switch the current status of the relay and
therefore of the valve. The LED will show the state of the relay anytime (on
= relay closed; off = relay open).
Disabled output: outputs disabled by parameter will not react to button
presses under the Test Off mode.
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 outputs through
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 parameterized 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 parameterized times.
For safety reasons, only one closed relay per shutter channel is allowed.
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 move-down order, or by calibrating the
shutter position in the Test On mode until it matches the status objects.
Fan Coil module: the behaviour is similar to that of the Test Off mode,
although in this case the three fan speeds are supposed available.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
16
Disabled output: short and long presses will switch the state of the
corresponding relay. In case this consists in closing the relay, then the
remaining relays of its block will open, for safety reasons.
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 outputs 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 all the outputs disabled, and with
both manual modes (Test Off and Test On) enabled.
ETS PARAMETERISATION
The Manual Control is configured from the Configuration tab itself under Manual
Control.
The only two parameters are:
Figure 7. Manual Control
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 long-
pressing the Prog/Test button.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
17
Manual Control Lock [enabled/disabled]: 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.
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
18
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 programme itself.
Number
Size
I/O
Flags
Data type (DPT)
Functional Range
Name
Function
1
1 Bit
C - - T -
DPT_Trigger
0/1
Reset 0
Voltage Recovery -> Sending of 0
2
1 Bit
C - - T -
DPT_Trigger
0/1
Reset 1
Voltage Recovery -> Sending of 1
3
1 Bit
I
C - W - -
DPT_Enable
0/1
Lock Manual Control
0 = Lock; 1 = Unlock
1 Bit
I
C - W - -
DPT_Enable
0/1
Lock Manual Control
0 = Unlock; 1 = Lock
4
1 Bit
C - - T -
DPT_Trigger
0/1
[Heartbeat] Object to Send '1'
Sending of '1' Periodically
5, 16, 27, 38
1 Byte
I
C - W - -
DPT_SceneControl
0-63; 128-191
[Ox] Scenes
0 – 63 (Execute 1 – 64); 128 – 191
(Save 1 – 64)
6, 17, 28, 39
1 Bit
I
C - W - -
DPT_BinaryValue
0/1
[Ox] On/Off
N.O. (0=Open Relay; 1=Close Relay)
1 Bit
I
C - W - -
DPT_BinaryValue
0/1
[Ox] On/Off
N.C. (0=Close Relay; 1= Open Relay)
7, 18, 29, 40
1 Bit
O
C R - T -
DPT_BinaryValue
0/1
[Ox] On/Off (Status)
0=Output Off; 1=Output On
8, 19, 30, 41
1 Bit
I
C - W - -
DPT_Enable
0/1
[Ox] Lock
0=Unlock; 1=Lock
9, 20, 31, 42
1 Bit
I
C - W - -
DPT_Start
0/1
[Ox] Timer
0=Switch Off; 1=Switch On
10, 21, 32, 43
1 Bit
I
C - W - -
DPT_Start
0/1
[Ox] Flashing
0=Stop; 1=Start
11, 22, 33, 44
1 Bit
I
C - W - -
DPT_Alarm
0/1
[Ox] Alarm
0=Normal; 1=Alarm
1 Bit
I
C - W - -
DPT_Alarm
0/1
[Ox] Alarm
0=Alarm; 1=Normal
12, 23, 34, 45
1 Bit
I
C - W - -
DPT_Ack
0/1
[Ox] Unfreeze Alarm
Alarm=0 + Unfreeze=1 => End Alarm
13, 24, 35, 46
1 Bit
O
C R - T -
DPT_State
0/1
[Ox] Warning Time (Status)
0=Normal; 1=Warning
14, 25, 36, 47
4 Bytes
I/O
C R W T -
DPT_LongDeltaTimeSec
-2147483648 - 2147483647
[Ox] Operating Time (s)
Time in Seconds
15, 26, 37, 48
2 Bytes
I/O
C R W T -
DPT_TimePeriodHrs
0 - 65535
[Ox] Operating Time (h)
Time in Hours
269
1 Byte
I
C - W - -
DPT_SceneControl
0-63; 128-191
[Shutter] Scenes
0 - 63 (Execute 1 - 64); 128 - 191
(Save 1 - 64)
270, 299
1 Bit
I
C - W - -
DPT_UpDown
0/1
[Cx] Move
0 = Raise; 1 = Lower
271, 300
1 Bit
I
C - W - -
DPT_Step
0/1
[Cx] Stop/Step
0 = Stop/StepUp; 1 = Stop/StepDown
1 Bit
I
C - W - -
DPT_Trigger
0/1
[Cx] Stop
0 = Stop; 1 = Stop
272, 301
1 Bit
I
C - W - -
DPT_Trigger
0/1
[Cx] Switched Control
0, 1 = Up, Down or Stop, Depending
on the Last Move
273, 302
1 Bit
I
C - W - -
DPT_Enable
0/1
[Cx] Lock
0 = Unlock; 1 = Lock
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
19
274, 303
1 Byte
I
C - W - -
DPT_Scaling
0% - 100%
[Cx] Shutter Positioning
0% = Top; 100% = Bottom
275, 304
1 Byte
O
C R - T -
DPT_Scaling
0% - 100%
[Cx] Shutter Position (Status)
0% = Top; 100% = Bottom
276, 305
1 Byte
I
C - W - -
DPT_Scaling
0% - 100%
[Cx] Slats Positioning
0% = Open; 100% = Closed
277, 306
1 Byte
O
C R - T -
DPT_Scaling
0% - 100%
[Cx] Slats Position (Status)
0% = Open; 100% = Closed
278, 307
1 Bit
O
C R - T -
DPT_Switch
0/1
[Cx] Rising Relay (Status)
0 = Open; 1 = Closed
279, 308
1 Bit
O
C R - T -
DPT_Switch
0/1
[Cx] Lowering Relay (Status)
0 = Open; 1 = Closed
280, 309
1 Bit
O
C R - T -
DPT_Switch
0/1
[Cx] Movement (Status)
0 = Stopped; 1 = Moving
281, 310
1 Bit
O
C R - T -
DPT_UpDown
0/1
[Cx] Movement Direction
(Status)
0 = Upward; 1 = Downward
282, 311
1 Bit
I
C - W - -
DPT_Switch
0/1
[Cx] Auto: On/Off
0 = On; 1 = Off
1 Bit
I
C - W - -
DPT_Switch
0/1
[Cx] Auto: On/Off
0 = Off; 1 = On
283, 312
1 Bit
O
C R - T -
DPT_Switch
0/1
[Cx] Auto: On/Off (Status)
0 = On; 1 = Off
1 Bit
O
C R - T -
DPT_Switch
0/1
[Cx] Auto: On/Off (Status)
0 = Off; 1 = On
284, 313
1 Bit
I
C - W - -
DPT_UpDown
0/1
[Cx] Auto: Move
0 = Raise; 1 = Lower
285, 314
1 Bit
I
C - W - -
DPT_Step
0/1
[Cx] Auto: Stop/Step
0 = Stop/StepUp; 1 = Stop/StepDown
1 Bit
I
C - W - -
DPT_Step
0/1
[Cx] Auto: Stop
0 = Stop; 1 = Stop
286, 315
1 Byte
I
C - W - -
DPT_Scaling
0% - 100%
[Cx] Auto: Shutter Positioning
0% = Top; 100% = Bottom
287, 316
1 Byte
I
C - W - -
DPT_Scaling
0% - 100%
[Cx] Auto: Slats Positioning
0% = Open; 100% = Closed
288, 317
1 Bit
I
C - W T U
DPT_Scene_AB
0/1
[Cx] Sunshine/Shadow
0 = Sunshine; 1 = Shadow
1 Bit
I
C - W T U
DPT_Scene_AB
0/1
[Cx] Sunshine/Shadow
0 = Shadow; 1 = Sunshine
289, 318
1 Bit
I
C - W T U
DPT_Heat_Cool
0/1
[Cx] Cooling/Heating
0 = Heating; 1 = Cooling
1 Bit
I
C - W T U
DPT_Heat_Cool
0/1
[Cx] Cooling/Heating
0 = Cooling; 1 = Heating
290, 319
1 Bit
I
C - W T U
DPT_Occupancy
0/1
[Cx] Presence/No Presence
0 = Presence; 1 = No Presence
1 Bit
I
C - W T U
DPT_Occupancy
0/1
[Cx] Presence/No Presence
0 = No Presence; 1 = Presence
291, 292, 320, 321
1 Bit
I
C - W - -
DPT_Alarm
0/1
[Cx] Alarm x
0 = No Alarm; 1 = Alarm
1 Bit
I
C - W - -
DPT_Alarm
0/1
[Cx] Alarm x
0 = Alarm; 1 = No Alarm
293, 322
1 Bit
I
C - W - -
DPT_Ack
0/1
[Cx] Unfreeze Alarm
Alarm1 = Alarm2 = No Alarm +
Unfreeze (1) => End Alarm
294, 323
1 Bit
I
C - W - -
DPT_Scene_AB
0/1
[Cx] Move (Reversed)
0 = Lower; 1 = Raise
295, 324
1 Bit
I
C - W - -
DPT_Ack
0/1
[Cx] Direct Positioning 1
0 = No Action; 1 = Go to Position
296, 325
1 Bit
I
C - W - -
DPT_Ack
0/1
[Cx] Direct Positioning 2
0 = No Action; 1 = Go to Position
297, 326
1 Bit
I
C - W - -
DPT_Ack
0/1
[Cx] Direct Positioning 1 (Save)
0 = No Action; 1 = Save Current
Position
298, 327
1 Bit
I
C - W - -
DPT_Ack
0/1
[Cx] Direct Positioning 2 (Save)
0 = No Action; 1 = Save Current
Position
618
1 Byte
I
C - W - U
DPT_SceneControl
0-63; 128-191
[Fan Coil] Scenes
0 - 63 (Execute 1 - 64); 128 - 191
(Save 1 - 64)
619
1 Bit
I
C - W - U
DPT_Switch
0/1
[FCx] On/Off
0 = Off; 1 = On
MINiBOX 40 v2
http://www.zennio.com Technical Support: http://support.zennio.com
20
620
1 Bit
O
C R - T -
DPT_Switch
0/1
[FCx] On/Off (Status)
0 = Off; 1 = On
621
1 Bit
I
C - W - U
DPT_Heat_Cool
0/1
[FCx] Mode
0 = Cool; 1 = Heat
622
1 Bit
O
C R - T -
DPT_Heat_Cool
0/1
[FCx] Mode (Status)
0 = Cool; 1 = Heat
623
1 Bit
I
C - W - U
DPT_Enable
0/1
[FCx] Fan: Manual/Automatic
0 = Automatic; 1 = Manual
1 Bit
I
C - W - U
DPT_Enable
0/1
[FCx] Fan: Manual/Automatic
0 = Manual; 1 = Automatic
624
1 Bit
O
C R - T -
DPT_Enable
0/1
[FCx] Fan: Manual/Automatic
(Status)
0 = Automatic; 1 = Manual
1 Bit
O
C R - T -
DPT_Enable
0/1
[FCx] Fan: Manual/Automatic
(Status)
0 = Manual; 1 = Automatic
625
1 Bit
I
C - W - U
DPT_Step
0/1
[FCx] Manual Fan: Step Control
0 = Down; 1 = Up
626
1 Bit
I
C - W - U
DPT_Switch
0/1
[FCx] Manual Fan: Speed 0
0 = Off; 1 = On
627
1 Bit
I
C - W - U
DPT_Switch
0/1
[FCx] Manual Fan: Speed 1
0 = Off; 1 = On
628
1 Bit
I
C - W - U
DPT_Switch
0/1
[FCx] Manual Fan: Speed 2
0 = Off; 1 = On
629
1 Bit
I
C - W - U
DPT_Switch
0/1
[FCx] Manual Fan: Speed 3
0 = Off; 1 = On
630
1 Bit
O
C R - T -
DPT_Switch
0/1
[FCx] Fan: Speed 0 (Status)
0 = Off; 1 = On
631
1 Bit
O
C R - T -
DPT_Switch
0/1
[FCx] Fan: Speed 1 (Status)
0 = Off; 1 = On
632
1 Bit
O
C R - T -
DPT_Switch
0/1
[FCx] Fan: Speed 2 (Status)
0 = Off; 1 = On
633
1 Bit
O
C R - T -
DPT_Switch
0/1
[FCx] Fan: Speed 3 (Status)
0 = Off; 1 = On
634
1 Byte
I
C - W - U
DPT_Fan_Stage
0 - 255
[FCx] Manual Fan: Enumeration
Control
S0 = 0; S1 = 1; S2 = 2; S3 = 3
1 Byte
I
C - W - U
DPT_Fan_Stage
0 - 255
[FCx] Manual Fan: Enumeration
Control
S0 = 0; S1 = 1; S2 = 2
1 Byte
I
C - W - U
DPT_Fan_Stage
0 - 255
[FCx] Manual Fan: Enumeration
Control
S0 = 0; S1 = 1
635
1 Byte
O
C R - T -
DPT_Fan_Stage
0 - 255
[FCx] Fan: Speed Enumeration
(Status)
S0 = 0; S1 = 1; S2 = 2; S3 = 3
1 Byte
O
C R - T -
DPT_Fan_Stage
0 - 255
[FCx] Fan: Speed Enumeration
(Status)
S0 = 0; S1 = 1; S2 = 2
1 Byte
O
C R - T -
DPT_Fan_Stage
0 - 255
[FCx] Fan: Speed Enumeration
(Status)
S0 = 0; S1 = 1
636
1 Byte
I
C - W - U
DPT_Scaling
0% - 100%
[FCx] Manual Fan: Percentage
Control
S0 = 0%; S1 = 0,4-33,3%; S2 =
33,7-66,7%; S3 = 67,1-100%
1 Byte
I
C - W - U
DPT_Scaling
0% - 100%
[FCx] Manual Fan: Percentage
Control
S0 = 0%; S1 = 1-50%; S2 = 51-
100%
1 Byte
I
C - W - U
DPT_Scaling
0% - 100%
[FCx] Manual Fan: Percentage
Control
S0 = 0%; S1 = 1-100%
637
1 Byte
O
C R - T -
DPT_Scaling
0% - 100%
[FCx] Fan: Speed Percentage
(Status)
S0 = 0%; S1 = 33,3%; S2 = 66,6%;
S3 = 100%
1 Byte
O
C R - T -
DPT_Scaling
0% - 100%
[FCx] Fan: Speed Percentage
S0 = 0%; S1 = 1-50%; S2 = 51-
Page is loading ...
Page is loading ...
Page is loading ...
-
1
-
2
-
3
-
4
-
5
-
6
-
7
-
8
-
9
-
10
-
11
-
12
-
13
-
14
-
15
-
16
-
17
-
18
-
19
-
20
-
21
-
22
-
23
Ask a question and I''ll find the answer in the document
Finding information in a document is now easier with AI
Related papers
-
Zennio ZIO-MN20 Owner's manual
-
Zennio ZIOMN25V2 Owner's manual
-
Zennio ZIO-MN25 Owner's manual
-
Zennio ZIO-MN40 Owner's manual
-
Zennio ZCLFB230C1 Owner's manual
-
Zennio ZIO-RQUAD8 Owner's manual
-
Zennio ZIOIB24VT Multifunction Actuator for Flush Mounting User manual
-
Zennio ZIOIB24V2 Owner's manual
-
Zennio ZIO-IB20 Owner's manual
-
Zennio ZPR1612 Owner's manual
Other documents
-
König CS80MMFAN Datasheet
-
-
-
-
Elsner Leak KNX 2.0 User manual
-
Elsner Cala KNX IL User manual
-
Sinclair KNX-01 User manual
-
Elsner KNX S1-B2 230 V Installation And Adjustment
-
Elsner KNX S4-B12 24 V User manual
-
Mean Well KAA-8R-10S User manual
