/
EWPM (EN)

EWPM (EN)

Extension for a KNX / EIB connection

The heat pump manager can be used as an accessory EWPM extension can be integrated into a KNX bus system.

New!
The documentation "Room temperature control Smart-RTC +" is now available for describing the room temperature, room humidity and target room temperature via the KNX extension. "

EWPM extension

Order reference

EWPM
(Discontinued at the end of 2017,
Will be replaced in the 1st quarter of 2018 by KNX WPM)

item number

356970
(Discontinued at the end of 2017,
Will be replaced in the 1st quarter of 2018 by 376350)

Operating conditions

-20 to 60 ° C
<85% RH

Cable sizing

0.2 to a maximum of 1.5 mm²; YCYM 1x2x0.8 mm²

Can be used with

WPM 2006 / R
WPM 2007 / R
WPM EconPlus / R
WPM Econ5

Available for

ETS3 / ETS4 / ETS5

Function overview

With the available as an accessory EWPM extension it is possible to integrate a Dimplex heat pump with a heat pump manager into a KNX bus system. Values for up to 110 group addresses can be sent from the heat pump manager to the KNX bus system or sent from the KNX bus system to the heat pump manager. Among other things, it is possible to read out the status, the operating data or the history in order to visualize this later on the KNX level. The operating mode, the target hot water temperature or the heating curve could also be changed.

New:
Should the function of the intelligent room temperature control Smart-RTC + be used despite the existing KNX room sensors? From the heat pump manager software WPM_L23.1, it is possible to send the room temperature, room humidity and target room temperature of up to 10 rooms with KNX room sensors from the KNX bus to the heat pump manager. Further information and descriptions are given in the chapter Room temperature control Smart-RTC + made available.

System requirement

The minimum system requirement for using the EWPM extension is a Dimplex heat pump with heat pump manager WPM 2006, WPM 2007 or WPM EconPlus from software version H_H50 and higher. For the programming a PC with ETS3, ETS4 or ETS5 software (not included), a Project file, the "KSet" programming tool and a Data point list needed.

installation

ATTENTION
Before opening the device, all circuits must be disconnected from the power supply. All electrical connection work may only be carried out by a qualified electrician or a specialist for specified activities in compliance with the installation and operating instructions.

The installation of the EWPM extension takes place on the heat pump manager in the designated slot “Serial Card / BMS Card”. The following steps are carried out:

  • De-energize the heat pump manager

  • Remove the cover of the “Serial Card / BMS Card” slot with a small screwdriver

  • Remove the cover of the “Serial Card / BMS Card” slot with a small screwdriver

  • Installation of the EWPM extension

  • Breaking out the existing cover

  • Close the opening with the cover

 

 

  • Supply the heat pump manager with voltage

Electrical connection

The EWPM extension is connected to the KNX bus using the enclosed terminal. The device is supplied with power via the KNX bus. It should be noted that a new EWPM extension does not have a physical address owns and before programmed must become.

Heat pump manager settings

Depending on the software version of the heat pump manager, the following settings must be checked and, if necessary, adjusted:

Software version

menu

Submenu

Setting value

Software version

menu

Submenu

Setting value

from WPM_H

Modem -> with the key combination «menu"+"Enter" Select

protocol

Modbus

baud rate

9600

address

001

from WPM_L

Network -> with the key «menu" Select

protocol

EIB / KNX

from WPM_L20.2

Network -> with the key «menu" Select

protocol

EIB / KNX

Address range

1..127

from WPM_L23.1

Network -> with the key «menu" Select

protocol

EIB / KNX

Address range

1..207

Import device into ETS

The EWPM extension is integrated into the ETS by importing a Project file. In the Project file the device "EWPM Plugin" is included. After the successful import, the physical address programmed and the project-related XML file Loading.

NOTE
Before a bus monitor or communication with another application can be started, communication with the device must first be established! If this is not the case, the error message appears: "Verify connection cable and restart procedure"

Bus communication error

Import project file ETS3

The EWPM extension is imported into the ETS3 with the help of the * .pr4 project file.

  • Import project

  • Select the path to the file to be imported

  • Select the project to be imported

  • Open / manage project

  • Select and open a project

  • Device in the project

Import project file ETS4

The EWPM extension is imported into the ETS4 using the * .knxproj project file.

  • Import project

 

  • Select the path of the file to be imported

  • Choose a file

  • Imported file selected

  • Select project

  • Import selected project

  • Project imported successfully

 

