KONNEKTING Wiki - User contributions [en]

MicroBCU2

2021-02-10T12:16:17Z

SirSydom: /* User Documentation */

MicroBCU2

2021-02-10T12:16:00Z

SirSydom:

Konnekting Rail System XL

2021-02-05T20:50:09Z

SirSydom:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Konnekting Rail System XL
|-
! colspan="2"|[[File:KRS-XL DIM-24CVLED insights.jpeg|300px|thumb|center]]
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| 1. device realized / Ready to use
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]] / [[SiemensBCU]]
|-
! Repository
| [https://gitlab.com/knx-makerstuff/knx-rail-system-xl On GitLab]
|}

== Description ==

The '''K'''onnekting '''R'''ail '''S'''ystem '''XL''' (KRS-XL) is a bunch of modular hard- and software for building devices in big DIN Rail Casings. It is designed for applications with a high number of channels.

== Design ideas and principles ==

The itention for developing this system was to reduce the costs of the devices. Because Bus connection, case, microcontroller are often the most expensive parts, a high number of channels very effectively reduces the cost per channel.
So the system is designed for use in 6, 9 and 12 TE DIN-Rail cases.

Another important design priciple was the use of prebuild componentes. Not only to reduce developement complexity and enable persons with limited soldering skills and tools to build it, but also to make it easier to repair devices in the future.
On the Controller Board three prebuild components which are generally availible are used: a pluggable microcontroller board, a pluggable Bus interface and a display module.

Modularity was added later in the developement phase, but was a logical step. The Controller Board is designed to be used in all devices within this system. It contains not only the microcontroller and bus interface, but also the user interface (frontend). To make it possible to handle high channel numbers and also to have one common hardware, a 320x240 px 2.2" Display is used as UI, operated by 4 buttons.
To improve supply quality, it is not only possible to use the [[MicroBCU]], but also the [[SiemensBCU]]. Unfortunately, the [[SiemensBCU]] comes with some limitations regarding power consumption.
To fit the needs for every device regarding power supply and galvanic insulation there is a wide range of assembly variants and solder jumper options.

Because of the need to have the Controller Board at the top (because of the UI) and the fact that the pluggable component need some space, I choose a two PCB design - the big application PCB at the bottom and a the Controller Board at the top. With the ApraRail DB DIN Rail casing series, KRS-XL comes with quite robust, widely availible (Reichelt, Amazon) casings.
Unfortunately in this casings there is no possibilty to connect to the top PCB - so KNX and if neccessary DC power have to be connected to the application PCB which is connected to the Controller Board.

To enable easy replacement, repair or improvement, two-part conectors are used. They can be unplugged from the device an remain in the cabinet without the danger of short circuits, and the cany easily plugged in again.
To achieve this, Phoenix combicon MSTB with 5.08 pitch (to enable bread board use at application PCB) are used. They are avaiblibe up to 16 amps and can also be used with 230V.

Because there is no possibility to have a standard KNX connector with the ApraRAIL DB casings, the Combicon connector is also used of standard for the KNX connection. Plugs with two wire per pin are availibe, so the devices can be chained.

== Distribution concept ==

I will not sell kits or even pre soldered kits. The System is designed for hobbyists that can and want to build it on their own (to save money, or just because they can). The needed soldering skills are low due to the usage of only THT and big SMD components.

Almost all parts can be purchased at standard shops with normal shipping costs. For special parts and the PCBs I will maybe organize bulk orders.

== Controller Board CB6-9-12 ==
=== Schematic ===

[https://wiki.konnekting.de/images/d/d3/KRS-XL_CB6-9-12.V01.00_schematic.pdf KRS-XL CB6-9-12 V01.00 Schematic]

=== Microcontroller Board ===

A Adafruit ItsyBitsy M0 Express Board was the almost perfect solution for the needs of KRS-XL:
* ATSAMD21 controller ("standard" controller for Konnekting) with sufficient cpu power, RAM, and FLASH
* SPI Flash to enable FOTB
* good availablity
* quality supllier
* pin compatible big brother ItsyBitsy M4 with Cortex M4 CPU available

== Devices ==

=== Roadmap ===

* [[ DIM-24CVLED.01 | DIM-24CVLED.01 - 24 channel PWM-LED Dimmer (24V DC) 9TE ]]
* 16-24 channel CC-LED Dimmer 9 or 12 TE based on Meanwell LDD
* 230V switching actuator

== Links ==
https://gitlab.com/knx-makerstuff/knx-rail-system-xl

https://knx-user-forum.de/forum/projektforen/konnekting/1449711-krs-xl-konnekting-rail-system-xl

https://knx-user-forum.de/forum/projektforen/konnekting/1412984-in-entwicklung-modulares-ger%C3%A4tekonzept-6-9-12-te

MicroBCU2

2021-01-15T11:46:56Z

SirSydom: /* User Documentation */

DIM-24CVLED.01

2020-12-04T11:56:14Z

SirSydom:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|KRS-XL 24 channel PWM-LED Dimmer (24V DC) 9TE
|-
! colspan="2"|[[File:DIM-24CVLED 01 wo case top.jpeg|300px|thumb|center]]
|-
! Short name
| DIM-24CVLED.01
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| HW: Developement Completed

SW: Working Beta, Improvements planned
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]], [[MicroBCU2]] or [[SiemensBCU]]
|-
! Device Family
| [[Konnekting Rail System XL]]
|-
! Manufacturer/Device ID
| 7337 / 100
|-
! Repository
| -
|}

== Short Description ==
This device is a 24 channel PWM dimmer for usage in e-cabinets on DIN rail.

== Software ==

== Hardware ==

== User Doc ==

== Dev Doc ==

== Build It ==

== Links ==

<gallery>
DIM-24CVLED 01 wo case front.jpeg
</gallery>

[[Category:Device/Kits]]

DIM-24CVLED.01

2020-12-04T11:55:27Z

SirSydom:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|KRS-XL 24 channel PWM-LED Dimmer (24V DC) 9TE
|-
! colspan="2"|[[File:DIM-24CVLED 01 wo case top.jpeg|300px|thumb|center]]
|-
! Short name
| DIM-24CVLED.01
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| HW: Developement Completed

SW: Working Beta, Improvements planned
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]], [[MicroBCU2]] or [[SiemensBCU]]
|-
! Device Family
| [[Konnekting Rail System XL]]
|-
! Manufacturer/Device ID
| 7337 / 100
|-
! Repository
| -
|}

== Short Description ==
This device is a 24 channel PWM dimmer for usage in e-cabinets on DIN rail.

== Software ==

== Hardware ==

== User Doc ==

== Dev Doc ==

== Build It ==

== Links ==

File:DIM-24CVLED 01 wo case front.jpeg

[[Category:Device/Kits]]

File:DIM-24CVLED 01 wo case front.jpeg

2020-12-04T11:54:33Z

SirSydom:

DIM-24CVLED.01

2020-12-04T11:53:59Z

