1 / 24

The KNX system in a nutshell. (a tiny part of a great story)* Marc Goossens – Konnex Association

The KNX system in a nutshell. (a tiny part of a great story)* Marc Goossens – Konnex Association. ISO/IEC JTC 1/ SC25 / WG 1 Brussels, March 17, 2005. Network Management and Configuration Modes. The KNX System Architecture. ETS – the unique vendor-neutral PC software for KNX. KNX Interworking.

guido
Download Presentation

The KNX system in a nutshell. (a tiny part of a great story)* Marc Goossens – Konnex Association

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. The KNX system in a nutshell.(a tiny part of a great story)*Marc Goossens – Konnex Association ISO/IEC JTC 1/ SC25 / WG 1Brussels, March 17, 2005

  2. Network Management and Configuration Modes.The KNX System Architecture.ETS – the unique vendor-neutral PC software for KNX.KNX Interworking. 1 2 3 4 « The basic ingredients. An invitation. »

  3. Management and Configuration in KNX... an integral part of our solution. 1 « While autonomous consumer goods may get by with plug-and-play, distributed applications like lighting, shading, heating and cooling must be designed and configured to suit the requirements of each individual home or office. »

  4. PC-based Master Device Local (Touch) Local (TAG) Auto The KNX Configuration Modes  Our answer to a variety of real-world needs.

  5. A A B C C B System (“S”) mode for PC-based configuration with common ETS software • import “product libraries” (A, B, C, ...) from product vendors • design required configuration for entire project off-line • configure installation by on-line download ETS • [identify / discover device] • [load executable application] • [load application parameters] • [load bindings] PC-based Master Device Local (Touch) Local (TAG) Auto

  6. Legend 0.0.255 IP Backbone Line 0.0.1 0.0.2 ML Main Line L Line ... IP Router IP Router IP Router IP Router 1.0.0 2.0.0 3.0.0 15.0.0 2.0.1 3.0.1 1.0.1 15.0.1 2.0.2 3.0.2 1.0.2 15.0.2 Main Line 1 ML 2 ML 3 ML 15 2.0.255 3.0.255 1 .0.255 15.0.255 15.1.0 15.2.0 15.3.0 15.15.0 LC LC LC LC LC LC LC 15.1.1 15.3.1 15.15.1 15.2.1 15.1.2 15.3.2 15.15.2 15.2.2 L L L L L L L 15.1.255 15.3.255 15.15.255 1.2 1.3 1.15 15.1 15.2 15.3 15. 15 15.2.255 Addressing capabilities KNX supports a 16 bit Individual Address space Legend ¡ IP Router ¡ LC Line Coupler ¨ End Device Line Coupler 1.2.0 1.3.0 1.15.0 1.2.1 1.1.0 1.3.1 1.1.1 1.15.1 1.2.2 1.3.2 1.1.2 1.15.2 Line 1.1 1.2.255 1.3.255 1.1.255 1.15.255

  7. Easy (“E”) Controller Mode with Master device • activate Master to “acquire partner devices” • [search devices] • connect / activate further devices one by one (Master learns!) • [identify / discover device] • link channels (via Master menu or by “touching” devices) • [load bindings] • tune parameters (via Master menu) • [load parameters] Master (“Controller”) Master (“Controller”) PC-based Engineering Master Device Local (Touch) Local (TAG) Auto

  8. Easy (“E”) Push-button Mode = peer-to-peer touch-to-link for each intended link: • activate actuator to “acquire” sensors as “partner devices” • touch appropriate sensor to be “enrolled”  [set up link (on sensor’s request)] PC-based Engineering Master Device Local (Touch) Local (TAG) Auto

  9. KNX Logical Tag Extended (“LTE”) mode = advanced on-device configuration fan coil unit for each device: boiler unit • (connect HMI interface to device if not present) • assign semantical or geographical zoning tag • tune device / application parameters hot water valve positioner air valve positioner also permits configuration with ETS! ETS LTE = a compatible extension to the KNX system PC-based Engineering Master Device Local (Touch) Local (TAG) Auto

  10. Automatic (“A”) mode = peer-to-peer plug-and-play plug each device ... [device acquires address] [announces itself on network] [interested communication partners may discover newly plugged device] [interested communication partners may build links with newly plugged device]  realization today as “EHS” PC-based Engineering Master Device Local (Touch) Local (TAG) Auto

  11. KNX proposes a flexible architecturefor an open technology. 2 « Numerous manufacturers integrate their own KNX implementations. Several independent technology-providers are eager to help you getting started.»

  12. IP Communication Services Port No. 367; IP- MA 224.0.23.12 (assigned by IANA) Transport Layer Network Layer UDP TCP Link Layer (R)ARP ICMP BootP/DHCP IGMP Ethernet WLAN KNX Communication Architecture - Infrastructure Media KNX Twisted Pair KNX Powerline KNX Radio Freq.

  13. KNX Communication Architecture – Run-time API Run-time Run-time AL Core Model (Publisher / Subscriber Datapoints) “Communication Object” Datapoints Multicast API IP Communication Services Multicast Routing Transport Layer Full 64K linking space between any group of datapoints! Network Layer UDP TCP Link Layer Media KNX Twisted Pair KNX Powerline KNX Radio Freq. Ethernet WLAN

  14. Configuration & Servicing Management AL Resources Model (handler) Service API (apci’s + payload) API ETS Broadcast Point-to-point KNX Communication Architecture – Life Cycle API Run-time Run-time AL Core Model (Publisher / Subscriber Datapoints) “Communication Object” Datapoints Multicast API IP Communication Services Multicast Routing Tunneling Transport Layer Network Layer UDP TCP Link Layer Media KNX Twisted Pair KNX Powerline KNX Radio Freq. Ethernet WLAN

  15. Configuration & Life-cycle (Servicing) Management AL Configuration & Life-cycle (Servicing) Resources Model (handler) Service API (apci’s + payload) Management AL API Resources Model (handler) Service API (apci’s + payload) KNX Communication Architecture – Life Cycle API

  16. Configuration & Life-cycle (Servicing) Management AL Appl NL Dedicated Resource Handler (some “Easy-modes”) Dedicated API Identification + Discovery AL LL Shared Resources Model (handler) Service API (apci’s + payload) TL PL • Generic Resource Model • object.property • stream (file) Generic API Platform Resource Pool (“Raw”) KNX Communication Architecture – Life Cycle API  publish  Distributed Control requires Configuration Interworking models!

  17. The ETS engineering software for KNX... today 18’000 registered users worldwide. 3 « The 3rd generation ETS 3 embodies 14 years of our Association’s experience and know-how in open tools for home and building engineering. »

  18. ETS = the unique, common tool for the design, configuration and servicing of KNX sites. • The ETS tool suite is vendor / manufacturer-independent. • User imports “Product Libraries” from any desired manufacturers. • A toolkit for product manufacturers supports product testing and creation of Product Libraries. • The ETS end-user edition now comes in 2 versions: • ETS 3 Starter – entry level / single-home projects = 149,- € • ETS 3 Professional – full edition – 895, - € ETS 3 – launched at the Light+Building Fair Frankfurt, April 2004 ETS 3 Professional ETS 3 Starter

  19. A world of business with KNX.  Today, an estimated 50% of KNX product business is realised outside Germany. • ETS and KNX: business enablers for thousands of installation companies worldwide. • Today, about 8’860companies are registered “KNX Partner” and have made KNX their daily business. • Most are small or medium-size enterprises in the business of electrical or hvac installation, real estate development, contracting and consulting, facility management and home and building services. • Worldwide regional distribution (12.2004): Uwe Knüpfer Helmut Lintschinger the Elektro-Rothenhager van

  20. KNX / ETS Training = a multiplier for global business with KNX  Today, fastest growth of KNX product business is achieved in exports. • Today, 97 Certified KNX Training Centres teach KNX and ETS usage to professional users worldwide. • KNX is on the official technical education curriculum in a growing number of countries: • Worldwide regional distribution: at the DIAL Training Centre

  21. Welcome to KNX. Welcome to Interworking. 4 « Since 15 years, KNX/EIB leads the way in open, multi-vendor interworking in tens of thousands of installations – without any engineering overhead. »

  22. Why Application Interworking? • For the home owner: continuity of the solution over typical building product lifetimes of 20 years and more. • For contractors and installers: a broad choice of products and solutions. • For integrators, operators and Facility Managers: smooth integration and connectivity. • For product managers and developers: a solid guideline as a starting point for creativity. • For manufacturers: improved customer acceptance. • For niche players with specialised products: immediate market potential. • ... • overview of the KNX Functional Block scheme for HVAC applications  But... KNX’ Configuration Interworking is essential to bring Application Interworking to life!

  23. The building blocks for KNX Application Interworking. output datapoints • The KNX specification essentially fixes: • The “atoms” of interworking: Datapoint Types • The “molecules” of interworking: Functional Blocks = a grouping of typed datapoints, representing the operational interface (with inputs and outputs) of one instance (“channel”) of a function. • The “organisms” of interworking: Distributed Application Models input datapoints application model Basic Dimming  Manufacturers get ample room for differentiation, while rich Interworking remains ensured.

  24. Thank you for your attention. ISO/IEC JTC 1/ SC25 / WG 1 Brussels, March 17, 2005

More Related