Difference between revisions of "S16: Laser Cutter Motor Controller"

From Embedded Systems Learning Academy
Jump to: navigation, search
(Created page with "=== Grading Criteria === <font color="green"> * How well is Software & Hardware Design described? * How well can this report be used to reproduce this project? * Code Quali...")
 
(→‎Grading Criteria)
 
(25 intermediate revisions by one other user not shown)
Line 1: Line 1:
−
=== Grading Criteria ===
 
−
<font color="green">
 
−
*  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.
 
−
</font>
 
−
 
 
== Project Title ==
 
== Project Title ==
 +
Laser Cutter Motor Controller
  
 
== Abstract ==
 
== Abstract ==
−
This section should be a couple lines to describe what your project does.
+
This is a PoC (Proof of Concept) project to aid in the design of my CmpE 195A senior project. For this PoC I will be using a joystick hooked up to one SJOne board to wirelessly (or not) control another SJOne board which will in turn control 2 stepper motor controller chips to finally control 2 stepper motors on my laser cutter.
  
 
== Objectives & Introduction ==
 
== 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.
+
The LazTech Motor Driver should be able to drive two motors independently. It should be able to follow both scripted and manually input movement commands which include: moves, lines, and curves.
  
 
=== Team Members & Responsibilities ===
 
=== Team Members & Responsibilities ===
−
*  Yaron Alexandrovich
+
*  Alex Kennedy
−
** 
+
**  Hardware design
−
*  Emil Kurian
+
**  Software design
−
** 
+
**  System integration
−
*  Gerard Ramos
 
−
** 
 
−
*  Fred Sun
 
−
** 
 
  
 
== Schedule ==
 
== 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.
 
−
 
 
{| class="wikitable"
 
{| class="wikitable"
 
|-
 
|-
Line 40: Line 23:
 
|-
 
|-
 
! scope="row"| 1
 
! scope="row"| 1
−
| 10/8
+
| 4/11
−
| Task list
+
| Initialization
−
| Completed?  Problems Encountered?
+
| Completed
 +
|-
 +
! scope="row"| 2
 +
| 4/18
 +
| PCB Design
 +
| Completed. Some of the traces are not ideally placed but they should still work.
 +
|-
 +
! scope="row"| 3
 +
| 4/25
 +
| Order Parts and Start Coding
 +
| Completed
 +
|-
 +
! scope="row"| 4
 +
| 5/2
 +
| Finish Coding and Assemble
 +
| Not completed. Due to problems with assembling the board, it is going to be impossible to complete this project on time. (See the Issues section for details.)
 +
|-
 +
! scope="row"| 5
 +
| 5/9
 +
| Finalization
 +
| Completed.
 
|}
 
|}
  
 
== Parts List & Cost ==
 
== Parts List & Cost ==
−
Give a simple list of the cost of your project broken down by components. Do not write long stories here.
+
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]
  
 
== Design & Implementation ==
 
== 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.
+
Below are the hardware and software design files. This includes both the hardware schematics and board layout (all layers). In addition the software workflow is provided.
 +
 
 +
The main interface is a simple GPIO clock pulse interface that latches into the Allegro stepper motor driver chips. Various options can be specified such as the direction, step size, and sleep functions. Details of how the interface works can be found in the Allegro documentation.
  
 
=== Hardware Design ===
 
=== Hardware Design ===
−
Discuss your hardware design here. Show detailed schematics, and the interface here.
+
[[File:laztech_sch.png|center|Figure 2. Schematics]]
 +
[[File:laztech_brd.png|center|Figure 3. Board layout]]
  
 
=== Hardware Interface ===
 
=== Hardware Interface ===
Line 58: Line 64:
  
 
=== Software Design ===
 
=== 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.
+
For this project the task will enter the workflow at the flex scanner stage. from here we can manually generate move, line, and curve primitives which can be queued into the curve queue. For this project only one static graphics stack will be required and therefore graphics opcodes will not need to be decoded. Additionally a graphics stack will not be required. Once a set of curves is queued and a stroke command is sent, the cut_curve task will be started which will then perform the actual motor control movements.
 +
[[File:laztech_sw_flow.png|center|Figure 4. Software workflow]]
  
 
=== Implementation ===
 
=== 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.
+
The following are simulated renders of the above board and schematic.
 +
[[File:laztech_brd_sim_front.png|500px|thumb|center|Figure 5. Front of simulated board]]
 +
[[File:laztech_brd_sim_back.png|500px|thumb|center|Figure 6. Back of simulated board]]
  
 
== Testing & Technical Challenges ==
 
