Difference between revisions of "S14: Tricopter"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Objectives & Introduction)
(Parts List & Cost)
Line 45: Line 45:
 
== Parts List & Cost ==
 
== Parts List & Cost ==
 
Give a simple list of the cost of your project broken down by components.  Do not write long stories here.
 
Give a simple list of the cost of your project broken down by components.  Do not write long stories here.
 +
 +
 +
{| class="wikitable"
 +
|-
 +
! scope="col"| Name
 +
! scope="col"| Quantity
 +
! scope="col"| Price
 +
!
 +
|-
 +
! scope="row1"| Turnigy Park480
 +
|  3
 +
| $61.47
 +
|-
 +
! scope="row2" | Hobby King 30A ESC 
 +
|  3
 +
| $30.45
 +
|-
 +
! scope="row3" | Corona 919MG Servo
 +
|  1
 +
| $7.01
 +
|-
 +
! scope="row4" | Sunkee 10DOF
 +
|  1
 +
| $20.00
 +
|-
 +
! scope="row5" | Hobbyking X900
 +
|  1
 +
| $32.16
 +
|-
 +
! scope="row6" | Prop 9047
 +
|  3
 +
| $9.48
 +
|-
 +
! scope="row7" | Truningy 5000mah
 +
|  1
 +
| $27.85
 +
|-
 +
! scope="row8" | Cables / Connectors
 +
|  N/A
 +
| $20.00
 +
|-
 +
! scope="row9" | SJSU One Board
 +
|  1
 +
| $80.00
 +
|-
 +
! scope="row10" | Total
 +
|
 +
| $292.00
 +
|- 
 +
|}
  
 
== Design & Implementation ==
 
== Design & Implementation ==

Revision as of 18:28, 25 April 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.

Code name Cerberus

Abstract

The goal of this project is to produce a stable hovering tricopter. This craft will hover using three motors with three propellers, one of which is mounted on a swivelling piece that allows the raft to have more yaw control. The plan for this project is to use COTS parts for all but the flight controller which will be our software on an SJOne board. The flight controller is responsible for determining how fast each motor spins and the angle of the swivelling motor using inputted data from an accelerometer, a gyroscope, and possibly a magnetometer. The tricopter will elevate itself to a fixed height and using a barometer will stay stabilized at this height.

Objectives & Introduction

The objective of this project is to produce a Tricopter capable of rising to a given altitude, hovering in one position for at least 15 seconds, and then landing safely in the same position it took off from.

Maintaining stable flight is the key requirement for this project. Orientation is calculated using an accelerometer and gyroscope. The height above ground is determined using the output of an ultrasonic sensor.

Team Members & Responsibilities

  • Carlos Fernandez-Martinez
  • Shane Loretz
  • Michael Schneider

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 Actual
1 10/8 Task list Completed? Problems Encountered?

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.


Name Quantity Price
Turnigy Park480 3 $61.47
Hobby King 30A ESC 3 $30.45
Corona 919MG Servo 1 $7.01
Sunkee 10DOF 1 $20.00
Hobbyking X900 1 $32.16
Prop 9047 3 $9.48
Truningy 5000mah 1 $27.85
Cables / Connectors N/A $20.00
SJSU One Board 1 $80.00
Total $292.00

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

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.