Category: Emmanuel’s Status Reports

New Knowledge:

During every iteration of this project I learned something new. I learned more about interacting with different microcontrollers (RPis, Arduinos, etc), bluetooth  communication, use cases of various sensors, operating different CAD softwares, 3D printing, acrylic bending, and  the approach for screwing different materials together.  The most prevalent learning strategy I used was youtube videos along with trial and error. I also leaned on GitHub (for starting certain serial communications)  and TechSpark workers (3D printing, drill, and acrylic bending) for guidance.

TESTING VERIFICATION:

I tested the basic functionalities of OPS243 and it work wells in doors when stationary. It does have a more limited field of view than the ultrasonic sensors but it’s better at filtering out unnecessary objects if I set the right configurations. Our encasing for our device has not been created yet so I can’t test on a bike yet.

The wristband system is able to meet our use case in a limited setting. When the system was stationary, a vibration haptic feedback response is generated within a second of an incoming object being detected. Unfortunately, the coverage area for the blind spot is minimal with the OPS243 sitting around 20 degrees laterally but for MVP we’re hoping this will suffice. I have yet to test the accuracy rate of the blindspot system but aim to do so next week.

WORK ACCOMPLISHED:

This week I continued working on the wristband subsystem.

I wrote code to the sensor script so it can send a signal to the HC-05 when an object is detected within a certain range, but I haven’t been able to test it due to a road block with configuring the HC-05 bluetooth modules. I’m struggling to establish connection between to the two HC-05 modules because I have been unable to get a response from them individually using AT Commands on the Micro Arduino.  The AT Commands are needed to sync the modules and dictate which one is the “master”. I’ve tried various solutions I’ve seen online but will now pivot to trying to configure the HC-05 with the RPi4 instead because this seems to be a common issue with the micro Arduino.

PROGRESS:

I’m pretty behind on tasks right now, but if I’m able to establish how to send data I will make a significant leap. I wanted to have a functioning blindspot detection system for the interim demo by now. I will continue to work on  establishing connection between HC-05s throughout the weekend. I also noticed theres a really good radar sensor in the ECE inventory so I will put in a request for that.

NEXT WEEK’S DELIVERABLES:

Next week, I aim to have basic functionality of the blindspot detection subsystem and make any tweaks based on feedback from the interim demo.  Also, I will get a new radar sensor from ECE inventory.

WORK ACCOMPLISHED:

This week I spent time working on our wristband system.

I was able to setup a circuit using the mini breadboards, that cause the ERM motor to vibrate from a script on the micro Arduino. I spent time learning how to use HC-05 bluetooth module in order to send data that the Arduino can use to dictate when the motor should vibrate. I’m currently working on adding code to the sensor script so it can send a signal to the HC-05 when an object is detected within a certain range.

PROGRESS:

I’m currently behind with tasks, I wanted to be able to send data to the motor circuit from a python script by now. I aim to have this done later today though. I also still need to find a better sensor, but want to make sure I can get basic functionality of the blindspot detection subsystem before I spend more time trying to improve accuracy.

 

NEXT WEEK’S DELIVERABLES:

Next week, I aim to have basic functionality of the blindspot detection subsystem and look into sensors available in the ECE inventory.

WORK ACCOMPLISHED:

This week I spent time creating a script to use and test the ultrasonic sensors along with completing the ethics report assignment.

A significant portion of my time was dedicated to creating a script for the ultrasonic sensors and researching the proper configuration settings for RPi4 when the using the Rx and Tx pins with different interfaces . The script allowed me to test the sensors object detection capabilities by printing out the distances of an object that’s detected.  I did some basic tests indoors, outdoors, while the sensors are stationary, and while they’re moving but still need to conduct stronger field of view tests to gain a better understanding of their accuracy. There are some risk concerns from testing that are in our team status report.  I also focused on completing the ethics report assignment. This involved delving into ethical considerations and principles relevant to the field, which not only enhanced my understanding of the subject but also allowed me to reflect on the broader implications our project.

PROGRESS:

I’m still currently slightly behind with tasks, I wanted to have the basic circuit for the wristband built right now, but I think I can make up time next week. There needs to be more exploration of the bluetooth module as well.

NEXT WEEK’S DELIVERABLES:

Next week, I aim to do more sensor testing, make a decision on wether to order a different sensor, and setup circuit for the wristband with a stretch goal of transmitting data to it through the bluetooth module.

WORK ACCOMPLISHED:

This week I spent time working on our team’s design report, refining the device encasing mount design, and getting setup with RPi4 to use the sensors.

