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.

Control System and User Interface for Hydraulic Bike

Iain Brearton

Featured Project

Parker-Hannifin, a fluid power systems company, hosts an annual competition for the design of a chainless bicycle. A MechSE senior design team of mechanical engineers have created a hydraulic circuit with electromechanical valves, but need a control system, user interface, and electrical power for their system. The user would be able to choose between several operating modes (fluid paths), listed at the end.

My solution to this problem is a custom-designed control system and user interface. Based on sensor feedback and user inputs, the system would change operating modes (fluid paths). Additionally, the system could be improved to suggest the best operating mode by implementing a PI or PID controller. The system would not change modes without user interaction due to safety - previous years' bicycles have gone faster than 20mph.

Previous approaches to this problem have usually not included an electrical engineer. As a result, several teams have historically used commercially-available systems such as Parker's IQAN system (link below) or discrete logic due to a lack of technical knowledge (link below). Apart from these two examples, very little public documentation exists on the electrical control systems used by previous competitors, but I believe that designing a control system and user interface from scratch will be a unique and new approach to controlling the hydraulic system.

I am aiming for a 1-person team as there are 6 MechSE counterparts. I emailed Professor Carney on 10/3/14 and he thought the general concept was acceptable.

Operating modes, simplified:

Direct drive (rider's pedaling power goes directly to hydraulic motor)

Coasting (no power input, motor input and output "shorted")

Charge accumulators (store energy in expanding rubber balloons)

Discharge accumulators (use stored energy to supply power to motor)

Regenerative braking (use motor energy to charge accumulators)

Download Competition Specs: https://uofi.box.com/shared/static/gst4s78tcdmfnwpjmf9hkvuzlu8jf771.pdf

Team using IQAN system (top right corner): https://engineering.purdue.edu/ABE/InfoFor/CurrentStudents/SeniorProjects/2012/GeskeLamneckSparenbergEtAl

Team using discrete logic (page 19): http://deepblue.lib.umich.edu/bitstream/handle/2027.42/86206/ME450?sequence=1