Stm32World Wiki - User contributions [en]

Streamline

2026-04-21T01:59:40Z

Niclas: /* Miscellaneous */

[[Category:STM32]][[Category:Streamline]][[Category:CurrentMakers]][[Category:Work in progress]]{{metadesc|Streamline Development Boards Home}}
[[File:Streamline Backplane with 2 blades - top right 3.jpg|300px|thumb|Streamline Backplane with 2 blades - 1 Connect and 1 MCU]]
This page documents the new [[CurrentMakers]] [[Streamline]] series of [[Green]] development boards. If you are looking for the previous series, that is document here: [[STM32World Legacy]].

[[Streamline]] boards are available here: [https://currentmakers.com/products/streamline/ Streamline on CurrentMakers]

{{clear}}
== Rationale ==
[[File:3 STM32World Modules stacked.jpg|300px|thumb]]
A number of [[STM32World Legacy]] boards have been developed, and produced, and in general the "system" worked very well. It did however have one fatal flaw which was the sole cause of it never being considered for more widespread production. This flaw was the board to board connector.

The original boards used a 2x20 standard pin header on each side giving a result of 80 pins. In terms of connectivity this was a pretty good solution. It did however present some issues:

# Cost - the long pin 2x20 connectors are fairly expensive - around $0.80 each - so $1.60 per board. This may not sound that high but when producing a lot it becomes a serious cost.
# Manufacturing - the headers can not be manufactured with traditional SMD technologies but require a manual step or hand soldering.
# Fragile - when shipping or disconnecting boards it is hard not to bend one or more pins and once bend it becomes extremely difficult to reconnect them.

To get around this flaw a new "connector" was considered and after a long search the best solution was the standard PCI-E X8 connector.

== Videos ==

{{#ev:youtube|5xQqV7BhYxM}}

Receiving the first prototypes ever:

{{#ev:youtube|YS1w_8ghCf4}}

== Backplane ==

The overall idea is to base [[StreamLine]] around a passive backplane. The backplane contains a number of PCI connectors with 2 x 49 pins (98) that is simply connected in a parallel bus.

<div class="res-img">
[[File:Sl bp 5 top left.png|1000px]]
</div>

In each end of the bus all the A and B signals are broken out into regular pin headers.

=== Backplane rendering ===

<gallery>
File:Backplane top render.png
File:Backplane front render.png
File:Backplane front left render.png
File:Sl bp 5 top.png
File:Sl bp 5 top left.png
File:Sl bp 5 top right.png
</gallery>

== Modules ==

=== [[Backplane]]s ===

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Backplane 5]]
| [[File:sl_bp_5_top_left.png|80px]]
| Basic 5 position backplane
| [https://currentmakers.com/products/streamline/streamline_backplane_5/ Available]
|}

=== [[Blade]]s ===

==== STM32 ====

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Connect]]
| [[File:Sl prog top left render.png|80px]]
| Streamline Programmer & Debugger. This module is essentially identical to [[Jolt Connect]]
| [https://currentmakers.com/products/streamline/streamline_connect/ Available]
|-
| [[Streamline MCU STM32F407]]
| [[File:Sl mcu stm32f407 top left render.png|80px]]
| Streamline MCU board including a [[STM32F407]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32f407/ Available]
|-
| [[Streamline MCU STM32H562]]
| [[File:Sl mcu stm32h562 top left render.png|80px]]
| Streamline MCU board including a [[STM32H562]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32h562/ Available]
|-
| [[Streamline MCU STM32L475]]
| [[File:Sl mcu stm32l475 top left render.png|80px]]
| Streamline MCU board including a [[STM32L475]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32l475/ Available]
|-
| [[Streamline MCU STM32C511]]
| [[File:Sl_mcu_stm32c551_top_left_render.png|80px]]
| Streamline MCU board including a [[STM32C511]]
| [https://currentmakers.com/products/streamline/streamline_mcu_stm32c511/ Available]
|}

==== Miscellaneous ====

{| class="wikitable"
|-
! Name
! Image
! Description
! Status
|-
| [[Streamline Neopixel 8x8]]
| [[File:Sl neopixel 8x8 top left render.png|80px]]
| Module with an 8x8 matrix of Neopixel WS2812 LEDs
| [https://currentmakers.com/products/streamline/streamline_neopixel_8x8/ Available]
|-
| [[Streamline Storage SD]]
| [[File:Sl storage sd top left render rev A.png|80px]]
| Module with Micro-SD slot
| [https://currentmakers.com/products/streamline/streamline_sd/ Available]
|-
| [[Streamline Storage Flash]]
| [[File:Sl storage flash top left render.png|80px]]
| Module with 16 MB Flash storage ([[W25q128]])
| [https://currentmakers.com/products/streamline/streamline_flash/ Available]
|-
| [[Streamline Storage EEPROM]]
| [[File:Sl storage eeprom top left render.png|80px]]
| Module with 512kB EEPROM storage ([[M24M01]])
| [https://currentmakers.com/products/streamline/streamline_eeprom/ Available]
|-
| Streamline Real Time Clock
|
| Real time clock with on board coin cell battery (or supercap) backup
| Idea
|-
| Streamline ESC
|
| Electronic speed control for BLDC motors
| Idea
|-
| Streamline HS USB
|
| HS USB blade using [[USB3300]]
| Idea
|-
| Streamline CAN-FD
|
| CAN-FD bus interface
| Idea
|-
| Streamline Ethernet
|
| Ethernet interface for STM32F407
| Prototype
|-
| Streamline RS485
|
| Non-isolated RS485 interface
| Prototype
|-
| Streamline WiFi
|
| WiFi interface
| Idea
|}

== Standard Pinout ==

The pinout table is based on a [[MCU]] board with a 100 pin STM32F407. Boards using [[STM32]] [[MCU]]s with less pins will leave some of the pins unused.

{{Streamline Pinout}}

== Prototype Photos ==

<gallery>
File:Streamline Backplane with 2 blades - top right 3.jpg
File:Streamline Backplane with 2 blades - top right 2.jpg
File:Streamline Backplane with 2 blades - top right.jpg
File:Streamline Backplane with 2 blades - top left.jpg
File:Streamline Backplane with 2 blades - front.jpg
File:Streamline Multiple Blades.jpg
File:Streamline MCU STM32L475 - top view.jpg
File:Streamline MCU STM32L475 - bottom view.jpg
File:Streamline MCU STM32H562 - top view.jpg
File:Streamline MCU STM32H562 - bottom view.jpg
File:Streamline MCU STM32F407 - top view.jpg
File:Streamline MCU STM32F407 - bottom view.jpg
File:Streamline Connect - top view.jpg
File:Streamline Connect - bottom view.jpg
</gallery>

== Miscellaneous Links ==

[https://currentmakers.com CurrentMakers main site]

Colibri Zephyr

2026-04-20T11:15:27Z

Niclas: /* Setting up Zephyr */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

Colibri is intended to be used by systems integrators, makers, automation engineers, home automation enthusiasts and in general people how doesn't necessarily know how to write low-level programs or operate soldering iron. That means that "flashing an image" to the MCU is beyond what is expected by the potential customers.

Instead, we need an "operating system", where we can deploy user applications without low-level programming skills. With that comes two challenges;

1. How are those applications written?

2. How are they going to be executed on the Colibri MCUs?

TL;DR
* A ''user application'' will deployed in a so called [https://en.wikipedia.org/wiki/WebAssembly ''Web Assembly''] runtime. The number and size of user applications are dependent on available RAM in the MCU.
* Each I/O module will contain its own ''Web Assembly'' driver that user applications will be able to interface with.
* I/O driver is (initially?) limited to 16kB in size and will run inside its own ''Web Assembly'' runtime and given time slots to execute, via a <code>tick(slot_number)</code> function call at a (per I/O slot) settable interval. I/O modules may also emit '''''events''''' that applications can subscribe to. The exact API is documented for each Colibri I/O module.

It could happen that domain-specific languages are to be developed for this environment. Or perhaps, we will managed to get [https://autonomylogic.com/runtime OpenPLC] running on ''Web Assembly''. It is a little bit too early to tell in which direction this will be going.

= What is Zephyr? =
From [https://docs.zephyrproject.org/latest/introduction/index.html Zephyr's website];

The Zephyr OS is based on a small-footprint kernel designed for use on resource-constrained
and embedded systems: from simple embedded environmental sensors and LED wearables to sophisticated
embedded controllers, smart watches, and IoT wireless applications.

Please read the entire [https://docs.zephyrproject.org/latest/introduction/index.html introduction page].

Additionally to task scheduling, we also get '''cross-platform APIs for SPI and I2C peripherals''', as well as access to many Zephyr libraries, such as '''Modbus/RTU, TCP/IP, MQTT''' and much more.

= Supported Boards =
* [[Streamline MCU STM32F407]]
* [[Colibri MCU3]]
* [[Colibri 3a]]
* [[Colibri 8]]

= Colibri Integration =
Colibri carrier boards and Colibri MCU modules are being integrated with Zephyr.

= Setting up Zephyr =
Follow the installation instructions on [https://docs.zephyrproject.org/latest/develop/getting_started/index.html Zephyr's Getting Started documentation].

You will end up with a <code>${HOME}/zephyrproject</code> directory. If you chose to place that elsewhere, the instructions below must be adjusted.

Check out [https://github.com/currentmakers/zephyr-cm https://github.com/currentmakers/zephyr-cm]

Create a <code>${HOME}/.zephyrrc</code> with the following content;
export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr/ # Maybe change this
export ZEPHYR_EXTRA_MODULES=${HOME}/dev/currentmakers/zephyr-cm # <--- CHANGE THIS

Create a file <code>init-zephyr</code> and place somewhere you easily remember how to access it. Let's assume it is in <code>${HOME}</code>. Following content;
export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr
source ${ZEPHYR_BASE}/../.venv/bin/activate
source ${ZEPHYR_BASE}/zephyr-env.sh

= Developing with Zephyr =

After opening the terminal to compile, remember to run
. ${HOME}/init-zephyr
to enable the Python environment and set up the paths.

For any given Zephyr project, for instance the ones in [https://github.com/currentmakers/zephyr-examples] you build like this

west build -b colibri_mcu3 -- -DSHIELD=colibri_8

and the <code>.elf</code> and <code>.bin</code> output files are in <code>build/zephyr</code> and can be flashed as usual with

st-flash --connect-under-reset write build/zephyr/zephyr.bin 0x8000000

(I have seen the <code>st-flash</code> failed to access without the <code>connect-under-reset</code>.)

Colibri Zephyr

2026-04-20T11:14:39Z

Niclas: /* Setting up Zephyr */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

Colibri is intended to be used by systems integrators, makers, automation engineers, home automation enthusiasts and in general people how doesn't necessarily know how to write low-level programs or operate soldering iron. That means that "flashing an image" to the MCU is beyond what is expected by the potential customers.

Instead, we need an "operating system", where we can deploy user applications without low-level programming skills. With that comes two challenges;

1. How are those applications written?

2. How are they going to be executed on the Colibri MCUs?

TL;DR
* A ''user application'' will deployed in a so called [https://en.wikipedia.org/wiki/WebAssembly ''Web Assembly''] runtime. The number and size of user applications are dependent on available RAM in the MCU.
* Each I/O module will contain its own ''Web Assembly'' driver that user applications will be able to interface with.
* I/O driver is (initially?) limited to 16kB in size and will run inside its own ''Web Assembly'' runtime and given time slots to execute, via a <code>tick(slot_number)</code> function call at a (per I/O slot) settable interval. I/O modules may also emit '''''events''''' that applications can subscribe to. The exact API is documented for each Colibri I/O module.

It could happen that domain-specific languages are to be developed for this environment. Or perhaps, we will managed to get [https://autonomylogic.com/runtime OpenPLC] running on ''Web Assembly''. It is a little bit too early to tell in which direction this will be going.

= What is Zephyr? =
From [https://docs.zephyrproject.org/latest/introduction/index.html Zephyr's website];

The Zephyr OS is based on a small-footprint kernel designed for use on resource-constrained
and embedded systems: from simple embedded environmental sensors and LED wearables to sophisticated
embedded controllers, smart watches, and IoT wireless applications.

Please read the entire [https://docs.zephyrproject.org/latest/introduction/index.html introduction page].

Additionally to task scheduling, we also get '''cross-platform APIs for SPI and I2C peripherals''', as well as access to many Zephyr libraries, such as '''Modbus/RTU, TCP/IP, MQTT''' and much more.

= Supported Boards =
* [[Streamline MCU STM32F407]]
* [[Colibri MCU3]]
* [[Colibri 3a]]
* [[Colibri 8]]

= Colibri Integration =
Colibri carrier boards and Colibri MCU modules are being integrated with Zephyr.

= Setting up Zephyr =
Follow the installation instructions on [https://docs.zephyrproject.org/latest/develop/getting_started/index.html]

You will end up with a <code>${HOME}/zephyrproject</code> directory. If you chose to place that elsewhere, the instructions below must be adjusted.

Check out [https://github.com/currentmakers/zephyr-cm https://github.com/currentmakers/zephyr-cm]

Create a <code>${HOME}/.zephyrrc</code> with the following content;
export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr/ # Maybe change this
export ZEPHYR_EXTRA_MODULES=${HOME}/dev/currentmakers/zephyr-cm # <--- CHANGE THIS

Create a file <code>init-zephyr</code> and place somewhere you easily remember how to access it. Let's assume it is in <code>${HOME}</code>. Following content;
export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr
source ${ZEPHYR_BASE}/../.venv/bin/activate
source ${ZEPHYR_BASE}/zephyr-env.sh

= Developing with Zephyr =

After opening the terminal to compile, remember to run
. ${HOME}/init-zephyr
to enable the Python environment and set up the paths.

For any given Zephyr project, for instance the ones in [https://github.com/currentmakers/zephyr-examples] you build like this

west build -b colibri_mcu3 -- -DSHIELD=colibri_8

and the <code>.elf</code> and <code>.bin</code> output files are in <code>build/zephyr</code> and can be flashed as usual with

st-flash --connect-under-reset write build/zephyr/zephyr.bin 0x8000000

(I have seen the <code>st-flash</code> failed to access without the <code>connect-under-reset</code>.)

Colibri Zephyr

2026-04-20T10:53:52Z

Niclas:

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

Colibri is intended to be used by systems integrators, makers, automation engineers, home automation enthusiasts and in general people how doesn't necessarily know how to write low-level programs or operate soldering iron. That means that "flashing an image" to the MCU is beyond what is expected by the potential customers.

Instead, we need an "operating system", where we can deploy user applications without low-level programming skills. With that comes two challenges;

1. How are those applications written?

2. How are they going to be executed on the Colibri MCUs?

TL;DR
* A ''user application'' will deployed in a so called [https://en.wikipedia.org/wiki/WebAssembly ''Web Assembly''] runtime. The number and size of user applications are dependent on available RAM in the MCU.
* Each I/O module will contain its own ''Web Assembly'' driver that user applications will be able to interface with.
* I/O driver is (initially?) limited to 16kB in size and will run inside its own ''Web Assembly'' runtime and given time slots to execute, via a <code>tick(slot_number)</code> function call at a (per I/O slot) settable interval. I/O modules may also emit '''''events''''' that applications can subscribe to. The exact API is documented for each Colibri I/O module.

It could happen that domain-specific languages are to be developed for this environment. Or perhaps, we will managed to get [https://autonomylogic.com/runtime OpenPLC] running on ''Web Assembly''. It is a little bit too early to tell in which direction this will be going.

= What is Zephyr? =
From [https://docs.zephyrproject.org/latest/introduction/index.html Zephyr's website];

The Zephyr OS is based on a small-footprint kernel designed for use on resource-constrained
and embedded systems: from simple embedded environmental sensors and LED wearables to sophisticated
embedded controllers, smart watches, and IoT wireless applications.

Please read the entire [https://docs.zephyrproject.org/latest/introduction/index.html introduction page].

Additionally to task scheduling, we also get '''cross-platform APIs for SPI and I2C peripherals''', as well as access to many Zephyr libraries, such as '''Modbus/RTU, TCP/IP, MQTT''' and much more.

= Supported Boards =
* [[Streamline MCU STM32F407]]
* [[Colibri MCU3]]
* [[Colibri 3a]]
* [[Colibri 8]]

= Colibri Integration =
Colibri carrier boards and Colibri MCU modules are being integrated with Zephyr.

= Setting up Zephyr =
Follow the installation instructions on [https://docs.zephyrproject.org/latest/develop/getting_started/index.html]

You will end up with a <code>${HOME}/zephyrproject</code> directory. If you chose to place that elsewhere, the instructions below must be adjusted.

Check out [https://github.com/currentmakers/zephyr-cm]

Create a <code>${HOME}/.zephyrrc</code> with the following content;
export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr/ # Maybe change this
export ZEPHYR_EXTRA_MODULES=${HOME}/dev/currentmakers/zephyr-cm # <--- CHANGE THIS

Create a file <code>init-zephyr</code> and place somewhere you easily remember how to access it. Let's assume it is in <code>${HOME}</code>. Following content;
export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr
source ${ZEPHYR_BASE}/../.venv/bin/activate
source ${ZEPHYR_BASE}/zephyr-env.sh

= Developing with Zephyr =

After opening the terminal to compile, remember to run
. ${HOME}/init-zephyr
to enable the Python environment and set up the paths.

For any given Zephyr project, for instance the ones in [https://github.com/currentmakers/zephyr-examples] you build like this

west build -b colibri_mcu3 -- -DSHIELD=colibri_8

and the <code>.elf</code> and <code>.bin</code> output files are in <code>build/zephyr</code> and can be flashed as usual with

st-flash --connect-under-reset write build/zephyr/zephyr.bin 0x8000000

(I have seen the <code>st-flash</code> failed to access without the <code>connect-under-reset</code>.)

Colibri Zephyr

2026-04-20T10:53:25Z

Niclas:

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

Colibri is intended to be used by systems integrators, makers, automation engineers, home automation enthusiasts and in general people how doesn't necessarily know how to write low-level programs or operate soldering iron. That means that "flashing an image" to the MCU is beyond what is expected by the potential customers.

Instead, we need an "operating system", where we can deploy user applications without low-level programming skills. With that comes two challenges;

1. How are those applications written?

2. How are they going to be executed on the Colibri MCUs?

TL;DR
* A ''user application'' will deployed in a so called [https://en.wikipedia.org/wiki/WebAssembly ''Web Assembly''] runtime. The number and size of user applications are dependent on available RAM in the MCU.
* Each I/O module will contain its own ''Web Assembly'' driver that user applications will be able to interface with.
* I/O driver is (initially?) limited to 16kB in size and will run inside its own ''Web Assembly'' runtime and given time slots to execute, via a <code>tick(slot_number)</code> function call at a (per I/O slot) settable interval. I/O modules may also emit '''''events''''' that applications can subscribe to. The exact API is documented for each Colibri I/O module.

It could happen that domain-specific languages are to be developed for this environment. Or perhaps, we will managed to get [https://autonomylogic.com/runtime OpenPLC] running on ''Web Assembly''. It is a little bit too early to tell in which direction this will be going.

= What is Zephyr? =
From [https://docs.zephyrproject.org/latest/introduction/index.html Zephyr's website];

The Zephyr OS is based on a small-footprint kernel designed for use on resource-constrained
and embedded systems: from simple embedded environmental sensors and LED wearables to sophisticated
embedded controllers, smart watches, and IoT wireless applications.

Please read the entire [https://docs.zephyrproject.org/latest/introduction/index.html introduction page].

Additionally to task scheduling, we also get '''cross-platform APIs for SPI and I2C peripherals''', as well as access to many Zephyr libraries, such as '''Modbus/RTU, TCP/IP, MQTT''' and much more.

= Colibri Integration =
Colibri carrier boards and Colibri MCU modules are being integrated with Zephyr.

= Setting up Zephyr =
Follow the installation instructions on [https://docs.zephyrproject.org/latest/develop/getting_started/index.html]

You will end up with a <code>${HOME}/zephyrproject</code> directory. If you chose to place that elsewhere, the instructions below must be adjusted.

Check out [https://github.com/currentmakers/zephyr-cm]

Create a <code>${HOME}/.zephyrrc</code> with the following content;
export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr/ # Maybe change this
export ZEPHYR_EXTRA_MODULES=${HOME}/dev/currentmakers/zephyr-cm # <--- CHANGE THIS

Create a file <code>init-zephyr</code> and place somewhere you easily remember how to access it. Let's assume it is in <code>${HOME}</code>. Following content;
export ZEPHYR_BASE=${HOME}/zephyrproject/zephyr
source ${ZEPHYR_BASE}/../.venv/bin/activate
source ${ZEPHYR_BASE}/zephyr-env.sh

= Developing with Zephyr =

After opening the terminal to compile, remember to run
. ${HOME}/init-zephyr
to enable the Python environment and set up the paths.

For any given Zephyr project, for instance the ones in [https://github.com/currentmakers/zephyr-examples] you build like this

west build -b colibri_mcu3 -- -DSHIELD=colibri_8

and the <code>.elf</code> and <code>.bin</code> output files are in <code>build/zephyr</code> and can be flashed as usual with

st-flash --connect-under-reset write build/zephyr/zephyr.bin 0x8000000

(I have seen the <code>st-flash</code> failed to access without the <code>connect-under-reset</code>.)

= Supported Boards =
* [[Streamline MCU STM32F407]]
* [[Colibri MCU3]]
* [[Colibri 3a]]
* [[Colibri 8]]

File:Colibri Architecture-1.svg

2026-04-20T04:37:22Z

Niclas: Niclas uploaded a new version of File:Colibri Architecture-1.svg

== Summary ==
One architectural conceptual view of the Colibri system.

File:Colibri Architecture-1.svg

2026-04-20T01:04:38Z

Niclas: Niclas uploaded a new version of File:Colibri Architecture-1.svg

== Summary ==
One architectural conceptual view of the Colibri system.

File:Colibri Architecture-1.svg

2026-04-19T23:53:24Z

Niclas: Niclas uploaded a new version of File:Colibri Architecture-1.svg

== Summary ==
One architectural conceptual view of the Colibri system.

Colibri

2026-04-19T16:00:13Z

Niclas: /* Architecture Overview */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

<div class="thumb tright">
<div class="thumbinner" style="width: 250px;">
<div style="width: 250px; height: 150px; overflow: hidden; position: relative; background: #000;">
<div style="position: absolute; top: -20px; left: -15px;">
[[File:Colibri_8_photo1.jpg|250px|link=File:Colibri_8_photo1.jpg|alt=Colibri 8 PCB]]
</div>
</div>
</div>
</div>
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri rs485u-2.jpg|180px|thumb]]
[[File:Colibri aic-RevA-2.jpg|180px|thumb]]

Check out the [[Colibri Videos]] on Youtube.

Colibri is a low-cost automation system, primarily intended for building automation, home automation, energy supervision, agriculture supervision and similar systems. Main features beside costs are;
* Flexible I/O system, via MCU modules and I/O modules in M.2 Key E sockets. Many types already developed.
* Power supply of 9-36 Volt, either AC or DC (some I/O cards won't work with DC supply, and some not with AC supply)
* Each I/O slot can be powered-up/down individually from the MCU.
* Each I/O slot is addressable individually.
* MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
* Each I/O module has an 1Mbit EEPROM with calibration parameters and a WebAssembly program for the MCU module to execute.
* Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.

== Architecture Overview ==
<div class="res-img">
[[File:Colibri_Architecture-1.svg|240px]]
</div>

Colors in this view represents who creates the software for each part.

== Programming ==
The Colibri system is designed around two main external projects, [[Colibri Zephyr|Zephyr]] and WebAssembly ([https://github.com/wasm3/wasm3 wasm3]).

Zephyr provides a lot of ''operating system'' type of features, like task scheduling, concurrency data types, timers, peripheral drivers and cross-platform compatibility to be able to support STM32, RP2354 and possibly other MCU families. And combining that with a WebAssembly environment, we should be able to have a lot of platform independence.

The WebAssembly approach is to allow for;
* I/O modules that are unknown to the MCU module to be installed without re-flashing the firmware,
* Uploading of user programs, without flashing the firmware,
* Sandboxed execution to limit issues that user programs can create,
* Simplified tool chain,
* Deferring the choice of programming languages,
* Future-proofing for programming evolution, option to create our own language.

== Carrier Boards ==
* ''Colibri 3a'' has 2 I/O slots and one MCU slot, one USB-C port to the MCU slot, Jolt Connect pin header for programming.
* ''Colibri 8'' is like the ''Colibri 3a'', but with 7 I/O slots and an isolated RS-485 port to the MCU slot.
* Planned; ''Colibri 8pi'' is like the ''Colibri 8'' but with a full-fledged Raspberry Pi Compute Module 5. 1 Colibri MCU slot and 7 I/O slots,
* Planned; ''Colibri 16pi'' is like the ''Colibri 8pi'', but with 15 I/O slots rather than 7.

== MCU Modules ==
There is a choice, and more will follow;

* ''[[Colibri MCU1]]'' - MCU module with a STM32WLE5, 256kB Flash, 64kB RAM, on-chip LoRa and LoraWAN protocol available in STM32CubeMX.
* ''[[Colibri MCU2]]'' - MCU module with a STM32H562RG, 1024kB Flash, 640kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
* ''[[Colibri MCU6]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.

== I/O Modules ==
The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an [[Colibri_EEPROM_Layout|EEPROM memory]] available to identify which module is present in each I/O slot, links to documentation, calibration parameters, testing results and (up to) 16kB of WebAssembly for the MCU module to execute.

== [[Colibri Form Factor|Form Factor]] ==

Both Colibri I/O modules and MCU modules are 22x42mm and has an edge connector called M.2 Key E, '''but it doesn't follow the M.2 specification for Key E'''. The distance between the I/O slots are specified to 23.5mm,
theoretically making it possible for multi-slot I/O modules (none are planned).

<span style="color:#FF4444">'''WARNING!!! Do NOT plug Colibri I/O modules nor any MCU module into other equipment. Do NOT plug any M.2 card into a Colibri system, unless that card/board is specifically made for Colibri.'''</span>

== Boards ==

{| class=wikitable
|-
! Name
! Type
! Description
! Status
|-
| ''[[Colibri 3a]]''
| Colibri Carrier
| Minimal Colibri carrier board with 2 I/O slots and one MCU slot. MCU slot is to be populated with any of the MCU variants available.
| Active
|-
| ''[[Colibri 8]]''
| Colibri Carrier
| Colibri carrier board with Colibri MCU slot and 7 Colibri I/O slots.
| Early Access
|-
| ''[[Colibri 1dp]]''
| Colibri Carrier
| Minimal Colibri Host with a single MCU slot and 0-500Pa air pressure sensor.
| Prototypes
|-
| ''[[Colibri MCU1]]''
| Host MCU
| MCU module with a STM32WLE5CC, for LoraWAN applications.
| Prototyping
|-
| ''[[Colibri MCU2]]''
| Host MCU
| MCU module with a STM32H562RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU3]]''
| Host MCU
| MCU module with a STM32F405RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU4]]''
| Host MCU
| MCU module with a STM32L475RGTx and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU6]]''
| Host MCU
| MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.
| Prototyping
|-
| ''[[M.2 E Breakout]]''
| M.2 breakout board
| Generic breakout board for M.2 E key boards.
| Prototypes
|-
| ''[[Colibri AIC]]''
| I/O module
| Two analog 0-20mA inputs
| Prototypes
|-
| ''[[Colibri AIV]]''
| I/O module
| Two analog 0-10V inputs
| Prototypes
|-
| ''[[Colibri AQV]]''
| I/O module
| Two analog 0-10V outputs
| Active
|-
| ''[[Colibri DII]]''
| I/O module
| Two ISOLATED digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DIO1]]''
| I/O module
| IEC 61131-2 compliant, 4-channels digital inputs and outputs.
| Prototypes
|-
| ''[[Colibri DIU]]''
| I/O module
| Four digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DP1]]''
| I/O module
| A 0-500Pa air pressure sensor mounted on I/O module.
| Prototyping
|-
| ''[[Colibri FET]]''
| I/O module
| Four digital outputs, FET outputs sinking to GND. Max 1 Amp per channel.
| Prototypes
|-
| ''[[Colibri PID1]]''
| I/O module
| PID regulator, with a PT1000 input and a 0-10V analog output. On-board STM32F030 for host-independent operation.
| Active
|-
| ''[[Colibri Pt1000]]''
| I/O module
| Two PT1000 temperature sensor inputs.
| Active
|-
| ''[[Colibri RS485I]]''
| I/O module
| Isolated RS-485 port. On-board STM32G431KB to implement protocols, such as Modbus RTU.
| Prototyping
|-
| ''[[Colibri RS485U]]''
| I/O module
| Two non-isolated RS-485 ports. On-board STM32F030 implementing Modbus protocol, either as master or slave device.
| Prototypes
|-
| ''[[Colibri SSR]]''
| I/O module
| Two Solid State Relays, ON/OFF.
| Prototypes
|-
| ''[[Colibri TRIAC1]]''
| I/O module
| Four Triac outputs, driving 24V AC.
| Prototyping
|}

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| ''[[Colibri-8pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 7 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|-
| ''[[Colibri-16pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 15 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|}

= License =
All Schematics are licensed with the GPLv3, meaning that you are free to make your own designs or manufacture devices using these. We expect that if you derive new design, that you publish these, preferably on this website.

The software will also be published with GPLv3, when something is workable.

= Resources =

Colibri

2026-04-19T15:59:53Z

Niclas: /* Architecture Overview */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

<div class="thumb tright">
<div class="thumbinner" style="width: 250px;">
<div style="width: 250px; height: 150px; overflow: hidden; position: relative; background: #000;">
<div style="position: absolute; top: -20px; left: -15px;">
[[File:Colibri_8_photo1.jpg|250px|link=File:Colibri_8_photo1.jpg|alt=Colibri 8 PCB]]
</div>
</div>
</div>
</div>
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri rs485u-2.jpg|180px|thumb]]
[[File:Colibri aic-RevA-2.jpg|180px|thumb]]

Check out the [[Colibri Videos]] on Youtube.

Colibri is a low-cost automation system, primarily intended for building automation, home automation, energy supervision, agriculture supervision and similar systems. Main features beside costs are;
* Flexible I/O system, via MCU modules and I/O modules in M.2 Key E sockets. Many types already developed.
* Power supply of 9-36 Volt, either AC or DC (some I/O cards won't work with DC supply, and some not with AC supply)
* Each I/O slot can be powered-up/down individually from the MCU.
* Each I/O slot is addressable individually.
* MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
* Each I/O module has an 1Mbit EEPROM with calibration parameters and a WebAssembly program for the MCU module to execute.
* Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.

== Architecture Overview ==
<div class="res-img">
[[File:Colibri_Architecture-1.svg|2400px]]
</div>

Colors in this view represents who creates the software for each part.

== Programming ==
The Colibri system is designed around two main external projects, [[Colibri Zephyr|Zephyr]] and WebAssembly ([https://github.com/wasm3/wasm3 wasm3]).

Zephyr provides a lot of ''operating system'' type of features, like task scheduling, concurrency data types, timers, peripheral drivers and cross-platform compatibility to be able to support STM32, RP2354 and possibly other MCU families. And combining that with a WebAssembly environment, we should be able to have a lot of platform independence.

The WebAssembly approach is to allow for;
* I/O modules that are unknown to the MCU module to be installed without re-flashing the firmware,
* Uploading of user programs, without flashing the firmware,
* Sandboxed execution to limit issues that user programs can create,
* Simplified tool chain,
* Deferring the choice of programming languages,
* Future-proofing for programming evolution, option to create our own language.

== Carrier Boards ==
* ''Colibri 3a'' has 2 I/O slots and one MCU slot, one USB-C port to the MCU slot, Jolt Connect pin header for programming.
* ''Colibri 8'' is like the ''Colibri 3a'', but with 7 I/O slots and an isolated RS-485 port to the MCU slot.
* Planned; ''Colibri 8pi'' is like the ''Colibri 8'' but with a full-fledged Raspberry Pi Compute Module 5. 1 Colibri MCU slot and 7 I/O slots,
* Planned; ''Colibri 16pi'' is like the ''Colibri 8pi'', but with 15 I/O slots rather than 7.

== MCU Modules ==
There is a choice, and more will follow;

* ''[[Colibri MCU1]]'' - MCU module with a STM32WLE5, 256kB Flash, 64kB RAM, on-chip LoRa and LoraWAN protocol available in STM32CubeMX.
* ''[[Colibri MCU2]]'' - MCU module with a STM32H562RG, 1024kB Flash, 640kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
* ''[[Colibri MCU6]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.

== I/O Modules ==
The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an [[Colibri_EEPROM_Layout|EEPROM memory]] available to identify which module is present in each I/O slot, links to documentation, calibration parameters, testing results and (up to) 16kB of WebAssembly for the MCU module to execute.

== [[Colibri Form Factor|Form Factor]] ==

Both Colibri I/O modules and MCU modules are 22x42mm and has an edge connector called M.2 Key E, '''but it doesn't follow the M.2 specification for Key E'''. The distance between the I/O slots are specified to 23.5mm,
theoretically making it possible for multi-slot I/O modules (none are planned).

<span style="color:#FF4444">'''WARNING!!! Do NOT plug Colibri I/O modules nor any MCU module into other equipment. Do NOT plug any M.2 card into a Colibri system, unless that card/board is specifically made for Colibri.'''</span>

== Boards ==

{| class=wikitable
|-
! Name
! Type
! Description
! Status
|-
| ''[[Colibri 3a]]''
| Colibri Carrier
| Minimal Colibri carrier board with 2 I/O slots and one MCU slot. MCU slot is to be populated with any of the MCU variants available.
| Active
|-
| ''[[Colibri 8]]''
| Colibri Carrier
| Colibri carrier board with Colibri MCU slot and 7 Colibri I/O slots.
| Early Access
|-
| ''[[Colibri 1dp]]''
| Colibri Carrier
| Minimal Colibri Host with a single MCU slot and 0-500Pa air pressure sensor.
| Prototypes
|-
| ''[[Colibri MCU1]]''
| Host MCU
| MCU module with a STM32WLE5CC, for LoraWAN applications.
| Prototyping
|-
| ''[[Colibri MCU2]]''
| Host MCU
| MCU module with a STM32H562RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU3]]''
| Host MCU
| MCU module with a STM32F405RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU4]]''
| Host MCU
| MCU module with a STM32L475RGTx and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU6]]''
| Host MCU
| MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.
| Prototyping
|-
| ''[[M.2 E Breakout]]''
| M.2 breakout board
| Generic breakout board for M.2 E key boards.
| Prototypes
|-
| ''[[Colibri AIC]]''
| I/O module
| Two analog 0-20mA inputs
| Prototypes
|-
| ''[[Colibri AIV]]''
| I/O module
| Two analog 0-10V inputs
| Prototypes
|-
| ''[[Colibri AQV]]''
| I/O module
| Two analog 0-10V outputs
| Active
|-
| ''[[Colibri DII]]''
| I/O module
| Two ISOLATED digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DIO1]]''
| I/O module
| IEC 61131-2 compliant, 4-channels digital inputs and outputs.
| Prototypes
|-
| ''[[Colibri DIU]]''
| I/O module
| Four digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DP1]]''
| I/O module
| A 0-500Pa air pressure sensor mounted on I/O module.
| Prototyping
|-
| ''[[Colibri FET]]''
| I/O module
| Four digital outputs, FET outputs sinking to GND. Max 1 Amp per channel.
| Prototypes
|-
| ''[[Colibri PID1]]''
| I/O module
| PID regulator, with a PT1000 input and a 0-10V analog output. On-board STM32F030 for host-independent operation.
| Active
|-
| ''[[Colibri Pt1000]]''
| I/O module
| Two PT1000 temperature sensor inputs.
| Active
|-
| ''[[Colibri RS485I]]''
| I/O module
| Isolated RS-485 port. On-board STM32G431KB to implement protocols, such as Modbus RTU.
| Prototyping
|-
| ''[[Colibri RS485U]]''
| I/O module
| Two non-isolated RS-485 ports. On-board STM32F030 implementing Modbus protocol, either as master or slave device.
| Prototypes
|-
| ''[[Colibri SSR]]''
| I/O module
| Two Solid State Relays, ON/OFF.
| Prototypes
|-
| ''[[Colibri TRIAC1]]''
| I/O module
| Four Triac outputs, driving 24V AC.
| Prototyping
|}

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| ''[[Colibri-8pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 7 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|-
| ''[[Colibri-16pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 15 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|}

= License =
All Schematics are licensed with the GPLv3, meaning that you are free to make your own designs or manufacture devices using these. We expect that if you derive new design, that you publish these, preferably on this website.

The software will also be published with GPLv3, when something is workable.

= Resources =

Colibri

2026-04-19T15:58:44Z

Niclas: /* Programming */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

<div class="thumb tright">
<div class="thumbinner" style="width: 250px;">
<div style="width: 250px; height: 150px; overflow: hidden; position: relative; background: #000;">
<div style="position: absolute; top: -20px; left: -15px;">
[[File:Colibri_8_photo1.jpg|250px|link=File:Colibri_8_photo1.jpg|alt=Colibri 8 PCB]]
</div>
</div>
</div>
</div>
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri rs485u-2.jpg|180px|thumb]]
[[File:Colibri aic-RevA-2.jpg|180px|thumb]]

Check out the [[Colibri Videos]] on Youtube.

Colibri is a low-cost automation system, primarily intended for building automation, home automation, energy supervision, agriculture supervision and similar systems. Main features beside costs are;
* Flexible I/O system, via MCU modules and I/O modules in M.2 Key E sockets. Many types already developed.
* Power supply of 9-36 Volt, either AC or DC (some I/O cards won't work with DC supply, and some not with AC supply)
* Each I/O slot can be powered-up/down individually from the MCU.
* Each I/O slot is addressable individually.
* MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
* Each I/O module has an 1Mbit EEPROM with calibration parameters and a WebAssembly program for the MCU module to execute.
* Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.

== Architecture Overview ==
[File:Colibri_Architecture-1.svg]

Colors in this view represents who creates the software for each part.

== Programming ==
The Colibri system is designed around two main external projects, [[Colibri Zephyr|Zephyr]] and WebAssembly ([https://github.com/wasm3/wasm3 wasm3]).

Zephyr provides a lot of ''operating system'' type of features, like task scheduling, concurrency data types, timers, peripheral drivers and cross-platform compatibility to be able to support STM32, RP2354 and possibly other MCU families. And combining that with a WebAssembly environment, we should be able to have a lot of platform independence.

The WebAssembly approach is to allow for;
* I/O modules that are unknown to the MCU module to be installed without re-flashing the firmware,
* Uploading of user programs, without flashing the firmware,
* Sandboxed execution to limit issues that user programs can create,
* Simplified tool chain,
* Deferring the choice of programming languages,
* Future-proofing for programming evolution, option to create our own language.

== Carrier Boards ==
* ''Colibri 3a'' has 2 I/O slots and one MCU slot, one USB-C port to the MCU slot, Jolt Connect pin header for programming.
* ''Colibri 8'' is like the ''Colibri 3a'', but with 7 I/O slots and an isolated RS-485 port to the MCU slot.
* Planned; ''Colibri 8pi'' is like the ''Colibri 8'' but with a full-fledged Raspberry Pi Compute Module 5. 1 Colibri MCU slot and 7 I/O slots,
* Planned; ''Colibri 16pi'' is like the ''Colibri 8pi'', but with 15 I/O slots rather than 7.

== MCU Modules ==
There is a choice, and more will follow;

* ''[[Colibri MCU1]]'' - MCU module with a STM32WLE5, 256kB Flash, 64kB RAM, on-chip LoRa and LoraWAN protocol available in STM32CubeMX.
* ''[[Colibri MCU2]]'' - MCU module with a STM32H562RG, 1024kB Flash, 640kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
* ''[[Colibri MCU6]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.

== I/O Modules ==
The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an [[Colibri_EEPROM_Layout|EEPROM memory]] available to identify which module is present in each I/O slot, links to documentation, calibration parameters, testing results and (up to) 16kB of WebAssembly for the MCU module to execute.

== [[Colibri Form Factor|Form Factor]] ==

Both Colibri I/O modules and MCU modules are 22x42mm and has an edge connector called M.2 Key E, '''but it doesn't follow the M.2 specification for Key E'''. The distance between the I/O slots are specified to 23.5mm,
theoretically making it possible for multi-slot I/O modules (none are planned).

<span style="color:#FF4444">'''WARNING!!! Do NOT plug Colibri I/O modules nor any MCU module into other equipment. Do NOT plug any M.2 card into a Colibri system, unless that card/board is specifically made for Colibri.'''</span>

== Boards ==

{| class=wikitable
|-
! Name
! Type
! Description
! Status
|-
| ''[[Colibri 3a]]''
| Colibri Carrier
| Minimal Colibri carrier board with 2 I/O slots and one MCU slot. MCU slot is to be populated with any of the MCU variants available.
| Active
|-
| ''[[Colibri 8]]''
| Colibri Carrier
| Colibri carrier board with Colibri MCU slot and 7 Colibri I/O slots.
| Early Access
|-
| ''[[Colibri 1dp]]''
| Colibri Carrier
| Minimal Colibri Host with a single MCU slot and 0-500Pa air pressure sensor.
| Prototypes
|-
| ''[[Colibri MCU1]]''
| Host MCU
| MCU module with a STM32WLE5CC, for LoraWAN applications.
| Prototyping
|-
| ''[[Colibri MCU2]]''
| Host MCU
| MCU module with a STM32H562RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU3]]''
| Host MCU
| MCU module with a STM32F405RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU4]]''
| Host MCU
| MCU module with a STM32L475RGTx and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU6]]''
| Host MCU
| MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.
| Prototyping
|-
| ''[[M.2 E Breakout]]''
| M.2 breakout board
| Generic breakout board for M.2 E key boards.
| Prototypes
|-
| ''[[Colibri AIC]]''
| I/O module
| Two analog 0-20mA inputs
| Prototypes
|-
| ''[[Colibri AIV]]''
| I/O module
| Two analog 0-10V inputs
| Prototypes
|-
| ''[[Colibri AQV]]''
| I/O module
| Two analog 0-10V outputs
| Active
|-
| ''[[Colibri DII]]''
| I/O module
| Two ISOLATED digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DIO1]]''
| I/O module
| IEC 61131-2 compliant, 4-channels digital inputs and outputs.
| Prototypes
|-
| ''[[Colibri DIU]]''
| I/O module
| Four digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DP1]]''
| I/O module
| A 0-500Pa air pressure sensor mounted on I/O module.
| Prototyping
|-
| ''[[Colibri FET]]''
| I/O module
| Four digital outputs, FET outputs sinking to GND. Max 1 Amp per channel.
| Prototypes
|-
| ''[[Colibri PID1]]''
| I/O module
| PID regulator, with a PT1000 input and a 0-10V analog output. On-board STM32F030 for host-independent operation.
| Active
|-
| ''[[Colibri Pt1000]]''
| I/O module
| Two PT1000 temperature sensor inputs.
| Active
|-
| ''[[Colibri RS485I]]''
| I/O module
| Isolated RS-485 port. On-board STM32G431KB to implement protocols, such as Modbus RTU.
| Prototyping
|-
| ''[[Colibri RS485U]]''
| I/O module
| Two non-isolated RS-485 ports. On-board STM32F030 implementing Modbus protocol, either as master or slave device.
| Prototypes
|-
| ''[[Colibri SSR]]''
| I/O module
| Two Solid State Relays, ON/OFF.
| Prototypes
|-
| ''[[Colibri TRIAC1]]''
| I/O module
| Four Triac outputs, driving 24V AC.
| Prototyping
|}

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| ''[[Colibri-8pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 7 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|-
| ''[[Colibri-16pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 15 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|}

= License =
All Schematics are licensed with the GPLv3, meaning that you are free to make your own designs or manufacture devices using these. We expect that if you derive new design, that you publish these, preferably on this website.

The software will also be published with GPLv3, when something is workable.

= Resources =

File:Colibri Architecture-1.svg

2026-04-19T15:57:57Z

Niclas: Niclas uploaded a new version of File:Colibri Architecture-1.svg

== Summary ==
One architectural conceptual view of the Colibri system.

File:Colibri Architecture-1.svg

2026-04-19T15:56:43Z

Niclas: One architectural conceptual view of the Colibri system.

== Summary ==
One architectural conceptual view of the Colibri system.

Colibri MCU3

2026-04-17T04:55:00Z

Niclas:

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU3 module}}
[[File:Colibri_mcu3_rev-B_front.jpg|125px|thumb]]
[[File:Colibri_mcu3_rev-B_back.jpg|125px|thumb]]
[[File:Colibri_mcu3_top_right_render.png|250px|thumb]]
[[File:Colibri_mcu3_bot_render.png|250px|thumb]]

[[Colibri]] MCU3 is a processor board for the [[Colibri]] carrier boards. It is an STM32F405RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Hardware =
The MCU3 is a relatively simple MCU module, on an M.2 board with the size 22x42mm and the Key E configuration.

Besides the [[STM32F405|STM32F405RG]] MCU there are also
* 128 Mbits (16MB) flash memory for application use.
* a dual-colored (Green/Red) LED
* 16MHz HSE crystal
* 32768 Hz LSE crystal, intended for calendar functions in the STM32.

'''NOTE: All modules in Colibri are NOT electrically compatible with the M.2 connector standard. DO NOT plug Colibri modules into any M.2 socket other than Colibri (or compatible) ones. And DO NOT plug any M.2 modules (Key E is typically WiFi/BLE) into a Colibri carrier board.

= Programming =
STM32CubeMX file [[Media:Mcu3.ioc|MCU3.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== C/C++ ==
The standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

Use the STM32CubeMX [[File:Mcu3.ioc|mcu.ioc template file]] to get the pinout right from the beginning. (Right-click, "Save link as..." to download it)

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">
[[File:Colibri_mcu3.svg|2400px]]
</div>

== Gallery ==

<gallery>
File:Colibri_mcu3_top_render.png
File:Colibri_mcu3_bot_render.png
File:Colibri_mcu3_top_right_render.png
File:Colibri_mcu3_top_left_render.png
</gallery>

Colibri

2026-04-17T01:44:36Z

Niclas: /* Programming */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

<div class="thumb tright">
<div class="thumbinner" style="width: 250px;">
<div style="width: 250px; height: 150px; overflow: hidden; position: relative; background: #000;">
<div style="position: absolute; top: -20px; left: -15px;">
[[File:Colibri_8_photo1.jpg|250px|link=File:Colibri_8_photo1.jpg|alt=Colibri 8 PCB]]
</div>
</div>
</div>
</div>
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri rs485u-2.jpg|180px|thumb]]
[[File:Colibri aic-RevA-2.jpg|180px|thumb]]

Check out the [[Colibri Videos]] on Youtube.

Colibri is a low-cost automation system, primarily intended for building automation, home automation, energy supervision, agriculture supervision and similar systems. Main features beside costs are;
* Flexible I/O system, via MCU modules and I/O modules in M.2 Key E sockets. Many types already developed.
* Power supply of 9-36 Volt, either AC or DC (some I/O cards won't work with DC supply, and some not with AC supply)
* Each I/O slot can be powered-up/down individually from the MCU.
* Each I/O slot is addressable individually.
* MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
* Each I/O module has an 1Mbit EEPROM with calibration parameters and a WebAssembly program for the MCU module to execute.
* Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.

== Programming ==
The Colibri system is designed around two main external projects, [[Colibri Zephyr|Zephyr]] and WebAssembly ([https://github.com/wasm3/wasm3 wasm3]).

Zephyr provides a lot of ''operating system'' type of features, like task scheduling, concurrency data types, timers, peripheral drivers and cross-platform compatibility to be able to support STM32, RP2354 and possibly other MCU families. And combining that with a WebAssembly environment, we should be able to have a lot of platform independence.

The WebAssembly approach is to allow for;
* I/O modules that are unknown to the MCU module to be installed without re-flashing the firmware,
* Uploading of user programs, without flashing the firmware,
* Sandboxed execution to limit issues that user programs can create,
* Simplified tool chain,
* Deferring the choice of programming languages,
* Future-proofing for programming evolution, option to create our own language.

== Carrier Boards ==
* ''Colibri 3a'' has 2 I/O slots and one MCU slot, one USB-C port to the MCU slot, Jolt Connect pin header for programming.
* ''Colibri 8'' is like the ''Colibri 3a'', but with 7 I/O slots and an isolated RS-485 port to the MCU slot.
* Planned; ''Colibri 8pi'' is like the ''Colibri 8'' but with a full-fledged Raspberry Pi Compute Module 5. 1 Colibri MCU slot and 7 I/O slots,
* Planned; ''Colibri 16pi'' is like the ''Colibri 8pi'', but with 15 I/O slots rather than 7.

== MCU Modules ==
There is a choice, and more will follow;

* ''[[Colibri MCU1]]'' - MCU module with a STM32WLE5, 256kB Flash, 64kB RAM, on-chip LoRa and LoraWAN protocol available in STM32CubeMX.
* ''[[Colibri MCU2]]'' - MCU module with a STM32H562RG, 1024kB Flash, 640kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
* ''[[Colibri MCU6]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.

== I/O Modules ==
The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an [[Colibri_EEPROM_Layout|EEPROM memory]] available to identify which module is present in each I/O slot, links to documentation, calibration parameters, testing results and (up to) 16kB of WebAssembly for the MCU module to execute.

== [[Colibri Form Factor|Form Factor]] ==

Both Colibri I/O modules and MCU modules are 22x42mm and has an edge connector called M.2 Key E, '''but it doesn't follow the M.2 specification for Key E'''. The distance between the I/O slots are specified to 23.5mm,
theoretically making it possible for multi-slot I/O modules (none are planned).

<span style="color:#FF4444">'''WARNING!!! Do NOT plug Colibri I/O modules nor any MCU module into other equipment. Do NOT plug any M.2 card into a Colibri system, unless that card/board is specifically made for Colibri.'''</span>

== Boards ==

{| class=wikitable
|-
! Name
! Type
! Description
! Status
|-
| ''[[Colibri 3a]]''
| Colibri Carrier
| Minimal Colibri carrier board with 2 I/O slots and one MCU slot. MCU slot is to be populated with any of the MCU variants available.
| Active
|-
| ''[[Colibri 8]]''
| Colibri Carrier
| Colibri carrier board with Colibri MCU slot and 7 Colibri I/O slots.
| Early Access
|-
| ''[[Colibri 1dp]]''
| Colibri Carrier
| Minimal Colibri Host with a single MCU slot and 0-500Pa air pressure sensor.
| Prototypes
|-
| ''[[Colibri MCU1]]''
| Host MCU
| MCU module with a STM32WLE5CC, for LoraWAN applications.
| Prototyping
|-
| ''[[Colibri MCU2]]''
| Host MCU
| MCU module with a STM32H562RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU3]]''
| Host MCU
| MCU module with a STM32F405RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU4]]''
| Host MCU
| MCU module with a STM32L475RGTx and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU6]]''
| Host MCU
| MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.
| Prototyping
|-
| ''[[M.2 E Breakout]]''
| M.2 breakout board
| Generic breakout board for M.2 E key boards.
| Prototypes
|-
| ''[[Colibri AIC]]''
| I/O module
| Two analog 0-20mA inputs
| Prototypes
|-
| ''[[Colibri AIV]]''
| I/O module
| Two analog 0-10V inputs
| Prototypes
|-
| ''[[Colibri AQV]]''
| I/O module
| Two analog 0-10V outputs
| Active
|-
| ''[[Colibri DII]]''
| I/O module
| Two ISOLATED digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DIO1]]''
| I/O module
| IEC 61131-2 compliant, 4-channels digital inputs and outputs.
| Prototypes
|-
| ''[[Colibri DIU]]''
| I/O module
| Four digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DP1]]''
| I/O module
| A 0-500Pa air pressure sensor mounted on I/O module.
| Prototyping
|-
| ''[[Colibri FET]]''
| I/O module
| Four digital outputs, FET outputs sinking to GND. Max 1 Amp per channel.
| Prototypes
|-
| ''[[Colibri PID1]]''
| I/O module
| PID regulator, with a PT1000 input and a 0-10V analog output. On-board STM32F030 for host-independent operation.
| Active
|-
| ''[[Colibri Pt1000]]''
| I/O module
| Two PT1000 temperature sensor inputs.
| Active
|-
| ''[[Colibri RS485I]]''
| I/O module
| Isolated RS-485 port. On-board STM32G431KB to implement protocols, such as Modbus RTU.
| Prototyping
|-
| ''[[Colibri RS485U]]''
| I/O module
| Two non-isolated RS-485 ports. On-board STM32F030 implementing Modbus protocol, either as master or slave device.
| Prototypes
|-
| ''[[Colibri SSR]]''
| I/O module
| Two Solid State Relays, ON/OFF.
| Prototypes
|-
| ''[[Colibri TRIAC1]]''
| I/O module
| Four Triac outputs, driving 24V AC.
| Prototyping
|}

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| ''[[Colibri-8pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 7 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|-
| ''[[Colibri-16pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 15 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|}

= License =
All Schematics are licensed with the GPLv3, meaning that you are free to make your own designs or manufacture devices using these. We expect that if you derive new design, that you publish these, preferably on this website.

The software will also be published with GPLv3, when something is workable.

= Resources =

Colibri

2026-04-17T01:35:36Z

Niclas:

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

<div class="thumb tright">
<div class="thumbinner" style="width: 250px;">
<div style="width: 250px; height: 150px; overflow: hidden; position: relative; background: #000;">
<div style="position: absolute; top: -20px; left: -15px;">
[[File:Colibri_8_photo1.jpg|250px|link=File:Colibri_8_photo1.jpg|alt=Colibri 8 PCB]]
</div>
</div>
</div>
</div>
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri rs485u-2.jpg|180px|thumb]]
[[File:Colibri aic-RevA-2.jpg|180px|thumb]]

Check out the [[Colibri Videos]] on Youtube.

Colibri is a low-cost automation system, primarily intended for building automation, home automation, energy supervision, agriculture supervision and similar systems. Main features beside costs are;
* Flexible I/O system, via MCU modules and I/O modules in M.2 Key E sockets. Many types already developed.
* Power supply of 9-36 Volt, either AC or DC (some I/O cards won't work with DC supply, and some not with AC supply)
* Each I/O slot can be powered-up/down individually from the MCU.
* Each I/O slot is addressable individually.
* MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
* Each I/O module has an 1Mbit EEPROM with calibration parameters and a WebAssembly program for the MCU module to execute.
* Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.

== Programming ==
The Colibri system is designed around two main external projects, [[Colibri Zephyr|Zephyr]] and WebAssembly ([https://github.com/wasm3/wasm3 wasm3]).

Zephyr provides a lot of ''operating system'' type of features, like task scheduling, concurrency data types, timers, peripheral drivers and more.

The WebAssembly approach is to allow for;
* I/O modules that are unknown to the MCU module to be installed without re-flashing the firmware,
* Uploading of user programs, without flashing the firmware,
* Sandboxed execution to limit issues that user programs can create,
* Simplified tool chain,
* Deferring the choice of programming languages,
* Future-proofing for programming evolution, option to create our own language.

== Carrier Boards ==
* ''Colibri 3a'' has 2 I/O slots and one MCU slot, one USB-C port to the MCU slot, Jolt Connect pin header for programming.
* ''Colibri 8'' is like the ''Colibri 3a'', but with 7 I/O slots and an isolated RS-485 port to the MCU slot.
* Planned; ''Colibri 8pi'' is like the ''Colibri 8'' but with a full-fledged Raspberry Pi Compute Module 5. 1 Colibri MCU slot and 7 I/O slots,
* Planned; ''Colibri 16pi'' is like the ''Colibri 8pi'', but with 15 I/O slots rather than 7.

== MCU Modules ==
There is a choice, and more will follow;

* ''[[Colibri MCU1]]'' - MCU module with a STM32WLE5, 256kB Flash, 64kB RAM, on-chip LoRa and LoraWAN protocol available in STM32CubeMX.
* ''[[Colibri MCU2]]'' - MCU module with a STM32H562RG, 1024kB Flash, 640kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
* ''[[Colibri MCU6]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.

== I/O Modules ==
The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an [[Colibri_EEPROM_Layout|EEPROM memory]] available to identify which module is present in each I/O slot, links to documentation, calibration parameters, testing results and (up to) 16kB of WebAssembly for the MCU module to execute.

== [[Colibri Form Factor|Form Factor]] ==

Both Colibri I/O modules and MCU modules are 22x42mm and has an edge connector called M.2 Key E, '''but it doesn't follow the M.2 specification for Key E'''. The distance between the I/O slots are specified to 23.5mm,
theoretically making it possible for multi-slot I/O modules (none are planned).

<span style="color:#FF4444">'''WARNING!!! Do NOT plug Colibri I/O modules nor any MCU module into other equipment. Do NOT plug any M.2 card into a Colibri system, unless that card/board is specifically made for Colibri.'''</span>

== Boards ==

{| class=wikitable
|-
! Name
! Type
! Description
! Status
|-
| ''[[Colibri 3a]]''
| Colibri Carrier
| Minimal Colibri carrier board with 2 I/O slots and one MCU slot. MCU slot is to be populated with any of the MCU variants available.
| Active
|-
| ''[[Colibri 8]]''
| Colibri Carrier
| Colibri carrier board with Colibri MCU slot and 7 Colibri I/O slots.
| Early Access
|-
| ''[[Colibri 1dp]]''
| Colibri Carrier
| Minimal Colibri Host with a single MCU slot and 0-500Pa air pressure sensor.
| Prototypes
|-
| ''[[Colibri MCU1]]''
| Host MCU
| MCU module with a STM32WLE5CC, for LoraWAN applications.
| Prototyping
|-
| ''[[Colibri MCU2]]''
| Host MCU
| MCU module with a STM32H562RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU3]]''
| Host MCU
| MCU module with a STM32F405RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU4]]''
| Host MCU
| MCU module with a STM32L475RGTx and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU6]]''
| Host MCU
| MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.
| Prototyping
|-
| ''[[M.2 E Breakout]]''
| M.2 breakout board
| Generic breakout board for M.2 E key boards.
| Prototypes
|-
| ''[[Colibri AIC]]''
| I/O module
| Two analog 0-20mA inputs
| Prototypes
|-
| ''[[Colibri AIV]]''
| I/O module
| Two analog 0-10V inputs
| Prototypes
|-
| ''[[Colibri AQV]]''
| I/O module
| Two analog 0-10V outputs
| Active
|-
| ''[[Colibri DII]]''
| I/O module
| Two ISOLATED digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DIO1]]''
| I/O module
| IEC 61131-2 compliant, 4-channels digital inputs and outputs.
| Prototypes
|-
| ''[[Colibri DIU]]''
| I/O module
| Four digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DP1]]''
| I/O module
| A 0-500Pa air pressure sensor mounted on I/O module.
| Prototyping
|-
| ''[[Colibri FET]]''
| I/O module
| Four digital outputs, FET outputs sinking to GND. Max 1 Amp per channel.
| Prototypes
|-
| ''[[Colibri PID1]]''
| I/O module
| PID regulator, with a PT1000 input and a 0-10V analog output. On-board STM32F030 for host-independent operation.
| Active
|-
| ''[[Colibri Pt1000]]''
| I/O module
| Two PT1000 temperature sensor inputs.
| Active
|-
| ''[[Colibri RS485I]]''
| I/O module
| Isolated RS-485 port. On-board STM32G431KB to implement protocols, such as Modbus RTU.
| Prototyping
|-
| ''[[Colibri RS485U]]''
| I/O module
| Two non-isolated RS-485 ports. On-board STM32F030 implementing Modbus protocol, either as master or slave device.
| Prototypes
|-
| ''[[Colibri SSR]]''
| I/O module
| Two Solid State Relays, ON/OFF.
| Prototypes
|-
| ''[[Colibri TRIAC1]]''
| I/O module
| Four Triac outputs, driving 24V AC.
| Prototyping
|}

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| ''[[Colibri-8pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 7 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|-
| ''[[Colibri-16pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 15 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|}

= License =
All Schematics are licensed with the GPLv3, meaning that you are free to make your own designs or manufacture devices using these. We expect that if you derive new design, that you publish these, preferably on this website.

The software will also be published with GPLv3, when something is workable.

= Resources =

Colibri

2026-04-17T01:29:50Z

Niclas: /* I/O Modules */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

<div class="thumb tright">
<div class="thumbinner" style="width: 250px;">
<div style="width: 250px; height: 150px; overflow: hidden; position: relative; background: #000;">
<div style="position: absolute; top: -20px; left: -15px;">
[[File:Colibri_8_photo1.jpg|250px|link=File:Colibri_8_photo1.jpg|alt=Colibri 8 PCB]]
</div>
</div>
</div>
</div>
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri rs485u-2.jpg|180px|thumb]]
[[File:Colibri aic-RevA-2.jpg|180px|thumb]]

Check out the [[Colibri Videos]] on Youtube.

Colibri is a low-cost automation system, primarily intended for building automation, home automation, energy supervision, agriculture supervision and similar systems. Main features beside costs are;
* Flexible I/O system, via MCU modules and I/O modules in M.2 Key E sockets. Many types already developed.
* Power supply of 9-36 Volt, either AC or DC (some I/O cards won't work with DC supply, and some not with AC supply)
* Each I/O slot can be powered-up/down individually from the MCU.
* Each I/O slot is addressable individually.
* MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
* Each I/O module has an 1Mbit EEPROM with calibration parameters and a Forth program for the MCU module.
* Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.

== Carrier Boards ==
* ''Colibri 3a'' has 2 I/O slots and one MCU slot, one USB-C port to the MCU slot, Jolt Connect pin header for programming.
* ''Colibri 8'' is like the ''Colibri 3a'', but with 7 I/O slots and an isolated RS-485 port to the MCU slot.
* Planned; ''Colibri 8pi'' is like the ''Colibri 8'' but with a full-fledged Raspberry Pi Compute Module 5. 1 Colibri MCU slot and 7 I/O slots,
* Planned; ''Colibri 16pi'' is like the ''Colibri 8pi'', but with 15 I/O slots rather than 7.

== MCU Modules ==
There is a choice, and more will follow;

* ''[[Colibri MCU1]]'' - MCU module with a STM32WLE5, 256kB Flash, 64kB RAM, on-chip LoRa and LoraWAN protocol available in STM32CubeMX.
* ''[[Colibri MCU2]]'' - MCU module with a STM32H562RG, 1024kB Flash, 640kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
* ''[[Colibri MCU6]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.

== I/O Modules ==
The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an [[Colibri_EEPROM_Layout|EEPROM memory]] available to identify which module is present in each I/O slot, links to documentation, calibration parameters, testing results and (up to) 16kB of WebAssembly for the MCU module to execute.

== [[Colibri Form Factor|Form Factor]] ==

Both Colibri I/O modules and MCU modules are 22x42mm and has an edge connector called M.2 Key E, '''but it doesn't follow the M.2 specification for Key E'''. The distance between the I/O slots are specified to 23.5mm,
theoretically making it possible for multi-slot I/O modules (none are planned).

<span style="color:#FF4444">'''WARNING!!! Do NOT plug Colibri I/O modules nor any MCU module into other equipment. Do NOT plug any M.2 card into a Colibri system, unless that card/board is specifically made for Colibri.'''</span>

== Boards ==

{| class=wikitable
|-
! Name
! Type
! Description
! Status
|-
| ''[[Colibri 3a]]''
| Colibri Carrier
| Minimal Colibri carrier board with 2 I/O slots and one MCU slot. MCU slot is to be populated with any of the MCU variants available.
| Active
|-
| ''[[Colibri 8]]''
| Colibri Carrier
| Colibri carrier board with Colibri MCU slot and 7 Colibri I/O slots.
| Early Access
|-
| ''[[Colibri 1dp]]''
| Colibri Carrier
| Minimal Colibri Host with a single MCU slot and 0-500Pa air pressure sensor.
| Prototypes
|-
| ''[[Colibri MCU1]]''
| Host MCU
| MCU module with a STM32WLE5CC, for LoraWAN applications.
| Prototyping
|-
| ''[[Colibri MCU2]]''
| Host MCU
| MCU module with a STM32H562RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU3]]''
| Host MCU
| MCU module with a STM32F405RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU4]]''
| Host MCU
| MCU module with a STM32L475RGTx and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU6]]''
| Host MCU
| MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.
| Prototyping
|-
| ''[[M.2 E Breakout]]''
| M.2 breakout board
| Generic breakout board for M.2 E key boards.
| Prototypes
|-
| ''[[Colibri AIC]]''
| I/O module
| Two analog 0-20mA inputs
| Prototypes
|-
| ''[[Colibri AIV]]''
| I/O module
| Two analog 0-10V inputs
| Prototypes
|-
| ''[[Colibri AQV]]''
| I/O module
| Two analog 0-10V outputs
| Active
|-
| ''[[Colibri DII]]''
| I/O module
| Two ISOLATED digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DIO1]]''
| I/O module
| IEC 61131-2 compliant, 4-channels digital inputs and outputs.
| Prototypes
|-
| ''[[Colibri DIU]]''
| I/O module
| Four digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DP1]]''
| I/O module
| A 0-500Pa air pressure sensor mounted on I/O module.
| Prototyping
|-
| ''[[Colibri FET]]''
| I/O module
| Four digital outputs, FET outputs sinking to GND. Max 1 Amp per channel.
| Prototypes
|-
| ''[[Colibri PID1]]''
| I/O module
| PID regulator, with a PT1000 input and a 0-10V analog output. On-board STM32F030 for host-independent operation.
| Active
|-
| ''[[Colibri Pt1000]]''
| I/O module
| Two PT1000 temperature sensor inputs.
| Active
|-
| ''[[Colibri RS485I]]''
| I/O module
| Isolated RS-485 port. On-board STM32G431KB to implement protocols, such as Modbus RTU.
| Prototyping
|-
| ''[[Colibri RS485U]]''
| I/O module
| Two non-isolated RS-485 ports. On-board STM32F030 implementing Modbus protocol, either as master or slave device.
| Prototypes
|-
| ''[[Colibri SSR]]''
| I/O module
| Two Solid State Relays, ON/OFF.
| Prototypes
|-
| ''[[Colibri TRIAC1]]''
| I/O module
| Four Triac outputs, driving 24V AC.
| Prototyping
|}

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| ''[[Colibri-8pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 7 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|-
| ''[[Colibri-16pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 15 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|}

= License =
All Schematics are licensed with the GPLv3, meaning that you are free to make your own designs or manufacture devices using these. We expect that if you derive new design, that you publish these, preferably on this website.

The software will also be published with GPLv3, when something is workable.

= Resources =

Colibri

2026-04-17T01:24:19Z

Niclas: /* Boards */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

<div class="thumb tright">
<div class="thumbinner" style="width: 250px;">
<div style="width: 250px; height: 150px; overflow: hidden; position: relative; background: #000;">
<div style="position: absolute; top: -20px; left: -15px;">
[[File:Colibri_8_photo1.jpg|250px|link=File:Colibri_8_photo1.jpg|alt=Colibri 8 PCB]]
</div>
</div>
</div>
</div>
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri rs485u-2.jpg|180px|thumb]]
[[File:Colibri aic-RevA-2.jpg|180px|thumb]]

Check out the [[Colibri Videos]] on Youtube.

Colibri is a low-cost automation system, primarily intended for building automation, home automation, energy supervision, agriculture supervision and similar systems. Main features beside costs are;
* Flexible I/O system, via MCU modules and I/O modules in M.2 Key E sockets. Many types already developed.
* Power supply of 9-36 Volt, either AC or DC (some I/O cards won't work with DC supply, and some not with AC supply)
* Each I/O slot can be powered-up/down individually from the MCU.
* Each I/O slot is addressable individually.
* MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
* Each I/O module has an 1Mbit EEPROM with calibration parameters and a Forth program for the MCU module.
* Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.

== Carrier Boards ==
* ''Colibri 3a'' has 2 I/O slots and one MCU slot, one USB-C port to the MCU slot, Jolt Connect pin header for programming.
* ''Colibri 8'' is like the ''Colibri 3a'', but with 7 I/O slots and an isolated RS-485 port to the MCU slot.
* Planned; ''Colibri 8pi'' is like the ''Colibri 8'' but with a full-fledged Raspberry Pi Compute Module 5. 1 Colibri MCU slot and 7 I/O slots,
* Planned; ''Colibri 16pi'' is like the ''Colibri 8pi'', but with 15 I/O slots rather than 7.

== MCU Modules ==
There is a choice, and more will follow;

* ''[[Colibri MCU1]]'' - MCU module with a STM32WLE5, 256kB Flash, 64kB RAM, on-chip LoRa and LoraWAN protocol available in STM32CubeMX.
* ''[[Colibri MCU2]]'' - MCU module with a STM32H562RG, 1024kB Flash, 640kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
* ''[[Colibri MCU6]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.

== I/O Modules ==
The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an EEPROM memory available to identify which module is present in each I/O slot. Furthermore, there is a ''[[zeptoforth]]'' program located in the EEPROM that contains the functionality of the module, executed in the MCU module. This allows for future I/O modules without requiring the upgrade of the MCU module. You might want to use other [[Colibri Programming Languages]], if Forth does not suit your needs.

NOTE; '''''[[zeptoforth]]''''' is only available/supported for the ''Colibri MCU3'' at the moment, while support for ''Colibri MCU4'' and ''Colibri MCU5'' will be coming soon.

== [[Colibri Form Factor|Form Factor]] ==

Both Colibri I/O modules and MCU modules are 22x42mm and has an edge connector called M.2 Key E, '''but it doesn't follow the M.2 specification for Key E'''. The distance between the I/O slots are specified to 23.5mm,
theoretically making it possible for multi-slot I/O modules (none are planned).

<span style="color:#FF4444">'''WARNING!!! Do NOT plug Colibri I/O modules nor any MCU module into other equipment. Do NOT plug any M.2 card into a Colibri system, unless that card/board is specifically made for Colibri.'''</span>

== Boards ==

{| class=wikitable
|-
! Name
! Type
! Description
! Status
|-
| ''[[Colibri 3a]]''
| Colibri Carrier
| Minimal Colibri carrier board with 2 I/O slots and one MCU slot. MCU slot is to be populated with any of the MCU variants available.
| Active
|-
| ''[[Colibri 8]]''
| Colibri Carrier
| Colibri carrier board with Colibri MCU slot and 7 Colibri I/O slots.
| Early Access
|-
| ''[[Colibri 1dp]]''
| Colibri Carrier
| Minimal Colibri Host with a single MCU slot and 0-500Pa air pressure sensor.
| Prototypes
|-
| ''[[Colibri MCU1]]''
| Host MCU
| MCU module with a STM32WLE5CC, for LoraWAN applications.
| Prototyping
|-
| ''[[Colibri MCU2]]''
| Host MCU
| MCU module with a STM32H562RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU3]]''
| Host MCU
| MCU module with a STM32F405RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU4]]''
| Host MCU
| MCU module with a STM32L475RGTx and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU6]]''
| Host MCU
| MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.
| Prototyping
|-
| ''[[M.2 E Breakout]]''
| M.2 breakout board
| Generic breakout board for M.2 E key boards.
| Prototypes
|-
| ''[[Colibri AIC]]''
| I/O module
| Two analog 0-20mA inputs
| Prototypes
|-
| ''[[Colibri AIV]]''
| I/O module
| Two analog 0-10V inputs
| Prototypes
|-
| ''[[Colibri AQV]]''
| I/O module
| Two analog 0-10V outputs
| Active
|-
| ''[[Colibri DII]]''
| I/O module
| Two ISOLATED digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DIO1]]''
| I/O module
| IEC 61131-2 compliant, 4-channels digital inputs and outputs.
| Prototypes
|-
| ''[[Colibri DIU]]''
| I/O module
| Four digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DP1]]''
| I/O module
| A 0-500Pa air pressure sensor mounted on I/O module.
| Prototyping
|-
| ''[[Colibri FET]]''
| I/O module
| Four digital outputs, FET outputs sinking to GND. Max 1 Amp per channel.
| Prototypes
|-
| ''[[Colibri PID1]]''
| I/O module
| PID regulator, with a PT1000 input and a 0-10V analog output. On-board STM32F030 for host-independent operation.
| Active
|-
| ''[[Colibri Pt1000]]''
| I/O module
| Two PT1000 temperature sensor inputs.
| Active
|-
| ''[[Colibri RS485I]]''
| I/O module
| Isolated RS-485 port. On-board STM32G431KB to implement protocols, such as Modbus RTU.
| Prototyping
|-
| ''[[Colibri RS485U]]''
| I/O module
| Two non-isolated RS-485 ports. On-board STM32F030 implementing Modbus protocol, either as master or slave device.
| Prototypes
|-
| ''[[Colibri SSR]]''
| I/O module
| Two Solid State Relays, ON/OFF.
| Prototypes
|-
| ''[[Colibri TRIAC1]]''
| I/O module
| Four Triac outputs, driving 24V AC.
| Prototyping
|}

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| ''[[Colibri-8pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 7 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|-
| ''[[Colibri-16pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 15 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|}

= License =
All Schematics are licensed with the GPLv3, meaning that you are free to make your own designs or manufacture devices using these. We expect that if you derive new design, that you publish these, preferably on this website.

The software will also be published with GPLv3, when something is workable.

= Resources =

Colibri

2026-04-17T01:23:56Z

Niclas: /* MCU Modules */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri Automation System}}

<div class="thumb tright">
<div class="thumbinner" style="width: 250px;">
<div style="width: 250px; height: 150px; overflow: hidden; position: relative; background: #000;">
<div style="position: absolute; top: -20px; left: -15px;">
[[File:Colibri_8_photo1.jpg|250px|link=File:Colibri_8_photo1.jpg|alt=Colibri 8 PCB]]
</div>
</div>
</div>
</div>
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri rs485u-2.jpg|180px|thumb]]
[[File:Colibri aic-RevA-2.jpg|180px|thumb]]

