System Specifications

Architecture

Glossary

Summary
This document provides a general glossary to the KNX Specifications.
Version 01.04.00 is a KNX Approved Standard.
This document is part of the KNX Specifications v2.1.
KNX Standard Glossary Architecture

Document updates
Version Date Modifications
1.0 2001.03.28 Approved Standard.
1.1 2008.12.12 Editorial update.
1.1.01 2009.11.06 - Update with “Differential download”
- AN118 “cEMI Transport Layer”: added “cEMI Transport Layer” and
“cEMI Transport Layer Services”
2010.07.15 - Included “HMI” of AN112.
1.1.02 2010.07.22 - AN117 “KNX Communication Medium” integrated.
1.1.03 2010.10.19 - AN127 “Master Reset” integrated.
1.1.04 2011.09.15 - AN134 “Flexible E-Mode Channels” integrated.
- Included “TP-UART”.
1.1.05 2011.09.28 - Added and clarified MSB, msb, LSB and lsb.
01.03.00 2012.09.10 - Revision of the integration of AN127 “Master Reset” according the
updated AN127 “Master Reset” v05.
01.04.00 2013.10.23 - AN153 “Mask 0912h Property based configuration” integrated.
- Editorial review in view of publication in the KNX Specifications v2.1.

References
[01] Volume 6 “Profiles”
[02] Volume 4: “KNX Hardware Requirements and Tests”
[03] Volume 9 “Basic and System Components/Devices – Minimum Requirements –
Standardised solutions - Tests KNX System Conformance Testing”
[04] Part 9/4 “BCUs and BIMs”

Contents
1 Glossary ................................................................................................................................... 3
2 List of abbreviations ............................................................................................................ 20

Filename: 03_01_02 Glossary v01.04.00 AS.docx

Version: 01.04.00
Status: Approved Standard
Savedate: 2013.10.23
Number of pages: 23

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 2 of 23

KNX Standard Glossary Architecture

1 Glossary
Term Definition

ack_request Service parameter informing the Data Link Layer on the required
L2-service acknowledgement when transmitting a Frame.

Address Number or name used for identifying entities in a KNX installation

(devices, group of devices, Shared Variable, Interface Object).
See also: Group Address, Individual Address

Adjusted E-Mode Channel This opposes to a Fixed E-Mode Channel. The definition of the available
Group Objects and Parameters depends on the value of the Adjustable
Parameter.
See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

Application An Application uses a set of functions to satisfy one user need.

An application is modelled as of one or more Functional Blocks and
covers one task within an Application Domain.
EXAMPLE In the HVAC Application Domain : direct electrical heating,
electrical heating with accumulators, warm water heating, fan
coil air-conditioning …

Application Domain Set of applications characterised by a common know-how, market

regulation, expertise...
EXAMPLE HVAC, lighting, security of goods, security of people, domestic
hot water, white goods …

Application Interface Object An Interface Object related to a user set of functions of a device.
EXAMPLE For storing and accessing the Parameters of a sensor
application.
See also: System Interface Object

Application Model Specification of the agreed solution for an Application in terms of

Functional Blocks, Datapoints and the links between them.

Application Modelling The process of analysing an Application, deciding on the common

solution and specifying and agreeing on the model in terms of
Functional Blocks, Datapoints and Datapoint Types.

Application Module (AM) That part of a modular KNX device that can be separated from the Bus
Coupling Unit. The Application Module typically determines the
function of the KNX device, i.e. whether it is a sensor (application
module is e.g. a push button) or actuator (application module is e.g. a
relay).

Application Process An element within an installation (this is, in a device) that performs
information processing for a particular application. The Application
Process ensures the operations needed to execute the application.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 3 of 23

KNX Standard Glossary Architecture

Term Definition

Application Product Is the combination of an Application Module, a Bus Access Unit and an
Application Program. In some cases two or more of these parts
constitute one unit, which can not be divided in the above mentioned
components (e.g. preloaded Application Programs in a KNX product, of
which the Application Module can not be separated from the BAU).

Application Profile Grouping and distribution of functions over several devices: defines
Functional Blocks grouping, and their external interfaces.

Application Program Functionality (software) in a KNX device that realises its Application
functions. It typically bases on API-functions for controlling hardware
inputs and outputs, to use Group Objects and Interface Objects to
interface to the KNX communication system. In S-Mode, the
Application Program is typically downloaded by means of ETS.

Application Reference Local reference for the Application Process, e.g. identification of a
Group Object.

Application Specification A complementary volume for a given application.

Its objective is to ensure KNX Interworking on basic functions subject to
agreement, keeping the possibility for inventive enhancements on
internal or complementary issues.

Area A Main Line and all connected Lines.

Backbone Coupler Router for connecting a Main Line to a Backbone Line of the same
Physical Layer Type.

