Actions

KNX

From trivum

Contents

Setup and Network Configuration

General

  • Use KNX IP router, NOT KNX Interfaces (see KNX IP router vs. KNX Interface)
  • Avoid any wireless connections. Use cable connections! (Often WLAN access points do NOT pass through multicast messages which are strictly required for KNX events.)
  • Connect the KNX IP router to trivum as direct as possible.

Example:

                  [internet]
                      |
                   [router]
                      |
           +----------+-----------+
           |                      |
        [switch]             other LAN devices
          |  |
     KNX-IP  trivum
     Router  server

KNX IP Router

KNX IP routers often support two operation modes to run as an Interface or Router.
Therefore make sure to configure the router to use routing mode
  • Check the run mode.
    The device must run as a router!
  • Check the IP address.
    Only if the device is running as a router you will see an address like 224.0.23.12
  • Check filter settings.
    By default, routers block many messages, and this must be changed.

Example Settings for Siemens N 146 IP Router:

  Parameters
   General
     Support of unconfigured interfaces: enabled
     Monitoring of bus voltage failure : enabled
   Routing (Bus > IP)
     Group telegrams of main groups 0 to 13 : transmit all (for testing)
     Group telegrams of main group 14 and 15: transmit all
     Individually addressed and broadcast telegrams: filter (normal)
     Telegram confirmation of group oriented telegrams: only if routed
   Routing (IP > Bus)
     Group telegrams of main groups 0 to 13 : transmit all (for testing)
     Group telegrams of main group 14 and 15: transmit all
     Individually addressed and broadcast telegrams: filter (normal)
   IP Config 1
     IP Address Assignment:  by DHCP Server
     IP Routing Multicast Address
        Byte 1 [224 ... 239] : 224
        Byte 2 [0 ... 255]   : 0
        Byte 3 [0 ... 255]   : 23
        Byte 4 [0 ... 255]   : 12
  Commissioning
   Address : 1.1.22

KNX IP Router vs. KNX Interface

Use a KNX IP Router (e. g. Siemens N146), but do NOT use a KNX Interface (e. g. Siemens N148)

The differences are:

Interface
Has ONLY a normal IP address, e. g. 192.168.1.100, to communicate only with ONE client at a time.
Router
Has also a multicast IP address, by default 224.0.23.12.
Can communicate with any number of clients in parallel. There is also a "normal" IP address, which is however not used in most cases.
KNX Interfaces are NOT useful for trivum systems.
Use KNX IP Router instead.

Multiple KNX IP Router

If there are two routers in the network they will use different communication addresses, typically 224.0.23.12 and 224.0.23.13. To configure the correct router for communication, go to the following places:

C4 server with V8

  1. Open the Multiroom Setup Tool
  2. Click System β†’ KNX Setup
  3. Enter a new IP address in the KNX/IP communication address input field
  4. Click Admin β†’ Quick restart
β†’ The server restarts automatically.

AudioBox

  1. Open the Multiroom Setup Tool
  2. Click System β†’ KNX Setup
  3. Enter a new IP address in the KNX/IP communication address input field
  4. Click Admin β†’ Quick restart
β†’ The server restarts immediately.

trivum Controller / MusicCenter Server

Activate KNX

