Supported devices 39
For datapoint type 3.007 (Control Dimmer), the coding is:
- 0: Decrease break.
- 1 .. 7: Decrease with step 1 to 7.
- 8: Increase break.
- 9 .. 15: Increase with step 1 to 7.
For datapoint type 3.008 (Control Blinds), the coding is similar but with Up and Down instead of Decrease and Increase.
KNX events and commands
ML Gateway generates an event whenever a group address is written to, provided the datapoint type written is 2 Bytes or less in size. An event can
be defined for a specific value set to the group address. If any of the bits is 1, then a TRUE event will be generated. Otherwise, a FALSE event will
be issued. For the common datapoint types:
- Boolean: TRUE or FALSE event, depending on the value received.
- Integer (1 or 2 Bytes): TRUE event if the value received is not 0, FALSE if 0.
! Commands can write any of the possible values to a group address.
IHC Control: Lauritz Knudsen (LK), Schneider LexControl and ELKO Living system
IHC/LexControl programming model consists of physical input and output devices plus function blocks. Function blocks implement the
programming of the system, and the interface between the programming and the actual components is made by linking physical input signals to
function block inputs, and function block outputs to actuators (dimmers, shade controllers, etc.).
The web-based user interface for the controller (LK IHC Visual software) saves all programming and setup in an XML file with the extension .VIS.
This file must be provided to ML Gateway in order to define the list of resources. Once this file is loaded into ML Gateway, all relevant resources are
selectable.
Resources available for generating events on ML Gateway are physical input signals and function block outputs.
Commands are always a logical pulse (True followed by False) on function block inputs. This way, all programming (scenarios, etc.) is implemented
by means of function blocks that can be executed by ML Gateway.
The Visual project file is absolutely necessary, since there is no way to inspect all of the events occurring on the controller. Therefore, monitoring
information will only be available for already defined resources.