Difference between revisions of "S15: Rubik's Cube Solver"
Proj user15 (talk | contribs) (→Parts List & Cost) |
Proj user15 (talk | contribs) (→Parts List & Cost) |
||
| Line 162: | Line 162: | ||
| | | | ||
| --- | | --- | ||
| − | | $ | + | | $16.5 |
|- | |- | ||
|} | |} | ||
Revision as of 09:50, 12 May 2015
Contents
Rubik's Cube Solver
Abstract
The project aims at taking a seemingly tough problem of a Rubik's cube and trying to solve it without human intervention, through the aid of the available SJOne board and a custom set of algorithms by automating the whole process. We intend to concentrate our efforts towards solving a 3x3x3 cube..
Objectives & Introduction
The project is intended to be designed to have the following features,
- A console that detects the upper face of the cube and capturing the colors of the 9 squares in it. By our initial study, we believe we just need to know the top face of the cube to solve it. The console application can be either a desktop application or a mobile application and it is open to discussion as yet.
- We initially would like to explore the algorithm that we think is optimum for solving the cube. If it does not turn out to be the case, we intend to program one of the more optimum algorithms called Kociemba's algorithm.
- A physical holder that contains an actual cube and rotates according to the aforementioned algorithm to solve the cube.
Team Members & Responsibilities
- Nikhil Chaturvedi
- Cube solving algorithm
- Interface SJOne with cube solving arms
- Bluetooth connectivity from console to SJOne board
- Preeti Benake
- Build the cube solving arms
- Interface cube algorithm with arms
- Rajashree Kambli
- Bluetooth connectivity from console to SJOne board
- Interface cube algorithm with arms
- Shahid Qureshi
- Bluetooth connectivity from console to SJOne board
- Build the cube solving arms
Team Schedule
| Sl.No | Start Date | End Date | Task | Status | Actual Completion Date |
|---|---|---|---|---|---|
| 1 | 02/28/2015 | 03/02/2015 | Finalized high level design architecture | Completed on time | 03/02/2015 |
| 2 | 02/28/2015 | 04/17/2015 | Investigating Robotic arm design; eliminated few hardware options. | Completed on time | --/--/2015 |
| 3 | 03/07/2015 | 03/09/2015 | Investigated interfacing console with SJOne board. | Completed on time | 03/09/2015 |
| 4 | 03/10/2015 | 03/14/2015 | Investigated BlueZ Bluetooth stack for Python and C. | Completed on time | 03/14/2015 |
| 5 | 03/29/2015 | 04/17/2015 | Implementing Bluetooth interfacing of SJOne board using C BlueZ and Console using PyblueZ | Completed on time | --/--/2015 |
| 6 | 04/18/2015 | 04/20/2015 | Order and test the hardware components | Completed on time | --/--/2015 |
| 7 | 04/22/2015 | 04/24/2015 | Interfacing the motors to SJOne board | Ongoing | --/--/2015 |
| 8 | 04/10/2015 | --/--/2015 | Investigating implementation of Rubik cube solving algorithm (Kociemba's algorithm) | Ongoing | --/--/2015 |
| 9 | 04/28/2015 | 05/03/2015 | Build the Robot arm and test the controls | Ongoing | --/--/2015 |
| 10 | 05/03/2015 | 05/10/2015 | Interface the Robot arm and test the algorithms | Scheduled | --/--/2015 |
| 11 | 05/11/2015 | 05/19/2015 | Testing | Scheduled | --/--/2015 |
Parts List & Cost
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
| Item# | Part Desciption | Vendor | Qty | Cost |
|---|---|---|---|---|
| 1 | Servo Motors | 6 | $56.58 | |
| 2 | Robotic Claw | 2 | $39.92 | |
| 3 | Speed Rubik cube | 2 | $21.48 | |
| 4 | Turnable table for Motors | 1 | $7.99 | |
| 5 | Robotic Claw stands | 2 | $7.52 | |
| 6 | Wires and other Accessories | --- | $16.5 |
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.