If you want to control trivum through KNX devices, or vice versa,
then configurations can be done at these places:
 Audio Actuator or Pro Line with MusicCenter V8:
 -  System / KNX Setup:
    Select router, enable bus communication trace.
    To see KNX I/O traces, close the dialog then
    select "Developer" at right top and "KNX Trace".
 -  Zones / zone name / KNX Settings:
    Configure simple actions per KNX message.
    Control zone on/off/mute, volume, skip track,
    and send diverse other commands into a zone from KNX.
    See also: KNX Events for more complex actions.
 -  Macros:
    Send 1-bit, 8-bit or 14-character data to KNX
    through self defined command sequences.
 -  KNX Displays:
    Send status infos like current artist or album,
    track title, time to a KNX Display.
 -  KNX Events:
    Configure actions on incoming KNX messages like:
    select a specific source, play an artist/album,
    control a zone (on/off/mute/volume/next source),
    multikey commands like next/prev. track,
    play/pause or device specific commands.
 C4 or X3 with MusicCenter V7:
 -  Addons / KNX / Businterface:
    Select router, enable bus communication trace.
    Select "Developer" at right top for trace outputs.
 -  Addons / KNX / Displays:
    Send status infos like current artist or album,
    track title, time to a KNX Display.
 -  Addons / KNX / Audio:
    Addons / KNX / Sensors:
    Control zone sources, mute, volume, skip track,
    and send diverse other commands into a zone from KNX.
 -  Macros:
    Send 1-bit, 8-bit or 14-character data to KNX
    through self defined command sequences.


If you want to use KNX at server side:

System V7:

  1. Open the server's configuration web GUI
  2. Click Addons β†’ KNX β†’ Businterface
  3. Make sure Use EibnetIP for EIB access is activated
  4. Configure Businterface at server side like:
    Use EibnetIP for EIB access: yes
    Interface device address   : 1.1.199
    Eibnet Routing Mode        : yes
    Communication speed        : Fast
    Trace bus communication    : yes

System V8:

  1. Open the Multiroom Setup Tool
  2. Click System β†’ KNX Setup
  3. Make sure Use EibnetIP for EIB access is activated
  4. Configure at server side like:
    Use EibnetIP for EIB access : yes
    KNX/IP communication address: xxx.xxx.xxx.xxx
    trivum KNX device address   : 1.1.199
    Trace bus communication     : yes
    GA scene save/restore       : x/x/x

Deactivate KNX

While KNX is active, trivum components will send occasional KNX search requests to the KNX IP router. If you don't want to use KNX in your project, you may disable it this way:

  1. Open the server's configuration web GUI
  2. Go to Addons β†’ KNX β†’ Businterface
  3. Uncheck Use EIBNet

trivum TouchPad

Activate KNX

On the TouchPad...

  1. Press the trivum icon (upper right corner) to open the System Menu.
  2. Press Info.
  3. Scroll down the table Informations.
    β†’ If you see a button Show KNX events, then KNX is already active.
    β†’ If you see no button Show KNX events continue.
  4. Press Special settings
  5. Manually enter
    knx on

β†’ KNX is now activated on the TouchPad.

Configure KNX

  1. Open the Multiroom Setup Tool of the TouchPad
  2. Click TouchPad Settings
  3. In the input field KNX device address, manually set an IP.
(Default is 1.1.199)

Usually, several TouchPads can use the same device address.

Other KNX devices on the KNX bus MUST NOT use the same device address as the trivum TouchPads!
Make sure that the addresses of the other KNX devices differ from the TouchPads!
  1. also check if your IP router uses multicast address 224.0.23.12 for communication. if not enter the correct address at "KNX broadcast address". For example, with two routers the second one usually uses 224.0.23.13.

Test KNX

Precondition:

KNX is activated on the TouchPad and correctly configured. The TouchPad needs to receive KNX data. To check this:

On the TouchPad...

  1. Press the trivum icon (upper right corner) to open the System Menu.
  2. Press Info.
  3. Scroll down the table Informations.
  4. Press Show KNX events.

β†’ If any messages from the KNX IP router appear in the left area Busmonitor, then the KNX settings are ok.

If these preconditions are fulfilled:

  1. Create a simple light object in the TouchPad, with only one group address for on/off.
  2. Within the ETS software, open the group monitor.
  3. Check if your light can be toggled by commands from the ETS.
  4. Toggle the light in the TouchPad GUI.

β†’ KNX messages should appear in the ETS group monitor.

If not:

  • Check again the router configuration within ETS, especially the filter settings.
  • Reprogram the router again, because it can be possible that the values are listed in ETS, but someone forgot to actually program them into the router.

