1 / 27

ECE 477 Design Review Team 4  Spring 2006

ECE 477 Design Review Team 4  Spring 2006. Justin Thacker, Matt Kocsis, Ian Snyder, Dustin Poe. Outline. Project overview Project-specific success criteria Block diagram Component selection rationale Packaging design Schematic and theory of operation PCB layout

thea
Download Presentation

ECE 477 Design Review Team 4  Spring 2006

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. ECE 477 Design Review Team 4  Spring 2006 Justin Thacker, Matt Kocsis, Ian Snyder, Dustin Poe

  2. Outline • Project overview • Project-specific success criteria • Block diagram • Component selection rationale • Packaging design • Schematic and theory of operation • PCB layout • Software design/development status • Project completion timeline • Questions / discussion

  3. Project Overview • The Digital Real-time Intelligent Networked Kegerator will address safety, legal, usability, and economic concerns of draft beverage distribution. Alcohol consumption monitoring will provide a tool to allow a person to know exactly how much they have consumed, learn estimated legal limits, and reduce unauthorized or unlawful drinking. System control and monitoring will allow users to track inventory, decrease beverage waste, and predict future resource needs.

  4. Project-Specific Success Criteria • An ability to sense and control beverage temperature. • An ability to identify authorized users via electronic identification. • An ability to track consumption on an individual basis. • An ability to display user/device status on an LCD. • An ability to control the function of and report the status of the kegerator via an embedded web server.

  5. Block Diagram

  6. Microprocessor Selection

  7. LCD Selection

  8. RFID Reader Selection

  9. Packaging Design • Self contained unit • Easy to add on to existing system

  10. Schematic/Theory of Operation

  11. Schematic/Theory of Operation

  12. Schematic/Theory of Operation

  13. Schematic/Theory of Operation

  14. Schematic/Theory of Operation

  15. Schematic/Theory of Operation

  16. Schematic/Theory of Operation

  17. Schematic/Theory of Operation

  18. PCB Layout 236 mm 117mm

  19. Bottom Copper Digital Gnd i Analog Gnd / Power Gnd 50 mil Pins 2 and 3 Internally Connected Single Point of Analog and Digital Ground

  20. Top Copper 5V Traces 50 mil 3.3V 12V 50 mil 12V 60 mil

  21. PCB Layout Temp/Compress Biometric Future Dev Serial Interface Common Beverage Interface RCM3315 MicrocontrollerModule 5V and 3.3V Converters

  22. Common Beverage Interface • Have common I/0 simplified easily through symmetry • Segregates High Current Analog From Rest of Circuit

  23. DC to DC Converter • Traces made short and large as possible • Bypass Capacitors mounted underneath to get as close as possible • Power and Signal Gnds Segregated • EMI reduction

  24. Software Design/Development Status • All functions built into costate statements. • Temperature polling • Rabbit web • External events triggered by interupts. • Flowmeters: code working on rabbit • Other hardware over serial communication. • Bill Validator: code working on rabbit • RFID: code working on rabbit • LCD: code working on computer

  25. Project Completion Timeline • Week 8 – PCB and Schematic finalization and test circuits • Week 9 – Finalize PCB and test circuits • Week 10 – Complete all functional software modules and hardware testing • Week 11 – PCB integration and testing • Week 12 – Integrate controller functions with web and hardware testing • Week 13 – Add complex features • Week 14 – Test complex features, create video and poster • Week 15 – Final Presentation, Report

  26. Questions / Discussion

More Related