ENGT 480 Project Notes (4) (2)

.pdf

School

Purdue University *

*We aren’t endorsed by this school

Course

480

Subject

Computer Science

Date

Apr 3, 2024

Type

pdf

Pages

3

Uploaded by PrivateStarlingPerson586

Nate Pitts AUET Team #9: Hurdy Gurdy FMEA Development Leader, PN6 March 6, 2024 Testing and Validation Manager Project Notes 1) Describe your contributions during the previous week: a) Research Wiring i. Further research on how to go about wiring the hurdy gurdy was conducted. To do this, wiring of the “Digi Gurdy” was analyzed. Following this, a basic knowledge of how to plan to wire the Hurdy Gurdy was acquired. A test plan was written out to help the process. - Identify all the components that need to be connected - mechanical elements - sensors (such as the rotary encoder) - Switches - Microcontroller - Sketch out a schematic diagram illustrating how these components will be interconnected - consider factors such as signal flow and power requirements - Determine the optimal placement of components within the hurdy gurdy's structure to ensure efficient wiring - Research best practices for wiring in musical instruments and MIDI interfaces to inform my approach. - create a detailed wiring plan document outlining the connections, wire routing, and any necessary modifications to the instrument's structure. This plan will serve as a roadmap for the wiring implementation phase, ensuring a well-organized and reliable system b) Researched Digi-Gurdy i) Similar to last week, the DigiGurdy was further researched. This is an example of a project that uses the same idea of making a Hurdy Gurdy MIDI compatible. This week, the parts list used for that project was analyzed. Doing so gave the team the opportunity to compare parts that we selected to the ones used for the “DigiGurdy” project. This gave the team better insight on which parts to buy now and knowledge for possible future parts.
c) FMEA progress i) A basic outline and start of the FMEA was conducted. I researched potential risks and failures that should be noted. These failures consisted of: - Key return rubber band breaks - Digital Switch breaks/ceases function - Encoder breaks/ceases function - Instrument does not work unless plugged in - Electrical short - Software Bug / Programming error - Instrument body breaks - Crank arm breaks - String breaks - Microcontroller Compatibility Issues After noting these potential failures, solutions were also implemented. Adding these potential solutions helps the team prepare for if these failures occur. Along with that, completing the FMEA helps the team’s progress in completing the Gate 2 Report. d) System Decomposition i) I helped contribute to the System Decomposition portion of the Gate 2 Report. This involved noting the different levels of the project and addressing those parts to the levels. My main contribution was finding and noting the parts used for each critical module. This helped the team make progress in the Gate 2 Report. 2) Describe your plan to contribute during the upcoming week: e) Look into 3D printed parts of the DigiGurdy i. Although this was planned to be researched this week, other tasks ended up taking priority. I plan to further research the 3D parts of the DigiGurdy. Doing this will allow me to get a good idea of a starting point for the structure needed. This will help the team make advancements of the structure of the first prototype.
Your preview ends here
Eager to read complete document? Join bartleby learn and gain access to the full version
  • Access to all documents
  • Unlimited textbook solutions
  • 24/7 expert homework help