Robots and Physical Computing

In an earlier post  https://robotsandphysicalcomputing.blogspot.com/2024/08/microbit-v1-datalogging.html  a single microbit was used to log data. The main problem with this is often we want to sense things that are away from the computer ie remotely (though only a short distance away). The previous solution was attached to the computer to work. So one solution (and closer to solutions used in the 'real-world' is to separate the sensing part and receiving and processing into two different devices. So in this case two micro bits; one collecting and sending data, and the other receiving and transferring the data to the computer.   How? So to play with this, we are going to extend our previous solution  https://robotsandphysicalcomputing.blogspot.com/2024/08/microbit-v1-datalogging.html  to be a remote monitoring system; and the easiest way to get started is with  a solution that already exists and adapt it . So we going to use the solution found in  https...

Often we need applications that allow collection of data over time, for example temperature or light levels through the day. Allowing us potentially analyse the data for trends. The microbit is a fantastic tool, with some of these sensors already in place (e.g. light and temperature) or can be added to with extra sensors from add-on boards (such as Kitronik Air Quality and Environmental Board for micro:bit https://shop.pimoroni.com/products/kitronik-air-quality-and-environmental-board-for-micro-bit?variant=39475687227475 )   Datalogging with a V2 microbit is relatively easy all the details are available here: https://microbit.org/get-started/user-guide/data-logging/ to get started.   But what about the older V1 can it do it?   The answer is yes but it is a little more work and is generally a little more limited but still very worth while. In this post we are going to look at doing this.   In Figure 1 starting the process off in MakeCode ( https://ma...