Embedded Systems Learning Academy - User contributions [en]

S16: Laser Cutter Motor Controller

2016-05-25T01:06:55Z

Alex: /* Conclusion */

=== 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 ==
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 ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]
[[File:laztech_brd.png|center|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.
[[File:laztech_sw_flow.png|center|Figure 4. Software workflow]]

=== 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 ==
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 ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T01:02:07Z

Alex: /* Testing & Technical Challenges */

=== 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 ==
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 ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]
[[File:laztech_brd.png|center|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.
[[File:laztech_sw_flow.png|center|Figure 4. Software workflow]]

=== 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 ==
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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:59:41Z

Alex: /* Software Design */

=== 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 ==
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 ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]
[[File:laztech_brd.png|center|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.
[[File:laztech_sw_flow.png|center|Figure 4. Software workflow]]

=== 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 ==
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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:48:04Z

Alex: /* Design & Implementation */

=== 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 ==
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 ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]
[[File:laztech_brd.png|center|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 ===
[[File:laztech_sw_flow.png|center|Figure 4. Software workflow]]

=== 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 ==
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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:45:30Z

Alex: /* Design & Implementation */

=== 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 ==
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 ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|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.

=== Hardware Design ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]
[[File:laztech_brd.png|center|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 ===
[[File:laztech_sw_flow.png|center|Figure 4. Software workflow]]

=== 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 ==
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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:43:05Z

Alex: /* Objectives & Introduction */

=== 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 ==
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 ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
[[File:laztech_sw_flow.png|center|Figure 3. Software workflow]]

=== Implementation ===
The following are simulated renders of the above board and schematic.
[[File:laztech_brd_sim_front.png|500px|thumb|center|Figure 4. Front of simulated board.]]
[[File:laztech_brd_sim_back.png|500px|thumb|center|Figure 5. Back of simulated board.]]

== 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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:41:24Z

Alex: /* Implementation */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
[[File:laztech_sw_flow.png|center|Figure 3. Software workflow]]

=== Implementation ===
The following are simulated renders of the above board and schematic.
[[File:laztech_brd_sim_front.png|500px|thumb|center|Figure 4. Front of simulated board.]]
[[File:laztech_brd_sim_back.png|500px|thumb|center|Figure 5. Back of simulated board.]]

== 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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:40:48Z

Alex: /* Implementation */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
[[File:laztech_sw_flow.png|center|Figure 3. Software workflow]]

=== Implementation ===
The following are simulated renders of the above board and schematic.
[[File:laztech_brd_sim_front.png|500px|thumb|left|Figure 4. Front of simulated board.]]
[[File:laztech_brd_sim_back.png|500px|thumb|right|Figure 5. Back of simulated board.]]

== 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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:38:13Z

Alex: /* Issue #1) Assembly */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
[[File:laztech_sw_flow.png|center|Figure 3. Software workflow]]

=== 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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:37:44Z

Alex: /* Acknowledgement */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
[[File:laztech_sw_flow.png|center|Figure 3. Software workflow]]

=== 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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:34:53Z

Alex: /* Conclusion */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
[[File:laztech_sw_flow.png|center|Figure 3. Software workflow]]

=== 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:

=== 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 ==
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 Source Code ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:34:20Z

Alex: /* My Issue #1 */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
[[File:laztech_sw_flow.png|center|Figure 3. Software workflow]]

=== 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:

=== 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 ==
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 ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:28:44Z

Alex: /* Software Design */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
[[File:laztech_sw_flow.png|center|Figure 3. Software workflow]]

=== 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 ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:27:17Z

Alex: /* Hardware Design */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
[[File:laztech_sch.png|center|Figure 2. Schematics]]

=== 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 ===
* [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 ==
=== 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.

File:Laztech sw flow.png

2016-05-25T00:25:26Z

Alex:

File:Laztech sch.png

2016-05-25T00:25:17Z

Alex:

File:Laztech brd sim front.png

2016-05-25T00:25:08Z

Alex:

File:Laztech brd sim back.png

2016-05-25T00:24:57Z

Alex:

File:Laztech brd.png

2016-05-25T00:24:13Z

Alex:

S16: Laser Cutter Motor Controller

2016-05-25T00:21:27Z

Alex: /* Parts List & Cost */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
[[File:laztech_bom.png|500px|thumb|center|Figure 1. Bill of Materials]]

== 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 ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:21:16Z

Alex: /* Parts List & Cost */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
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 ==
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 ===
* [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 ==
=== 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.

File:Laztech bom.png

2016-05-25T00:19:30Z

Alex:

S16: Laser Cutter Motor Controller

2016-05-25T00:05:18Z

Alex: /* Team Members & Responsibilities */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Hardware design
** Software design
** System integration

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
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 ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-05-25T00:04:45Z

Alex: /* Schedule */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Do all of the things.

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| 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 ==
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 ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-04-06T07:20:28Z

Alex: /* Schedule */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Do all of the things.

== Schedule ==
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| Completed? Problems Encountered?
|-
! scope="row"| 2
| 4/18
| PCB Design
| Completed? Problems Encountered?
|-
! scope="row"| 3
| 4/25
| Order Parts and Start Coding
| Completed? Problems Encountered?
|-
! scope="row"| 4
| 5/2
| Finish Coding and Assemble
| Completed? Problems Encountered?
|-
! scope="row"| 5
| 5/9
| Finalization
| Completed? Problems Encountered?
|}

== 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 ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-04-06T07:17:13Z

Alex: /* Project Source Code */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Do all of the things.

== 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"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| Completed? Problems Encountered?
|-
! scope="row"| 2
| 4/18
| PCB Design
| Completed? Problems Encountered?
|-
! scope="row"| 3
| 4/25
| Order Parts and Start Coding
| Completed? Problems Encountered?
|-
! scope="row"| 4
| 5/2
| Finish Coding and Assemble
| Completed? Problems Encountered?
|-
! scope="row"| 5
| 5/9
| Finalization
| Completed? Problems Encountered?
|}

== 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 ===
* [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 ==
=== 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.

S16: Laser Cutter Motor Controller

2016-04-06T07:00:44Z

Alex: /* Schedule */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Do all of the things.

== 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"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| Completed? Problems Encountered?
|-
! scope="row"| 2
| 4/18
| PCB Design
| Completed? Problems Encountered?
|-
! scope="row"| 3
| 4/25
| Order Parts and Start Coding
| Completed? Problems Encountered?
|-
! scope="row"| 4
| 5/2
| Finish Coding and Assemble
| Completed? Problems Encountered?
|-
! scope="row"| 5
| 5/9
| Finalization
| Completed? Problems Encountered?
|}

== 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 ===
* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]

== 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.

S16: Laser Cutter Motor Controller

2016-04-06T06:57:04Z

Alex: /* Schedule */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Do all of the things.

== 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"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 4/11
| Initialization
| Completed? Problems Encountered?
|-
! scope="row"| 2
| 4/18
| Task list
| Completed? Problems Encountered?
|-
! scope="row"| 3
| 4/25
| Task list
| Completed? Problems Encountered?
|-
! scope="row"| 4
| 5/2
| Task list
| Completed? Problems Encountered?
|-
! scope="row"| 5
| 5/9
| Finalization
| Completed? Problems Encountered?
|}

== 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 ===
* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]

== 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.

S16: Laser Cutter Motor Controller

2016-04-06T06:53:18Z

Alex: /* Team Members & Responsibilities */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Alex Kennedy
** Do all of the things.

== 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"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 10/8
| Task list
| Completed? Problems Encountered?
|}

== 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 ===
* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]

== 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.

S16: Laser Cutter Motor Controller

2016-04-06T06:51:10Z

Alex: /* Abstract */

=== 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 ==
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 ==
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.

=== Team Members & Responsibilities ===
* Yaron Alexandrovich
**
* Emil Kurian
**
* Gerard Ramos
**
* Fred Sun
**

== 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"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 10/8
| Task list
| Completed? Problems Encountered?
|}

