190 likes | 346 Views
Final Product Design Presentation P13265 Motorcycle Safety Lightin g Backpack Team. May 10th, 2013 RIT MSDII. MSD Team. Primary Customers: Sport bike/standard riders who ride with backpacks Surrogate Customer Andrew Nauss Faculty Guides: Leo Farnand Vince Burolla Team Members:
E N D
Final Product Design PresentationP13265Motorcycle Safety Lighting Backpack Team May 10th, 2013 RIT MSDII
MSD Team • Primary Customers: • Sport bike/standard riders who ride with backpacks • Surrogate Customer • Andrew Nauss • Faculty Guides: • Leo Farnand • Vince Burolla • Team Members: • Mike Baer, Project Manager • Tyler Davis, Lead Engineer • Ben Shelkey, ME Project Engineer • TJ Binotto, EE Project Engineer • Eric Dixon, EE Project Engineer • Killian Castner, Industrial Designer
Today’s Agenda • Overview 3 mins, 2 slides • Project Description Recap • Customer Needs • System Model Design 5 mins, 4 slides • Final Design • Testing 3 mins, 2 slides • Functionality vs. Test Plan • Project Management Review 8 mins, 2 slides • Schedule vs. MSDII Plan • Budget vs. Planned Budget • Next Steps 10 mins, 6 slides • Lessons Learned • Next Steps • Moving Forward, Comments
Concept Summary Problem: Want to reduce number of motorcycle accidents and deaths caused by other motorists Solution: Visibility product aimed at increasing safety of motorcycle rider Design: Backpack with LED turn signals, brake, and running lights that operate wirelessly with vehicle
Final DesignBackpack Brake/Running Lights User Control Panel On Chest Strap “Quick” access pouch Turn Signals Zipper attachment to hard-shell Electronics Box Inside Bottom Backpack Compartment Lower compartment for electronics housing Soft back and straps cut from existing backpack
Final DesignChest Strap User Control Panel Battery Health LEDs On/Off Button Hazard Button Light Brightness High/ Low Button StatusLEDs Control Panel (w/ Cover) Control Panel PCB • Concept to Creation- Changes and Problems: • Rapid prototyped instead of vacuum formed • Battery LED colors changed • LED push buttons are not two position (light up all the time) • Buttons not waterproof
Final DesignElectronics Housing* NiMH rechargeable battery Receiver XBee On/Off Power Button USB charging port 40 pin ribbon connector for light signals • Concept to Creation- • Changes and Problems: • Housing container • thicker than design • Low voltage battery shut-off • non-functional AC NiMH Charger Port Motorcycle Battery “Quick” Connect Port Flash Pattern Select Push Buttons * Lid Not Pictured
Final DesignMotorcycle Bergquist Thermal Adhesive Wireless Light Signals Out Transmitter Box Bike Light Signals In (Inside Box) Transmitter Board w/ Xbee Transmitter Bike Power • Concept to Creation- • Changes and Problems: • No standoffs used due to Bergquist donation • Board resized due to box being too small • Box is unnecessarily tall
Test Results *N/C= not completed
Test Results *N/C= not completed
Schedule vs. Plan Major Milestones:
Project Budget vs. Plan • Initial budget set to $500 • Increased to $1,000 • Team spent ~$1,200 • Unexpected/ high item costs: • 3 revisions of PCB’s with new components: • 1st $100 (budgeted for) • 2nd $90 (not budgeted for) • 3rd $150 (budgeted for in budget increase) • Mistakes • 1 Xbee units shorted ~$20 • Light covers knocked off chest strap buttons ~$10 • Etc. • Team meeting to divide costs among responsible members
Lessons Learned: Mechanical • Shell Assembly: • Problem: Thermoforming process did not create ideal results • Reason: Did not test assumptions about process • Lesson: Confirm manufacturing method limitations prior to final design • Backpack Oversized: • Problem: Backpack is too large for average person to wear • Reason: CAD models not accurate prior to build • Lesson: Print out CAD models to scale, check for tolerances between assemblies
Lessons Learned: Electrical • Board layout: • Problem: Major mistakes made in 2 board layouts • Reason: Lack of attention to detail during review • Lesson: A systematic, thorough approach is necessary to prevent careless, costly, and time-consuming mistakes • Software: • Problem: Software is not fully developed, which prevented full functionality (e.g. PWM and high/low functionality) • Reason: Poor planning/ uneven work distribution • Lesson: Make more refined deadlines/ don’t underestimate the complexity of software development
Lessons Learned: Group Dynamics • Planning: • Problem: Almost every major milestone missed • Reason: Did not follow MSDII plan, lack of motivation • Lesson: Plans are there for a reason, use them • Communication: • Problem: Disconnect/ lack of communication between team members • Reason: Not always prompt in responses, not asking questions • Lesson: Communicate frequently
Next Steps • Next Week: • Populate new board next week (upon arrival) • Complete all electronics testing • Install and test system on motorcycle • This summer: • Will present at RIT’s technology tent at the Wegman’s LPGA tournament
Future Improvements • Mechanical: • Redesign for smaller size • More precise manufacturing process • Electrical: • Complete software functionality • Change battery and wireless technologies • Overall Product: • Redesign for mass production • Reduce build cost
Thank You for Your Time! Questions?