Difference between revisions of "S14: Anti-Crash Car"

From Embedded Systems Learning Academy
Jump to: navigation, search
(My Issue #1)
(My Issue #2)
Line 187: Line 187:
 
=== My Issue #2 ===
 
=== My Issue #2 ===
 
Interrupt : When we had 2 interrupts and functional calls involve together, our code will not perform the way we expected. The system get crash or freeze time to time.
 
Interrupt : When we had 2 interrupts and functional calls involve together, our code will not perform the way we expected. The system get crash or freeze time to time.
 +
 
Solution : We end up putting sensor, gps, motor and state machine code in tasks.
 
Solution : We end up putting sensor, gps, motor and state machine code in tasks.
  

Revision as of 08:49, 17 May 2014

Grading Criteria

  • 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.

Anti-Crash Car

Abstract

The project involves a GPS controlled car that drives to a user determined destination and automatically stops or slows down when an obstacle is in its way in order to prevent itself from crashing. Any command that can potentially damage the car is disabled (e.g. moving forward when the obstacle is in front).

Objectives & Introduction

Show list of your objectives. This section includes the high level details of your project. You can write about the various sensors or peripherals you used to get your project completed.

Team Members & Responsibilities

  • Geff Lozano
    • GPS Module
      • Parser
      • Information Processing
    • System State Machine
  • Koko Maung
    • Car Kit Assembly
    • Infrared Sensor Module
    • Sonar Sensor Module
    • Compass Module
    • Servo / Wheels Motor
    • State Machine
  • Matthew Pham
    • GPS Module
      • UART Interface
      • Parser
      • Information Processing
    • System State Machine

Schedule

Show a simple table or figures that show your scheduled as planned before you started working on the project. Then in another table column, write down the actual schedule so that readers can see the planned vs. actual goals. The point of the schedule is for readers to assess how to pace themselves if they are doing a similar project.

Week# Date Task Description
1 3/23 Planning Top-Level System Drafting
2 3/30 Top-Level System Design Went through many drafts
3 4/6 Order Parts
4 4/13 Assign peripheral responsibilities
5/6 4/20 Peripheral Interfacing GPS, Infrared, Sonar; No communication with GPS; Burned GPS;
7 4/27 System State Machine Implementation Redrafted Original State Machine
8 5/4 Testing
8 5/11 Testing
8 5/18 Testing
8 5/22 Testing

Parts List & Cost

Qty Part Price
1 RC Rock Crawler $200.86
1 SRF08 Ultrasonic Range Finder $54.30
4 Sensor Housing MPSH-01 $4.95
3 GP2Y0A21YK0F IR Sensor - 10cm to 80cm $9.95
3 SIRC-01 Sensor Cable $1.95
1 3DR GPS Module w/ Compass $89.99
1 Battery $25.00
2 Shipping $10.22
1 GPS Receiver - LS20031 5Hz (66 Channel) $59.95
1 Compass Module 3-Axis HMC5883L $15.99
Total $432.04

Design & Implementation

The design section can go over your hardware and software design. Organize this section using sub-sections that go over your design and implementation.

Hardware Design

Discuss your hardware design here. Show detailed schematics, and the interface here. File:Anti crash Schematic.png

Hardware Interface

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.

Software Design

Design Flow

Cmpe146 S14 ACCAR SwDesignFlow.png | File:Anti crash State diagram.png ]

Implementation

This section includes implementation, but again, not the details, just the high level. For example, you can list the steps it takes to communicate over a sensor, or the steps needed to write a page of memory onto SPI Flash. You can include sub-sections for each of your component implementation.

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can be started from scratch again? Make a smooth transition to testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

My Issue #1

PWMs : I found out PWMs for servo and wheels motor must run at 50Hz even though motor is capable of handling faster frequency. When we use other frequency, the hand shake between PWMs and motor will not sync correctly.

Solution : We end up using 50Hz and we had to operate motor at slower speed.

My Issue #2

Interrupt : When we had 2 interrupts and functional calls involve together, our code will not perform the way we expected. The system get crash or freeze time to time.

Solution : We end up putting sensor, gps, motor and state machine code in tasks.

My Issue #1

Discuss the issue and resolution.

My Issue #1

Discuss the issue and resolution.

My Issue #1

Discuss the issue and resolution.

Conclusion

Conclude your project here. You can recap your testing and problems. You should address the "so what" part here to indicate what you ultimately learnt from this project. How has this project increased your knowledge?

Project Video

Upload a video of your project and post the link here.

Project Source Code

Send me your zipped source code and I will upload this to SourceForge and link it for you.

References

Acknowledgement

Any acknowledgement that you may wish to provide can be included here.

References Used

List any references used in project.

Appendix

You can list the references you used.