== 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 ===
* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]

== 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.

S16: Laser Cutter Motor Controller

2016-04-06T06:43:25Z

Alex: /* Project Title */

=== 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 ==
Laser Cutter Motor Controller

== Abstract ==
This section should be a couple lines to describe what your project does.

== 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.

=== Team Members & Responsibilities ===
* Yaron Alexandrovich
**
* Emil Kurian
**
* Gerard Ramos
**
* Fred Sun
**

== 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"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 10/8
| Task list
| Completed? Problems Encountered?
|}

== 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 ===
* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]

== 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.

S16: Laser Cutter Motor Controller

2016-04-06T06:42:45Z

Alex: Created page with "=== Grading Criteria === * How well is Software & Hardware Design described? * How well can this report be used to reproduce this project? * Code Quali..."

=== 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 ==

== Abstract ==
This section should be a couple lines to describe what your project does.

== 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.

=== Team Members & Responsibilities ===
* Yaron Alexandrovich
**
* Emil Kurian
**
* Gerard Ramos
**
* Fred Sun
**

== 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"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
|-
! scope="row"| 1
| 10/8
| Task list
| Completed? Problems Encountered?
|}

== 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 ===
* [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]

== 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.

Realtime OS on Embedded Systems

2016-04-06T06:41:53Z

