Difference between revisions of "S18: XY-Plotter"
Proj user12 (talk | contribs) (→Schedule) |
Proj user12 (talk | contribs) (→Schedule) |
||
| Line 54: | Line 54: | ||
| 04/10 | | 04/10 | ||
|• Determine the required software for generating and visualizing the Gcode. | |• Determine the required software for generating and visualizing the Gcode. | ||
| − | • Read | + | • Read file from Sd-card and interpret single line G-code. |
| In Progress | | In Progress | ||
|- | |- | ||
| Line 66: | Line 66: | ||
| 04/24 | | 04/24 | ||
| • Assemble the plotter machine. | | • Assemble the plotter machine. | ||
| − | • Circuit testing on protoboard. | + | • Circuit testing on protoboard. |
| − | • | + | • Determine the relation between G-code values and PWM pulses on both the stepper motors. |
|- | |- | ||
! scope="row"| 6 | ! scope="row"| 6 | ||
| 05/01 | | 05/01 | ||
| − | | • | + | | • Test the plotter machine for drawing a straight line. |
| − | • | + | • Read multiple lines G-code and in |
| − | |||
| | | | ||
|} | |} | ||
Revision as of 00:20, 2 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
XY-Plotter
Abstract
The project aims at building a 2D XY-plotter which can efficiently draw 2D figures. The plotter machine is assembled based on the H-bot mechanism where the two stepper motors are on the main chassis connected to the single belt. Both the motors account for the movement of the chassis in X and Y axis. A servo motor is used to control the pen height which is connected to the main chassis. Gcode interpreter is developed in order to make the SJ one board decode the G-code and control the motors accordingly.Sd-card is used to provide the Gcode to the SJ one board.
Objectives & Introduction
Team Members & Responsibilities
- Akshay Kurli
- Gaurav Yadav
- Pritam Gholap
- Tanmay Kishore Jambhekar
Schedule
| Week# | Date | Task | Actual |
|---|---|---|---|
| 1 | 03/27 | • Research different mechanism for plotter assembling.
• Requirement documentation.List out the parts required. |
Completed on 03/31 |
| 2 | 04/03 | Order Components | Completed on 04/08 |
| 3 | 04/10 | • Determine the required software for generating and visualizing the Gcode.
• Read file from Sd-card and interpret single line G-code. |
In Progress |
| 4 | 04/17 | • Test both the stepper motor and servo motor with the SJ one Board.
• Design the PCB shield for servo and stepper motor. |
In Progress |
| 5 | 04/24 | • Assemble the plotter machine.
• Circuit testing on protoboard. • Determine the relation between G-code values and PWM pulses on both the stepper motors. | |
| 6 | 05/01 | • Test the plotter machine for drawing a straight line.
• Read multiple lines G-code and in |
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:
<Bug/issue name>
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.
