Projekt settings - Telegramm Monitor

Telegrams can be recorded in the background with the telegram monitor. The telegrams are not stored on the SD card but in the RAM, therefore this recording does not limit the life of the SD card.

Aufruf menu project settings - Telegrammonitor

Activate monitor	Activates the telegram monitor
Ring buffer	Number of telegrams the controller keeps in its main memory. Recording continues indefinitely: once the set number is reached, the oldest telegrams are overwritten by the newest ones. The value therefore defines how far the "Current buffer" view reaches back, not when recording stops. One telegram takes about 300 bytes. The brackets behind the caption therefore continuously show how much main memory the ring buffer occupies when full at the current setting: 100000 telegrams are about 29 MB, the maximum of 262144 telegrams 77 MB. The value should only be as large as the diagnosis requires - otherwise the main memory is missing for the program. The ring buffer resides in main memory only. Its content is lost when the controller restarts or on a power failure. If "Save permanently" is not used, telegrams that have dropped out of the ring buffer are gone for good.
Filter	All: All telegrams are recorded. KNX only: Only KNX telegrams are recorded (all addresses less than or equal to 31/7/255). Internal only: Only internal telegrams are recorded (all address greater than 31/7/255) Filter: Only the addresses entered in the filter table are recorded. The filter table is shown with this selection only.
Filter table	Here addresses can be added as filters. Drag addresses from the variable window into this table to add addresses. All addresses of the table are always recorded, across all tabs. The check mark in front of the address only controls whether the telegrams of this address are shown in the table. This way the display can be changed at any time without losing recorded telegrams. Several filter lists can be created as freely named tabs; the table shows the telegrams of the currently selected tab.
Filter table view	The input field below the table limits the display, recording is not affected. Several search terms can be entered separated by spaces or semicolons. Without a wildcard the entry has to match exactly. The asterisk stands for any characters, for example 10/10/* shows all addresses of the middle group 10/10 and 10* all addresses of the main group 10. The destination address, the source address, the command, the value and the data in hex are compared, so the telegrams of a single device (for example 1.1.*) or all write telegrams (Write) can be shown as well.
Status line	Below the table the number of recorded telegrams and - as soon as a filter is active - the number of displayed telegrams is shown. If the filter type "Filter" is selected and the filter table is empty, the status line points out that the controller does not record anything at all in this case.
Export	The displayed telegrams are saved as a CSV file with a semicolon as separator. The first column contains the complete time stamp in the format year-month-day hour:minute:second.millisecond, which can be sorted and processed directly in a spreadsheet.
Save permanently	With this option, telegrams are additionally stored permanently, one file per day. Please note: Frequent saving can reduce the lifetime of the internal flash memory. An optional industrial memory card should be used. Interaction with the ring buffer: Every recorded telegram is written to the ring buffer and to the daily file. The size of the ring buffer therefore does not limit the files - the files contain everything the filter let through, without gaps, even if it has long been overwritten in the ring buffer. The ring buffer only determines how far the "Current buffer" view reaches back. How far the files reach back is set by "Save permanently days". "Load data" selects what is displayed: either "Current buffer" (main memory) or one of the daily files. The controller collects new telegrams in main memory for a short time and writes them to the file once per minute; when a file is requested it is saved beforehand, so the loaded file is always up to date. One file with the extension .mon2 is created per day. Recordings from versions before 2.3136 have the extension .mon, do not contain milliseconds and can still be opened unchanged.
Save permanently days	Number of days that are kept. If more days are present, the controller deletes the files of the oldest days. This value limits the files only, not the ring buffer.

Columns of the telegram table

Date	Day of the recording.
Time	Time of the recording including milliseconds. Recordings made by an older controller do not carry milliseconds and are shown with .000.
Interval (ms)	Time between this telegram and the previous displayed one in milliseconds. This makes telegrams in quick succession and telegram loops immediately visible. If a filter is active, the interval refers to the displayed telegrams, not to all recorded ones.
Source	Physical address of the sender. Telegrams of the controller itself have a blue background.
Destination	Group address of the telegram.
Value	Value of the telegram, converted with the data type of the address in the project.
Service ID	Service of the controller the telegram originates from.
Command	Read, Write or Response.
Data type	Data type of the telegram.
Length	Number of data bytes.
Data hex	Raw data of the telegram in hexadecimal notation.