Refinement of our design through working on our report took a significant amount of time. It led to me doing more research on other sensors like the doppler radar sensor. This might be used in the future if I struggle to develop an algorithm that allows use to differentiate incoming versus stationary objects with the the ultrasonic sensors. Creating a compatible Nite Rite bike mount for the device encasing seems more complicated than creating one for the GoPro bike mount so I decided to switch and order a GoPro mount since my AutoCad skills aren’t super strong. Lastly, I set up our RPi4 for my laptop and ran some test scripts in Thonny in preparation to program the sensors.

PROGRESS:

I’m currently slightly behind with tasks, I wanted to have the basic distance detection script for sensors working by now. I think I can make up time next week. We found out parts for the wristband got lost in delivery so we had them reordered and will pick them up after spring break.

NEXT WEEK’S DELIVERABLES:

Next week, I aim to establish basic object and distance detection functionality with the sensors and setup circuit for the wristband.

WORK ACCOMPLISHED:

This week I spent time familiarizing my self with the CMU’s 3D printing process and AutoCad in order to help tweak our device encasing design.  Additionally, I took time to look at different bikes around campus to get a better understanding of how our device will be attached.

Through my time exploring and even riding a bike during the city’s busy periods I realized a velcro strap would be unstable for securing our device. Additionally, our encasing protrusions will be difficult to design in way that keeps our sensors secure and in place when hitting bumps while riding. I did research into existing bike mounts that can clamp to the bike seat shaft and we aim to pivot so our encasing can clip into one of those mounts (specifically NiteRider design). Working in AutoCad for the first time in years too longer than expected but a rough idea of our new bike encasing (newer than in team status report) is below. Edits have yet to be made for the sensor holders (protrusions) because we just got the sensors at the end of the week.

PROGRESS:

I’m currently on schedule with my tasks. Still waiting on the mini bread board and the vibrations, hopefully they arrive next week.

NEXT WEEK’S DELIVERABLES:

Next week, I aim to establish basic object and distance detection functionality with the sensors, submit order for bike mount, and complete written design report.

WORK ACCOMPLISHED:

This week I focused on finding and comparing quantitative measurements for the hardware materials of our device in order to justify our use case requirements in our design presentation.  I focused on exploring current/power draw, baud rates, and pinouts  to solidify how the wristband mechanism will receive information from the Raspberry Pi wirelessly, and how the wristband will be held together for the user.  Also, I spent time building our design presentation.

I spent time researching different specifications for our batteries, sensors, and vibration motors. I started with current draw to make sure our batteries could sufficiently power our circuits for a decent amount of time. Next I fleshed out the pinouts for our components to refresh myself on creating circuits with a breadboard and to know if we had enough space to build our system on a mini breadboard . Additionally, we need to know if he had enough pins on our raspberry pi. Lastly I looked at baud rates for bluetooth module (HC-05) and average transmission times for our other components and they seem to be adequate to meet our latency goals. Between last week and now we decided to make this device only for bicycles that way we can attach our device underneath the bike seat so the rider isn’t blocking the sensors,

PROGRESS:

I’m currently on schedule with my tasks. We ordered  parts and hope to see somethings arriving next week.

NEXT WEEK’S DELIVERABLES:

Next week, we hope to make any adjustments based on our design presentation feedback. Additionally, we hope to start tinkering with parts that may come in.

WORK ACCOMPLISHED:

This week I focused on researching components for the hardware aspect of our device.  I focused on exploring parts for the vibration motor, different sensors for detecting objects, how the wristband will receive information from the Raspberry Pi wirelessly, and how the wristband will be held together for the user.  Also, I spent the beginning of this week preparing and presenting our proposal.

My decision making  for parts was based around  price, accuracy, and integration capabilities. We’re planning on using a simple Eccentric Rotating Mass (ERM) vibration motor because of size and shape. We’ll need a transistor that connects this motor to the Arduino so we have enough voltage to activate motor but it doesn’t need much We’re going to be leveraging HC-05 RF Wireless Bluetooth Transceiver that will send and receive data from the Raspberry Pi to the Arduino that will be in the wristband.  Between our proposal and now we decided to make switch from the VL53L0X ToF Sensors because their field of view for object detection is minimal.  We plan on moving to A02YYUW Waterproof Ultrasonic Distance Sensors or JSN-SR04T.

I spent a lot of time envisioning how the different parts will connect on the wrist band. We plan on using a mini bread board and encasing the system (breadboard, Arduino, and transceiver) in a 3D printed case while have the ERM motor embedded in a strap that will secure the case to the user’s wrist. Although the connections should be minimal I’m concerned about pin space on the breadboard and ensuring the vibrations don’t disrupt the circuit.

PROGRESS:

I’m currently on schedule with my tasks. We planned to have a finalized parts list by Monday (02/09).

NEXT WEEK’S DELIVERABLES:

Next week, I plan to focus on outlining the software stack for the sensors and motors, along with having a more detailed design for the wristband pin out. A physical design for the band would also be ideal. Lastly, I also want to put in a purchase request for parts .