S14: Anti-Crash Car - Revision history

Preet: /* Project Source Code */

2014-08-07T00:02:17Z

‎Project Source Code

Preet: /* Grading Criteria */

2014-08-07T00:02:06Z

‎Grading Criteria

Proj user22: /* Conclusion */

2014-05-24T07:48:56Z

‎Conclusion

Proj user22: /* Conclusion */

2014-05-24T07:46:19Z

‎Conclusion

Proj user22: /* References */

2014-05-24T07:43:51Z

‎References

Proj user22: /* Testing & Technical Challenges */

2014-05-24T07:42:30Z

‎Testing & Technical Challenges

Proj user22: /* Compass Issues */

2014-05-24T07:30:09Z

‎Compass Issues

Proj user22: /* Compass Issues */

2014-05-24T07:29:53Z

‎Compass Issues

Proj user22: /* Compass Issues */

2014-05-24T07:29:38Z

‎Compass Issues

Proj user22: /* Software Design */

2014-05-23T23:25:25Z

‎Software Design

@@ Line 406: / Line 406: @@
 === 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/CmpE244_SJSU_S2014/ Sourceforge source code link]
 == References ==

← Older revision		Revision as of 00:02, 7 August 2014
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>~~
−
	= Anti-Crash Car =		= Anti-Crash Car =
	[[File:Cmpe146 S14 ACCAR Car.jpg\|center\|frame]]		[[File:Cmpe146 S14 ACCAR Car.jpg\|center\|frame]]

@@ Line 406: / Line 406: @@
 == Conclusion ==
 Much of the car's functionalities were implemented correctly.
-From the project, the team gained firsthand experience after utilizing concepts and protocols such as state machines, ADC, UART, and I2C. Also, the team learned how to test individual modules and the system itself. Sensors were tested manually to make sure that they functional and were outputting correct values. System states had to be tested with great attention to detail to make sure the system transitioned to the correct state. The team learned the benefits of implementing functions as tasks to allow the system to execute multiple tasks concurrently. Also, the team learned how to work together and work efficiently by dividing up tasks and working side by side to design, implement, and test the project.
+From the project, the team gained firsthand experience after utilizing concepts and protocols such as state machines, ADC, UART, and I2C. Also, the team learned how to test individual modules and the system itself. Sensors were tested manually to make sure that they functional and were outputting correct values. System states had to be tested with great attention to detail to make sure the system transitioned to the correct state. The team learned the benefits of implementing functions as tasks to allow the system to execute multiple tasks concurrently. Also, the team learned how to work together and work efficiently by dividing up tasks and working side by side to design, implement, and test the project. As a result, we were able to deliver the anti-crash car that is nearly complete.
 <gallery widths=300px heights=300px>

@@ Line 406: / Line 406: @@
 == Conclusion ==
 Much of the car's functionalities were implemented correctly.
 From the project, the team gained firsthand experience after utilizing concepts and protocols such as state machines, ADC, UART, and I2C. Also, the team learned how to test individual modules and the system itself. Sensors were tested manually to make sure that they functional and were outputting correct values. System states had to be tested with great attention to detail to make sure the system transitioned to the correct state. The team learned the benefits of implementing functions as tasks to allow the system to execute multiple tasks concurrently. Also, the team learned how to work together and work efficiently by dividing up tasks and working side by side to design, implement, and test the project.
 <gallery widths=300px heights=300px>

@@ Line 425: / Line 425: @@
 == References ==
 === Acknowledgements ===
-We would like to thank Dr. Ozemek for giving us detailed knowledge of how circuits and components works.
+We would like to thanks Dr. Ozemek for giving us detailed knowledge of how circuits and components works.
-We would like to thank Preetpal Kang for teaching us how to use microcontrollers and FreeRTOS.
+We would like to thanks Preetpal Kang for teaching us how to use microcontrollers and FreeRTOS.
-We would like to thank James Loo for guiding me [Koko] throughout this whole project, making sure our project was being put together correctly.
+We would like to thanks James Loo for guiding me [Koko] throughout this whole project, making sure our project was being put together correctly.
 === References Used ===

@@ Line 374: / Line 374: @@
 * Due to having to reorder three different compasses, time had taken its toll. The compass still not able to output correct result.
 *According to Professor Preet, the inconsistency might have to do with our hardware design. Our compass is too close to motor which is producing magnetic field. We will update the result once we found the solution and the cause.
 ==== GPS Issues ====

@@ Line 373: / Line 373: @@
 ** During Field Testing, it was found that the compass DOES guide the car to its destination. It was trying to adjust the car left and right. However, since the compass value is inconsistent, that car was not able to reach destination.
 * Due to having to reorder three different compasses, time had taken its toll. The compass still not able to output correct result.
-**According to Preet, the inconsistency might have to do with our hardware design. Our compass is too close to motor which is producing magnetic field. We will update the result once we found the solution and the cause.
+*According to Preet, the inconsistency might have to do with our hardware design. Our compass is too close to motor which is producing magnetic field. We will update the result once we found the solution and the cause.
 ==== GPS Issues ====

@@ Line 369: / Line 369: @@
 <b>Solution:</b>
-* A third compass was bought. However, it had trouble returning values pointing in the NORTH-EAST direction (270° to 359°).
+* A third compass (CMPS10) was bought. However, it had trouble returning values pointing in the NORTH-EAST direction (270° to 359°).
 ** All expected values located in that range returned inconsistently incorrect values instead.
-** During Field Testing, it was found that the compass DOES guide the car to its destination. However, when the car needs to go NORTH-EAST, the car has to recalibrate more often than when it is required to go in another direction.
+** During Field Testing, it was found that the compass DOES guide the car to its destination. It was trying to adjust the car left and right. However, since the compass value is inconsistent, that car was not able to reach destination.
-* Due to having to reorder three different compasses, time had taken its toll. The compass still has trouble reading values in the NORTH-EAST range.
+* Due to having to reorder three different compasses, time had taken its toll. The compass still not able to output correct result.
 ==== GPS Issues ====

@@ Line 177: / Line 177: @@
 '''Sonar Task'''
 The task for sonar is responsible for detecting objects from a user specified distance and updating a global "sonar" variable used by the other tasks. Detections closer to the sonar return greater values while detections farther away return lesser values.
 '''Left and Right IR Tasks'''
 The left and right infrared sensor tasks act the same way as the sonar's task. These tasks are also used for object detection. It updates global "left IR" and "right IR" variables to be used by other tasks.
 '''GPS Task'''
 The GPS task updates a struct named "coordinates" with GPS coordinates. This struct contains two double types (one for longitude and one for latitude).
 '''Compass Task'''
 The compass task also updates a global variable which indicates the angle at which the compass is directed (e.g. 0°-359°).
 '''State Machine Task'''
 This task includes the system state machine as shown in the [http://www.socialledge.com/sjsu/index.php?title=S14:_Anti-Crash_Car#Design_Flow Design Flow Diagram]