Difference between revisions of "F13: Bulb Ramper"
Proj user9 (talk | contribs) (→Objectives & Introduction) |
Proj user9 (talk | contribs) (→Team Members & Responsibilities) |
||
| Line 30: | Line 30: | ||
* Rex Kung | * Rex Kung | ||
| − | ** WIFI Interface | + | ** WIFI Interface,FreeRTOS Software Design..... |
{| border="1" cellpadding="2" | {| border="1" cellpadding="2" | ||
Revision as of 06:03, 29 October 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.
Project Title
Bulb Ramper
Abstract
Time-lapse photography is the process of taking many exposures over a long period of time to produce impressive short videos and photos, which create a feeling of traveling quickly through time. While the ability to create time-lapse videos or photos is available to anyone with a camera and a fairly inexpensive with a trigger controller, the ability to increase exposure time (bulb ramping) while moving the camera is not. Moving bulb-ramping device currently on the market cost hundreds of dollars. Our team intends to create a bulb-ramping device that can rotate 360 degrees around and, will trigger the camera shutter in sync with travel and will also have the ability to pan as it travels.
Objectives & Introduction
The goals of the mechanical design will be to create a physically robust gear that has a professional appearance and has little environmental impact, all while performing its job in an efficient manner. The goals of the software design will be to create efficient and professional C code that performs all required tasks while minimizing the possibility of software and hardware conflicts. The microcontroller will be the operating brains for this project, interfacing with the motor driver to provide linear motion from the stepper motors and rotate the camera panning head. Coding will allow the operator to set a variety of attributes related to camera function. For example: 1. Number of pictures to take 2. How much exposure time to ramp in a specific period 3. Time between pictures 4. Rotating the camera platform Overall all the design will be handled with a top-down systematic and methodical approach.
Team Members & Responsibilities
- Hamed Gohari
- Motor Controller and FreeRTOS Software Design
- Rex Kung
- WIFI Interface,FreeRTOS Software Design.....
| Week # | Date | Planned Activities | Actual |
| 1 | 10/8/2013 | Develop Proposal | Successfully completed |
| 2 | 10/15/2013 | Acquire Parts
Identify interfaces to be used. Identify pin selections Review datasheets |
· All parts are in
· Interfaces are identified · All datasheets are reviewed |
| 3 | 10/22/2013 | ·Work on the Chassis
Write PWM driver for Servo motor and Integrate the Opto-coupler |
·Chassis build up has been completed
PWM Driver has been completed and Integration of Opto-coupler completed |
| 4 | 10/29/2013 | Integrate all the LEDs and Switches
· Work on WIFI Interface |
·Integration is completed successfully
Coding for WIFI has been completed |
| 5 | 11/5/2013 | Work on the FreeRTOS-based firmware | |
| 6 | 11/12/2013 | Debug and make minor adjustments | |
| 7 | 11/19/2013 | System Integration Initial round | |
| 8 | 11/26/2013 | System Integration Final round
Complete and revise project report |
|
| 9 | 12/3/2013 | Finalize and deliver project
Demo project |
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:
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
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.
