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.

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