SirSydom:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|KRS-XL 24 channel PWM-LED Dimmer (24V DC) 9TE
|-
! colspan="2"|[[File:DIM-24CVLED 01 wo case top.jpeg|300px|thumb|center]]
|-
! Short name
| DIM-24CVLED.01
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| HW: Developement Completed / SW: Working Beta, Improvements planned
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]], [[MicroBCU2]] or [[SiemensBCU]]
|-
! Device Family
| [[Konnekting Rail System XL]]
|-
! Manufacturer/Device ID
| 7337 / 100
|-
! Repository
| -
|}

== Short Description ==
This device is a 24 channel PWM dimmer for usage in e-cabinets on DIN rail.

== Software ==

== Hardware ==

== User Doc ==

== Dev Doc ==

== Build It ==

== Links ==

[[Category:Device/Kits]]

File:DIM-24CVLED 01 wo case top.jpeg

2020-12-04T11:53:31Z

SirSydom:

DIM-24CVLED.01

2020-12-04T11:49:36Z

SirSydom: Created page with "{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;" ! colspan="2"|KRS-XL 24 channel PWM-LED Dimmer (24V DC) 9TE |- ! colspan="2"..."

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|KRS-XL 24 channel PWM-LED Dimmer (24V DC) 9TE
|-
! colspan="2"|[[File:IMG 20190826 065357703.jpg|300px|thumb|center]]
|-
! Short name
| DIM-24CVLED.01
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| HW: Developement Completed / SW: Working Beta, Improvements planned
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]], [[MicroBCU2]] or [[SiemensBCU]]
|-
! Device Family
| [[Konnekting Rail System XL]]
|-
! Manufacturer/Device ID
| 7337 / 100
|-
! Repository
| -
|}

== Short Description ==
This device is a 24 channel PWM dimmer for usage in e-cabinets on DIN rail.

== Software ==

== Hardware ==

== User Doc ==

== Dev Doc ==

== Build It ==

== Links ==

[[Category:Device/Kits]]

Projects and Devices

2020-12-04T11:41:49Z

SirSydom: /* Devices/Kits */

On this page, we list all kind of KONNEKTING related projects and of course devices.

== ID Overview ==

* [https://github.com/KONNEKTING/KonnektingDocumentation/blob/master/konnekting_manufacturers.md Manufacturer ID List]
* [[Device_ID_List | Device ID List]]

== Naming Guide ==

If you look at different KNX device vendors, you will easily see, that they have a specific device name pattern. For KONNEKTING it would be good to have also a kind of device name pattern.

Recommendation so far:

* Find a "short name" for your device. For instance, if you have a LED PWM Dimmer, you could name it "LED Dimmer", and the short version could be "LEDD"
* Check if your device has channels or inputs... For instance your dimmer could have 4 channels/outputs.
* Check if the device exists in it's first, 2nd or 3rd "major version".

Combine all three things together:

LEDD4.1

LEDD --> LED Dimmer
4 --> 4 channels
. --> just a separator
1 --> 1st version

== Devices/Kits ==

Template for new pages: [[ Device/Kits Template | Device/Kits Template ]]

Completed:

* [[ Multi Interface (MI) | Multi Interface ]]
* [[ DFF4.1 | DFF4.1 - ROTO Rototronic Roof Window Actuator (Din Rail)]]
* [[ LEDD4.1 | LEDD4.1 - 4 channel LED PWM Dimmer (Din Rail)]]
* [[ EnOcean Gateway | EnOcean Gateway ]]
* [[ 16CH Binary Input | 16ch Binary Input ]]
* [[ HW1.2 | HW1.2 Beginner PCB ]]
* [[ MicroBCU | MicroBCU ]]
* [[ MicroBCU2 | MicroBCU2 ]]
* [[ UUPS | UUPS ]]
* [[ 1-Wire Gateway | 1-Wire Gateway ]]
* [[ DGC-CLDC0.01 CodeLock Door Controller ]]
* [[ EDS-WS433.01 Weatherstation for 433Mhz Sensors ]]

Not completed:

* [[ Modular LED Dimmer 1-12CH | Modular LED Dimmer 1-12CH ]]
* [[ Berker-Sensor-Einsatz (T,H,P,VOC) | Berker-Sensor-Einsatz (T,H,P,VOC) ]]
* [[ DB2.1_1.0 | DoorBell 2.1 ]]
* [[ Sliding Gate Controller for Wisniowski gates | Sliding Gate Controller for Wisniowski gates ]]

Ideas / Wishes:
* [[ SoundModule | SoundModule]]

== REG Components ==

=== Controller ===

* [[ M0dularis+ | M0dularis+ ]]

=== Applications ===

* [[ 8 Relay Bistable | 8x Relay Bistable, bus powered ]]

=== Frontends ===

* [[ Frontend 8 Buttons 8 LEDs | 8x Button + 8x LED ]]

== Konnekting Rail System XL ==

The KRS-XL is a bunch of modular hard- and software for building devices in big DIN Rail Cases - 6, 9 and 12 TE.
It is designed for high channel applications.

Read more: [[ Konnekting Rail System XL | Konnekting Rail System XL ]]

=== Devices ===

* [[ DIM-24CVLED.01 | DIM-24CVLED.01 - 24 channel PWM-LED Dimmer (24V DC) 9TE ]]

MicroBCU2

2020-12-03T13:38:47Z

SirSydom:

MicroBCU2

2020-12-03T13:02:43Z

SirSydom:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A a compact bus coupling unit for KNX building automation based on the NCN5120 knx transceiver. It serves as a power supply and UART access to KNX bus.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Weight: about 4g
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Ripple at VCC1+2: about 50mV
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===
If you want to get rid of VCC2, L2, R3, R4, R5, C11 and C111 are not needed. Close J2 in that case.

To change VCC2, change R4 and R5 according the NCN5120 dataheet. When VCC2 is greater than 10V, C11 must be changed so that the voltage rating matches or exceeds VCC2 (e.g. when VCC2 = 12V, use a 16V MLCC)

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===
[https://wiki.konnekting.de/images/3/33/MicroBCU_Schematic_V00.20.pdf Schematic V00.20]

=== KiCad ===

== Developer Documentation ==
=== Version history ===
*V00.11 - first prototype series
*V00.20 - second prototype series

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://knx-user-forum.de/forum/projektforen/konnekting/1575881-sammelbestellung-microbcu2-knx-transceiver-für-ardunio-raspberry-co 1. Sammelbestellung im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[https://gitlab.com/SirSydom/knx_microbcu2 MicroBCU2 on GitLab]

[[Category:Device/Kits]]

Konnekting Rail System XL

2020-12-02T11:07:55Z

SirSydom: /* Controller Board CB6-9-12 */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Konnekting Rail System XL
|-
! colspan="2"|[[File:KRS-XL DIM-24CVLED insights.jpeg|300px|thumb|center]]
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| 1. device realized / Ready to use
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]] / [[SiemensBCU]]
|-
! Repository
| [https://gitlab.com/SirSydom/konnekting_common On GitLab]
|}

