S15: Alarm Based Coffee Maker - Revision history

Preet: /* Grading Criteria */

2015-05-26T04:51:51Z

‎Grading Criteria

2015-05-25T17:07:26Z

‎Android App

2015-05-25T16:47:49Z

‎Android App

2015-05-25T15:05:01Z

‎Software Design

2015-05-25T15:00:40Z

‎Appendix

2015-05-25T14:57:37Z

‎Hardware Design

2015-05-25T14:55:20Z

‎Design & Implementation

2015-05-25T14:54:56Z

‎Schedule

2015-05-25T14:54:29Z

‎Software Design

2015-05-25T14:31:59Z

‎Hardware Interface

← Older revision		Revision as of 04:51, 26 May 2015
Line 1:		Line 1:
−	~~=== Grading Criteria ===~~
−	~~<font color="green">~~
−	* How well is Software & Hardware Design described?
−	* How well can this report be used to reproduce this project?
−	* Code Quality
−	* Overall Report Quality:
−	** Software Block Diagrams
−	** Hardware Block Diagrams
−	**: Schematic Quality
−	** Quality of technical challenges and solutions adopted.
−	~~</font>~~
−
	== Alarm Based Coffee Maker ==		== Alarm Based Coffee Maker ==

@@ Line 114: / Line 114: @@
     create_BT_socket();
     create_connecting_Thread()
-[[File:S15_Cmpe146_Coffee_Alarm_Menu.png]]
+[[File:S15_Cmpe146_Coffee_Alarm_Menu.png|200px|thumb|left|app screenshot]]

@@ Line 113: / Line 113: @@
     get_pairedDevice();
     create_BT_socket();
-    create_connecting_Thread();
+    create_connecting_Thread()
   [[File:S15_CmpE146_Coffee_Alarm_Screen1.jpg|200px|thumb|left|app screenshot]]
 *2. Entering the time (Screen 2)
@@ Line 124: / Line 127: @@
      sendhour();
      sendmin();
 == Free RTOS Tasks ==
 There are a total of seven tasks that were implemented using wrapper functions. They are meant to run the smart coffee maker with only the alarm time as a manual input.

@@ Line 104: / Line 104: @@
 The coffee maker alarm has software for two systems, the embedded system and the Android App. The embedded system is a collection of tasks that execute without user input, while the Android App gathers input from the user.
-Android App
+== Android App ==
 *1. A User selects the bluetooth device connected to their coffee maker. (Screen 1)
 - We decided to allow the user to select the device instead of hardcoding a MAC address so that we could use different bluetooth modules, and allow future users to easily use our app with their own bluetooth  module.
@@ Line 114: / Line 114: @@
     create_BT_socket();
     create_connecting_Thread();
-  [[File:S15_CmpE146_Coffee_Alarm_Screen1.jpg|200px|thumb|left|alt text]]
+  [[File:S15_CmpE146_Coffee_Alarm_Screen1.jpg|200px|thumb|left|app screenshot]]
 *2. Entering the time (Screen 2)
 - A user selects the time at which they would like their coffee maker to wake them up.
@@ Line 124: / Line 124: @@
      sendhour();
      sendmin();
 === Implementation ===

← Older revision		Revision as of 15:00, 25 May 2015
Line 158:		Line 158:

	=== Appendix ===		=== Appendix ===
−	~~http://developer.android.com/index.html~~

← Older revision		Revision as of 14:57, 25 May 2015
Line 91:		Line 91:

	=== Hardware Design ===		=== Hardware Design ===
		+	All the pins were connected from the SJSU One Board to the other modules as shown in the figure below. The BT module and motion sensor required a Vcc of 3.3V, and were connected to the microcontroller, while the MP3 player required a Vcc of 5v and was connected to the USB.
		+
		+
		+
	[[File:S15_Cmpe146_Coffee_Alarm_HardwareSchematic.png\|200px\|thumb\|schematic]]		[[File:S15_Cmpe146_Coffee_Alarm_HardwareSchematic.png\|200px\|thumb\|schematic]]

@@ Line 88: / Line 88: @@
 == Design & Implementation ==
-The design section can go over your hardware and software design.  Organize this section using sub-sections that go over your design and implementation.
 === Hardware Design ===

← Older revision		Revision as of 14:54, 25 May 2015
Line 33:		Line 33:

	== Schedule ==		== 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.

	{\| class="wikitable"		{\| class="wikitable"

@@ Line 105: / Line 105: @@
 - We decided to allow the user to select the device instead of hardcoding a MAC address so that we could use different bluetooth modules, and allow future users to easily use our app with their own bluetooth  module.
 - The precondition is that the BT module has been paired with the Android phone using the phones bluetooth settings.
-- If the BT device establishes a connection with the phone, this screen will disappear and allow the user to enter a time.
+- If the BT device establishes a connection with the phone, this screen will disappear and allow the user to enter a time. A connection is also indicated by a green LED light on the bluetooth module.
    '''Pseudo code:'''
     list_BT_devices();

@@ Line 95: / Line 95: @@
 === Hardware Interface ===
-The Hardware communicates through UART.  The Bluetooth module strips the bluetooth packets of all the wrappers and delivers a UART frame to the SJSU One Board. The smartphone sends a packet of data to the bluetooth module (through bluetooth) and the the bluetooth module relays it to the SJSU One Board. All other modules communicate through GPIO Pins, although the Mp3 player needed to be initialized using UART. The uart frame sends 8 bits of data. The start is indicated by a high-to-low transition, and a stop is indicated by a low to high transition.  When a frame is not being sent, the line is held HIGH as shown in the image below.
+In this project the microcontroller communicates with its' peripheral devieces through a UART connection and GPIO pins. The Bluetooth module communicates through UART, it strips the bluetooth packets of all the wrappers and delivers a UART frame to the SJSU One Board. The smartphone sends a packet of data to the bluetooth module and the the bluetooth module relays it to the SJSU One Board. All other modules communicate through GPIO Pins, although the MP3 player needed to be initialized using UART. The uart frame sends 8 bits of data. The start is indicated by a high-to-low transition, and a stop is indicated by a low to high transition.  When a frame is not being sent, the line is held HIGH as shown in the image below.
 [[File:S15_Cmpe146_Coffee_Alarm_UartFrame.png‎]]