F13: Vehicle On Board Diagnostics - Revision history

Preet: /* Project Video */

2013-12-08T03:00:26Z

‎Project Video

Preet: /* Project Source Code */

2013-12-08T02:58:27Z

‎Project Source Code

Proj user11: /* Grading Criteria */

2013-12-08T01:25:17Z

‎Grading Criteria

Proj user11: /* Software Design */

2013-12-08T01:02:18Z

‎Software Design

Proj user11: /* Hardware Interface */

2013-12-08T00:53:34Z

‎Hardware Interface

Proj user11: /* Hardware Interface */

2013-12-08T00:52:00Z

‎Hardware Interface

Proj user11: /* Hardware Interface */

2013-12-08T00:41:23Z

‎Hardware Interface

Proj user11: /* Schedule */

2013-12-07T23:59:06Z

‎Schedule

Proj user11: /* Schedule */

2013-12-07T23:58:49Z

‎Schedule

Proj user11: /* Parts List & Cost */

2013-12-07T22:52:27Z

‎Parts List & Cost

@@ Line 206: / Line 206: @@
 === Project Video ===
-Upload a video of your project and post the link here.
+* [http://youtu.be/MdjbbQKWd3E Project Video]
 === Project Source Code ===

@@ Line 209: / Line 209: @@
 === Project Source Code ===
-Send me your zipped source code and I will upload this to SourceForge and link it for you.
+*  [https://sourceforge.net/projects/sjsu/files/CmpE240_LM_F2013/ Sourceforge link for source code]
 == References ==

← Older revision		Revision as of 01:25, 8 December 2013
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>~~
−
	== Vehicle On Board Diagnostics ==		== Vehicle On Board Diagnostics ==

@@ Line 182: / Line 182: @@
 === Software Design ===
-The software constantly sends commands to the ECU for RPM, speed, then temperature sequentially.  The commands should return values for RPM, speed, and temperature.  The RPM, speed, and temperature must be converted into understandable numbers.  Once translated, the data is passed to the LCD in a format for optimized display.  It is also stored in a TBD format to the SD card.
+The software loops through a routine to retrieve information from the car's engine control unit (ECU).  The routine is as follows.
+*Send a 1 byte UART 2 command in hex
-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.
+*Read UART 2 output data
 === Implementation ===

@@ Line 162: / Line 162: @@
 === Hardware Interface ===
 UART Bus
--UART 2 connection between the SJ One Board to the OBDII to UART board through Rx and Tx communication lines
+*UART 2 connection between the SJ One Board to the OBDII to UART board through Rx and Tx communication lines
--SJ One Board pins P0.10 "TXD2" and P0.11 "RXD2" interface to OBDII to UART board's RX-1 and TX-0 through jumper wires
+*SJ One Board pins P0.10 "TXD2" and P0.11 "RXD2" interface to OBDII to UART board's RX-1 and TX-0 through jumper wires
 SPI Bus
--SPI connection with onboard micro SD card and LCD display
+*SPI connection with onboard micro SD card and LCD display
--Place micro SD card in micro SD card holder
+*Place micro SD card in micro SD card holder
--Utilized SPI 1 connection between the SJ One Board and the LCD display from New Haven
+*Utilized SPI 1 connection between the SJ One Board and the LCD display from New Haven
--SJ One Board pins P0.9 "MOSI1", P0.7 "SCK1", and P1.28 "GPIO" connected to New Haven LCD Display J2 pin4 "SPI Data", J2 pin3 "SPI CLK", and J2 pin1 "SPI Slave Select"
+*SJ One Board pins P0.9 "MOSI1", P0.7 "SCK1", and P1.28 "GPIO" connected to New Haven LCD Display J2 pin4 "SPI Data", J2 pin3 "SPI CLK", and J2 pin1 "SPI Slave Select"
 I2C Bus (did not function)
--Alternative, I2C 2 connection between the SJ One Board and the LCD Display
+*Alternative, I2C 2 connection between the SJ One Board and the LCD Display
--SJ One Board pins P0.10 "SDA2" and P0.11 "SCL2" to LCD Display J2 pin4 "I2C data" and J2 pin4 "I2C clock"
+*SJ One Board pins P0.10 "SDA2" and P0.11 "SCL2" to LCD Display J2 pin4 "I2C data" and J2 pin4 "I2C clock"
--Observe that the pins interfere with the UART 2 connection so adaptation to a different UART port is necessary
+*Observe that the pins interfere with the UART 2 connection so adaptation to a different UART port is necessary
 Power and Grounding
--5V/1A Power is derived from the battery USB interface, a spliced USB cord directs power to the LCD and the SJ One Board
+*5V/1A Power is derived from the battery USB interface, a spliced USB cord directs power to the LCD and the SJ One Board
--The battery is rechargeable for continued use
+*The battery is rechargeable for continued use
--Grounds from the SJ One Board, LCD, and OBDII to UART board are shorted together through on the SJ One board
+*Grounds from the SJ One Board, LCD, and OBDII to UART board are shorted together through on the SJ One board
 === Software Design ===

← Older revision		Revision as of 00:41, 8 December 2013
Line 161:		Line 161:

	=== Hardware Interface ===		=== Hardware Interface ===
		+	UART Bus
		+	-UART 2 connection between the SJ One Board to the OBDII to UART board through Rx and Tx communication lines
		+	-SJ One Board pins P0.10 "TXD2" and P0.11 "RXD2" interface to OBDII to UART board's RX-1 and TX-0 through jumper wires
		+	-Placed ground wire jumper between the boards
		+
		+	SPI Bus
		+	-SPI connection with onboard micro SD card and LCD display
		+	-Place micro SD card in micro SD card holder
		+	-Utilized SPI 1 connection between the SJ One Board and the LCD display from New Haven
		+	-SJ One Board pins P0.9 "MOSI1", P0.7 "SCK1", and P1.28 "GPIO" connected to New Haven LCD Display J2 pin4 "SPI Data", J2 pin3 "SPI CLK", and J2 pin1 "SPI Slave Select"
		+
		+	I2C Bus
		+
	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.		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.

@@ Line 76: / Line 76: @@
 | 11/25
 | Debug and Complete wikipedia report
+| Y
 |-
 ! scope="row"| 9
 | 12/2
 | Prepare Presentation
+| Y
 |-
 |}

@@ Line 61: / Line 61: @@
 | 11/4
 | SPI interface with LCD display, Setup SPI H/W
+| N
 |-
 ! scope="row"| 6
 | 11/11
 | SPI to SD card interface
+| Y
 |-
 ! scope="row"| 7
 | 11/18
 | Purchase enclosure, Perform integration and test
+| Y
 |-
 ! scope="row"| 8

@@ Line 129: / Line 129: @@
 | Total
+|
-| 182.25
+| 196.80
 |-
 |}