Check out the [[Colibri Videos]] on Youtube.

Colibri is a low-cost automation system, primarily intended for building automation, home automation, energy supervision, agriculture supervision and similar systems. Main features beside costs are;
* Flexible I/O system, via MCU modules and I/O modules in M.2 Key E sockets. Many types already developed.
* Power supply of 9-36 Volt, either AC or DC (some I/O cards won't work with DC supply, and some not with AC supply)
* Each I/O slot can be powered-up/down individually from the MCU.
* Each I/O slot is addressable individually.
* MCU communicates with each I/O slot via I2C and/or SPI. The I2C bus is multiplexed to avoid address collision. SPI uses one Chip Select per I/O slot and 2 additional Chip Select if multi SPI devices are on a single I/O module.
* Each I/O module has an 1Mbit EEPROM with calibration parameters and a Forth program for the MCU module.
* Some I/O modules have on-board secondary processors for time-critical or other reasons, for instance RS-485 communication, digital inputs (pulse counting) and PID regulator.

== Carrier Boards ==
* ''Colibri 3a'' has 2 I/O slots and one MCU slot, one USB-C port to the MCU slot, Jolt Connect pin header for programming.
* ''Colibri 8'' is like the ''Colibri 3a'', but with 7 I/O slots and an isolated RS-485 port to the MCU slot.
* Planned; ''Colibri 8pi'' is like the ''Colibri 8'' but with a full-fledged Raspberry Pi Compute Module 5. 1 Colibri MCU slot and 7 I/O slots,
* Planned; ''Colibri 16pi'' is like the ''Colibri 8pi'', but with 15 I/O slots rather than 7.

== MCU Modules ==
There is a choice, and more will follow;

* ''[[Colibri MCU1]]'' - MCU module with a STM32WLE5, 256kB Flash, 64kB RAM, on-chip LoRa and LoraWAN protocol available in STM32CubeMX.
* ''[[Colibri MCU2]]'' - MCU module with a STM32H562RG, 1024kB Flash, 640kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU3]]'' - MCU module with a STM32F405RG, 1MB Flash, 192kB+4kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU4]]'' - MCU module with a STM32L475RG, 1MB Flash, 128kB RAM and a 16MB external flash memory.
* ''[[Colibri MCU5]]'' - (deprecated) MCU module with a STM32F103RE, 512kB Flash and 64kB RAM. No external flash memory.
* ''[[Colibri MCU6]]'' - MCU module with a RP2354B, 2MB Flash, 192kB+4kB RAM and a 16MB external flash memory.