== Description ==

The '''K'''onnekting '''R'''ail '''S'''ystem '''XL''' (KRS-XL) is a bunch of modular hard- and software for building devices in big DIN Rail Casings. It is designed for applications with a high number of channels.

== Design ideas and principles ==

The itention for developing this system was to reduce the costs of the devices. Because Bus connection, case, microcontroller are often the most expensive parts, a high number of channels very effectively reduces the cost per channel.
So the system is designed for use in 6, 9 and 12 TE DIN-Rail cases.

Another important design priciple was the use of prebuild componentes. Not only to reduce developement complexity and enable persons with limited soldering skills and tools to build it, but also to make it easier to repair devices in the future.
On the Controller Board three prebuild components which are generally availible are used: a pluggable microcontroller board, a pluggable Bus interface and a display module.

Modularity was added later in the developement phase, but was a logical step. The Controller Board is designed to be used in all devices within this system. It contains not only the microcontroller and bus interface, but also the user interface (frontend). To make it possible to handle high channel numbers and also to have one common hardware, a 320x240 px 2.2" Display is used as UI, operated by 4 buttons.
To improve supply quality, it is not only possible to use the [[MicroBCU]], but also the [[SiemensBCU]]. Unfortunately, the [[SiemensBCU]] comes with some limitations regarding power consumption.
To fit the needs for every device regarding power supply and galvanic insulation there is a wide range of assembly variants and solder jumper options.

Because of the need to have the Controller Board at the top (because of the UI) and the fact that the pluggable component need some space, I choose a two PCB design - the big application PCB at the bottom and a the Controller Board at the top. With the ApraRail DB DIN Rail casing series, KRS-XL comes with quite robust, widely availible (Reichelt, Amazon) casings.
Unfortunately in this casings there is no possibilty to connect to the top PCB - so KNX and if neccessary DC power have to be connected to the application PCB which is connected to the Controller Board.

To enable easy replacement, repair or improvement, two-part conectors are used. They can be unplugged from the device an remain in the cabinet without the danger of short circuits, and the cany easily plugged in again.
To achieve this, Phoenix combicon MSTB with 5.08 pitch (to enable bread board use at application PCB) are used. They are avaiblibe up to 16 amps and can also be used with 230V.

Because there is no possibility to have a standard KNX connector with the ApraRAIL DB casings, the Combicon connector is also used of standard for the KNX connection. Plugs with two wire per pin are availibe, so the devices can be chained.

== Distribution concept ==

I will not sell kits or even pre soldered kits. The System is designed for hobbyists that can and want to build it on their own (to save money, or just because they can). The needed soldering skills are low due to the usage of only THT and big SMD components.

Almost all parts can be purchased at standard shops with normal shipping costs. For special parts and the PCBs I will maybe organize bulk orders.

== Controller Board CB6-9-12 ==
=== Schematic ===

