BLOG# 5 - BPM Display - Conclusion and Future Enhancements
A Heart Rate Monitor Display project utilizing the PSoC 6S2 + AIROC Wi-Fi/Bluetooth Pioneer Kit
manufactured by CYPRESS - INFINEON TECHNOLOGIES (Part# CY8CKIT-062S2-43012)
This is my 5th and last blog post for this Design Challenge: Low Power IoT Design Challenge
version 1.3
<<< PREVIOUS BLOG |
---|
- This is my final blog for this design challenge.
- I did learn quite a bit about this device and I have only scratched the surface of what can be done this this device.
- My design is now working as described in my previous Blog#4. in this blog,
- I will share my conclusions of my experimentation using the "PSoC 6 Pioneer Kit " and my idea for other experiments that I would like to try out.
- I did not completely use my design to implement my idea for the challenge, but after this challenge ends, I plan to expand my design to include some future enhancements that I've listed below.
- For a first pass I'd like to wrap up this challenge with getting the example project by Jan Crumps to work and build some test scripts to be able to unit test the components as I implement them.
My Idea
- When I first started the challenge my idea was to connect a heart rate sensor and a OLED display (that I had from a previous challenge) to the PSoC 6 Kit.
- Then since the bpm project from that Design challenge was basically working generating a BPM value, I decided to connect the project breadboard to the PSoC6 kit.
- I then was recommended a PCoS6 series by element14 member Jan Crumps. Jan was referring to his AnyCloud connection to AWS, but when I started reading his blogs, I discovered that he was using and Arduino connected over a serial connection to the PSoC6 kit. He used a different kit (CY8CPROTO-062-4343W), but he stated that this kit (CY8CKIT-062S2-43012)
- So my idea expanded to:
- Connecting my Android base BPM project breadboard to the PScO6 kits UART.
- Using FreeRTOS designed by Jan, with Scheduling, messaging, triggers and semaphores.
- Send the BPM values thru this design pipeline
- Then publish the BPM values using the modified MQTT client example .to AWS MQTT broker.
Conclusions
- In this section ,I'll give some conclusions as to what you have gained from this Design Challenge
- I did learn a great deal more about embedded software.
- Did everything work as designed?
- Everything did not work for me, which was a little disappointing. but I had a huge learning curve to get to implement my idea.
- What were the biggest hurdles you had to overcome?
- There were many hurdles to learn and get to to the point where I could implement my idea.
- PSoC8 kit
- ModusToolbox
- FreeRTOS
- UART
- MQTT
- AWS
- a local MQTT Broker MosQuiTTo
- There were many hurdles to learn and get to to the point where I could implement my idea.
Future Enchantments
- I've Listed some possible enhancements that can be added to the design and implementation.
- Anycloud Client to Azure
- Azure RTOS
- OLED display on working on the kit
- Unit testing in ModusToolbox.
- Othere Anycloud examples as listed in ModusToolbox AnyCloud flow and assets,
- ble
- capsense
<<< PREVIOUS BLOG |
---|
Blog#4 - BPM Display - System Implementation and Testing |