01 Joost Demarest - KNX Association

KNX RF Then, Now, Future Inn Style Maarssen 8 maart 2012
Joost Demarest System and Admin Director KNX Association Diegem/Brussels Belgium
www.knx.org
Contents
1. 2. 3. Original system requirements for KNX RF Relevant standards KNX RF Physical Layer
4.
5.
KNX RF telegram structure

KNX RF retransmitter functionality
6.
7.
KNX (RF) Easy Mode

KNX Bibat procedure
8.
9.
Recent KNX RF extensions

Future of KNX RF
KNX Radio Frequency Mr. Joost Demarest
KNX: The worldwide STANDARD for Home & Building Control
Page No. 2 March 12
Original system requirements for KNX RF

retrofit market mainly home & residential market Decentralised (no master) but centralised functions possible
usable as stand alone solution and together with other KNX media (media couplers)
Implementation on off-the-shelf components, small footprint
Re-transmitter use only for bigger installations

Bi- and unidirectional implementations possible
Low power consumption

for all application domains of home automation
lighting, shutters & blinds, security, HVAC, ..
KNX RF metering protocol as subsystem to KNX RF

Non-PC based programming ( Easy installation ), future tool support
Page No. 3 March 12
Relevant Standards
Layers 3-7 = EN 50090-series Layers 1-2, approved by CLC/TC 205 as EN 50090-5-3 common solution with/according to CEN/TC 294 EN 13757-3/-4 (Metering!) RF according to CEPT/ERC 70-03 (868 MHz - Band) Data Link Layer according to IEC 870-5-2 (FT3 - Protocol)
Page No. 4 March 12
KNX RF Physical Layer (1) acc. to CEPT/ERC 70-03
Application: Duty Cycle:
SRD
Alarms
SRD
< 1%
MAC, SRD SRD Alarms Alarms

<0.1% t.b.d. <10 % < 10% 100%
< 1%
< 0.1 %
[mW] 500
500mW
POWER [ ERP ]
25
10 5
25 mW
10mW
25 mW
25 mW 10mW
25 mW
5 mW
600 kHz 500 kHz 100kHz 100 250 kHz 300 kHz
868.0
868.6
870 [MHz]
FREQUENCY
Page No. 5 March 12
KNX RF Physical Layer (2)

Characteristic
Frequency band Center frequency Frequency tolerance Modulation FSK deviation Rx Bandwidth Rx sensitivity Tx minimum ERP
Value
868 .... 868.6 MHZ fc = 868.300 MHz +/-35 ppm FSK fDEV = 40 kHz to 80 kHz 300 kHz typical -95 dBm (BER 10-4) 0 dBm
Remark
1% duty cycle
+/-30.4 kHz
typically 50kHz -80 dBm minimum bit "0" is coded as fHI to fLO transition, chip sequence "10" bit "1" is coded as fLO to fHI transition, chip sequence "01 enables usage of clock crystal EN 300 220 1, 9.3.3 for class 2 receivers
Bit coding
Manchester
Bitrate Chiprate (transmit) Jitter per transition Tx Blocking performance Chip rate tolerance Tx Chip rate tolerance Rx
16.384 kBit/sec 32.768 kChips/sec +- 5 sec Class 2 +/- 1.5% +/- 2%
Page No. 6 March 12
KNX RF Physical Layer (3)

Characteristic
Duty cycle Preamble Manchester violation Sync word Postamble Hamming distance Protection Data link layer Typical air time per frame Retransmitters
Value
1% 30 Chips chip sequence "000111" chip seq "011010010110" 2 to 8 chips 6 CRC IEC 870-5-1/2 FT3 ~16ms up to 3
Remark
necessary for capture effect
16 bit
typical 4 byte datapoint cascading possible
Page No. 7 March 12
KNX RF general frame structure

IEC870-5-2 (FT3)
Preamble Block 1 CRC Block 2 CRC
...
CRC
Postamble
Preamble
Manch. Violation Sync Word
max. 15 x 01 chip
preamble for synchronisation
Block 1 CRC Further blocks Last block
10 bytes
fixed length, more info on next slide
2 bytes CRC after each data block 16 bytes 1 to 16 bytes details of block 2 on next slides
Postamble
2 to 8 chips
provides defined end of frame
Page No. 8 March 12
KNX RF Block 1
Length
C-field
ESC
Ctrl
SN
Length C-field Esc
1 byte 1 byte 1 byte
total number of user bytes counting from C-field fixed to value 44h escape code to separate KNX from metering (fixed to value FFh)
Ctrl
1 byte
uni or bidirectional sender signal strength battery state

