Team Status Report for 2/21

The biggest risk we are facing right now is our parts not arriving on time. We are behind schedule if they do not come this week as our plan was to assemble the glove and begin testing. However, without hardware we are still making progress working on the communication between Raspberry Pi and software as well as working on the user-interface. This week we will finish the Design document and assemble the glove if our parts arrive. We will also continue implementing the software portions that we do not need hardware for.

 

This week we also formalized parts of the design for the design report, like picking which protocols we’ll use for MVP and final. The glove is based on Raspberry Pi and will use C for the controls. The IMU will use I2C to communicate with the Raspberry Pi. The flex resistors will communicate with the Raspberry Pi through its GPIO, possibly with capacitors to filter out noise. For MVP, the glove will communicate with the computer via USB, but we’d like to do wireless communication for final. We’re considering adjusting the weight requirements based on the batteries we’ve been able to find: if we can’t find a light enough battery to make the glove easy to use, we’ll need to switch to powering the glove with a USB cable or similar, but make the cable long so it’s still ergonomic.

Teadora’s Status Report 2/21

This week I worked on the design presentation, then presented it on Monday. To get ready for the presentation, I had to confirm several details about our solution approach, like which protocols and languages we’ll use for the ASL glove. I also ordered more parts and worked with Quinn to handle a supply issue. The supply issue has me concerned that we won’t have parts before Spring Break, which would push us back 2 weeks. If the parts are here this week, I’ll test them to make sure I can get data out, attach them to the glove, and start figuring out what formulas we’ll use to convert sensor data into reasonable measurements / sign classification.

Teadora’s Status Report for 2/14

This week I ordered the first set of parts for the glove (Spectra Symbol Flex Sensors), and looked into other parts. For example, I looked at the datasheets for several different IMUs Adafruit sells to consider how much data we need (ex: do we need magnetic field sensing? Probably not, and it’ll save us $5 on budget). I’ve decided to use a Raspberry Pi Pico 2W since it’s lightweight and has WiFi and Bluetooth capability. We borrowed a Raspberry Pi 5 (8Gb) from lending, but it won’t work for the final model since it’s too big. We’ll also need a monitor and keyboard to interface with it, which we need to get from ITS. I also worked on the Design Presentation

Team Status Report for 2/14

Like last week, there are no significant risks at this stage. We’re in the process of ordering parts, trying to balance getting enough parts early while not blowing our budget if the parts aren’t right. However, we have a pretty good idea of which specific parts we need at this point. We need to look into software choices soon, including how to receive data and use it to build the model.

Part A was written by Nia

Our project aims to improve welfare by providing education to all for learning ASL and increasing fluency. We’re taking into account safety by ensuring batteries that won’t overheat during use.

Part B was written by Teadora

The product solution we’re designing meets needs for social factors. ASL (and other sign languages) are a large part of the deaf community, and it’s common for signed languages to be a child’s first language, especially if people in their family are hard of hearing. Learning sign language can also be useful for older adults since hearing loss can occur later in life, especially as a complication of other health concerns. In recent years, it’s become more common to see sign interpreters in everyday events, like concerts, government press briefings, and other events with live speakers. While sign language interpreting is a complicated skill that takes many years to master, learning sign language is an important way to connect with the deaf community and create accessible environments. Our solution will help people learn ASL and facilitate communication between different cultural groups.

https://www.asha.org/siteassets/ais/ais-comorbidities-and-hearing-loss.pdf

https://signhealth.org.uk/resources/learn-about-deafness/deaf-or-deaf/

 

Part C was written by Katherine

The economic factors are important as there are many versions of our product that are similar being built so it is very important we create a cheap and easily accessible one. Our production should be high quality and also cheaper than other products. As for distribution we want it to be easily accessible which we are demonstrating by creating ourselves with parts we order ourselves.

Teadora’s Report for 2/7/2026

This week I contributed to the project proposal, specifically the slides explaining hardware. I also did the website setup. I think we are slightly behind schedule since we haven’t ordered parts yet. We will resolve this by ordering parts online and from the inventory in our Monday meeting. I want to work on board to computer console communication this week since we can get a RPi from inventory and play around with it while waiting for flex sensors.