KNX is a popular building automation protocol and is used to interconnect sensors, actuators and other components of a smart building together. Our KNX Bus Dump tool uses the Calimero java library, which we contributed to for the sake of this tool, to record the telegrams sent over a KNX bus. Particularly, our tool accesses the KNX bus through a TPUART connection but can be changed to use different connection mediums. The telegrams are dumped into a Wireshark-compatible hex dump file. Timestamps are provided and normalized to UTC time with nanosecond precision to perform data analysis and provide a timeline of the telegrams. The hex dump file can be imported into Wireshark, which can be configured to dissect the KNX telegrams with Wireshark’s cEMI dissector.

Our tool can be used for protocol analysis of KNX sensors, actuators and other KNX devices. For example, we used the tool to understand our KNX devices and found irregular KNX telegrams. The tool is also ideal for security analysis of KNX devices given that it exposes all details of the involved protocol and data sent over the KNX bus.

Tcpdump and Wireshark cannot be used to dump telegrams sent over a KNX bus since we are dealing with native KNX telegrams, not TCP/IP packets. Wireshark and tcpdump can dump KNXnet/IP packets, which are TCP/IP packets. KNXnet/IP is a protocol for sending commands and data to a KNX bus over a TCP/IP network.

This tool is designed to work with the Calimero Java library and is compatible with a Raspberry Pi 3 or 4 and a Raspberry Pi HAT for the TPUART connection.

Here are some guides to getting the environment setup:

1. KNX Raspberry PiHAT Usage Walkthrough
2. Raspberry Pi and Calimero Suite Setup

Note: The next steps will assume that you setup your environment according to these guides.

Creating the Hex Dump

1. Place the KNXBusDump.java file into the introduction/src/main/java/ folder of the Calimero Project suite.

2. Change into the introduction folder.

3. To run the program, you can simply run:

   ./gradlew run -Pcalimero.serial.tpuart.maxInterByteDelay=60000 -DmainClass=KNXBusDump
   

   Refer to the troubleshooting guide below for some common error solutions.

4. Now, you wait for some messages to be transmitted on the bus and the dumped telegrams will be in the KNXBusDump-Telegrams.txt file.

5. Cancel the tool using Ctrl-C and the file is now ready to be imported into Wireshark to be analyzed.

Analyzing the Hex Dump

In Wireshark, you have the ability to import packets from a hex dump and specify a dissector to analyze the packet.

1. Upon starting Wireshark, wait for the initial loading to finish. Then click File -> Import From Hex Dump...

   

   
   

2. In order to properly parse this out, we need to give it a regular expression (regex) with some tags.

   ^\s*(?<time>\d{4}-\d\d\-\d\dT(\d\d\:){2}\d\d.(\d){6}[Z])\s(?<seqno>\d{6})\s+(?<data>[0-9a-fA-F]*)$
   

3. Choose the hex dump file as the source.

4. Under the new dialog, change to the Regular Expression tab and paste the regex into the box.

5. Ensure that the data encoding is Plain hex 200*16

6. In the Timestamp format textbox, we need to specify the pattern that is generated by the tool.

   NOTE: The timestamp format MUST be the EXACT SAME as this. Otherwise, there will not be a timestamp parsed out.

7. Under the Encapsulation section, change Encapsulation Type to Wireshark Upper PDU Export.

8. Check ExportPDU to specify the cemi dissector.

9. Now you're able to import the file and analyze the telegram.

   

Wireshark Timestamp:

Corresponding Hex Dump File

Note: The time that is highlighted is the NORMALIZED UTC TIME. No matter what the timezone next to the time says, it will ALWAYS be the right time in UTC.

Considerations:

1. The cemi dissector starts at the message code (MC) portion of the telegram. It does not take into consideration the medium type.
2. The reason why the TPCI is highlighted in red is because of a design choice. The dissector will see that the packet is an Unnumbered Data Packet (UDP) which means that the sequence number, according to the KNX standard, is usually set to 0. However, sometimes some devices will set this to a non-zero value. In this case, it was set to 1. The dissector will then check if the sequence number is zero. In this case it is not, thus the error message for the sequence number expecting to be 0.

These are some common errors that can occur when running this program with this setup guide. I have provided solutions in hopes that it fixes the error.

Running Discover KNX Servers program instead of the Bus Dump

Make sure that you type in all the commands exactly. Running the command with "Dmainclass" will cause the program to default to the Discover KNX Servers program. Make sure it's "DmainClass"

Cannot get the initial state of the TPUART port

Make sure that KNXD (if you have it installed per these guides) is not running. If following this guide, then KNXD will be using that same port and only one process can use the serial port at a time.

Wireshark: "Can't initialize scanner: Unknown error"

If you copy and pasted the contents of the hex dump files from above, you could be missing an extra new line character. For example, in "SampleData1.txt", the github representation shows 4 lines of data when in reality it is 4 lines of data plus a newline character. So one possible option is to simply press "Enter" after the last byte of data in the file you're importing.

In this repository, I have provided the sample file data in Sample-KNXBusDump-Telegrams.txt that was used to create the screenshots. Feel free to import this into Wireshark to test it yourself.

The tool was tested on this local KNX Testbed.