== I/O Modules ==
The Colibri system is based around the M.2 connector and a non-standard bus for I2C and SPI communications. Each I/O module has an EEPROM memory available to identify which module is present in each I/O slot. Furthermore, there is a ''[[zeptoforth]]'' program located in the EEPROM that contains the functionality of the module, executed in the MCU module. This allows for future I/O modules without requiring the upgrade of the MCU module. You might want to use other [[Colibri Programming Languages]], if Forth does not suit your needs.

NOTE; '''''[[zeptoforth]]''''' is only available/supported for the ''Colibri MCU3'' at the moment, while support for ''Colibri MCU4'' and ''Colibri MCU5'' will be coming soon.

== [[Colibri Form Factor|Form Factor]] ==

Both Colibri I/O modules and MCU modules are 22x42mm and has an edge connector called M.2 Key E, '''but it doesn't follow the M.2 specification for Key E'''. The distance between the I/O slots are specified to 23.5mm,
theoretically making it possible for multi-slot I/O modules (none are planned).

<span style="color:#FF4444">'''WARNING!!! Do NOT plug Colibri I/O modules nor any MCU module into other equipment. Do NOT plug any M.2 card into a Colibri system, unless that card/board is specifically made for Colibri.'''</span>

== Boards ==

{| class=wikitable
|-
! Name
! Type
! Description
! Status
|-
| ''[[Colibri 3a]]''
| Colibri Carrier
| Minimal Colibri carrier board with 2 I/O slots and one MCU slot. MCU slot is to be populated with any of the MCU variants available.
| Active
|-
| ''[[Colibri 8]]''
| Colibri Carrier
| Colibri carrier board with Colibri MCU slot and 7 Colibri I/O slots.
| Early Access
|-
| ''[[Colibri 1dp]]''
| Colibri Carrier
| Minimal Colibri Host with a single MCU slot and 0-500Pa air pressure sensor.
| Prototypes
|-
| ''[[Colibri MCU1]]''
| Host MCU
| MCU module with a STM32WLE5CC, for LoraWAN applications.
| Prototyping
|-
| ''[[Colibri MCU2]]''
| Host MCU
| MCU module with a STM32H562RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU3]]''
| Host MCU
| MCU module with a STM32F405RG and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU4]]''
| Host MCU
| MCU module with a STM32L475RGTx and a 16MB flash memory.
| Prototyping
|-
| ''[[Colibri MCU5]]''
| Host MCU
| MCU module with a Raspberry Pi RP2354B and a 16MB flash memory.
| Prototyping
|-
| ''[[M.2 E Breakout]]''
| M.2 breakout board
| Generic breakout board for M.2 E key boards.
| Prototypes
|-
| ''[[Colibri AIC]]''
| I/O module
| Two analog 0-20mA inputs
| Prototypes
|-
| ''[[Colibri AIV]]''
| I/O module
| Two analog 0-10V inputs
| Prototypes
|-
| ''[[Colibri AQV]]''
| I/O module
| Two analog 0-10V outputs
| Active
|-
| ''[[Colibri DII]]''
| I/O module
| Two ISOLATED digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DIO1]]''
| I/O module
| IEC 61131-2 compliant, 4-channels digital inputs and outputs.
| Prototypes
|-
| ''[[Colibri DIU]]''
| I/O module
| Four digital inputs, for state, counter, pulsewidth measurement. On-board STM32F030 for ability to count very fast pulses and high accuracy PWM measurements.
| Prototypes
|-
| ''[[Colibri DP1]]''
| I/O module
| A 0-500Pa air pressure sensor mounted on I/O module.
| Prototyping
|-
| ''[[Colibri FET]]''
| I/O module
| Four digital outputs, FET outputs sinking to GND. Max 1 Amp per channel.
| Prototypes
|-
| ''[[Colibri PID1]]''
| I/O module
| PID regulator, with a PT1000 input and a 0-10V analog output. On-board STM32F030 for host-independent operation.
| Active
|-
| ''[[Colibri Pt1000]]''
| I/O module
| Two PT1000 temperature sensor inputs.
| Active
|-
| ''[[Colibri RS485I]]''
| I/O module
| Isolated RS-485 port. On-board STM32G431KB to implement protocols, such as Modbus RTU.
| Prototyping
|-
| ''[[Colibri RS485U]]''
| I/O module
| Two non-isolated RS-485 ports. On-board STM32F030 implementing Modbus protocol, either as master or slave device.
| Prototypes
|-
| ''[[Colibri SSR]]''
| I/O module
| Two Solid State Relays, ON/OFF.
| Prototypes
|-
| ''[[Colibri TRIAC1]]''
| I/O module
| Four Triac outputs, driving 24V AC.
| Prototyping
|}

