Meeting with Your TA

Description

By the Thursday of the third week, you must have a project approved, and should be ready to get working! At this time, you'll need to log into PACE and submit your schedule for the semester. Please be sure to make this as accurate as possible because once it's submitted, it can only be changed manually. Making a block of your schedule red means that you are unavailable during that time.

Once each person on your team has submitted their schedule, your TA will be able to easily check for available times to schedule a weekly meeting. Your TA should contact you, usually by the fourth week, via email, to set up a weekly meeting schedule at mutual convenience. During the first weekly meeting, your TA will assign your team a locker and a lab kit.

Weekly meetings with your TA are required and will be held throughout the entire semester until demonstrations are completed. Your TA is your project manager. The "homework" of the course consists of preparing for the weekly meetings. Your TA will evaluate your lab notebook each week, provide feedback, and recommend improvements. At each meeting you will be expected to present your progress since your last meeting, plans for the coming week, and any technical or administrative questions you need to discuss with your TA. You are expected to arrive on time and prepared to make good use of your time with your TA. Your TA may require that each team member to fill out the Progress Report Template and submit it to them prior to each weekly meeting.

Requirements and Grading

Attendance and participation in weekly meetings is required and will affect Teamwork and Lab Notebook scores. If you can't make it to a particular weekly meeting, it is your responsibility to inform your TA prior to the meeting time and set up an alternate time.

Submission and Deadlines

Your schedule must be submitted by the end of the third week of class and you will receive an email from your TA shortly after. Your first meeting with your TA should be during the fourth week of the semester.

Prosthetic Control Board

Caleb Albers, Daniel Lee

Prosthetic Control Board

Featured Project

Psyonic is a local start-up that has been working on a prosthetic arm with an impressive set of features as well as being affordable. The current iteration of the main hand board is functional, but has limitations in computational power as well as scalability. In lieu of this, Psyonic wishes to switch to a production-ready chip that is an improvement on the current micro controller by utilizing a more modern architecture. During this change a few new features would be added that would improve safety, allow for easier debugging, and fix some issues present in the current implementation. The board is also slated to communicate with several other boards found in the hand. Additionally we are looking at the possibility of improving the longevity of the product with methods such as conformal coating and potting.

Core Functionality:

Replace microcontroller, change connectors, and code software to send control signals to the motor drivers

Tier 1 functions:

Add additional communication interfaces (I2C), and add temperature sensor.

Tier 2 functions:

Setup framework for communication between other boards, and improve board longevity.

Overview of proposed changes by affected area:

Microcontroller/Architecture Change:

Teensy -> Production-ready chip (most likely ARM based, i.e. STM32 family of processors)

Board:

support new microcontroller, adding additional communication interfaces (I2C), change to more robust connector. (will need to design pcb for both main control as well as finger sensors)

Sensor:

Addition of a temperature sensor to provide temperature feedback to the microcontroller.

Software:

change from Arduino IDE to new toolchain. (ARM has various base libraries such as mbed and can be configured for use with eclipse to act as IDE) Lay out framework to allow communication from other boards found in other parts of the arm.