Book Image

Creative DIY Microcontroller Projects with TinyGo and WebAssembly

By : Tobias Theel
Book Image

Creative DIY Microcontroller Projects with TinyGo and WebAssembly

By: Tobias Theel

Overview of this book

While often considered a fast and compact programming language, Go usually creates large executables that are difficult to run on low-memory or low-powered devices such as microcontrollers or IoT. TinyGo is a new compiler that allows developers to compile their programs for such low-powered devices. As TinyGo supports all the standard features of the Go programming language, you won't have to tweak the code to fit on the microcontroller. This book is a hands-on guide packed full of interesting DIY projects that will show you how to build embedded applications. You will learn how to program sensors and work with microcontrollers such as Arduino UNO and Arduino Nano IoT 33. The chapters that follow will show you how to develop multiple real-world embedded projects using a variety of popular devices such as LEDs, 7-segment displays, and timers. Next, you will progress to build interactive prototypes such as a traffic lights system, touchless hand wash timer, and more. As you advance, you'll create an IoT prototype of a weather alert system and display those alerts on the TinyGo WASM dashboard. Finally, you will build a home automation project that displays stats on the TinyGo WASM dashboard. By the end of this microcontroller book, you will be equipped with the skills you need to build real-world embedded projects using the power of TinyGo.
Table of Contents (13 chapters)

Requesting data from the microcontroller

We might want to know if the light is currently turned on or off inside the living room, without having to walk all the way into the room. So, it would be great if the Wasm app could request the status of the light and display it.

Now, let's imagine we have one or multiple microcontrollers in different rooms, listening to messages. For this example, we do not want the microcontroller to continuously report the state of the light as this would cause unnecessary network traffic. So, we go on and send a message to request the data. The microcontrollers are subscribed to the status topic and get the message delivered. After receiving the status request, they answer it by each sending a status message.

This process is represented in the following diagram:

Figure 8.6 – Architecture diagram

In order to implement that behavior, one microcontroller is sufficient. So, let's go on and update our code accordingly...