Import project file ETS5 (chapter in progress)

Import project file ETS5.5.2

The EWPM extension is imported into the ETS5.5.2 with the help of the * .knxproj project file.

  • Activate the Compatibility Mode app

  • Import project

 

  • Select the path of the file to be imported

 

  • Start import

  • Project imported successfully

  • Project available in the project selection

Physical address

In order to program the physical address via the ETS, the programming button on the EWPM extension must be pressed. Then the green LED starts to light up. This goes out when the device has successfully received the physical address from the ETS.

Program communication EWPM <-> KNX bus

An XML file is required for communication between the KNX bus and the heat pump manager. This XML file must be created and adapted according to the relevant system parameters and customer requirements. The program KSet needed.

Programming tool KSet

After installing and opening KSet it is recommended to use the attached file Example.xml to open. In Example.xml the most common standard addresses are preset at the factory.

First of all, the system-specific addresses to be transmitted should be specified. The main / middle and subgroups are then created in the ETS for the addresses. Means KSet the XML file is now edited. The following figure shows the structure of the XML file in KSet shown. The individual columns are described in the following table.

split

description

split

description

Group

As in the associated ETS project, the main, middle and subgroups must be entered.

Surname

The description is optional. However, it is recommended to enter a meaningful name.

Datapoint typ*

The data point type of the desired data point must be entered.

IN / OUT*

IN: The value is sent from the KNX bus to the heat pump manager.
OUT: The value is sent from the heat pump manager to the KNX bus.

index*

The index of the desired data point must be entered.

COIL / REG*

The type of data point required must be entered.

COIL: Digital
REG: register

Conversion Rule*

If necessary, a corresponding conversion rule must be entered.

Conversion Value*

If necessary, a corresponding conversion factor must be entered.

*NOTE
The required data is in the Data point list contain.

Loading the XML file at ETS3 (in progress)

Loading the XML file with ETS4

After the user-specific XML file has been created, it must be loaded into the device for communication between the KNX bus and the heat pump manager.

  • Select device

  • "Edit" menu - select "Edit parameters"

  • Selection window appears

  • "Choose XML file" - select the XML file to be imported

  • "Download data" - Load XML file

  • "Confirmation request" - If the security question appears, this is confirmed with "Yes"

  • XML file was imported successfully, the selection window can be closed

 

 

Loading the XML file with ETS5 (in progress)

Loading the XML file with ETS5.5.2

After the user-specific XML file has been created, it must be loaded into the device for communication between the KNX bus and the heat pump manager.

  • Select device

  • Select "Parameter" - "Open product-specific parameter dialog"

  • Selection window appears - "Choose XML file"

  • Select the XML file to be imported

  • "Download data" - Load XML file

  • "Confirmation request" - If the security question appears, this is confirmed with "Yes"

  • XML file was imported successfully, the selection window can be closed

 

 

Data point list

The data point lists listed in the following tables contain the most frequently used addresses. The tables are subdivided according to the menus contained in the heat pump manager. The following examples deal with addresses that have some special features and must be explained separately.

Data points that can be written via the KNX bus are marked with "IN", those that deliver values to the KNX bus are marked with "OUT".

NOTE
With the current firmware of the EWPM extension, no values can be read via the KNX bus. The values are sent to the KNX bus cyclically or when the value changes!

Operating data

Surname

Datapoint
Type

IN / OUT

index

COIL / REG

Conversion Rule

Conversion Value

DPT

R / W

Unit

WPM J / L software

WPM H software

Outside temperature (R1)

16 bit float

OUT

1

27

register

None

 

9.001

R.

° C

Return temperature (R2)

16 bit float

OUT

2

29

register

None

 

9.001

R.

° C

Set return temperature

16 bit float

OUT

53

28

register

None

 

9.001

R.

° C

Hot water temperature (R3)

16 bit float

OUT

3

30th

register

None

 

9.001

R.

° C

Flow temperature (R9)

16 bit float

OUT

5

31

register

None

 

9.001

R.

° C

Heat source inlet (R24) *

16 bit float

OUT

6th

-

register

None

 

9.001

R.

° C

Heat source outlet (R6)

16 bit float

OUT

7th

41

register

None

 

9.001

R.

° C

Temperature 2nd heating circuit (R5)

16 bit float

OUT

9

33

Rechtliche Bedingungen / Legal Terms | Impressum / Imprint