F15: Doorknock over Bluetooth - Revision history

Proj user20: /* Project Title */

2015-12-19T02:17:03Z

‎Project Title

Proj user20: /* Grading Criteria */

2015-12-19T02:16:35Z

‎Grading Criteria

Proj user20: /* Objectives & Introduction */

2015-12-19T02:16:16Z

‎Objectives & Introduction

Proj user20: /* Design & Implementation */

2015-12-19T02:15:53Z

‎Design & Implementation

Proj user20: /* Hardware Interface */

2015-12-19T02:15:33Z

‎Hardware Interface

Proj user20: /* Software Design */

2015-12-19T02:15:18Z

‎Software Design

Proj user20: /* Implementation */

2015-12-19T02:15:01Z

‎Implementation

Proj user20: /* Testing & Technical Challenges */

2015-12-19T02:14:38Z

‎Testing & Technical Challenges

Proj user20: /* Conclusion */

2015-12-19T02:14:11Z

‎Conclusion

Proj user20: /* Appendix */

2015-12-19T02:13:36Z

‎Appendix

← Older revision		Revision as of 02:17, 19 December 2015
Line 1:		Line 1:
−	== ~~Project Title~~ ==	+	== DoorKnock over Bluetooth ==
−	~~Doorknock over Bluetooth~~	+

← Older revision		Revision as of 02:16, 19 December 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>~~
−
	== Project Title ==		== Project Title ==
	Doorknock over Bluetooth		Doorknock over Bluetooth

← Older revision		Revision as of 02:16, 19 December 2015
Line 21:		Line 21:

	== Objectives & Introduction ==		== 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.~~

@@ Line 102: / Line 102: @@
 == 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 ===
-Discuss your hardware design here.  Show detailed schematics, and the interface here.
 [[File:cmpe146_F15_Doorknock_HWSchematic.png|thumb|450px|Figure 1. Hardware Design Schematic]]
 For the Bluetooth module, UART communication was used to send data to the mobile application, alerting the user of a knock on the door.

← Older revision		Revision as of 02:15, 19 December 2015
Line 156:		Line 156:

	=== Hardware Interface ===		=== 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 communication between the vibration sensor and the SJSU One board takes place through the GPIO pin P0.26, which is configured during initialization to operate as an analog-to-digital converter (ADC). The analog signal is sent over a wire to the board, which then converts the value to a scaled digital value.		The communication between the vibration sensor and the SJSU One board takes place through the GPIO pin P0.26, which is configured during initialization to operate as an analog-to-digital converter (ADC). The analog signal is sent over a wire to the board, which then converts the value to a scaled digital value.

← Older revision		Revision as of 02:15, 19 December 2015
Line 199:		Line 199:

	=== Software Design ===		=== 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.

	For this project, the team used FreeRTOS tasks to design and execute the main drivers of the device. The software for the Android application will be discussed in a later section. The flowchart below depicts the basic operation of our device's software.		For this project, the team used FreeRTOS tasks to design and execute the main drivers of the device. The software for the Android application will be discussed in a later section. The flowchart below depicts the basic operation of our device's software.

@@ Line 232: / Line 232: @@
 === Implementation ===
 '''Vibration Sensor:'''
@@ Line 262: / Line 261: @@
 [[File:cmpe146_F15_Doorknock_DoorKnockApp.png|thumb|200px|right|Figure 6. DoorKnock App Icon]]
 === Android Application ===
 [[File:cmpe146_F15_Doorknock_AppInterface.png|thumb|200px|right|Figure 7. App User Interface]]

@@ Line 338: / Line 338: @@
 == Testing & Technical Challenges ==
 === Issue #1: Piezo Sensor Sensitivity ===
 We used several different types of Piezo vibration sensors before deciding to use this particular Piezo Element model. The other sensors seemed to generate a lot of noise and provided inconsistent resulting voltage values.

← Older revision		Revision as of 02:14, 19 December 2015
Line 375:		Line 375:

	== Conclusion ==		== 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?

	Overall, this project was very exciting to work on. In all honesty, it gave us more motivation to work on this project compared to our own senior design projects. The doorknock idea was something that was fun and could potentially be used in a real life situation. One of the main things that we have learned to the development of an Android app. Neither one of us has ever developed an app before and it was definitely at great learning experience. We also became much more familiar with driver writing, UART bus communication, Bluetooth communication, FreeRTOS tasks, and sensor interfacing. The ability to receive data from a Bluetooth module to a smartphone was quite amazing. Combining all the individual modules to create our successful end product was a very rewarding experience.		Overall, this project was very exciting to work on. In all honesty, it gave us more motivation to work on this project compared to our own senior design projects. The doorknock idea was something that was fun and could potentially be used in a real life situation. One of the main things that we have learned to the development of an Android app. Neither one of us has ever developed an app before and it was definitely at great learning experience. We also became much more familiar with driver writing, UART bus communication, Bluetooth communication, FreeRTOS tasks, and sensor interfacing. The ability to receive data from a Bluetooth module to a smartphone was quite amazing. Combining all the individual modules to create our successful end product was a very rewarding experience.

← Older revision		Revision as of 02:13, 19 December 2015
Line 403:		Line 403:

	Android Communicate to HC-06 Bluetooth Module: http://android-er.blogspot.com/2015/07/android-example-to-communicate-with.html		Android Communicate to HC-06 Bluetooth Module: http://android-er.blogspot.com/2015/07/android-example-to-communicate-with.html
−
−	~~=== Appendix ===~~
−	~~You can list the references you used.~~