Difference between revisions of "S15: Drone"
Proj user20 (talk | contribs) (→Schedule) |
Proj user20 (talk | contribs) (→Schedule) |
||
| Line 57: | Line 57: | ||
|- | |- | ||
! scope="row"| 3 | ! scope="row"| 3 | ||
| − | | 04/ | + | | 04/01/2015 |
| − | | 04/ | + | | 04/07/2015 |
| Interfaced Motors and RC to SJOne Board. | | Interfaced Motors and RC to SJOne Board. | ||
| Completed | | Completed | ||
Revision as of 02:01, 15 April 2015
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.
Project Title
Abstract
This section should be a couple lines to describe what your project does.
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
- Bhushan Gopala Reddy
- Karthik Govindaswamy
- Rishikesh Nagare
- Mayur Salve
- Manuj Shinkar
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.
| Sl.No | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 03/17/2015 | 03/24/2015 | Ordered parts for quad-copter | Completed | 09/24/2015 |
| 2 | 03/25/2015 | 03/31/2015 | Assembled quad-copter and Tested it using pre-programmed board (KK 2.1.5). | Completed | 03/31/2015 |
| 3 | 04/01/2015 | 04/07/2015 | Interfaced Motors and RC to SJOne Board. | Completed | 04/07/2015 |
| 4 | 04/07/2015 | 04/14/2015 | Study quad-copters software framework provided by Preet | Ongoing | --/--/2015 |
| 5 | 04/14/2015 | 04/21/2015 | Interface and test 10-DOF IMU sensor by Adafruit. | Ongoing | --/--/2015 |
| 6 | 04/21/2015 | 05/05/2015 | Understanding and Tuning PID values. | --/--/2015 | |
| 7 | 05/05/2015 | 05/19/2015 | Final Testing. | --/--/2015 |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Item# | Part Desciption | Vendor | Part Number | Qty | Cost |
|---|---|---|---|---|---|
| 1 | Motors and Propellers | tiger motors | 2 | $89.99 | |
| 2 | Afro ESC 30 Amp Speed Controller (SimonK Firmware) | Turnigy | 6 | $84 | |
| 3 | Turnigy 9X 9Ch Transmitter w/ Module & 8ch Receiver (Mode 2) (v2 Firmware) | Turnigy | 1 | $59.99 | |
| 4 | Turnigy nano-tech 4000mAh 3S1P 25-50C Lipo Pack | Turnigy | 1 | $26.90 | |
| 5 | Hobbyking SK450 Glass Fiber Quadcopter Frame 450mm | Hobbyking | 1 | $17.99 | |
| 6 | Landing Kit set | Hobbyking | 1 | $9.49 | |
| 7 | Hobbyking Quadcopter Power distribution board | Hobbyking | 1 | $3.39 | |
| 8 | Hobbyking Lipoly low voltage alarm | Hobbyking | 1 | $2.15 | |
| 9 | Turnigy Battery Strap | Hobbyking | 1 | $1.59 | |
| 10 | Mounting pad | Hobbyking | 1 | $1.99 | |
| 11 | 4mm bullet heads to connect battery to power distribution board | polymax | 1 | $2.83 | |
| 12 | Vibration damping balls | 1 | $9.10 | ||
| 13 | 3.5 mm bullet heads for power break distribution board | 1 | $1.83 | ||
| 14 | iMax B6 Battery Charger | 1 | $33.46 |
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
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.