== Planned Boards ==

{| class=wikitable
|-
!
! Name
! Type
! Description
! Status
|-
| ''[[Colibri-8pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 7 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|-
| ''[[Colibri-16pi]]''
| Carrier board
| Colibri carrier board with Raspberry Pi CM5, Colibri MCU slot, 15 Colibri I/O slots, two Ethernet ports, 3 USB ports and SDcard connector.
| Planned
|}

= License =
All Schematics are licensed with the GPLv3, meaning that you are free to make your own designs or manufacture devices using these. We expect that if you derive new design, that you publish these, preferably on this website.

The software will also be published with GPLv3, when something is workable.

= Resources =

Colibri MCU5

2026-04-17T01:20:33Z

Niclas: /* Programming */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU5 module}}
[[File:Colibri-mcu5-revB-photo-front.png|180px|thumb]]

[[Colibri]] MCU5 is a processor board for the [[Colibri]] carrier boards. It uses a Raspberry Pi RP2354A as the MCU.

= Programming =

== C/C++ ==

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

= Documentation =

Colibri MCU2

2026-04-17T01:19:55Z

Niclas: /* Programming */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU2 module}}
[[Colibri]] MCU2 is a processor board for the [[Colibri]] carrier boards. It is an STM32H562RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Programming =
STM32CubeMX file [[Media:Mcu2.ioc|mcu2.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== ''zeptoforth'' ==
The MCU2 does NOT come preloaded with the [[zeptoforth]] programming language and environment. We intend to assist the ''zeptoforth'' project to achieve this. Stay tuned for updates.

== C/C++ ==
The standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">

</div>

== Gallery ==

<gallery>
</gallery>

Colibri MCU4

2026-04-17T01:19:37Z

Niclas: /* Programming */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU4 module}}

