ECE 477 Design Review Team 07  Spring 2014

1. ECE 477 Design Review Team 07  Spring 2014 From left to right: Michael Standiford, Rebecca Krause, Amanda Schultz, Mark Luzarowski

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 Automatic Bartender is a project which presents a simple user interface to allow bar patrons to select and electronically mix their own drinks. The device will feature at least five connections to attach different types of liquid, and small pumps will control the flow of liquid. The machine will also feature a mechanism for accepting and recording payment for drinks.

4. Project-Specific Success Criteria • An ability to run a cleaning cycle of water through the device. • An ability to process, record, and generate statistics for payments based on monetary input on site and/or via account. • An ability to control the output volumes of various fluids drawn from connected canisters. • An ability to allow the user to input commands via buttons from a screen monitor based upon a generated GUI. • An ability to allow the user to choose their own drinks and choose custom contents of each drink via the GUI.

5. Block Diagram

6. Component Selection Rationale • Microcontroller: LPC1768 • 100MHz • 512KB Flash Memory • 8 PWM • 8 ADC • Ethernet capable

7. Component Selection Rationale • Raspberry Pi: • HDMI capable • Ethernet/USB • Programming ease • Memory: Spansion S25FL127S • 128MB size for asset storage • 6MB/s

8. Component Selection Rationale • LCD Screen: • 7 inch display (800*480) • Aspect Ratio: 16:9 • Driver Board • HDMI/VGA connections • 12 V power supply • Keyboard

9. Component Selection Rationale • Pumps: • Food grade • 5 volt input • Output: 1.0L/min • Valves: • ¾” inlet • 12 VDC

10. Packaging Design

11. Package Design

12. Package Design

13. Package Design

14. Theory of Operation • Upon startup, retrieve library data over Ethernet • Wait for card swipe from Pi • Sends customer information to Microcontroller • Returns list of pertinent data • Microcontroller polls buttons • Decodes button inputs • control pumps to dispense liquid amounts • Based on drink database • Contingent on sensor inputs

15. Theory of Operation • Administrative mode • While not in operation • Cleaning cycle, general maintenance • While in operation • Emergency stop

16. Schematic

17. Schematic

18. Schematic

19. Schematic

20. Schematic

21. Schematic

22. Schematic

23. Schematic

24. PCB Layout • JTAG • Plugs go on outskirts • Resistors flipped to add space

25. PCB Layout • Pumps • Takes up large amounts of space • Bound to transistors • Close to micro

26. PCB Layout • BypassCapacitors • Close to micro

27. PCB Layout • LED Region • Large connector • Additional parts (resistors, shift register)

28. PCB Layout • Microcontroller • Centered • Large concentration of traces • Shorter trace length

29. PCB Layout • Ethernet • Close to Ethernet Jack

30. PCB Layout • Power • Isolated Regulators • Close to source • Close to filter capacitors

31. Software Design/Development Status • Still in design/prototyping stage • Raspberry Pi and Microcontroller setup • Button organization and preliminary screen plans in place • Memory option: flash • Code organization: command/flag driven • Raspberry Pi / Microcontroller interface

32. Software Design/Development Status • Fail-safe plans: • Cup solenoid valve is normally closed • Pumps are normally off • Sensors will be located at the base of the bottle so that the software can turn off the pump if bottle is empty • Admin Button

33. Software Design/Development Status

34. Software Design/Development Status

35. Software Design/Development Status

36. Project Completion Timeline

37. Project Completion Timeline

38. Questions / Discussion