KNX (standard)
KNX is a standardized (EN 50090, ISO/IEC 14543), OSI-based network communications protocol for intelligent buildings. KNX is the successor to, and convergence of, three previous standards: the European Home Systems Protocol (EHS), BatiBUS, and the European Installation Bus (EIB or Instabus). The KNX standard is administered by the KNX Association.
KNX protocol
The standard is based on the communication stack of EIB but enlarged with the physical layers, configuration modes and application experience of BatiBUS and EHS.
KNX defines several physical communication media:
- Twisted pair wiring (inherited from the BatiBUS and EIB Instabus standards)
- Powerline networking (inherited from EIB and EHS - similar to that used by X10)
- Radio (KNX-RF)
- Infrared
- Ethernet (also known as EIBnet/IP or KNXnet/IP)
KNX is designed to be independent of any particular hardware platform. A KNX Device Network can be controlled by anything from an 8-bit microcontroller to a PC, according to the needs of a particular implementation. The most common form of installation is over twisted pair medium.
KNX is approved as an open standard to:
- International standard (ISO/IEC 14543-3)
- Canadian standard (CSA-ISO/IEC 14543-3)
- European Standard (CENELEC EN 50090 and CEN EN 13321-1)
- China Guo Biao (GB/T 20965)[1]
KNX Association, as of 1 March 2014, had 339 members/manufacturers from 37 countries.[2] Japan's Fujitsu General was enlisted as member number 300.[3] The complete list can be found here at knx.org
The KNX Association has partnership agreements with more than 30,000 installer companies in 100 countries and more than 60 technical universities as well as over 150 training centres.
KNX system components
All the devices for a KNX installation are connected together by a two wire bus (the most common form of installation), thus allowing them to exchange data. The function of the individual bus devices is determined by their project planning, which can be changed and adapted at any time.
- Sensors (e.g. push buttons, wind-, temperature-, movement-sensors)
- Actuators (dimming units, electrical heating valves, displays)
- System devices and components (e.g. Line-Couplers, Backbone-Couplers)
Sensors are the starting point for every action, because they gather information and send it on the bus as a data telegram. This can be information about room temperatures, movements, wind measurements or manually input instructions (Push buttons). Sensors are selected depending on the required application.
Actuators receive data telegrams which are then converted into actions. This can include controlling blinds, dimming lights or controlling heating and air conditioning systems. Actuators are also selected depending on the required application and consist of a bus coupler and an application module with the corresponding application program.
The application program is loaded into the devices together with the project design and commissioning software via a system component called interface (either serial or USB interface) connected to the PC and the bus. The two-wire installation bus is routed in parallel to the 230 V electrical power supply connects all devices and systems of the household technology together, and transmits all the control signals. It looks the same as the DALI protocol bus.
Logical Topology and Individual Address Space
KNX allows different bus topologies: Tree, line and star topologies. These topologies can be mixed as needed. However, ring topologies are not allowed. The tree topology has advantages over other topologies in cases where a large network has to be created.
KNX is a fully distributed network, which accommodates up to 65’536 devices in a 16 bit Individual address space. The logical topology or sub network structure allows 256 devices on one line. As shown below, lines may be grouped together with a main line into an area. Up to 15 Lines can be connected to a main line via a line coupler (LC) for a total of 16 lines. The line couplers used to establish the lines from main line 1 have physical addresses from 1.1.0 to 1.15.0. 15 lines form an area. An entire domain is formed by 15 areas together with a backbone line using backbone/area couplers.
One line consists of a maximum of 4 line segments, each with a maximum of 64 bus devices. Each segment requires an appropriate power supply. Maximum segment length is 1000 m. 4 segments may be connected with line repeaters to establish a network length of 4000 m and 256 devices. The actual number of devices is dependent on the power supply selected and the power input of the individual devices. Note: Line repeaters may not be used on backbone or main lines. Note that KNX KNXnet/IP optionally allows the integration of KNX sub networks via IP. As shown above, this topology is reflected in the numerical structure of the individual addresses, which (with few exceptions) uniquely identify each node on the network. Note: Each line, including the main line, must have its own power supply unit. Installation restrictions may depend on implementation (medium, transceiver types, power supply capacity) and environmental (electromagnetic noise …) factors. Installation and product guidelines shall be taken into account.
Wire transmission
Twisted pair using differential signaling with a signaling speed of 9600 bit/s. Ideal wave resistance at 100 kHz is 120 Ω. Line resistance at 20 Ω/km, max 75 Ω/km. Maximum capacitance bus-to-bus line max 800 pF/m at 800 Hz. Higher capacitance requires proportionally shorter cable length. Bus power with 30 V DC and 25 mA[4] Polarization critical.[5] Devices within same physical segment are addressed with 8-bits[6] Maximum 57600 network nodes.[5] Media access control is controlled with the CSMA/CA method[7] Maximum segment length is 1000 m.[7] 4 segments may be connected with line repeaters to establish a network length of 4000 m.[7] Loops are not allowed.[7]
# | Field | D7 | D6 | D5 | D4 | D3 | D2 | D1 | D0 |
---|---|---|---|---|---|---|---|---|---|
0 | Control[5] R-repeated packet Px-priority | 1 | 0 | R | 1 | P1 | P0 | 0 | 0 |
1 | Source address #0[5] | ||||||||
2 | Source address #1[5] | ||||||||
3 | Destination address #0[5] | ||||||||
4 | Destination address #1[5] | ||||||||
5 | Destination type[5] Routing info Length | DT | R2 | R1 | R0 | L3 | L2 | L1 | L0 |
6 | User data 1-16 bytes[5] | ||||||||
Checksum (S)[5] |
If the destination type flag (DT) is set the packet will be multicast or broadcast.[7] R2-R0 is decremented for each routing hop, like TTL in IP.[7] L3-L0 correspond to 1-16 user data bytes.[7] Source is always a physical address. Destination may be either a physical or group address.[5] Logical “0” is defined as impulse under the reference level 30 V DC. Logical “1” is lack of the same impulses.[5]
There exist an alternative interface speed at 4800 bit/s taken over from BatiBUS. But KNX TP-0 products will only operate on the same network. But not be able to exchange information with BatiBUS devices.[7]
Configuration modes
There are three categories of KNX device:
- A-mode or "Automatic mode" devices automatically configure themselves, and are intended to be sold to and installed by the end user.
- E-mode or "Easy mode" devices require basic training to install. Their behaviour is pre-programmed, but has configuration parameters that need to be tailored to the user's requirements.
- S-mode or "System mode" devices are used in the creation of bespoke building automation systems. S-mode devices have no default behaviour, and must be programmed and installed by specialist technicians.
KNX Products
One of the strengths of the KNX system, is that any product labeled with the KNX trademark is not a mere declaration of the manufacturer but is based on conformity testing carried out by KNX accredited third party test labs. During these tests, it is not only checked that the device supports the KNX protocol but that its useful data is coded according to the KNX standardized Data types.
This results in devices of different manufacturers and different applications that can be combined to a working installation.
The KNX Association member companies have more than 7000 KNX certified product in their catalogues.[8] This wide range of products allow, for example, the integration of:
- Lighting control
- Heating/ventilation & Air Conditioning control
- Shutter/Blind & shading control
- Alarm monitoring
- Energy management & Electricity/Gas/Water metering
- Audio & video distribution
On top of that you can enable access to the system via LAN, analog or mobile phone networks for having a central or distributed control of the system via PCs, Touch screens and Smartphones.
List of KNX Open Source or Free software
You can see at Ask About KNX forum a list of KNX open source or free software.[9] There is a wide variety of software for multiple operating systems and platforms running on PCs, Macs, Smartphones and tablets with Windows, Linux, OS X, iPhone/iPad iOS and Android.
See also
- BACnet
- DOLLx8
- EnOcean
- Home automation
- INSTEON
- Z-Wave
- Intelligent building
- Lighting control system
- Lonworks
- Modbus
- OpenTherm
- Room automation
- Smart Environments
- Touch panel
References
- ↑ Knx.org: What ist KNX?
- ↑ Knx.org: KNX Association Members
- ↑ Press Release: Fujitsu General joins as KNX member No. 300! PDF 2012-11-01
- ↑ Synco, KNX bus, Product range Synco 700, 900, RXB/RXL 2012-09-26
- ↑ 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 knx.org - Communication Reliability in the Intelligent Building Systems 2011-03-29
- ↑ 753-646 KNX/EIB/TP1 I/O Module 2010-11-30
- ↑ 7.0 7.1 7.2 7.3 7.4 7.5 7.6 7.7 tuwien.ac.at - Simulation of a KNX network with EIBsec protocol extensions
- ↑ Interview with Joost Demarest 2012-10-15
- ↑ Ask.AboutKNX.com - List of KNX Open Source or Free software
External links
- The KNX Association
- The KNX (UK) Association
- The KNX (Australia) Association
- The KNX (Hungary) Association
- KNX Interface Solutions
|