Skip to main content
Demo phasevenfree is still being built.
venfree/Wiki/KNX Telegram

KNX Telegram

A KNX telegram is the smallest unit of communication on the bus. It contains sender (physical address), destination address (group address), data value and priority, and is received simultaneously by all devices on the line.

Telegram Structure

A standard telegram consists of: control byte (priority, repeat flag), source address (physical address of sender, 2 bytes), destination address (group address or physical address, 2 bytes), NPCI (network protocol control with hop counter, 1 byte), APDU (payload including APCI code, 1–15 bytes), and FCS (checksum, 1 byte).

The APCI code in the APDU field defines the telegram type: GroupValueWrite (write), GroupValueRead (read request) or GroupValueResponse (response to read request). For normal control, GroupValueWrite is the most common type.

Bus Access and Priorities

KNX TP uses CSMA/CA (Carrier Sense Multiple Access / Collision Avoidance). Each device wishing to send waits until the bus is free, then begins transmitting. In the event of simultaneous transmission, the device with higher priority wins, the other detects the collision and waits.

There are four priority levels: System (highest, for group address programming), Alarm, High and Normal. During normal operation, almost all devices send at Normal priority. Safety and alarm telegrams are sent at Alarm priority.

Key Facts

  • Payload (APDU): max. 14 bytes for standard frames
  • APCI types: Write, Read, Response
  • CSMA/CA: collisions resolved via priority arbitration
  • 4 priorities: System, Alarm, High, Normal
  • No ACK → sender retries up to 3 times
  • All devices on the line receive every telegram

Plan your project with venfree

From room functions to device list and bill of materials, automatically, free, no account required.

Plan now