Chip Award Winner
Product of the Year 2012
Chip Award

New cheaper LED strips

written by admin, on Sep 9, 2014 6:56:00 PM.

As of today we have new WS2812B LED strips in our shop. You can now buy 5m strips for 59.99€ (incl. VAT). The old WS2801 LED strips had a price of 99.99€!

The strips have 30 RGB-LEDs per meter (previously 32 LEDs). The controlling IC (WS2812B, sometimes called “NeoPixel”) has the LEDs directly integrated. The strips can be controlled by the LED Strip Bricklet. You only have to connect 5V, ground and one data line. The strips with WS2812B are cheaper to acquire for us and we are of course sharing the price advantage with you!

We will only offer full reals of length 5m with the new strip type. The effort to create strips with custom length does not make a lot of sense anymore with the new retail price.

RED Brick in EMC laboratory

written by admin, on Aug 28, 2014 12:57:00 PM.

Yesterday we were in an EMC (electromagnetic compatibility measures) laboratory.

We did an preliminary EMI (electromagnetic interference) test of the RED Brick prototype. As a first test we put the RED Brick alone without any other components in the chamber. The RED Brick was running and just doing CPU cycles on its own.

The result was phenomenal! It was beyond our expectation, during the run we temporary thought that something with the test chamber was not in order. But it turns out that everything worked and the RAM, oscillator and similar are routed very well. They nearly don’t show up at all!

As a next test we tested a stack comprised of Step-Down Power Supply, RED Brick and Master Brick.

Here you can clearly see the SPI stack communication, since all of the peaks are a multiple of 9MHz (the frequency that we use for SPI). However, the result is still very good.

The green line is the absolut maximum measurement, while the magenta line is an average. For the real measurements that we will do with the final version of the RED Brick the quasi-peak will be measured. This will lie somewhere in the middle of both lines.

Unfortunately we were not expecting the phenomenal result of the RED Brick alone, so we weren’t well prepared for the stack tests. The RED Brick has resistors in the SPI traces that can affect the edge steepness. The RED Brick that we used for testing had 0 ohm resistor soldered in place. The next time we are in the EMC laboratory we will try out different resistor values to further decrease the interference that comes from the SPI communication.

However, all in all we can now already be completely sure that we will be able to issue a CE certificate for the final version of the RED Brick. This is very good news, we weren’t even expecting results this good!

We will now be able to order circuit boards for the next prototype. We hope that this prototype will already be the final version of the RED Brick. In the new prototype we incorporate the following changes:

  • Reset button is now connected to GPIO and will halt the Linux properly.

  • We can now reset the stack that is on top of the RED Brick via software, this makes it possible for brickd to restart the stack when it is started the first time to get the Bricks in a known state.

  • JTAG hardware is now configured correctly.

  • We use an inverter on the serial RTS line and fix CTS to ground to be able to control the RS485 Extension more easily.

  • Fix wrong wiring in power supply.

  • Pick-and-place-ability improved.

  • USB ESD protection circuit error fixed.

After these test results we are confident that we will have the RED Brick in our shop this year. So stay tuned!

MakerBeam at Tinkerforge

written by admin, on Aug 25, 2014 6:32:00 PM.

As of now you can by MakerBeams in our shop! It is the perfect mounting solution for Bricks, Bricklets & Co.

MakerBeam is a versatile and lightweight structural system with a cross section of 10x10mm. It has endless building possibilities in desktop size and uses Mini-T, which is a smaller version of the T-Slot standard that is widely used in industrial automation. Each beam has a 8mm deep 2.5mm diameter threaded hole on both ends, sized for normal M3 screws. The profile system is very light, each millimeter of beam has a weight of only 0.136g. You can use MakerBeam to build the mechanical structure for robots, CNC projects, camera sliders and other cool projects! The official MakerBeam website has a big list of example projects.

With MakerBeams we are extending our range of accessories. As a next step we want to add motors (stepper, servo, dc). We are currently testing different motors from different manufacturers, stay tuned!

As soon as we received the first beams and brackets we of course had to start tinkering with them immediately ;-). We were able to mount different Bricks and Bricklets into a frame in no time:

This thing would be doing well as a satellite, don’t you think?

New Bricklets: Color, NFC/RFID and Solid State Relay

written by admin, on Aug 11, 2014 6:16:00 PM.

We used your feedback to design three new Bricklets. All three of them have been released today including lots of accessories:

1) Color Bricklet

