1 / 17

System Level Design Review

System Level Design Review. Customer: Dr. Lamkin-Kennard Faculty Guide: Ed Hanzlik. P10029: Control Enhancements for Air Muscle Biomimetic Hand. Team Members:. Zach Wessner, Jaci Tylkowski, Alex Bean Mark Wood, Tuan Tran, Kevin Mudrak. October 16, 2009. Summary.

afia
Download Presentation

System Level Design Review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. System Level Design Review Customer: Dr. Lamkin-KennardFaculty Guide: Ed Hanzlik P10029: Control Enhancements for Air Muscle Biomimetic Hand Team Members: Zach Wessner, Jaci Tylkowski, Alex Bean Mark Wood, Tuan Tran, Kevin Mudrak October 16, 2009

  2. Summary • P10029 is a continuation project • Physical system was built by P09023 • Final design will be integrated into Dr. Lamkin-Kennard’s pneumatically driven scalable robotic hand devices • Controls system is the focus • Maintenance and repair only of the physical system • Virtual and Physical prototypes • Virtual system modeled in SolidWorks and both controlled by LabView

  3. Customer Needs • Kinematic model - SolidWorks/Cosmos Motion Builder • Closed loop feedback for both hand and model. • Drive modelusing the inputs from the mechanical hand. • Virtual and Physical models output displacements • Quantitative analysis comparing displacements of mechanical hand to model.

  4. Voice of the Engineer • Top 3 Metrics based on the HOQ • Functionality • Accuracy • Repeatability

  5. System Level Risks

  6. System Level Architecture Inputs to LabView GUI -% of Travel -3 Space Location -System Selection (Physical/Virtual) -Coded Movements -Absolute/Relative Joint Position LabView GUI Physical System Architecture Virtual System Architecture Physical Programming Function -convert input into time to open/close valves -convert DAQ voltages into position outputs • Virtual Programming Function • convert GUI input into angular actuation for joints • -convert sensor output to 3 Space Location InputsOutputs

  7. Physical Architecture 2.5 to 10 VDC

  8. Controls Architecture

  9. NI LabView 2009 w/ SoftMotion SolidWorks 2009 Premium SoftMotion Functions Trajectory Generator Communication Interface (Scan Engine) Motion Simulation Virtual Architecture User Input: [SolidWorks Assembly]Motion Analysis System Output: [SolidWorks Assembly]Visual Motion of Assembly User Input: [LabView Front Panel]Coordinate MoveSingle Axis Move System Output: [LabView Front Panel]Displacement Feedback

  10. Virtual Proof of Concept • Goal: • LabView 2009 SoftMotion: meets objectives? • Educate team for full-scale model • System architecture • Plan • Simplified SolidWorks model • Research & tutorials for LabView • Develop LabView control (single axis) • Functional Evaluation • Joint design, movement, controls scheme, feedback • Iterative (adding complexity)

  11. Virtual Proof of Concept SolidWorks Model 1 DOF Simulated Joint

  12. Virtual Proof of Concept

  13. Virtual Proof of Concept • Issues / Risks: • Scan Engine Period [5ms or 10 ms] / Deployment • Virtual Controls Scheme differs from Physical • Virtual Error = 0?

  14. Physical System Risks/Issues • Leaking air muscles • Excessive play due to rubber mount (not measurable for feedback because sensor is also moving) • Slop in finger joint • Pulleys breaking, and translating • Past teams poor documentation misguiding our repairs • USB 2.0 needed

  15. Evaluation Method • Concepts generated for measurement of displacement • Measurement of error was also considered

  16. Critical Dates • System Level Design Review – 10/16/09 • Detailed Design Review – 11/06/09 (3 weeks) • Virtual Concept Selected • Physical Prototype benchmarked • Controls (Physical & Virtual) designed • Project Management Review – 11/20/09 (5 weeks) • Controllable virtual system • Controllable physical system • Calibration Plan / DAT Plan

  17. Decisions/Action Items • Are our resources sufficient? • Physical System • Computer • Software • Are we solving the right problem?

More Related