[https://wiki.konnekting.de/images/d/d3/KRS-XL_CB6-9-12.V01.00_schematic.pdf KRS-XL CB6-9-12 V01.00 Schematic]

=== Microcontroller Board ===

A Adafruit ItsyBitsy M0 Express Board was the almost perfect solution for the needs of KRS-XL:
* ATSAMD21 controller ("standard" controller for Konnekting) with sufficient cpu power, RAM, and FLASH
* SPI Flash to enable FOTB
* good availablity
* quality supllier
* pin compatible big brother ItsyBitsy M4 with Cortex M4 CPU available

== Devices ==

=== Roadmap ===

* [[ DIM-24CVLED.01 | DIM-24CVLED.01 - 24 channel PWM-LED Dimmer (24V DC) 9TE ]]
* 16-24 channel CC-LED Dimmer 9 or 12 TE based on Meanwell LDD
* 230V switching actuator

== Links ==
https://knx-user-forum.de/forum/projektforen/konnekting/1449711-krs-xl-konnekting-rail-system-xl

https://knx-user-forum.de/forum/projektforen/konnekting/1412984-in-entwicklung-modulares-ger%C3%A4tekonzept-6-9-12-te

File:KRS-XL CB6-9-12.V01.00 schematic.pdf

2020-12-02T11:06:28Z

MicroBCU2

2020-12-01T07:44:26Z

SirSydom: /* Links */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A a compact bus coupling unit for KNX building automation based on the NCN5120 knx transceiver. It serves as a power supply and UART access to KNX bus.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Ripple at VCC1+2: about 50mV
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===
If you want to get rid of VCC2, L2, R3, R4, R5, C11 and C111 are not needed. Close J2 in that case.

To change VCC2, change R4 and R5 according the NCN5120 dataheet. When VCC2 is greater than 10V, C11 must be changed so that the voltage rating matches or exceeds VCC2 (e.g. when VCC2 = 12V, use a 16V MLCC)

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===
[https://wiki.konnekting.de/images/3/33/MicroBCU_Schematic_V00.20.pdf Schematic V00.20]

=== KiCad ===

== Developer Documentation ==
=== Version history ===
*V00.11 - first prototype series
*V00.20 - second prototype series

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://knx-user-forum.de/forum/projektforen/konnekting/1575881-sammelbestellung-microbcu2-knx-transceiver-für-ardunio-raspberry-co 1. Sammelbestellung im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[https://gitlab.com/SirSydom/knx_microbcu2 MicroBCU2 on GitLab]

[[Category:Device/Kits]]

MicroBCU2

2020-12-01T07:22:33Z

SirSydom: /* Description */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A a compact bus coupling unit for KNX building automation based on the NCN5120 knx transceiver. It serves as a power supply and UART access to KNX bus.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Ripple at VCC1+2: about 50mV
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===
If you want to get rid of VCC2, L2, R3, R4, R5, C11 and C111 are not needed. Close J2 in that case.

To change VCC2, change R4 and R5 according the NCN5120 dataheet. When VCC2 is greater than 10V, C11 must be changed so that the voltage rating matches or exceeds VCC2 (e.g. when VCC2 = 12V, use a 16V MLCC)

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===
[https://wiki.konnekting.de/images/3/33/MicroBCU_Schematic_V00.20.pdf Schematic V00.20]

=== KiCad ===

== Developer Documentation ==
=== Version history ===
*V00.11 - first prototype series
*V00.20 - second prototype series

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[https://gitlab.com/SirSydom/knx_microbcu2 MicroBCU2 on GitLab]

[[Category:Device/Kits]]

MicroBCU2

2020-11-30T21:24:03Z

SirSydom: /* Hardware */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A Bus Coupler Unit (BCU) / KNX Transveiver which supplies the connected device with power from KNX Bus and provides a bus interface at OSI Layer 2.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Ripple at VCC1+2: about 50mV
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===
If you want to get rid of VCC2, L2, R3, R4, R5, C11 and C111 are not needed. Close J2 in that case.

To change VCC2, change R4 and R5 according the NCN5120 dataheet. When VCC2 is greater than 10V, C11 must be changed so that the voltage rating matches or exceeds VCC2 (e.g. when VCC2 = 12V, use a 16V MLCC)

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===
[https://wiki.konnekting.de/images/3/33/MicroBCU_Schematic_V00.20.pdf Schematic V00.20]

=== KiCad ===

== Developer Documentation ==
=== Version history ===
*V00.11 - first prototype series
*V00.20 - second prototype series

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[https://gitlab.com/SirSydom/knx_microbcu2 MicroBCU2 on GitLab]

[[Category:Device/Kits]]

MicroBCU2

2020-11-30T09:57:46Z

SirSydom: /* Links */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A Bus Coupler Unit (BCU) / KNX Transveiver which supplies the connected device with power from KNX Bus and provides a bus interface at OSI Layer 2.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===
If you want to get rid of VCC2, L2, R3, R4, R5, C11 and C111 are not needed. Close J2 in that case.

To change VCC2, change R4 and R5 according the NCN5120 dataheet. When VCC2 is greater than 10V, C11 must be changed so that the voltage rating matches or exceeds VCC2 (e.g. when VCC2 = 12V, use a 16V MLCC)

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===
[https://wiki.konnekting.de/images/3/33/MicroBCU_Schematic_V00.20.pdf Schematic V00.20]

=== KiCad ===

== Developer Documentation ==
=== Version history ===
*V00.11 - first prototype series
*V00.20 - second prototype series

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[https://gitlab.com/SirSydom/knx_microbcu2 MicroBCU2 on GitLab]

[[Category:Device/Kits]]

MicroBCU2

2020-11-29T14:48:29Z

SirSydom: /* Schematic */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A Bus Coupler Unit (BCU) / KNX Transveiver which supplies the connected device with power from KNX Bus and provides a bus interface at OSI Layer 2.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===
If you want to get rid of VCC2, L2, R3, R4, R5, C11 and C111 are not needed. Close J2 in that case.

To change VCC2, change R4 and R5 according the NCN5120 dataheet. When VCC2 is greater than 10V, C11 must be changed so that the voltage rating matches or exceeds VCC2 (e.g. when VCC2 = 12V, use a 16V MLCC)

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===
[https://wiki.konnekting.de/images/3/33/MicroBCU_Schematic_V00.20.pdf Schematic V00.20]

=== KiCad ===

== Developer Documentation ==
=== Version history ===
*V00.11 - first prototype series
*V00.20 - second prototype series

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[[Category:Device/Kits]]

File:MicroBCU Schematic V00.20.pdf

2020-11-29T14:47:05Z

SirSydom:

MicroBCU2

2020-11-29T12:50:40Z

SirSydom: /* Developer Documentation */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A Bus Coupler Unit (BCU) / KNX Transveiver which supplies the connected device with power from KNX Bus and provides a bus interface at OSI Layer 2.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===
If you want to get rid of VCC2, L2, R3, R4, R5, C11 and C111 are not needed. Close J2 in that case.

To change VCC2, change R4 and R5 according the NCN5120 dataheet. When VCC2 is greater than 10V, C11 must be changed so that the voltage rating matches or exceeds VCC2 (e.g. when VCC2 = 12V, use a 16V MLCC)

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===

=== KiCad ===

== Developer Documentation ==
=== Version history ===
*V00.11 - first prototype series
*V00.20 - second prototype series

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[[Category:Device/Kits]]

MicroBCU2

2020-11-29T12:49:47Z

SirSydom: /* Deactivate / Change VCC2 */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A Bus Coupler Unit (BCU) / KNX Transveiver which supplies the connected device with power from KNX Bus and provides a bus interface at OSI Layer 2.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===
If you want to get rid of VCC2, L2, R3, R4, R5, C11 and C111 are not needed. Close J2 in that case.

To change VCC2, change R4 and R5 according the NCN5120 dataheet. When VCC2 is greater than 10V, C11 must be changed so that the voltage rating matches or exceeds VCC2 (e.g. when VCC2 = 12V, use a 16V MLCC)

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===

=== KiCad ===

== Developer Documentation ==

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[[Category:Device/Kits]]

MicroBCU2

2020-11-29T12:00:02Z

SirSydom: /* Enable High Bus current */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered top.jpg|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU2 V00 11 soldered bot.jpg|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Version
| V00.20
|-
! Microcontroller/Board
| universal
|}

== Description ==
A Bus Coupler Unit (BCU) / KNX Transveiver which supplies the connected device with power from KNX Bus and provides a bus interface at OSI Layer 2.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==

=== Soldering the Kit ===
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
*C4 - 100µF / 35V electrolytic capacitor. Polarization is important, refer to silkscreen or photo
*C41 - 1µF MLCC 1206
*L1 and L2 - 220µH inductors
*R1 - 22R resistor 2512
*J1 - 7x1 2.54 pin header (or whatever you need to connect to your host PCB)
*D1 - SS16 reverse polarity protection diode. . Polarization is important, refer to silkscreen. The bar on the diode should match the bar on silkscreen.
*D2 - SMAJ40CA TVS diode

I recommend to solder the parts in this order: L1, L2, C4, C41, R1, D1, D2, J1

=== Deactivate / Change VCC2 ===

=== Enable High Bus current ===
For bus current consumption up to 20mA, J3 must be closed (This is the default, closed by a 0R resistor).

For bus current consumption of 10mA or less, J3 can be open.

=== Schematic ===

=== KiCad ===

== Developer Documentation ==

== Links ==

[https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse Vorstellungs- / Entwicklunsthread im KNX User Forum]

[https://www.google.de/url?sa=t&rct=j&q=&esrc=s&source=web&cd=&cad=rja&uact=8&ved=2ahUKEwjZ_46X2aftAhUxvlkKHbOJCF4QFjAAegQIBBAC&url=https%3A%2F%2Fwww.onsemi.com%2Fpub%2FCollateral%2FNCN5120-D.PDF&usg=AOvVaw0KUimWgup68HXisop9pYTW OnSemi NCN5120 Datasheet]

[[Category:Device/Kits]]

MicroBCU2

2020-11-29T11:57:01Z

SirSydom: /* Links */

MicroBCU2

2020-11-29T11:54:54Z

SirSydom: /* Soldering the Kit */

MicroBCU2

2020-11-29T11:07:36Z

SirSydom:

MicroBCU2

2020-11-29T11:01:04Z

SirSydom:

File:MicroBCU2 V00 11 soldered bot.jpg

2020-11-29T10:58:08Z

SirSydom:

File:MicroBCU2 V00 11 soldered top.jpg

2020-11-29T10:57:21Z

SirSydom:

MicroBCU2

2020-11-29T10:01:49Z

SirSydom: Created page with "{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;" ! colspan="2"|MicroBCU2 |- ! colspan="2"|File:MicroBCU_top.png|300px|thumb|..."

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|MicroBCU2
|-
! colspan="2"|[[File:MicroBCU_top.png|300px|thumb|center]]
|-
! colspan="2"|[[File:MicroBCU_bottom.png|300px|thumb|center]]
|-
! Developer
| SirSydom
|-
! Status
| beta
|-
! Microcontroller/Board
| universal
|}

== Description ==
A Bus Coupler Unit (BCU) / KNX Transveiver which supplies the connected device with power from KNX Bus and provides a bus interface at OSI Layer 2.

== Hardware ==
*IC: NCN5120 (ready for NCN5121 / 5130)
*Size: 23 x 19 x 9 mm
*Voltage 1: 3.3V
*Voltage 2 (optional): 5V (default), can be changed: 3.3V - 21V
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 3.3V

== User Documentation ==
- deativate 5V
- change 5V

== Developer Documentation ==

== Build It ==
MicroBCU2 comes as a kit where the big parts on the bottom side have to be soldered:
C4
C41
L1 and L2
R1
J1

== Links ==

Vorstellungs- / Entwicklunsthread im KNX User Forum [https://knx-user-forum.de/forum/projektforen/konnekting/1550342-sehr-g%C3%BCnstige-micro-bcu-lite-als-bausatz-interesse]

[[Category:Device/Kits]]

KONNEKTING Protocol Specification 0x01

2020-11-08T20:30:53Z

SirSydom: /* 0x0B ProgrammingModeRead */

= 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
* 255 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 />

SiemensBCU

2020-11-06T11:09:51Z

SirSydom:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|SiemensBCU
|-
! colspan="2"|[[File:SiemensBCU naked top.jpg|300px|thumb|center]]
|-
! Developer
| Siemens AG
|-
! Status
| availible
|-
! MLFB
| 5WG1117-2AB12
|-
! Price
| 20-25€
|}

== Description ==
[[File:SIEMENS_5WG1117-2AB12.jpg|200px|thumb|right]]
[[File:SiemensBCU naked top.jpg|200px|thumb|right]]
[[File:SiemensBCU naked bot.jpg|200px|thumb|right]]
A cheap Bus Coupler Unit with an UART interface designed
for the use with Siemens Gamma switches.

It comes with a case and support frame (de: Tragring) for use in a flush mount box (de: Unterputzdose).

For the use in Konnekting devices it can be stripped out easily.

== Hardware ==
*IC: TPUart2
*Size: 42 x 44 x 9 mm
*Voltage 1: 5V (30mA / 50mA max)
*Voltage 2 : 20V (25mA max)
*UART: 19200bps 8E1 / 5V

== User Documentation ==
<gallery>
SiemensBCU dimensions.png
SiemensBCU interface.png
SiemensBCU pinout.png
</gallery>

== Links ==
[https://www.konnekting.de/konnekting-lernen/lektion-2-was-steckt-in-der-siemens-bcu/]

[[Category:Device/Kits]]

File:SiemensBCU naked bot.jpg

2020-11-06T11:08:27Z

SirSydom:

== Licensing ==
{{CC-by-sa-2.5}}

Konnekting Rail System XL

2020-08-04T19:56:48Z

SirSydom: /* Roadmap */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Konnekting Rail System XL
|-
! colspan="2"|[[File:KRS-XL DIM-24CVLED insights.jpeg|300px|thumb|center]]
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| 1. device realized / Ready to use
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]] / [[SiemensBCU]]
|-
! Repository
| [https://gitlab.com/SirSydom/konnekting_common On GitLab]
|}

== Description ==

The '''K'''onnekting '''R'''ail '''S'''ystem '''XL''' (KRS-XL) is a bunch of modular hard- and software for building devices in big DIN Rail Casings. It is designed for applications with a high number of channels.

== Design ideas and principles ==

The itention for developing this system was to reduce the costs of the devices. Because Bus connection, case, microcontroller are often the most expensive parts, a high number of channels very effectively reduces the cost per channel.
So the system is designed for use in 6, 9 and 12 TE DIN-Rail cases.

Another important design priciple was the use of prebuild componentes. Not only to reduce developement complexity and enable persons with limited soldering skills and tools to build it, but also to make it easier to repair devices in the future.
On the Controller Board three prebuild components which are generally availible are used: a pluggable microcontroller board, a pluggable Bus interface and a display module.

Modularity was added later in the developement phase, but was a logical step. The Controller Board is designed to be used in all devices within this system. It contains not only the microcontroller and bus interface, but also the user interface (frontend). To make it possible to handle high channel numbers and also to have one common hardware, a 320x240 px 2.2" Display is used as UI, operated by 4 buttons.
To improve supply quality, it is not only possible to use the [[MicroBCU]], but also the [[SiemensBCU]]. Unfortunately, the [[SiemensBCU]] comes with some limitations regarding power consumption.
To fit the needs for every device regarding power supply and galvanic insulation there is a wide range of assembly variants and solder jumper options.

Because of the need to have the Controller Board at the top (because of the UI) and the fact that the pluggable component need some space, I choose a two PCB design - the big application PCB at the bottom and a the Controller Board at the top. With the ApraRail DB DIN Rail casing series, KRS-XL comes with quite robust, widely availible (Reichelt, Amazon) casings.
Unfortunately in this casings there is no possibilty to connect to the top PCB - so KNX and if neccessary DC power have to be connected to the application PCB which is connected to the Controller Board.

To enable easy replacement, repair or improvement, two-part conectors are used. They can be unplugged from the device an remain in the cabinet without the danger of short circuits, and the cany easily plugged in again.
To achieve this, Phoenix combicon MSTB with 5.08 pitch (to enable bread board use at application PCB) are used. They are avaiblibe up to 16 amps and can also be used with 230V.

Because there is no possibility to have a standard KNX connector with the ApraRAIL DB casings, the Combicon connector is also used of standard for the KNX connection. Plugs with two wire per pin are availibe, so the devices can be chained.

== Distribution concept ==

I will not sell kits or even pre soldered kits. The System is designed for hobbyists that can and want to build it on their own (to save money, or just because they can). The needed soldering skills are low due to the usage of only THT and big SMD components.

Almost all parts can be purchased at standard shops with normal shipping costs. For special parts and the PCBs I will maybe organize bulk orders.

== Controller Board CB6-9-12 ==

=== Microcontroller Board ===

A Adafruit ItsyBitsy M0 Express Board was the almost perfect solution for the needs of KRS-XL:
* ATSAMD21 controller ("standard" controller for Konnekting) with sufficient cpu power, RAM, and FLASH
* SPI Flash to enable FOTB
* good availablity
* quality supllier
* pin compatible big brother ItsyBitsy M4 with Cortex M4 CPU available

== Devices ==

=== Roadmap ===

* [[ DIM-24CVLED.01 | DIM-24CVLED.01 - 24 channel PWM-LED Dimmer (24V DC) 9TE ]]
* 16-24 channel CC-LED Dimmer 9 or 12 TE based on Meanwell LDD
* 230V switching actuator

== Links ==
https://knx-user-forum.de/forum/projektforen/konnekting/1449711-krs-xl-konnekting-rail-system-xl

https://knx-user-forum.de/forum/projektforen/konnekting/1412984-in-entwicklung-modulares-ger%C3%A4tekonzept-6-9-12-te

Konnekting Rail System XL

2020-08-04T07:25:26Z

SirSydom: /* Design ideas and principles */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Konnekting Rail System XL
|-
! colspan="2"|[[File:KRS-XL DIM-24CVLED insights.jpeg|300px|thumb|center]]
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| 1. device realized / Ready to use
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]] / [[SiemensBCU]]
|-
! Repository
| [https://gitlab.com/SirSydom/konnekting_common On GitLab]
|}

== Description ==

The '''K'''onnekting '''R'''ail '''S'''ystem '''XL''' (KRS-XL) is a bunch of modular hard- and software for building devices in big DIN Rail Casings. It is designed for applications with a high number of channels.

== Design ideas and principles ==

The itention for developing this system was to reduce the costs of the devices. Because Bus connection, case, microcontroller are often the most expensive parts, a high number of channels very effectively reduces the cost per channel.
So the system is designed for use in 6, 9 and 12 TE DIN-Rail cases.

Another important design priciple was the use of prebuild componentes. Not only to reduce developement complexity and enable persons with limited soldering skills and tools to build it, but also to make it easier to repair devices in the future.
On the Controller Board three prebuild components which are generally availible are used: a pluggable microcontroller board, a pluggable Bus interface and a display module.

Modularity was added later in the developement phase, but was a logical step. The Controller Board is designed to be used in all devices within this system. It contains not only the microcontroller and bus interface, but also the user interface (frontend). To make it possible to handle high channel numbers and also to have one common hardware, a 320x240 px 2.2" Display is used as UI, operated by 4 buttons.
To improve supply quality, it is not only possible to use the [[MicroBCU]], but also the [[SiemensBCU]]. Unfortunately, the [[SiemensBCU]] comes with some limitations regarding power consumption.
To fit the needs for every device regarding power supply and galvanic insulation there is a wide range of assembly variants and solder jumper options.

Because of the need to have the Controller Board at the top (because of the UI) and the fact that the pluggable component need some space, I choose a two PCB design - the big application PCB at the bottom and a the Controller Board at the top. With the ApraRail DB DIN Rail casing series, KRS-XL comes with quite robust, widely availible (Reichelt, Amazon) casings.
Unfortunately in this casings there is no possibilty to connect to the top PCB - so KNX and if neccessary DC power have to be connected to the application PCB which is connected to the Controller Board.

To enable easy replacement, repair or improvement, two-part conectors are used. They can be unplugged from the device an remain in the cabinet without the danger of short circuits, and the cany easily plugged in again.
To achieve this, Phoenix combicon MSTB with 5.08 pitch (to enable bread board use at application PCB) are used. They are avaiblibe up to 16 amps and can also be used with 230V.

Because there is no possibility to have a standard KNX connector with the ApraRAIL DB casings, the Combicon connector is also used of standard for the KNX connection. Plugs with two wire per pin are availibe, so the devices can be chained.

== Distribution concept ==

I will not sell kits or even pre soldered kits. The System is designed for hobbyists that can and want to build it on their own (to save money, or just because they can). The needed soldering skills are low due to the usage of only THT and big SMD components.

Almost all parts can be purchased at standard shops with normal shipping costs. For special parts and the PCBs I will maybe organize bulk orders.

== Controller Board CB6-9-12 ==

=== Microcontroller Board ===

A Adafruit ItsyBitsy M0 Express Board was the almost perfect solution for the needs of KRS-XL:
* ATSAMD21 controller ("standard" controller for Konnekting) with sufficient cpu power, RAM, and FLASH
* SPI Flash to enable FOTB
* good availablity
* quality supllier
* pin compatible big brother ItsyBitsy M4 with Cortex M4 CPU available

== Devices ==

=== Roadmap ===

* 24 channel PWM CV-LED Dimmer 9 TE
* 16-24 channel CC-LED Dimmer 9 or 12 TE based on Meanwell LDD
* 230V switching actuator

== Links ==
https://knx-user-forum.de/forum/projektforen/konnekting/1449711-krs-xl-konnekting-rail-system-xl

https://knx-user-forum.de/forum/projektforen/konnekting/1412984-in-entwicklung-modulares-ger%C3%A4tekonzept-6-9-12-te

File:SiemensBCU naked top.jpg

2020-08-04T07:22:50Z

SirSydom: SirSydom uploaded a new version of File:SiemensBCU naked top.jpg

SiemensBCU

2020-08-04T07:22:06Z

SirSydom: /* Hardware */

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|SiemensBCU
|-
! colspan="2"|[[File:SiemensBCU naked top.jpg|300px|thumb|center]]
|-
! Developer
| Siemens AG
|-
! Status
| availible
|-
! MLFB
| 5WG1117-2AB12
|-
! Price
| 20-25€
|}

== Description ==
[[File:SIEMENS_5WG1117-2AB12.jpg|200px|thumb|right]]
[[File:SiemensBCU naked top.jpg|200px|thumb|right]]
A cheap Bus Coupler Unit with an UART interface designed for the use with Siemens Gamma switches.

It comes with a case and support frame (de: Tragring) for use in a flush mount box (de: Unterputzdose).

For the use in Konnekting devices it can be stripped out easily.

== Hardware ==
*IC: TPUart2
*Size: 42 x 44 x 9 mm
*Voltage 1: 5V (30mA / 50mA max)
*Voltage 2 : 20V (25mA max)
*UART: 19200bps 8E1 / 5V

== User Documentation ==
<gallery>
SiemensBCU dimensions.png
SiemensBCU interface.png
SiemensBCU pinout.png
</gallery>

== Links ==
[https://www.konnekting.de/konnekting-lernen/lektion-2-was-steckt-in-der-siemens-bcu/]

[[Category:Device/Kits]]

SiemensBCU

2020-08-04T07:21:44Z

SirSydom: Created page with "{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;" ! colspan="2"|SiemensBCU |- ! colspan="2"|File:SiemensBCU naked top.jpg|300..."

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|SiemensBCU
|-
! colspan="2"|[[File:SiemensBCU naked top.jpg|300px|thumb|center]]
|-
! Developer
| Siemens AG
|-
! Status
| availible
|-
! MLFB
| 5WG1117-2AB12
|-
! Price
| 20-25€
|}

== Description ==
[[File:SIEMENS_5WG1117-2AB12.jpg|200px|thumb|right]]
[[File:SiemensBCU naked top.jpg|200px|thumb|right]]
A cheap Bus Coupler Unit with an UART interface designed for the use with Siemens Gamma switches.

It comes with a case and support frame (de: Tragring) for use in a flush mount box (de: Unterputzdose).

For the use in Konnekting devices it can be stripped out easily.

== Hardware ==
*IC: TPUart2
*Size: 42 x 44 x 9 mm
*Voltage 1: 5V (30mA / 50mA max)
*Voltage 2 : 20V (25mA max)
*Max. current: up to 100mA
*UART: 19200bps 8E1 / 5V

== User Documentation ==
<gallery>
SiemensBCU dimensions.png
SiemensBCU interface.png
SiemensBCU pinout.png
</gallery>

== Links ==
[https://www.konnekting.de/konnekting-lernen/lektion-2-was-steckt-in-der-siemens-bcu/]

[[Category:Device/Kits]]

File:SiemensBCU naked back.jpg

2020-08-04T07:19:17Z

SirSydom: SirSydom uploaded a new version of File:SiemensBCU naked back.jpg

== Licensing ==
{{CC-by-sa-2.5}}

File:SiemensBCU naked back.jpg

2020-08-04T07:05:05Z

SirSydom:

== Licensing ==
{{CC-by-sa-2.5}}

File:SiemensBCU naked top.jpg

2020-08-04T07:04:37Z

SirSydom:

File:SiemensBCU pinout.png

2020-08-04T07:02:41Z

SirSydom:

File:SiemensBCU interface.png

2020-08-04T07:02:13Z

SirSydom:

File:SiemensBCU dimensions.png

2020-08-04T07:01:37Z

SirSydom:

File:SIEMENS 5WG1117-2AB12.jpg

2020-08-04T06:57:10Z

SirSydom:

Konnekting Rail System XL

2020-08-04T06:33:56Z

SirSydom:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Konnekting Rail System XL
|-
! colspan="2"|[[File:KRS-XL DIM-24CVLED insights.jpeg|300px|thumb|center]]
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| 1. device realized / Ready to use
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]] / [[SiemensBCU]]
|-
! Repository
| [https://gitlab.com/SirSydom/konnekting_common On GitLab]
|}

== Description ==

The '''K'''onnekting '''R'''ail '''S'''ystem '''XL''' (KRS-XL) is a bunch of modular hard- and software for building devices in big DIN Rail Casings. It is designed for applications with a high number of channels.

== Design ideas and principles ==

The itention for developing this system was to reduce the costs of the devices. Because Bus connection, case, microcontroller are often the most expensive parts, a high number of channels very effectively reduces the cost per channel.
So the system is designed for use in 6, 9 and 12 TE DIN-Rail cases.

Another important design priciple was the use of prebuild componentes. Not only to reduce developement complexity and enable persons with limited soldering skills and tools to build it, but also to make it easier to repair devices in the future.
On the Controller Board three prebuild components which are generally availible are used: a pluggable microcontroller board, a pluggable Bus interface and a display module.

Modularity was added later in the developement phase, but was a logical step. The Controller Board is designed to be used in all devices within this system. It contains not only the microcontroller and bus interface, but also the user interface (frontend). To make it possible to handle high channel numbers and also to have one common hardware, a 320x240 px 2.2" Display is used as UI, operated by 4 buttons.
To improve supply quality, it is not only possible to use the µBCU, but also the Siemens BCU. Unfortunately, the Siemens BCU comes with some limitations regarding power consumption.
To fit the needs for every device regarding power supply and galvanic insulation there is a wide range of assembly variants and solder jumper options.

Because of the need to have the Controller Board at the top (because of the UI) and the fact that the pluggable component need some space, I choose a two PCB design - the big application PCB at the bottom and a the Controller Board at the top. With the ApraRail DB DIN Rail casing series, KRS-XL comes with quite robust, widely availible (Reichelt, Amazon) casings.
Unfortunately in this casings there is no possibilty to connect to the top PCB - so KNX and if neccessary DC power have to be connected to the application PCB which is connected to the Controller Board.

To enable easy replacement, repair or improvement, two-part conectors are used. They can be unplugged from the device an remain in the cabinet without the danger of short circuits, and the cany easily plugged in again.
To achieve this, Phoenix combicon MSTB with 5.08 pitch (to enable bread board use at application PCB) are used. They are avaiblibe up to 16 amps and can also be used with 230V.

Because there is no possibility to have a standard KNX connector with the ApraRAIL DB casings, the Combicon connector is also used of standard for the KNX connection. Plugs with two wire per pin are availibe, so the devices can be chained.

== Distribution concept ==

I will not sell kits or even pre soldered kits. The System is designed for hobbyists that can and want to build it on their own (to save money, or just because they can). The needed soldering skills are low due to the usage of only THT and big SMD components.

Almost all parts can be purchased at standard shops with normal shipping costs. For special parts and the PCBs I will maybe organize bulk orders.

== Controller Board CB6-9-12 ==

=== Microcontroller Board ===

A Adafruit ItsyBitsy M0 Express Board was the almost perfect solution for the needs of KRS-XL:
* ATSAMD21 controller ("standard" controller for Konnekting) with sufficient cpu power, RAM, and FLASH
* SPI Flash to enable FOTB
* good availablity
* quality supllier
* pin compatible big brother ItsyBitsy M4 with Cortex M4 CPU available

== Devices ==

=== Roadmap ===

* 24 channel PWM CV-LED Dimmer 9 TE
* 16-24 channel CC-LED Dimmer 9 or 12 TE based on Meanwell LDD
* 230V switching actuator

== Links ==
https://knx-user-forum.de/forum/projektforen/konnekting/1449711-krs-xl-konnekting-rail-system-xl

https://knx-user-forum.de/forum/projektforen/konnekting/1412984-in-entwicklung-modulares-ger%C3%A4tekonzept-6-9-12-te

Konnekting Rail System XL

2020-08-04T06:27:06Z

SirSydom:

{| class="wikitable" style="float:right;margin-left: 15px;margin-top: 15px; margin-bottom: 15px;"
! colspan="2"|Konnekting Rail System XL
|-
! colspan="2"|[[File:KRS-XL DIM-24CVLED insights.jpeg|300px|thumb|center]]
|-
! Developer
| [http://wiki.konnekting.de/index.php/User:SirSydom SirSydom]
|-
! Phase
| 1. device realized / Ready to use
|-
! µC-Board
| [https://wiki.konnekting.de/index.php/Recommended_Arduino_Boards#Adafruit_ItsyBitsy_M0_Express ItsyBitsy M0 Express]
|-
! µC
| SAMD21G18
|-
! KNX
| [[MicroBCU]] / [[SiemensBCU]]
|-
! Repository
| [https://gitlab.com/SirSydom/konnekting_common On GitLab]
|}

== Description ==

The '''K'''onnekting '''R'''ail '''S'''ystem '''XL''' (KRS-XL) is a bunch of modular hard- and software for building devices in big DIN Rail Casings. It is designed for applications with a high number of channels.

== Design ideas and principles ==

The itention for developing this system was to reduce the costs of the devices. Because Bus connection, case, microcontroller are often the most expensive parts, a high number of channels very effectively reduces the cost per channel.
So the system is designed for use in 6, 9 and 12 TE DIN-Rail cases.

Another important design priciple was the use of prebuild componentes. Not only to reduce developement complexity and enable persons with limited soldering skills and tools to build it, but also to make it easier to repair devices in the future.
On the Controller Board three prebuild components which are generally availible are used: a pluggable microcontroller board, a pluggable Bus interface and a display module.

Modularity was added later in the developement phase, but was a logical step. The Controller Board is designed to be used in all devices within this system. It contains not only the microcontroller and bus interface, but also the user interface (frontend). To make it possible to handle high channel numbers and also to have one common hardware, a 320x240 px 2.2" Display is used as UI, operated by 4 buttons.
To improve supply quality, it is not only possible to use the µBCU, but also the Siemens BCU. Unfortunately, the Siemens BCU comes with some limitations regarding power consumption.
To fit the needs for every device regarding power supply and galvanic insulation there is a wide range of assembly variants and solder jumper options.

Because of the need to have the Controller Board at the top (because of the UI) and the fact that the pluggable component need some space, I choose a two PCB design - the big application PCB at the bottom and a the Controller Board at the top. With the ApraRail DB DIN Rail casing series, KRS-XL comes with quite robust, widely availible (Reichelt, Amazon) casings.
Unfortunately in this casings there is no possibilty to connect to the top PCB - so KNX and if neccessary DC power have to be connected to the application PCB which is connected to the Controller Board.

To enable easy replacement, repair or improvement, two-part conectors are used. They can be unplugged from the device an remain in the cabinet without the danger of short circuits, and the cany easily plugged in again.
To achieve this, Phoenix combicon MSTB with 5.08 pitch (to enable bread board use at application PCB) are used. They are avaiblibe up to 16 amps and can also be used with 230V.

Because there is no possibility to have a standard KNX connector with the ApraRAIL DB casings, the Combicon connector is also used of standard for the KNX connection. Plugs with two wire per pin are availibe, so the devices can be chained.

== Distribution concept ==

I will not sell kits or even pre soldered kits. The System is designed for hobbyists that can and want to build it on their own (to save money, or just because they can). The needed soldering skills are low due to the usage of only THT and big SMD components.

Almost all parts can be purchased at standard shops with normal shipping costs. For special parts and the PCBs I will maybe organize bulk orders.

== Controller Board CB6-9-12 ==

=== Microcontroller Board ===

A Adafruit ItsyBitsy M0 Express Board was the almost perfect solution for the needs of KRS-XL:
* ATSAMD21 controller ("standard" controller for Konnekting) with sufficient cpu power, RAM, and FLASH
* SPI Flash to enable FOTB
* good availablity
* quality supllier
* pin compatible big brother ItsyBitsy M4 with Cortex M4 CPU available

== Devices ==

=== Roadmap ===

* 24 channel PWM CV-LED Dimmer 9 TE
* 16-24 channel CC-LED Dimmer 9 or 12 TE based on Meanwell LDD
* 230V switching actuator

File:KRS-XL DIM-24CVLED insights.jpeg

2020-08-04T06:25:24Z

SirSydom:

== Licensing ==
{{CC-by-sa-2.5}}

Recommended Arduino Boards

2020-07-08T07:08:20Z

SirSydom:

= Clarification =

We focus on devices found on www.arduino.cc and support following chips for following devices:

* Atmel ATmega 328P
** Arduino Nano
** Arduino ProMini
* Atmel ATmega 32U4
** Arduino Leonardo
** Arduino Micro
* Atmel/Microchip SAMD21G18
** Arduino Zero

Our [[KONNEKTING Device Library]] has been developed and tested against the following platforms:

* Arduino.cc default ATmega based boards
* Arduino.cc SAMD Boards: https://github.com/arduino/ArduinoCore-samd

It is totally okay to use cheap Arduino boards from ebay or aliexpress, but you should be aware of the matching type of board according to the board-definitions of the platforms we use.

'''Our current and clear recommendation is, to use a SAM21G18 based board, as the chip provides 32k RAM and 256k Memory and 48Mhz clock speed. So plenty of space and performance at lowest possible current consumption.
'''
Be aware that there are different SAMD boards out there:

* Boards which refer to "M0"
* Boards which refer to "Zero"

Both may use different bootloader and both use in general differen pin-definitions. So you cannot really use the same sketch on both. You have to adapt to the few differences they have.

= Boards we can recommend =
== WeMos SAMD21 mini ==
https://img.staticbg.com/thumb/large/oaupload/banggood/images/87/BD/4f4ad980-0b6a-4b20-bf06-bf7c12d9b2e6.JPG

This board uses Arduino Zero Bootloader. It has '''no''' OnBoard (pin 13) LED.

P.S. This board was neither developed nor produced by WeMos... So you can't find it on WeMos homepage...

== WeMos SAMD21 ==
https://img.staticbg.com/thumb/large/oaupload/banggood/images/A0/49/8528801a-ee06-424a-8d87-57d4f9ba22a1.jpg

This board is "big brother" of '''WeMos SAMD21 mini'''.
It has a standard Arduino UNO R3 pin layout with additional RX(31) and TX(30) pins (UART name: Serial)

== Elecrow Crowduino M0 SD ==

[[File:Crowduino-m0-sd.jpg|Elecrow Crowduino M0-SD|800px]]

https://www.elecrow.com/crowduino-m0-sd-p-1649.html

'''Attention:''' this boards runs a "M0 bootloader". Please ensure that you select the correct board in Arduino IDE. It's "Arduino M0 Pro (Native USB Port)". [[User:Konnekting|KONNEKTING]] ([[User talk:Konnekting|talk]]) to be verified ...

Cost:~14US$ directly from Elecrow

== Adafruit ItsyBitsy M0 Express ==

https://cdn-shop.adafruit.com/970x728/3727-01.jpg

=== Advantages ===
* small size (1.5"/0.8" => 15x7 Pins 2.54 Grid )
* 2MB SPI Flash (ready for [FOTB_-_Firmware_Over_The_Bus]
* quality supplier (Adafruit), no china crap

=== Used in ===
* [[ DGC-CLDC0.01 CodeLock Door Controller ]]
* [[ EDS-WS433.01 Weatherstation for 433Mhz Sensors ]]
* [[ Konnekting_Rail_System_XL ]]

=== Further Infos ===
https://www.adafruit.com/product/3727

https://cdn-learn.adafruit.com/downloads/pdf/introducing-itsy-bitsy-m0.pdf?timestamp=1594182408

Schematic: https://cdn-learn.adafruit.com/assets/assets/000/054/505/original/adafruit_products_schem.png?1527457190

Eagle sources: https://github.com/adafruit/Adafruit-ItsyBitsy-M0-PCB

=== Buy at ===
https://www.adafruit.com/product/3727#technical-details

https://www.digikey.de/product-detail/de/3727/1528-2554-ND/8346575/?itemSeq=331621883

https://eckstein-shop.de/Adafruit-ItsyBitsy-M0-Express-for-CircuitPython-Arduino-IDE

https://www.exp-tech.de/plattformen/arduino/8448/adafruit-itsybitsy-m0-express-circuitpython-arduino-ide
'''
Board-Selection:''' to-be-done