InfluxDB + Grafana for the IoT

Hello everyone, it has been a while since our last post. The Kickstarter campaign has proven to be quite involving, but things start to get back to normal and new posts will keep appearing.

As now we’ve an official product/platform, there’s a plan to start creating practical posts, complemented by video blogs to show real use cases step-by-step. Stay tuned!

Moving on, this post will present a very promising solution to store, presenting and analyse time series data. Perfect to save all the IoT data produced.


Continue reading

Talk² on Kickstarter

As you may already noticed, we’re running a Kickstarter campaign. The objective is to get enough pledges to produce our Whisper Node in larger scale, reducing the total board costs to everyone.

Whisper Node -- Kicktraq Mini

Thank you all for supporting us! The project got funded and all updates will be posted directly into the Kickstarter Campaign page:

Talk² Shop


We’re please to announce that the Talk² Shop is now Open! To access it just follow the link below:

You also can get more information about the Talk² boards on the new “Product” menu.

We’re currently working to make the store better, so please let us know if you have any question or suggestion.


Connecting to the Internet

Talk² is all about communication and adding Internet connectivity to your project can easily bring it to the next level! Despite the fact that you can find a couple of alternatives to it, we would like to present our prefered way.

On this post we’ll briefly check the common ways of connecting an Arduino to the Internet, evaluate the Pros and Cons. After we’ll present the Talk² approach to this problem, explaining concepts and queueing techniques to build a much more robust and flexible solution.

The popular options

After some research we easily concluded that the most popular way people are connecting their Arduino to the Internet is by using a direct Ethernet connection. Some cases using shields or expansion modules, others by simply relying on the build-in Ethernet capabilities of the board/MCU.

Continue reading

Low Power Budget

One of the biggest challenge for the Internet of Things, especially for those devices using RF communication, is the power consumption. In many situations it’s normal to expect the wireless equipment to have their own source of power, instead of relying on an AC-DC power supply connected to the wall outlet. In the IoT world there is a real demand for 100% wireless devices, powered by battery or any kind of power harvesting.

The first question you need to answer yourself before start building battery powered circuits is: For how long I wish the device to run on new batteries? One day, a whole week, maybe a year? Or just be brave and say 2 decades.

On this post we’ll talk about the low power world, how you can plan, design and implement circuits that can work for years on a pair of wide available AA batteries. We’ll also present the common trade-off and techniques necessary to reduce power consumption, as well discuss how RF communication can be implemented with minimal power requirements.

This can be a very complex and long topic and we’ll try to keep it as much practical and simple as possible. Bear in mind that we won’t offer a ready-to-use, kind of copy and paste code. The whole idea is to be broader and educate how to identify and solve common problems.

Talking about Power

Continue reading

Wireless Link

This post is a continuation of The Talk² Protocol post, which explained some basics about the Talk² protocol as well basic details about the Wired link.

One more time is important to highlight that the Talk² protocol is independent of the hardware it runs on. For our own boards designs we’ve made some decision, defining which technologies and hardware to use based on our experience. Remember that you’re free to implement the same protocol rules on top of any other media.

RF: Not so simple

A wireless link sounds much simpler than a wired connection. There’s no cables laying around, no mess and all works. But in reality, from an engineering point of view, it’s exactly the opposite. Wireless or radio-frequency (RF) links are much more susceptible to interference, reliability, privacy issues and even local government regulations. In an attempt to simplify our decision to which hardware should be used, we evaluate the following requirements: frequency, cost and features.

Frequency: ISM Band

Continue reading