Difference between revisions of "F16: Autonomous Fire Extinguishing Vehicle"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Abstract)
(Schedule)
Line 84: Line 84:
 
| 12/2/2016
 
| 12/2/2016
 
| Assemble vehicle
 
| Assemble vehicle
| In Progress
+
| Completed
|
+
| 12/9/2016
 
|-
 
|-
 
! scope="row"| 7
 
! scope="row"| 7
Line 91: Line 91:
 
| 12/9/2016
 
| 12/9/2016
 
| Test/troubleshoot system setup
 
| Test/troubleshoot system setup
| Not Completed
+
| Completed
|
+
| 12/11/2016
 
|-
 
|-
 
! scope="row"| 8
 
! scope="row"| 8
Line 98: Line 98:
 
| 12/16/2016
 
| 12/16/2016
 
| Fine-tune/Finalize of project
 
| Fine-tune/Finalize of project
| Not Completed
+
| In Progress
 
|
 
|
 
|-
 
|-
Line 105: Line 105:
 
| 12/20/2016
 
| 12/20/2016
 
| Prepare for demo/presentation
 
| Prepare for demo/presentation
| Not Completed
+
| In Progress
 
|
 
|
 
|}
 
|}

Revision as of 06:43, 20 December 2016

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.

Project Title

Abstract

The Autonomous FEV is able to scan a room for fires through a focused IR sensor and navigate to each fire's location. Once the vehicle reaches a reasonable distance from the fire's location, the vehicle will spray water in the fire's general location and extinguish it.

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

  • Kevin Gadek
    • Project Documentation
  • John Purkis
    • Project Documentation
  • RuiQiang Yu
    • Project Documentation

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# Start Date End Data Task Status Actual Completion Date
1 10/21/2016 10/28/2016 Finalize Project Proposal Completed 10/28/2016
2 10/28/2016 11/04/2016 Compile Bill of Materials/Design Schematics Completed 11/04/2016
3 11/04/2016 11/11/2016 Order necessary parts Completed 11/15/2016
4 11/11/2016 11/18/2016 Disassemble prebuilt RC car/Develop initial IR sensor task Completed 11/21/16
5 11/18/2016 11/25/2016 Develop preliminary servo motor control task Completed 11/21/16
6 11/25/2016 12/2/2016 Assemble vehicle Completed 12/9/2016
7 12/2/2016 12/9/2016 Test/troubleshoot system setup Completed 12/11/2016
8 12/9/2016 12/16/2016 Fine-tune/Finalize of project In Progress
9 12/16/2016 12/20/2016 Prepare for demo/presentation In Progress

Parts List & Cost

Part Name Quantity Cost Notes
SJOne Board 1 $80 Main microcontroller
Infrared Sensor Module 6 $13.67 Placed around front of car to detect flame location
Hitec HS-425BB Servo Motor 2 $26.00 To rotate spray apparatus vertically and horizontally
RC car 1 $39.99 Main vehicle
Water pump 1 $25.77 Aubig 12V Brushless DC water pump
Battery supply 2 $8.00 12V 8xAA battery pack w/ switch

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.

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

Show your software design. For example, if you are designing an MP3 Player, show the tasks that you are using, and what they are doing at a high level. Do not show the details of the code. For example, do not show exact code, but you may show psuedocode and fragments of code. Keep in mind that you are showing DESIGN of your software, not the inner workings of it.

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

Calibration of IR sensor to focus on detecting a flame rather than ambient light.

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

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.