[[Colibri]] MCU4 is a processor board for the [[Colibri]] carrier boards. It is simply an STM32L475RE to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Programming =
STM32CubeMX file [[Media:Mcu4.ioc|mcu4.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective development environment.

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== C/C++ ==
If Forth is not your cup of tea, the standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

= Documentation =

Colibri MCU2

2026-04-17T01:19:04Z

Niclas: /* Programming */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU2 module}}
[[Colibri]] MCU2 is a processor board for the [[Colibri]] carrier boards. It is an STM32H562RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Programming =
STM32CubeMX file [[Media:Mcu2.ioc|MCU2.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== ''zeptoforth'' ==
The MCU2 does NOT come preloaded with the [[zeptoforth]] programming language and environment. We intend to assist the ''zeptoforth'' project to achieve this. Stay tuned for updates.

== C/C++ ==
The standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">

</div>

== Gallery ==

<gallery>
</gallery>

Colibri MCU2

2026-04-17T01:18:39Z

Niclas: /* Programming */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU2 module}}
[[Colibri]] MCU2 is a processor board for the [[Colibri]] carrier boards. It is an STM32H562RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Programming =
STM32CubeMX file [[Media:Mcu2.ioc|MCU3.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== ''zeptoforth'' ==
The MCU2 does NOT come preloaded with the [[zeptoforth]] programming language and environment. We intend to assist the ''zeptoforth'' project to achieve this. Stay tuned for updates.

== C/C++ ==
The standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">

</div>

== Gallery ==

<gallery>
</gallery>

Colibri MCU3

2026-04-17T01:16:42Z

Niclas: /* C/C++ */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU3 module}}
[[File:Colibri_mcu3_rev-B_front.jpg|125px|thumb]]
[[File:Colibri_mcu3_rev-B_back.jpg|125px|thumb]]
[[File:Colibri_mcu3_top_right_render.png|250px|thumb]]
[[File:Colibri_mcu3_bot_render.png|250px|thumb]]