β†’ If the light can still not be switched:

  • Check the KNX network for bus couplers and their programming. They also have some filter settings.
  • Check and correct them, and reprogram them multiple times by ETS.

Deactivate KNX

While KNX is active, trivum components will send occasional KNX search requests to the KNX IP router. If you don't want to use KNX in your project, you may disable it this way:

On the TouchPad...

  1. Press the trivum icon (upper right corner) to open the System Menu.
  2. Press Info.
  3. Scroll down the table Informations.
  4. Press Special settings.
  5. Enter:
    knx off

β†’ KNX is now deactivated on the TouchPad.

KNX Data Points

This is a list of all possible KNX inputs and outputs with a trivum Server V8 (Actuator / Pro Line), Server V7, and TouchPad.

Server with Software V8 (Actuator, ProLine)

Zones / zone name / KNX
action KNX - trivum
Control zone-status and zone-volume by KNX
set zone on/off 1 bit β†’
set zone mute 1 bit β†’
set zone volume 4 bit β†’
set zone volume 1 byte β†’
Push zone-status and zone-volume to KNX
push on/off status to bus ← 1 bit
push mute status to bus ← 1 bit
push volume to bus ← 1 byte
Control current source by KNX
skip to next/previous source 1bit β†’
send ">" command to source 1 bit β†’
send "<" command to source 1 bit β†’
send ">>" command to source 1 bit β†’
send "<<" command to source 1 bit β†’
Special controls
include/exclude in scene 1 bit β†’
run any command 2 bytes β†’
Macros / macro name / Steps / send KNX command
action KNX - trivum
send 1 bit, 1 byte, or 14 chars text ←
KNX Displays
action KNX - trivum
set display page ← 1 byte
set display icon number ← 1 byte
set display text line 1 ← 14 bytes
set display text line 2 ← 14 bytes
set display text line 3 ← 14 bytes
set display text line 4 ← 14 bytes
KNX Events / event name / edit
action KNX - trivum
on bit/byte, 2 bytes or string from KNX β†’
run one of the Generic Server Actions,
e.g. activate a source, change volume etc.
For the full list of possible actions see this article.
β†’
KNX Actuators / object name / edit (by double click)
action KNX - trivum
binary switches
send switch on/off ← 1 bit
dimmers
set on/off ← 1 bit
read status 1 bit β†’
set brightness ← 1 byte
read brightness 1 byte β†’
shutters
send short action ← 1 bit
send long action ← 1 bit
send position ← 1 byte
read position 1 byte β†’
set angle ← 1 byte
read angle 1 byte β†’

Server with Software V7 (X3 or C4)

Addons / KNX / ...
action KNX - trivum
businterface
scene save/restore 1 byte β†’
lights
set on/off ← 1 bit
set brightness ← 1 byte
dimm ← 4 bits
read status 1 bit β†’
read brightness 1 byte β†’
climate
read setpoint temperature 1 byte β†’
read current temperature 1 byte β†’
temp. controller on/off ← 1 bit
set controller action ← 1 byte
activate comfort mode ← 1 bit
activate night mode ← 1 bit
activate standby mode ← 1 bit
shutters
send long action ← 1 bit
send short action ← 1 bit
activate preset ← 1 bit
read position 1 byte β†’
read angle 1 byte β†’
displays
set display page ← 1 byte
set display icon number ← 1 byte
set display text line 1 ← 14 bytes
set display text line 2 ← 14 bytes
set display text line 3 ← 14 bytes
set display text line 4 ← 14 bytes
sensors
run action on bit value
e.g. activate source, use device, change volume.
possible actions are different to those in V8.
1 bit β†’
audio
status and volume
set zone on/off 1 bit β†’
send on/off status ← 1 bit
set zone mute 1 bit β†’
send mute status ← 1 bit
change zone volume 4 bit β†’
set zone volume 1 byte β†’
send current volume ← 1 byte
source control
skip to next/previous source 1bit β†’
send ">" command to source 1 bit β†’
send "<" command to source 1 bit β†’
send ">>" command to source 1 bit β†’
send "<<" command to source 1 bit β†’
special controls
include/exclude in scene 1 bit β†’
run any command 2 bytes β†’

