S19: Zeus - Revision history

Proj user6: /* Team Members & Responsibilities */

2019-10-12T22:12:35Z

‎Team Members & Responsibilities

Proj user12: /* Team Members & Responsibilities */

2019-06-12T21:52:02Z

‎Team Members & Responsibilities

Proj user12: /* Team Members & Responsibilities */

2019-05-30T19:18:29Z

‎Team Members & Responsibilities

Proj user12: /* Team Members & Responsibilities */

2019-05-30T19:09:39Z

‎Team Members & Responsibilities

Proj user12: /* Team Members & Responsibilities */

2019-05-29T17:17:52Z

‎Team Members & Responsibilities

Proj user12: /* Team Members & Responsibilities */

2019-05-24T17:56:15Z

‎Team Members & Responsibilities

Proj user12: /* CAN BUS Design */

2019-05-24T04:13:27Z

‎CAN BUS Design

Proj user12: /* Objectives & Introduction */

2019-05-24T04:09:45Z

‎Objectives & Introduction

Proj user12: /* Team Members & Responsibilities */

2019-05-23T22:46:32Z

‎Team Members & Responsibilities

Proj user12: /* Team Members & Responsibilities */

2019-05-23T22:45:56Z

‎Team Members & Responsibilities

@@ Line 36: / Line 36: @@
 ** ''Motor Module''
 ** ''PCB Design''
-* '''Namdev Prabhugaonkar'''
+* '''[https://www.linkedin.com/in/namdev-prabhugaonkar/ Namdev Prabhugaonkar] <br>
 ** ''GEO module''
 ** ''PCB Design''

@@ Line 23: / Line 23: @@
 * '''[https://www.linkedin.com/in/himanshu-gunjal/ Himanshu Gunjal]<br>'''
 ** ''Master Module''
-** ''Testing''
+** ''BLE Module''
 * '''Aman Chandan'''
 ** ''Material/ Components Manager''

@@ Line 23: / Line 23: @@
 * '''[https://www.linkedin.com/in/himanshu-gunjal/ Himanshu Gunjal]<br>'''
 ** ''Master Module''
-** ''Testing Lead''
+** ''Testing''
 * '''Aman Chandan'''
 ** ''Material/ Components Manager''

@@ Line 17: / Line 17: @@
 [[File:Zeus Team Photo.JPG|thumb|650px|right|Zeus Team Members]]
 * '''[https://www.linkedin.com/in/neel-patel-806309126/ Neel Patel]<br> '''
-** ''Team Lead''
+** '''''Team Lead'''''
 ** ''Master Module''
 ** ''Android App''

@@ Line 16: / Line 16: @@
 == Team Members & Responsibilities ==
 [[File:Zeus Team Photo.JPG|thumb|650px|right|Zeus Team Members]]
 * '''[https://www.linkedin.com/in/neel-patel-806309126/ Neel Patel]<br> '''
 ** ''Master Module''
 ** ''Android App''
 ** ''BLE Module''
 * '''Aman Chandan'''
 ** ''Material/ Components Manager''

@@ Line 411: / Line 411: @@
 == CAN BUS Design ==
-CAN Communication is used to communicate between all the boards and it requires the bus to be terminated using two 120 Ohm resistors. CAN is a very deterministic broadcast bus. Based on the .dbc file, each module will transmit only selected messages. Receiving of the messages is enabled by filtering. The module can be configured to receive all messages or receive selected messages. GIven below are features of CAN bus:
+CAN Communication is used to communicate between all the boards and it requires the bus to be terminated using two 120 Ohm resistors. CAN is a very deterministic broadcast bus. Based on the .dbc file, each module will transmit only selected messages. Receiving of the messages is enabled by filtering. The module can be configured to receive all messages or receive selected messages. Given below are features of CAN bus:
-* Stadard baud rate of 100K, 125K, 250K, 500k or 1M
+* Standard baud rate of 100K, 125K, 250K, 500k or 1M
 * Differential Pair - Half duplex
@@ Line 422: / Line 422: @@
 * Message ID (11 bit or 29 bit)
-For CAN we require a transciever(unlike) other BUSes. This transciever converts the Rx and Tx lines to a single differential pair. where Logic 1( recessive) is represented by a ZERO volt difference and Logic 0(dominant) is represented by 2V difference.
+For CAN we require a transceiver(unlike) other BUSes. This transceiver converts the Rx and Tx lines to a single differential pair. where Logic 1( recessive) is represented by a ZERO volt difference and Logic 0(dominant) is represented by 2V difference.
-'''Arbitration''' happens in can bus to make sure no two nodes are transmitting at the same time. A lower Message ID has Higher priority on the CAN bus, since 0 is the dominant bit.
+'''Arbitration''' happens in can bus to make sure no two nodes are transmitting at the same time. A lower Message-ID has a Higher priority on the CAN bus since 0 is the dominant bit.
 To make sure that a node does not put a lot of consecutive 1s or 0s together '''Bit Stuffing''' is done, where the CAN HW ''stuffs'' extra bits to improve CAN BUS integrity. Our project's overall design is described below.
@@ Line 439: / Line 439: @@
 [[File:CMPE 243 Zeus-can-board.jpg|200px|thumb|right|CAN Transceiver]]
-We connected a play and plug Waveshare CAN Tranceivers Board for CAN Communication with our SjOne Boards. This Board works on 3.3V and connects to the CAN Rx and CAN Tx Pins of the SjOne Board. This Board then converts the signal to CAN High and CAN Low signal. This board itself has terminating resistors, thus when we connect 5 of them in one bus we bypass the terminating resistors present on the board itself and just use 120 ohms of terminating resistor at each end. This board has TI Chip installed on it and works flawlessly when interfaced with SjOne boards.
+We connected a play and plug Waveshare CAN Transceivers Board for CAN Communication with our SjOne Boards. This Board works on 3.3V and connects to the CAN Rx and CAN Tx Pins of the SjOne Board. This Board then converts the signal to CAN High and CAN Low signal. This board itself has terminating resistors, thus when we connect 5 of them in one bus we bypass the terminating resistors present on the board itself and just use 120 ohms of terminating resistor at each end. This board has TI Chip installed on it and works flawlessly when interfaced with SjOne boards.
 {| class="wikitable"
@@ Line 509: / Line 509: @@
 |4
 |121
-|Obstacle Data for the front, left and right sensor
+|Obstacle Data for the front left and right sensor
 |Master
 |-

@@ Line 8: / Line 8: @@
 == Objectives & Introduction ==
-Zeus revolves around 5 SJone boards that have LPC 1758 at the center and has many peripherals ranging from motor, GPS and Bluetooth modules connected to them. Each SjOne board has the responsibility to control a specific peripheral. These 5 SJOne boards form the 5 modules of this project viz. Master module, Motor module, BLE module, GPS module, and the sensor module. These individual modules combine together to achieve the objective of this project. Following are the objectives of this project.:
+Zeus revolves around 5 SJone boards that have LPC 1758 at the center and has many peripherals ranging from motor, GPS and Bluetooth modules connected to them. Each SJOne board has the responsibility to control a specific peripheral. These 5 SJOne boards form the 5 modules of this project viz. Master module, Motor module, BLE module, GPS module, and the sensor module. These individual modules combine together to achieve the objective of this project. Following are the objectives of this project.:
 * Zeus should successfully navigate from a fixed starting point to a fixed destination based on GPS.
 * Obstacles on the way should be avoided.