[[Colibri]] MCU3 is a processor board for the [[Colibri]] carrier boards. It is an STM32F405RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Hardware =
The MCU3 is a relatively simple MCU module, on an M.2 board with the size 22x42mm and the Key E configuration.

Besides the [[STM32F405|STM32F405RE]] MCU there are also
* 128 Mbits (16MB) flash memory for application use.
* a dual-colored (Green/Red) LED
* 16MHz HSE crystal
* 32768 Hz LSE crystal, intended for calendar functions in the STM32.

'''NOTE: All modules in Colibri are NOT electrically compatible with the M.2 connector standard. DO NOT plug Colibri modules into any M.2 socket other than Colibri (or compatible) ones. And DO NOT plug any M.2 modules (Key E is typically WiFi/BLE) into a Colibri carrier board.

= Programming =
STM32CubeMX file [[Media:Mcu3.ioc|MCU3.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== C/C++ ==
The standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

Use the STM32CubeMX [[File:Mcu3.ioc|mcu.ioc template file]] to get the pinout right from the beginning. (Right-click, "Save link as..." to download it)

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">
[[File:Colibri_mcu3.svg|2400px]]
</div>

== Gallery ==

<gallery>
File:Colibri_mcu3_top_render.png
File:Colibri_mcu3_bot_render.png
File:Colibri_mcu3_top_right_render.png
File:Colibri_mcu3_top_left_render.png
</gallery>

Colibri MCU3

2026-04-17T01:16:22Z

Niclas: /* C/C++ */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU3 module}}
[[File:Colibri_mcu3_rev-B_front.jpg|125px|thumb]]
[[File:Colibri_mcu3_rev-B_back.jpg|125px|thumb]]
[[File:Colibri_mcu3_top_right_render.png|250px|thumb]]
[[File:Colibri_mcu3_bot_render.png|250px|thumb]]

[[Colibri]] MCU3 is a processor board for the [[Colibri]] carrier boards. It is an STM32F405RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Hardware =
The MCU3 is a relatively simple MCU module, on an M.2 board with the size 22x42mm and the Key E configuration.

Besides the [[STM32F405|STM32F405RE]] MCU there are also
* 128 Mbits (16MB) flash memory for application use.
* a dual-colored (Green/Red) LED
* 16MHz HSE crystal
* 32768 Hz LSE crystal, intended for calendar functions in the STM32.

'''NOTE: All modules in Colibri are NOT electrically compatible with the M.2 connector standard. DO NOT plug Colibri modules into any M.2 socket other than Colibri (or compatible) ones. And DO NOT plug any M.2 modules (Key E is typically WiFi/BLE) into a Colibri carrier board.

