F16: OBD2 Reader - Revision history

146 user15: /* CAN Bus */

2016-12-21T01:59:38Z

‎CAN Bus

146 user15: /* Implementation */

2016-12-21T01:59:15Z

‎Implementation

146 user15: /* Implementation */

2016-12-21T01:59:01Z

‎Implementation

146 user15: /* Implementation */

2016-12-21T01:58:11Z

‎Implementation

146 user15: /* References Used */

2016-12-21T01:55:26Z

‎References Used

146 user15: /* Implementation */

2016-12-21T01:54:33Z

‎Implementation

146 user15: /* Implementation */

2016-12-21T01:52:05Z

‎Implementation

146 user15: /* Implementation */

2016-12-21T01:51:34Z

‎Implementation

146 user15: /* References Used */

2016-12-21T01:44:44Z

‎References Used

146 user15: /* Appendix */

2016-12-21T01:44:29Z

‎Appendix

@@ Line 41: / Line 41: @@
-The CAN Bus data message frame is composed of a Starting Frame, an Arbitration Field, a Control Field, Data Field, Cyclic Redundancy Check, Acknowledge Field, and an End of Frame. The Starting Frame is used to indicate the start of a message when bit is zero. The Arbitration Field is used to define the message priority. The Control Field is used to describe the length of the data being sent. The Data Field is used to send the actual payload to the other CAN nodes. The Cyclic Redundancy Check is used to detect any errors in the data. The Acknowledge Field is used to let the transmitter know that they successfully received the data. The End of Frame is used to indicate the end of the data.
+The CAN Bus data message frame is composed of a Starting Frame, an Arbitration Field, a Control Field, Data Field, Cyclic Redundancy Check, Acknowledge Field, and an End of Frame. The Starting Frame is used to indicate the start of a message when the bit is zero. The Arbitration Field is used to define the message priority. The Control Field is used to describe the length of the data being sent. The Data Field is used to send the actual payload to the other CAN nodes. The Cyclic Redundancy Check is used to detect any errors in the data. The Acknowledge Field is used to let the transmitter know that the data was successfully received. The End of Frame is used to indicate the end of the data.
-In the CAN system, there is no control host. When a CAN node is about to send data into the bus it first checks to see if the bus is busy. If the bus is not busy, the CAN node will send a message frame to the bus. The message frame does not contain a destination address so the message frame will be received by all nodes on the bus. Depending on the Arbitration Field, each CAN node will decide if they should ignore or accept the frame. When more than one CAN node tries to send a frame to the BUS at the same time, the node with the lower Arbitration ID will have the higher priority to the bus. The lower priority nodes will have to wait until the higher priority one is done.
+In the CAN system, there is no control host. When a CAN node is about to send data into the bus it first checks to see if the bus is busy. If the bus is not busy, the CAN node will send a message frame to the bus. The message frame does not contain a destination address so the message frame will be received by all nodes on the bus. Depending on the Arbitration Field, each CAN node will decide if they should ignore or accept the frame. When more than one CAN node tries to send a frame to the BUS at the same time, the node with the lower Arbitration ID will have the higher priority to the bus. The lower priority nodes will have to wait until the higher priority node is done.
 == Objectives & Introduction ==

@@ Line 323: / Line 323: @@
 message is written. Alternatives to this approach entail using the on-board memory.
-[[File:CMPE146_F16_G1_SDCard.jpg|center|thumb|50px|Figure 13. SD Card]]
+[[File:CMPE146_F16_G1_SDCard.jpg|center|thumb|Figure 13. SD Card]]
 == Testing & Technical Challenges ==

@@ Line 323: / Line 323: @@
 message is written. Alternatives to this approach entail using the on-board memory.
-[[File:CMPE146_F16_G1_SDCard.jpg|center|thumb|Figure 13. SD Card]]
+[[File:CMPE146_F16_G1_SDCard.jpg|center|thumb|50px|Figure 13. SD Card]]
 == Testing & Technical Challenges ==

@@ Line 310: / Line 310: @@
 The following diagram shows the functions utilized in the initialization sequence of the display driver. First, the I2C protocol is initialized in order to set up the communication between the SJ One board and the OLED display. Afterwards, the initial contents of the buffer are displayed to the screen. The buffer initially contains a bitmap image of the Adafruit Logo, this splash screen image is to be displayed upon boot up as requested by the manufacturer. The process of writing the buffer to the display consists of of sending each entry in the buffer to the display over the I2C bus. After some time delay, the display splash screen is cleared and the display becomes ready for interfacing.
-[[File:CmpE146_F16_G1_OLEDSWInit.png|center|thumb|Figure 11. OLED display software initialization sequence]]
+[[File:CmpE146_F16_G1_OLEDSWInit.png|center|720 px|thumb|Figure 11. OLED display software initialization sequence]]
 The following diagram shows the functions utilized in the writing sequence of the display driver. First, the display is prepared for the writing sequence through a series of register writes. The purpose of these register writes is to configure the rows and columns that are to be used by the display. Afterwards, the string is dissected and saved to the buffer. Finally, the buffer is written to the display one character at a time over the I2C bus.

← Older revision		Revision as of 01:55, 21 December 2016
Line 371:		Line 371:

	=== References Used ===		=== References Used ===
		+
		+	* [http://www.socialledge.com/sjsu/index.php?title=CAN_BUS_Tutorial CAN Bus Tutorial]

	=== Appendix ===		=== Appendix ===

@@ Line 312: / Line 312: @@
 [[File:CmpE146_F16_G1_OLEDSWInit.png|center|thumb|Figure 11. OLED display software initialization sequence]]
-The following diagram shows the functions utilized in the writing sequence of the display driver. First, the display is prepared for the writing sequence through a series of register writes. The purpose of these register writes is to configure the rows and columns that are to be used by the display. Afterwards, the string is dissected and saved to the buffer. Finally, the buffer is written to the display one character at a time.
+The following diagram shows the functions utilized in the writing sequence of the display driver. First, the display is prepared for the writing sequence through a series of register writes. The purpose of these register writes is to configure the rows and columns that are to be used by the display. Afterwards, the string is dissected and saved to the buffer. Finally, the buffer is written to the display one character at a time over the I2C bus.
 [[File:CmpE146_F16_G1_OLEDSWDisplay.png|center|thumb|Figure 12. OLED display writing sequence]]

← Older revision		Revision as of 01:44, 21 December 2016
Line 367:		Line 367:

	=== References Used ===		=== References Used ===
−	~~List any references used in project.~~

	=== Appendix ===		=== Appendix ===

@@ Line 370: / Line 370: @@
 === Appendix ===
 * [http://www.ti.com/lit/ds/symlink/sn65hvda1040a-q1.pdf SN65HVDA1040 CAN Transceiver Datasheet]
 * [https://cdn-shop.adafruit.com/datasheets/SSD1306.pdf OLED Display Datasheet]