F14: Self Driving Undergrad Team - Revision history

Proj user8: /* Grading Criteria */

2015-03-05T19:43:28Z

‎Grading Criteria

Proj user2: /* Team Members & Responsibilities */

2014-12-23T05:23:10Z

‎Team Members & Responsibilities

Proj user8: /* Project Source Code */

2014-12-22T22:39:42Z

‎Project Source Code

Proj user8: /* Project Video */

2014-12-22T22:38:32Z

‎Project Video

Proj user8: /* Communication Bridge + Android Issue #2 */

2014-12-22T17:59:56Z

‎Communication Bridge + Android Issue #2

Proj user8: /* Geographical Controller Testing - Compass */

2014-12-22T16:23:06Z

‎Geographical Controller Testing - Compass

Proj user8: /* Technical Challenges */

2014-12-22T16:05:33Z

‎Technical Challenges

Proj user8: /* Master Controller Team Issues */

2014-12-22T15:59:24Z

‎Master Controller Team Issues

Proj user8: /* Master Controller Issue #4 */

2014-12-22T15:05:26Z

‎Master Controller Issue #4

Proj user8: /* Master Controller Issue #5 */

2014-12-22T15:05:16Z

‎Master Controller Issue #5

← Older revision		Revision as of 19:43, 5 March 2015
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>~~
	== Chi Lam ==		== Chi Lam ==
	<center>		<center>

@@ Line 55: / Line 55: @@
 | - Overall vehicle logic<br/>- Overall software vehicle Integration<br/>- CAN TX/RX messages architecture
 | - Vehicle hardware interfacing<br/>- Assistant to other teams<br/>- Module specific logic
-| - Module specific logic<br/>- CAN RX processing
+| - Module specific logic<br/>- CAN RX processing<br/>- GPS waypoint logic
 |-
 |}

@@ Line 2,623: / Line 2,623: @@
 === Project Source Code ===
-*  [https://sourceforge.net/projects/sjsu/files/CmpE_SJSU_F2014/ Sourceforge Source Code Link]
+*  [https://gitlab.com/cpham/undergrad243/ GitLab Source Code Link]
 == References ==

@@ Line 2,620: / Line 2,620: @@
 === Project Video ===
-Link provided upon request.
+http://youtu.be/fvZmUlMSQwU
 === Project Source Code ===

@@ Line 2,520: / Line 2,520: @@
 '''PROBLEM:'''When testing to see if the terminal task received the expected messages, the values would not print to the terminal.
-'''RESOLUTION:''' It was assumed that the terminal task was operating properly and receiving commands from Bluetooth but printing the information back over UART. The terminal command code was rewritten to log information received instead of print it. It was confirmed that messages were being received and parsed properly by the terminal task.
+'''RESOLUTION:''' It was assumed that the terminal task was operating properly and receiving commands from Bluetooth but printing the information back over UART. The terminal command code was rewritten to log information received instead of printing it. It was confirmed that messages were being received and parsed properly by the terminal task.
 '''FUTURE RECOMMENDATIONS:''' Make extensive use of the built in logging function.

← Older revision		Revision as of 16:23, 22 December 2014
Line 2,421:		Line 2,421:
	----		----

−	~~----~~
	=== Master Controller ===		=== Master Controller ===

@@ Line 2,447: / Line 2,447: @@
 '''FUTURE RECOMMENDATIONS:''' Before any software debugging, the hardware connections must be the first area to check because it is the easiest and fastest.
+----
 === Motor Controller Team Issues ===
@@ Line 2,473: / Line 2,473: @@
 '''FUTURE RECOMMENDATIONS:''' Prioritize mounting a hall sensor with magnetic strips as soon as motor module is able to control car movement.
 === I/O Team Issues ===
@@ Line 2,503: / Line 2,504: @@
 Find areas for optimizations to better improve performance. If analyzed closer, there could be other areas which could improve performance, but the screen seemed sufficiently responsive now.
 === Communication Bridge + Android Team Issues ===
@@ Line 2,529: / Line 2,532: @@
 '''FUTURE RECOMMENDATIONS:''' Implement a watchdog function that will reboot the board upon termination of Bluetooth connections.
 === Geographical Controller Issues ===
@@ Line 2,553: / Line 2,557: @@
 '''FUTURE RECOMMENDATIONS:'''
 Create code to calibrate all modules to make sure the data produced are the same data that you're looking for before piecing the components together.
 === Master Controller Team Issues ===

@@ Line 2,568: / Line 2,568: @@
 '''FUTURE RECOMMENDATIONS:'''
-Make the sensor team filter their data.
+Assure the data being sent by sensors is filtered. If the issue cannot be resolved, work together with the Sensor Team to debug and solve the issue.
 ==== Master Controller Issue #2 ====
 '''BACKGROUND'''
-Geo were supposed to transmit valid heading over CAN at a 10hz periodic rate.
+The heading being sent by Geo over CAN should be at a 10hz periodic rate.
 '''PROBLEM:'''
@@ Line 2,579: / Line 2,579: @@
 '''RESOLUTION:'''
-Ask geo team to calibrate their heading data, that didnt work so go in and refactor their code.
+Ask geo team to calibrate their heading data/ refactor calibration code.
 '''FUTURE RECOMMENDATIONS:'''
-Make geo team to calibrate their heading data.
+Assure that the heading data being sent by the Geo team is calibrated. If the issue cannot be resolved, work together with the Geo Team to debug and solve the issue.
 ==== Master Controller Issue #3 ====
 '''BACKGROUND'''
-Geo were supposed to transmit valid gps latitude and longitude over CAN at a 10hz periodic rate.
+Valid GPS latitude and longitude information transmitted over CAN should be at a 10hz periodic rate.
 '''PROBLEM:'''
@@ Line 2,596: / Line 2,596: @@
 '''FUTURE RECOMMENDATIONS:'''
-Make geo team to fix their priority and timing issues with updating GPS latitude and longitude.
+Assure that the GPS latitude and longitude priority and timing issues are fixed. If the issue cannot be resolved, work together with the Geo Team to debug and solve the issue.
 ==== Master Controller Issue #4 ====
@@ Line 2,610: / Line 2,610: @@
 '''FUTURE RECOMMENDATIONS:'''
-Don't make mistakes.
+When debugging, review the overall algorithms to assure the design is valid.
 == Conclusion ==

@@ Line 2,612: / Line 2,612: @@
 Make geo team ensure no CAN messages are dropped or missed.
-==== Master Controller Issue #5 ====
+==== Master Controller Issue #4 ====
 '''BACKGROUND'''