Difference between revisions of "F16: I2Coffee"
(→Implementation) |
|||
| Line 1: | Line 1: | ||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
== Abstract == | == Abstract == | ||
i2Coffee is a coffee maker machine that allows its user to pick from different types of | i2Coffee is a coffee maker machine that allows its user to pick from different types of | ||
Revision as of 05:59, 20 December 2016
Contents
Abstract
i2Coffee is a coffee maker machine that allows its user to pick from different types of coffee powders. i2Coffee will also allow the user to choose their ideal coffee temperature.
Objectives & Introduction
Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.
Team Members & Responsibilities
- Man Hin Wong
- Emil: wongmanhin@msn.com
- Mauricio Rivera
- Email: mauricio.rivera1993@yahoo.com
Schedule
Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.
| Week# | Date | Task | Actual |
|---|---|---|---|
| 1 | 11/4 | Finalize schedule and materials. | Done |
| 2 | 11/11 | Design schematic with slave and master board. | Done |
| 3 | 11/18 | Test I2C code and enhance it. | Pending. |
| 4 | 11/25 | Debug and enhance code. | Done |
| 5 | 12/2 | Start building project. | Done |
| 6 | 12/9 | Test prototype. | Pending. |
| 7 | 12/16 | Finalize project and demo. | Pending. |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Item | Quantity | Cost (1) |
|---|---|---|
| SJSU One Board | 2 | $60 |
| 5V DC Motors | 4 | $2 |
| 5V Servos | 3 | $3 |
| Shoe Box | 1 |
Design & Implementation
Hardware Design
Block diagram
Hardware Interface
In this section, you can describe how your hardware communicates, such as which BUSes used. You can discuss your driver implementation here, such that the Software Design section is isolated to talk about high-level workings rather than inner working of your project.
The coffee making machine uses I2C protocol to establish communication between a master and slave board using the SDA and SCL pins. The slave SJSUOne board is also used to control the different I/O components used in this project. To allow any of the components to receive a signal from the slave board, transistors were placed between the board and the I/O components to allow the component to go from 0V to 5V when necessary (see Figure 2).
Hardware Used
- Transistor
- Resistors
- 5v DC Motor
- 12V Fan
- 5v Step Motor
- Water Valve
- Bread Board
- Jumper Cables
Software Design
Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.
The software of this machine is designed to interact with the user so that the user's needs are met. The buttons on the board are programmed to control the options for coffee beans, temperature, and the mixing.
Implementation
Inserting a transistor between the SJSUOne board and the I/O component helped to control the component and activate it when needed. Motors and Transistor Interface
Connecting Transitor to I/O component
- Connect power supply (5V) to bread board
- Emmitter is connected to resistor (<200 Ohms)
- Resistor connects to board's GPIO pin
- Base pin Connected to component's ground
- Component's Vcc connected to power supply
- Collector pin goes to power supply's ground
Testing & Technical Challenges
Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.
Include sub-sections that list out a problem and solution, such as:
My Issue #1
Discuss the issue and resolution.
Conclusion
Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?
Project Video
Upload a video of your project and post the link here.
Project Source Code
References
Acknowledgement
Any acknowledgement that you may wish to provide can be included here.
References Used
List any references used in project.
Appendix
You can list the references you used.
