Difference between revisions of "F16: Autonomous Secure Delivery"
(→Team Members & Responsibilities) |
(→Parts List & Cost) |
||
| Line 92: | Line 92: | ||
== Parts List & Cost == | == Parts List & Cost == | ||
| − | |||
| − | |||
| − | |||
| + | {| class="wikitable" | ||
| + | ! align="center"|Qty | ||
| + | ! align="center"|Description | ||
| + | ! align="center"|Manufacturer | ||
| + | ! align="center"|Part Number | ||
| + | ! align="center"|Cost | ||
| + | ! align="center"|Links | ||
| + | |- | ||
| + | |1 | ||
| + | |SJ One Board [http://www.socialledge.com/sjsu/images/d/de/2012SJOneBoardSchematic.pdf] | ||
| + | |Preet | ||
| + | |SJ-one | ||
| + | |$80 | ||
| + | |http://www.socialledge.com/sjsu/index.php?title=SJ_One_Board | ||
| + | |- | ||
| + | |} | ||
== Design & Implementation == | == Design & Implementation == | ||
Revision as of 18:53, 18 November 2016
Contents
Autonomous Secure Delivery
Abstract
Autonomous vehicle, that autonomously searches an area until it is able to locate a unique object. Once the unique object is recognized by the onboard Pixy Camera, the BOT will then drive towards the object. This will be done by the Pixy Camera sending a signal to the microcontroller that the object has been located. The microcontroller will then call a different function and control the servos to drive the vehicle towards the located object. Overall, the main idea of this project is to create the drivers for the pixy camera to find the object and to communicate with the Microstick II Controller.
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
- Mohit Bhasin
- Make mount and configure Pixy Camera along with the SJOne Board
- Develop SPI Driver to allow for communication between the micro-controller and Pixy Camera
- Make communication between Pixy Camera and servos on the mount for movement
- Nadim Sarras
- Design and Create Hardware connections between micro-controller and external parts.
- Develop SPI Driver to allow for communication between the micro-controller and Pixy Camera
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 Date | Task | Completion |
|---|---|---|---|---|
| 1 | 10/21/2016 | 10/28/2016 | Finish Proposal and confirm idea | Completed |
| 2 | 10/29/2016 | 11/04/2016 | Draw schematics of final product and determine the materials we need | Not Completed |
| 3 | 11/05/2016 | 11/11/2016 | Write Drivers for Pixy camera to learn and recognize objects | Not Completed |
| 4 | 11/12/2016 | 11/18/2016 | Make a mount for the camera that is able to move around and follow objects | Not Completed |
| 5 | 11/19/2016 | 11/25/2016 | Program Microcontroller to interface with the Pixy Camera, using SPI communication. | Not Completed |
| 6 | 11/26/2016 | 11/02/2016 | Finish Free RTOS tasks for the camera and moveable mount | Not Completed |
| 7 | 12/03/2016 | 12/09/2016 | Test and Configure Project Accordingly | Not Completed |
| 8 | 12/10/2016 | 12/16/2016 | Final Tests | Not Completed |
Parts List & Cost
| Qty | Description | Manufacturer | Part Number | Cost | Links |
|---|---|---|---|---|---|
| 1 | SJ One Board [1] | Preet | SJ-one | $80 | http://www.socialledge.com/sjsu/index.php?title=SJ_One_Board |
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.