Backbone Line The Backbone Line is the Subnetwork of the first level.
In the three-level topology the Backbone Line shall be the Subnetwork
connecting the Primary Sides of the Backbone Couplers.

Basic E-Mode Channel Specification of the minimal, mandatory Functional Blocks and
Datapoints thereof that compose an E-Mode Channel.
NOTE 1 The Basic E-Mode Channel gives the Channel Code to the Extended E-Mode
Channel.

See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

Basic Restart The feature of the KNX device to be able to receive an A_Restart-PDU
and restart the communication stack of the device or the entire device.
NOTE 2 In more complex devices, the microprocessor is not reset if an A_Restart is
handled.

See also: Master Reset

BiBat device A BiBat device shall be either

- a BiBat Master, a BiBat Slave or a BiBat Retransmitters, or
- a BiBat device with long header (Bidirectional RF alarm
sensor), or
- a BiBat device expecting feedback to own action.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 4 of 23

KNX Standard Glossary Architecture

Term Definition

BiBat device with long header A BiBat device with long header shall emit its (rare) alarm telegrams
with a 3,5 s header, thus allowing not only mains powered BiBat
Masters but also battery driven receivers with a wake-up period of
< 3,4 s. A BiBat device with long header shall implement such a
wake-up period of ≤ 3,4 s. In addition they may optionally use
synchronized communication with a BiBat Master according the
methods of synchronous BiBat Slaves.
SYNONYM Bidirectional RF alarm sensors

BiBat Master The BiBat Master shall be part of in a Synchronous BiBat System. It
shall be is a bidirectional RF device with permanent reception capability
that shall be able to transmit synchronous RF frames for the
communication with the BiBat devices of its domain. In addition it shall
support all asynchronous communication of the standard KNX RF.

BiBat Slave A BiBat Slave shall be a device that shall support bidirectional RF
communication. It shall be able to receive synchronous RF frames in
receive windows from a BiBat Master and shall be able to resynchronise
its internal clock and hence the position of its receive windows.

BiBat Slave expecting A BiBat Slave expecting feedback to own action asynchronously (not
feedback to own action periodically but rarely i.e. activated by human interaction or an alarm)
sends a telegram to a mains powered BiBat Master. It expects a fast
(typically < 100 ms) asynchronous Data Link Layer acknowledge from
its BiBat Master. In addition status information may be transmitted to
the initiating BiBat Slave and to other components of the application
using the standard principles of synchronous BiBat Slaves.

Bridge System Device interconnecting two (physical) Segments.

A Bridge will forward any frame from one Segment to another,
respecting the rules of the Data Link Layer.
SYNONYM TP1 Bridge

Broadcast Address Group Address 0000h used for the Broadcast Communication Service.

Bus Access Unit (BAU) A Bus Access Unit is a part of a KNX device containing electronics and
stack for its KNX communication and complying with at least the
minimum requirements as laid down in [01] as regards implemented
KNX protocol stack and agreed Physical Layer.

Bus Coupling Unit (BCU) A Bus Coupling Unit is a standardised Bus Access Unit.
See also: Bus Access Unit

Bus Device Under Test The combination of hardware (in standardisation normally referred to as
(BDUT) DUT or EUT) and software (in standardisation normally called SUT or
IUT).

Bus Interface Module (BIM) A Bus Interface Module is a standardised Bus Access Unit.
cEMI Transport Layer Transport Layer instance provided by a cEMI Server and accessible via
cEMI Transport Layer services.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 5 of 23

KNX Standard Glossary Architecture

Term Definition
cEMI Transport Layer Transport Layer services provided by the cEMI Transport Layer.
services
Certifiable Product Product for which requirements and tests have been laid down in the
KNX Specifications.

Certified KNX Product A product that conforms to the KNX Specifications minimum
requirements and has successfully passed the KNX Association
Conformance Assessment. As a consequence it may bear the KNX logo.
Such a product may either be an Application Product, a Basic - or
System Component or a software (tool or similar).
A certified Basic - and or System Component or Device may or may not
comply with the KNX standardised features as laid down in the
KNX Specifications [03]. These standardised features are optional for
certification: if implemented, the features however have to follow the
regulations of the KNX Specifications. Both the standardised as well as
the non-standardised solution may bear the KNX logo, provided in both
cases at least the minimum are fulfilled (for more information see [03]).

Channel Code Globally defined identifier for a given type of E-Mode Channel.
EXAMPLE Dimmer

Chapter Subdivision of a Part

EXAMPLE Chapter 3/2/2 specifies the KNX Twisted Pair 1 Communication
Medium.

Client Application Process using application-specific services offered by a

Server.

Client/Server Model Messaging Model using Interface Objects.

In this model each object belongs to the relevant application process of
one given device and is accessed by / provided to remote processes.

Coexistence Absence of unwanted interference of a device with other devices

Communication Mode Kind of object on which the communication relies.