Serial number/domain address of sender
SN
6 bytes
Page No. 9 March 12
KNX RF Block 2
Ctrl
Standard frame
Data
Ctrl Standard frame
1 byte variable
standard or extended? difference with frame on other media lies in - LFN: duplication avoidance - Domain address bit: indicates significance of SN field in Block 1 actual payload, remaining in next block
Data
variable
Page No. 10 March 12
Re-transmitter Technology
up to 3 Retransmitters are supported
No need for meshed networking

Link Layer Frame Number (LFN) + history list
solution to multipath communication
and avoiding message duplication:
T
M(LFN) M-1(LFN)
RT 2
M-2(LFN) M-1-2(LFN)
routing counter
Limitation of number of retransmissions
RT 1
M-1(LFN) M(LFN)
short interframe time + random delay: 0...10 ms

avoiding collisions of retransmitted messages
T
Dedicated retransmitters avoid complexity and overhead in normal end devices!
= Transmitter = Receiver = Retransmitter
R
RT
Concept of KNX Easy Installation
Device Functionality is made known to the partner device or configurator via E-Mode channels

Instead of via ETS product database entries Functionality of product is already contained in E-Mode device S-Mode device is in theory empty
E-Mode channels are a collection of data points and parameters Each Group Object has one or more different connection codes, depending on its functionality (e.g. switch, time, temperature, )
During configuration, group objects with the same connection code can be linked.
Push button: same approach but partner device decides whether linking is possible Easy installations are limited to one single line
Example Easy channel Heating actuator
KNX Easy Controller Mode

One single, central controller takes over role of ETS Procedure

Assignment of unique individual address to each found E-Mode device Read out of the E-Mode channels and parameters Show capabilities of devices on controllers display
Installer indicates which channels shall be linked

Controller decides on group addresses and parameters and downloads the devices
Channel CH_LIGHT_ACTUATOR_COMPLEX selected here According the links requested by the user, this is your address table, association table and parameters block:
I only have Channel CH_motion_detector_basic here
According the links requested by the user, this is your address table, association table and parameters block:
Group Addresses
Associations
Parameters
Parameters
Associations
Group Addresses
KNX Push button Mode

No central intelligence Procedure

Each device searches for itself a free Individual Address Installers first selects actuator channel (e.g. by pressing a button) Installer then selects sensor channel
Devices negotiate whether or not a link can be established

Linking must always be done two by two
I am 05FFh, 0908013FA14Dhh
Enter_Config_Mode Start_Link I am CH_light-actuator-complex COOL. I am ch_motion_detector_BASIC

I am 05FFh, 0100017A34AAh
I have an input CC_TIMED_STARTSTOP GrEAT! MY output cc_TIMED_STARTSTOP HAS Group address 8300h. USE that!
Extended group address table because of Unidirectional devices

Undirectional senders use fixed and unchangeable Group addresses Partner device (actuator) has to have extended group address table combination with serial number of sensor device makes group address unique Big drawback: if sensor needs to be replaced also reprogramming actuator!
Sensor 1
Device SN
Actuator
Device SN Partner SN Partner GA
SN=1
GA=1
T
SN=3
SN=1 SN=2
GA=1 GA=1
T R
Sensor 2
Device SN
SN=2
GA=1
T T R
= Channel
= Transmitter = Receiver
RF extension for bidirectional battery powered devices (BiBat)
Bidirectional battery-driven RF devices cant be in receive-mode all the time because of battery-lifetime The BiBat extension reduces the active receive windows of battery operated receivers to a minimum by means of a time slot procedure Application:
-
heating actuators for radiators

bidirectional room units
fire/smoke sensors remote controls with

feedback
Typical battery life times 1-3 years
Recent extensions KNX RF

