Hello. Sign In
Standards Store

DIN EN 13321-2

2013 Edition, March 1, 2013

Complete Document

Open Data Communication in Building Automation, Controls and Building Management - Home and Building Electronic Systems - Part 2: KNXnet/IP Communication

Detail Summary

Active, Most Current

Additional Comments:
Price (USD)
Single User
In Stock
Add to Cart

Product Details:

  • Revision: 2013 Edition, March 1, 2013
  • Published Date: March 2013
  • Status: Active, Most Current
  • Document Language: English
  • Published By: Deutsches Institut fur Normung E.V. (DIN)
  • Page Count: 172
  • ANSI Approved: No
  • DoD Adopted: No

Description / Abstract:

This European Standard defines the integration of KNX protocol implementations on top of Internet Protocol (IP) networks, called KNXnet/IP. It describes a standard protocol for KNX devices connected to an IP network, called KNXnet/IP devices. The IP network acts as a fast (compared to KNX transmission speed) backbone in KNX installations.

Widespread deployment of data networks using the Internet Protocol (IP) presents an opportunity to expand building control communication beyond the local KNX control bus, providing:

- remote configuration;

- remote operation (including control and annunciation);

- fast interface from LAN to KNX and vice versa;

- WAN connection between KNX systems (where an installed KNX system is at least one line).

A KNXnet/IP system contains at least these elements:

- one EIB line with up to 64 (255) EIB devices;


- one KNX segment (KNX-TP1, KNX-TP0, KNX-RF, KNX-PL110, KNX-PL132);

- a KNX-to-IP network connection device (called KNXnet/IP server);

and typically additional

- software for remote functions residing on e.g. a workstation (may be data base application, BACnet Building Management System, browser, etc.).

Figure 1 shows a typical scenario where a KNXnet/IP client (e.g. running ETS) accesses multiple KNX installed systems or KNX subnetworks via an IP network. The KNXnet/IP client may access one or more KNXnet/IP servers at a time. For subnetwork, routing server-to-server communication is possible.