See also: Group Objects, Application Interface Objects, System Interface
Objects

Communication Process A process providing reliable communication facilities between the

devices.

Communication Profile A consistent set of communication features supported by devices.

Intended for runtime Interworking in a given Profile.
See also: Configuration Profile; Device Profile

Communication Service A global service provided by the Communication Process to transfer

Messages. There are services for:
- group communication
- broadcast communication
- point-to-point connectless- and connection-oriented
communication
- TP1 Fast Polling

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 6 of 23

KNX Standard Glossary Architecture

Term Definition

Compatibility This word is ambiguous, it may be applied to any of the words

Coexistence, Exchangeability, Interworking, Interoperability,
Compatibility. It therefore should not be used

Complex Network Network where the hierarchical addressing is possible, under full control
of a professional installer.
See also: Simple Network

Configuration Operation : Establish links and set some functional parameters between
channels of devices that co-operate to provide a given system function.

Configuration Controller Controller that configures the links between Devices, Channels,
Functional Blocks or Datapoints.

Configuration Interworking Ability to set up links and parameters on two or more devices so that
they achieve afterwards Runtime Interworking.
See also: Runtime Interworking

Configuration Mode A way to configure a system.A specification describes, for each

Configuration Mode:
− the specific ways to use the standard communication features
− the process and usage of relevant network management
services.

Configuration Profile List of requirements for devices conerning configuration.

See also: Communication Profile, Device Profile

Configurator Configuration function whose role is to establish the link between

device’s channels, according to the inputs of the installer.
The function is hosted in a Configuration Controller.

Connection Code Globally defined identifier assigned to Datapoints in E-Mode that can be
linked together.
EXAMPLE Blinds_Move

Coupler A Coupler can be a Router or a Bridge.

Ctrl FEC The name of the Profile for the Controller Mode with Flexible E-Mode
Channels.
See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

Ctrl SEC The name of the Profile for the Controller Mode with Static E-Mode
Channels.
 This term replaces the indication “Ctrl-Mode”.

See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

Datagram Full sequence of elements (physical symbols) transmitted by a device as

such transporting a frame on the medium.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 7 of 23

KNX Standard Glossary Architecture

Term Definition

Datapoint A Datapoint is any interface over which data in the Functional Block can
be set or received and/or transmitted (for its run-time operation).
A Datapoint can be
- an Input,
- an Output,
- a Parameter
- a Status of Diagnostic Value
and can be implemented as
- Group Object
- Interface Object
- memory mapped value or
- TP1 Fast Polling Value.

Datapoint Type The specification of format, encoding, range and unit for Datapoints.

Derived Certificate Certificate granted to a KNX Association member company or licensee,

who markets a product under his own brand name for which a main
certificate already exists.
See also: Main Certificate

Descriptor Type The value of the field descriptor_type in the A_DeviceDescriptor_-

Read-PDU and the A_DeviceDescriptor_Response-PDU.

Destination Address The field in the KNX telegram that contains the Group Address or
Individual Address indicating to which device(s) the frame is sent.

Device The physical element which will be attached to the network. It is a

physical, concrete object that a customer can buy. Devices provide
different functions to the system for each distributed application. So it
contains one or more Functional Blocks.

Device Address Part of the Individual Address identifying a device in one Subnetwork.
Depending on the Configuration Mode, the Device Address shall be
unique within a Subnetwork. It is a one octet value.

Device Descriptor The value of the field device_descriptor in the A_DeviceDescriptor_-

Response-PDU.

device localisation action This shall be an action performed by the device and that should be
observable by a human and is further implementation dependent. It may
be
- a single short action, or
EXAMPLE 1 A relay may close and open again.
- a continuous state, or
EXAMPLE 2 An LED may flash.
- a repeated action, or
EXAMPLE 3 A signal tone may be given periodically.
- any implementation specific action.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 8 of 23

KNX Standard Glossary Architecture

Term Definition

Device Profile Standardised set of features of a device required for configuration and
runtime interworking. It consists of
- a Communication Profile, and
- a Configuration Profile.

Differential Download Optimisation of the Configuration Procedure in S-Mode, in which only

the data is downloaded that is assumed to differ between the current
contents and the intended contents after download.
NOTE 3 To this purpose, the Management Client may for instance hold a
memory image of a preceding download, which it compares with a new memory
image (new parameters, links…) to decide on which data to write in the device.

Domain Logical Network on open media.(in a network with several media, part
of the network on one given open medium).

Domain Address Address of a Domain on open media. Identifies one Logical Network, so
insulated from neighbouring networks.

