Skip to content
Website
🧱 CFC 238KNX home automation: topology, addressing and parameter settingChapter 1 of 10 in the section

Designing the bus: lines, areas, couplers and participant limits

This chapter details the design rules for a robust KNX topology for telecommunications and building automation installations. You will learn how to segment a network according to constraints of distance, electrical consumption and data traffic. You will know how to size lines, position each coupler judiciously and incorporate the margins essential for future building extensions.

Key takeaways

  • A KNX line is sized according to the electrical load and foreseeable traffic volume.
  • The limit of sixty-four participants per segment maintains bus voltage and stability.
  • The line coupler electrically isolates segments and filters telegrams between lines.
  • Allowing a twenty per cent reserve for addressing and current prevents heavy rework.

Bus hierarchy and physical constraints of a KNX line segment

Laying green cable without a prior addressing plan invariably leads to intermittent faults as soon as the first additional modules are introduced. A KNX network cannot be improvised during cable pulling. Differential baseband transmission over TP1 twisted pair adheres to strict limits of line resistance and distributed capacitance. Exceeding these thresholds causes distortion of the telegram wave fronts, undetectable during simple multimeter tests, but a source of repeated collisions in real operation as soon as several push buttons or detectors transmit simultaneously.

KNX TP1
Standardised physical communication medium simultaneously transmitting direct-current safety extra-low voltage power and digital data at a rate of 9600 bits per second over a shielded twisted pair.
Physical limit values for a standard KNX line segment
Geometric or electrical parameterAbsolute maximum limitRecommended design target
Total deployed cable length per segment1000 metres700 metres
Maximum distance between power supply and participant350 metres250 metres
Maximum distance between two participants on the segment700 metres500 metres
Tolerated bus voltage drop at the furthest point9 volts (21 V minimum)6 volts (24 V minimum)

Although the modern software stack permits theoretical addressing of two hundred and fifty-six participants per line, the reality on the construction site requires limiting each physical segment to sixty-four devices. This historical limit remains the golden rule to prevent direct-current voltage collapse under cumulative inrush currents. A standard participant draws about 10 milliamperes at 29 to 30 volts, but some touch-screen room controllers or IP gateways consume up to 30 milliamperes. The power budget of the chosen line power supply determines the actual feasibility of the run.

Segmentation using couplers and sizing the extension reserve

Connecting several segments or functional sub-assemblies requires inserting a line coupler. This device ensures complete galvanic isolation between the main line side and the sub-line side. Logically, the coupler analyses every incoming telegram and consults its internal filter table, generated automatically by the ETS software during programming. Only telegrams whose group addresses concern participants located on the other line are allowed to cross the component.

  • Containment of local traffic to prevent congesting the backbone network with lighting or blind control frames.
  • Electrical isolation protecting the entire installation against a dead short circuit occurring on an isolated segment.
  • Ability to address up to fifteen sub-lines on a single main line via their respective couplers.
  • Methodical structuring facilitating diagnostics of open circuits or insulation faults during maintenance operations.

Physical addressing strictly mirrors this hardware topology using the Area.Line.Participant format. For example, the physical address 1.2.0 specifically designates the coupler connecting line 2 to the main line of area 1, whereas the modules connected downstream will bear identifiers from 1.2.1 to 1.2.255. When the building comprises several areas, the main lines of each area are in turn connected to a general backbone line via area couplers configured with the address Area.0.0.

  1. Inventory of initial loadsCalculate the sum of the nominal currents of all modules planned on the segment using a default value of 10 mA for passive sensors and the manufacturer value for screens.
  2. Application of the diversity factor and reserveIncrease the line power supply capacity by at least 30%. For an initial consumption of 400 mA, directly select a 640 mA or 1280 mA power supply unit to absorb extensions.
  3. Reservation of physical address rangesBlock out at least 20 consecutive free addresses per line in ETS, and reserve the necessary physical space for three additional DIN-rail modules per distribution board.

Physical addressing and traffic filtering by the line coupler

A KNX home and building electronic systems installation that operates seamlessly on handover day but rejects any new sensor or actuator six months later reveals an initial design flaw. Connecting devices haphazardly along a twisted pair without structuring the addressing amounts to mere cable pulling, not network engineering. As soon as the building exceeds twenty or so devices distributed across several distribution boards or levels, topological segmentation becomes the absolute condition for long-term viability.

KNX line coupler
Modular DIN-rail-mounted device providing galvanic and logical coupling between a sub-line and the main line. It analyses incoming telegrams and applies a filter table to only forward shared information to other lines, blocking purely local traffic.

The role of the line coupler is not limited to joining two runs of green cable. It guarantees a genuine communication boundary. Without a coupler, every lighting command, every cyclic temperature report and every state change of a window contact is broadcast across the entirety of the physical medium. On the scale of a detached house, this overhead often remains invisible. In commercial premises, an administrative building or a multi-family dwelling in Romandy, this practice inevitably leads to repeated frame collisions, perceptible latencies at push buttons and loss of telegrams.

Line coupler behaviour depending on the nature of the transmitted message
Telegram typeAddressing modeProcessing by the couplerImpact on the main bus
Group telegramGroup address present in tableImmediate routing to the upper lineTraffic transmitted only to actual subscribers
Group telegramGroup address absent from tableStrict blocking within the local lineZero residual load on the rest of the network
Individual telegramPhysical address outside the local lineTargeted routing to the destination segmentOne-off forwarding without general broadcast
Diagnostic telegramProgramming mode or bus monitoringSelective pass-through or blocking depending on parameterSecuring commissioning operations

