For some reason, the example code that looked for the sensor would enter an infinite loop if it didn't detect a sensor during startup. I think it was supposed to keep checking, but that wasn't how the code executed. A few changes fixed it so that it will not continue booting until it sees a sensor. Additionally, the screen will print a message about the missing sensor. This will be useful for a badge with a detachable sensor.
When I queried the sensor for a green light reading, it would return a value, but it was not responsive to any reflective or light-absorbing surfaces. I uploaded the basic example code and confirmed that the lack of a green light source was indicative of the sensor's inability in that regard. To verify that I could still read a pulse, I viewed the raw red light feedback on the graph, and my heart rate was as clear as day. The line graph matched the pulse I could feel on my carotid artery.
I made some changes to the code for the new sensor. Firstly, I removed the green numbers. Secondly, the red light feedback dropped to almost nothing when there was nothing to reflect off. I used the low reading as an indication of when the user took their finger away. Now, there is a message asking for the user to replace their finger on the sensor.
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2020-01-26
When I queried the sensor for a green light reading, it would return a value, but it was not responsive to any reflective or light-absorbing surfaces. I uploaded the basic example code and confirmed that the lack of a green light source was indicative of the sensor's inability in that regard. To verify that I could still read a pulse, I viewed the raw red light feedback on the graph, and my heart rate was as clear as day. The line graph matched the pulse I could feel on my carotid artery.
Heart monitoring
I made some changes to the code for the new sensor. Firstly, I removed the green numbers. Secondly, the red light feedback dropped to almost nothing when there was nothing to reflect off. I used the low reading as an indication of when the user took their finger away. Now, there is a message asking for the user to replace their finger on the sensor.
Two values and a finger presence notice
The rest of the posts for this project have been arranged by date.
First time here?
Completed projects from year 1
Completed projects from year 2
Completed projects from year 3
Completed projects from year 4
Completed projects from year 5
Completed projects from year 6
Disclaimer for http://24hourengineer.blogspot.com and 24HourEngineer.com
This disclaimer must be intact and whole. This disclaimer must be included if a project is distributed.
All information in this blog, or linked by this blog, is not to be taken as advice or solicitation. Anyone attempting to replicate, in whole or in part, is responsible for the outcome and procedure. Any loss of functionality, money, property, or similar, is the responsibility of those involved in the replication.
All digital communication regarding the email address 24hourengineer@gmail.com becomes the intellectual property of Brian McEvoy. Any information contained within these messages may be distributed or retained at the discretion of Brian McEvoy. Any email sent to this address, or any email account owned by Brian McEvoy, cannot be used to claim property or assets.
Comments to the blog may be utilized or erased at the discretion of the owner. No one posting may claim property or assets based on their post.
This blog, including pictures and text, is copyright to Brian McEvoy.
2020-01-26
Comments
Post a Comment