Difference between revisions of "F16: The-Nine"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Team Members & Responsibilities)
Line 83: Line 83:
 
== Parts List & Cost ==
 
== Parts List & Cost ==
 
Give a simple list of the cost of your project broken down by components.  Do not write long stories here.
 
Give a simple list of the cost of your project broken down by components.  Do not write long stories here.
−
=== Schedule ===
 
  
 
{| class="wikitable"
 
{| class="wikitable"
Line 106: Line 105:
 
|}
 
|}
  
−
== Design & Implementation ==
+
 
 +
 
 +
 
 +
 
 +
== Bluetooth Communications ==
 +
 
 +
=== Schedule ===
 +
 
 +
{| class="wikitable"
 +
|-
 +
! scope="col"| Task #
 +
! scope="col"| Start Date
 +
! scope="col"| End Date
 +
! scope="col"| Task Description
 +
! scope="col"| Status
 +
! scope="col"| Actual End Date
 +
|-
 +
! scope="row"| 1
 +
| 9/14/2016
 +
| 9/20/2016
 +
| Research Project Components and Read Previous Reports
 +
| Completed
 +
|
 +
|-
 +
! scope="row"| 2
 +
| 9/21/2016
 +
| 9/27/2016
 +
| Set up Version Control System and Basic Project Documentation
 +
| Completed
 +
|
 +
|-
 +
! scope="row"| 3
 +
| 9/28/2016
 +
| 10/04/2016
 +
| Order Project Components and Discuss Project Implementation
 +
| Completed
 +
|
 +
|-
 +
! scope="row"| 4
 +
| 10/05/2016
 +
| 10/19/2016
 +
| Individual Prototyping and Module Design
 +
| Completed
 +
|
 +
|-
 +
! scope="row"| 5
 +
| 10/20/2016
 +
| 10/27/2016
 +
| Status Update: Demoing first round of Prototyping to the group
 +
| In Progress
 +
|
 +
|-
 +
! scope="row"| 6
 +
| 10/28/2016
 +
| 11/18/2016
 +
| Adding a level of complexity to designs: Interfacing Motor, Sensor, GPS, and BLE Modules with the Master Controller over CAN bus
 +
| In Progress
 +
|
 +
|}
 +
 
 +
=== 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.
 +
 
 +
 
 +
== Application & Control Interface ==
 +
 
 +
=== 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.
 +
 
 +
 
 +
 
 +
== Obstacle Detection Systems ==
 +
 
 +
=== 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.
 
The design section can go over your hardware and software design.  Organize this section using sub-sections that go over your design and implementation.
  
Line 121: Line 235:
 
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.
 
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 ==
+
=== 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?
 
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.
 
Make a smooth transition to testing section and described what it took to test your project.
Line 129: Line 243:
 
=== My Issue #1 ===
 
=== My Issue #1 ===
 
Discuss the issue and resolution.
 
Discuss the issue and resolution.
 +
 +
 +
 +
== Localization and Positioning (GPS) ==
 +
 +
=== 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.
 +
 +
 +
 +
== Propulsion Systems and Speed Tracking ==
 +
 +
=== 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.
 +
 +
 +
 +
== Master Control Systems ==
 +
 +
=== 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 ==
 
== 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?
 
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 ===
+
== Project Video ==
 
Upload a video of your project and post the link here.
 
Upload a video of your project and post the link here.
  
−
=== Project Source Code ===
+
== Project Source Code ==
 
*  [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]
 
*  [https://sourceforge.net/projects/sjsu/files/CmpE_S2016/ Sourceforge Source Code Link]
  

Revision as of 05:05, 19 October 2016

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.

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.

Schedule

Task # Start Date End Date Task Description Status Actual End Date
1 9/14/2016 9/20/2016 Research Project Components and Read Previous Reports Completed
2 9/21/2016 9/27/2016 Set up Version Control System and Basic Project Documentation Completed
3 9/28/2016 10/04/2016 Order Project Components and Discuss Project Implementation Completed
4 10/05/2016 10/19/2016 Individual Prototyping and Module Design Completed
5 10/20/2016 10/27/2016 Status Update: Demoing first round of Prototyping to the group In Progress
6 10/28/2016 11/18/2016 Adding a level of complexity to designs: Interfacing Motor, Sensor, GPS, and BLE Modules with the Master Controller over CAN bus In Progress

Team Members & Responsibilities

Application & Control Interface

  • Khalil Estell

Obstacle Detection Systems

  • Charles MacDonald
  • John Strube

Localization and Positioning (GPS)

  • Sara Sepasian

Propulsion Systems and Speed Tracking

  • Derek Tran

Master Control Systems

  • Steven Hwu
  • Adam Iglesias

Bluetooth Communications (BLE)

Propulsion Systems and Speed Tracking

  • Matthew Boyd

Parts List & Cost

Give a simple list of the cost of your project broken down by components. Do not write long stories here.

Item # Part Description Vendor QTY Cost
1 RC Car 1
2 SJSUOne Board Preet Kang 1 $80.00



Bluetooth Communications

Schedule

Task # Start Date End Date Task Description Status Actual End Date
1 9/14/2016 9/20/2016 Research Project Components and Read Previous Reports Completed
2 9/21/2016 9/27/2016 Set up Version Control System and Basic Project Documentation Completed
3 9/28/2016 10/04/2016 Order Project Components and Discuss Project Implementation Completed
4 10/05/2016 10/19/2016 Individual Prototyping and Module Design Completed
5 10/20/2016 10/27/2016 Status Update: Demoing first round of Prototyping to the group In Progress
6 10/28/2016 11/18/2016 Adding a level of complexity to designs: Interfacing Motor, Sensor, GPS, and BLE Modules with the Master Controller over CAN bus In Progress

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.


Application & Control Interface

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.


Obstacle Detection Systems

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.


Localization and Positioning (GPS)

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.


Propulsion Systems and Speed Tracking

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.


Master Control Systems

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

GitLab

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.

Retrieved from "http://socialledge.com/sjsu/index.php?title=F16:_The-Nine&oldid=28684"