Strain gauge

2,944 views

Published on

Published in: Education
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
2,944
On SlideShare
0
From Embeds
0
Number of Embeds
134
Actions
Shares
0
Downloads
106
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Strain gauge

  1. 1. Micro Strain Gauge <br />Real Time Measurement<br />Lennon Pultz, Kyle Stacy & Gabe Palkert<br />
  2. 2. Video Demonstration<br />Micro Strain Gauge Real Time Measurement<br />
  3. 3. THE PRODUCT<br /><ul><li>Initial product goal:
  4. 4. Produce a real time strain gauge measurement using more advanced technology than currently exists.
  5. 5. Our target audience:
  6. 6. Students and faculty of the Mechanical Engineering & Mechanical Engineering Technology Department</li></li></ul><li>PROJECT MANAGEMENT <br /><ul><li>How was the project managed:
  7. 7. Working in parallel utilizing Agile SCRUM methodology
  8. 8. Tasks broken down into subtasks utilizing iterative development
  9. 9. Collaboration:
  10. 10. Communicated via text and cell phone
  11. 11. Weekly group meetings in lab to discuss progress and issues
  12. 12. Breakfast club</li></li></ul><li>METHODOLOGIES<br /><ul><li>Jira for task management
  13. 13. SVN for version control
  14. 14. Confluence for wiki and project progress</li></li></ul><li>DEVELOPMENT TIMELINE<br /><ul><li>First, developed requirements and a wish list
  15. 15. Laid out and manufactured the PCB board for the analog to digital conversion
  16. 16. Create Hardware Prototype of case and design
  17. 17. Started working on displaying objects on the LCD board –Altera IP here helped
  18. 18. Started creating file I/O from ADS1231 to text file.</li></li></ul><li>EXTERNAL CASE<br /><ul><li>Power Plug
  19. 19. Key Holes for wall mounting
  20. 20. Large holes for wires from </li></ul> the strain gauges<br />
  21. 21. CASE PROTOTYPE<br /><ul><li>Designed in Solidworks
  22. 22. Worked with MET Rapid Prototype Lab to have the 3D model printed
  23. 23. Model Design: 4-6hrs
  24. 24. Print Time: 4hrs
  25. 25. Made of plastic</li></li></ul><li>PCB DESIGN & PRODUCTION<br /><ul><li>Schematic done in EAGLE
  26. 26. Utilize EAGLE net-list to layout board
  27. 27. Used mill purchased by department to produce double sided board and drill holes
  28. 28. Used on campus resources to place and solder parts.</li></li></ul><li>HIGH LEVEL DESIGN SPECIFICATION<br /><ul><li>Strain gauge connected to an in-house fabricated printed circuit board (PCB)
  29. 29. Connect through GPIO pins to DE2 development board
  30. 30. Touch Screen GUI is connected through GPIO pins to the DE2
  31. 31. Bridge was created to go between DE2 & MAVRK through serial i/o (RS-232)</li></li></ul><li>HARDWARE DESIGNVIDEO PROCESSOR<br /><ul><li>Utilizes NIOS II/f processor
  32. 32. Needed for fast refresh rates
  33. 33. Interfaces to the LCD Controller
  34. 34. Runs the GUI
  35. 35. Screen resolution: 400 x 240
  36. 36. Color Depth: 16 bits per pixel</li></li></ul><li>
  37. 37. IP DESIGN AND REUSE<br /><ul><li>Reused a significant amount of code in our system
  38. 38. LCD drivers
  39. 39. Altera University Program IP
  40. 40. Basic GUI from MP3 Player last year
  41. 41. Created these components:
  42. 42. VHDL for ADS1231
  43. 43. Test bench for testing ADS1231 component
  44. 44. File I/O average strain measurement </li></li></ul><li>GUI DESIGN<br /><ul><li>Image Display
  45. 45. All images are stored in the software code.
  46. 46. All characters are stored as images.
  47. 47. Touch screen response
  48. 48. Reads a flag controlled by the video processor.
  49. 49. Compares the x and y coordinates to a range represented by a button.
  50. 50. Main Menu
  51. 51. Obtain Data
  52. 52. Pause Data Sample
  53. 53. Clear Data</li></li></ul><li>CODE REVIEWS<br /><ul><li>Code coverage is a measure used in software testing. It describes the degree to which the source code of a program has been tested..
  54. 54. Functional verification, in electronic design automation, is the task of verifying that the logic design conforms to specification.
  55. 55. These generally help to improve coding as you may be doing something wrong that you don’t know</li></li></ul><li>ISSUES IN DEVELOPMENT<br /><ul><li>Time management
  56. 56. Communication between platforms
  57. 57. GUI Development
  58. 58. Acquiring hardware from Texas Instruments and digikey</li></li></ul><li>CONCLUSIONS<br /><ul><li>Accomplished most of our intended goals
  59. 59. Project was interesting and fun but also challenging
  60. 60. Lessons learned, recommendations
  61. 61. Future plans</li>

×