Difference between revisions of "F13: Quadcopter"
Proj user6 (talk | contribs) (→Objectives & Introduction) |
Proj user6 (talk | contribs) (→Schedule) |
||
| Line 27: | Line 27: | ||
== Schedule == | == Schedule == | ||
| − | |||
| Line 81: | Line 80: | ||
|align="left"|Code PWM input | |align="left"|Code PWM input | ||
|align="center"|29-Oct | |align="center"|29-Oct | ||
| − | || | + | |align="center"|15-Nov |
| − | || | + | |align="center"|Complete |
| | | | ||
|- | |- | ||
| Line 91: | Line 90: | ||
|align="left"|Code PID | |align="left"|Code PID | ||
|align="center"|5-Nov | |align="center"|5-Nov | ||
| − | ||||| | + | |align="center"|17-Nov |
| + | |align="center"|Complete | ||
| + | | | ||
|- | |- | ||
|align="left"|Code PWM Encode Driver | |align="left"|Code PWM Encode Driver | ||
| Line 99: | Line 100: | ||
|align="left"|Integrate Processor with Aircraft | |align="left"|Integrate Processor with Aircraft | ||
|align="center"|12-Nov | |align="center"|12-Nov | ||
| − | ||||| | + | |align="center"|1-Nov |
| + | |align="center"|Complete | ||
| + | | | ||
|- | |- | ||
|align="left"|Tether Testing 1D stabilization (pitch) | |align="left"|Tether Testing 1D stabilization (pitch) | ||
Revision as of 05:11, 19 November 2013
Contents
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.
Quadcopter
Abstract
This section should be a couple lines to describe what your project does.
Objectives & Introduction
The objective of this project is to build a remote controlled quadcopter that is capable stable flight. We will control the quadcopter via a Spektrum DX5E hobbyist controller. We will be creating an Inertial Measurement Unit(IMU) using a 3 axis accelerometer and a 3 axis gyroscope. The IMU will communicate with the SJ One Board via I2C. We will be implementing a complementary filter in software to estimate the quadcopter attitude, and will then have a PID control loop in software to generate outputs to the motors.
Team Members & Responsibilities
- Craig Farless
- Airframe Design
- Sensor Design
- Remote Control Interface Design
- Flight Controller Software Design
Schedule
| Task | Projected Completion Date | Actual Completion Date | Status | Notes |
| Buy Parts | 1-Oct | 1-Oct | Complete | |
| Build frame | 8-Oct | 8-Oct | Complete | |
| Install Sensors | 15-Oct | 8-Oct | Complete | |
| Code I2C i/f to sensors | 15-Oct | 15-Oct | Complete | |
| Code Filters | 22-Oct | 15-Oct | Complete | |
| Code accel/gyro conversion to angle | 22-Oct | 22-Oct | Complete | |
| Integrate Power System | 22-Oct | 22-Oct | Complete | |
| Code PWM input | 29-Oct | 15-Nov | Complete | |
| Code cmd translator | 29-Oct | |||
| Code PID | 5-Nov | 17-Nov | Complete | |
| Code PWM Encode Driver | 12-Nov | |||
| Integrate Processor with Aircraft | 12-Nov | 1-Nov | Complete | |
| Tether Testing 1D stabilization (pitch) | 12-Nov | |||
| Tether Testing 2D stabilization (pitch, roll) | 19-Nov | |||
| Tether Testing 3D stabilization (pitch, roll, yaw) | 26-Nov | |||
| Full Flight Testing | 26-Nov | |||
| Demo | 3-Dec | |||
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
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:
Wifi Connection Issues
Many wifi connection issues were encountered. To solve this problem, a dedicated task was created to re-connect to wifi if the connection was ever lost.
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.
