wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

42-6 Industrial Communication Systems
with either the KNX individual or group address (correspondingly referred to as an extended individual or
an extended group address) was introduced. Transmit-only devices also use preassigned group addresses.
To allow an adequate battery lifetime for battery driven bidirectional devices as well, a synchronous operation
mode was defined. In this mode, devices need only have their receivers enabled during certain time
windows which are known by all nodes. Also, the specification includes a draft for extending KNX RF to
multiple channels, different signalling speeds, additional frequency bands, and providing additional features
for power-saving asynchronous receiver operation.
KNX Powerline 110 (PL110) uses the 230.V/50.Hz electrical power supply network for data and power
transmission (in compliance with EN 50065-1). Half-duplex bidirectional communication is supported.
KNX data are modulated using spread frequency shift keying (SFSK) with a center frequency of 110.kHz.
The signal is injected between phase and neutral and is superimposed to the sinusoidal oscillation of the
mains. No restrictions are made on the physical topology of the installation. Repeaters can be installed
in three-phase networks if passive phase coupling is not sufficient. Owing to the relatively poor transmission
properties of the mains network, the data transmission rate is limited to 1200.bit/s. Each data
link octet is coded into a 12 bit character (8 bit data, 4 bit error correction). Medium access control is
based on a slotted technique to reduce the probability of collisions: After the minimum silence period
between two frames has elapsed, two time slots are reserved for pending high-priority transmissions,
followed by seven more from which nodes with pending standard-priority transmissions choose one at
random as their starting time. PL110 was taken over from EIB. The EHS powerline medium was also
part of the KNX standard under the name of PL132, but was removed from release 2.0.
Regarding the transportation of KNX telegrams on top of IP networks, KNXnet/IP (formerly
known as EIBnet/IP) currently focuses on scenarios for enhancing central and/or remote management.
KNXnet/IP specifies several service protocols. The KNXnet/IP Core Services define the packet structure
and methods required for discovery and self-description of a KNXnet/IP server and for setting up and
maintaining a communication channel between the client and the server.
KNXnet/IP tunneling describes the point-to-point exchange of KNX data over the IP network. Its main
purpose is to replace USB or EIA-232 connections between KNX network interfaces and PC workstations or
servers (e.g., for configuration and diagnostics of devices on the KNX network or visualization) by tunneling
L_Data frames. Acknowledgments, sequence counters, and a heartbeat mechanism are used to ensure the
robustness expected in comparison with such a traditional connection. KNXnet/IP routing is a point-to-multipoint
protocol for routing messages between KNX lines over a high-speed IP backbone. KNXnet/IP routers
send UDP/IP multicast messages to other KNXnet/IP routers on the same IP network, which in turn filter
the messages according to their destination address or group address and eventually pass them to the “native”
KNX segment. KNXnet/IP routers can replace traditional KNX LCs and BCs. KNXnet/IP device management
allows configuration and diagnosis of KNXnet/IP tunneling interfaces or routing devices via the IP
network. Within all these three service protocols, the actual KNX data is carried within cEMI messages.
While KNXnet/IP is designed for devices with one IP and one “traditional” KNX network interface,
the upcoming KNX IP is also intended for end devices that are solely connected to the IP medium.
A typical bandwidth of 10–100.Mbps for IP over Ethernet allows the integration of devices requiring
higher data rates (e.g., telecommunication and multimedia), which is a significant improvement compared
to the 9.6.kbps of TP1. Largely based on KNXnet/IP routing, KNX IP will also include mechanisms
to counteract possible problems arising from this throughput difference. Both configuration and
runtime interworking remain unchanged from other KNX media.
42.4 runtime Interworking
In KNX, runtime interworking refers to the definitions that enable devices to communicate for the purpose
of exchanging process control data. The communication endpoints of a KNX device application
relevant for this purpose (such as the illuminance level measured by a light sensor or the control input
of a load switch) are called group objects (GOs). The KNX AL provides services to propagate changes to
© 2011 by Taylor and Francis Group, LLC