Blog

Thank you for all of the orders! The announcement of the RED on last Friday and the articles from Golem and Heise (German) did lead to a rather large shipping backlog.

All currently open orders will be shipped this week. Generally we will be shipping up until December 23rd.

We did prepare very well this time, but could nevertheless not keep pace with the orders. Currently we are working at full speed to process the backlog. Thank you for your patience!

Since we frequently got this question: We will ship up until (including) December 23rd. So you do have some more time left to order if you want Bricks and Bricklets underneath your Christmas tree. If you order from outside of Germany, the only shipping option that can guarantee a shipment before Christmas is FedEx. Orders with DHL or Deutsche Post as shipping option may not arrive before Christmas.

One of our tasks is to flash the ordered SD cards. You can take a look at our flashing setup in the image above. It uses a USB 3.0 hubs with 10 USB 3.0 card-readers each. This setup is currently running around the clock.

HDMI cables and some of the cases will be delivered subsequently.

Edit: Miraculously, new plastic arrived already today. So there won’t be a shortage of cases!

In beforehand we did speculate about the composition of the orders. One question was, how many accessories will be bought together with the RED Brick on average. We did misjudge the amount of necessary HDMI cables. We estimated an order rate of 25%, but in reality about 85% of all RED Brick orders include an HDMI cable. We already ordered new HDMI cables, but our supplier also seems to have a backlog. We do have a similar problem with our cases. Our laser cutter, that is used to cut the cases, is also in continuous operation. Our former big stock of plastic is drawing to a close and new plastic will not arrive before Christmas. We likely won’t have enough plastic here to produce all of the necessary cases. So we have to deliver some of them subsequently.

Don’t panic if your package is missing an HDMI cable or a case, they will be delivered separately as soon as possible (see delivery note)!

It’s happening! After nearly a year of development and in sum over 7400 hours of work, we are able to release the RED Brick today! The last days were suspense-packed for us, since we had some small delays. The delays nearly put a release date before Christmas at risk. Up until yesterday we did not know exactly if we would be able to release the RED Brick on schedule. However, now the time has come, the RED Brick is available in our shop for 69.99€.

In the last few days we gave the RED Brick away to a small group of testers, they gave us lots of feedback and found many bugs. All of the bugs should be fixed in the current release version, some of the improvement suggestions will be added to the Software in the next few weeks. Please write us an email (info@tinkerforge.com) if you find more bugs or if you have other constructive feedback!

We look forward to your feedback!

Please note that the stack communication had to be changed for the RED Brick. To be compatible, all of the Brick firmwares need to have a version of at least 2.3.0. Otherwise they won’t be recognized in the stack.

Surely everybody has heard of the Internet of Things. It describes the vision of intelligent objects which assist us in our everyday life. A realization of this vision can be made possible by embedded systems in things and their interconnection (”Internet of Things”).

The Tinkerforge building block system makes the development of intelligent things very easy, but interconnecting these things can be hard. Cumulocity makes building Internet of Things solutions simple and affordable for all businesses through ready-made cloud applications. Cumulocity offers a free 60 day access for Tinkerforge customers. Starting today, you can find the access code on a flyer in your order.

The long waiting time will be over soon! We plan to release the RED Brick in early December.

In the photo above you can see the yield of a small test production of RED Bricks. At the beginning of the week we produced a small quantity. The goal was to recognize problems with faulty/defective components as early as possible. The production run was not completely without issues, but we did not have bigger problems. This means that we can start the production in the end of this month.

Unfortunately there are still many open todos. Currently we are working with full speed to get the software in a usable state. We still need to implement some small things, test a lot and of course fix bugs. But all in all things are going well. We did already start with the documentation, but there are still full sections as well as a final touch missing. Additionally there are marketing todos like making photos, press releases and a video for the RED Brick.

As you can see, there won’t be any boredom in the Tinkerforge headquarters. Nevertheless we are optimistic that we will be able to release the RED Brick in early December.

Stay tuned!

