S15: MENL (Monster Encounter Night Light) - Revision history

Preet: /* Grading Criteria */

2015-05-26T04:50:09Z

‎Grading Criteria

146 user6: /* Conclusion */

2015-05-26T01:27:38Z

‎Conclusion

146 user6: /* Implementation */

2015-05-26T01:18:41Z

‎Implementation

146 user6: /* Hardware Interface */

2015-05-26T01:05:45Z

‎Hardware Interface

146 user6: /* Testing & Technical Challenges */

2015-05-26T00:39:27Z

‎Testing & Technical Challenges

146 user6: /* References Used */

2015-05-26T00:25:29Z

‎References Used

146 user6: /* Appendix */

2015-05-26T00:24:25Z

‎Appendix

146 user6: /* Acknowledgement */

2015-05-26T00:21:18Z

‎Acknowledgement

146 user6: /* Project Video */

2015-05-26T00:17:55Z

‎Project Video

146 user6 at 00:16, 26 May 2015

2015-05-26T00:16:38Z

← Older revision		Revision as of 04:50, 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>~~
−
	== MENL (Monster Encounter Night Light) ==		== MENL (Monster Encounter Night Light) ==

@@ Line 193: / Line 193: @@
 == 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?
+We had more problems then success in this project. Although, we though this will be a simple project, in reality we ended up having to drop a few things and changing projects because of the failure of fixing some problems. We learned about the uncertainty that this sensors bring, having timing issues ( specially from the motion sensor) that lead to late responses, which not only affected our testing but lead to hour and hours analyzing why we were getting the opposite reaction, when it was just the time. Overall, we learn about analog to digital conversion, learn a little bit more with I2C specially when we were working with the LCD Display, we worked with pulse width modulation when we working on the servos, and learn about the GPIO and SPI libraries offer from FreeRtos. At the end we should have done better, but we think we can actually complete this project, which is marketable to large population that buy toys just because is the new thing in town.
 === Project Video ===

@@ Line 177: / Line 177: @@
 === Implementation ===
-This section includes implementation, but again, not the details, just the high level.  For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash.  You can include sub-sections for each of your component implementation.
+A Step by Step process of our implementation run like this
 == Testing & Technical Challenges ==

@@ Line 143: / Line 143: @@
 === 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.
+For the parts required to complete our project, we opted on using GPIO for the motion sensor since we only needed to read a high and low signal from it to know if anyone was approaching MENL. The distance sensor provided us with an analog output which lead us the analog to digital libraries provided in FreeRtos. For the LED matrices, we tested it using the spi 1 library as well as we created our own SPI driver from our previous lab assigments. Both of them work exactly the same. Since the board came with a Pic device, all we needed to do was to send the correct byte through SPI. In addition, we needed a chip select to enable the output for the registers controlling the matrices. We used a GPIO signal for this. Similar to the SPI part, we used our own drivers, but decided to use the libraries to reduce the amount of code. All of this components work together are shown below.
 [[File: S15_146_GRP3_LED_MATRIX_BACKandFront.jpg|500px |thumb|LED Matrix source: https://www.olimex.com/Products/Modules/LED/MOD-LED8x8RGB/open-source-hardware ]]

@@ Line 180: / Line 180: @@
 == 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?
+The first thing that we would tell ourselves if we were able to go back in time is to buy better devices. The sensors that we bought are really sensible and have delays and other problems that lead to obtaining the wrong outcome or the receive the outcome at different unexpected times. We notice this when testing. Our first test we did was the first time we were going to use the motion sensor in a while after having it tested a few weeks after it had arrived. We notice that it didn't work and it wasn't until we found out that sensor has an extra delay that makes the sensor take more then 40 seconds for it to start working properly. Also, the pins for the distance sensor are really sensitive and don't stay put. We notice this since it would sometimes measure the correct distance and a second later it will be negative. In addition, one they actually work, we did multiple test by moving our hands at different distances from both sensors. When we notice that it actually work, we installed the servo which we had been able to make it work by itself. However, we had to take it off from a few of the test that we had, ended up making MENL become FMENL, (flying monster encounter night light). Then, we retested everything again the night previous to the presentation, and notice that the distance sensor wasn't able to actually produce the night light since it kept detecting that there was something in front of it, when there was nothing at all.
 === My Issue #1 ===

@@ Line 210: / Line 210: @@
 === References Used ===
-List any references used in project.
+We made all of our code with the libraries provided by FreeRtos and Drivers created from previous labs projects.
 === Appendix ===

← Older revision		Revision as of 00:24, 26 May 2015
Line 213:		Line 213:

	=== Appendix ===		=== Appendix ===
−	~~You can list the references you used~~.	+	* PIR Motion Sensor (JST) Datasheet: https://www.sparkfun.com/datasheets/Sensors/Proximity/SE-10.pdf
		+	* MOD-LED8x8RGB schematics: https://www.olimex.com/Products/Modules/LED/MOD-LED8x8RGB/resources/MOD-LED8x8RGB_Rev_B1_sch.pdf
		+	* Infrared Proximity Sensor - Sharp GP2Y0A21YK : https://www.sparkfun.com/datasheets/Components/GP2Y0A21YK.pdf
		+	* The CMPE 146 wiki page

@@ Line 206: / Line 206: @@
 == References ==
 === Acknowledgement ===
-Any acknowledgement that you may wish to provide can be included here.
+We would like to Ann Verakukala for providing us with one of the LED Matrices.
 === References Used ===

@@ Line 196: / Line 196: @@
 === Project Video ===
 Upload a video of your project and post the link here.
-  [[Media:https://www.youtube.com/watch?v=Bbh2tejiG7Y&feature=youtu.be]]
+  https://www.youtube.com/watch?v=Bbh2tejiG7Y&feature=youtu.be
 [[File: S15_146_GRP3_Night_Light.jpg|500px|centre|thumb|Night Light]]
   [[File: S15_146_GRP3_EYES_OPEN.jpg|500px|centre|thumb|Eyes Closed]]