= Programming =
STM32CubeMX file [[Media:Mcu3.ioc|MCU3.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== C/C++ ==
The standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

Use the STM32CubeMX [[File:Mcu.ioc|mcu.ioc template file]] to get the pinout right from the beginning. (Right-click, "Save link as..." to download it)

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">
[[File:Colibri_mcu3.svg|2400px]]
</div>

== Gallery ==

<gallery>
File:Colibri_mcu3_top_render.png
File:Colibri_mcu3_bot_render.png
File:Colibri_mcu3_top_right_render.png
File:Colibri_mcu3_top_left_render.png
</gallery>

Colibri 3a

2026-04-17T01:13:14Z

Niclas: /* MCU slot */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Coliri 3a carrier board}}

Minimal Colibri carrier board with 1 MCU slot and 2 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri_3a_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that. There is
nothing connected to the USART1 port.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* 16MB flash memory
* 128kB EEPROM memory

== I/O module slots ==
There are two I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
There are others.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

=== I2C Addresses ===
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

; Slot 0 is selected in MUX (TCA9548)
TCA6424 = 0x22 ; IO Expander for RESET, POWER and SPI select
M24M01 = 0x50-0x51 ; 1 Mbit of EEPROM

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

= Architecture =
[[File:Architecture-colibri-3a.svg]]

= Documentation =
* [[File:Colibri 3-RevC-pcb.pdf|thumb|Colibri 3 PCB]]
* [[File:Colibri 3-RevC-schematics.pdf|thumb|Colibri 3 Schematics]]

Colibri 3a

2026-04-17T01:12:54Z

Niclas: /* I2C communications */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Coliri 3a carrier board}}