You don’t know what the RED Brick is? Read our old blog entries (chronological order):

• https://www.tinkerforge.com/en/blog/2014/2/21/tinkerforge-goes-stand-alone-aka-red-brick

• https://www.tinkerforge.com/en/blog/2014/4/10/red-brick-circuit-boards-arrived

• https://www.tinkerforge.com/en/blog/2014/5/13/red-brick-news

• https://www.tinkerforge.com/en/blog/2014/5/23/red-brick:-does-it-work

• https://www.tinkerforge.com/en/blog/2014/6/20/red-brick-software-infrastructure

• https://www.tinkerforge.com/en/blog/2014/8/28/red-brick-in-emc-laboratory

• https://www.tinkerforge.com/en/blog/2014/10/16/red-brick-status-report

The last time we wrote about the RED Brick is now over a month ago (RED Brick in EMC laboratory). A lot of work has been done in the meantime. We already wrote about the general software infrastructure of the RED Brick. Now we want to give you an update:

Stack communication with other Bricks: The stack communication between RED Brick and other Bricks was a lot more effort than expected. The currently used protocol could not be used, thus we had to change it. The new protocol had to be discarded and reworked several times until we found an implementation that could support the peculiarities of the DMA controller on the RED Brick and still be compatible with the normal Brick microcontrollers. However, we now do have a protocol that is stable, corrects errors and performs well on both platforms.

Ethernet and RS485 Extension: We would like to support these two extensions at sales launch. The Ethernet Extension uses the Wiznet W5200 Ethernet IC. There is no Linux kernel support available for this IC. We were however able to develop a driver based on the similar W5500, which already had a kernel driver in the works by Wiznet. If you now put an Ethernet Extension on a RED Brick stack, the Ethernet Extension will be seen by the underlying Linux as a normal network interface (”eth0”).

RED Brick API Daemon and Brick Daemon: The RED Brick API daemon implements the RED Brick API. It is the interface between the RED Brick and anything external. With this API you can configure the RED Brick. You can upload programs, schedule and execute them. The API Daemon is now nearly done. The Brick Daemon has been extended, besides USB connections it can now also manage serial (RS485 Extension) and SPI (stack communication) connections on the RED Brick.

Brick Viewer: The Brick Viewer is currently still missing lots of necessary features. We still need to implement lots of the features that will be needed to use the RED Brick as a black box. This includes configuring network configurations, hostname, ip address or configurations for the local Brick Daemon (port, authentication, logging). It will be possible to monitor the state of the RED Brick (processes, cpu/memory usage). Extensions need to be configured (baudrate, slave addresses, etc) and much more.

Below you can find a first screenshot of the RED Brick tab in the Brick Viewer:

More hardware hickups: We did already talk about errors in the hardware design. Unfortunately we did not manage to fix all of the bugs in the first go. The datasheet of the processor has a table with the available pins. It shows the available features for each pin (e.g. input, output, etc). Nearly all pins can do input as well as output, according to the table this is also true for “PG2”.

This pin is used in our design by the second extension. Unfortunately we only found out that this pin does not really support output very late in the development. We just couldn’t get the Ethernet Extension working if it was put on the stack as a second extension. We then found a hint about this in the revision history of the datasheet:

In the revision history they say that they changed the pin description for PG2 from Input/Output to Input only. But they only put this hint in the history, they didn’t actually change the table! GODDAMNIT!

What does this mean? We already had the circuit boards for the production run ordered, we couldn’t cancel them anymore. We discussed the issue and came to the conclusion that we can’t sell the first version of the RED Brick with a known bug that prevents the usage of a second extension. This would not affect a huge amount of applications, but it just does not comply with our standards regarding quality.

We will use the circuit boards with the bug on them to do another test run of the RED Brick production. We will then be able to test the hardware extensively, since we will have lots of prototypes. After that we will order new circuit boards and we are now planning the production for the beginning of December, so that we can start selling RED Bricks before Christmas.

Stay tuned!