Physical addressing reflects the hardware location of the participant: area.line.participant (for example 1.2.15). The line coupler must obligatorily occupy address zero of the branch it serves (1.2.0). It is this strict hierarchy that allows the engineering software to automatically generate filter tables during application download. Leaving a coupler in transparent mode ('route all') after the testing phase negates its barrier function and exposes the system to instability as soon as an extension injects new messages.

Engineering rules: number of participants and sizing of reserves

From a purely standards-based perspective, the introduction of low-consumption KNX components (TP1-256) technically allows addressing up to 256 participants on a single physical segment without using a repeater, provided that the bus power supply rating supports it. In practice, designing a project by lining up 240 addresses on a single line is professional negligence. This configuration saturates the addressing space, prohibits any subsequent modification without heavy rework of the technical cabinet, and multiplies the risk of general failure in the event of a short circuit on a branch.

Proper sizing dictates allocating one line per distinct functional entity: an office floor, a show flat, technical rooms or communal areas. The number of participants per line at handover should never exceed 40 to 50 devices on a standard line. This rule ensures an immediate extension reserve when a user wishes to add presence detectors, room interfaces or switching modules in suspended ceilings.

  • Addressing reserve: keep at least 15 to 20 contiguous physical addresses free within the line range to simplify identification during extensions.
  • Power reserve: size the bus power supply so that the cumulative consumption of devices at idle and during operation does not exceed 70% of the nominal current (for example 450 mA consumed on a 640 mA unit).
  • Modular space reserve: provide space for at least 4 free modular units on the DIN rail carrying the KNX bus equipment in each sub-distribution board.
  • Continuity and topology: distribute the bus in a star or open-line pattern, strictly avoiding any loop, with each end remaining accessible in a clearly labelled junction box.

Finally, the extension reserve must incorporate the cabling topology within conduits. Since pulling an additional cable through an already saturated KRFw conduit is precluded, anticipation is required as early as the installation of flush-mounted conduits. Clean separation of lines using couplers allows an extension work area to be electrically isolated without interrupting operation of already occupied sections, thereby honouring the service commitments owed to the client.

Saturation diagnostics and remedial action for a faulty bus topology

On a KNX installation handed over without rigorous topological study, erratic behaviour manifests as soon as the first supplementary modules are added. Symptoms on site are typical: slow execution of commands, dropped lighting orders, red flashing diagnostic LEDs on gateways and continuously repeating telegram frames. The network electrician or telematics installer must determine whether the cause of the lockup stems from a direct-current supply voltage collapse or from bandwidth saturation caused by a breakdown in logical segmentation.

  1. TP1 supply voltage checkMeasure direct-current voltage with a multimeter on the red and black terminals of the participant furthest from the board. The value must not fall below 21 V DC under active load. Excessive voltage drop necessitates adding a decentralised power supply or splitting the physical segment.
  2. Load audit using the bus monitorConnect the USB or IP interface to the bus and launch the ETS software bus monitor. Identify the line utilisation rate. Recurring presence of repeated frames indicates a missing acknowledgement (ACK), often caused by packet collisions on an overloaded line.
  3. Coupler filter table checkInterrogate each line coupler. A coupler left in full-forwarding mode passes all telegrams from the main line to sub-lines, choking secondary segments. Reload the exact filter table compiled based on the project's group addresses.
  4. Physical splitting and readdressingIf the number of participants exceeds functional reserves or transmission capacity, split the line into two separate segments connected by a new line coupler, recalculating the individual addressing of each module affected.

art. 364 CO requires the contractor to carry out the work with care and according to the rules of their trade. Handing over a KNX bus bordering on the addressing or electrical consumption limit without an extension reserve constitutes manifest technical negligence. Traceability of the ETS software project, archiving the source file on the construction site and systematically installing supplementary isolating terminals guarantee maintainability in accordance with professional practice.

Frequently asked questions

How should one respond if bus voltage drops below 21 V DC at a remote participant?

A voltage drop below 21 V DC causes spurious reboots of KNX participants. One should first check for loose connections on the micro branch terminals. If the drop is due to cable length or the number of devices, a second certified KNX power supply must be installed on the line, strictly observing a minimum cable spacing of two hundred metres from the first source.

Can a faulty line coupler be replaced with a repeater without modifying the ETS project?

No. The line coupler logically isolates two distinct lines using specific physical addresses (such as 1.1.0) and applies a precise filter table. The repeater, meanwhile, electrically extends a segment on the same line without filtering traffic. Replacing a coupler with a repeater destroys the hierarchical structure, scrambles physical addresses and immediately saturates the overall bus bandwidth.

Why does the ETS bus monitor display a continuous stream of repeated telegrams?

When a participant sends a telegram, it expects an acknowledgement of receipt from at least one configured receiver. If no participant acknowledges receipt of the message, the sender automatically retries up to three times. This phenomenon occurs when a group address contains no listening receiver, or when a line coupler blocks the telegram due to an obsolete, uncompiled filter table.

What is the procedure for inserting a new KNX line into an already full installation?

When the area main line or sub-line segments have reached their quota or capacity, a new line must be created in the area via a dedicated line coupler, provided that a free sub-line address between 1 and 15 remains. If the area main line is itself saturated, it becomes essential to create a new area connected via an area coupler.

Texts and standards cited

  • CO art. 364contractor obligations: liability subject to the same rules as that of an employee; performs the work in person or under personal direction; unless custom or agreement provides otherwise, provides at own expense the necessary means, plant and tools.

In the same section