Iteration 4

 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 in the data of the slaves and sends it off to an MQTT broker. For most of the semester we spent the time working on the communication architecture, sending a roll value of the microbits to the master board, hoping that once everything functions correctly we can add HRV functionality to the slave microbits, letting the project go full circle.
  • One of the main things we aimed to achieve during development was to set up an MQTT broker which would work with our equipment. The code for the master microbit contains all the tokens and secret API strings for MQTT to be enabled, and it is during this process of development that we found out that v2 boards seem to not have proper MQTT compatibility.
  • The final piece of architecture present in the project is the MQTT client app, which was set up, connected to the MQTT broker allowing us to view and send data to said MQTT broker in real time, with the established infrastructure allowing the slave microbits to access specific data being sent to them via the MQTT app, and then displaying the data on their screen.

The main work made during this iteration was getting an MQTT broker working along with starting work on IFTTT code, below is hello world code made to check IFTTT compatibility with the DFRobot cloud board.


Comments

Post a Comment

Popular posts from this blog

Iteration 2 | Jack | HRV Micro:bit Research

Image
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...
Read more

Iteration 5.2 | Lock In | Jack

Image
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...
Read more

Week 1: HRV Review

Image
  What is it? Heart rate variability (HRV) is the measure of the variation between heartbeats. It is controlled by your autonomic nervous system (ANS). This system operates automatically and regulate process such as the heart rate and other bodily functions that are are not under conscious control. This system is broken into two branches the flight or fight (which preparing the body for action and stress) and the rest + digest (which promotes relaxation + recovery). HRV is influenced by the ability to smoothly shift between these two branches.  High HRV: Larger difference between successive heartbeats - Indicates a more flexible and adaptable autonomic nervous system.  Low HRV: Smaller differences between successive heartbeats - Indicates a less flexible autonomic nervous system.                                                ...
Read more