Easy Configuration Mode This is a Configuration Mode requiring only a limited number of simple
(= Easy Mode- manual operations, possibly using a (electronic) "screwdriver", and with
limited cost. Higher complexity is reached by switching to the
(= E-Mode)
Configuration Mode “System Mode” (= S-Mode).
See also: System Configuration Mode

E-Mode Channel An independent functional part of device containing a standardised

combination of one or more Functional Blocks.
EXAMPLE A 4 fold binary input has 4 channels.
See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

Engineering Tool A standard set of components and Application Programmer’s interfaces

Environment Components for KNX PC software engineering.
(EteC)

Engineering Tool Software Removable tool used for planning and commissioning KNX
(ETS) installations, supporting all KNX approved media. It contains a standard
database of device description files and application programs
SYNONYM System Tool

eteC Repository Collection of templates of KNX products and applications, which may
be used in ETS projects, currently stored in a database.

ETS Catalog Entry A catalogue entry in the ETS Window ‘Product Sets’ groups the
commercial data of a product defined in the ETeC repository and is
symbolised by a booklet. A catalogue entry is linked to a product: the
latter does not contain any commercial information. A product is
symbolised by an agreed product symbol. Many catalogue entries, i.e.
many commercial variations may be attributed to one product if all these
variations belong to a same product group.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 9 of 23

KNX Standard Glossary Architecture

Term Definition

Exchangeability Possibility for one product to fully replace another product (which may
be from another manufacturer) and to provide all the same functionality.
Full exchangeability is difficult to achieve, because it requires an
exhaustive definitions of the products and does not enable the
manufacturers to distinguish their products from the other’s.
Exchangeability is not the target of KNX.

Extended E-Mode Channel Specification of a Basic E-Mode Channel extended with possible
(allowed) additional, optional extensions that are implemented.
NOTE 4 An Extended E-Mode Channel does not have an own unique Channel Code. It
has the Channel Code of its Basic E-Mode Channel. Two or more implementations of the
same Extended E-Mode Channels, differing in their implemented set of optional features
will still have the same E-Mode Channel Code.

See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

External Message Interface The External Message Interface provides a generic message interface to
(EMI) each KNX OSI stack protocol layer. This optional interface is defined to
enable generic solutions for configuration tools or modular devices.

Fixed E-Mode Channel This opposed to an Adjusted E-Mode Channel. The definition of the
available Group Objects and Parameters is fixed.
See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

Flexible E-Mode Channel The possibility to specify and implement optional functionality (Group
Objects, Parameters) in E-Mode Channels.
See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

Frame Sequence of octets exchanged between Data Link Layer instances over
the medium or media. It contains all information needed to ensure the
exchange.
SYNONYM LPDU.

Function A self-contained part that describes part of the behaviour of a Functional

Block and that is not standardized.
EXAMPLE logical and arithmetic functionals, morning boost, read outside temperature

Functional Block Consists of one or more Functions that belong together and that can not
be separated across two devices but big enough that a device with only
one such Functional Block could be marketed. A Functional Block has a
well-defined black-box behaviour.
EXAMPLE boiler controller, room demand manager, demand transformer.

Functional Safety Those issues, specific to an Application Domain, and which come in
addition to, or as a precision to the general HBES functional safety
requirements (see CLC TC205 documents) and the normal product
functional safety requirements (see the relevant product standards).

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 10 of 23

KNX Standard Glossary Architecture

Term Definition

Gateway Device interconnecting a KNX network with an external network, on top

of Application Interface Layer.

Group Address The Group Address identifies one or several entities in the network (one
Shared Variable or several devices). It is a two octet value. A device
may have/know more than one Group Address.
Group Addresses are defined globally for the whole network. However
the specification allows local and global Group Addresses by defining in
each frame the maximum number of Routers to be crossed.

Group Address Table This table contains each Group Address known by a Device. It enables
to a Group Address to be converted into a local Group Index and vice
versa.

Group Association Table This table enables a Group Index to be converted into a local Application
(GrAT) Reference and vice versa.

Group Index Abstract internal reference of a communication relationship. Enables to

build indirection's between Group Addresses or Individual Addresses
and Application References.

Group Object Local image in the device of a Shared Variable available in the
installation.
EXAMPLE light_level in room x

Group Object Handle A handle for accessing Group Objects in point-to-point communication
via the Property PID_OBJECT_VALUE.

Hop Count Service Parameter indicating to the Network Layer how many
Subnetworks the message is allowed to pass. Its use is to prevent endless
circulation of messages in case of incorrectly configured installations.

Identifier (Id) Global identification in the KNX System of a given feature.

EXAMPLE Every standard Interface Object is assigned a unique Identifier, the Object
Type. Object Type 320 for instance uniquely identifies the Functional Block modelling the
Outside Temperature Sensor.

Index (Idx) Local identification in a device of a feature in an ordered list.

EXAMPLES an element in an array, Interface Object index in the list of Interface
Objects of a device

Individual Address Address of a given Device in an installation. The Individual Address is a

two octet value that consists of an eight bit Subnetwork Address and an
eight bit Device Address. If the Device Address is unique, then also the
Individual Address will be unique in the installation.

Installed system A set of distributed applications and the underlying communication

infrastructure. It is made of several devices linked by a medium (with or
without cabling).

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 11 of 23

KNX Standard Glossary Architecture

Term Definition

Interface Object An implementation of a standard model for accessing data in a device,

using dedicated Application Layer services and independently of the
device specific storage. Interface Objects are handled by the Interface
Object Server in the Application Interface Layer. An Interface Object
contains one or more Properties.
See also: Application Interface Object, System Interface Object, Property

Interoperability (of Capability of a device, in conformance with a set of standards, to

communication) communicate with other devices.
See also: Interworking, Exchangeability

KNX KNX provides one consistent system for applications in the home and
buildings, from residential home to tertiary buildings.

KNX Basic and System These are products of which the features are explicitly laid down in the
Components/Devices KNX Specifications.
Some of these features are standardised (see [03]), of which compliance
is optional for certification.
As basic and system components/devices constitute the core of the KNX
system, they shall comply with the hardware requirements as laid down
in [02].

KNX Basic A KNX product without communication relevant part.

Components/Devices The following basic components are defined:
TP Cable, several connector types (DIN rail contact block, bus
interface connection block (for BCU), PEI, data rail to wire
connector, …), TP data rail (cover), TP overvoltage protector, TP
power supply unit, TP choke, PL filter, PL phase coupler.

KNX IP Usage of the Internet Protocol as a KNX communication medium.

KNX IP device A KNX device using the Internet Protocol as the only KNX
Communication Medium.
NOTE 5 A KNXnet/IP Tunnelling Server and a KNXnet/IP
Router are no KNX IP devices.

KNX Serial Number The KNX Serial Number (or Unique Code), is a globally unique
identifier, programmed at manufacture, used to distinguish devices. The
KNX Serial Number is exactly 6 octets. First two octets are the
Manufacturer’s Code.

KNX Specification Specification of the KNX System.

KNX System The KNX System provides a generic means for the exchange of
messages between distributed functions of one or more applications.

KNX System Components A KNX product with a communication relevant part enabling connection
of an application part (as specified in ) is considered a KNX system
component.
EXAMPLE BCU UP TP/PL, BCU AP/GE TP/PL, BCU N TP/PL, standardised Bus
Interface Modules

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 12 of 23

KNX Standard Glossary Architecture

Term Definition

KNX Tools Software packages such as visualisation and control software, planning
and configuration tools and test tools.

KNXnet/IP Client An application that implements the KNXnet/IP Client protocol to get
access to a KNX Subnetwork over an IP network channel.

KNXnet/IP Router A dedicated type of KNXnet/IP device that routes KNX protocol packets
between KNX Subnetworks.

KNXnet/IP Server A KNX device that has physical access to a KNX network and
implements the KNXnet/IP Server protocol to communicate with
KNXnet/IP Client or other KNXnet/IP Servers (in case of KNXnet/IP
Routing) on an IP network channel. A KNXnet/IP Server is by design
always also a KNX node.

Layer Subdivision of the OSI Architecture, that hierarchically structures a

communication system into several layers.

Line (Logical) The Line is the Subnetwork of third level.

The Line shall serve to connect the Secondary Sideof one Line Couplers.
One or more Bridges may be present on a Line.
See also: Main Line; Backbone Line

Line (Physical) The physical medium carrying the data exchange and power feed
services. A Line may be physically subdivided into several (physical)
Segments, interconnected by Bridges or Repeaters.

Line Coupler Router for connecting a Line to a Main Line of the same Physical Layer
Type.

Logical Tag Logical number given to one or more devices. Depending on the value, it
corresponds to a zone number (which may be functional,
geographical…) or to an Individual Address. Correspondence rules are
standardized.

Main Certificate Certificate granted to a KNX Association member company or licensee,

who was responsible for the development of a KNX compatible product
and applied to have it certified by the KNX Association.
See also: Derived Certificate

Main Line The Main Line is the Subnetwork of the second level.
In the three-level topology the Main Line shall serve to connect to the
Primary Sides of one or more Line Couplers and to the Secondary Side
of one Backbone Coupler.
See also: Line, Backbone Line

Mains The low voltage electricity distribution network of 230 V/50 Hz.

Manufacturer’s code Global identifier assigned to a manufacturer. Manufacturer’s codes are

administered by the KNX Association. The Manufacturer’s code is made
of 2 octets.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 13 of 23

KNX Standard Glossary Architecture

Term Definition

Mask Version Identification of an implementation, for operation like download,

memory_write ...(dedicated operations themselves are out of the scope
of the specification).
In particular, the Mask Version is read through a dedicated Application
Layer service by the S-Mode Management Client (ETS) to conclude on
the Configuration Profile of the device and on possible further discovery
and configuration steps.
SYNONYM: Device Descriptor Type 0

Master Product The Master Product is a product selected by the manufacturer out of a
product group. Only this product is submitted to the required
conformance tests. However, the results of these tests are applicable for
all the other members of the group.

Master Reset The feature of the KNX device that assumes the support of the Basic
Restart and additionally at least one of the following features.
- Reset of the device to its ex-factory state.
- Reset of the IA to the default, medium dependent IA.
- Reset of all GO-links (Group Addresses, Associations),
possibly per application channel.
- Reset of the application to the default application.
- Reset of the Application Parameters to their default value,
possibly per application channel.
See also: Basic Restart

Media Coupler Router for connecting two Subnetworks of different Physical Layer
types.
See also: Router, Transparant Media Coupler

Member of Product Group All products of a product group including the master product.

Message Data exchanged between two adjacent layers - say (N+1)-layer and
(N)-layer in the OSI communication model.

Messaging Model A way to define the distribution of information in the system for one
given application, and corresponding types of communication
exchanges.
Used messaging models are:
- Shared Variable
- Client/Server

Network The Network is made of 1 or several logical Subnetworks,

interconnected through Routers.

Non-certifiable Product A product for which requirements and tests are not defined in the
KNX Specifications (e.g. peripheral devices such as infrared remote
transmitter) at the time of application for certification. As a
consequence, they may not be branded with the KNX logo.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 14 of 23

KNX Standard Glossary Architecture

Term Definition

Non-selective Data Link Acknowledge by the Data Link Layer upon reception of
Layer acknowledge − an L_Data-PDU in multicast communication mode irrespective
of whether the destination Standard Mode Group Address is
contained in the Group Address Table of the receiver, or
− an L_Data_Extended-PDU in multicast communication mode
irrespective of whether the destination standard mode Group
Address is contained in the Group Address Table of the
receiver or is an LTE-HEE Group Address that addresses a
zone assigned to the receiving device.

Octet Count Service parameter defining number of significant octets in a APDU.

OSI model Open Systems Interconnection Reference Model (OSI Model or OSI
Reference Model for short) is a layered abstract description for
communications and network protocol design. Standardized by the
International Standards Organization ISO.

Part Subdivision of a Volume of the KNX Specifications.

EXAMPLE Part 3/2 contains several Chapters specifying the KNX Communication Media.

PB FEC The name of the Profile for the Push Button Mode with Flexible E-Mode
Channels.
See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

PB SEC The name of the Profile for the Push Button Mode with Static E-Mode
Channels.
 This term replaces the indication PB-Mode.
See also: Adjusted E-Mode Channel, Basic E-Mode Channel, Ctrl FEC,
Ctrl SEC, E-Mode Channel, Extended E-Mode Channel, Fixed
E-Mode Channel, Flexible E-Mode Channel, PB FEC, PB SEC

Physical External Interface Optional standardised interface between a Bus Access Unit and an
(PEI) Application Module.

Primary side of a Coupler In the TP1 three-level topology, if the Coupler is configured as a Line
Coupler, this is the Main Line. In case the Coupler is configured as
a Backbone Coupler, this is the Backbone Line. In case the Coupler is
configured as a Bridge, this is the part of the Line containing
other Couplers and possibly other devices.
See also: Coupler, Router, Secondary side of a Coupler

Priority Service Parameter defining different priority levels for transmitting a

frame. The priority level is encoded in the frame, and attained (or not) in
a specific way for each medium.

Product Any device, component or tool that is connected to the KNX network
(whether or not with communication relevant parts).A way to define the
distribution of information in the system for one given application, and
corresponding types of communication exchanges.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 15 of 23

KNX Standard Glossary Architecture

Term Definition

Product Group The collection of all products for which the KNX Association
requirements apply in the same way and give the same result during
conformance assessment.

Property (of an Interface Addressable object representing one aspect of an internal object. The
Object) Property is an addressable part of an Interface Object.
The Property consists of the Property Description and the actual
Property Value.
EXAMPLE A Property containing the Object Type, a Property containing a
setpoint value of some control

Protocol Data Unit (PDU) Sequence of an integral number, N, of octets numbered O0 through ON-1.
Each octet may be viewed in turn as a sequence of eight bits numbered
b7 through b0. Throughout this document OI is shown to the left of OI+1
and b j to the left of b j-1. In one octet, b7 is the most significant bit
(MSB), b0 the least significant one (LSB).
On the physical medium, the bit order in each octet is medium
dependent.

Quality Of Service Set of service parameters specifying the quality level to be reached when
transmitting a frame. Includes the Priority parameter.

Re-assessment Procedure that is applied when modifications are carried out to an

already certified product (be it main or derived).

Repeater System Device interconnecting two Segments. A Repeater will forward

every physical symbol from one segment to another.
See also: TP1 Repeater

RF chip A chip tick shall be the basic time unit of the RF synchronous system. Its
duration is 1/32 768 s (approx. 30,5 µs). This shall also the basic RF
chip rate of any KNX RF system.

Router System Device interconnecting two Subnetworks. A Router will forward

a Frame from one Subnetwork to another depending on the Destination
Address and position of devices in the network.
A Router can be either a Line Coupler or a Backbone Coupler
See also: Transparant Media Coupler

Runtime Interworking Capability of a product, in conformance with a set of standards, to

communicate with other products and to properly operate their intended
functions or properly respond to their stimuli according to the
application specifications.
See also: Configuration Interworking

Secondary side of a Coupler In the TP1 three-level topology, if the Coupler is configured as a Line
Coupler, this is the Line. In case the Coupler is configured as
a Backbone Coupler, this is the Main Line. In case the Coupler is
configured as a Bridge, this is the part of the Line possibly containing
other devices but no Couplers.
See also: Coupler, Router, Primary side of a Coupler

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 16 of 23

KNX Standard Glossary Architecture

Term Definition

Segment Physical elementary subdivision of a Physical Line.

Selector Any kind of selector enabling to set a logical tag: coding wheel, jumper,
dip switches, electronic screwdriver+EEPROM, …

Server Application Process providing application-specific services.

See also: Client

Service Function provided by an (N)-Layer to an (N+1)-Layer.

Service Access Point The point at which Service Primitives are exchanged between adjacent
layers.

Service Element An Active Element within a Layer embodying a set of functions.

Service parameters Parameters delivered by the (N+1)-layer to the (N)-layer in a service

primitive and needed by the (N)-layer to produce the protocol control
information ((N)-PCI) of the (N)-layer PDU.

Service primitive A primitive exchanged between adjacent Layers, related to a given

Service. It transports a Message and Service Parameters.

Shared Variable An object in the Shared Memory Model, belonging to the system. A
local copy (or instance) of such a variable is called a Group Object. Also
referred to directly as Group Object.
See also: Group Object, Shared Memory model

Shared Variable Model Messaging model based on Group Objects. In this model each object
belongs to the communication system. The object may be produced
and/or consumed by several devices.

Simple Network Network with one or a very limited set of Subnetworks, without
configuration of Routers (flat addressing).
In such installations, (all) Subnetwork(s) shall be using their default
Subnetwork Address.
To allow consistent management, such a network is limited to at
maximum one instance of each possible medium.
Routers - if any – shall be Transparent Media Couplers. Installation of
such Routers don't require a professional installer. There are no
requirements on topology.
See also: Complex Network

Source Address Address field; contains the Individual Address of the device that
transmits a Frame.

Subnetwork Logical subdivision of a Network. Subnetwork have a different name,

depending on their position in the Network hierarchy: Backbone Line,
Main Line and Lines.

Subnetwork Address Part of an Individual Address identifying a Subnetwork in a network.

The Subnetwork Address consists of a four-bit Main Line Number and a
four bit Line Number.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 17 of 23

KNX Standard Glossary Architecture

Term Definition

Synchronous BiBat System A Synchronous BiBat System consists of a single BiBat Master and one
or several BiBat Slaves (devices). Optionally there can be BiBat
Retransmitters in addition.

Synchronous RF Frame These are the Frames that are transmitted by a BiBat Master to its BiBat
Slaves in a time-slotted mechanism. These can be data Frames or Sync
Frames. They are identified by a dedicated value of the KNX Crt-field in
the frame.

Synchronous RF A Synchronous RF Retransmitter shall have permanent RF reception

Retransmitter capabilities (normally mains powered). It shall retransmit Synchronous
RF telegrams with a fixed time delay without the usual collision
avoidance of anynchronous RF. It shall treat asynchronous telegrams
like an asychronous RF Retransmitter.
SYNONYM BiBat Retransmitter

System Configuration Mode This is a Configuration Mode where the installation is designed and
(= System Mode) configured by using a tool (e.g. PC based, perhaps including CAD
functions). The tool enables to manage the system complexity efficiently
(= S-Mode)
and with reliability. The configuration may be very detailed.
KNX S-Mode installations are configured by means of the ETS
software.
See also: Easy Configuration Mode, Engineering Tool Software (ETS)

System Device A KNX device with (one or more) communication relevant part(s) not
enabling connection of an additional application part (as specified in
[04]) is considered a KNX system device.
EXAMPLE TP1 Coupler, EDI/RS232, appliance interface, TP/PL Media
Coupler, PL110 Repeater, TP1 Repeater.

System Interface Object Internal Object related to a system function of a device

EXAMPLES Application Program, Group Address Table….
This may be accessed dedicated L7 services.

TP1 Repeater System Device interconnecting two (physical) TP1 Segments. A

TP1 Repeater will forward any frame from one Segments to another
without filtering (this is a Bridge functionality), but with hop count
decrement (this is a Router functionality).

TP-UART A specific commercially available integrated solution for KNX TP1 bus
access.

Transparant Media Coupler A Router that couples two different media and does not requires
configuration.
It forwards broadcast-, multicast- and point-to-point messages without
filtering but with evaluation of the hop_count.
See also: Router, Media Coupler

user localisation action: This shall be an action performed by a human on the device. the specific
realisation is implementation dependent.
EXAMPLE 4 a press on a rocker of a push button

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 18 of 23

KNX Standard Glossary Architecture

Term Definition

Volume Self consistent set of documents of the KNX Specifications, dedicated to

a given aspect.
EXAMPLE Volume 3 “System Specifications”

Zone Usually a geographical entity like a room, an appartment… May also be

functional.

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 19 of 23

KNX Standard Glossary Architecture

2 List of abbreviations
Abbreviation Description
AA Area Address
AC Alternating Current
ACK Positive Acknowledgement
ADC Analog to Digital Converter
AIL Application Interface Layer
AIL-PDU Application Interface Layer PDU
AIS Application Interworking Specifications
AL Application Layer
AM Application Management
Application Module
AP Application Process
Application Program
APDU Application Layer PDU
API Application Programmer’s Interface
APS Ancillary Power Supply
ASAP Application Layer Service Access Point
ASCII American Standard Code for Information Interchange
BAU Bus Access Unit
BCU Bus Coupling Unit
BDUT Bus Device Under Test
BIM Bus Interface Module
cEMI Common EMI
COM Communication
CSMA Carrier Sense Multiple Access
CSMA/CA Carrier Sense, Multiple Access, with Collision Avoidance
DAA Distributed Address Assignment
DAF Destination Address Flag
DC Direct Current
DD0 Device Descriptor Type 0
The value 000000b for the Descriptor Type in the A_DeviceDescriptor-
_Read-service.
DD2 Device Descriptor Type 2
The value 000010b for the Descriptor Type in the A_DeviceDescriptor-
_Read-service.
DLL Data Link Layer

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 20 of 23

KNX Standard Glossary Architecture

Abbreviation Description
DoA Domain Address
DPSU Distributed Power Supply Unit
DPT Datapoint Type
EITT KNX (formerly EIB) Interoperability Test Tool
EMC Electro Magnetic Compatibility
EMI External Message Interface
eteC KNX Tool Environment Components
ETS KNX Engineering Tool Software
FB Functional Block
FCS Frame Check Sequence / Frame CheckSum
FEC Flexible E-Mode Channel
See also: Flexible E-Mode Channel

FOCI Function Of Common Interest

GA Group Address
GO Group Object
GrAT Group Addresss Table
GrOT Group Object Table
Group_Obj Group Object
HBES Home and Building Electronic Systems
HID Human Interface Device
HMI Human Machine Interface
ID Identifier
Idx Index
IMI Internal Message Interface
Int_Obj Interface Object
IO Interface Object
IOT Interface Object Type
IR Infra-Red
KMB KNX Association Marketing Board
KSG KNX Association System Group
KTB KNX Association Technical Board
L2-acknowledge Layer 2 acknowledge (values ACK, NAK, BUSY, FULL)
L4-acknowledge Layer 4 acknowledge
LA Line Address
LPDU Data Link Layer PDU

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 21 of 23

KNX Standard Glossary Architecture

Abbreviation Description
LSAP Link Layer Service Access Point
lsb Least Significant Bit
LSB Least Significant Byte
LSM Load State Machine
MC Message Code
msb Most Significant Bit
MSB Most Significant Byte
NL Network Layer
NM Network Management
NPDU Network Layer PDU
NRZ Non Return to Zero
OS (PC) Operating System
OSI Open Systems Interconnection
PCI Protocol Control Information
PDT Property Datatype
PDU Protocol Data Unit
PEI Physical External Interface
PELV Protective Extra Low Voltage
PhL Physical Layer
Ph-PDU Physical Layer PDU
PID Property Identifier
PL Powerline
PSU Power Supply Unit
RF Radio Frequency
SAP Service Access Point
SDU Service Data Unit
SEC Static E-Mode Channel
SELV Safety Extra Low Voltage
SL Session Layer
SM System Management
SNA Subnetwork Address
TF Task Force
TL Transport Layer
TP Twisted Pair
TPDU Transport Layer PDU

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 22 of 23

KNX Standard Glossary Architecture

Abbreviation Description
TP-UART Twisted Pair Universal Asynchronous Receiver/Transmitter
See also: TP-UART

TSAP Transport Layer Service Access Point

UART Universal Asynchronous Receiver/Transmitter
USB Universal Serial Bus
WG Working Group

© Copyright 1998 - 2013, KNX Association System Specifications AS v01.04.00 - page 23 of 23