· PDF fileoffered by Siemens 2. License one of the KNX Communication stacks offered by TAPKO...

KNX:

How to Develop a KNXDevice

Part1:

First Steps

KNX Association International Page No. 3January 13

KNX: The worldwide STANDARD for Home & Building Control

The KNX Profiles Conceptensures:• Runtime interworking with

other KNX devices• Configuration interworking with

the latest ETS version

Supported CommunicationMedia:

• Twisted Pair• IP• Radio Frequency• Powerline

Implementation Options:• Own solution Develop (practically) from scratch certified KNX system components

• Concentrate on Application Program and ETS integration only

• OEM sell already KNX certified device from other KNX member

Step 1: KNX Profile and Platform



Certified KNX systemcomponents:• Development + certification of

Application Program and ETSdatabase entry only

• Basis = Volume 2 (with examples)+ Volume 3 of KNX Standard

Own developed Solution:• Requires development + certification of Physical Layer KNX Communication Stack Application Program ETS database entry

• Basis = Volume 3 of KNX Standard

OEM:• No Development effort• Contact any KNX member

company wishing to sell hisproducts via OEM channel

• pure Administrative process only

Step 2: Develop Hardware & AP



Step 3: Use MT4

MT4 “Manufacturer Tool, Version 4” It can be installed as standalone tool Workflow:

• Create a MT4 project• Import Application Program binary• Create Group Objects• Create Parameters• Prepare the presentation of the AP• Import into ETS + test• Add translations



Step 4: Use EITT

EITT is a tool to test KNX devices:• During development (manufacturers)• During certification (test laboratories)

EITT will save time and money. How?• Develop the device.• Add it to an ETS project and configure it

(parameter settings, GAs, etc.).• Create PIXIT header and telegram

sequences in order to test the device.• Send the PIXIT export



L1 - Introduction• Membership

- Only KNX Members have the option to certify productsaccording KNX & EIB certification schemes.

• Signing of• the Trademark License Agreement (conditions for use of

respective logo)• the IPR License Agreement (conditions for free use of

KNX technology patents of fellow members in KNX certifiedproducts)

• Compliance to minimum ISO 9001:2000

When L1 = OK next stage will start

Step 5: Register your product (I)



L2 – Registration• KNX Association registers the new product

- Applicant (KNX member) gets a registration number- Entry ETS database

• Paperwork- General application form- product datasheet- (for any application) PIXIT - overview of implemented (non)-standardized data types

- (for non-certified system implementation) PICS• From now Conditional use of logo is allowed

F3 – Testing• Maximum allowed time: 6 months• Hardware tests: manufacturer’s responsibility• Software tests: at KNX accredited test lab of manufacturer’s choice

Step 5: Register your product (II)



L4 – Certification• If CE declaration + positive test reports (application &/or system)

available- KNX Member receives (e-)Certificate

• If product + software are left unchanged: certificate never expires

L5 – Surveillance• Retesting of products drawn from the market at KNX

accredited test labs• Checking of test reports underlying submitted CE-declaration

Step 6: KNX Certificate



Step 7: Promote your product

The KNX Product Certificate automatically:

• adds the product on the KNX website

• Allows publication of article on product in the KNXjournal

• Makes the product appear in the ETS4 ProductPlacement window

• Show it off at KNX Seminars, Fairs, Congresses…

Part2:

Solutions on the Market,Time & Cost



#1: Bus Access Units (BAU):Development

time cost/unit

#2: Bus Interface Module (BIM):Development

time cost/unit

#3: UART TransceiverDevelopment time cost/unit

#4: Bit interface (Transceiver/Discrete)Development time cost/unit

TP System Components



Developmenttime cost/unit

Serial Interface Module (SIM)

• Host Protocol based on ASCII or I2C

• Generic or specific ETS Database possible

Solution 1: Bus Access Units




WEINZIERLWEINZIERL

Bus Access and Object Server (BAOS)

• Interface on Group object level –Serial Host Protocol based on FT 1.2

• Generic or specific ETSDatabase possible

Solution 1: Bus Access Units



PCB with onboard: A Physical Layer implementation A µC with implemented KNX Communication Stack

• Developed by (distributed by Opternus)

• Only the development of an Application Program and itsintegration into ETS is required

• Also available as ‘chip set’ ASIC + Microcontroller


Solution 2: Bus Interface Module, BIM



Uart Transceivers offered by:

(distributed by Opternus)

Development time cost/unit

Solution 3: UART Transceiver




• Need to develop: KNX Communication Stack Application Program ETS database entry


• Options:1. Use microcontroller with embedded stack

offered by Siemens2. License one of the KNX Communication

stacks offered by TAPKO Weinzierl

3. Develop your own KNX CommunicationStack





• Speciality:

1. Bus Transceiver Module offered by

2. Bus Coupling Unit containing TP-UART only, forcoupling any flush mounted device to the KNX bus

3. Same development effort as above



• Types of KNX Bit interfaces• Bit Transceivers: offered by

(distributed by Opternus)

• Discrete: offered byin cooperation with Tapko (distributed by Opternus)


Solution 4: KNX Bit Interface

#4: Bit interface (Transceiver/Discrete)



#4: Bit interface (Transceiver/Discrete)


• Need to develop:

Physical Layer hardware (if not using above certified solutions)

KNX Communication Stack Same options as for case using UART

transceiver but higher timing requirements

Application Program

ETS database entry

Solution 4: KNX Bit Interface

Part3:

Other Solutions



KNX RF Development

• Configuration mostly via Easy Installation KNXstandardized Push Button Mode Procedure

• Physical Layer (868,3 MHz SRD band) profiles Single Channel KNX RF Multi-Channel KNX RF

• Need to develop: Physical Layer Implementation KNX Communication Stack Application Program

• Currently no inherent ETS supportof KNX RF devices



WEINZIERLWEINZIERL

KNX RF Development

• Options:

1. Use KNX RF Physical Layer and/or system stacksoffered by

2. Develop your own solution



KNX PL Development

• Physical Layer profiles PL110 FSK PL110+ OFDM Downwards compatible and interopable to PL110 FSK For higher data throughput (up to 32,4 kbit/s (D8PSK))

• Need to develop: Physical Layer Implementation KNX Communication Stack Application Program ETS database entry



KNX PL Development

• Configuration by ETS supported

• Options

1. Use KNX PL Physical Layer offered by

1. Use system stacks offered by• Kellendonk Elektronik• Weinzierl

3. Develop your own solution



KNX IP Development

• Configuration by ETS supported

• Physical Layer Use any Ethernet or WIFI controller KNX Communication Stack Application Program

• Options:1. License one of the KNX Communication Stacks offered

by TAPKO Weinzierl

2. Develop your own KNX Communication Stack

Part4:

Tools and Guidelines

· PDF fileoffered by Siemens 2. License one of the KNX Communication stacks offered by TAPKO...

Documents

Transcript of · PDF fileoffered by Siemens 2. License one of the KNX Communication stacks offered by TAPKO...