The Color Bricklet uses a precision color sensor. The sensor can measure RGB color, color temperature and Illuminance with a resolution of 16 bit each! It is possible to enable a defined lightning (by an LED) via software. Using the LED makes it possible to measure the light reflection of an object with high precision and repeatability. A usage for the Bricklet is for example the sorting of objects. While the Ambient Light Bricklet can measure up to ~1000 Lux, the new Color Bricklet can measure values of several 10000 Lux without any problems.

2) NFC/RFID Bricklet

With the NFC/RFID Bricklet you can read and write different 13.56MHz NFC or RFID tags. The Bricklet supports Mifare Classic, NFC Forum Type 1 and 2 RFID/NFC tags with an arbitrary amount of memory. Suitable tags in the form of cards, keyfobs and stickers can be found in our shop. As an example you could build an intelligent cat door with this Bricklet. It could log the enter/leave times, twitter it and similar :-). We have lots of ideas for interesting projects for this product! This example is also good to explain an important feature of NFC: The range is limited to 10cm. The cat door should of course not open itself if the cat is only roughly in the vicinity.

3) Solid State Relay Bricklet

Switching big loads, such as motors, can be problematic. Currently it is possible to use the Dual Relay Bricklet to switch voltages. But especially big 230V loads can be problematic if switched with a mechanical relay. Switching sparks can easily lead to unstable systems. In this case it is possible to use a Snubber (see Dual Relay Bricklet documentation). It is however easier to use a solid state relay. A solid state relay does not switch mechanically, it is a completely electronic switch. Thus there are no switching sparks present whatsoever. A solid state relay also has more switching cycles (it is wear-free) because no mechanical parts are used. It also has a galvanic isolation between the controlling (input) and the load (output).

It is very easy to switch these relays with the Solid State Relay Bricklet. We are offering two different types of relays. One can switch alternating current of up to 25A at 380V and the other can switch direct current of up to 50V at 80A. Additionally we have a cover that can protect you against touching the contacts as well as a heatsink that is necessary if you want to switch big loads.

We tested different types and manufacturers of solid state relays. Please note that the relays in our shop are of high quality compared to some of the super cheap relays that can be bought in china. Although the Bricklet might be compatible to these super cheap relays (at least if you solder a wire to it), we would highly recommend to not use a 2$ relay. We learned our lesson while testing a cheap solid state relay with our electronic load.

Fully automatic photography turntable

written by admin, on Aug 4, 2014 3:57:00 PM.

By this time we have lots of experience in making photos for the documentation and the shop. Our equipment got steadily better over time. What we were still missing was a turntable that would allow us to make 360° pictures. A professional photography turntable is super expensive, so we made our own!

In front we will show you the resulting 360° photo of the finished turntable and a small video that shows it in action (the video is of low quality, we took it with a smart phone, the camera was used otherwise for obvious reasons ;-) ).

360° Photography of a Bricklet.

From the system of Tinkerforge building blocks we used a Industrial Quad Relay Bricklet and a Stepper Brick. The source code that controls the Stepper Brick and the Quad Relay Bricklet can be found on github.

There are only a few ingredients needed to build a turntable:

We used a stepper motor (14€) and a hub (6€) from Pololu as well as two cutting boards (1€, 3€) as table and foot. In addition we bought a rotary ball bearing from ebay (10€) and we use a few wood offcuts as spacer and brackets/screws from our scrap box.

In sum: Not too expensive!

After we screwed the ball bearing to the top board, the stepper brick to the hub, the spacers to the bottom board, as well as the brackets between the spacers, the whole assembly looks as follows:

You probably noticed that the screws that connect the rotary ball bearing to the top board are not completely screwed in. This was unfortunately necessary because of the high quality of the ball bearing. The ball bearing, which we bought used from ebay is super smooth-running, it can carry 250kg and it has no clearance whatsoever. The latter turned out to be a problem.

Since the hub is directly connected to the stepper motor which in turn has its place because of the position of the ball bearing, the hub has to be perfectly in the middle of the ball bearing. If it is off by only 0.5mm the ball bearing will not turn. Oooops! Despite many tries to screw the hub exactly to the middle, we couldn’t do it as precise as needed. To fix the issue we gave the ball bearings a bit of clearance by not screwing it completely firm to the top board.

Now we have a turntable that we can control to drive to an arbitrary position. For a full automation we also need a possibility to automatically take a photograph. The trigger of our Canon 500D can be driven by a small 2.5mm audio jack. This jack has two strands and shielding. To focus we can connect the shield to the red strand and to trigger a photograph we can connect it to the white strand.