trivum TouchPad

Possible KNX objects that can be defined via the web configuration interface of a TouchPad. These are completely independent from any server side KNX configuration.

action KNX - trivum
binary switch
set on/off ← 1 bit
read status 1 bit β†’
dimmer
set on/off ← 1 bit
read status 1 bit β†’
set brightness ← 1 byte
read brightness 1 byte β†’
RGB dimmer
set on/off ← 1 bit
read status 1 bit β†’
set brightness ← 1 byte
read brightness 1 byte β†’
set red, green, blue ← 1 byte each
read red, green, blue 1 byte each β†’
shutters
send short action ← 1 bit
send long action ← 1 bit
send position ← 1 byte
read position 1 byte β†’
set angle ← 1 byte
read angle 1 byte β†’
climate
read room temperature 2 bytes β†’
activate comfort mode ← 1 bit
activate night mode ← 1 bit
activate antifrost mode ← 1 bit
set heating/cooling mode ← 1 bit
read heating/cooling mode 1 bit β†’
set comfort/standby/... ← 1 byte
read operation mode 1 byte β†’
set comfort temperature ← 2 bytes
read comfort temperature 2 bytes β†’
set setpoint temperature ← 2 bytes
read setpoint temperature 2 bytes β†’

KNX Objects and Apps

Objects

Switch actuator

Dimmer actuator

RGB actuator

Shutter/blind actuator

The small WebVisualization of a Shutter/blind actuator object, in this example named as "Rolladen" (ger.: Shutter)
The large WebVisualization of a Shutter/blind actuator object

The Shutter/blind actuator object allows to configure the following group addresses:

GA action
GA for short action (to change angle)
GA for long action (to move shutter up/down)
GA to write position
GA to read position
GA to set angle
GA to read angle

Possible Actions

Configure "GA for long action"'

Button KNX-Action Comments
Position
Knx objects buttons down.png
TouchPad sends "1" to "GA for long action". The shutter should then start to move down and continue to move down until bottom is reached. A move down can be interrupted by pressing Up, or by pressing an Angle Arrow as below.
Position
Knx objects buttons up.png
TouchPad sends "0" to "GA for long action". The shutter should then start to move up and continue to move up until top is reached. A move up can be interrupted by pressing Down, or by pressing an Angle Arrow as below.

Configure "GA to set angle"
The angle arrows appear.

Button KNX-Action Comments
Angle
Knx objects buttons down.png
TouchPad sends "1" to "GA for short action". Shutter blades should change their angle for one step and then stop.
Angle
Knx objects buttons up.png
TouchPad sends "0" to "GA for short action". Shutter blades should change their angle for one step and then stop.

Configure "GA to write/read position"

Button KNX-Action Comments
Preset
Knx objects buttons preset.png
(long pressed)
Position is read from "GA to read position" and stored in the TouchPad on that button.
Preset
Knx objects buttons preset.png
(short pressed)
Position is sent to "GA to write position".

Climate actuator

Fancoil actuator

Scene

Apps

Analog clock

Audio visu

Stopwatch

Weather forecast

Webcam

How to configure a webcam for trivum TouchPad

Preconditions

  • Make sure you have TouchPad SW Version 1.69 or higher (To check which version you have, press the trivum icon in the upper right corner to open the System Menu and then press Info. Check the entry SW Version.)
    If your SW Version is lower than 1.69, update your TouchPad SW (see this article)
  • Use only Webcams that deliver Motion JPEG streams, i.e. a sequence of plain JPEG images.
    Do NOT use webcams that require any kind of browser plugin (Quicktime or Flash) as the trivum TouchPad does not support such kind of video streams.

Configure the webcam

  • to use JPEG or MotionJPEG (but NOT MPEG-4 etc.)
  • to use a low resolution of 320x240, with 10 fps (these settings might be hidden under "Advanced settings")
    You may try higher resolutions and frame rates later, but they may cause bad performance or an empty picture.

