Blog #6 - The start of a Bigger Better Heart 2.0

 Deciding on the Final Project 

Dean Sinnott, 20067691 

This week, we held a standing group meeting to brainstorm potential directions for our end-of-year IoT project. The goal was to have an open discussion and figure out what direction interested everyone, based on what we’ve learned so far — especially our focus on input/output systems.

After some discussion, we agreed to build on the work from the previous class group, who had developed a heart rate monitoring system that used the data to change the orientation of a bottle filled with thick water, simulating ocean waves. Since our semester heavily emphasized inputs and outputs, we liked the idea of continuing that theme but pushing for low latency and a more graphical multi-display dashboard using micro:bits.

However, we quickly ran into a challenge: there were a lot of big ideas, but not a lot of time. While some group members were extremely enthusiastic and willing to work outside class hours, we agreed that keeping the project within class time was a more sustainable and fair approach. The main difficulty was making sure everyone understood the need to limit scope so we could finish something that worked reliably - instead of trying to merge every idea and falling short.

We also thought about how this project might continue into future years. A lot of the work we've done so far has been quite code-heavy and networking-focused, which may not be accessible to every student who joins the module later. That led to a discussion about low-code and no-code approaches, which could allow new students to contribute more easily without needing deep technical backgrounds. We didn’t want Jason, the module lecturer, to have to relearn an entirely different stack just to support new groups. Making the project modular and approachable is key to keeping it going.

By the end of the meeting, we hadn’t locked in a final plan, but we had narrowed things down to two strong concepts:

  1. A multi-micro:bit dashboard to display real-time heart rate data in a simple visual format.

  2. Using an RTC (real-time clock) module with FFT (Fast Fourier Transform) to explore converting heart rate signals into sound waves for ultra-fast data transfer.

It’s still early, but this discussion helped us align expectations and start thinking critically about accessibility, and realistic goals.





















Comments

Popular posts from this blog

Iteration 2 | Jack | HRV Micro:bit Research

Iteration 5.2 | Lock In | Jack

Week 1: HRV Review