F12: OBD-II Android Monitor - Revision history

Preet: /* Project Source Code */

2013-02-04T22:03:31Z

‎Project Source Code

Ryan f12: /* Android Application */

2012-12-19T07:16:07Z

‎Android Application

Ryan f12: /* Testing & Technical Challenges */

2012-12-19T06:42:39Z

‎Testing & Technical Challenges

Ryan f12: /* Testing & Technical Challenges */

2012-12-19T06:42:19Z

‎Testing & Technical Challenges

Ryan f12: /* Android Application */

2012-12-19T06:10:32Z

‎Android Application

Ryan f12: /* Appendix */

2012-12-19T05:41:24Z

‎Appendix

Ryan f12: /* Testing the Android Application */

2012-12-19T05:34:51Z

‎Testing the Android Application

Ryan f12: /* Android Application */

2012-12-19T05:34:20Z

‎Android Application

Ryan f12: /* Hardware Design */

2012-12-19T05:30:57Z

‎Hardware Design

Ryan f12: /* Schedule */

2012-12-19T05:29:52Z

‎Schedule

@@ Line 389: / Line 389: @@
 === Project Source Code ===
-Send me your zipped source code and I will upload this to SourceForge and link it for you.
+*  [http://sourceforge.net/projects/sjsuf12/files Project source code is available at SourceForge]
 == References ==

@@ Line 319: / Line 319: @@
 In terms of developing the front end of the application, there were two key elements to implement the GUI, creating the layout and creating the animations for the layout. There are many ways to make user interfaces as shown in Android's [http://developer.android.com/guide/topics/ui/index.html API Guides]. In the OBD-II Android Monitor, the application GUI used ImageView to create the background and gauges for the GUI.
-Before creating the layout, the layout orientation for the application was fixed to landscape. Modified in the ''AndroidManifest.xml'' file, using a landscape orientation provided a lower device profile as well as wider viewing angle. Figure X below shows the modification to set the layout to "landscape." If the application was to be portrait or can switch from both, then the orientation would be changed to "portrait" or "auto" respectively.
+Before creating the layout, the layout orientation for the application was fixed to landscape. Modified in the ''AndroidManifest.xml'' file, using a landscape orientation provided a lower device profile as well as wider viewing angle. Figure 10 below shows the modification to set the layout to "landscape." If the application was to be portrait or can switch from both, then the orientation would be changed to "portrait" or "auto" respectively.
@@ Line 325: / Line 325: @@
-[[File:CmpE146_F12_T6_ImageView.png|thumb|right|300px|Figure 11. ImageView]]To create the GUI layout, the ''main.xml'' from the ''res'' folder must be selected. ImageView features allows using an external source to import images to the application. In this case, the background and needles were the external sources to implement the gauges. In order to implement the background, select the "ImageView" under the palette section once main.xml is opened. As shown in Figure X. Once selected, an external image from either project or system folder can be imported into the application. In Figure 12, the cf.png image was imported from the ''res/drawable'' project folder.
+[[File:CmpE146_F12_T6_ImageView.png|thumb|right|300px|Figure 11. ImageView]]To create the GUI layout, the ''main.xml'' from the ''res'' folder must be selected. ImageView features allows using an external source to import images to the application. In this case, the background and needles were the external sources to implement the gauges. In order to implement the background, select the "ImageView" under the palette section once main.xml is opened as shown in Figure 11. Once selected, an external image from either project or system folder can be imported into the application. In Figure 12, the cf.png image was imported from the ''res/drawable'' project folder.
@@ Line 331: / Line 331: @@
-Once the file has been imported into the application, the image is then displayed into the workspace of the .xml file, as shown in Figure X.
+Once the file has been imported into the application, the image is then displayed into the workspace of the .xml file, as shown in Figure 13.

← Older revision		Revision as of 06:42, 19 December 2012
Line 355:		Line 355:

	To test the Android application for it's functionality. TeraTerm was used to send messages to the Nexus 7 over SPP to test if obtain the desired result. This helped to ensure that our regular expressions was correct and that there weren't any issues calculating data to be displayed on the gauges. The testing and debugging was mostly done through TeraTerm and once the team felt that there was significant progress added to the application functionality, then we would go out and test the application with the vehicle. It seemed very tedious to go out to the vehicle after every build, so TeraTerm helped out the team a lot with testing.		To test the Android application for it's functionality. TeraTerm was used to send messages to the Nexus 7 over SPP to test if obtain the desired result. This helped to ensure that our regular expressions was correct and that there weren't any issues calculating data to be displayed on the gauges. The testing and debugging was mostly done through TeraTerm and once the team felt that there was significant progress added to the application functionality, then we would go out and test the application with the vehicle. It seemed very tedious to go out to the vehicle after every build, so TeraTerm helped out the team a lot with testing.
−

	=== Issues with Getting Data From the ELM327 ===		=== Issues with Getting Data From the ELM327 ===

@@ Line 347: / Line 347: @@
 == Testing & Technical Challenges ==
 === Issues with Getting Data From the ELM327 ===
@@ Line 370: / Line 379: @@
 A drawback of using String.matches() and regular expressions is that it is a "hit or miss" scenario. This is due to the fact that the message received will either match or not match with the given regular expression. To address this, all message possibilities must be addressed and accounted for with regular expressions. This is essential to the performance of our application because the more matches obtained will give the user a real time response.
 == Conclusion ==

← Older revision		Revision as of 06:10, 19 December 2012
Line 298:		Line 298:
	As shown in the sample code, the use of regular expressions was used in order to parse the incoming data. The regular expression shown is to match incoming data of a two hex byte format such as "0F 5D." Once we are able to get a match with the incoming data, we then use String.trim() to remove any excess white space which will cause errors in calculations if not removed. Once we implemented the parsing code for Intake Temperature, we can apply the same methods to the other five parameters.		As shown in the sample code, the use of regular expressions was used in order to parse the incoming data. The regular expression shown is to match incoming data of a two hex byte format such as "0F 5D." Once we are able to get a match with the incoming data, we then use String.trim() to remove any excess white space which will cause errors in calculations if not removed. Once we implemented the parsing code for Intake Temperature, we can apply the same methods to the other five parameters.

−	Given the nature of the ELM327 OBD to serial interpreter, it is hard to predict the incoming string format response. Therefore, many regular expression cases were implemented in order to match data more often. It is desired to match data as much as possible in order to display the change in values as real time as possible which was a goal of this project.	+	Given the nature of the ELM327 OBD to serial interpreter, it is hard to predict the incoming string format response. Therefore, many regular expression cases were implemented in order to match data more often. It is desired to match data as much as possible in order to display the change in values as real time as possible which was a goal of this project.
		+
		+	Once the incoming data has been retrieved, the data must be converted into different units based on parameters. Each PID based on the OBD-II have a specific conversion formula to give users the actual value. These formulas can be found [http://en.wikipedia.org/wiki/OBD-II_PIDs here]. After conversion has been complete, the data values will then be sent to the front end of the application.

← Older revision		Revision as of 05:41, 19 December 2012
Line 407:		Line 407:

	=== Appendix ===		=== Appendix ===
−	~~You can list the references you used~~.	+	*[http://plxdevices.com/ PLX Devices Company Website]
		+	*[http://www.google.com/nexus/7/ Google Nexus 7 Product Page]

@@ Line 372: / Line 372: @@
 === Testing the Android Application ===
-To test and debug the Android application during development, TeraTerm was used as a tool. TeraTerm is an open source terminal application program for Windows that can communicate with SPP devices. Figure X. below shows a screenshot of the TeraTerm program.
+To test and debug the Android application during development, TeraTerm was used as a tool. TeraTerm is an open source terminal application program for Windows that can communicate with SPP devices. Figure 15. below shows a screenshot of the TeraTerm program.
-[[File:CmpE146_F12_T6_TeraTerm.jpeg|400px|thumb|center|Figure X. TeraTerm Serial Terminal]]
+[[File:CmpE146_F12_T6_TeraTerm.jpeg|400px|thumb|center|Figure 15. TeraTerm Serial Terminal]]
 To test the Android application for it's functionality. TeraTerm was used to send messages to the Nexus 7 over SPP to test if obtain the desired result. This helped to ensure that our regular expressions was correct and that there weren't any issues calculating data to be displayed on the gauges. The testing and debugging was mostly done through TeraTerm and once the team felt that there was significant progress added to the application functionality, then we would go out and test the application with the vehicle. It seemed very tedious to go out to the vehicle after every build, so TeraTerm helped out the team a lot with testing.

@@ Line 271: / Line 271: @@
-[[File:CmpE146_F12_T6_Manifest_2.JPG||thumb|350px|center|Figure 3. AndroidManifest.xml Original]]
+[[File:CmpE146_F12_T6_Manifest_2.JPG||thumb|350px|center|Figure 4. AndroidManifest.xml Original]]
-From Figure 3, the original Android manifest file only stated a minimum SDK version allowed but not a target version. This is a problem for Android devices using versions 4.0 and up. To correct this, add a target version which is shown in Figure 4.
+From Figure 4, the original Android manifest file only stated a minimum SDK version allowed but not a target version. This is a problem for Android devices using versions 4.0 and up. To correct this, add a target version which is shown in Figure 5.
-[[File:CmpE146_F12_T6_Manifest_1.JPG||thumb|350px|center|Figure 4. AndroidManifest.xml Modified]]
+[[File:CmpE146_F12_T6_Manifest_1.JPG||thumb|350px|center|Figure 5. AndroidManifest.xml Modified]]
-The next modification dealt with the Universally Unique Identifier (UUID) which is used by BluetoothChat to assign each connected device an ID. For our purposes of using BluetoothChat to connect to SPP devices, the UUID needed to be changed to a specific UUID used by all SPP devices which is shown in Figure 5.
+The next modification dealt with the Universally Unique Identifier (UUID) which is used by BluetoothChat to assign each connected device an ID. For our purposes of using BluetoothChat to connect to SPP devices, the UUID needed to be changed to a specific UUID used by all SPP devices which is shown in Figure 6.
-[[File:CmpE146_F12_T6_HWInterface.JPG||thumb|500px|center|Figure 5. UUID Code]]
+[[File:CmpE146_F12_T6_HWInterface.JPG||thumb|500px|center|Figure 6. UUID Code]]
@@ Line 293: / Line 293: @@
-[[File:CmpE146_F12_T6_SampleCode.png|center|thumb|550px|Figure X. Intake Temperature Parsing Sample Code]]
+[[File:CmpE146_F12_T6_SampleCode.png|center|thumb|550px|Figure 7. Intake Temperature Parsing Sample Code]]
@@ Line 303: / Line 303: @@
 ''' Android Frontend'''
-Figure A below displays the main page for the application.
+Figure 8 below displays the main page for the application.
-[[File:CmpE146_F12_T6_Screenshot.png|thumb|center|500px|Figure X. Android Application Interface]]
+[[File:CmpE146_F12_T6_Screenshot.png|thumb|center|500px|Figure 8. Android Application Interface]]
-[[File:CmpE146_F12_T6_SearchDevice.png|thumb|right|400px|Figure B. Device Connection Menu]]
+[[File:CmpE146_F12_T6_SearchDevice.png|thumb|right|400px|Figure 9. Device Connection Menu]]
-When opening up the application, the user must first connect to the PLX Kiwi by pressing on the button at the top right and selecting the device from the list (as shown in Figure B). Once the tablet has successfully connected, you can start the gathering of parameter data by pressing on the toggleButton on the bottom left. The second button is to clear check engine codes (if any are present in the vehicle).
+When opening up the application, the user must first connect to the PLX Kiwi by pressing on the button at the top right and selecting the device from the list (as shown in Figure 9). Once the tablet has successfully connected, you can start the gathering of parameter data by pressing on the toggleButton on the bottom left. The second button is to clear check engine codes (if any are present in the vehicle).
 To make it easier for the user to read the current data of the vehicle, Android textViews were also inserted into the gauges to provide a numerical representation. This allows the user to quickly identify the value of each current parameter. There are also TX and RX field to display the information that the tablet is currently sending and receiving at that particular moment.
@@ Line 320: / Line 320: @@
-[[File:CmpE146_F12_T6_Hlayout.png|thumb|center|400px|Figure X. Layout Orientation.]]
+[[File:CmpE146_F12_T6_Hlayout.png|thumb|center|400px|Figure 10. Layout Orientation.]]
-[[File:CmpE146_F12_T6_ImageView.png|thumb|right|300px|Figure X. ImageView]]To create the GUI layout, the ''main.xml'' from the ''res'' folder must be selected. ImageView features allows using an external source to import images to the application. In this case, the background and needles were the external sources to implement the gauges. In order to implement the background, select the "ImageView" under the palette section once main.xml is opened. As shown in Figure X. Once selected, an external image from either project or system folder can be imported into the application. In Figure X, the cf.png image was imported from the ''res/drawable'' project folder.
+[[File:CmpE146_F12_T6_ImageView.png|thumb|right|300px|Figure 11. ImageView]]To create the GUI layout, the ''main.xml'' from the ''res'' folder must be selected. ImageView features allows using an external source to import images to the application. In this case, the background and needles were the external sources to implement the gauges. In order to implement the background, select the "ImageView" under the palette section once main.xml is opened. As shown in Figure X. Once selected, an external image from either project or system folder can be imported into the application. In Figure 12, the cf.png image was imported from the ''res/drawable'' project folder.
-[[File:CmpE146_F12_T6_ImageView2.png|thumb|center|325px|Figure X. Importing External Image]]
+[[File:CmpE146_F12_T6_ImageView2.png|thumb|center|325px|Figure 12. Importing External Image]]
@@ Line 332: / Line 332: @@
-[[File:CmpE146_F12_T6_ImageView3.png|thumb|center|500px|Figure X. Android Workspace in Eclipse]]
+[[File:CmpE146_F12_T6_ImageView3.png|thumb|center|500px|Figure 13. Android Workspace in Eclipse]]
@@ Line 339: / Line 339: @@
-[[File:CmpE146_F12_T6_RotateAnimation.png|thumb|center|500px|Figure X. Using RotateAnimation for Intake Temperature Gauge]]
+[[File:CmpE146_F12_T6_RotateAnimation.png|thumb|center|500px|Figure 14. Using RotateAnimation for Intake Temperature Gauge]]
 From the sample code above, the Interpolator deals with the data rate of change. For circular gauges, we want the needles to move in a linear way. The setFillAfter(true) allows the gauge to stay at the final position. By default, RotateAnimation will rotate an image and then bring it back to it's previous position which isn't the desired behavior for gauges. More about the RotateAnimation API is detailed [http://developer.android.com/reference/android/view/animation/RotateAnimation.html here].
 == Testing & Technical Challenges ==

@@ Line 221: / Line 221: @@
 === Hardware Design ===
-The OBD-II is a computer system built into modern vehicles. The OBD-II is responsible for monitoring and recording vehicle operating information such as temperatures and engine fault codes. Following different protocols such as SAE J1979, SAE J1850, ISO 9141-2, and etc, many users are using the OBD-II interface as a scan tool to diagnose the status of their vehicles. A pinout of the OBD-II connector is shown in Figure 1. There are many OBD-II adapter devices in the market that range from $25-$200. The OBD-II Android Monitor project uses the PLX Kiwi Bluetooth by PLX Devices.
+The OBD-II is a computer system built into modern vehicles. The OBD-II is responsible for monitoring and recording vehicle operating information such as temperatures and engine fault codes. Following different protocols such as SAE J1979, SAE J1850, ISO 9141-2, and etc, many users are using the OBD-II interface as a scan tool to diagnose the status of their vehicles. A pinout of the OBD-II connector is shown in Figure 2. There are many OBD-II adapter devices in the market that range from $25-$200. The OBD-II Android Monitor project uses the PLX Kiwi Bluetooth by PLX Devices.
-[[File:CmpE146_F12_T6_OBDpinout.jpeg|thumb|center|Figure 1. OBD-II Pin Layout]]
+[[File:CmpE146_F12_T6_OBDpinout.jpeg|thumb|center|Figure 2. OBD-II Pin Layout]]
-Figure 2 is the block diagram for the OBD-II Android Monitor project. The Nexus 7 tablet communicates with the PLX Bluetooth Kiwi using serial over Bluetooth (SPP). Refer to the Hardware Interface section for details.
+Figure 3 is the block diagram for the OBD-II Android Monitor project. The Nexus 7 tablet communicates with the PLX Bluetooth Kiwi using serial over Bluetooth (SPP). Refer to the Hardware Interface section for details.
-[[File:CmpE146_F12_T6_Block_Diagram.jpg|thumb|600px|center|Figure 2. Hardware Block Diagram]]
+[[File:CmpE146_F12_T6_Block_Diagram.jpg|thumb|600px|center|Figure 3. Hardware Block Diagram]]
 === Hardware Interface ===

@@ Line 193: / Line 193: @@
 * Project report completed
 * System testing completed
-* Presented on Wed (Dec. 26th)
+* Presented Wednesday December 19
 </td>