A Big Heart :-)

Iteration #2 - Micro: Bit Research & HRV Jack Duggan | 20094010 | IOT Apps For the second iteration sprint of the module, I got hands-on with the Micro:bit. I had previously used these devices way back in secondary school for Leaving Certificate Computer Science, so the basics came back to me fairly quickly. We were sent home to 'research' the Micro:bit, and become familiar with it's basic functionality, before class on Friday the 2nd of February. In the class, I worked alone (as we had an odd number of students present) with a Micro:bit V2, an expansion board for the Microbit, and a heart rate sensor. Above is the physical setup Below is the device output screen with my finger on the sensor. The top graph shows my pulse as analogue input as identified by the sensor. Some mathematics is performed (as shown under the below graph) that converts these pulse values to HRV (delta_t). This HRV value is then displayed on the 'boxier looking' graph underneath. The way t...

 Lock-In Final Iteration Dominik Martynski 20094523  Before the lock-in itself, as a team we brainstormed the specifics of said lock-in, so that everyone knew what team they were on, what functionality to work on and a general breakdown of all the features we hoped to get working during it.    We worked on three pieces of hardware, the wearable (what you put on your finger), a wave machine (the main visualizer for your heartbeat) and a teddy bear whose belly moves up and down imitating a breathing motion using the HRV. One of the main ideas we came up with for the project was that of a wave machine that would visualise the HRV using a bottle being lifted up and down using a motor linked to the HRV values, mostly based off of the Hughes Wave Motion machine we were shown in class as inspiration. The rocking and intensity of the waves was determined by the HRV, but instead of a massive tank of liquid we opted for a more realistic water bottle filled with food colouring ...

Iteration 5.1 | Brainstorms, Biofeedback 🧠🌊 Jack Duggan

Iteration 5.2 | The Lock-In 🔒 Jack Duggan | 20094010 | 10/05/2024 The "lock-in" was something initially devised months ago, an idea that involved taking a couple of days towards the end of the semester to commit fully to this module. As the semester began to wind up in terms of general workload, it became increasingly apparent that this "lock-in" would be necessary. In week 10/11 when we finally set it in stone, it was a great relief off all of all shoulders, knowing it was one less module to stress about, especially with already rampant workload due in week 12/13. With the lock-in pencilled in for the second week of May, it allowed myself and the others to put increased focus on other modules, and helped reduce the stresses we faced at this time. Eventually, the lock-in week did come around, and I and the others arrived in the room on Tuesday 7th May at 10am sharp. We had split into two teams, one team consisting of Emma, Conor and Eric that would look at adding H...

    Big Heart SETU  The Final Iteration 🧠🔒

 Iteration 4 of HRV project   Above is a diagram of the current infrastructure of the microbit HRV project. A DFRobot Cloud Board is used in tandem with the main microbit to serve as the main master of the system. The Cloud Board gives the microbit extra functionality, letting it connect to the internet, enable MQTT IFTTT etc. Currently only a v1 board is being used for the project as we believe the MQTT functionality present in a v1 was removed in any v2 board. A mobile phone is used as a hotspot for connecting the cloud board to the internet. During the development phase we found out that an Android hotspot works best while windows laptop hotspots and iphone hotspots work far too inconsistently to be used properly. The project contains two piece of microbit code, one for the master cloud board and another for every microbit connecting to it sending information. The slaves communicate with the master using a radio group, thus not requiring any internet, while the master takes...

  Lock In Teddy Bear team Before diving into the actual lock project, we began by distributing the workload to clearly define who would be responsible for each aspect of the project. Given our objective to implement two distinct ideas using Heart Rate Variability (HRV), we devised a plan that included both a teddy bear and a wave machine, each designed to simulate HRV in unique ways. The first idea involved creating a teddy bear that could mimic HRV. This project aimed to provide a comforting and interactive experience, particularly for children and mother, by having the teddy bear's movements or vibrations align with a person’s heart rate variability. This approach required careful consideration of the mechanisms and sensors needed to accurately capture and reflect HRV in a tangible and soothing manner. Luckily we found a teddy bear that have display some of the mechanics that we reguired such as motor that simulate breathing -  Fisher-Price Soothe 'n' Snuggle Otter | Smyt...

Source: Canva AI   7/05/24 HRV Lock in Day 1 As discussed in the Brainstorming blog there had been a list of work that needed to be completed by my group, this includes:                     1. Creating a HRV wearable (Myself and Hasan)                     2. Building a wave machine (Everyone)                     3. Wearable to/from Tweet, spreadsheet using IFTTT (Jack)                     4. Calculate phase difference for servo output. (Everyone) The class had been split into two groups one to design a the wave machine and the other to design a teddy bear that would "breath" according to the users HRV. To begin the lock in the Pulse sensors for the HRV measurements needed a way to stay in the same position so that a user was able to give accurate...