Senior Design Team • Prosthetic arm

Project Overview

Our team recognized a fundamental problem that amputees in today's society still do not have access to affordable, life normalizing, myoelectric prosthetic arms. Amputees are exposed to undue stress in all aspects of their lives. One solution to this problem is a robotic prosthetic, however, most solutions in today's market cost anywhere from $20,000 to $100,000 before insurance. This represents an additional financial burden that is unnecessarily forced upon them. Our goal is to design an affordable solution to disrupt the market. We have no plans of mass manufacturing, but if we are able to design and prove our concept in less than a year, we can hopefully provide a better option for some people and put pressure on manufacturers who are currently overcharging for their products. The largest benefit of this project is that development is student driven and university funded, so there are no overhead costs and no profit margin that will be passed on to users.

Battery Management System (BMS)

The BMS circuit was tested on a breadboard by setting all of the components and subjecting the circuit to an input voltage of 5V. This simulated the standard voltage that comes out of a phone charger. The voltage that would be sent back to the battery through the battery terminals was measured to be 7.583V which is slightly higher than the nominally charged voltage of 7.4V experienced by the battery. Further implementation was tested by applying 7.4V at the battery terminals and testing to see if the BMS circuit relayed the correct charge level of the simulated battery. This test had some form of success but only 3 of the 5 charge indicator lights lit at this voltage level. The following lights would turn on when a voltage of 7.8 and 8.3 V were hit respectively.


Motherboard

For the MCU, powering up the component failed. Multiple parts on the motherboard began to heat at a very rapid rate. After troubleshooting the primary power components it was determined that the primary power trace had been blown causing a massive short. This short caused a current draw of nearly 3 Amps. In order to test this theory further a second motherboard was populated with all of the power components one at a time in order to test for current draw and if the trace that the team believed to be blown would could be fully determined. The second motherboard did not pull near the current through the board as the first had but a significant amount of current (512 mA) was observed when the 3.3V linear voltage regulators had been added to the second motherboard. A little more indepth research led the team to believe that that the trace between the 5V and 3.3V regulator was not of correct width for the expected current draw of the motherboard. The images below show the required trace width requirements for both the inner and outer layer traces that make up the power distribution circuits in the board. These trace widths could also be mitigated by adding more of the 5V voltage regulators allowing for less current to be drawn from a single regulator and thus lowering the required width of the traces.


Motor Driver Board

The motor driver circuit was tested through the PCB as the motor drivers were only found in surface mount components making it difficult for the team to test the circuit in a breadboard environment. Once the PCB was populated with the correct components a voltage of 7.4V was applied to the power input terminals. This then turned on lights found on the motors and ensured that the encoders of every motor were powered. Since the motherboard at this point had already failed, a separate breadboard was connected to a raspberry pi in order to test encoder outputs. Proper measurement of the encoder outputs were seen by the raspberry pi and the motor drivers could be controlled through all of the ports adding to a successful implementation of the driver board circuit.


Team Members

Jack Vetsch

Electrical

Jack is a transfer fifth year senior in Electrical Engineering with a focus in semiconductors and a previous focus on biomedical engineering before his transfer. He also participates in the decathlon for the Division 1 Track and Field team here at Iowa State. He hopes to bring a knowledge of biomechanics and leadership to help our team succeed.

Erik Raman

Software

Erik is a senior in software engineering. He does coding work for Iowa State laboratories and loves messing around with Arduinos. When he’s not doing technical work, he can be found doing some bouldering at the ISU climbing walls.

Jake Eisbrenner

Mechanical/Electrical

Jacob is a senior in Electrical and Mechanical Engineering with a focus in biosensors and bionic devices. His hobbies include tinkering with electronics, 3D printing, and working on cars.

Jeremy Wallace

Electrical

Jeremy is a senior in Electrical Engineering with a focus in controls. In his spare time he enjoy running, creating music, and tinkering with electronics.

Leo Forney

Software

Leo is a senior in Software Engineering. He specializes in mobile development and operating systems. In his free time he enjoys snowboarding, skateboarding, frisbee golf, and making software.

Scott Bolek

Electrical

Scott is a Senior in Electrical Engineering with a focus on semiconductor devices and VLSI design. When not working on classwork he works at the data center under Durham Hall and goes on cross country motorcycle trips yearly.

Sean Gray

Electrical

Sean is a senior in Electrical Engineering with a focus on automation and programming. He also works on multiple project cars in his free time.





Semester 1: 491 (Weekly Reports)

Report 1
Report 2
Report 3
Report 4
Report 5
Report 6
Report 7
Report 8
Report 9
Report 10
Report 11




Semester 2: 492 (Bi-Weekly Reports)

Report 1
Report 2
Report 3
Report 4
Report 5
Report 6




Design Documents

Requirements
User needs
Project Plan
Final Design Document
Final Poster
Design Context And Exploration