KONNEKTING Wiki - User contributions [en]

KONNEKTING Manufacturers

2026-01-31T07:48:17Z

Konnekting:

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|*removed*
|KNX User Forum
|*removed*
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|
|
|
|
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|282
|011A
|jsCon Hardware
|Connecting IoT devices to KNX
|jschaefer[a]jscon.de / jsCon Beratung, Im Erlen 21, D-45731 Waltrop, Germany
|28.07.2021
|-
|283
|011B
|Geord Ridder
|Arduino self made Products
|georg[a]ridder.email
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43962
|ABBA
|thewhobox
|KNX User Forum (proggerKA)
|info[a]kaenx.de
|02.08.2021
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|47806
|BABE
|Thomas Finke
|Thomas Finke
|finke.thomas[a]gmx.de
|18.09.2021
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|52701
|CDDD
|Christian González
|nerdocs' KNX components
|konnekting[a]nerdocs.at
|17.01.2023
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2026-01-31T07:47:33Z

Konnekting: removed email of dreamy

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|*removed*
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|
|
|
|
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|282
|011A
|jsCon Hardware
|Connecting IoT devices to KNX
|jschaefer[a]jscon.de / jsCon Beratung, Im Erlen 21, D-45731 Waltrop, Germany
|28.07.2021
|-
|283
|011B
|Geord Ridder
|Arduino self made Products
|georg[a]ridder.email
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43962
|ABBA
|thewhobox
|KNX User Forum (proggerKA)
|info[a]kaenx.de
|02.08.2021
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|47806
|BABE
|Thomas Finke
|Thomas Finke
|finke.thomas[a]gmx.de
|18.09.2021
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|52701
|CDDD
|Christian González
|nerdocs' KNX components
|konnekting[a]nerdocs.at
|17.01.2023
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2024-01-30T12:08:02Z

Konnekting: Christian González / nerdocs' KNX components

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|
|
|
|
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|282
|011A
|jsCon Hardware
|Connecting IoT devices to KNX
|jschaefer[a]jscon.de / jsCon Beratung, Im Erlen 21, D-45731 Waltrop, Germany
|28.07.2021
|-
|283
|011B
|Geord Ridder
|Arduino self made Products
|georg[a]ridder.email
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43962
|ABBA
|thewhobox
|KNX User Forum (proggerKA)
|info[a]kaenx.de
|02.08.2021
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|47806
|BABE
|Thomas Finke
|Thomas Finke
|finke.thomas[a]gmx.de
|18.09.2021
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|52701
|CDDD
|Christian González
|nerdocs' KNX components
|konnekting[a]nerdocs.at
|17.01.2023
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING XML Device Description

2022-03-29T13:49:17Z

Konnekting:

== KONNEKTING XML Device Description (.kdevice.xml) ==

After writing your arduino KONNEKTING Device sketch, you should have a list of communication objects and parameters your device will use or provide. To be able to program the device via the KNX bus, you have to provide a XML file which describes your device. This XML file can then be used by the [[ KONNEKTING_Suite | KONNEKTING Suite]], which provides a comfortable way of device programming.