RF ready
Single RF channel version upgrade of version 1 of KNX RF
RF multi
3 fast RF channels and 2 slow RF channels
Bibat
single RF channel version, unchanged compared to version 1 of
HBES RF
Bibat 2
2 RF channels
KNX RF Ready
Single channel, evolution with 4.8ms preamble for Tx Rx change to ignore some bits in CTRL field The rest of the stack remains the same Only a software upgrade of existing products All new developments shall be RF ready
500mW
25mW
Bibat KNX RF ready Duty Cycle 1%
868MHz
868.3
868.6
868.9
869.2
869.4
869.7
870MHz
KNX RF multi
3 RF fast channels for low latency devices 2 RF slow channels for battery powered devices F3 optional 25mW in F3 is now allowed by regulation Energy savings
Allow very low power consumption for receivers
Compatibility scheme
Tx Ok Existing Rx Ok Add KNX RF ready products
Downgrade via manuf specific action Add KNX RF multi products

KNX RF ready products Rx Ok
Existing
Tx Ok
Single channel
Add KNX RF multi products

Rx Ok Tx Ok
Multi channel
Add KNX RF multi products

Future of KNX RF (1)

KNX is No. 1 system for home and building control
Especially for the professional market with complex installations
Only system with several supported media

Only system with scalable configuration modes Usable in different application domains Supported by many manufacturers Accepted by many installers
Current Radio Frequency situation

Radio Frequency is a high volume and fast growing business Many manufacturers however develop and market proprietary solutions Many manufacturers wish to change to an open standard
There is no clear number one RF standard, many standards

still result in products with proprietary communication
Future of KNX RF (2)

Current KNX RF situation
Insufficient number of involved manufacturers Insufficient number of available devices Specification of Encryption and Authentication still work in progress Use of different configuration modes leads to impossibility to link products of different manufacturers No direct tool support - support of current KNX RF solution would lead to difference in look and feel of ETS for RF Coupling to TP via manufacturer media coupler specific solutions and ETS plug ins Not usable for complex installations
What is needed ?
Streamline addressing scheme between TP/PL and RF If accessed by ETS, devices shall allow the use of a domain address common to the installation instead of individual serial number Possibility to develop much simpler media couplers between TP and RF Finalize the KNX Security concept for encryption and authentication Support RF in ETS and add RF to KNX Basic course training
Thank you for your attention!

For more information Joost Demarest KNX Association cvba Tel: +32 2 775 86 44 E-Mail: joost.demarest@knx.org Web: www.knx.org
www.knx.org

01 Joost Demarest - KNX Association

Uploaded by

Document Information

Original Description:

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

01 Joost Demarest - KNX Association

Uploaded by

Copyright:

Available Formats

KNX RF Then, Now, Future Inn Style Maarssen 8 maart 2012

KNX RF telegram structure

KNX (RF) Easy Mode

Recent KNX RF extensions

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 2 March 12

Original system requirements for KNX RF

Re-transmitter use only for bigger installations

Low power consumption

KNX Radio Frequency Mr. Joost Demarest

KNX RF metering protocol as subsystem to KNX RF

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 4 March 12

KNX RF Physical Layer (1) acc. to CEPT/ERC 70-03

Application: Duty Cycle:

MAC, SRD SRD Alarms Alarms

KNX: The worldwide STANDARD for Home & Building Control

Page No. 5 March 12

KNX RF Physical Layer (2)

16.384 kBit/sec 32.768 kChips/sec +- 5 sec Class 2 +/- 1.5% +/- 2%

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 6 March 12

KNX RF Physical Layer (3)

necessary for capture effect

typical 4 byte datapoint cascading possible

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 7 March 12

KNX RF general frame structure

preamble for synchronisation

Block 1 CRC Further blocks Last block

fixed length, more info on next slide

provides defined end of frame

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 8 March 12

Length C-field Esc

1 byte 1 byte 1 byte

uni or bidirectional sender signal strength battery state

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 9 March 12

Ctrl Standard frame

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 10 March 12

No need for meshed networking

short interframe time + random delay: 0...10 ms

Dedicated retransmitters avoid complexity and overhead in normal end devices!

= Transmitter = Receiver = Retransmitter

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 11 March 12

Concept of KNX Easy Installation

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control

Page No. 12 March 12

Example Easy channel Heating actuator

KNX Radio Frequency Mr. Joost Demarest

KNX: The worldwide STANDARD for Home & Building Control