Difference between revisions of "S17: ElectricBoard"
Proj user15 (talk | contribs) (→Schedule) |
Proj user15 (talk | contribs) (→Schedule) |
||
| Line 96: | Line 96: | ||
| Testing/Debug/Troubleshoot | | Testing/Debug/Troubleshoot | ||
| Completed | | Completed | ||
| − | | | + | | Need to improve wireless communication range. Max motor velocity causes instability. |
| 05/08/2017 | | 05/08/2017 | ||
|- | |- | ||
| Line 109: | Line 109: | ||
| 05/16 | | 05/16 | ||
| Prepare for Demo/Complete Report | | Prepare for Demo/Complete Report | ||
| + | | In Progress | ||
| + | | Report began 05/13 | ||
| | | | ||
| − | |||
| − | |||
|- | |- | ||
! scope="row"| 10 | ! scope="row"| 10 | ||
Revision as of 00:54, 14 May 2017
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.
ElectricBoard
Abstract
Plan to create a user-controlled skateboard primarily via wireless remote and/or additionally a pressure sensor. One microcontroller necessary for wireless remote. Another microcontroller necessary for motor controls.
Objectives & Introduction
- Make a setup for an Electric skateboard which can be controlled with a remote.
Team Members & Responsibilities
- Andrew Vo
- Elton Leung
- Eric Panganiban
- James Grantham
- Saketh Sai Narayana
Schedule
| Week# | Date | Task | Status | Details | Actual Date Complete |
|---|---|---|---|---|---|
| 0 | 03/14 | Finalize Project Proposals | Completed | Project Proposal Finalized. | 03/14/2017 |
| 1 | 03/21 | Finalize Bill of Materials/Design Schematic | Completed | BoM finalized. Design schematic completed. | 03/25/2017 |
| 2 | 03/28 | Order Parts/Components | Completed | Kit ordered 3/22. LiPo and Charger ordered 3/30. Personal longboard to be used. | 03/30/2017 |
| 3 | 04/04 | PCB Design/Order | Completed | PCB designed 04/07. PCB received 5/11. | 05/11/2017 |
| 4 | 04/11 | Assembly of Components | Completed | Will not be using housing. All parts mounted by velcro tape. | 05/10/2017 |
| 5 | 04/18 | Motor Control Implementation | Completed | Use PWM pin 2.0 on board. | 04/20/2017 |
| 6 | 04/25 | Remote Control Implementation | Screen in progress. | Using pin 2.6 for button and pin 0.26 for analog slider. | |
| 7 | 05/02 | Testing/Debug/Troubleshoot | Completed | Need to improve wireless communication range. Max motor velocity causes instability. | 05/08/2017 |
| 8 | 05/09 | Fine Tune | |||
| 9 | 05/16 | Prepare for Demo/Complete Report | In Progress | Report began 05/13 | |
| 10 | 05/23 | Project Demo |
Parts List & Cost
| Part Name | Cost | Qty | Comments |
|---|---|---|---|
| SJOne Board | $80.00 | 2 | Microcontrollers used for communicating b/w remote control/skateboard |
| Nucbot Motor Kit | $369.00 | 1 | Includes Motors, wheels, and ESC |
| LiPo Batteries | $85.99 | 2 | Rechargeable batteries for ESC inputs |
| LiPo Balancer/Charger | $62.99 | 1 | Charge LiPo batteries |
| PCB order | ??? | 1 | ??? |
| Skateboard | ??? | 1 | ??? |
| Component Housing | ??? | 1 | ??? |
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.
