MSD II: Week 11 Review

System operates on different terrains, meets most customer and engineering specifications

Created a second system without activation for data logging

Project Status: Outcomes

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

Project Status

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

Areas of Improvement

Crashing occurred at end of project, fell behind schedule (delayed system testing)

Project Plan: Outstanding Tasks

Task Name Owner Complete (%) Completetion GoalDefine Project  Concept Generation    Develop Proposed Design    Compile Systems Design Review    Part Selection    Detailed Design     Write function for SD card writing John/Sam 0% 1/18/2012 Debug and test code w/ micro-controller John/Sam   on going  Update risk assessment Pattie   on goingDetermine component testing Test Plan      Design Tasks: End of Quarter      Additional Tasks      Update EDGE Sam   on goingSenior Design II      

 Test to verify electrical (including computer) product specs Rob/John 90% 1/22/2012

  Test to verify mechaincal product specs Shane/Pattie 90% 1/16/2013  Built and test Battery Level Circuit Rob / CE 80% 12/21/2012  Create model for PCB and correct enclosure Pattie 90% 2/13/2013

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

Risk Assessment

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

Lessons Learned: Team

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

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

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

Individual Team Member Status

Dana

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

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

Individual Team Member Status