Alex: /* Spring 2016 */

== Program History ==
My contribution in Embedded System courses started with CmpE146. This course teaches students on how to write UART, SPI, and I2C Drivers and interface their drivers to peripherals. There are about 8 weekly labs in which students not only write drivers, but also learn the core of Real-time Operating Systems including threading (tasks), and inter-task communication using Queues and Semaphores. FreeRTOS is the operating system used with C/C++ Compiler based on GNU.

When the course was started by Dr. Ozemek @ SJSU (sometime before 2005), not many resources were out there. Still, with helpful guidance from Dr. Ozemek, interesting projects were created. This is when I started to help out in Embedded System Courses, and by collecting and sharing knowledge, we've raised the bar at SJSU!

There have been many great projects at SJSU, but since no one knew about them, the hard work went to a waste for anyone but the creator. But now we've got the infrastructure to share the projects, which turn out as great references for future students. Here is my project that started around 2007, and turned into Bachelor's Senior Design Project: 
[http://www.youtube.com/watch?v=QEadXdRl3ws&feature=plcp YouTube Video of Self-Navigating Car]

As of 2013, I have broadened my contribution to other embedded system courses like CmpE240, CmpE243 and CmpE244.

== Lab Assignments ==
This article contains laboratory assignments and resources. The assignments are under construction as we move towards SJ-One development board.
* [[Embedded System Tutorial GPIO | Lesson 1 : GPIO]]
* [[Embedded System Tutorial UART | Lesson 2 : UART]]
* [[Embedded System Tutorial SPI | Lesson 3 : SPI]]
* [[Embedded System I2C Tutorial | Lesson 4 : I2C]]
* [[Embedded System Tutorial Interrupts | Lesson 5 : Interrupts]]
* [[Embedded System Tutorial FreeRTOS | Lesson 6 : FreeRTOS Tasks]]
* [[Embedded System Tutorial File I/O | Lesson 7 : FreeRTOS Application Programming]]

Other reference articles :
* [[Bitmasking Tutorial]] (+ GPIO Example)
* [[ LPC17xx Memory Map & Interrupts]]

 
== Class Project ==
=== [[Self-driving Car]] ===
In this class project, students accomplish a self-drivable RC car with the following learning objectives:
* Learn CAN Bus and how to communicate in an industrial or automotive environment.
* Learn integration and testing across different controllers.
* Learn how to work in teams.
* Learn basics of an RTOS.

 
== Senior Design Projects ==

 
== Semester Projects ==
Every semester, students are given about 7-10 weeks to complete their projects. During this short time-span, students form groups, order parts, and begin working on their projects. The work performed during the semester is documented at this Wiki.

Here is the list of Preet's documented projects: 
* [[Preet's Relay Controller Project]]
* [[Nordic Low Powered Mesh Network stack]]
* [http://www.youtube.com/watch?v=QEadXdRl3ws&feature=plcp Senior Design Project (MS-CmpE) Video]

Here is another resource for good project references :
[http://people.ece.cornell.edu/land/courses/ece4760/FinalProjects/ Cornell EE476 Projects]

 
<HR>
=== [[Spring 2016 | Spring 2016]] ===
* [[S16: Fantastic Four]]
* [[S16: Simpsons]]
* [[S16: Mars 1]]
* [[S16: OpenSJ Bluz]]
* [[S16: Motion Copy Bot]]
* [[S16: Biker Assist]]
* [[S16: Helios]]
* [[S16: Sound Buddy]]
* [[S16: Warriors]]
* [[S16: Expendables]]
* [[S16: Ahava]]
* [[S16: Number 1]]
* [[S16: SkyNet]]

Cmpe 146:
* [[S16: Camera Gimbal]]
* [[S16: Laser Harp]]
* [[S16: Laser Cutter Motor Controller]]

 
<HR>

=== [[Fall 2015 | Fall 2015]] ===
* [[F15: Quadcopter by Thomas]]
* [[F15: Undergrads++]]
* [[F15: TopGun]]
* [[F15: Fury]]
* [[F15: Minion]]
* [[F15: ThunderBird]]

CmpE146:
* [[F15: Autonomous Mobile]]
* [[F15: Car Report]]
* [[F15: Electronic Piano]]
* [[F15: Doorknock over Bluetooth]]
* [[F15: Smart Car]]
* [[F15: Plant Control]]
* [[F15: Laser Security System]]

 
<HR>

=== [[CmpE244 Spring 2015 | Spring 2015]] ===

 
* [[S15: Quadcopter - It flies]]
* [[S15: Remote Learner]]
* [[S15: Protocol Interface: I2C - CAN Bridge]]
* [[S15: Vision RC Car]]
* [[S15: SJeight Octocopter]]
* [[S15: Swarm Robots]]
* [[S15: Smart Sparta Parking System]]
* [[S15: Touch Navigator]]
* [[S15: Wizard's Chess System]]
* [[S15: Bug Rider]]
* [[S15: Real Time Brake Assist (RTBA)]]
* [[S15: Wireless Mesh Network]]
* [[S15: Wireless Power Transfer System]]
* [[S15: Drone]]
* [[S15: Tree Node using Google Protocol Buffers]]
* [[S15: Multi-media Car]]
* [[S15: Hand Gesture Recognition using IR Sensors]]
* [[S15: CAN controlled RGB LED cubes]]
* [[S15: Rubik's Cube Solver]]
* [[S15: RFID Security Box]]
* [[S15: Automated Meeting Room Reservation]]
* [[S15: Patient Buddy System (PBS)]]

CmpE146:
* [[S15: Hovercopter]]
* [[S15: Triclops: Smart RC Car]]
* [[S15: Connect Four - Robotic Player]]
* [[S15: Self-Balancing Robot]]
* [[S15: MP3 Player with Graphic Equalizer Display]]
* [[S15: Motion-Controlled RC Car]]
* [[S15: MENL (Monster Encounter Night Light) ]]
* [[S15: Tilt Motion Controlled LED Alarm Clock]]
* [[S15: Alarm Based Coffee Maker]]

=== [[CmpE243 Fall 2014 | Fall 2014]] ===

 
* [[F14: Team2-Self Driving Car - AUG]]
* [[F14: Team3-Self Driving Car - Optimus Prime]]
* [[F14: Team4-Self Driving Car - AUG]]
* [[F14: Team5-Self Driving Car - AUG]]
* [[F14: Self Driving Undergrad Team]]

=== [[CmpE244 Spring 2014 | Spring 2014]] ===

 
* Senior Project: [[Project Advising: Remote Security System]]

 
* [[S14: Quadcopter]]
* [[S14: Smart Weather Clock]]
* [[S14: Divine WINd]]
* [[S14: Data Acquisition using CAN bus]]
* [[S14: E-Ink Display for Shopping Tags]]
* [[S14: Spectrum Analyzer for Audio Frequency Signals]]
* [[S14: CAN Firmware Uploader]]
* [[S14: Asset Management and Location System]]
* [[S14: Location Tracker]]
* [[S14: Androbot]]
* [[S14: Virtual Dog]]
* [[S14: Android based Automation]]
* [[S14: FaceTime Robo]]
* [[S14: Wireless Control Car]]
* [[S14: Power Efficient Security Door System for Light-rail using CAN Bus]]
* [[S14: Android based home monitoring system]]
* [[S14: Need For Speed]]

CmpE146
* [[S14: Hyperintelligent NFC Locker of the Future]]
* [[S14: Smart Planter]]
* [[S14: Modular Security System]]
* [[S14: Autonomous Control System]]
* [[S14: Anti-Crash Car]]
* [[S14: Tricopter]]

=== [[CmpE240 Fall 2013 | Fall 2013]] ===

* [[F13: POV Display]]
* [[F13: Line Following Robot]]
* [[F13: LED Display]]
* [[F13: Bulb Ramper]]
* [[F13: Garage Parking Assistant]]
* [[F13: Quadcopter]]
* [[F13: BarkMaster2000]]
* [[F13: Remote Control Car]]
* [[F13: Obstacle Avoidance Robot]]
* [[F13: Vehicle On Board Diagnostics]]

=== [[CmpE146 Spring 2013 | Spring 2013]] ===

* [[S13: 2D Plotter]]
* [[S13: Smart Cube]]
* [[S13: Garage Parking Aid]]
* [[S13: Smart Security]]
* [[S13: Door Alarm System]]
* [[S13: Solar Panel Tracker]]

=== [[CmpE146 Fall 2012|Fall 2012]] ===

* [[F12: Evil Watchdog]]
* [[F12: Smart Bulb]]
* [[F12: All Your Base are Belong to You]]
* [[F12: Android Controlled MP3]]
* [[F12: Unified Wireless Health Monitoring System]]
* [[F12: OBD-II Android Monitor]]
* [[F12: Self-Driving GPS Following Car]]
* [[F12: Android Door Lock]]

=== [[CmpE146 Spring 2012|Spring 2012]] ===
* [[S12: FreeRTOS based QuadCopter]]
* [[S12: Web-based MP3 Player]]
* [[S12: Self Drive Car]]
* [[S12: VAndroid]]
* [[S12: Traffic Light Sensing Vehicle]]
* [[S12: Sound Reader]]
* [[S12: Remote Controlled MP3 Player]]
* [[S12: Android Controlled Robot]]
* [[S12: Eyes-Free GPS]]

 

== Handy References ==
* [[Sample Project Report]]
* [[Project Proposal Guidelines]]
* [[CmpE146 Lab. Resources]]

ES101 - Lesson 6 : Arrays and Loops Continued

2012-10-11T22:36:43Z

Alex: Changed tolower() to toupper() so that the text matches the example.

== do/while Loops ==
'''do/while''' loops provide a way to loop through elements, and is preferred solution if the content of the body is more complex than a '''for''' loop. As long as the condition enclosed in the round brackets is a non-zero number, the loop will repeat the code body. Notice from the examples that:
* do/while loop checks for its loop continuation condition at the end
* while loop checks for its loop continuation at the beginning

<syntaxhighlight lang="c">
int quit = 0;
/**
* do/while loop will always enter its code at least once
* if quit is not 1, loop will repeat
*/
do {
printf("Enter 1 to quit: ");
scanf("%i", &quit);
}while(quit != 1);

/**
* If quit was already 1, loop will never run
*/
while(quit != 1) {
printf("Enter 1 to quit: ");
scanf("%i", &quit);
}
</syntaxhighlight>

In summary, you enclose your code within the body of the loop that you want to run and if the condition inside the round brackets is true, the loop will keep repeating the code body. The conditions can use combinational logic, such as <code>quit != 1 && quit != -1</code> as well. Furthermore, there are more ways to control the behavior of the loop as discussed in the '''break''' and '''continue''' section of this laboratory lecture.

 

== break and continue ==
The '''break''' and '''continue''' are instructions that can be used inside a loop to control the loop behavior. In simple words, the word '''break''' quits the loop immediately, and makes the CPU go to the instruction after the loop. The '''continue''' statement makes the CPU restart the loop immediately. These instructions should not be used unless absolutely necessary.

<syntaxhighlight lang="c">
int main(void)
{
int quit = 0;
while(1) { // forever loop until broken
printf("Enter 1 to quit: ");
scanf("%i", &quit);

if(1 == quit) {
break;
printf("This will not print, break immediately quits the loop.");
}
}

int restart = 0;
while(1) { // forever loop until broken
printf("Enter 1 to restart the loop: ");
scanf("%i", &restart);

if(1 == restart) {
continue;
printf("This will not print, continue immediately restarts the loop.");
}
else {
break;
}
}
}
</syntaxhighlight>

 

== Pre and Post Increment ==
You have used ++ operator before, which increments the value of a variable by one, but there is a difference between i++ and ++i when it comes to comparing the variable inside an if statement or during the comparison within a loop. i++ is called post-increment, and ++i is called pre-increment, and the difference is when the value is being compared for both.

<syntaxhighlight lang="c">
int main(void)
{
int i = 0;

// i is compared to zero first, and then incremented to 1
i = 0;
if(i++ == 0) {
printf("This will be printed!\n");
}

// i is changed to 1 first, then compared with 0
i = 0;
if(++i == 0) {
printf("This will NOT be printed!\n");
}
}
</syntaxhighlight>

 
== Example Program ==
This example code shows you how to get an input string, and capitalize every single letter of the string, and then print out the string.

<syntaxhighlight lang="c">
#include <ctype.h> // This file needed for tolower() or toupper() functions

int main(void)
{
char name[32];
printf("Enter your name: ");
scanf("%s", &name[0]);

// Get the number of chars user entered
int len = strlen(name);

for(int i=0; i<len; i++) {
// Call toupper() function to capitalize a char
// assign the upper-cased version back to name[i]
name[i] = toupper( name[i] );
}

printf("Your name in capital letters: %s\n", name);

return -1;
}
</syntaxhighlight>

 

== Assignment ==
# Build and present a menu to a user like the following and enclose it into a loop that ends when the Quit option is chosen.
## Display the square of all numbers from 1-100
## Enter a word
## Enter Midterm scores and calculate average.
## Quit
# For choice 1, use a '''for''' loop, and using a single variable, your output should be similar to:
#: Square of 1 is 1
#: Square of 2 is 4
# For choice 2, scanf a string, change the entire string to uppercase letters and print it out. Then, change the entire string to lowercase letters and print it out.
# For choice 3, first, ask how many midterms there are (maximum of 5), and then ask the score for each midterm, and print out the average score on the screen. If the user enters more than 5, inform the user that it is not a valid entry, and re-prompt the user to enter the number of midterms again.
# When the Quit option is chosen, end the primary loop that contains the menu.

=== Sample Code ===
<syntaxhighlight lang="c">
#include <ctype.h> // This file needed for tolower() or toupper() functions

int main(void)
{
int option = 0;
do {
printf("1. Menu item 1\n");
printf("2. Menu item 2\n");
printf("3. Quit\n");

if(1 == option) {
// do something here
}
else if(2 == option) {
// do something else here
}
} while(option != 3);
}
</syntaxhighlight>