Final Presentation

Description

Presentations of the projects are given a few days after the Final Demo to an audience of fellow student reviewers, the lab instructors, and occasionally faculty or even students from outside the class who are following up a project of personal interest to them. The style is formal and professional, and students should dress accordingly (Generally business professional, or what you would wear to a career fair).

Requirements and Grading

Each project team has 25 minutes for a Powerpoint presentation and questions. Every group member must present their own work contributing to the project and be ready to answer questions. Presentations are judged on the basis of presentation technique and of technical organization and content.

Presentation technique includes dress, use of display materials (slides), clarity of speech, absence of filler words/fidgeting, proper eye contact with audience and smooth transitions between speakers. Content is judged on use of a proper introduction, orderly and connected development of ideas, absence of unnecessary details, proper pacing to stay within the allotted time, and an adequate summary at the close of the talk. Quantitative results are expected whenever applicable. Here is a general outline to follow:

  1. Introduction to your team and your project.
  2. Objective. What problem are you solving?
  3. Brief review of original design, statement on areas of design that changed, and overview of each functional block's requirements.
  4. Description of project build and functional test results. You can choose to include a short (30s) video of your project here.
  5. Discussion of successes and challenges, as well as explanations of any failed verifications demonstrating and understanding of the engineering reason behind the failure
  6. Conclusions from the project: what did you learn, what would you do differently if you redesigned your project, etc.
  7. Recommendations for further work.

Any significant, relevant ethical issues should be briefly addressed, preferably in a single slide.

Presentations will be graded using the presentation grading rubric. Your slides should follow ECE or College of Engineering presentation theming.

Submission and Deadlines

Slides for your final presentation must be uploaded to your project page on PACE prior to your presentation time. Deadlines for signing up may be found on the Calendar. Sign-up for the final presentation is done through PACE. Remember to sign up for a peer review of another group.

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.