Configure the TouchPad
On the TouchPad...

  1. Press the trivum icon (upper right corner) to open the System Menu.
  2. Press Info.
  3. In the left table Informations you can check the IP address.
  4. Open a web browser and enter the IP address.
    β†’ There Multiroom Setup Tool of the TouchPad opens.
    http://192.168.1.200/
  5. Click KNX Objects β†’ Add object β†’ new App... β†’ Add webcam
    (some SW versions may require Google Chrome browser here)
  6. Click the input field Webcam examples and select Example 1
    β†’ An URL appears.
    - without leading http://
    - it must be the URL of a real .jpg or .mjpeg object, not an .html page
    - default port is 80
  7. Find out the web address (URL) of your camera image or image stream
    1. Open the camera web page of your camera where an image is shown
    2. Right-Click on that image, select Copy Image Location
  8. Paste the copied address into the Webcam address-field
    • Remove the leading "http://" if it wasn't done automatically
    • if the URL contains a port number, e. g. :8080 then remove it from the URL and type it into the port field

β†’ The new image should appear instantly in the webcam on the TouchPad.

How to configure up/down/left/right with a webcam

In the Multiroom Setup Tool of your TouchPad...

  1. Click KNX Objects.
  2. Click the webcam object and select Edit the object properties.
  3. In the row Webcam command address, enter the base URL on which your webcam receives commands
    192.168.1.229/com/ptz.cgi?move=
    Example: webcam URL for commands
    β†’ Once done, new fields appear like:
    • command UP
    • command DOWN
    • command LEFT
    • command RIGHT
  4. Fill these in as well depending on the commands your camera supports
    command UP: up

β†’ For example, pressing up should then send a command 192.168.1.229/com/ptz.cgi?move=up to the camera.

Tested Webcams
Webcam Notice
Axis 205 The Axis 205 supports up to 20 clients in parallel. If it is important for you to view the same webcams on multiple touchpads in parallel, make sure to use a webcam that supports multiple streams. For example, the Axis m7001 does NOT support multiple streams.
Edimax 7010pt The Edimax may also support multiple client streams, but this was not tested so far. Please check the product specification at the vendor's website.
Troubleshootings

[151.1] No webcam image appears on TouchPad

[151.2] An webcam image appears and freezes for several seconds on TouchPad

Page navigation

KNX Events

Switching off multiple KNX and AudioActuators

For example, by a single KNX message you want to

  • switch off light
  • drive down the shutter
  • switch off audio

This cannot be done directly by the KNX TouchPad and/or AudioActuator.

Instead:

  1. program your KNX devices (by ETS) to listen on multiple group addresses, one of them being an "all off" address that is listened to by many knx devices
  2. at the trivum actuator, create a knx event that also listens on this address, just to switch off audio.

Creating and deleting of zone groups

Since V8.61 zone groups can be defined which can be activated or deactivated instantly by a KNX event.

  1. Open the Multiroom Setup Tool.
  2. Click Zonegroups β†’ Add zone group
  3. Create groups and define which zone members they contain.
  4. Enter KNX addresses to "start" this group (to "start" means to join the member zones into a group).
  5. Enter KNX addresses to "stop" this group (to "stop" means all member zones become independent, isolated zones again).

Selecting Local Sources in Zone sources or by KNX

Example:

An Output Connect or Poweramp Connect card exists in Zone "MyRoom". This means a Local Source is also available within Zone "MyRoom". If you want to activate this source through a KNX event, then enter a Group Address (GA) like 3/3/1 under

  • System V7: Addons β†’ KNX β†’ Audio β†’ Zone MyRoom: Listen Sourcechange
  • System V8: Zones β†’ MyRoom β†’ KNX: GA to send: ">"

This means if a 1-bit event 3/3/1 is received, it will toggle between the Zone sources.

Now you have to configure these sources.

  • System V7: Zones β†’ MyRoom β†’ Zonesource# ...
  • System V8: Zones β†’ MyRoom β†’ Sources ...

