S17: Smart Planter - Revision history

Proj user9: /* Android App */

2017-05-27T06:30:12Z

‎Android App

Proj user9: /* Software Design */

2017-05-27T06:25:20Z

‎Software Design

Proj user9: /* Android Things App */

2017-05-27T06:02:27Z

‎Android Things App

Proj user9: /* Server Application */

2017-05-27T06:01:32Z

‎Server Application

Proj user9: /* Android Things App */

2017-05-27T05:59:01Z

‎Android Things App

Proj user9: /* Testing & Technical Challenges */

2017-05-27T05:57:35Z

‎Testing & Technical Challenges

Proj user9: /* Testing & Technical Challenges */

2017-05-27T05:45:16Z

‎Testing & Technical Challenges

Proj user9: /* Issue #2 */

2017-05-27T05:35:35Z

‎Issue #2

Proj user9: /* References */

2017-05-27T05:32:28Z

‎References

Proj user9: /* Raspberry Pi 3 */

2017-05-27T05:24:55Z

‎Raspberry Pi 3

@@ Line 379: / Line 379: @@
 The app will continuously listen for data from the server. When data is received the UI is updated with the most recent sensor data.
-The app displays the following information:
+The following information is displayed in the UI:
 * Connection status of the Android app to the server and Smart Planter system
@@ Line 402: / Line 402: @@
 </ul></div>
-The below flowchart shows the software design of Android application.
+The app targets Android API 25 (Nougat; Android 7.0) but the minimum API supported is 19 (KitKat; Android 4.4). The flowchart below shows the software design of Android application.
 [[File:Cmpe244_S17_t6_Android_app.png|center|500px|thumb|High-level block diagram of the Android app]]

@@ Line 370: / Line 370: @@
 [[File:Cmpe244_S17_t6_Flowchart.jpg|center|900px|thumb|Flow chart]]
 ==== Android App ====
@@ Line 408: / Line 401: @@
 <li style="display: inline-block;"> [[File:Cmpe244_S17_t6_Android.jpg|right|230px|thumb|Android app connected to Smart Planter system]] </li>
 </ul></div>
 ==== Server Application ====

@@ Line 441: / Line 441: @@
 ==== Android Things App ====
-Android Things (an OS based on the low levels of Android targeting IoT projects) runs on a Raspberry Pi 3. The development language for Android Things is the same as for Android (Java) and the IDE Android Studio is also used for development.
+Android Things is an OS based on the low levels of Android targeting IoT projects. In our project the Android Things OS (developer preview 4) runs on a Raspberry Pi 3. The development language for Android Things is the same as for Android (Java) and the IDE Android Studio is also used for development.
 The app communicates with the SJOne over UART (using interrupts on both boards) and with the server using the Socket.io JavaScript library.

@@ Line 410: / Line 410: @@
 ==== Server Application ====
-The server uses the Socket.io JavaScript library to receive data from the Android Things app (such as the sensor data) and forwards the data to the Android app.
+The server (a Digital Ocean Droplet) uses the Socket.io JavaScript library to receive data from the Android Things app (such as the sensor data) and forwards the data to the Android app. All of the code was written in JavaScript in the Atom text editor. In addition, WinSCP is a client used to load the code to the server from a local development machine.
 An example of the light sensor readings being received by the server from the Android Things app (the socket.on portion) and forwarding this data to the Android app (the io.sockets.emit) is below:

@@ Line 441: / Line 441: @@
 ==== Android Things App ====
-Android Things (an OS based on the low levels of Android targeting IoT projects) runs on a Raspberry Pi 3.
+Android Things (an OS based on the low levels of Android targeting IoT projects) runs on a Raspberry Pi 3. The development language for Android Things is the same as for Android (Java) and the IDE Android Studio is also used for development.
 The app communicates with the SJOne over UART (using interrupts on both boards) and with the server using the Socket.io JavaScript library.

← Older revision		Revision as of 05:57, 27 May 2017
Line 782:		Line 782:

	This issue has not been resolved yet. One possible solution is to save the state at the server (the "middle" part of the system) rather than at the ends of the system (the Android app being at one end and the SJOne at the other).		This issue has not been resolved yet. One possible solution is to save the state at the server (the "middle" part of the system) rather than at the ends of the system (the Android app being at one end and the SJOne at the other).
		+
		+	====Issue #4 ====
		+	The Android app will not alert the user right away that the Android Things app/Raspberry Pi 3 has gone offline after previously being connected to the Internet. Currently, the app has to reload (i.e. when the Android device is rotated) before it can determine that the Pi 3 is offline.

	== '''Conclusion''' ==		== '''Conclusion''' ==

