Bus events
This dialog literately traces what happens with a telegram over the entire KNX Virtual installation once sent by a device.
ID
By means of the (additional) 'ID' column it is possible to:
- Filter out telegram events from devices
- Disconnect devices from the bus
Filter
- Clicking the respective device cell once sets its color to orange and means that all related telegram events of the device will not appear anymore, the device is however still active
- Filtering is possible for all devices
- The filtering is only applied within this dialog
Disconnect
- Clicking the respective device cell a second time sets its color to red and disconnects the device from the bus, which automatically means that no longer telegram events will appear for this device (because it is no longer active)
- This typically is applied for devices sending telegrams cyclically, like D12 (Weather Module)
- Disconnecting is however not possible for couplers
- Only during the life-time of this dialog devices can be disconnected, i.e. disconnected devices will be automatically connected again after closing this dialog
Coloring
In which segment a specific telegram event occurs can be recognized by means of the coloring, the colors are set according to the segment coloring.
HC
This column indicates the hop count of the telegram (at that moment). The hop count is also known as 'routing counter'.
AES
This column indicates the encryption status of the telegram (at that moment) :
- '-' : the telegram is plain (no encryption)
- 'a' : encryption type authentication is applied
- 'a + c' : encryption type authentication + confidentiality is applied
Event types
The following events can be distinguished:
- AL: GroupWrite
- AL: GroupRead
- AL: GroupResponse
- AL
- TL
- NL: forward
- NL: decrypt + forward
- NL: encrypt + forward
AL
- Application Layer : the group address is linked to at least one object of the device and is hence applicable by the application
- 'GroupWrite' : telegram sent because of e.g. an object representing a push button rocker after being manipulated
- 'GroupRead' : telegram type sent after device reset in case the I-flag is set for the respective object
- 'GroupResponse' : telegram sent after receiving a GroupRead telegram in case the R-flag is set for the respective object
- in case of no specific indication (just 'AL') : e.g. an object representing a relay after receiving a GroupWrite telegram
TL
- Transport Layer : the group address is linked to at least one object of the device, but is not applicable by the application
- typical case: an object representing a push button rocker after receiving a GroupWrite telegram
NL
- Network Layer : the telegram being processed by a coupler
- 'forward' : forward the telegram as is (at that moment)
- 'decrypt + forward' : decrypt the telegram before forwarding it
- 'encrypt + forward' : encrypt the telegram before forwarding it