In System V7 it is not possible to select Local Source here at all, and in System 8, it is possible but still inflexible, as you cannot change the displayed name and icon of that source as it will appear on a touchpad or other display. Therefore use a virtual device that selects the source, like this:

  • System V7: Addons β†’ Devices β†’ New: Basic/IR β†’ Every function
  • System V8: Devices β†’ Add Device β†’ Basic/IR β†’ Every function

Then change device name "Every function", e.g. to "Local Input".

  1. Enter the device definition.
  2. Edit AudioOut Connection, and select Local input of current zone.
  3. Then go back to the Zone Source definitions as discussed above.
  4. Now you can select a Zone source: Device use β†’ Local Input.
  5. And then, a KNX event 3/3/1 should activate that source.

Changing between multiple sources by one KNX button

Precondition: A zone source (Tuner, Streaming etc.) must be defined. To do this,

  1. Open the Multiroom Setup Tool.
  2. Click Zones.
  3. Click Edit-icon left to the zone and select Sources.

Here you can define up to 8 sources, or simply actions, like activating Tuner, Streaming etc.


Configuring a command to skip between the sources

  1. Open the Multiroom Setup Tool.
  2. Click Zones.
  3. Click Edit-icon left to the zone and select KNX Settings.
  4. In the section Start music in the current zones, define a command for GA skip to next/previous source.

For example, if you configure "1 2 3" here and then send a 1-bit message "1" to KNX group address 1/2/3 then the zone will switch from Zonesource #1 to #2 etc.

This scheme can be used for many things, like sources, FM radio stations, TuneIn web radio stations, toggling between Playlists and more.

Scenes

Example

A trivum AudioActuator should be controlled by KNX scenes. By selecting two different scenes through GA 1/5/99 the first zone should either be off, or it should play a station of the FM tuner.

1. System / KNX Setup

  • enable Use EibNetIP for EIB access
  • GA scene save/restore: enter
    1 5 99

2. Zones / first zone / KNX settings

  • GA to include/exclude in scene: enter
    1 5 90

3. Scene programming

Szene 1: off state
  • make sure the zone is off
  • tell first zone it is part of a scene:
    send through KNX
    1 Bit, Value 1, to 1/5/90
    β†’ to verify if this KNX command was accepted, look under Developer β†’ Traces β†’ KNX Trace where it should say:
    Zone 'first zone' will handle scene part '1' telegram"
  • store the current (off) state as scene number one:
    calculate the scene index:
    index = scene number - 1
    calculate the command code
    Store = 128 + scene index
    Restore = 0 + scene index
  • send through KNX
    1 Byte, Value 128, to 1/5/99
    β†’ verify if the KNX trace says:
    will save scene 1. scene 1 save included 1 zones.
Scene 2: FM tuner station
  • activate FM tuner in the zone, select station 3.
  • store the current (on) state as scene number two:
    send through KNX:
    1 Byte, Value 129, to 1/5/99
    β†’ verify if the KNX trace says:
    will save scene 2. scene 2 save included 1 zones.

4. Use the scenes

use the "off" scene

  • send through KNX:
    1 Byte, Value 0, to 1/5/99
    β†’ the zone should switch off
    β†’ verify if the KNX trace says:
    will restore scene 1. included 1 zones.

use the FM tuner scene

  • send through KNX:
    1 Byte, Value 1, to 1/5/99
    β†’ the zone should play FM tuner station 3
    β†’ verify if the KNX trace says:
    will restore scene 2. included 2 zones.

Note that it is not required to have "trace bus communication" active to see the KNX trace messages shown above. The important action messages for scene handling are always traced.

Volume Control via KNX

Volume of a zone can be controlled via knx in two ways:

Method 1