We opened up an audio jack cable and gave the strands and the shielding some wire end sleeves. The resulting four wires can be connected to the Industrial Quad Relay Bricklet. Now we can trigger a photograph by switching relay 1 and we can focus be switching relay 2. That was easy!

The end result with a white photo pad on top of the board looks as follows:

It fits like a charm in our (of course also self-made) photo booth!

API Bindings and package management

written by admin, on Jul 25, 2014 2:36:00 PM.

In the past our API Bindings installation and usage guides did assume that a user already knows one of our languages. In the last days we improved the old documentation considerably. It should now be possible to to install the API Bindings and test an example as a novice without having to look it up anything somewhere else.

You can find links to the usage and install guides for each language in our documentation.

One suggestions we got very often in the past was to use packages and package repositories for languages that have this feature. At first we didn’t like the idea since all of our Bindings are automatically generated and uploading a package to a repository adds an otherwise unnecessary manual step to the process of releasing new Bindings.

However, we got so many requests that we decided to add packages to repositories where it is easily possible for us. Currently we support Maven (Java), NPM (JavaScript), CPAN (Perl), PyPI (Python) and GEM (Ruby). This means, that you can install and update the Bindings for each these languages with one simple command line one-liner.

Java - Maven

Add dependency to your pom.xml

JavaScript - NPM

> npm -g install tinkerforge

Perl - CPAN

> cpanm Tinkerforge

Python - PyPI

> pip install tinkerforge

Ruby - GEM

> gem install tinkerforge

First LiveHacking in Hamburg

written by admin, on Jul 15, 2014 3:08:00 PM.

As we already wrote in the blog, the first LiveHacking in Hamburg took place yesterday:

It was organized by the Java User Group Hamburg, Sven Ruppert (Codecentric AG) and Alexander Bischof. Bastian was there to attend the event. The participants where invited in the accommodations of the “Hacker- und Makerspace Attraktor e.V” and could realize their ideas with the Tinkerforge building blocks. It was very nice to look over their shoulders and to discuss different ideas and possible improvements with the participants. We already released some of the suggested improvements today.

Sven has also written an article about the event. You can find it here (in German) .

More LiveHackings will take place all over the country. We will support Sven Ruppert on these events. Many thanks for all the positive feedback and the ideas for improvement! We look forward to the next events.

LED Strip Bricklet supports WS2811 and WS2812(B)

written by admin, on Jul 10, 2014 2:33:00 PM.

With the new firmware version 2.0.4 the LED Strip Bricklet now also supports the LED drivers WS2811, WS2812 and WS2812B (sometimes also called “NeoPixel”) additionally to the already supported driver WS2801.

The tested it with different LED strips as well as a 256 Pixel LED matrix from different manufacturers.

At the Maker Faire we also had a WS2812B strip connected to a RED Brick which was running two days straight without any hickups. The tutorials in the documentation has also been updated accordingly. It now also describes how you can connect the newly supported drivers (the clock line is not used anymore).

LiveHacking with Tinkerforge

written by admin, on Jun 27, 2014 9:57:00 PM.

There will be a whole series of events about “Tinkerforge and IoT” in different cities of Germany and around the World in the coming months. The first event will be on the 7th of July in Hamburg. The series of events is called LiveHacking and will be managed by Sven Ruppert. You can attend for free, a description can be found here (German).

Sven works for the Codecentric AG and does lots of lectures at Java User Groups (JUGs) and he writes for Jaxenter and EclipseMagazin. Currently he is engaged in “Internet of Things”. While searching for appropriate hardware for his events he found the Tinkerforge building blocks, which he will use to familiarize people with Java8 in the context of IoT.

Bastian (from Tinkerforge) will also be present at the event in Hamburg, which is unfortunately already booked out. More LiveHackings are however planned.

RED Brick Software Infrastructure

written by admin, on Jun 20, 2014 3:34:00 PM.

In the past we only wrote about the hardware of the RED Brick. Today we want to discuss the software infrastructure of the RED Brick.

Attention: This article discusses the technical details of the software of the RED Brick. This detailed background knowledge is not necessary to use the RED Brick in its final stage!

The following graphical overview shows the currently planned software infrastructure. This infrastructure will be explained in this blog post.


The colors in the graphic have the following meaning:

  • Blue: Tinkerforge software components

  • Green: Tinkerforge hardware in the Stack of the RED Brick

  • Purple: Tinkerforge hardware externally connected

  • Orange: External software components

The stack, as well as Mini USB and USB A, are shown as the interface between the RED Brick and the environment in the graphic.

