1 / 13

MSD II: Week 11 Review

MSD II: Week 11 Review. Project Status: Outcomes. System operates on different terrains, meets most customer and engineering specifications Created a second system without activation for data logging. Project Status. Budget: used $462.76 for both system components

callie
Download Presentation

MSD II: Week 11 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. MSD II: Week 11 Review

  2. Project Status: Outcomes • System operates on different terrains, meets most customer and engineering specifications • Created a second system without activation for data logging

  3. Project Status • Budget: used $462.76 for both system components • Missing some testing metrics • SD card does not operate • Could not test code for accuracy since did not work on the board

  4. Areas of Improvement • Create smaller electronics box • Reduce weight, improve aesthetics, switch in correct location • Different battery • Reduce size and weight, improve usage time • Recommend using plastic fittings • Weight reduction, corrosion resistance, could not find in store • SD card expansion board • Improve data collection • Human Trials with AFO that fits user • More accurate data collection

  5. Project Plan: Outstanding Tasks • Crashing occurred at end of project, fell behind schedule (delayed system testing)

  6. Risk Assessment • Did not update as much during MSDII • Few points added at beginning of MSDII • Trouble-shooting done “on the fly” • Could have utilized more during trouble-shooting phases

  7. Lessons Learned: Team • Critical tasks should be completed earlier • Communication for overlapping tasks • Need strict deadlines and avoid falling behind • Design concepts may need to be slightly modified in order to be properly implemented • Parts break when not handled properly-this will put you back a few days • Feedback from outside sources helps to catch mistakes • Allow time for feedback and revisions

  8. Individual Team Member Status Pattie • Followed the project plan to plan tasks • Created new PCB model for next stage, updated electronics enclosure • Finalized and submitted Technical Paper • Created Poster • Created report out presentations • Updated text on EDGE

  9. Individual Team Member Status Shane • Assembled and tested mechanical parts (pre-build) • Attachment of mechanical subsystems to modified orthotic • Assisted in attaching electrical components to orthotic • Tested mechanical functionality and specifications

  10. Individual Team Member Status Rob • Designed an electrical circuit to interface with the processor, battery and sensors • Built and tested a prototype for the electrical system • Designed a PCB based on the prototype • Populated and tested the PCB with the orthotic and all other systems • Tested electrical functionality and specifications

  11. Individual Team Member Status Dana

  12. Individual Team Member Status Sam • Write code for reading sensors • Outline code for SD card even though it didn’t work • Work with John to develop code for determining terrain, when the foot is on or off the ground

  13. Individual Team Member Status John • Developed code for testing battery • Developed code for determining terrain and on or off ground value with Sam • Mounted electrical components on both AFO and secondary systems • Modified enclosures for the system to house all the components

More Related