F16: Wireless Tilt Controlled Camera Arm
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.
Wireless Tilt Controlled Camera Arm
Abstract
For this camera system, the camera moves along a track according to user’s controls. The controller, which will be one of the SJOne boards, will control the direction of movement of the camera along the track. The camera will be mounted on a track and will be connected to the second SJOne board. The camera’s movement speed is set. However, the camera’s direction will be determined by the angle in which the controller is tilted. The camera’s tilt speed will be tracked using the attached SJOne board’s accelerometer and used in the movement of the camera’s vision. Similar to the movement of the human eye, the camera in this camera system will be able see 180 degrees in all directions in forward vision. The camera can look at an angle in any direction such as left, right, up, and down. The camera can be stopped or turned off by pressing a button on the controller. If the controller is tilted 90 degrees vertically, then the camera will start moving in that tilted direction. If there is an error, the user can press a button on the controller that will stop receiving accelerometer data from the controller board and the camera will reset back to the center position of the track and the camera will be back to facing the correct orientation. Data is transferred through wireless communication between the 2 SJOne boards.
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
- Kevin Lai
- Acceleration Sensor and Wireless communications Software developer
- Document Writer
- Alex Reyna
- Arm and Track Designer, and Motor Driving Software developer
- Document Writer
r
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 | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 10/8 | 10/14 | Write Project Proposal | Completed | 10/14 |
| 2 | 10/14 | 10/21 | Finalize Project Design | Completed | 10/21 |
| 3 | 10/21 | 10/28 | Research and Determine Necessary Components | Completed | 10/28 |
| 4 | 10/28 | 11/11 | Purchase Parts | In Progress | TBA |
| 5 | 11/11 | 11/18 | Generate Schematics and Begin Prototyping | Incomplete | TBA |
| 6 | 11/18 | 11/25 | Create Moveable Camera Arm | Incomplete | TBA |
| 7 | 11/25 | 12/2 | Program First Microcontroller to Interface with the Camera Arm | Incomplete | TBA |
| 8 | 12/2 | 12/9 | Program Second Microcontroller to Act as Wireless Remote Controller of Camera Arm | Incomplete | TBA |
| 9 | 12/9 | 12/16 | Perform Final Tests, Generate Final Report, and Prepare for Demo | Incomplete | TBA |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Part Name | Part Number | Quantity | Cost | Notes |
|---|---|---|---|---|
| Microcontroller | SJOne Board | 2 | $160 | One for Main Wireless Controller and One for Camera Motion Controller |
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.
