Replace Device

This article covers the following topics:

• Purpose
• Activation
• Use of the Replace Device app in ETS
• Background information

Purpose

The Replace Device app allows replacing KNX devices in a project without losing the device properties. This is possible for devices with similar functionality, regardless of the manufacturer. The most common use cases are:

• Expansion: An existing device function shall be expanded, for example, by two additional channels.
• Replacement: An original device is no longer available, so it must be replaced with a functionally equivalent device from the same manufacturer or from a different one.

Activation

Follow these instructions in order to activate this app in ETS:

• Purchase a Replace Device license from MyKNX
• License it as explained here
• No additional *.etsapp file needs to be installed

Use of the Replace Device app in ETS

The following steps shall be followed for a device replacement:

1. Select the device to be replaced

Select at least one device to be replaced (i.e. original device) and invoke the app. In order to be able to perform a replacement for several devices in one go, all the device applications should be identical. If this is not the case, then the process shall be repeated respectively.

2. Select a template

Once the device is selected click 'Next'. This opens the replacement selection dialog allowing to select a new device from the list (the replacement device to be used as a template). This will be used to replace the original devices selected under point 1 with the replacement device.

All devices from any open project are displayed here. The devices from the currently open project are by default shown. To change the project click the dropdown 'From this open project'. The search field makes it possible to search for replacement devices.

The following logic is used for displaying the devices in the list:

• The original device selected is also displayed (the destination and the source are identical; use case: swap channels A <-> B).
• Devices without an Application Program are not shown (e.g. power supplies).
• Devices with collection objects are not shown.
• If the original device(s) have Group Objects, the replacement devices should also have Group Objects.
• If the original device(s) do not have any Group Objects, the replacement devices do not necessarily have to be without Group Objects. If they have, they will not be assigned.

3. Define the assignments (mapping)

Make the assignment of Group Objects between the original and the replacement device in the wizard and click 'Finish'.

The Group Objects that are displayed here require mapping (i.e. only visible Group Objects with at least one Group Address assigned). The mapping can be realized by clicking the 'Replacement object' and then the corresponding 'Available target object'. Once the mapping is of a Group Object is done, the  icon is shown on the 'Available target object'. To remove the mapping one has to click the  icon on the 'Replacement object'. The following conditions apply:

• Every original Group Object can be linked with a maximum of one replacement Group Object.
• The original and the replacement Group Objects should have the same bit size.

File Templates

Any completed mapping can be saved as a template per device by clicking the 'Save' button; it can, later on, be loaded as a template via the 'Load' button.

File templates contain various sections, each having an mapping between the original Group Object and a replacement Group Object.

The logic for a mapping from a file is respective to that of the automatic mapping. If a match is found in the file for a Group Object which is to be replaced, it is mapped automatically. If not, the field remains blank and shall be assigned manually.

In principle, any template can be used for any replacement device, regardless of whether or not the mapping makes sense.

Background information

Device properties