Minimal Colibri carrier board with 1 MCU slot and 2 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri-3-6.jpg|thumb|250px]]
[[File:Colibri_3a_photo1.jpg|thumb|250px]]
[[File:Colibri_3a_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that. There is
nothing connected to the USART1 port.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* 16MB flash memory
* 128kB EEPROM memory on carrier board

== I/O module slots ==
There are two I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
There are others.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

=== I2C Addresses ===
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

; Slot 0 is selected in MUX (TCA9548)
TCA6424 = 0x22 ; IO Expander for RESET, POWER and SPI select
M24M01 = 0x50-0x51 ; 1 Mbit of EEPROM

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

= Architecture =
[[File:Architecture-colibri-3a.svg]]

= Documentation =
* [[File:Colibri 3-RevC-pcb.pdf|thumb|Colibri 3 PCB]]
* [[File:Colibri 3-RevC-schematics.pdf|thumb|Colibri 3 Schematics]]

Colibri 8

2026-04-17T01:11:08Z

Niclas: /* MCU slot */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 8'' are powered by an AC source.
Also [[Colibri DIO1]] must '''NOT''' be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 8'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 8'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 8'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 8'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

; Slot 0 is selected in MUX (TCA9548)
TCA6424 = 0x22 ; IO Expander for RESET, POWER and SPI select
M24M01 = 0x50-0x51 ; 1 Mbit of EEPROM

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-IO_Expansion.svg|2400px]]
[[File:Colibri 8-IO Expansion-X1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

Colibri 8

2026-04-17T01:03:21Z

Niclas: /* I/O slot power */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 8'' are powered by an AC source.
Also [[Colibri DIO1]] must '''NOT''' be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 8'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 8'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 8'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 8'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

; Slot 0 is selected in MUX (TCA9548)
TCA6424 = 0x22 ; IO Expander for RESET, POWER and SPI select
M24M01 = 0x50-0x51 ; 1 Mbit of EEPROM

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-IO_Expansion.svg|2400px]]
[[File:Colibri 8-IO Expansion-X1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

Colibri 8

2026-04-17T01:03:03Z

Niclas: /* I/O slot power */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 8'' are powered by an AC source.
Also [[Colibri DIO1]] must '''NOT''' be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 8'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 8'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 8'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

; Slot 0 is selected in MUX (TCA9548)
TCA6424 = 0x22 ; IO Expander for RESET, POWER and SPI select
M24M01 = 0x50-0x51 ; 1 Mbit of EEPROM

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-IO_Expansion.svg|2400px]]
[[File:Colibri 8-IO Expansion-X1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

Colibri 8

2026-04-17T01:02:47Z

Niclas: /* I2C communications */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 8'' are powered by an AC source.
Also [[Colibri DIO1]] must '''NOT''' be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 8'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

; Slot 0 is selected in MUX (TCA9548)
TCA6424 = 0x22 ; IO Expander for RESET, POWER and SPI select
M24M01 = 0x50-0x51 ; 1 Mbit of EEPROM

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-IO_Expansion.svg|2400px]]
[[File:Colibri 8-IO Expansion-X1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

Colibri 8

2026-04-17T01:02:08Z

Niclas: /* I/O module slots */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 8'' are powered by an AC source.
Also [[Colibri DIO1]] must '''NOT''' be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

; Slot 0 is selected in MUX (TCA9548)
TCA6424 = 0x22 ; IO Expander for RESET, POWER and SPI select
M24M01 = 0x50-0x51 ; 1 Mbit of EEPROM

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-IO_Expansion.svg|2400px]]
[[File:Colibri 8-IO Expansion-X1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

Colibri 8

2026-04-17T00:58:34Z

Niclas: /* I2C Addresses */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
Also [[Colibri DIO1]] must NOT be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

; Slot 0 is selected in MUX (TCA9548)
TCA6424 = 0x22 ; IO Expander for RESET, POWER and SPI select
M24M01 = 0x50-0x51 ; 1 Mbit of EEPROM

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-IO_Expansion.svg|2400px]]
[[File:Colibri 8-IO Expansion-X1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

Colibri 8

2026-04-17T00:53:09Z

Niclas: /* Schematics */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
Also [[Colibri DIO1]] must NOT be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-IO_Expansion.svg|2400px]]
[[File:Colibri 8-IO Expansion-X1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

File:Colibri 8-IO Expansion-X1.svg

2026-04-17T00:52:45Z

Niclas: Schematics of the I/O slot on Colibri 8. This is repeated 7 times.

== Summary ==
Schematics of the I/O slot on Colibri 8. This is repeated 7 times.

File:Colibri 8-IO Expansion.svg

2026-04-17T00:51:35Z

Niclas: Schematics of the I/O subsystem on Colibri 8

== Summary ==
Schematics of the I/O subsystem on Colibri 8

Colibri 8

2026-04-17T00:50:42Z

Niclas: /* Documentation */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
Also [[Colibri DIO1]] must NOT be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

Colibri 8

2026-04-17T00:50:12Z

Niclas: /* Documentation */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
Also [[Colibri DIO1]] must NOT be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics1.pdf|Colibri 8 Schematics]]

Colibri 8

2026-04-17T00:49:40Z

Niclas: /* Schematics */

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
Also [[Colibri DIO1]] must NOT be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics1.svg|2400px]]
[[File:Colibri_8-Power Supply.svg|2400px]]
[[File:Colibri 8-IO Expansion-LEDs.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

File:Colibri 8-IO Expansion-LEDs.svg

2026-04-17T00:47:18Z

Niclas: Schematics for Colibri_8 IO Expansion, LEDs

== Summary ==
Schematics for Colibri_8 IO Expansion, LEDs

File:Colibri 8-Power Supply.svg

2026-04-17T00:46:14Z

Niclas: Colibri 8 powers supply schematics

== Summary ==
Colibri 8 powers supply schematics

File:Colibri 8-rev A-schematics1.svg

2026-04-17T00:44:56Z

Niclas: Colibri schematics 1

== Summary ==
Colibri schematics 1

Colibri 8

2026-04-17T00:43:36Z

Niclas:

[[Category:Colibri]][[Category:Work in progress]]{{metadesc|Colibri 8 carrier board}}

DIN-rail mounted Colibri carrier board with 1 MCU slot and 7 I/O clots. MCU slot is to be populated with any of the MCU variants available.
[[File:Colibri_8_photo1.jpg|thumb|250px]]
[[File:Colibri_8_photo2.jpg|thumb|250px]]

= Features =

== MCU slot ==
The MCU slot is the standard [[Colibri MCU slot]] for accepting any of the available MCU modules. The MCU module can
be programmed in many different ways, and see the [[Colibri Programming Languages]] page for details on that.

The MCU in the MCU slot will be the manager of all the hardware resources;
* SPI bus and SPI slot select device
* I2C bus and I2C Mux
* Galvanically Isolated RS-485 port, for SCADA and other supervisory systems.
* 16MB flash memory
* 128kB EEPROM memory on carrier board
* Temperature and Humidity sensor

== I/O module slots ==
There are seven I/O module slots on this carrier board. Most I/O modules can be used, but there are I/O modules that
will depend on the power supply, for instance [[Colibri Triac1]] will only work if the ''Colibri 3a'' are powered by an AC source.
Also [[Colibri DIO1]] must NOT be used on systems with AC power supply.

== I2C communications ==
The I2C bus from the MCU module must be multiplexed to allow for many I/O modules of the same type to be used in different I/O slots.

The multiplexer is a TCA9548APWR on address 0x70 (0b1110000x), and each bit in the "data byte" written to the multiplexer will enable
that I/O slot's I2C bus. I2C bus 0 is the ''Colibri 3a'' carrier board itself, i.e. to the EEPROM. It is important that only one I2C
bus is enable at a time.

== SPI communications ==
Each I/O slot has a SPI Chip Select (CS, active low) individually addressable, and two shared chip selects
(no defined state, I/O module dependent, often unused) for addressing more than one SPI device on a single I/O module.

SPI communications happens at 1Mbps by default.

== I/O slot power ==
Each I/O slot has +3.3V, +5V and +12V available on the connector. On the ''Colibri 3a'' the power for +3.3V and +5V can be turned on/off
individually by the MCU, meaning the MCU can for instance turn off the +5V on X2, for instance to re-initialize some circuit.

Additionally, the external power that is used to power the ''Colibri 3a'' device is also available on the I/O slot header. This is how some
I/O modules become dependent on the type of power that drives the ''Colibri 3a'', for instance the [[Colibri DIO1]] that will malfunction and
possibly break if AC voltage is used.

== Power input ==
The built-in power supply is versatile and accepts either AC or DC voltages, over a vast range;

* 7-36 Volt AC
* 6-50 Volt DC

== USB-C port ==
There is a USB-C port for upstream communication with PC or other devices, typically used for Service and Maintenance.

== Jolt Connect programming header ==
A standard Jolt Connect compatible programming header is available. The device will NOT be powered through that header.

= I2C Addresses =
TCA9548 = 0x70 ; Selects which I/O slot the I2C should be connected to.

= Architecture =
[[File:Architecture-colibri-8.svg]]

= Schematics =
<div class="res-img">
[[File:Colibri_8-rev_A-schematics.svg|2400px]]
</div>

= Errata =
* In Revision A, the secondary USART on the MCU slot was not yet defined, so the RS-485 transceiver is connected to the programming USART (USART2). This has been corrected for later revisions.

= Documentation =
[[File:Colibri_8-rev_A-schematics.pdf|Colibri 8 Schematics]]

Colibri MCU3

2026-04-17T00:16:24Z

Niclas: /* Hardware */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU3 module}}
[[File:Colibri_mcu3_rev-B_front.jpg|125px|thumb]]
[[File:Colibri_mcu3_rev-B_back.jpg|125px|thumb]]
[[File:Colibri_mcu3_top_right_render.png|250px|thumb]]
[[File:Colibri_mcu3_bot_render.png|250px|thumb]]

[[Colibri]] MCU3 is a processor board for the [[Colibri]] carrier boards. It is an STM32F405RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Hardware =
The MCU3 is a relatively simple MCU module, on an M.2 board with the size 22x42mm and the Key E configuration.

Besides the [[STM32F405|STM32F405RE]] MCU there are also
* 128 Mbits (16MB) flash memory for application use.
* a dual-colored (Green/Red) LED
* 16MHz HSE crystal
* 32768 Hz LSE crystal, intended for calendar functions in the STM32.

'''NOTE: All modules in Colibri are NOT electrically compatible with the M.2 connector standard. DO NOT plug Colibri modules into any M.2 socket other than Colibri (or compatible) ones. And DO NOT plug any M.2 modules (Key E is typically WiFi/BLE) into a Colibri carrier board.

= Programming =
STM32CubeMX file [[Media:Mcu3.ioc|MCU3.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== C/C++ ==
If Forth is not your cup of tea, the standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">
[[File:Colibri_mcu3.svg|2400px]]
</div>

== Gallery ==

<gallery>
File:Colibri_mcu3_top_render.png
File:Colibri_mcu3_bot_render.png
File:Colibri_mcu3_top_right_render.png
File:Colibri_mcu3_top_left_render.png
</gallery>

Colibri MCU3

2026-04-17T00:15:52Z

Niclas: /* Hardware */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU3 module}}
[[File:Colibri_mcu3_rev-B_front.jpg|125px|thumb]]
[[File:Colibri_mcu3_rev-B_back.jpg|125px|thumb]]
[[File:Colibri_mcu3_top_right_render.png|250px|thumb]]
[[File:Colibri_mcu3_bot_render.png|250px|thumb]]

[[Colibri]] MCU3 is a processor board for the [[Colibri]] carrier boards. It is an STM32F405RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Hardware =
The MCU3 is a relatively simple MCU module, on an M.2 board with the size 22x42mm and the Key E configuration.

Besides the [[STM32F405|STM32F405RE]] MCU there are also
* 128 Mbits (16MB) flash memory for application use.
* a dual-colored (Green/Red) LED
* 16MHz HSE crystal
* 32768 Hz LSE crystal, intended for calendar functions in the STM32.

'''NOTE: All modules in Colibri are NOT compatible with the M.2 connector standard. DO NOT plug Colibri modules into any M.2 socket other than Colibri (or compatible) ones. And DO NOT plug any M.2 modules (Key E is typically WiFi/BLE) into a Colibri carrier board.

= Programming =
STM32CubeMX file [[Media:Mcu3.ioc|MCU3.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== C/C++ ==
If Forth is not your cup of tea, the standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">
[[File:Colibri_mcu3.svg|2400px]]
</div>

== Gallery ==

<gallery>
File:Colibri_mcu3_top_render.png
File:Colibri_mcu3_bot_render.png
File:Colibri_mcu3_top_right_render.png
File:Colibri_mcu3_top_left_render.png
</gallery>

Colibri MCU3

2026-04-17T00:15:08Z

Niclas: /* Programming */

[[Category:Components and Modules]][[Category:Modules]][[Category:Colibri]]{{metadesc|Colibri MCU3 module}}
[[File:Colibri_mcu3_rev-B_front.jpg|125px|thumb]]
[[File:Colibri_mcu3_rev-B_back.jpg|125px|thumb]]
[[File:Colibri_mcu3_top_right_render.png|250px|thumb]]
[[File:Colibri_mcu3_bot_render.png|250px|thumb]]

[[Colibri]] MCU3 is a processor board for the [[Colibri]] carrier boards. It is an STM32F405RG to be used as the MCU for a Colibri system. Primarily intended for battery operated applications.

= Hardware =
The MCU3 is a relatively simple MCU module, on an M.2 board with the size 22x42mm and the Key E configuration.

Besides the [[STM32F405RE]] MCU there are also
* 128 Mbits (16MB) flash memory for application use.
* a dual-colored (Green/Red) LED
* 16MHz HSE crystal
* 32768 Hz LSE crystal, intended for calendar functions in the STM32.

'''NOTE: All modules in Colibri are NOT compatible with the M.2 connector standard. DO NOT plug Colibri modules into any M.2 socket other than Colibri (or compatible) ones. And DO NOT plug any M.2 modules (Key E is typically WiFi/BLE) into a Colibri carrier board.

= Programming =
STM32CubeMX file [[Media:Mcu3.ioc|MCU3.ioc template file]] for Colibri carrier boards. (Right-click, "Save link as..." on the link)

== Low Level ==
The standard SWDIO/SWCLK pins are available in the pin header together with USART2 for effective low level development environment.

== C/C++ ==
If Forth is not your cup of tea, the standard SWDIO/SWCLK pins are available on the M.2 connector, as well as BOOT0 + USART1 for effective development environment. We recommend the use of the STM32CubeMX to set up the MCU correctly, and then your favorite IDE for the edit-compile-flash-run cycle.

== Zephyr ==
Zerphyr is an MCU-independent embedded OS, with a very modular approach to software, which fits quite well with the modular support of Streamline and Colibri products.

Read more about how [[Colibri Zephyr]] is intended (work in progress) to operate on the [[Colibri]] family.

== Schematics ==

<div class="res-img">
[[File:Colibri_mcu3.svg|2400px]]
</div>

== Gallery ==

<gallery>
File:Colibri_mcu3_top_render.png
File:Colibri_mcu3_bot_render.png
File:Colibri_mcu3_top_right_render.png
File:Colibri_mcu3_top_left_render.png
</gallery>

Colibri MCU3

2026-04-17T00:06:39Z

Niclas: /* Programming */

Colibri MCU3

2026-04-17T00:06:16Z

Niclas:

Colibri MCU3

2026-04-17T00:03:11Z

Niclas: