At the time of writing this - this was the most complex setup that I had undertaken. So on this page I am describing a process of commissioning the air-conditioner with the KLIC-DI - as that's the intent at this point in time - I'm going to walk before I can run. In a subsequent page I intend to describe how this can be further integrated to control dampers in zones throughout the house. As part of the commissioning process I will make use of a Z41 device to control and monitor the air-conditioner. This control functionality will be refined at a later stage.
As a novice at this process (fortunately guided by an experienced integrator) I am not 100% certain what the air-conditioner itself is capable of, nor exactly what the KLIC-DI can get the air-conditioning unit to do. However, having said that I think I have enough of an idea to complete the commissioning stage. So here's what I understand the air-conditioner is capable of and what I will setup the KLIC-DI to control.
turn the air-conditioner on and off,
set the mode of the air-conditioner - this could be to heat, cool, fan, dry or auto - however this will be simplified so that we just tell the air-con to either heat or cool,
set the fan speed - the KLIC-DI has the ability to be set to control either 2 or 3 levels of fan speed - and as our unit supports 3 speed that's what I'll use,
set the temperature - now this is where I'm ot least clear on how this will function - unlike a wall mounted split system we have multiple zones where we can read the temperature from within the house and how this integrates with the temperature we set the air-conditioner to is something I'm still trying to fully understand. However, for the commissioning process this shouldn't be too much of an issue as I just want to make sure the KLIC-DI will send the basic commands to control the unit - and then I'll work out the rest later.
the KLIC-DI can control 'swing' which is not something required or supported by this ducted unit (and I assume any ducted unit).
During the commissioning process the KLIC-DI will be run as a slave control. (It's likely the Daikin remote supplied can only run in Master mode and as such will remain connected only for the commissioning process. After this it is disconnected and the KLIC-DI will be set to run as master control.)
Parameter Setup
The following images show the parameter Setup I used for the KLIC DI. I've highlighted a few of the settings, which were significant at this stage. There were some other changes from the default (including setting the fan to have 3 levels).
Group objects
The following images show the group objects for the KLIC DI. The image shows that these have already been linked to group addresses. It's worth looking at these in a little more detail.
On/Off - there is both a W (writable) group address for turning air-conditioner off, and a status for this.
Temperature - there are 3 group objects associated with temperature - the first is a W (writable) address for setting the "setpoint", the second is to read the setpoint, and the third is to read the Internal Temperature (which I gather is the temperature that the air-conditioner is reading on it's inlet (or both or some funtion of both).
Mode - there are 4 group objects associated with mode. If we refer to the parameters above we can see that we selected simplified mode - doing so means group objects for 'simplified mode' setting and status become available. Interestingly the group object for setting a status for the more complex set of modes (Aut, Ht, Cool, Fan and Dry) are both still there as well.
Fan - we can also set and read the status of the fan, with a further group object allowing to increment the fan up or down.
Error - finally there are some error group objects
Note: there is a 4th group object known as the reference temperature when the KLIC-DI is set to be the master. This is not required in the initial commissioning phase, but will be used later. I've created a separate page which describes more detail about all the temperature group objects and aspects related to the reference temperature here: Temperature Group Objects for KLIC-DI and Daikin.
As part of the commissioning process the Z41 will be used to test control and monitoring of the air-conditioner. A page on the Z41 will be setup to do this.
Parameter Setup and Associated Group Objects
The following images show the parameters on the Z41 related to the air-conditioner control. A page is created with 6 boxes which subsequently assigned settings. The group objects relating to each Box has been immediately shown with each of the box settings.
So after this settings page/box settings were placed on the Z41 I took a picture of how it appeared. At this point KLIC-DI was not functioning. However, some of the boxes/buttons on the Z41 were responsive.
It can be seen (from settings and group objects above) that box 3 and box 6 have a single writable group object and as such will only display accurate details once the KLIC-DI is operational.
For reasons that are not totally clear to me buttons/boxes 1 (climate), 2 (mode) and 4 (setpoint) respond when the buttons are pressed and update the displayed state. For example pressing the + button for setpoint increases the displayed temperature. Given the KLIC-DI was not operational at this point I would assume the the internal operation of the box is to adjust the details immediately and also to update when the appropriate group address is received. However, in the absence of a group address being received the box seems happy enough to display what it has told the KLIC-DI to set the setpoint to.
Interestingly the fan speed must be implemented somewhat differently as pressing the + and - buttons for box 5 doesn't change the displayed speed. Anyway - so far so good. Once the KLIC-DI is connected to the air-conditioner and the KNX bus these buttons should operate with some greater legitimacy.
The buttons on the Z41 are now linked to the functions I intend to test during commissioning. I've included the full list provided to me by the integrator. This list includes some functionality that is either not available (e.g. swing) and other functionality that will not be part of the commissioning process. However, I list every group address with connected group objects below for every group address that has at least a single group object assigned.