Difference between revisions of "S18: Spybot"
Proj user1 (talk | contribs) (→Acknowledgement) |
Proj user1 (talk | contribs) (→References Used) |
||
| Line 163: | Line 163: | ||
List any references used in project. | List any references used in project. | ||
<p> </p> | <p> </p> | ||
| − | + | * [https://github.com/ccrisan/motioneyeos/wiki MotionEyeOS Source Code] | |
=== Appendix === | === Appendix === | ||
You can list the references you used. | You can list the references you used. | ||
Revision as of 01:56, 23 May 2018
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
Spybot
Abstract
The team will develop a RC car driven remotely with an Android smartphone. The RC car will be equipped with a camera to provide real-time visual feedback to the smartphone. The camera will also be mounted on a servo to add the capability to change the camera angle. The SJOne will be used to drive the motor and servo of the car in addition to the camera’s servo. The Android smartphone will communicate with the SJOne using Bluetooth. The Android smartphone will be used to command the SJOne and drive the car and motorized camera. The SJOne will stream visual data to the Android smartphone.
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
- YuYu Chen
- Android app & bluetooth communication
- Jason Tran
- PCB design & RC car firmware
- Sophia Quan
- Servo camera mount and camera integration
- Andrew Javier
- Camera integration
- Jeremy Chau
- Camera integration
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 | Status |
|---|---|---|---|
| 1 | 04/15/2018 | Able to communicate with Bluetooth module on MCU by end of the week | Completed |
| 2 | 04/22/2018 | Start on Android application and have UI finished by end of week
Research possible ways to display live video feed in Android application |
Completed |
| 3 | 04/29/2018 | Establish Bluetooth communication with Android App and MCU
Start PCB design Start on motor and servo(s) controller Install MotionEyeOS and get familiar with the UI |
Completed |
| 4 | 05/06/2018 | Test Android app communication with RC car
Test RPi Camera with MotionEyeOS on multiple devices Get camera servo up and running by end of week |
Completed |
| 5 | 05/13/2018 | System Integration and testing | In progress |
| 6 | 05/20/2018 | System testing | In progress |
Parts List & Cost
| Quantity | Vendor | Item | Price |
|---|---|---|---|
| 1 | San Jose State University | SJ One Board | $80.00 |
| 1 | Adafruit | Raspberry Pi Zero W Camera Pack | $44.95 |
| 1 | Traxxas | Traxxas Stampede: Monster Truck | $199.95 |
| 1 | ITead | BTBee Pro | $12.50 |
| Total | $337.37 |
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:
<Bug/issue name>
Discuss the issue and resolution.
Connecting to the Pi Zero W
Initially, the group wanted to have the phone to connect to the Raspberry Pi through Wi-Fi. However, when setting up the Pi to be a Wi-Fi host, the phones could not discover the Pi making communication impossible. Furthermore, it did not allow the Pi to initially boot up properly. To rectify this problem, the group decided to have the mobile phone with the application be a hotspot host. While this means that the Pi would have to be reconfigured every time it wants to connect to a new phone but the results were consistent with the feed from the camera being able to broadcast to the host phone.
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
- Preetpal Kang
- Khalil Estell
References Used
List any references used in project.
Appendix
You can list the references you used.
