SharKNX can save the telegrams in the monitor to a file - as an ETS-compatible XML communication log, or as a CSV table with every detail SharKNX recorded. You can save the file on your device or share it straight from the app, and load it back into the monitor later.
Which format should I use?
| Format | Best for |
|---|---|
| XML (default) | Handing a recording to ETS or anyone who works with ETS. It uses the ETS communication log format, so the file opens directly in the ETS bus and group monitor. |
| CSV | Analysis in Excel or other tools, and a complete archive of the session. It keeps everything SharKNX observed - names, decoded values, datapoint types, Data Secure status, and bus events - so importing it back loses nothing. |
Both formats are described column by column in Export Formats.
From the Monitor page
Run a monitor session until you have the traffic you need. You can export while the monitor is running or after stopping it.
Tap the export button in the filter bar, or choose ⋯ Actions → Export Telegrams.
In the export sheet, set:
Option Description Export Format XML or CSV. Switching the format also switches the file extension. File Name Pre-filled with the telegram count, date, and time, e.g. SharKNX_1840t_2026-09-29_143022.xml. Edit it to something meaningful - your name is kept when you switch format.Export Limit All, or only the most recent 100, 500, or 1000 telegrams. Tap Save to choose where to store the file, or Share to send it to email, a messaging app, a cloud drive, or another app.
However many telegrams you export, the file lists them in chronological order, oldest first.
What gets exported: everything currently in the monitor buffer - not only what the current filter shows. The buffer holds up to your Telegram buffer size setting (default 2000, see Monitor Settings); older telegrams have already been dropped, so export before a long session overflows it. On the free plan, the buffer - and so the export - is limited to the last 20 telegrams.
XML and bus events: some things SharKNX records have no equivalent in the ETS format - for example gaps where telegrams were missed. They are left out of XML exports, and SharKNX tells you how many were omitted. Use CSV if you need them.
From a Shark Hunt monitor
The same export sheet is available while a Shark Hunt monitor action is open - tap the export button in its top bar. It exports the telegrams that match the hunt's filter, and the file name includes the hunt and action name.
Loading an export back into SharKNX
Open the ⋯ Actions menu:
- Import SharKNX CSV - loads a CSV exported by SharKNX (the current v3 format; files from much older app versions are not accepted).
- Import from ETS XML - loads an XML communication log, whether it was exported by SharKNX or recorded in ETS. Files with more than 5000 telegrams are rejected.
Importing replaces the telegrams currently in the monitor, and names and values are shown using your loaded ETS project. If you load a project after importing, stop the monitor and use ⋯ Actions → Apply Project Data to name and decode the imported telegrams.
Tips
- Load the ETS project before you record. Names, datapoint types, and decoded values in the CSV come from the project; without one, those columns stay empty. XML stores the raw frames, so names can be added later by whoever opens it.
- Record from the start of a test. Clear the monitor before you begin so the export contains only the traffic you care about.
- Sharing with a colleague on ETS? Use XML - they can open it straight in the ETS monitor. Keeping your own records? Use CSV.
Related
- Export Formats - the XML and CSV file structures
- Monitor Page - filters, views, and badges