== 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?
+
Given another few weeks on this project, it could have been completed. A large portion of the learning from this project was in the hardware assembly phase. I learned that to effectively design and implement custom PCBs with SMT a good rework station or oven is required. I will be purchasing these items in the very near future.
−
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 ===
+
=== Issue #1 Assembly ===
−
Discuss the issue and resolution.
+
This project was ultimately stopped by a lack of manufacturing hardware. The Allegro stepper motor driver chips use a eTSSOP-24 SMD pad layout. This means that the pin pitch (spacing between pins) is only 0.6 mm. This proved too hard to solder by hand. In order to resolve this issue, a solder paste mask is required. This would allow solder paste to be applied to the pads only and would limit the amount of pin bridging. Due to time constraints it is impossible to order one of these in time for demo.
  
 
== Conclusion ==
 
== 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?
+
This project has ultimately given me more experience with full system engineering. I feel like I have a complete mastery over the software side of this class so it was really interesting to try my hand and more PCB design and system integration. Although a failure in this class, the lessons learned here will help me in CmpE 195B and in future endeavors.
−
 
 
−
=== Project Video ===
 
−
Upload a video of your project and post the link here.
 
  
 
=== Project Source Code ===
 
=== Project Source Code ===
 
*  [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]
 
*  [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]
 +
*  [https://sourceforge.net/projects/armdevpkg/files/ SJSU_Dev.7z]
 +
*  [https://gitlab.com/preet/lpc1758_freertos lpc1758_freertos]
 +
*  [https://gitlab.com/LaikaN57/lpc1758_freertos lpc1758_freertos (modified)]
  
 
== References ==
 
== References ==
 
=== Acknowledgement ===
 
=== Acknowledgement ===
−
Any acknowledgement that you may wish to provide can be included here.
+
I would like to thank my CmpE 195A group for their help in this project.
  
 
=== References Used ===
 
=== References Used ===

Latest revision as of 19:55, 26 May 2016

Project Title

Laser Cutter Motor Controller

Abstract

This is a PoC (Proof of Concept) project to aid in the design of my CmpE 195A senior project. For this PoC I will be using a joystick hooked up to one SJOne board to wirelessly (or not) control another SJOne board which will in turn control 2 stepper motor controller chips to finally control 2 stepper motors on my laser cutter.

Objectives & Introduction

The LazTech Motor Driver should be able to drive two motors independently. It should be able to follow both scripted and manually input movement commands which include: moves, lines, and curves.

Team Members & Responsibilities

  • Alex Kennedy
    • Hardware design
    • Software design
    • System integration

Schedule

Week# Date Task Actual
1 4/11 Initialization Completed
2 4/18 PCB Design Completed. Some of the traces are not ideally placed but they should still work.
3 4/25 Order Parts and Start Coding Completed
4 5/2 Finish Coding and Assemble Not completed. Due to problems with assembling the board, it is going to be impossible to complete this project on time. (See the Issues section for details.)
5 5/9 Finalization Completed.

Parts List & Cost

Figure 1. Bill of Materials

Design & Implementation

Below are the hardware and software design files. This includes both the hardware schematics and board layout (all layers). In addition the software workflow is provided.

The main interface is a simple GPIO clock pulse interface that latches into the Allegro stepper motor driver chips. Various options can be specified such as the direction, step size, and sleep functions. Details of how the interface works can be found in the Allegro documentation.

Hardware Design

Figure 2. Schematics
Figure 3. Board layout

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

For this project the task will enter the workflow at the flex scanner stage. from here we can manually generate move, line, and curve primitives which can be queued into the curve queue. For this project only one static graphics stack will be required and therefore graphics opcodes will not need to be decoded. Additionally a graphics stack will not be required. Once a set of curves is queued and a stroke command is sent, the cut_curve task will be started which will then perform the actual motor control movements.

Figure 4. Software workflow

Implementation

The following are simulated renders of the above board and schematic.

Figure 5. Front of simulated board
Figure 6. Back of simulated board

Testing & Technical Challenges

Given another few weeks on this project, it could have been completed. A large portion of the learning from this project was in the hardware assembly phase. I learned that to effectively design and implement custom PCBs with SMT a good rework station or oven is required. I will be purchasing these items in the very near future.

Issue #1 Assembly

This project was ultimately stopped by a lack of manufacturing hardware. The Allegro stepper motor driver chips use a eTSSOP-24 SMD pad layout. This means that the pin pitch (spacing between pins) is only 0.6 mm. This proved too hard to solder by hand. In order to resolve this issue, a solder paste mask is required. This would allow solder paste to be applied to the pads only and would limit the amount of pin bridging. Due to time constraints it is impossible to order one of these in time for demo.

Conclusion

This project has ultimately given me more experience with full system engineering. I feel like I have a complete mastery over the software side of this class so it was really interesting to try my hand and more PCB design and system integration. Although a failure in this class, the lessons learned here will help me in CmpE 195B and in future endeavors.

Project Source Code

References

Acknowledgement

I would like to thank my CmpE 195A group for their help in this project.

References Used

List any references used in project.

Appendix

You can list the references you used.

Retrieved from "http://socialledge.com/sjsu/index.php?title=S16:_Laser_Cutter_Motor_Controller&oldid=27857"