← Older revision		Revision as of 05:45, 27 May 2017
Line 775:		Line 775:

	We faced several issues integrating sensors to our PCB design, there were several components that needed further circuit implementation. This was due to the SJOne not being able to supply enough current to activate the transistors/Solid State Relay that we had at our disposal. The components that required further hardware included light sensor, DC Pump, and AC Lamp. We addressed these issues by creating another custom perforated board design on top of our PCB. The circuit diagrams for these can be seen in the DC Pump, Light Sensor, and AC Lamp sub-sections of Hardware Interface section. To address this issue in the future our PCB design would include level shifting circuits as well as buffer to be able to activate a wider variety of devices.		We faced several issues integrating sensors to our PCB design, there were several components that needed further circuit implementation. This was due to the SJOne not being able to supply enough current to activate the transistors/Solid State Relay that we had at our disposal. The components that required further hardware included light sensor, DC Pump, and AC Lamp. We addressed these issues by creating another custom perforated board design on top of our PCB. The circuit diagrams for these can be seen in the DC Pump, Light Sensor, and AC Lamp sub-sections of Hardware Interface section. To address this issue in the future our PCB design would include level shifting circuits as well as buffer to be able to activate a wider variety of devices.
		+
		+	====Issue #3 ====
		+	Both switches in the Android app reflect the state of the water pump and light with respect to the SJOne. There is an issue where the state of the switches in the app change quickly from on to off then back on again after the user has pressed one of the switches on.
		+
		+	The change from the on to off state in the Android app is caused by the original state of the pump and light (in this case off) at the SJOne side being sent through the system to the Android app before the SJOne receives the command to turn on the pump or light. Once the SJOne receives the request to turn on the pump or light, then it sends the new state (on) to the Android app (which causes the last change in the Android UI switch from off to on).
		+
		+	This issue has not been resolved yet. One possible solution is to save the state at the server (the "middle" part of the system) rather than at the ends of the system (the Android app being at one end and the SJOne at the other).

	== '''Conclusion''' ==		== '''Conclusion''' ==

@@ Line 774: / Line 774: @@
 ====Issue #2 ====
-We faced several issues integrating sensors to our PCB design, there were several components that needed further circuit implementation. This was do to the SJOne not being able to supply enough current to activate the transistors/Solid State Relay that we had at our disposal. The components that required further hardware included light sensor, DC Pump, and AC Lamp. We addressed these issues by creating another custom perforated board design on top of our PCB. The circuit diagrams for these can be seen in the DC Pump, Light Sensor, and AC Lamp sub-sections of Hardware Interface section. To address this issue in the future our PCB design would include level shifting circuits as well as buffer to be able to activate a wider variety of devices.
+We faced several issues integrating sensors to our PCB design, there were several components that needed further circuit implementation. This was due to the SJOne not being able to supply enough current to activate the transistors/Solid State Relay that we had at our disposal. The components that required further hardware included light sensor, DC Pump, and AC Lamp. We addressed these issues by creating another custom perforated board design on top of our PCB. The circuit diagrams for these can be seen in the DC Pump, Light Sensor, and AC Lamp sub-sections of Hardware Interface section. To address this issue in the future our PCB design would include level shifting circuits as well as buffer to be able to activate a wider variety of devices.
 == '''Conclusion''' ==

@@ Line 806: / Line 806: @@
 == '''References''' ==
-[1] [https://developer.android.com/things/preview/index.html "Android Things - Getting Started with the SDK Preview"] <br>
+[1] [https://developer.android.com/things/preview/index.html Android Things - Getting Started with the SDK Preview] <br>
 [2] [https://github.com/androidthings/sample-uartloopback Android Things - Samples - UART Loopback] <br>
 [3] Hoisington, Corinne. Android Boot Camp for Developers Using Java: A Guide to Creating Your First Android Apps. Boston, MA: Cengage Learning,2016 <br>

← Older revision		Revision as of 05:24, 27 May 2017
Line 298:		Line 298:

	==== Raspberry Pi 3 ====		==== Raspberry Pi 3 ====
		+	[[File:Cmpe244_S17_t6_RPI3.jpg\|right\|330px\|thumb\|Raspberry Pi 3]]
		+
	The Raspberry Pi 3 connects to the SJOne using UART (the SJOne utilizes UART2 and the Pi 3 uses its UART0).		The Raspberry Pi 3 connects to the SJOne using UART (the SJOne utilizes UART2 and the Pi 3 uses its UART0).