S16: Sprinkler - Revision history

Preet: /* Grading Criteria */

2016-05-26T19:57:42Z

‎Grading Criteria

Proj user22: /* Project Source Code */

2016-05-25T03:30:58Z

‎Project Source Code

Proj user22: /* Software Design */

2016-05-25T01:15:07Z

‎Software Design

Proj user22: /* Software Design */

2016-05-25T01:14:33Z

‎Software Design

Proj user22: /* Software Design */

2016-05-25T01:13:33Z

‎Software Design

Proj user22: /* Conclusion */

2016-05-25T01:12:24Z

‎Conclusion

Proj user22: /* Hardware Design */

2016-05-25T01:10:35Z

‎Hardware Design

Proj user22: /* Project Video */

2016-05-25T01:05:13Z

‎Project Video

Proj user22: /* Implementation */

2016-05-25T01:04:11Z

‎Implementation

Proj user22: /* Implementation */

2016-05-25T01:03:23Z

‎Implementation

← Older revision		Revision as of 19:57, 26 May 2016
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>~~
−
	== Smart Sprinkler System ==		== Smart Sprinkler System ==

@@ Line 433: / Line 433: @@
 === Project Source Code ===
-*  [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]
+*  [https://drive.google.com/open?id=0B7SIT3CI4e80bmg2dGY3VnV0dTA Google Drive Source Code Link]
 == References ==

@@ Line 257: / Line 257: @@
 '''Sprinkler Task'''
+The goal of the Sprinkler task is to activate the sprinkler device as instructed by the scheduler. The item received on the its queue define the duration of time in minutes to keep the sprinkler device active. For example, if the scheduler sent an item = 1 to the sprinkler's queue, then the sprinkler task will activate the sprinkler device for 1 minute long. The sprinkler task set an event bit to let the scheduler know that the sprinkler device is active, and when the sprinkler device is turned off, the event bit is then cleared. We do this just as a sanity check to make sure the sprinkler device is not held active after the time duration passes.
 [[File:Sprinkler146 flow.JPG|300px|thumb|center|Figure 9. Sprinkler Task Design]]
 === Schedule Time ===

@@ Line 258: / Line 258: @@
 '''Sprinkler Task'''
-[[File:Sprinkler146 flow.JPG|300px|thumb|right|Figure 9. Sprinkler Task Design]]
+[[File:Sprinkler146 flow.JPG|300px|thumb|center|Figure 9. Sprinkler Task Design]]
 The goal of the Sprinkler task is to activate the sprinkler device as instructed by the scheduler. The item received on the its queue define the duration of time in minutes to keep the sprinkler device active. For example, if the scheduler sent an item = 1 to the sprinkler's queue, then the sprinkler task will activate the sprinkler device for 1 minute long. The sprinkler task set an event bit to let the scheduler know that the sprinkler device is active, and when the sprinkler device is turned off, the event bit is then cleared. We do this just as a sanity check to make sure the sprinkler device is not held active after the time duration passes.

@@ Line 237: / Line 237: @@
 The overall software design of the system used several tasks to accomplish its objective. Below are descriptions of each task and its responsibility.
-[[File:Cmpe_146-team_psa-Top_Level_Tasks.jpg|500px|thumb|centre|Figure 4. Top Level Tasks Design]]
+[[File:Cmpe_146-team_psa-Top_Level_Tasks.jpg|500px|thumb|centre|Figure 5. Top Level Tasks Design]]
 The Figure 4 above shows what data are transferred between tasks at the top level. The Irrigation Scheduler Task is the main task that dictates and controls the overall system by providing instruction to other tasks. For example, the Irrigation Scheduler Task send command codes that instruct the ESP8266 Task to perform certain functions such as connecting to wifi and obtain current time or weather data. The Irrigation Scheduler also instruct the Sprinkler Task to activate the sprinkler device for certain amount of minutes. Finally, when the scheduler need to obtain soil moisture reading, it instruct the Soil Moisture Sensor Task to take readings from its sensor. After completing its work, each task, excluding the scheduler, update event bits to notify the scheduler of their status.
-[[File:CmpE 146 Team PSA SysFlowChart.jpg|300px|thumb|right|Figure 5. Scheduler Task Flowchart]]
+[[File:CmpE 146 Team PSA SysFlowChart.jpg|300px|thumb|right|Figure 6. Scheduler Task Flowchart]]
 '''Scheduler Task'''
@@ Line 249: / Line 249: @@
 The goal of the ESP8266 Task is to process the command code provided by the scheduler and send the command over UART interface to control the ESP8266 Wifi Module. This task control the WiFi module through AT+<x> commands, where <x> is the parameter that define certain functions such as joining an access point, creating TCP  connection to server, send data, etc. For each command sent over to the WiFi module, the WiFi provide a response back of the query status or data depending on which type of commands used. The main usage of the ESP8266 task is to obtain such data including weather data, current time-stamp of location, and user's schedule through webservice API calls from ''Thingspeak'' and weather station.
-[[File:CmpE 146 Team PSA ESP8266 Task Design.jpg|700px|thumb|centre|Figure 6. ESP8266 Task Design]]
+[[File:CmpE 146 Team PSA ESP8266 Task Design.jpg|700px|thumb|centre|Figure 7. ESP8266 Task Design]]
 '''Soil Moisture Sensor Task'''
 The goal of the moisture sensor task was to enhance the functionality of the Sprinkler system. The moisture sensor outputted an analog signal with respect to the "resistance" between both probes. This signal was converted to a readable input by accounting the steps size, which was 4096 (2^12), due to the number of bits used in the signal. This information was sent and stored in the task to check the moisture level. A level below 25% was considered to by dry and if the value that was read upon the task waking up, an event bit would be set. This bit indicated to the irrigation scheduler task that the dirt was dry and needed to be watered. In the end, this adds the functionality of being efficient of when to water a lawn.
-[[File:Moist146 flow.JPG|300px|thumb|left|Figure 6. Moisture Sensor Task Design]]
+[[File:Moist146 flow.JPG|300px|thumb|left|Figure 8. Moisture Sensor Task Design]]
 '''Sprinkler Task'''
 The goal of the Sprinkler task is to activate the sprinkler device as instructed by the scheduler. The item received on the its queue define the duration of time in minutes to keep the sprinkler device active. For example, if the scheduler sent an item = 1 to the sprinkler's queue, then the sprinkler task will activate the sprinkler device for 1 minute long. The sprinkler task set an event bit to let the scheduler know that the sprinkler device is active, and when the sprinkler device is turned off, the event bit is then cleared. We do this just as a sanity check to make sure the sprinkler device is not held active after the time duration passes.
 === Schedule Time ===

@@ Line 425: / Line 425: @@
 === Project Video ===
-Demo
+[https://www.youtube.com/watch?v=jIWNVB63liU Hardware Setup]
-Demo with Moisture Sensor
-https://www.youtube.com/watch?v=ouFXmykhYAE
+[https://www.youtube.com/watch?v=Umf7tZogosM Demo]
 === Project Source Code ===

@@ Line 192: / Line 192: @@
 [[File:cmpe 146-team_psa-Top_level.JPG|1000px|thumb|centre|Figure 1. Hardware System Schematic.]]
-[[File:Valve.jpg|600px|thumb|center|Figure 2a. Valve System.]]
+[[File:Hardware.jpg|600px|thumb|centre|Figure 2a. Hardware in its case .]]
-[[File:Hardware.jpg|600px|thumb|centre|Figure 2b. Hardware in its case .]]
+[[File:Valve.jpg|500px|thumb|left|Figure 2b. Valve System.]]
-[[File:Sprinkler.jpg|600px|thumb|centre|Figure 2c. Sprinkler Head.]]
+[[File:Sprinkler.jpg|500px|thumb|centre|Figure 2c. Sprinkler Head.]]
 [[File:Sprinkler Deactivated.jpg|550px|thumb|left|Figure 3. Sprinkler Deactivated.]]

@@ Line 365: / Line 365: @@
 * clear event Bit_5 to signal scheduler that sprinkler device
 * set event Bit_4 to signal scheduler this task has finished doing work
 '''Soil Moisture Sensor Task'''
 Here is the process describing the steps the Soil Moisture Sensor Task takes upon receiving an item from the scheduler

@@ Line 348: / Line 348: @@
 . Update event bit
 * if WiFi error set Bit_1
-* set Bit_0, signaling scheduler the task has finish doing work
+* set Bit_0, signaling scheduler this task has finish doing work
-'''Sprinkler'''
+'''Sprinkler Task'''
 Here is the process describing the steps the Sprinkler task take when it received an item from the scheduler
@@ Line 364: / Line 364: @@
 * clear GPIO Pin 2.1, deactivating the sprinkler device
 * clear event Bit_5 to signal scheduler that sprinkler device
-* set event Bit_4 to signal scheduler the task has finished doing work
+* set event Bit_4 to signal scheduler this task has finished doing work
 == Testing & Technical Challenges ==