Either you use a standard text editor (on windows we can recommend [https://notepad-plus-plus.org/ Notepad++]), or you use an XML editor of your choice. In case of an XML Editor that can handle XML Schema Definition files (.xsd), you can use this one:

https://github.com/KONNEKTING/KonnektingXmlSchema/blob/master/src/main/xsd/KonnektingDeviceV0.xsd

=== Preparation ===

If you haven't registered a manufacturer-id yet, NOW would be the best time for it. [[ KONNEKTING_Manufacturers | REGISTER FOR FREE]]

=== XML Format explained (1.0.0-RC1 Format!) ===

<syntaxhighlight lang=XML line>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<KonnektingDevice xmlns="http://konnekting.de/xml/KonnektingDevice/v0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://konnekting.de/xml/KonnektingDevice/v0 http://konnekting.de/xml/KonnektingDevice/KonnektingDeviceV0.xsd">


<Device ManufacturerId="12345" DeviceId="123" Revision="123" SystemType="1">

<ManufacturerName>You Manufacturer Name</ManufacturerName>
<DeviceName>Your Device Name</DeviceName>


<Parameters>


<ParameterGroup Name="A Parameter Group" Id="0">


<Parameter Id="0" IdName="aParameter">


<Description>A Parameter</Description>


<Value Type="uint8" Default="01" Options="" Min="00" Max="0A"/>

</Parameter>

<Parameter Id="1" IdName="anotherParameter">
<Description>Another Parameter</Description>
<Value Type="int16" Default="0001" Options=""/>
</Parameter>

<Parameter Id="2" IdName="yetAnotherParameter">
<Description>Yet Another Parameter</Description>
<Value Type="uint8" Default="00" Options="00=10ms|01=30ms|02=60ms|04=120ms|FF=no delay"/>
</Parameter>

<Parameter Id="3" IdName="activate1">
<Description>Activate 'Another Parameter'</Description>
<Value Type="uint8" Default="01" Options="00=disabled|01=enabled"/>
</Parameter>

<Parameter Id="4" IdName="activate2">
<Description>Activate 'Another Parameter Group'</Description>
<Value Type="uint8" Default="01" Options="00=disabled|01=enabled"/>
</Parameter>

<Parameter Id="5" IdName="activate3">
<Description>Activate 'My Second Com Object'</Description>
<Value Type="uint8" Default="01" Options="00=disabled|01=enabled"/>
</Parameter>
</ParameterGroup>

<ParameterGroup Id="1" Name="Another Parameter Group">
<Parameter Id="6">
<Description>Another parameter in another parametergroup</Description>
<Value Type="uint8" Default="02" Options="00=Aus|01=An|02=letzter Wert|04=Helligkeitswert"/>
</Parameter>
</ParameterGroup>

</Parameters>

<CommObjects>

<CommObject Id="0">

<Name>My First Com Object</Name>

<Function>Test-Function #1</Function>

<DataPointType>1.001</DataPointType>


<Flags>52</Flags>
</CommObject>

<CommObject Id="1">
<Name>My Second Com Object</Name>
<Function>Test-Function #2</Function>
<DataPointType>1.001</DataPointType>
<Flags>42</Flags>
</CommObject>
</CommObjects>


<Dependencies>
<ParameterDependency ParamId="1" Test="eq" TestParamId="3" TestValue="01" TestList=""/>
<ParameterDependency ParamId="2" Test="in" TestParamId="3" TestValue="01" TestList="02|03"/>
<ParameterGroupDependency ParamGroupId="1" Test="eq" TestParamId="4" TestValue="01" TestList=""/>
<CommObjectDependency CommObjId="1" Test="eq" TestParamId="5" TestValue="01" TestList=""/>
</Dependencies>
</Device>
</KonnektingDevice>
</syntaxhighlight>

KONNEKTING XML Device Description

2022-03-29T13:47:59Z

Konnekting:

== KONNEKTING XML Device Description (.kdevice.xml) ==

After writing your arduino KONNEKTING Device sketch, you should have a list of communication objects and parameters your device will use or provide. To be able to program the device via the KNX bus, you have to provide a XML file which describes your device. This XML file can then be used by the [[ KONNEKTING_Suite | KONNEKTING Suite]], which provides a comfortable way of device programming.

Either you use a standard text editor (on windows we can recommend [https://notepad-plus-plus.org/ Notepad++]), or you use an XML editor of your choice. In case of an XML Editor that can handle XML Schema Definition files (.xsd), you can use this one:

https://github.com/KONNEKTING/KonnektingXmlSchema/blob/master/src/main/xsd/KonnektingDeviceV0.xsd

=== Preparation ===

If you haven't registered a manufacturer-id yet, NOW would be the best time for it. [[ KONNEKTING_Manufacturers | REGISTER FOR FREE]]

=== XML Format explained (1.0.0-RC1 Format!) ===

<syntaxhighlight lang=XML line>
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<KonnektingDevice xmlns="http://konnekting.de/xml/KonnektingDevice/v0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://konnekting.de/xml/KonnektingDevice/v0 http://konnekting.de/xml/KonnektingDevice/KonnektingDeviceV0.xsd">


<Device ManufacturerId="12345" DeviceId="123" Revision="123">

<ManufacturerName>You Manufacturer Name</ManufacturerName>
<DeviceName>Your Device Name</DeviceName>


<Parameters>


<ParameterGroup Name="A Parameter Group" Id="0">


<Parameter Id="0" IdName="aParameter">


<Description>A Parameter</Description>


<Value Type="uint8" Default="01" Options="" Min="00" Max="0A"/>

</Parameter>

<Parameter Id="1" IdName="anotherParameter">
<Description>Another Parameter</Description>
<Value Type="int16" Default="0001" Options=""/>
</Parameter>

<Parameter Id="2" IdName="yetAnotherParameter">
<Description>Yet Another Parameter</Description>
<Value Type="uint8" Default="00" Options="00=10ms|01=30ms|02=60ms|04=120ms|FF=no delay"/>
</Parameter>

<Parameter Id="3" IdName="activate1">
<Description>Activate 'Another Parameter'</Description>
<Value Type="uint8" Default="01" Options="00=disabled|01=enabled"/>
</Parameter>

<Parameter Id="4" IdName="activate2">
<Description>Activate 'Another Parameter Group'</Description>
<Value Type="uint8" Default="01" Options="00=disabled|01=enabled"/>
</Parameter>

<Parameter Id="5" IdName="activate3">
<Description>Activate 'My Second Com Object'</Description>
<Value Type="uint8" Default="01" Options="00=disabled|01=enabled"/>
</Parameter>
</ParameterGroup>

<ParameterGroup Id="1" Name="Another Parameter Group">
<Parameter Id="6">
<Description>Another parameter in another parametergroup</Description>
<Value Type="uint8" Default="02" Options="00=Aus|01=An|02=letzter Wert|04=Helligkeitswert"/>
</Parameter>
</ParameterGroup>

</Parameters>

<CommObjects>

<CommObject Id="0">

<Name>My First Com Object</Name>

<Function>Test-Function #1</Function>

<DataPointType>1.001</DataPointType>


<Flags>52</Flags>
</CommObject>

<CommObject Id="1">
<Name>My Second Com Object</Name>
<Function>Test-Function #2</Function>
<DataPointType>1.001</DataPointType>
<Flags>42</Flags>
</CommObject>
</CommObjects>


<Dependencies>
<ParameterDependency ParamId="1" Test="eq" TestParamId="3" TestValue="01" TestList=""/>
<ParameterDependency ParamId="2" Test="in" TestParamId="3" TestValue="01" TestList="02|03"/>
<ParameterGroupDependency ParamGroupId="1" Test="eq" TestParamId="4" TestValue="01" TestList=""/>
<CommObjectDependency CommObjId="1" Test="eq" TestParamId="5" TestValue="01" TestList=""/>
</Dependencies>
</Device>
</KonnektingDevice>
</syntaxhighlight>

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2022-03-29T13:43:31Z

Konnekting:

== New and Noteworthy ==

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f). Requires in any case new TestList-attribute in dependency section. The list-separator is "|".
** '''TODO''' Add example or adapt existing XML example: https://wiki.konnekting.de/index.php/KONNEKTING_XML_Device_Description
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5/1.0.0-RC1 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* Sketch:
** Function '''getFreeEepromOffset''' was renamed to '''getMemoryUserSpaceStart''' to reflect the new memory layout.

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** Add attribute <code>TestList=""</code> to any <code><*Dependency></code> element in your .kdevice.xml
* ... '''TODO''' ...

Documentation

2022-03-11T11:40:30Z

Konnekting:

== Software ==

* [[KONNEKTING Suite]]
* [[KONNEKTING Device Library]]
** [[KONNEKTING_Device_Library_1.0.0-RC1_Release_Notes | Version 1.0.0-RC1]]

== Specifications ==

* [[KONNEKTING Development Rules]]
* [[KONNEKTING Device Specification]]
* [[KONNEKTING XML Device Description]]
* [[KONNEKTING Modular DIN RAIL Device Specification]]
* [[KONNEKTING Protocol Specification]]

== Technical Documentation ==

* [[Recommended Arduino Boards]]
* [[Programming Workflow]]
* [[FOTB - Firmware Over The Bus]]
* [[SAMD Flash Overview]]
* [[Arduino BETA5 Startup Log explained]]

== HowTos ==

* [[Solder contact pins for KNX terminal]]
* [[Quick_Start_Guide#Debug | Activate Debug Prints]]

== Research ==

* [[Tiny-BCU]]

1.0.0-RC1 Release Notes

2022-03-11T11:40:05Z

Konnekting: Konnekting moved page 1.0.0-RC1 Release Notes to KONNEKTING Device Library 1.0.0-RC1 Release Notes

#REDIRECT [[KONNEKTING Device Library 1.0.0-RC1 Release Notes]]

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2022-03-11T11:40:05Z

Konnekting: Konnekting moved page 1.0.0-RC1 Release Notes to KONNEKTING Device Library 1.0.0-RC1 Release Notes

== New and Noteworthy ==

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
** '''TODO''' Add example or adapt existing XML example: https://wiki.konnekting.de/index.php/KONNEKTING_XML_Device_Description
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5/1.0.0-RC1 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* Sketch:
** Function '''getFreeEepromOffset''' was renamed to '''getMemoryUserSpaceStart''' to reflect the new memory layout.

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... '''TODO''' ...
* ... '''TODO''' ...

Documentation

2022-03-11T11:39:29Z

Konnekting:

== Software ==

* [[KONNEKTING Suite]]
* [[KONNEKTING Device Library]]
** [[1.0.0-RC1_Release_Notes | Version 1.0.0-RC1]]

== Specifications ==

* [[KONNEKTING Development Rules]]
* [[KONNEKTING Device Specification]]
* [[KONNEKTING XML Device Description]]
* [[KONNEKTING Modular DIN RAIL Device Specification]]
* [[KONNEKTING Protocol Specification]]

== Technical Documentation ==

* [[Recommended Arduino Boards]]
* [[Programming Workflow]]
* [[FOTB - Firmware Over The Bus]]
* [[SAMD Flash Overview]]
* [[Arduino BETA5 Startup Log explained]]

== HowTos ==

* [[Solder contact pins for KNX terminal]]
* [[Quick_Start_Guide#Debug | Activate Debug Prints]]

== Research ==

* [[Tiny-BCU]]

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2022-03-11T11:14:39Z

Konnekting:

== New and Noteworthy ==

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
** '''TODO''' Add example or adapt existing XML example: https://wiki.konnekting.de/index.php/KONNEKTING_XML_Device_Description
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5/1.0.0-RC1 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* Sketch:
** Function '''getFreeEepromOffset''' was renamed to '''getMemoryUserSpaceStart''' to reflect the new memory layout.

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... '''TODO''' ...
* ... '''TODO''' ...

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2022-03-11T11:05:56Z

Konnekting:

== New and Noteworthy ==

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
** '''TODO''' Add example or adapt existing XML example: https://wiki.konnekting.de/index.php/KONNEKTING_XML_Device_Description
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5/1.0.0-RC1 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* Sketch:
** '''getFreeEepromOffset''' was renamed to '''getMemoryUserSpaceStart'''

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... todo ...
* ...todo...

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2022-03-11T11:05:35Z

Konnekting:

== New and Noteworthy ==

New things and features in beta5 are:

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
** '''TODO''' Add example or adapt existing XML example: https://wiki.konnekting.de/index.php/KONNEKTING_XML_Device_Description
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5/1.0.0-RC1 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* Sketch:
** '''getFreeEepromOffset''' was renamed to '''getMemoryUserSpaceStart'''

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... todo ...
* ...todo...

1.0.0-beta5 Changelog and porting guide

2022-03-11T11:05:17Z

Konnekting: Konnekting moved page 1.0.0-beta5 Changelog and porting guide to 1.0.0-RC1 Release Notes

#REDIRECT [[1.0.0-RC1 Release Notes]]

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2022-03-11T11:05:17Z

Konnekting: Konnekting moved page 1.0.0-beta5 Changelog and porting guide to 1.0.0-RC1 Release Notes

== New and Noteworthy ==

New things and features in beta5 are:

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
** '''TODO''' Add example or adapt existing XML example: https://wiki.konnekting.de/index.php/KONNEKTING_XML_Device_Description
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* Sketch:
** '''getFreeEepromOffset''' was renamed to '''getMemoryUserSpaceStart'''

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... todo ...
* ...todo...

DFF4.1

2022-02-20T11:55:09Z

Konnekting: /* Help */ added details on how to find error with non-switching relais.

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|DFF4.1
|-
! colspan="2"|[[File:DFF4.1 1.0.png|300px|thumb|center]]
|-
! Developer
| Alexander Christian
|-
! Status
| Version 1.0 finished
|-
! Microcontroller/Board
| [[M0dularisM+]]
|-
! KNX connectivity
| Siemens BCU, Eugen's µBCU
|}

== Description ==

The purpose of this actuator is, to control Roto Rototronic skylight with shutters and/or sun blinds.
It has 4 "channels". Each channel internally uses two relays: One for the open-action, and one for the close-action.

Of course you can also control your Roto Rototronic skylight with help of a standard switch-actuator. But then you don't have the possibility to "open the window 75%" or "close the shutter 80%". The firmware for DFF4.1 provides all this neat feature that you know from typical shutter/blinds actuators.

== Hardware ==

This actuator consists of the following REG parts:

* [[ M0dularis+ | M0dularis+ ]]
* [[ Frontend 8 Buttons 8 LEDs | 8x Button + 8x LED ]]
* [[ 8 Relay Bistable | 8x Relay Bistable, bus powered ]] (8 relays in total, 2 for each channel = 4 channels).

I2C address on application board:

A0: 1
A1: 0
A2: 0

I2C address on frontend board:

A0: 0
A1: 0
A2: 0

== Software ==

== User Documentation ==

Check here for the [[DFF4.1 User Manual]]

== Developer Documentation ==

Firmware sourcecode is on github: https://github.com/KONNEKTING/DFF4.1
Follow this guide for updating the firmare from source-code: [[KONNEKTING USB Firmware Update]]

== Get a DIY kit ==

You are interested in this actuator? Great! This device is available as a DIY kit.

The kit includes all required parts with pre-soldered SMD parts and pre-flashed controller board.

You only need:
* soldering iron and solder
* a screw driver
* a sharp knife with a fine tip
* a working KNX installation where you can connect the device to
* ~2-3hrs to build it according to the build instructions linked on this page
* a computer: Windows, Linux or MAC that is able to run [[KONNEKTING Suite]] plus a KNX IP Interface or an KNX IP Router.
* for updating the firmware: A Mini USB cable (Not Micro-USB like on your smartphone. Mini USB is a big thicker as Micro USB)

Please write a mail to info@konnekting.de and refer to this page.

== Build It ==

This actuator uses three PCBs, a bunch of SMD components as well as a lot of mechanical parts. As most users are not able to solder SMD, the PCBs are pre-soldered with all SMD components. Due to the big amount of parts, this actuator comes as a DIY kit: You have to solder non-SMD parts yourself and build up the device and finally flash the firmware with help of a USB connection.

Check here for the [[DFF4.1 Building Instructions]]

== Help ==

If relays do not work as expected, you can run this test-sketch to be able to switch relais by serial console. Commands follow this syntax (\n = LF/LineFeed/NewLine):

[a-h0-1]\n

f.i. "a0" disables relay A, "f1" enables relay F
On startup all relays are disabled.
It is recommended to use this test without attached window/shutter, but with am multimeter/continuity-tester to be able to test relay by relay.

<syntaxhighlight lang="C" line='line'>
#include <Wire.h>
#include <Adafruit_MCP23017.h>

Adafruit_MCP23017 mcp;
#define LED A5
#define EN A0

// MCP23017 Output register<->pin map
#define GPA0 0 // E 1
#define GPA1 1 // E 0
#define GPA2 2
#define GPA3 3
#define GPA4 4
#define GPA5 5
#define GPA6 6
#define GPA7 7
#define GPB0 8
#define GPB1 9
#define GPB2 10 // B 0
#define GPB3 11 // B 1
#define GPB4 12 // C 0
#define GPB5 13 // C 1
#define GPB6 14 // D 0
#define GPB7 15 // D 1

#define A_SET GPB1
#define A_RESET GPB0

#define B_SET GPB3
#define B_RESET GPB2

#define C_SET GPB5
#define C_RESET GPB4

#define D_SET GPB7
#define D_RESET GPB6

#define E_SET GPA0
#define E_RESET GPA1

#define F_SET GPA2
#define F_RESET GPA3

#define G_SET GPA4
#define G_RESET GPA5

#define H_SET GPA6
#define H_RESET GPA7

boolean state[16];

void setup() {

SerialUSB.begin(115200);
while (!SerialUSB) {
delay(100);
}

SerialUSB.println("SetupMCP Relais Test ...");

pinMode(LED, OUTPUT);
pinMode(EN, OUTPUT);
digitalWrite(LED, HIGH);
digitalWrite(EN, HIGH);

mcp.begin(1);

for (int i = 0; i < 16; i++) {
mcp.pinMode(i, OUTPUT);
state[i]=false;
setMCP(i, false);
}

//#define D 100

SerialUSB.println("... done");
digitalWrite(LED, LOW);

// initial delay
delay(1000);
SerialUSB.println("Initial delay done.");
SerialUSB.println("Waiting for command...[a-h0-1]");
}

//84
#define WAIT_TIME 84

//16
#define SET_TIME 16

String cmd;

char c[4];

void loop() {

cmd = SerialUSB.readStringUntil('\n');

if (cmd.length() == 2) {

SerialUSB.print("Command: ");
SerialUSB.println(cmd);

if (cmd == "a1") {
pulseMCP(A_SET);
} else if (cmd == "a0") {
pulseMCP(A_RESET);
}

else if (cmd == "b1") {
pulseMCP(B_SET);
} else if (cmd == "b0") {
pulseMCP(B_RESET);
}

else if (cmd == "c1") {
pulseMCP(C_SET);
} else if (cmd == "c0") {
pulseMCP(C_RESET);
}

else if (cmd == "d1") {
pulseMCP(D_SET);
} else if (cmd == "d0") {
pulseMCP(D_RESET);
}

else if (cmd == "e1") {
pulseMCP(E_SET);
} else if (cmd == "e0") {
pulseMCP(E_RESET);
}

else if (cmd == "f1") {
pulseMCP(F_SET);
} else if (cmd == "f0") {
pulseMCP(F_RESET);
}

else if (cmd == "g1") {
pulseMCP(G_SET);
} else if (cmd == "g0") {
pulseMCP(G_RESET);
}

else if (cmd == "h1") {
pulseMCP(H_SET);
} else if (cmd == "h0") {
pulseMCP(H_RESET);
}

SerialUSB.println("\n\nWaiting for command...[a-h0-1]");

} else if (cmd.length() == 4) {
SerialUSB.print("Command: ");
SerialUSB.println(cmd);

if (cmd == "gpa0") {
state[GPA0] = !state[GPA0];
setMCP(GPA0, state[GPA0gpb5]);
} else
if (cmd == "gpa1") {
state[GPA1] = !state[GPA1];
setMCP(GPA1, state[GPA1]);
} else
if (cmd == "gpa2") {
state[GPA2] = !state[GPA2];
setMCP(GPA2, state[GPA2]);
} else
if (cmd == "gpa3") {
state[GPA3] = !state[GPA3];
setMCP(GPA3, state[GPA3]);
} else
if (cmd == "gpa4") {
state[GPA4] = !state[GPA4];
setMCP(GPA4, state[GPA4]);
} else
if (cmd == "gpa5") {
state[GPA5] = !state[GPA5];
setMCP(GPA5, state[GPA5]);
} else
if (cmd == "gpa6") {
state[GPA6] = !state[GPA6];
setMCP(GPA6, state[GPA6]);
} else
if (cmd == "gpa7") {
state[GPA7] = !state[GPA7];
setMCP(GPA7, state[GPA7]);
} else
if (cmd == "gpb0") {
state[GPB0] = !state[GPB0];
setMCP(GPB0, state[GPB0]);
} else
if (cmd == "gpb1") {
state[GPB1] = !state[GPB1];
setMCP(GPB1, state[GPB1]);
} else
if (cmd == "gpb2") {
state[GPB2] = !state[GPB2];
setMCP(GPB2, state[GPB2]);
} else
if (cmd == "gpb3") {
state[GPB3] = !state[GPB3];
setMCP(GPB3, state[GPB3]);
} else
if (cmd == "gpb4") {
state[GPB4] = !state[GPB4];
setMCP(GPB4, state[GPB4]);
} else
if (cmd == "gpb5") {
state[GPB5] = !state[GPB5];
setMCP(GPB5, state[GPB5]);
} else
if (cmd == "gpb6") {
state[GPB6] = !state[GPB6];
setMCP(GPB6, state[GPB6]);
} else
if (cmd == "gpb7") {
state[GPB7] = !state[GPB7];
setMCP(GPB7, state[GPB7]);
}

}
}

void setMCP(int i, boolean s){
SerialUSB.print("Set addr #");
SerialUSB.print(i);
SerialUSB.print(" to ");
SerialUSB.println(s);
mcp.digitalWrite(i, s);
}

void pulseMCP(int i) {
SerialUSB.print("Pulse at addr #");
SerialUSB.print(i);

mcp.digitalWrite(i, HIGH);
delay(SET_TIME);
mcp.digitalWrite(i, LOW);
delay(WAIT_TIME);
SerialUSB.println(" *DONE*");
}
</syntaxhighlight>

If there are relais that do not switch, follow these steps:

# Set MCP IO pin one by one and check if voltage (0V vs. 3.3V) can be measured between MCP IC and ULN2803 IC.
# Measure also the voltage on ULN2803 output pin.

If MCP fires 0V (low), ULN should almost show 5V (typically 4.8V) on output. If MCP fires 3.3V (high) the ULN output voltage will go down to almost 0V (low), but typically 0.7V. If itÄs 0.9V, it will work as well. But if voltage just drops to 1..1.5V, the ULN driver IC is bad and needs to be replaced. Make sure you use a genuine one and not a china-copy.

== Links ==

[[Category:Device/Kits]]

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2021-10-27T09:27:17Z

Konnekting:

== New and Noteworthy ==

New things and features in beta5 are:

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
** '''TODO''' Add example or adapt existing XML example: https://wiki.konnekting.de/index.php/KONNEKTING_XML_Device_Description
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... todo ...
* ...todo...

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2021-10-27T09:26:02Z

Konnekting:

== New and Noteworthy ==

New things and features in beta5 are:

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* .kconfig.xml files have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... todo ...
* ...todo...

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2021-10-27T09:18:20Z

Konnekting:

== New and Noteworthy ==

New things and features in beta5 are:

* completely new programming protocol: Suite no longer writes group-adresses, com-objects etc. one by one, but prepares a complete memory image upfront and writes to arduino memory directly (see: https://wiki.konnekting.de/index.php/KONNEKTING_Protocol_Specification_0x01). With that in place, we can also extremely speed up the partial-programming (only write changes since last programming) and gain more flexibility for future changes.
* added IN/NOTIN/BETWEEN/NOTBETWEEN to parameter, parametergroup and comobject as test type (https://gitlab.com/konnekting/KonnektingXmlSchema/-/commit/692cf83bcbd3729e8eaed351da661fe8292d609f)
* KonnektingSuite now can read your .knxproj exported project file from ETS. Just place it into you project folder and restart your Suite. Once you want to assign a group-address to a com-object, you can search/autocomplete your input with help of the knxproject file you provided.
* You can now assign more than one group-address to one com-object

== Porting beta4 to beta5 ==

Things you need to adapt or consider to port your sketch and .kdevice.xml to beta5:

* .kconfig.xml file have a new format. So you need to start the configuration of your devices from scratch. There's no conversion tool yet available.
* .kdevice.xml also has a new format. To make it work again, you need to:
** Add <code>SystemType</code> parameter to <code><Device></code> tag, typically <code>SystemType="1"</code>, e.g. <code><Device ManufacturerId="57005" DeviceId="255" Revision="0" SystemType="1"></code>. [[
** ... todo ...
* ...todo...

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2021-10-27T07:57:50Z

Konnekting:

== New and Noteworthy ==

New things and features in beta5 are:

* ...todo...
* ...todo...

== Porting beta4 to beta5 ==

Things you need to adapt to port your sketch and .kdevice.xml to beta5:

* ...todo...
* ...todo...

KONNEKTING Device Library 1.0.0-RC1 Release Notes

2021-10-27T07:57:35Z

Konnekting: Created page with "== New and Noteworthy New things and features in beta5 are: * ...todo... * ...todo... == Porting beta4 to beta5 Things you need to adapt to port your sketch and .kdevice.x..."

== New and Noteworthy

New things and features in beta5 are:

* ...todo...
* ...todo...

== Porting beta4 to beta5

Things you need to adapt to port your sketch and .kdevice.xml to beta5:

* ...todo...
* ...todo...

Documentation

2021-10-27T07:54:09Z

Konnekting: /* Software */

== Software ==

* [[KONNEKTING Suite]]
* [[KONNEKTING Device Library]]
* [[1.0.0-beta5 Changelog and porting guide]]

== Specifications ==

* [[KONNEKTING Development Rules]]
* [[KONNEKTING Device Specification]]
* [[KONNEKTING XML Device Description]]
* [[KONNEKTING Modular DIN RAIL Device Specification]]
* [[KONNEKTING Protocol Specification]]

== Technical Documentation ==

* [[Recommended Arduino Boards]]
* [[Programming Workflow]]
* [[FOTB - Firmware Over The Bus]]
* [[SAMD Flash Overview]]
* [[Arduino BETA5 Startup Log explained]]

== HowTos ==

* [[Solder contact pins for KNX terminal]]
* [[Quick_Start_Guide#Debug | Activate Debug Prints]]

== Research ==

* [[Tiny-BCU]]

Documentation

2021-10-27T07:53:26Z

Konnekting: /* HowTos */

== Software ==

* [[KONNEKTING Suite]]
* [[KONNEKTING Device Library]]

== Specifications ==

* [[KONNEKTING Development Rules]]
* [[KONNEKTING Device Specification]]
* [[KONNEKTING XML Device Description]]
* [[KONNEKTING Modular DIN RAIL Device Specification]]
* [[KONNEKTING Protocol Specification]]

== Technical Documentation ==

* [[Recommended Arduino Boards]]
* [[Programming Workflow]]
* [[FOTB - Firmware Over The Bus]]
* [[SAMD Flash Overview]]
* [[Arduino BETA5 Startup Log explained]]

== HowTos ==

* [[Solder contact pins for KNX terminal]]
* [[Quick_Start_Guide#Debug | Activate Debug Prints]]

== Research ==

* [[Tiny-BCU]]

Documentation

2021-10-27T07:53:00Z

Konnekting: /* HowTos */

KONNEKTING Manufacturers

2021-09-18T08:55:04Z

Konnekting: added thomas finke

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|
|
|
|
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|282
|011A
|jsCon Hardware
|Connecting IoT devices to KNX
|jschaefer[a]jscon.de / jsCon Beratung, Im Erlen 21, D-45731 Waltrop, Germany
|28.07.2021
|-
|283
|011B
|Geord Ridder
|Arduino self made Products
|georg[a]ridder.email
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43962
|ABBA
|thewhobox
|KNX User Forum (proggerKA)
|info[a]kaenx.de
|02.08.2021
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|47806
|BABE
|Thomas Finke
|Thomas Finke
|finke.thomas[a]gmx.de
|18.09.2021
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-08-02T11:25:05Z

Konnekting:

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|
|
|
|
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|282
|011A
|jsCon Hardware
|Connecting IoT devices to KNX
|jschaefer[a]jscon.de / jsCon Beratung, Im Erlen 21, D-45731 Waltrop, Germany
|28.07.2021
|-
|283
|011B
|Geord Ridder
|Arduino self made Products
|georg[a]ridder.email
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43962
|ABBA
|thewhobox
|KNX User Forum (proggerKA)
|info[a]kaenx.de
|02.08.2021
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-07-28T07:57:17Z

Konnekting:

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|
|
|
|
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|282
|011A
|jsCon Hardware
|Connecting IoT devices to KNX
|jschaefer[a]jscon.de / jsCon Beratung, Im Erlen 21, D-45731 Waltrop, Germany
|28.07.2021
|-
|283
|011B
|Geord Ridder
|Arduino self made Products
|georg[a]ridder.email
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-07-28T07:54:28Z

Konnekting: added Georg ridder

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|282
|011A
|jsCon Hardware
|Connecting IoT devices to KNX
|jschaefer[a]jscon.de / jsCon Beratung, Im Erlen 21, D-45731 Waltrop, Germany
|28.07.2021
|-
|283
|011B
|Geord Ridder
|Arduino self made Products
|georg[a]ridder.email
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-07-28T07:48:12Z

Konnekting: added jsCon

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|282
|011A
|jsCon Hardware
|Connecting IoT devices to KNX
|jschaefer@jscon.de / jsCon Beratung, Im Erlen 21, D-45731 Waltrop, Germany
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-07-28T07:45:34Z

Konnekting: fixed numbers

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|277
|0115
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|278
|0116
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0117
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0118
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0119
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-07-28T07:40:41Z

Konnekting: added BergenSoft

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|278
|0115
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0116
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0117
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0118
|TheNavy
|KNX User Forum
|richard[a]die-haasen.camp
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48830
|BEBE
|BergenSoft
|Samuel Bergen
|bergensoft[a]gmail.com
|28.07.2021
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-07-28T07:33:40Z

Konnekting: added TheNavy

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|278
|0115
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0116
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0117
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|281
|0118
|TheNavy
|KNX User Forum
|richard@die-haasen.camp
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-07-28T07:29:08Z

Konnekting: added Cluster Industrie

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|278
|0115
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0116
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|280
|0117
|Cluster Industrie
|KNX User Forum
|cluster2[a]gmx.de
|28.07.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-05-06T06:41:35Z

Konnekting: added onemotion

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|278
|0115
|F. Zösch
|ZOESCH.ART
|info[a]zoesch.art
|22.04.2021
|-
|279
|0116
|R. Stutz
|onemotion
|info[a]onemotion.ch
|06.05.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Manufacturers

2021-04-22T06:20:25Z

Konnekting: Added zoesch.art

= KONNEKTING Manufacturer ID List =

If you want to create an KONNEKTING device, you have to have a manufacturer ID. The ID is a 16-bit value and is used to prevent conflicts when programming devices.
You can register your ID for free. Please drop us a email with your
* Manufacturer Name
* a short description of you and/or your company, at least your full name
* and a contact information, like a valid email or mail address

Examples:

* Manufacturer Name: Max Mustermann
* Description: Mustermann Ltd.
* Contact: max@mustermannltd.de

* Manufacturer Name: Max Mustermann
* Description: KNX User Forum / MaxMustermann0815
* Contact: max@mustermannltd.de

--> [mailto:register@konnekting.de?Subject=KONNEKTING:%20Register%20Manufacturer-ID&body=Dear%20KONNEKTING%20Team,%0A%0APlease%20register%20a%20manufacturer%20ID:%0A%0AManufacturer%20Name:%20Your%20manufacturer%20name%0ADescription:%20a%20short%20description%0AContact:%20contact%20information,%20like%20email%20or%20mail%20address register@konnekting.de]

The Device ID and Revision, which is also required for a working KONNEKTING Device is completely up to you. You have to ensure by yourself that you do not create duplicates and conflicts.

= FAQ =

# Why do I have to register? 
We don't force you to register. As long as you build devices just for you, you can do whatever you want. But we would like to see you share your device with the world. So others would use your Sketch/Firmware as well, which may then conflict with an existing ID...

# How many devices can be created with one manufacturer id? 
You can create up to 256 devices which can have 256 revisions. So in sum 65536 devices are possible with just one manufacturer ID. Choosing device ID and revision is up to you.

# Can I have ID 12345 (insert any ID here)? 
In principle yes, but we try to fill the gaps from the beginning of the list.

= Manufacturer-List =

''The following list shows the known/registered manufacturers (not devices!)''

{| class="wikitable"
!ID dec
!ID hex
!Name
!Description
!Contact*
!Date
|-
|0..255
|0000..00FF
|KONNEKTING Team
|system reserved
|info@konnekting.de
|01.01.2016
|-
|256
|0100
|Mag Gyver
|KNX User Forum
|foxfox[a]versanet.de
|01.01.2016
|-
|257
|0101
|dreamy1
|KNX User Forum
|stejak9999[a]gmail.com
|28.02.2015
|-
|258
|0102
|ProtoLab
|3D printers and others prototypes
|protolabch[a]gmail.com
|25.08.2016
|-
|259
|0103
|Hassel K.
|KNX User Forum
|hassel[a]audiocommand.de
|16.09.2016
|-
|260
|0104
|simplesign.de
|Andreas Michel
|support[a]simplesign.de
|07.11.2016
|-
|261
|0105
|ivande
|KNX User Forum
|ivande[a]gmx.net
|10.01.2017
|-
|262
|0106
|Simon Golpe
|KNX User Forum
|simongolpevarela[a]hotmail.de
|30.10.2017
|-
|263
|0107
|Peterich
|KNX User Forum
|tomypter89[a]gmail.com
|05.01.2018
|-
|264
|0108
|Sonnengruesser
|KNX User Forum
|ah-angst[a]gmx.at
|10.02.2018
|-
|265
|0109
|Frank Plass
|Frank Plass
|konnekting[a]f-plass.de
|24.04.2018
|-
|266
|010A
|Thomas Willi
|KNX User Forum
|info[a]thomas-willi.de
|25.06.2018
|-
|267
|010B
|Chris Lelie
|LELIE electronics
|leliekonnekting[a]gmail.com
|18.09.2018
|-
|268
|010C
|Klaus Weltermann
|Ingenieurbüro Dipl.-Ing. Klaus Weltermann
|klaus[a]weltermann.eu
|22.10.2018
|-
|269
|010D
|Michael Rüttgers
|Michael Rüttgers
|michael[a]ruettgers.eu
|22.11.2018
|-
|270
|010E
|bonzai
|KNX User Forum / bonzai
|konnekting[a]bonzais-garden.de
|13.12.2018
|-
|271
|010F
|Markus Netzlaff
|KNX User Forum / netzlaff
|info[a]netzlaff.de
|22.01.2019
|-
|272
|0110
|Albatros
|Frank Klee
|fklee[a]t-online.de
|23.03.2019
|-
|273
|0111
|MC-Devices
|KNX User Forum / SX3
|m.cheraghi[a]hotmail.com
|23.03.2019
|-
|274
|0112
|traxanos
|KNX User Forum
|konnekting[a]marco-scholl.de
|24.07.2019
|-
|275
|0113
|HRit
|Maker
|smarthome[a]eulennetz.de
|15.09.2020
|-
|276
|0114
|Christoph Reck
|KNX User Forum / reckch
|christoph.reck[a]gmx.de
|15.02.2021
|-
|278
|0115
|F. Zösch
|ZOESCH.ART
|info@zoesch.art
|22.04.2021
|-
|666
|029a
|MGK
|KNX User Forum
|knx[a]grzlhmpf.de
|24.09.2018
|-
|1908
|0774
|Eden Devices
|KNX Special Sensors
|technobucks[a]gmail.com
|06.02.2018
|-
|2069
|0815
|Jens Höppner / jentz1986
|KNX User Forum
|mail[a]jens-hoeppner.de
|05.03.2018
|-
|3333
|0D05
|Ahlqvist
|Joakim Ahlqvist
|konnekting[a]ahlqvist.name
|11.04.2017
|-
|4112
|1010
|René Seigert
|KNX User Forum
|rene_seigert[a]me.com
|12.10.2016
|-
|7070
|1B9E
|Eugen Burkowski
|KONNEKTING Team
|e.burkowski[a]konnekting.de
|12.02.2016
|-
|29495
|7337
|SirSydom
|KNX User Forum
|com[a]sirsydom.de
|10.02.2018
|-
|43981
|ABCD
|Matthias Freudenreich
|KONNEKTING
|KNX.Matthias[a]gmx.de
|15.02.2016
|-
|48842
|BECA
|Josef L.
|KNX User Forum
|josef-konnekting[a]2lj.de
|26.02.2016
|-
|48879
|BEEF
|Artur Pajonk
|Cleveres-Heim
|konnekting[a]cleveres-heim.de
|23.03.2019
|-
|49374
|C0DE
|Alexander Christian
|KONNEKTING Team
|knx[a]root1.de
|15.02.2016
|-
|51966
|CAFE
|E. Hermanns / emax
|KNX User Forum
|emax[a]hermanns.net
|15.02.2016
|-
|52700
|CDDC
|Christian Dürnberger / ChriD
|KNX User Forum
|chris_d85[a]hotmail.com
|27.05.2018
|-
|56506
|DCBA
|Digihome
|Custom Electronic Interfaces
|info[a]digihome.io
|24.07.2019
|-
|57005
|DEAD
|KONNEKTING Team
|For testing only
|info@konnekting.de
|01.01.2016
|-
|64738
|FCE2
|Northman
|KNX User Forum
|northman[a]gmx.de
|25.04.2016
|-
|}

<nowiki>*</nowiki>note: '@' replaced by '[a]'

Click here for a list of known Device IDs: https://wiki.konnekting.de/index.php/Device_ID_List

KONNEKTING Protocol Specification 0x01

2021-03-26T15:22:56Z

Konnekting: /* System Type */ fixed default system to 512 params, see https://gitlab.com/konnekting/KonnektingSuite/-/issues/38

= Workflow =

The following describes the workflow for programming a KONNEKTING device. The diagrams show the required actions the programming device (f.i. [[KONNEKTING Suite]]) needs to do in order to program a KONNEKTING device.

== Start Programming Mode ==

Before the programming can start, the KONNEKTING device needs to be in "programming mode" (short: ProgMode). The following diagram describes the two possible ways to achive ProgMode.

{{#drawio:Protocol0x01WorkflowProgMode}}

== Do Programming ==

After ProgMode has been achived, it's time to do the actual device programming.
For getting an answer for the "... changed?" decision-blocks, a comparison between the "DeviceMemory" section (see: https://gitlab.com/konnekting/KonnektingXmlSchema/blob/develop/src/main/xsd/KonnektingDeviceV0.xsd) of .kconfig.xml with the data the application wants to write. If there are any differences, data has to be written. Either complete, or only the blocks with changes (will speed up programming a lot, especially for small changes).

{{#drawio:Protocol0x01WorkflowTables}}

The parts for "Program CommObjects" and "Program Parameters" are optional an depend on what the user want to program. So you can skip or include them, as you like.

== Working with files ==

This is about working with files, means transfering files to the device, including firmware upgrade

todo ...

= Device Memory Layout =

The device's memory is divided in multiple sections:

{{#drawio:Protocol0x01MemoryLayout}}

Hints:

* The AddressTable is sorted by the GroupAdress ascending by its integer value.
* The AssociationTable is sorted by the GroupAddress ID ascending by its integer value.

== System Table ==

* '''Total table size in bytes:''' 64 bytes, first 48 bytes: fixed, read only; next 16 bytes: variable, readable/writeable

{| class="wikitable"
!style="text-align:center"|Access Mode
!style="text-align:center"|Table Byte Index
!style="text-align:center"|Description
|-
|R
|0
|version byte HI
|-
|R
|1
|version byte LO
|-
|R
|2
|[[#Device Flags]]
|-
|R
|3
|[[#GroupAddress Table]] address HI
|-
|R
|4
|GroupAddress Table address LO
|-
|R
|5
|[[#Association Table]] address HI
|-
|R
|6
|Association Table address LO
|-
|R
|7
|[[#CommObject Table]] address HI
|-
|R
|8
|CommObject Table address LO
|-
|R
|9
|[[#Parameter Table]] address HI
|-
|R
|10
|Parameter Table address LO
|-
|R
|11..14
|CRC System Table
|-
|R
|15..18
|CRC Address Table
|-
|R
|19..22
|CRC Association Table
|-
|R
|23..26
|CRC CommObject Table
|-
|R
|27..30
|CRC Parameter Table
|-
|R
|31..47
|0xFF, unused
|-
|R/W
|48
|IndividualAddress HI
|-
|R/W
|49
|IndividualAddress LO
|-
|R/W
|50..63
|0xFF, unused
|}

=== Device Flags ===

b7 ist the left most bit, b0 is the right most bit.

{| class="wikitable"
!bit
!hex mask
!Description
|-
|b7
|0x80
|Factory flag: 
* 1 = factory settings
* 0 = stored settings
|-
|b6
|0x40
|IA flag: 
* 1 = factory settings
* 0 = stored IA
|-
|b5
|0x20
|CO flag: 
* 1 = factory settings
* 0 = stored COs
|-
|b4
|0x10
|Params flag: 
* 1 = factory settings
* 0 = stored params
|-
|b3
|0x08
|data storage flag: 
* 1 = factory settings
* 0 = storage in use
|-
|b2..b0
|n/a
|unused
|}

== GroupAddress Table ==

* '''Total table size in bytes:''' 1+(n*2) bytes, where n = GroupAddress limit, see [[#System_Type]]

{| class="wikitable"
!style="text-align:center"|Table Byte Index
!style="text-align:center"|Description
|-
|0
|number of filled entries in table
|-
|1
|GroupAddress 0 HI
|-
|2
|GroupAddress 0 LO
|-
|3
|GroupAddress 1 HI
|-
|4
|GroupAddress 1 LO
|-
|5
|GroupAddress 2 HI
|-
|6
|GroupAddress 2 LO
|-
|...
|...
|}

== Association Table ==

* '''Total table size in bytes:''' 1+(n*2) bytes, where n = GA-CommObj relation limit, see [[#System_Type]]

{| class="wikitable"
!style="text-align:center"|Table Byte Index
!style="text-align:center"|Description
|-
|0
|number of filled entries in GA<->CommObj relations table
|-
|1
|GroupAddress ID Nr.1
|-
|2
|CommObj ID Nr.1
|-
|3
|GroupAddress ID Nr.2
|-
|4
|CommObj ID Nr.2
|-
|5
|GroupAddress ID Nr.3
|-
|6
|CommObj ID Nr.3
|-
|...
|...
|}

== CommObject Table ==

* '''Total table size in bytes:''' 1+(n) bytes, where n = CommObjects limit, see [[#System_Type]]

{| class="wikitable"
!style="text-align:center"|Table Byte Index
!style="text-align:center"|Description
|-
|0
|number of existing CommObjects
|-
|1
|config byte (see below) of CommObject ID 0
|-
|2
|config byte of CommObject ID 1
|-
|3
|config byte of CommObject ID 2
|-
|...
|...
|}

=== CommObject config byte ===

b7 ist the left most bit, b0 is the right most bit.

{| class="wikitable"
!bit
!hex mask
!Description
|-
|b7
|0x80
|unused, 0x00
|-
|b6
|0x40
|unused, 0x00
|-
|b5
|0x20
|C: the Communication flag
|-
|b4
|0x10
|R: the Read flag
|-
|b3
|0x08
|T: the Transmit flag
|-
|b2
|0x04
|W: the Write flag
|-
|b1
|0x02
|U: the Update flag
|-
|b0
|0x01
|I: the Initialization flag
|}

== Parameter Table ==

* '''Total table size in bytes:''' depends on actual by device provided parameters

{| class="wikitable"
!style="text-align:center"|Table Byte Index
!style="text-align:center"|Description
|-
|0
|...
|-
|1
|...
|-
|2
|...
|-
|3
|...
|-
|...
|...
|}

== User Space ==

This is the space where user data can be stored. The [[KONNEKTING Device Library]] provides an API to query the start address for this user space in memory.

= Property Pages =

Property pages are blocks information with up to 12 bytes of length. Property pages are read-only and do not directly belong to the device's memory (f.i. EEPROM or Flash). The information is mostly stored in the device firmware.

== 0x00 Device Info ==

* '''Property Page Number:''' 0 dec / 0x00 hex
* '''Property Page Name:''' Device Information

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|Manufacturer-ID HI
|-
|3
|Manufacturer-ID LO
|-
|4
|Device-ID
|-
|5
|RevisionID
|-
|6
|'''System Type''', see [[#System Type]]
|-
|7..13
|0xFF, unused
|}

=== System Type ===

{| class="wikitable"
!hex
!Name
!Description
|-
|0x00
|System 0 ''Simple''
|Up to: 
* 128 GAs
* 128 GA-ComObj relations
* 128 ComObjects
* 128 Parameters
* Supports Default Frame
|-
|0x01
|System 1 ''Default''
| Up to: 
* 255 GAs
* 255 GA-ComObj relations
* 255 ComObjects
* 512 Parameters
* Supports FOTB (firmware-over-the-bus)
* Supports Extended Frame (DRAFT)
|-
|0x02
|System 2 Extended ''DRAFT''
| Up to: 
* 65535 GAs (32*8*256)
* 65535 GA-ComObj relations
* 65535 ComObjects
* 65535 Parameters
* Supports FOTB (firmware-over-the-bus)
* Supports Extended Frame
|-
|}

GAs = Unique GroupAddresses 
GA-ComObj relations = Assignments of GAs to ComObjects 
ComObjects = Number of ComObjects 
Parameters = Number of Parameters 

= Message Types for Protocol-Version 0x01 =

These are the messages KONNEKTING uses to communicate between the programming device and the KONNEKTING device.

== 0x00 Acknowledge ==

* '''Message Name:''' Acknowledge
* '''Message-Type-ID:''' 0 dec / 0x00 hex
* '''Direction:''' Device -> Suite
* '''Expected Response:''' n/a
* '''Description:''' Sent by device as answer to most WRITE messages
* '''Requires Programming Mode:''' n/a

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|'''Acknowledge Type'''
|-
|3
|'''Error Code'''
|-
|4..13
|0xFF, unused
|}

=== Acknowledge Type ===

{| class="wikitable"
!style="text-align:center"|hex
!style="text-align:center"|Description
|-
|0x00
|ACK
|-
|0xFF
|NACK
|}

=== Error Code ===

{| class="wikitable"
!style="text-align:center"|hex
!style="text-align:center"|Description
|-
|0x00
|ERR_CODE_OK
|-
|0x01
|ERR_CODE_NOT_SUPPORTED
|-
|0x02
|ERR_CODE_DATA_OPEN_WRITE_FAILED
|-
|0x03
|ERR_CODE_DATA_OPEN_READ_FAILED
|-
|0x04
|ERR_CODE_DATA_WRITE_FAILED
|-
|0x05
|ERR_CODE_DATA_READ_FAILED
|-
|0x06
|ERR_CODE_DATA_CRC_FAILED
|-
|0x07
|ERR_CODE_TIMEOUT
|-
|0x08
|ERR_CODE_ILLEGAL_STATE
|-
|0x09
|ERR_CODE_TABLE_CRC_FAILED
|}

== 0x01 PropertyPageRead ==

* '''Message Name:''' PropertyPageRead
* '''Message-Type-ID:''' 1 dec / 0x01 hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x02 PropertyPageResponse]]
* '''Description:''' Read one page of property data
* '''Requires Programming Mode:''' no

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|addressflag: 0x00=only reply when progmode is set; 0xFF=only reply if following IA does match
|-
|3
|IndividualAddress HI; 0xFF/unused if b[2]=0x00
|-
|4
|IndividualAddress LO; 0xFF/unused if b[2]=0x00
|-
|5
|property page num, 0x00..0xFF, see [[#Property Pages]] for more details
|-
|6..13
|0xFF, unused
|}

== 0x02 PropertyPageResponse ==

* '''Message Name:''' PropertyPageResponse
* '''Message-Type-ID:''' 2 dec / 0x02 hex
* '''Direction:''' Device -> Suite
* '''Expected Response:''' n/a
* '''Description:''' One page of property data
* '''Requires Programming Mode:''' no

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2..13
|12 bytes of property page data, see [[#Property Pages]] for more details
|}

== 0x03 ChecksumSet ==

* '''Message Name:''' ChecksumSet
* '''Message-Type-ID:''' 3 dec / 0x03 hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' store a CRC value
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|CRC identifier, see [[#CRC identifier]]
|-
|3..6
|CRC32, 4 byte value
|-
|7..16
|0xFF, unused
|}

=== CRC identifier ===

{| class="wikitable"
!style="text-align:center"|hex
!style="text-align:center"|Description
|-
|0x00
|SystemTable ReadWriteable section checksum
|-
|0x01
|AddressTable checksum
|-
|0x02
|AssociationTable checksum
|-
|0x03
|CommObjectTable checksum
|-
|0x04
|PaameterTable checksum
|}

== 0x08 Unload ==

* '''Message Name:''' Unload
* '''Message-Type-ID:''' 8 dec / 0x08 hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' Unload device. After successfull unload, device will reboot.
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|Factory Reset, 0x00 = false, 0xFF=true if true, all other bits are irrelevant
|-
|3
|Unload Individual Address, 0x00 = false, 0xFF=true
|-
|4
|Unload ComObjects, 0x00 = false, 0xFF=true
|-
|5
|Unload Parameters, 0x00 = false, 0xFF=true
|-
|6
|Unload data storage (see: #0x28 DataWriteprepare etc), 0x00 = false, 0xFF=true
|-
|7..13
|0xFF, unused
|}

== 0x09 Restart ==

* '''Message Name:''' Restart
* '''Message-Type-ID:''' 9 dec / 0x09 hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' Restart device (device reboot, no memory reset)
* '''Requires Programming Mode:''' no

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|IndividualAddress HI
|-
|3
|IndividualAddress LO
|-
|4..13
|0xFF, unused
|}

== 0x0A ProgrammingModeWrite ==

* '''Message Name:''' ProgrammingModeWrite
* '''Message-Type-ID:''' 10 dec / 0x0A hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' Sets/Unsets Programming-Mode for device with given individual address. Device will respond with a "Acknowledge" message.
* '''Requires Programming Mode:''' no

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|IndividualAddress HI
|-
|3
|IndividualAddress LO
|-
|4
|'''Mode:''' 
0x00 = OFF 
0x01 = ON
|-
|5..13
|0xFF, unused
|}

== 0x0B ProgrammingModeRead ==

* '''Message Name:''' ProgrammingModeRead
* '''Message-Type-ID:''' 11 dec / 0x0B hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x0C ProgrammingModeResponse]]
* '''Description:''' Reads current programming mode of all listening devices. If more than one device is in programming-mode, you will get more then one [[#0x0C ProgrammingModeResponse]] messages.
* '''Requires Programming Mode:''' no

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2..13
|0xFF, unused
|}

== 0x0C ProgrammingModeResponse ==

* '''Message Name:''' ProgrammingModeResponse
* '''Message-Type-ID:''' 12 dec / 0x11 hex
* '''Direction:''' Device -> Suite
* '''Expected Response:''' n/a
* '''Description:''' Response to ProgrammingModeRead message.
* '''Requires Programming Mode:''' n/a

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|IndividualAddress HI
|-
|3
|IndividualAddress LO
|-
|4..13
|0xFF, unused
|}

== 0x1E MemoryWrite ==

* '''Message Name:''' MemoryWrite
* '''Message-Type-ID:''' 30 dec / 0x1E hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' Write data to device memory
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|Count: Number of bytes to write to memory, starting at "Address"
|-
|3
|Address uint16[0] HI
|-
|4
|Address uint16[1] LO
|-
|5..13
|1..9 bytes of Data, depends on "Count". Remaining bytes: 0xFF
|}

== 0x1F MemoryRead ==

* '''Message Name:''' MemoryRead
* '''Message-Type-ID:''' 31 dec / 0x1F hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x20 MemoryResponse]]
* '''Description:''' Reads data from device memory
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|Count: Number of bytes to read from address. Range 1..9
|-
|3
|Address HI
|-
|4
|Address LO
|-
|5..13
|0xFF, unused
|}

=== Memory Tables ===

With help of [[#0x1F MemoryRead]] and [[#0x1E MemoryWrite]] one can access the device's memory (EEPROM, flash, ...). The memory stores different tables for different usage.
As both messages access memory by memory address, one has to know at which address which table starts. To get the start addresses of all tables, see [[#System Table]].

== 0x20 MemoryResponse ==

* '''Message Name:''' MemoryResponse
* '''Message-Type-ID:''' 32 dec / 0x20 hex
* '''Direction:''' Device -> Suite
* '''Expected Response:''' n/a
* '''Description:''' Response to MemoryRead
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|Count: Number of bytes that have been read from address
|-
|3
|Address HI
|-
|4
|Address LO
|-
|5..13
|1..9 bytes of Data, depends on "Count". Remaining bytes: 0xFF
|}

== 0x28 DataWritePrepare ==

* '''Message Name:''' DataWritePrepare
* '''Message-Type-ID:''' 40 dec / 0x28 hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' prepare writing data
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|'''Data Type''', see below
|-
|3
|Data ID unique identifier for the data
|-
|4
|size of data uint32[0]
|-
|5
|size of data uint32[1]
|-
|6
|size of data uint32[2]
|-
|7
|size of data uint32[3]
|-
|8..13
|unused, 0xFF
|}

=== Data Type ===

{| class="wikitable"
!hex
!Name
!Data ID range
!Description
|-
|0x00
|UPDATE
|always 0x00
|Firmware update for KONNEKTING device
|-
|0x01
|DATA
|0x00..0xFF
|f.i. additional configuration, images, sounds, ...
|}

== 0x29 DataWrite ==

* '''Message Name:''' DataWrite
* '''Message-Type-ID:''' 41 dec / 0x29 hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' Writing data
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|Count<ref>required to determin the end of data in last DataWrite message</ref>: 1..11 bytes
|-
|3..13
|1..11 bytes of Data, depends on "Count". Remaining bytes: 0xFF
|}

'''Notes:'''
<references />

== 0x2A DataWriteFinish ==

* '''Message Name:''' DataWriteFinish
* '''Message-Type-ID:''' 42 dec / 0x2A hex
* '''Description:''' finish writing data
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|CRC32[0] <ref>https://github.com/bakercp/CRC32</ref>
|-
|3
|CRC32[1]
|-
|4
|CRC32[2]
|-
|5
|CRC32[3]
|-
|6..13
|unused, 0xFF
|}

'''Notes:'''
<references />

== 0x2B DataRead ==

* '''Message Name:''' DataRead
* '''Message-Type-ID:''' 43 dec / 0x2B hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x2C DataReadResponse]], providing the size, followed by n times [[#0x2D DataReadData]] until end of data and finally again [[#0x2C DataReadResponse]], providing the CRC32
* '''Description:''' trigger reading data
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|'''[[Data Type]]''' range: 0x01..01FF (0x00 can't be read, as this is firmware)
|-
|3
|Data ID unique identifier for the data to read
|-
|4..13
|unused, 0xFF
|}

== 0x2C DataReadResponse ==

* '''Message Name:''' DataReadResponse
* '''Message-Type-ID:''' 44 dec / 0x2C hex
* '''Direction:''' Device -> Suite
* '''Expected Response:''' n/a
* '''Description:''' meta data about the requested data. The actual data will follow in separate messages ([[#0x2D DataReadData]])
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|'''[[#Data_Type|Data Type]]'''
|-
|3
|Data ID unique identifier for the data
|-
|4
|size of data uint32[0]
|-
|5
|size of data uint32[1]
|-
|6
|size of data uint32[2]
|-
|7
|size of data uint32[3]
|-
|8
|CRC32[0] <ref>https://github.com/bakercp/CRC32</ref>
|-
|9
|CRC32[1]
|-
|10
|CRC32[2]
|-
|11
|CRC32[3]
|-
|12..13
|unused, 0xFF
|}

== 0x2D DataReadData ==

* '''Message Name:''' DataReadData
* '''Message-Type-ID:''' 45 dec / 0x2D hex
* '''Direction:''' Device -> Suite
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' packet of requested data from device. Device will send several messages of this type until whole data is transferred
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|Count<ref>required to determin the end of data in message</ref>: 1..11 bytes
|-
|3..13
|1..11 bytes of Data, depends on "Count". Remaining bytes: 0xFF
|}

== 0x2E DataRemove ==

* '''Message Name:''' DataRemove
* '''Message-Type-ID:''' 46 dec / 0x2E hex
* '''Direction:''' Suite -> Device
* '''Expected Response:''' [[#0x00 Acknowledge]]
* '''Description:''' remove previously stored data
* '''Requires Programming Mode:''' yes

{| class="wikitable"
!style="text-align:center"|Byte no#
!style="text-align:center"|Description
|-
|2
|'''[[#Data_Type|Data Type]]''' range: 0x01..0xFF<ref>0x00 is reserved for UPDATE</ref>
|-
|3
|Data ID unique identifier for the data
|-
|4..13
|unused, 0xFF
|}

'''Notes:'''
<references />

KONNEKTING Modular DIN RAIL Device Specification

2021-02-15T09:50:58Z

Konnekting: /* Mechanical */

== Din Rail Case ==

Manufacturer: https://www.okw.com

Part: Railtec B - 4 TE / https://www.okw.com/de/Railtec-B/B6503121.htm?var=c9f11140-cb2e-11e3-89f9-00163e72470b

The case can be ordered directly from OKW. But keep in mind that you should reach 100EUR netto to overcome additional shipping fees.
Your can also order the case at buerklin.com without the 100EUR limit. Just search for the OKW part-number with the search on the Bürklin web page.

Example:

[[File:DFF4.1 1.0.png|300px|thumb|center]]

== BOM ==

{| border="1" style="border-collapse:collapse"
! scope="col"|Picture
! scope="col"|Description
! scope="col"|OKW part number
! scope="col"|Bürklin order number
! scope="col"|OKW link
! scope="col"|Bürklin link
|-
|[[File:OKW-B6503121.png|120px|thumb|left|B6503121]]
|RAILTEC B, 4 MODULES, VERS. VI (1 base part with locking clip, 1 top part)
|B6503121
|30H2334
|https://www.okw.com/en/Railtec-B/B6503121.htm
|https://www.buerklin.com/de/RAILTEC-B-4-Module-Ausf-VI/p/30H2334
|-
|[[File:OKW-B6607145.png|120px|thumb|left|B6607145]]
|KNX COVER, FLAT
|B6607145
|30H2433
|https://www.okw.com/en/Railtec-B/B6607145.htm
|https://www.buerklin.com/de/Abdeckung-KNX-flach/p/30H2433
|-
|[[File:OKW-B6607143.png|120px|thumb|left|B6607143]]
|TERMINAL GUARDS, FLAT (Perforated, for block 5.0)
|B6607143
|30H2432
|https://www.okw.com/en/Railtec-B/B6607143.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2432
|-
|[[File:OKW-B6607141.png|120px|thumb|left|B6607141]]
|TERMINAL GUARDS, FLAT (With ventilation slots)
|B6607141
|30H2430
|https://www.okw.com/en/Railtec-B/B6607141.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2430
|-
|[[File:OKW-B6607140.png|120px|thumb|left|B6607140]]
|TERMINAL GUARDS, FLAT (Closed)
|B6607140
|30H2429
|https://www.okw.com/en/Railtec-B/B6607140.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2429
|-
|[[File:OKW-B6603180.png|120px|thumb|left|B6603180]]
|FRONT PANEL, 4 MODULES, VERS. VI
|B6603180
|30H2402
|https://www.okw.com/en/Railtec-B/B6603180.htm
|https://www.buerklin.com/de/Frontplatte-4-Module-Ausf-VI/p/30H2402
|}

== Mechanical ==

The OKW case allows PCBs on 3 levels. From top to bottom we name them:

* Frontend PCB
* Controller PCB
* Application PCB

The PCBs are screwed together with M3 hex-spacers. Here's a mechanical overview (from top to bottom):

[2mm space to outer case edge]
[1,6mm inner OKW Railtec cover]
[6,1mm free space to inner OKW Railtec lid] → top-edge inner lid to top-edge frontend pcb = 7,7mm
['''1,6mm Frontend PCB''']
[15mm M3 hex spacer]
['''1,6mm Controller PCB''']
[18mm M3 hex spacer]
['''1,6mm Application PCB''']
[3,5mm screw pin on black OKW Railtec base plate]

Recommendation for tactile push button Frontend PCB: 9,5mm height.

{|
|'''THT'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/3/index.html?ACTION=3&LA=2&ARTICLE=27893&GROUPID=7587&artnr=TASTER+3301B&SEARCH=%252A
|-
|'''SMD'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-9319/3/index.html?ACTION=3&LA=2&ARTICLE=44518&GROUPID=7587&artnr=TASTER+9319&SEARCH=%252A
|}

5mm LED PCB spacer for 3mm THT LEDs: http://www.reichelt.de/Zubehoer-fuer-LEDs/MEN-2818-3045/3/index.html?ACTION=3&LA=446&ARTICLE=62820&GROUPID=3044&artnr=MEN+2818.3045&SEARCH=led%2Babstandshalter

→ the LED protrudes about 2mm out of the cover lid.
→ Use 4mm led spacer to reduce this to 1mm

You can use a plain PCB with silkscreen printing and wholes to create a nice looking cover, that sits on the OKW Railtec lid. This will also fill the remaining space to the outer case edge on top of the OKW lid.

== Reference controller ==

See [[M0dularis+]]

== Interconnections ==

=== Controller: Application Socket ===

The controller PCB must use a 2x4 or 2x8 micromatch socket.

Example controller PCB (on top: application socket, on left: frontend socket):

[[File:M0dularisM Plus.jpg|300px|thumb|center|M0dularis+ Controller with µBCU]]

Pinout:

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND / KNX GND
|1
|2
| style="background-color: grey;"|GND from 24V Input
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: indianred;"|24V from 24V Input
|-
| style="background-color: yellow;"|SDA / IO0
|5
|6
| style="background-color: limegreen;"|IO3
|-
| style="background-color: yellow;"|SCL / IO1
|7
|8
| style="background-color: lightblue;"|ExtINT Application / IO2
|-
| style="background-color: mediumseagreen;"|Option0
|9
|10
| style="background-color: mediumseagreen;"|Option7
|-
| style="background-color: mediumseagreen;"|Option1
|11
|12
| style="background-color: mediumseagreen;"|Option6
|-
| style="background-color: mediumseagreen;"|Option2
|13
|14
| style="background-color: mediumseagreen;"|Option5
|-
| style="background-color: mediumseagreen;"|Option3
|15
|16
| style="background-color: mediumseagreen;"|Option4
|}

Remarks:

* '''Option0..7''': Freely selectable, depends on the controller. If not used at all: Stick to Pin1..8 and apply a 2x4 micromatch socket only.
* '''IO0..IO3''': Freely selectable, but:
**'''SDA/SCL''': This pins must have I2C capabilities
**'''ExtINT''': This pin must have interrupt capabilities
*'''24V Input''': 24V DC supply voltage from separate socket with white/yellow wire pair
*'''GND''': relative to VCC
*'''GND 24V''': relative to 24V DC Input
*'''VCC''': 3.3V or 5V, depending on the controller, if possible, selectable with jumper/solderjumper

=== Controller: Frontend Application Socket ===

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND
|1
|2
| style="background-color: yellow;"|SDA
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: yellow;"|SCL
|-
|unused/reserve
|5
|6
| style="background-color: lightblue;"|ExtINT Frontend
|}

Remarks:

* See Application Connector above

=== Controller: Extension Socket ===

[[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) not yet fully specified. work in progress

KONNEKTING Modular DIN RAIL Device Specification

2021-02-15T09:50:19Z

Konnekting: /* BOM */

== Din Rail Case ==

Manufacturer: https://www.okw.com

Part: Railtec B - 4 TE / https://www.okw.com/de/Railtec-B/B6503121.htm?var=c9f11140-cb2e-11e3-89f9-00163e72470b

The case can be ordered directly from OKW. But keep in mind that you should reach 100EUR netto to overcome additional shipping fees.
Your can also order the case at buerklin.com without the 100EUR limit. Just search for the OKW part-number with the search on the Bürklin web page.

Example:

[[File:DFF4.1 1.0.png|300px|thumb|center]]

== BOM ==

{| border="1" style="border-collapse:collapse"
! scope="col"|Picture
! scope="col"|Description
! scope="col"|OKW part number
! scope="col"|Bürklin order number
! scope="col"|OKW link
! scope="col"|Bürklin link
|-
|[[File:OKW-B6503121.png|120px|thumb|left|B6503121]]
|RAILTEC B, 4 MODULES, VERS. VI (1 base part with locking clip, 1 top part)
|B6503121
|30H2334
|https://www.okw.com/en/Railtec-B/B6503121.htm
|https://www.buerklin.com/de/RAILTEC-B-4-Module-Ausf-VI/p/30H2334
|-
|[[File:OKW-B6607145.png|120px|thumb|left|B6607145]]
|KNX COVER, FLAT
|B6607145
|30H2433
|https://www.okw.com/en/Railtec-B/B6607145.htm
|https://www.buerklin.com/de/Abdeckung-KNX-flach/p/30H2433
|-
|[[File:OKW-B6607143.png|120px|thumb|left|B6607143]]
|TERMINAL GUARDS, FLAT (Perforated, for block 5.0)
|B6607143
|30H2432
|https://www.okw.com/en/Railtec-B/B6607143.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2432
|-
|[[File:OKW-B6607141.png|120px|thumb|left|B6607141]]
|TERMINAL GUARDS, FLAT (With ventilation slots)
|B6607141
|30H2430
|https://www.okw.com/en/Railtec-B/B6607141.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2430
|-
|[[File:OKW-B6607140.png|120px|thumb|left|B6607140]]
|TERMINAL GUARDS, FLAT (Closed)
|B6607140
|30H2429
|https://www.okw.com/en/Railtec-B/B6607140.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2429
|-
|[[File:OKW-B6603180.png|120px|thumb|left|B6603180]]
|FRONT PANEL, 4 MODULES, VERS. VI
|B6603180
|30H2402
|https://www.okw.com/en/Railtec-B/B6603180.htm
|https://www.buerklin.com/de/Frontplatte-4-Module-Ausf-VI/p/30H2402
|}

== Mechanical ==

The OKW case allows PCBs on 3 levels. From top to bottom we name them:

* Frontend PCB
* Controller PCB
* Application PCB

The PCBs are scred together with M3 hex-spacers. Here's a mechanical overview (from top to bottom):

[2mm space to outer case edge]
[1,6mm inner OKW Railtec cover]
[6,1mm free space to inner OKW Railtec lid] → top-edge inner lid to top-edge frontend pcb = 7,7mm
['''1,6mm Frontend PCB''']
[15mm M3 hex spacer]
['''1,6mm Controller PCB''']
[18mm M3 hex spacer]
['''1,6mm Application PCB''']
[3,5mm screw pin on black OKW Railtec base plate]

Recommendation for tactile push button Frontend PCB: 9,5mm height.

{|
|'''THT'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/3/index.html?ACTION=3&LA=2&ARTICLE=27893&GROUPID=7587&artnr=TASTER+3301B&SEARCH=%252A
|-
|'''SMD'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-9319/3/index.html?ACTION=3&LA=2&ARTICLE=44518&GROUPID=7587&artnr=TASTER+9319&SEARCH=%252A
|}

5mm LED PCB spacer for 3mm THT LEDs: http://www.reichelt.de/Zubehoer-fuer-LEDs/MEN-2818-3045/3/index.html?ACTION=3&LA=446&ARTICLE=62820&GROUPID=3044&artnr=MEN+2818.3045&SEARCH=led%2Babstandshalter

→ the LED protrudes about 2mm out of the cover lid.
→ Use 4mm led spacer to reduce this to 1mm

You can use a plain PCB with silkscreen printing and wholes to create a nice looking cover, that sits on the OKW Railtec lid. This will also fill the remaining space to the outer case edge on top of the OKW lid.

== Reference controller ==

See [[M0dularis+]]

== Interconnections ==

=== Controller: Application Socket ===

The controller PCB must use a 2x4 or 2x8 micromatch socket.

Example controller PCB (on top: application socket, on left: frontend socket):

[[File:M0dularisM Plus.jpg|300px|thumb|center|M0dularis+ Controller with µBCU]]

Pinout:

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND / KNX GND
|1
|2
| style="background-color: grey;"|GND from 24V Input
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: indianred;"|24V from 24V Input
|-
| style="background-color: yellow;"|SDA / IO0
|5
|6
| style="background-color: limegreen;"|IO3
|-
| style="background-color: yellow;"|SCL / IO1
|7
|8
| style="background-color: lightblue;"|ExtINT Application / IO2
|-
| style="background-color: mediumseagreen;"|Option0
|9
|10
| style="background-color: mediumseagreen;"|Option7
|-
| style="background-color: mediumseagreen;"|Option1
|11
|12
| style="background-color: mediumseagreen;"|Option6
|-
| style="background-color: mediumseagreen;"|Option2
|13
|14
| style="background-color: mediumseagreen;"|Option5
|-
| style="background-color: mediumseagreen;"|Option3
|15
|16
| style="background-color: mediumseagreen;"|Option4
|}

Remarks:

* '''Option0..7''': Freely selectable, depends on the controller. If not used at all: Stick to Pin1..8 and apply a 2x4 micromatch socket only.
* '''IO0..IO3''': Freely selectable, but:
**'''SDA/SCL''': This pins must have I2C capabilities
**'''ExtINT''': This pin must have interrupt capabilities
*'''24V Input''': 24V DC supply voltage from separate socket with white/yellow wire pair
*'''GND''': relative to VCC
*'''GND 24V''': relative to 24V DC Input
*'''VCC''': 3.3V or 5V, depending on the controller, if possible, selectable with jumper/solderjumper

=== Controller: Frontend Application Socket ===

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND
|1
|2
| style="background-color: yellow;"|SDA
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: yellow;"|SCL
|-
|unused/reserve
|5
|6
| style="background-color: lightblue;"|ExtINT Frontend
|}

Remarks:

* See Application Connector above

=== Controller: Extension Socket ===

[[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) not yet fully specified. work in progress

File:OKW-B6603180.png

2021-02-15T09:47:51Z

Konnekting: OKW-B6603180

== Summary ==
OKW-B6603180
== Licensing ==
{{CopyrightByKONNEKTING}}

File:OKW-B6607140.png

2021-02-15T09:47:36Z

Konnekting: OKW-B6607140

== Summary ==
OKW-B6607140
== Licensing ==
{{CopyrightByKONNEKTING}}

File:OKW-B6607141.png

2021-02-15T09:46:55Z

Konnekting: OKW-B6607141

== Summary ==
OKW-B6607141
== Licensing ==
{{CopyrightByKONNEKTING}}

File:OKW-B6607143.png

2021-02-15T09:43:27Z

Konnekting: OKW-B6607143

== Summary ==
OKW-B6607143
== Licensing ==
{{CopyrightByKONNEKTING}}

KONNEKTING Modular DIN RAIL Device Specification

2021-02-15T09:42:06Z

Konnekting: /* BOM */

== Din Rail Case ==

Manufacturer: https://www.okw.com

Part: Railtec B - 4 TE / https://www.okw.com/de/Railtec-B/B6503121.htm?var=c9f11140-cb2e-11e3-89f9-00163e72470b

The case can be ordered directly from OKW. But keep in mind that you should reach 100EUR netto to overcome additional shipping fees.
Your can also order the case at buerklin.com without the 100EUR limit. Just search for the OKW part-number with the search on the Bürklin web page.

Example:

[[File:DFF4.1 1.0.png|300px|thumb|center]]

== BOM ==

{| border="1" style="border-collapse:collapse"
! scope="col"|Picture
! scope="col"|Description
! scope="col"|OKW part number
! scope="col"|Bürklin order number
! scope="col"|OKW link
! scope="col"|Bürklin link
|-
|[[File:OKW-B6503121.png|200px|thumb|left|B6503121]]
|RAILTEC B, 4 MODULES, VERS. VI (1 base part with locking clip, 1 top part)
|B6503121
|30H2334
|https://www.okw.com/en/Railtec-B/B6503121.htm
|https://www.buerklin.com/de/RAILTEC-B-4-Module-Ausf-VI/p/30H2334
|-
|[[File:OKW-B6607145.png|200px|thumb|left|B6607145]]
|KNX COVER, FLAT
|B6607145
|30H2433
|https://www.okw.com/en/Railtec-B/B6607145.htm
|https://www.buerklin.com/de/Abdeckung-KNX-flach/p/30H2433
|-
|[[File:OKW-B6607143.png|200px|thumb|left|B6607143]]
|TERMINAL GUARDS, FLAT (Perforated, for block 5.0)
|B6607143
|30H2432
|https://www.okw.com/en/Railtec-B/B6607143.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2432
|-
|[[File:OKW-B6607141.png|200px|thumb|left|B6607141]]
|TERMINAL GUARDS, FLAT (With ventilation slots)
|B6607141
|30H2430
|https://www.okw.com/en/Railtec-B/B6607141.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2430
|-
|[[File:OKW-B6607140.png|200px|thumb|left|B6607140]]
|TERMINAL GUARDS, FLAT (Closed)
|B6607140
|30H2429
|https://www.okw.com/en/Railtec-B/B6607140.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2429
|-
|[[File:OKW-B6603180.png|200px|thumb|left|B6603180]]
|FRONT PANEL, 4 MODULES, VERS. VI
|B6603180
|30H2402
|https://www.okw.com/en/Railtec-B/B6603180.htm
|https://www.buerklin.com/de/Frontplatte-4-Module-Ausf-VI/p/30H2402
|}

== Mechanical ==

The OKW case allows PCBs on 3 levels. From top to bottom we name them:

* Frontend PCB
* Controller PCB
* Application PCB

The PCBs are scred together with M3 hex-spacers. Here's a mechanical overview (from top to bottom):

[2mm space to outer case edge]
[1,6mm inner OKW Railtec cover]
[6,1mm free space to inner OKW Railtec lid] → top-edge inner lid to top-edge frontend pcb = 7,7mm
['''1,6mm Frontend PCB''']
[15mm M3 hex spacer]
['''1,6mm Controller PCB''']
[18mm M3 hex spacer]
['''1,6mm Application PCB''']
[3,5mm screw pin on black OKW Railtec base plate]

Recommendation for tactile push button Frontend PCB: 9,5mm height.

{|
|'''THT'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/3/index.html?ACTION=3&LA=2&ARTICLE=27893&GROUPID=7587&artnr=TASTER+3301B&SEARCH=%252A
|-
|'''SMD'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-9319/3/index.html?ACTION=3&LA=2&ARTICLE=44518&GROUPID=7587&artnr=TASTER+9319&SEARCH=%252A
|}

5mm LED PCB spacer for 3mm THT LEDs: http://www.reichelt.de/Zubehoer-fuer-LEDs/MEN-2818-3045/3/index.html?ACTION=3&LA=446&ARTICLE=62820&GROUPID=3044&artnr=MEN+2818.3045&SEARCH=led%2Babstandshalter

→ the LED protrudes about 2mm out of the cover lid.
→ Use 4mm led spacer to reduce this to 1mm

You can use a plain PCB with silkscreen printing and wholes to create a nice looking cover, that sits on the OKW Railtec lid. This will also fill the remaining space to the outer case edge on top of the OKW lid.

== Reference controller ==

See [[M0dularis+]]

== Interconnections ==

=== Controller: Application Socket ===

The controller PCB must use a 2x4 or 2x8 micromatch socket.

Example controller PCB (on top: application socket, on left: frontend socket):

[[File:M0dularisM Plus.jpg|300px|thumb|center|M0dularis+ Controller with µBCU]]

Pinout:

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND / KNX GND
|1
|2
| style="background-color: grey;"|GND from 24V Input
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: indianred;"|24V from 24V Input
|-
| style="background-color: yellow;"|SDA / IO0
|5
|6
| style="background-color: limegreen;"|IO3
|-
| style="background-color: yellow;"|SCL / IO1
|7
|8
| style="background-color: lightblue;"|ExtINT Application / IO2
|-
| style="background-color: mediumseagreen;"|Option0
|9
|10
| style="background-color: mediumseagreen;"|Option7
|-
| style="background-color: mediumseagreen;"|Option1
|11
|12
| style="background-color: mediumseagreen;"|Option6
|-
| style="background-color: mediumseagreen;"|Option2
|13
|14
| style="background-color: mediumseagreen;"|Option5
|-
| style="background-color: mediumseagreen;"|Option3
|15
|16
| style="background-color: mediumseagreen;"|Option4
|}

Remarks:

* '''Option0..7''': Freely selectable, depends on the controller. If not used at all: Stick to Pin1..8 and apply a 2x4 micromatch socket only.
* '''IO0..IO3''': Freely selectable, but:
**'''SDA/SCL''': This pins must have I2C capabilities
**'''ExtINT''': This pin must have interrupt capabilities
*'''24V Input''': 24V DC supply voltage from separate socket with white/yellow wire pair
*'''GND''': relative to VCC
*'''GND 24V''': relative to 24V DC Input
*'''VCC''': 3.3V or 5V, depending on the controller, if possible, selectable with jumper/solderjumper

=== Controller: Frontend Application Socket ===

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND
|1
|2
| style="background-color: yellow;"|SDA
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: yellow;"|SCL
|-
|unused/reserve
|5
|6
| style="background-color: lightblue;"|ExtINT Frontend
|}

Remarks:

* See Application Connector above

=== Controller: Extension Socket ===

[[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) not yet fully specified. work in progress

File:OKW-B6607145.png

2021-02-15T09:40:49Z

Konnekting: OKW-B6607145

== Summary ==
OKW-B6607145
== Licensing ==
{{CopyrightByKONNEKTING}}

KONNEKTING Modular DIN RAIL Device Specification

2021-02-15T09:40:25Z

Konnekting: /* BOM */

== Din Rail Case ==

Manufacturer: https://www.okw.com

Part: Railtec B - 4 TE / https://www.okw.com/de/Railtec-B/B6503121.htm?var=c9f11140-cb2e-11e3-89f9-00163e72470b

The case can be ordered directly from OKW. But keep in mind that you should reach 100EUR netto to overcome additional shipping fees.
Your can also order the case at buerklin.com without the 100EUR limit. Just search for the OKW part-number with the search on the Bürklin web page.

Example:

[[File:DFF4.1 1.0.png|300px|thumb|center]]

== BOM ==

{| border="1" style="border-collapse:collapse"
! scope="col"|Picture
! scope="col"|Description
! scope="col"|OKW part number
! scope="col"|Bürklin order number
! scope="col"|OKW link
! scope="col"|Bürklin link
|-
|[[File:OKW-B6503121.png|200px|thumb|left|B6503121]]
|RAILTEC B, 4 MODULES, VERS. VI (1 base part with locking clip, 1 top part)
|B6503121
|30H2334
|https://www.okw.com/en/Railtec-B/B6503121.htm
|https://www.buerklin.com/de/RAILTEC-B-4-Module-Ausf-VI/p/30H2334
|-
|[[File:OKW-B6607145.png|200px|thumb|left|B6607145]]
|KNX COVER, FLAT
|B6607145
|30H2433
|https://www.okw.com/en/Railtec-B/B6607145.htm
|https://www.buerklin.com/de/Abdeckung-KNX-flach/p/30H2433
|-
|n/a
|TERMINAL GUARDS, FLAT (Perforated, for block 5.0)
|B6607143
|30H2432
|https://www.okw.com/en/Railtec-B/B6607143.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2432
|-
|n/a
|TERMINAL GUARDS, FLAT (With ventilation slots)
|B6607141
|30H2430
|https://www.okw.com/en/Railtec-B/B6607141.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2430
|-
|n/a
|TERMINAL GUARDS, FLAT (Closed)
|B6607140
|30H2429
|https://www.okw.com/en/Railtec-B/B6607140.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2429
|-
|n/a
|FRONT PANEL, 4 MODULES, VERS. VI
|B6603180
|30H2402
|https://www.okw.com/en/Railtec-B/B6603180.htm
|https://www.buerklin.com/de/Frontplatte-4-Module-Ausf-VI/p/30H2402
|}

== Mechanical ==

The OKW case allows PCBs on 3 levels. From top to bottom we name them:

* Frontend PCB
* Controller PCB
* Application PCB

The PCBs are scred together with M3 hex-spacers. Here's a mechanical overview (from top to bottom):

[2mm space to outer case edge]
[1,6mm inner OKW Railtec cover]
[6,1mm free space to inner OKW Railtec lid] → top-edge inner lid to top-edge frontend pcb = 7,7mm
['''1,6mm Frontend PCB''']
[15mm M3 hex spacer]
['''1,6mm Controller PCB''']
[18mm M3 hex spacer]
['''1,6mm Application PCB''']
[3,5mm screw pin on black OKW Railtec base plate]

Recommendation for tactile push button Frontend PCB: 9,5mm height.

{|
|'''THT'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/3/index.html?ACTION=3&LA=2&ARTICLE=27893&GROUPID=7587&artnr=TASTER+3301B&SEARCH=%252A
|-
|'''SMD'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-9319/3/index.html?ACTION=3&LA=2&ARTICLE=44518&GROUPID=7587&artnr=TASTER+9319&SEARCH=%252A
|}

5mm LED PCB spacer for 3mm THT LEDs: http://www.reichelt.de/Zubehoer-fuer-LEDs/MEN-2818-3045/3/index.html?ACTION=3&LA=446&ARTICLE=62820&GROUPID=3044&artnr=MEN+2818.3045&SEARCH=led%2Babstandshalter

→ the LED protrudes about 2mm out of the cover lid.
→ Use 4mm led spacer to reduce this to 1mm

You can use a plain PCB with silkscreen printing and wholes to create a nice looking cover, that sits on the OKW Railtec lid. This will also fill the remaining space to the outer case edge on top of the OKW lid.

== Reference controller ==

See [[M0dularis+]]

== Interconnections ==

=== Controller: Application Socket ===

The controller PCB must use a 2x4 or 2x8 micromatch socket.

Example controller PCB (on top: application socket, on left: frontend socket):

[[File:M0dularisM Plus.jpg|300px|thumb|center|M0dularis+ Controller with µBCU]]

Pinout:

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND / KNX GND
|1
|2
| style="background-color: grey;"|GND from 24V Input
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: indianred;"|24V from 24V Input
|-
| style="background-color: yellow;"|SDA / IO0
|5
|6
| style="background-color: limegreen;"|IO3
|-
| style="background-color: yellow;"|SCL / IO1
|7
|8
| style="background-color: lightblue;"|ExtINT Application / IO2
|-
| style="background-color: mediumseagreen;"|Option0
|9
|10
| style="background-color: mediumseagreen;"|Option7
|-
| style="background-color: mediumseagreen;"|Option1
|11
|12
| style="background-color: mediumseagreen;"|Option6
|-
| style="background-color: mediumseagreen;"|Option2
|13
|14
| style="background-color: mediumseagreen;"|Option5
|-
| style="background-color: mediumseagreen;"|Option3
|15
|16
| style="background-color: mediumseagreen;"|Option4
|}

Remarks:

* '''Option0..7''': Freely selectable, depends on the controller. If not used at all: Stick to Pin1..8 and apply a 2x4 micromatch socket only.
* '''IO0..IO3''': Freely selectable, but:
**'''SDA/SCL''': This pins must have I2C capabilities
**'''ExtINT''': This pin must have interrupt capabilities
*'''24V Input''': 24V DC supply voltage from separate socket with white/yellow wire pair
*'''GND''': relative to VCC
*'''GND 24V''': relative to 24V DC Input
*'''VCC''': 3.3V or 5V, depending on the controller, if possible, selectable with jumper/solderjumper

=== Controller: Frontend Application Socket ===

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND
|1
|2
| style="background-color: yellow;"|SDA
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: yellow;"|SCL
|-
|unused/reserve
|5
|6
| style="background-color: lightblue;"|ExtINT Frontend
|}

Remarks:

* See Application Connector above

=== Controller: Extension Socket ===

[[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) not yet fully specified. work in progress

KONNEKTING Modular DIN RAIL Device Specification

2021-02-15T09:39:51Z

Konnekting:

== Din Rail Case ==

Manufacturer: https://www.okw.com

Part: Railtec B - 4 TE / https://www.okw.com/de/Railtec-B/B6503121.htm?var=c9f11140-cb2e-11e3-89f9-00163e72470b

The case can be ordered directly from OKW. But keep in mind that you should reach 100EUR netto to overcome additional shipping fees.
Your can also order the case at buerklin.com without the 100EUR limit. Just search for the OKW part-number with the search on the Bürklin web page.

Example:

[[File:DFF4.1 1.0.png|300px|thumb|center]]

== BOM ==

{| border="1" style="border-collapse:collapse"
! scope="col"|Picture
! scope="col"|Description
! scope="col"|OKW part number
! scope="col"|Bürklin order number
! scope="col"|OKW link
! scope="col"|Bürklin link
|-
|[[File:OKW-B6503121.png|200px|thumb|left|B6503121]]
|RAILTEC B, 4 MODULES, VERS. VI (1 base part with locking clip, 1 top part)
|B6503121
|30H2334
|https://www.okw.com/en/Railtec-B/B6503121.htm
|https://www.buerklin.com/de/RAILTEC-B-4-Module-Ausf-VI/p/30H2334
|-
|n/a
|KNX COVER, FLAT
|B6607145
|30H2433
|https://www.okw.com/en/Railtec-B/B6607145.htm
|https://www.buerklin.com/de/Abdeckung-KNX-flach/p/30H2433
|-
|n/a
|TERMINAL GUARDS, FLAT (Perforated, for block 5.0)
|B6607143
|30H2432
|https://www.okw.com/en/Railtec-B/B6607143.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2432
|-
|n/a
|TERMINAL GUARDS, FLAT (With ventilation slots)
|B6607141
|30H2430
|https://www.okw.com/en/Railtec-B/B6607141.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2430
|-
|n/a
|TERMINAL GUARDS, FLAT (Closed)
|B6607140
|30H2429
|https://www.okw.com/en/Railtec-B/B6607140.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2429
|-
|n/a
|FRONT PANEL, 4 MODULES, VERS. VI
|B6603180
|30H2402
|https://www.okw.com/en/Railtec-B/B6603180.htm
|https://www.buerklin.com/de/Frontplatte-4-Module-Ausf-VI/p/30H2402
|}

== Mechanical ==

The OKW case allows PCBs on 3 levels. From top to bottom we name them:

* Frontend PCB
* Controller PCB
* Application PCB

The PCBs are scred together with M3 hex-spacers. Here's a mechanical overview (from top to bottom):

[2mm space to outer case edge]
[1,6mm inner OKW Railtec cover]
[6,1mm free space to inner OKW Railtec lid] → top-edge inner lid to top-edge frontend pcb = 7,7mm
['''1,6mm Frontend PCB''']
[15mm M3 hex spacer]
['''1,6mm Controller PCB''']
[18mm M3 hex spacer]
['''1,6mm Application PCB''']
[3,5mm screw pin on black OKW Railtec base plate]

Recommendation for tactile push button Frontend PCB: 9,5mm height.

{|
|'''THT'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/3/index.html?ACTION=3&LA=2&ARTICLE=27893&GROUPID=7587&artnr=TASTER+3301B&SEARCH=%252A
|-
|'''SMD'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-9319/3/index.html?ACTION=3&LA=2&ARTICLE=44518&GROUPID=7587&artnr=TASTER+9319&SEARCH=%252A
|}

5mm LED PCB spacer for 3mm THT LEDs: http://www.reichelt.de/Zubehoer-fuer-LEDs/MEN-2818-3045/3/index.html?ACTION=3&LA=446&ARTICLE=62820&GROUPID=3044&artnr=MEN+2818.3045&SEARCH=led%2Babstandshalter

→ the LED protrudes about 2mm out of the cover lid.
→ Use 4mm led spacer to reduce this to 1mm

You can use a plain PCB with silkscreen printing and wholes to create a nice looking cover, that sits on the OKW Railtec lid. This will also fill the remaining space to the outer case edge on top of the OKW lid.

== Reference controller ==

See [[M0dularis+]]

== Interconnections ==

=== Controller: Application Socket ===

The controller PCB must use a 2x4 or 2x8 micromatch socket.

Example controller PCB (on top: application socket, on left: frontend socket):

[[File:M0dularisM Plus.jpg|300px|thumb|center|M0dularis+ Controller with µBCU]]

Pinout:

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND / KNX GND
|1
|2
| style="background-color: grey;"|GND from 24V Input
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: indianred;"|24V from 24V Input
|-
| style="background-color: yellow;"|SDA / IO0
|5
|6
| style="background-color: limegreen;"|IO3
|-
| style="background-color: yellow;"|SCL / IO1
|7
|8
| style="background-color: lightblue;"|ExtINT Application / IO2
|-
| style="background-color: mediumseagreen;"|Option0
|9
|10
| style="background-color: mediumseagreen;"|Option7
|-
| style="background-color: mediumseagreen;"|Option1
|11
|12
| style="background-color: mediumseagreen;"|Option6
|-
| style="background-color: mediumseagreen;"|Option2
|13
|14
| style="background-color: mediumseagreen;"|Option5
|-
| style="background-color: mediumseagreen;"|Option3
|15
|16
| style="background-color: mediumseagreen;"|Option4
|}

Remarks:

* '''Option0..7''': Freely selectable, depends on the controller. If not used at all: Stick to Pin1..8 and apply a 2x4 micromatch socket only.
* '''IO0..IO3''': Freely selectable, but:
**'''SDA/SCL''': This pins must have I2C capabilities
**'''ExtINT''': This pin must have interrupt capabilities
*'''24V Input''': 24V DC supply voltage from separate socket with white/yellow wire pair
*'''GND''': relative to VCC
*'''GND 24V''': relative to 24V DC Input
*'''VCC''': 3.3V or 5V, depending on the controller, if possible, selectable with jumper/solderjumper

=== Controller: Frontend Application Socket ===

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND
|1
|2
| style="background-color: yellow;"|SDA
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: yellow;"|SCL
|-
|unused/reserve
|5
|6
| style="background-color: lightblue;"|ExtINT Frontend
|}

Remarks:

* See Application Connector above

=== Controller: Extension Socket ===

[[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) not yet fully specified. work in progress

File:OKW-B6503121.png

2021-02-15T09:38:33Z

Konnekting: OKW-B6503121

== Summary ==
OKW-B6503121
== Licensing ==
{{CopyrightByKONNEKTING}}

KONNEKTING Modular DIN RAIL Device Specification

2021-02-15T09:36:03Z

Konnekting: /* BOM */

== Din Rail Case ==

Manufacturer: https://www.okw.com

Part: Railtec B - 4 TE / https://www.okw.com/de/Railtec-B/B6503121.htm?var=c9f11140-cb2e-11e3-89f9-00163e72470b

The case can be ordered directly from OKW. But keep in mind that you should reach 100EUR netto to overcome additional shipping fees.
Your can also order the case at buerklin.com without the 100EUR limit. Just search for the OKW part-number with the search on the Bürklin web page.

Example:

[[File:DFF4.1 1.0.png|300px|thumb|center]]

== BOM ==

{| border="1" style="border-collapse:collapse"
! scope="col"|Picture
! scope="col"|Description
! scope="col"|OKW part number
! scope="col"|Bürklin order number
! scope="col"|OKW link
! scope="col"|Bürklin link
|-
|n/a
|RAILTEC B, 4 MODULES, VERS. VI (1 base part with locking clip, 1 top part)
|B6503121
|30H2334
|https://www.okw.com/en/Railtec-B/B6503121.htm
|https://www.buerklin.com/de/RAILTEC-B-4-Module-Ausf-VI/p/30H2334
|-
|n/a
|KNX COVER, FLAT
|B6607145
|30H2433
|https://www.okw.com/en/Railtec-B/B6607145.htm
|https://www.buerklin.com/de/Abdeckung-KNX-flach/p/30H2433
|-
|n/a
|TERMINAL GUARDS, FLAT (Perforated, for block 5.0)
|B6607143
|30H2432
|https://www.okw.com/en/Railtec-B/B6607143.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2432
|-
|n/a
|TERMINAL GUARDS, FLAT (With ventilation slots)
|B6607141
|30H2430
|https://www.okw.com/en/Railtec-B/B6607141.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2430
|-
|n/a
|TERMINAL GUARDS, FLAT (Closed)
|B6607140
|30H2429
|https://www.okw.com/en/Railtec-B/B6607140.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2429
|-
|n/a
|FRONT PANEL, 4 MODULES, VERS. VI
|B6603180
|30H2402
|https://www.okw.com/en/Railtec-B/B6603180.htm
|https://www.buerklin.com/de/Frontplatte-4-Module-Ausf-VI/p/30H2402
|}

== Mechanical ==

The OKW case allows PCBs on 3 levels. From top to bottom we name them:

* Frontend PCB
* Controller PCB
* Application PCB

The PCBs are scred together with M3 hex-spacers. Here's a mechanical overview (from top to bottom):

[2mm space to outer case edge]
[1,6mm inner OKW Railtec cover]
[6,1mm free space to inner OKW Railtec lid] → top-edge inner lid to top-edge frontend pcb = 7,7mm
['''1,6mm Frontend PCB''']
[15mm M3 hex spacer]
['''1,6mm Controller PCB''']
[18mm M3 hex spacer]
['''1,6mm Application PCB''']
[3,5mm screw pin on black OKW Railtec base plate]

Recommendation for tactile push button Frontend PCB: 9,5mm height.

{|
|'''THT'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/3/index.html?ACTION=3&LA=2&ARTICLE=27893&GROUPID=7587&artnr=TASTER+3301B&SEARCH=%252A
|-
|'''SMD'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-9319/3/index.html?ACTION=3&LA=2&ARTICLE=44518&GROUPID=7587&artnr=TASTER+9319&SEARCH=%252A
|}

5mm LED PCB spacer for 3mm THT LEDs: http://www.reichelt.de/Zubehoer-fuer-LEDs/MEN-2818-3045/3/index.html?ACTION=3&LA=446&ARTICLE=62820&GROUPID=3044&artnr=MEN+2818.3045&SEARCH=led%2Babstandshalter

→ the LED protrudes about 2mm out of the cover lid.
→ Use 4mm led spacer to reduce this to 1mm

You can use a plain PCB with silkscreen printing and wholes to create a nice looking cover, that sits on the OKW Railtec lid. This will also fill the remaining space to the outer case edge on top of the OKW lid.

== Reference controller ==

See [[M0dularis+]]

== Interconnections ==

=== Controller: Application Socket ===

The controller PCB must use a 2x4 or 2x8 micromatch socket.

Example controller PCB (on top: application socket, on left: frontend socket):

[[File:M0dularisM Plus.jpg|300px|thumb|center|M0dularis+ Controller with µBCU]]

Pinout:

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND / KNX GND
|1
|2
| style="background-color: grey;"|GND from 24V Input
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: indianred;"|24V from 24V Input
|-
| style="background-color: yellow;"|SDA / IO0
|5
|6
| style="background-color: limegreen;"|IO3
|-
| style="background-color: yellow;"|SCL / IO1
|7
|8
| style="background-color: lightblue;"|ExtINT Application / IO2
|-
| style="background-color: mediumseagreen;"|Option0
|9
|10
| style="background-color: mediumseagreen;"|Option7
|-
| style="background-color: mediumseagreen;"|Option1
|11
|12
| style="background-color: mediumseagreen;"|Option6
|-
| style="background-color: mediumseagreen;"|Option2
|13
|14
| style="background-color: mediumseagreen;"|Option5
|-
| style="background-color: mediumseagreen;"|Option3
|15
|16
| style="background-color: mediumseagreen;"|Option4
|}

Remarks:

* '''Option0..7''': Freely selectable, depends on the controller. If not used at all: Stick to Pin1..8 and apply a 2x4 micromatch socket only.
* '''IO0..IO3''': Freely selectable, but:
**'''SDA/SCL''': This pins must have I2C capabilities
**'''ExtINT''': This pin must have interrupt capabilities
*'''24V Input''': 24V DC supply voltage from separate socket with white/yellow wire pair
*'''GND''': relative to VCC
*'''GND 24V''': relative to 24V DC Input
*'''VCC''': 3.3V or 5V, depending on the controller, if possible, selectable with jumper/solderjumper

=== Controller: Frontend Application Socket ===

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND
|1
|2
| style="background-color: yellow;"|SDA
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: yellow;"|SCL
|-
|unused/reserve
|5
|6
| style="background-color: lightblue;"|ExtINT Frontend
|}

Remarks:

* See Application Connector above

=== Controller: Extension Socket ===

[[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) not yet fully specified. work in progress

KONNEKTING Modular DIN RAIL Device Specification

2021-02-15T09:35:12Z

Konnekting:

== Din Rail Case ==

Manufacturer: https://www.okw.com

Part: Railtec B - 4 TE / https://www.okw.com/de/Railtec-B/B6503121.htm?var=c9f11140-cb2e-11e3-89f9-00163e72470b

The case can be ordered directly from OKW. But keep in mind that you should reach 100EUR netto to overcome additional shipping fees.
Your can also order the case at buerklin.com without the 100EUR limit. Just search for the OKW part-number with the search on the Bürklin web page.

Example:

[[File:DFF4.1 1.0.png|300px|thumb|center]]

== BOM ==

{| border="1" style="border-collapse:collapse"
! scope="col"|Description
! scope="col"|OKW part number
! scope="col"|Bürklin order number
! scope="col"|OKW link
! scope="col"|Bürklin link
|-
|RAILTEC B, 4 MODULES, VERS. VI (1 base part with locking clip, 1 top part)
|B6503121
|30H2334
|https://www.okw.com/en/Railtec-B/B6503121.htm
|https://www.buerklin.com/de/RAILTEC-B-4-Module-Ausf-VI/p/30H2334
|-
|KNX COVER, FLAT
|B6607145
|30H2433
|https://www.okw.com/en/Railtec-B/B6607145.htm
|https://www.buerklin.com/de/Abdeckung-KNX-flach/p/30H2433
|-
|TERMINAL GUARDS, FLAT (Perforated, for block 5.0)
|B6607143
|30H2432
|https://www.okw.com/en/Railtec-B/B6607143.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2432
|-
|TERMINAL GUARDS, FLAT (With ventilation slots)
|B6607141
|30H2430
|https://www.okw.com/en/Railtec-B/B6607141.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2430
|-
|TERMINAL GUARDS, FLAT (Closed)
|B6607140
|30H2429
|https://www.okw.com/en/Railtec-B/B6607140.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2429
|-
|FRONT PANEL, 4 MODULES, VERS. VI
|B6603180
|30H2402
|https://www.okw.com/en/Railtec-B/B6603180.htm
|https://www.buerklin.com/de/Frontplatte-4-Module-Ausf-VI/p/30H2402
|}

== Mechanical ==

The OKW case allows PCBs on 3 levels. From top to bottom we name them:

* Frontend PCB
* Controller PCB
* Application PCB

The PCBs are scred together with M3 hex-spacers. Here's a mechanical overview (from top to bottom):

[2mm space to outer case edge]
[1,6mm inner OKW Railtec cover]
[6,1mm free space to inner OKW Railtec lid] → top-edge inner lid to top-edge frontend pcb = 7,7mm
['''1,6mm Frontend PCB''']
[15mm M3 hex spacer]
['''1,6mm Controller PCB''']
[18mm M3 hex spacer]
['''1,6mm Application PCB''']
[3,5mm screw pin on black OKW Railtec base plate]

Recommendation for tactile push button Frontend PCB: 9,5mm height.

{|
|'''THT'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/3/index.html?ACTION=3&LA=2&ARTICLE=27893&GROUPID=7587&artnr=TASTER+3301B&SEARCH=%252A
|-
|'''SMD'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-9319/3/index.html?ACTION=3&LA=2&ARTICLE=44518&GROUPID=7587&artnr=TASTER+9319&SEARCH=%252A
|}

5mm LED PCB spacer for 3mm THT LEDs: http://www.reichelt.de/Zubehoer-fuer-LEDs/MEN-2818-3045/3/index.html?ACTION=3&LA=446&ARTICLE=62820&GROUPID=3044&artnr=MEN+2818.3045&SEARCH=led%2Babstandshalter

→ the LED protrudes about 2mm out of the cover lid.
→ Use 4mm led spacer to reduce this to 1mm

You can use a plain PCB with silkscreen printing and wholes to create a nice looking cover, that sits on the OKW Railtec lid. This will also fill the remaining space to the outer case edge on top of the OKW lid.

== Reference controller ==

See [[M0dularis+]]

== Interconnections ==

=== Controller: Application Socket ===

The controller PCB must use a 2x4 or 2x8 micromatch socket.

Example controller PCB (on top: application socket, on left: frontend socket):

[[File:M0dularisM Plus.jpg|300px|thumb|center|M0dularis+ Controller with µBCU]]

Pinout:

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND / KNX GND
|1
|2
| style="background-color: grey;"|GND from 24V Input
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: indianred;"|24V from 24V Input
|-
| style="background-color: yellow;"|SDA / IO0
|5
|6
| style="background-color: limegreen;"|IO3
|-
| style="background-color: yellow;"|SCL / IO1
|7
|8
| style="background-color: lightblue;"|ExtINT Application / IO2
|-
| style="background-color: mediumseagreen;"|Option0
|9
|10
| style="background-color: mediumseagreen;"|Option7
|-
| style="background-color: mediumseagreen;"|Option1
|11
|12
| style="background-color: mediumseagreen;"|Option6
|-
| style="background-color: mediumseagreen;"|Option2
|13
|14
| style="background-color: mediumseagreen;"|Option5
|-
| style="background-color: mediumseagreen;"|Option3
|15
|16
| style="background-color: mediumseagreen;"|Option4
|}

Remarks:

* '''Option0..7''': Freely selectable, depends on the controller. If not used at all: Stick to Pin1..8 and apply a 2x4 micromatch socket only.
* '''IO0..IO3''': Freely selectable, but:
**'''SDA/SCL''': This pins must have I2C capabilities
**'''ExtINT''': This pin must have interrupt capabilities
*'''24V Input''': 24V DC supply voltage from separate socket with white/yellow wire pair
*'''GND''': relative to VCC
*'''GND 24V''': relative to 24V DC Input
*'''VCC''': 3.3V or 5V, depending on the controller, if possible, selectable with jumper/solderjumper

=== Controller: Frontend Application Socket ===

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND
|1
|2
| style="background-color: yellow;"|SDA
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: yellow;"|SCL
|-
|unused/reserve
|5
|6
| style="background-color: lightblue;"|ExtINT Frontend
|}

Remarks:

* See Application Connector above

=== Controller: Extension Socket ===

[[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) not yet fully specified. work in progress

KONNEKTING Modular DIN RAIL Device Specification

2021-02-15T09:00:27Z

Konnekting: /* BOM */

== Din Rail Case ==

Manufacturer: https://www.okw.com

Part: Railtec B - 4 TE / https://www.okw.com/de/Railtec-B/B6503121.htm?var=c9f11140-cb2e-11e3-89f9-00163e72470b

The case can be ordered directly from OKW. But keep in mind that you should reach 100EUR netto to overcome additional shipping fees.
Your can also order the case at buerklin.com without the 100EUR limit. Just search for the OKW part-number with the search on the Bürklin web page.

Example:

[[File:DFF4.1 1.0.png|300px|thumb|center]]

== BOM ==

{| border="1" style="border-collapse:collapse"
! scope="col"|Description
! scope="col"|OKW part number
! scope="col"|Bürklin order number
! scope="col"|OKW link
! scope="col"|Bürklin link
|-
|RAILTEC B, 4 MODULES, VERS. VI
|B6503121
|30H2334
|https://www.okw.com/en/Railtec-B/B6503121.htm
|https://www.buerklin.com/de/RAILTEC-B-4-Module-Ausf-VI/p/30H2334
|-
|KNX COVER, FLAT
|B6607145
|30H2433
|https://www.okw.com/en/Railtec-B/B6607145.htm
|https://www.buerklin.com/de/Abdeckung-KNX-flach/p/30H2433
|-
|TERMINAL GUARDS, FLAT (Perforated, for block 5.0)
|B6607143
|30H2432
|https://www.okw.com/en/Railtec-B/B6607143.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2432
|-
|TERMINAL GUARDS, FLAT (With ventilation slots)
|B6607141
|30H2430
|https://www.okw.com/en/Railtec-B/B6607141.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2430
|-
|TERMINAL GUARDS, FLAT (Closed)
|B6607140
|30H2429
|https://www.okw.com/en/Railtec-B/B6607140.htm
|https://www.buerklin.com/de/Klemmenabdeckung-flach/p/30H2429
|-
|FRONT PANEL, 4 MODULES, VERS. VI
|B6603180
|30H2402
|https://www.okw.com/en/Railtec-B/B6603180.htm
|https://www.buerklin.com/de/Frontplatte-4-Module-Ausf-VI/p/30H2402
|}

== Mechanical ==

The OKW case allows PCBs on 3 levels. From top to bottom we name them:

* Frontend PCB
* Controller PCB
* Application PCB

The PCBs are scred together with M3 hex-spacers. Here's a mechanical overview (from top to bottom):

[2mm space to outer case edge]
[1,6mm inner OKW Railtec cover]
[6,1mm free space to inner OKW Railtec lid] → top-edge inner lid to top-edge frontend pcb = 7,7mm
['''1,6mm Frontend PCB''']
[15mm M3 hex spacer]
['''1,6mm Controller PCB''']
[18mm M3 hex spacer]
['''1,6mm Application PCB''']
[3,5mm screw pin on black OKW Railtec base plate]

Recommendation for tactile push button Frontend PCB: 9,5mm height.

{|
|'''THT'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-3301B/3/index.html?ACTION=3&LA=2&ARTICLE=27893&GROUPID=7587&artnr=TASTER+3301B&SEARCH=%252A
|-
|'''SMD'''
|http://www.reichelt.de/Kurzhubtaster/TASTER-9319/3/index.html?ACTION=3&LA=2&ARTICLE=44518&GROUPID=7587&artnr=TASTER+9319&SEARCH=%252A
|}

5mm LED PCB spacer for 3mm THT LEDs: http://www.reichelt.de/Zubehoer-fuer-LEDs/MEN-2818-3045/3/index.html?ACTION=3&LA=446&ARTICLE=62820&GROUPID=3044&artnr=MEN+2818.3045&SEARCH=led%2Babstandshalter

→ the LED protrudes about 2mm out of the cover lid.
→ Use 4mm led spacer to reduce this to 1mm

You can use a plain PCB with silkscreen printing and wholes to create a nice looking cover, that sits on the OKW Railtec lid. This will also fill the remaining space to the outer case edge on top of the OKW lid.

== Reference controller ==

See [[M0dularis+]]

== Interconnections ==

=== Controller: Application Socket ===

The controller PCB must use a 2x4 or 2x8 micromatch socket.

Example controller PCB (on top: application socket, on left: frontend socket):

[[File:M0dularisM Plus.jpg|300px|thumb|center|M0dularis+ Controller with µBCU]]

Pinout:

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND / KNX GND
|1
|2
| style="background-color: grey;"|GND from 24V Input
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: indianred;"|24V from 24V Input
|-
| style="background-color: yellow;"|SDA / IO0
|5
|6
| style="background-color: limegreen;"|IO3
|-
| style="background-color: yellow;"|SCL / IO1
|7
|8
| style="background-color: lightblue;"|ExtINT Application / IO2
|-
| style="background-color: mediumseagreen;"|Option0
|9
|10
| style="background-color: mediumseagreen;"|Option7
|-
| style="background-color: mediumseagreen;"|Option1
|11
|12
| style="background-color: mediumseagreen;"|Option6
|-
| style="background-color: mediumseagreen;"|Option2
|13
|14
| style="background-color: mediumseagreen;"|Option5
|-
| style="background-color: mediumseagreen;"|Option3
|15
|16
| style="background-color: mediumseagreen;"|Option4
|}

Remarks:

* '''Option0..7''': Freely selectable, depends on the controller. If not used at all: Stick to Pin1..8 and apply a 2x4 micromatch socket only.
* '''IO0..IO3''': Freely selectable, but:
**'''SDA/SCL''': This pins must have I2C capabilities
**'''ExtINT''': This pin must have interrupt capabilities
*'''24V Input''': 24V DC supply voltage from separate socket with white/yellow wire pair
*'''GND''': relative to VCC
*'''GND 24V''': relative to 24V DC Input
*'''VCC''': 3.3V or 5V, depending on the controller, if possible, selectable with jumper/solderjumper

=== Controller: Frontend Application Socket ===

{| border="1" style="text-align:center; border-collapse:collapse"
! scope="col"|Description
! scope="col"|Pin
! scope="col"|Pin
! scope="col"|Description
|-
| style="background-color: grey;"|GND
|1
|2
| style="background-color: yellow;"|SDA
|-
| style="background-color: red;"|VCC
|3
|4
| style="background-color: yellow;"|SCL
|-
|unused/reserve
|5
|6
| style="background-color: lightblue;"|ExtINT Frontend
|}

Remarks:

* See Application Connector above

=== Controller: Extension Socket ===

[[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) not yet fully specified. work in progress