Precondition:

  • You have to find out if your KNX sensor sends 4-bit events of the kind "start volume increase, stop volume increase", or if it sends 8-bit absolute values (0-255).
  1. Open the Multiroom Setup Tool
  2. Click Zones.
  3. Click icon left to your zone.
  4. Select KNX Settings.
  5. Click GA to control zone volume-input field (4 Bit or 1 Byte, depending on the condition)
  6. Enter GA.

Method 2

This can be used as an alternative to the Methode 1, for example if your KNX sensor sends only 1-bit messages for "increase volume" or "decrease volume".

  1. Open the Multiroom Setup Tool
  2. Click KNX Events β†’ Add KNX event action
  3. Click Action when content match-input field
  4. Select Control a zone β†’ Volume +
  5. Repeat Step 2 - 4 for Volume -

See also: [xxx] KNX Event mapped to Volume Up or Down does nothing

KNX Network Traffic Analysis Tools

You may check if KNX commands for IP routers are visible in your LAN network by the following tools:

ETS

You need this program already to configure and program a KNX IP router, especially the router filters. So in most cases, you should have an ETS at hand already. Open the Group Address Monitor in ETS and see therein what KNX events come in from the router.

trivum Controller or MusicCenter

  • System 7: Enable Addons β†’ KNX β†’ Bus interface β†’ trace bus communication
Then click print β†’ controller-trace
β†’ shows a mixed trace of system events and KNX events


  • System 8: In the Multiroom Setup Tool, enable System β†’ KNX Setup β†’ Trace bus communication
Then click Developer β†’ KNX/EIB-Trace
β†’ shows only KNX events

In the KNX events, events sent from outside to trivum will appear as "wrte" records (external writes to the KNX bus).

trivum Touchpad

On the TouchPad...

  1. Press the trivum icon (upper right corner) to open the System Menu.
  2. Press Info.
  3. Scroll down the table Informations.
  4. Press Show KNX events.

Trace tool

You can trace the TouchPad outputs:

  1. Download the trivum trace tool (see Trace Tool)
  2. Find out the TouchPad IP address by pressing System Menu β†’ Info
  • On a Windows or Mac PC, run the trace tool like trace.exe touchpadIpAddress.
  • If you see the welcome message "trace attached", press 'k' to toggle KNX trace (this may require a touchpad V 1.69 or higher).

With TouchPad V 1.84 or higher, you will see messages like

KNX: wrte 01/4/121 1bit 000 (0x40,0x00) - SRC:bc.d0 DST:11.14 IPSrc=192.168.0.229
KNX: wrte 01/4/124 byte 000 (0x40,0x00) - SRC:bc.d0 DST:11.14 IPSrc=192.168.0.229
KNX: answ 06/6/006 text Room_3________  - SRC:bc.e0 DST:11.c6 IPSrc=192.168.1.64

where 'byte' may also indicate any multi bit value like 4 bit dimming events.

Wireshark

You can also use the network analysis tool Wireshark.

    ip.dst == 224.0.23.12

SFK (free command line tool)

You can also use the free command line tool SFK. You can download it from ftp://service.trivum.com/Installer/freewaretools/.

sfk knxdump

Example output:

----- #011 from 192.168.1.76 at 02.11.2012 13:24:29 (14 bytes) -----
 KNX: search request
 >06100201 000E0801 E000170C 0E57<
       
----- #012 from 192.168.1.67 at 02.11.2012 13:24:32 (17 bytes) -----
 KNX: route 1/4/121 len=1 00
 KNX: nmc=29 addil=0 ctl1=BC ctl2=E0 src1/2=11C7 dest1/2=0C79
 KNX: dsttype=0 routcnt=0 tcpi=0 ncnt=0 acpitype=0 acpidata=0
 >06100530 00112900 BCE011C7 0C790100 00<

This way you see whenever something is sent, and from whom.

Example with a different multicast address:

sfk knxdump 3671 224.0.23.13

SFK also allows to send simple KNX events for testing like

sfk knxsend "3 4 250 1 0"

which would send a 1-bit value "0" to address 3/4/250.

Troubleshootings

A list of all Troubleshootings concerning KNX you can find here.