The Mini USB connection is used to provide a composite USB gadget driver with two USB classes: The first class is a serial port. It can be used to get easy shell access to the RED Brick. The second class is the Brick API. A PC will see a RED Brick that is connected through USB the same way as any other Brick. The RED Brick has an API like other Bricks and Bricklets. With this API the RED Brick can be configured. The configuration consists of the transfer of the user program, configurations for the program execution (programm is started once, every hour, on startup, etc.), as well as other configurations. Thus the RED Brick can be seen as a black box that controls Bricks and Bricklets with high level languages.

Over the stack connectors it is possible to use all Bricks as well as the Ethernet Extension and RS485 Extension with the RED Brick. For the Ethernet Extension we have to write a driver. This driver will show the Ethernet Extension as a normal Ethernet interface in the linux system (eth0).

With the USB A connector you can use any USB devices (mouse, keyboard, WIFI stick) and of course also other Tinkerforge hardware.

All of these connections can be used at the same time. A RED Brick stack that is connected to a PC via Mini USB, uses Bricks and Bricklets, uses more Bricks and Bricklets through the RS485 Extension, is connected to the Internet through the Ethernet Extension and has other devices connected over USB A is possible without problems.

In the following we will introduce the components that are necessary for this system:

Linux distribution

The Linux distribution of the RED Brick is based on Debian. It is already making very good progress. The Linux kernel configurations that are necessary for the components (RAM, power supply) and the interfaces (USB Mini/A, HDMI, SD card, SPI/I2C/UART in the stack, GPIO, LEDs, etc.) are done. All of the Tinkerforge Bindings and the necessary compilers and interpreters are preinstalled in the distribution. Additionally the most important libraries for all of the supported languages are preinstalled, this allows the development of more complex applications.

Further more it possible to create two images:

  • Full image: This image makes all possible functions of the RED Brick available, including the graphics driver for OpenGL and graphical output via HDMI.

  • Fast image: This image is designed for maximum speed. For example the GPU is turned off in this image, which reduces the boot time significantly.

With the full image the RED Brick acts as a PC replacement. With the fast image the RED Brick is more of a substitute for the Master Brick that has an OnDevice API for C/C++, C#, Delphi/Lazarus, Java, JavaScript, MATLAB/Octave, Perl, PHP, Python, Ruby, Shell and Visual Basic .NET.

Status: 100%

SPI stack communication

The communication between Bricks in the stack is done over SPI. The currently used protocol, which is used between Bricks, is made for the SAM3S4 processor that is used by the Bricks. This protocol is very efficient, but it would bring the Linux system on the RED Brick to its knees. The solution for this problem is to use DMA, the processor is not burdened by the communication if DMA is used. The protocol that is currently used is not compatible to DMA. Thus we have to design a new SPI protocol that is compatible to the DMA controller of the SAM3S4 processor as well as the A10S processor that is used on the RED Brick. This protocol then has to be implemented on the RED Brick as well as all of the other Bricks.

Status: 25%

The new protocol is completely laid out and the implementation for the SPI slaves is finished. Currently we are implementing the SPI master driver for the RED Brick. It looks like we will be able to use /dev/spidev, which simplifies the development since it can be done completely in the Brick Daemon. If we get performance problems we can easily transfer the relevant parts directly into the Linux kernel.

RED Brick API Daemon

The RED Brick API Daemon is a daemon that implements the API of the RED Brick. That means it implements the configuration that can be done over Mini USB.

Status: 25%

The most important components of the API are laid out and the necessary infrastructure (communication with Brick Daemon etc) is implemented.

Composite USB Gadget Driver

The composite USB gadget driver makes two interfaces available over Mini USB. Through this driver the RED Brick is seen as a “normal Brick” on the PC. It is however possible to get shell access to the Linux on the RED Brick at the same time.

Status: 100%

The driver is ready and functional.

User Interface

The goal is to be able to configure the RED Brick with the Brick Viewer. The API of the RED Brick only needs to be used by “power users”. The “normal user” can use the Brick Viewer to transfer his program to the RED Brick.

Status: 0%

The implementation of the user interface has not yet started.

Ethernet driver (W5200)

The Ethernet Extension uses the WIZnet W5200 IC for Ethernet communication. There is unfortunately currently no Linux kernel driver available for this IC. But there are drivers available for the very similar W5100 and W5300, which will simplify the implementation of the driver greatly.

Status: 0%

The implementation of the Ethernet driver has not yet started.

RS485 Extension support

Support for the RS485 Extension has currently a low priority. We will start with the implementation after the RED Brick is officially released.

About Us


Follow Us