Lock In Day 1 (20/05/25)

 

Lock In day 1

 

Briefing

We started the day with by getting the project briefing on what the end result should be.

We decided to make a system where we could read in heart rates using a Microbit and then send that via the cloud to a website that would display real time data from the heart sensor.

 

 

Kanban planning

Once everyone had a clear understanding of the briefing , we began defining a KanBan chart so that we could organise and allocate tasks. This consisted of Backlog, Doing, Done, Testing and Complete columns where we could quickly move tasks into different columns as they are completed.

A white board with sticky notes on it

AI-generated content may be incorrect.

 

 

 

 

 

Group allocation

We began breaking down the steps required to complete this pipeline. This consisted of many different areas such as creating the cloud infrastructure on AWS, reading data on a micro bit and radio sending it to a raspberry pi so that it could be sent to the cloud infrastructure, creating a unity app that shows a heart beating when a person’s heart beats.

Once we had defined the steps required to complete the pipeline, we began allocating people to groups. I decided to work on getting the data from an ECG sensor to radio send to a raspberry pi so the data could be converted and sent to the cloud.

 

Recreating old pipeline

I started by rebuilding the old pipeline that was functioning a few weeks before this lock in only instead of using the pi 4 (originally used) , I used my pi 5 with 8gb of ram which may handle more information.

This consisted of configuring mosquito (https://randomnerdtutorials.com/how-to-install-mosquitto-broker-on-raspberry-pi/ ) on the raspberry pi so that the pi 5 would act as an mqtt broker which ,later , the front end website could subscribe to it and receive the newest information.

Next, I cloned the repository containing the code for the website and the serial reading program. The website runs on localhost 7153 and the serial connection is used to read the data being received on a Microbit via radio send.

 

Recreating the initial pipeline took the entire day, however, once it was working, I had a starting point to modify the code so that it would convert the signal and send it using webrtc to the ec2 instance.

 

Code for Client Microbit (connected to ecg sensor)

https://makecode.microbit.org/S95466-10540-55671-12146

Code for Serial Microbit (received ecg data via radio and outputs it serially)

https://makecode.microbit.org/S90875-82211-76568-42127

 

What is WebRTC

https://webrtc.org/

 

New pipeline graph

A screenshot of a computer

AI-generated content may be incorrect.

 

Current UI (Locally run)

A computer monitor with a screen

AI-generated content may be incorrect.

 

 

 

 

 

End of day meeting

At the end of the day, we had a meeting to discuss how everyone was doing with their tasks and any potential issue they have run into or may run into. Once we did this meeting, we were able to offer input into the other groups as to how they may overcome the problem etc. This was a very productive meeting as it allowed us to prepare our next tasks so that we could begin work much faster in the morning after a shorter meeting to review where we are.

 

A group of people standing in a classroom

AI-generated content may be incorrect.

 

Comments

Popular posts from this blog

Iteration 2 | Jack | HRV Micro:bit Research

Iteration 5.2 | Lock In | Jack

Week 1: HRV Review