Delete-me - Revision history

146 user11: 146 user11 moved page F16: Alexa Assisted Robot to Delete-me: extra page.

2017-01-17T19:46:34Z

146 user11 moved page F16: Alexa Assisted Robot to Delete-me: extra page.

146 user11: Blanked the page

2017-01-17T19:45:52Z

Blanked the page

146 user11: /* Schedule */

2016-11-12T05:15:33Z

‎Schedule

146 user11: /* Schedule */

2016-11-12T05:13:53Z

‎Schedule

146 user11: /* Schedule */

2016-11-12T05:12:23Z

‎Schedule

146 user11: /* Schedule */

2016-11-12T05:05:07Z

‎Schedule

146 user11: /* Schedule */

2016-11-12T04:47:08Z

‎Schedule

146 user11: /* Team Members & Responsibilities */

2016-11-11T19:51:22Z

‎Team Members & Responsibilities

146 user11: 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..."

2016-11-11T19:50:45Z

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

New page

=== Grading Criteria ===
<font color="green">
* How well is Software & Hardware Design described?
* How well can this report be used to reproduce this project?
* Code Quality
* Overall Report Quality:
** Software Block Diagrams
** Hardware Block Diagrams
**: Schematic Quality
** Quality of technical challenges and solutions adopted.
</font>

== Project Title ==

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

← Older revision		Revision as of 19:45, 17 January 2017
Line 1:		Line 1:
−	~~=== Grading Criteria ===~~
−	~~<font color="green">~~
−	* How well is Software & Hardware Design described?
−	* How well can this report be used to reproduce this project?
−	* Code Quality
−	* Overall Report Quality:
−	** Software Block Diagrams
−	** Hardware Block Diagrams
−	**: Schematic Quality
−	** Quality of technical challenges and solutions adopted.
−	~~</font>~~

−	~~== Project Title ==~~
−
−	~~== 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 ===~~
−	* Sanjay Agarwal
−	**
−	* Mason Itkin
−	**
−
−	~~== 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"\| Task Description~~
−	~~! scope="col"\| Result~~
−	\|-
−	~~! scope="row"\| 1~~
−	~~\| 10/21~~
−	~~\| Rough System Design~~
−	~~\| - Raspberry Pi3 to run Amazon Alexa~~
−	~~- SJSUOne Board used to control car motors~~
−	~~\|Complete~~
−	\|-
−	~~! scope="row"\| 2~~
−	~~\| 10/28~~
−	~~\| Parts Order (pt. 1)~~
−	~~\| Raspberry Pi3 + microphone + SD Card (plans to order screen/case and car parts at a later date)~~
−	~~\|Complete~~
−	\|-
−	~~! scope="row"\| 3~~
−	~~\| 11/4~~
−	~~\| Create group organizational structure~~
−	~~\| Start Github repo and Trello board~~
−	~~\|Complete~~
−	\|-
−	~~! scope="row"\| 4~~
−	~~\| 11/11~~
−	~~\| Start Alexa Dev.~~
−	~~\| - NOOBs Loaded onto rPi3~~
−
−	~~- Skill deployment location created on AWS Lambda~~
−
−	~~\|Complete~~
−	\|-
−	~~! scope="row"\| 5~~
−	~~\| 11/18~~
−	~~\| Implement Alexa basic functionality~~
−	~~\| - All basic voice interactions~~
−
−	~~- Communication from lambda function to rPI3~~
−
−	~~\|Complete~~
−	\|-
−	~~! scope="row"\| 6~~
−	~~\| 11/25~~
−	~~\| Parts Order (pt. 2)~~
−	~~\| - Chassis/Mechanical Parts~~
−	~~- DC Motors~~
−
−	~~- Accelerometer~~
−
−	~~- Hardware Sensors~~
−	~~\|Incomplete~~
−	\|-
−	~~! scope="row"\| 7~~
−	~~\| 12/2~~
−	~~\| Start Robot Dev.~~
−	~~\| - Build robot car~~
−	~~- Ensure sensors work with SJSUOne Board~~
−	~~\|Incomplete~~
−	\|-
−	~~! scope="row"\| 8~~
−	~~\| 12/9~~
−	~~\| Implement Alexa functionality with Robot~~
−	~~\| Ensure that Alexa commands are able to work with the robot car~~
−	~~\|Incomplete~~
−	\|-
−	~~! scope="row"\| 9~~
−	~~\| 12/16~~
−	~~\| Test the Alexa Assisted Robot~~
−	~~\| Ensure that the project's functionality passes all tests to prepare for presentation~~
−	~~\|Incomplete~~
−	\|-
−	~~! scope="row"\| 10~~
−	~~\| 12/20~~
−	~~\| Project Presentation~~
−	~~\| Present our final version of the Alexa Assisted Robot to the class~~
−	~~\|Incomplete~~
−	\|}
−
−	~~== 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.~~

@@ Line 59: / Line 59: @@
 | Start Alexa Dev.
 | - NOOBs Loaded onto rPi3
   - Skill deployment location created on AWS Lambda
 |Complete
 |-
@@ Line 66: / Line 68: @@
 | Implement Alexa basic functionality
 | - All basic voice interactions
- - Communication from lambda function to rPI3
 |Complete
 |-

@@ Line 59: / Line 59: @@
 | Start Alexa Dev.
 | - NOOBs Loaded onto rPi3
-- Skill deployment location created on AWS Lambda
+ - Skill deployment location created on AWS Lambda
 |Complete
 |-
@@ Line 78: / Line 78: @@
 - Hardware Sensors
 |-
 ! scope="row"| 7
@@ Line 84: / Line 85: @@
 | - Build robot car
 - Ensure sensors work with SJSUOne Board
 |-
 ! scope="row"| 8
@@ Line 89: / Line 91: @@
 | Implement Alexa functionality with Robot
 | Ensure that Alexa commands are able to work with the robot car
 |-
 ! scope="row"| 9
@@ Line 94: / Line 97: @@
 | Test the Alexa Assisted Robot
 | Ensure that the project's functionality passes all tests to prepare for presentation
 |-
 ! scope="row"| 10
@@ Line 99: / Line 103: @@
 | Project Presentation
 | Present our final version of the Alexa Assisted Robot to the class
 |}

@@ Line 33: / Line 33: @@
 ! scope="col"| Date
 ! scope="col"| Task
-! scope="col"| Results
+! scope="col"| Task Description
 |-
 ! scope="row"| 1
@@ Line 40: / Line 41: @@
 | - Raspberry Pi3 to run Amazon Alexa
 - SJSUOne Board used to control car motors
 |-
 ! scope="row"| 2
 | 10/28
 | Parts Order (pt. 1)
-| Raspberry Pi3 ordered with plans to order screen/case and car parts at a later date
+| Raspberry Pi3 + microphone + SD Card (plans to order screen/case and car parts at a later date)
 |-
 ! scope="row"| 3
@@ Line 50: / Line 53: @@
 | Create group organizational structure
 | Start Github repo and Trello board
 |-
 ! scope="row"| 4
@@ Line 56: / Line 60: @@
 | - NOOBs Loaded onto rPi3
 - Skill deployment location created on AWS Lambda
 |-
 ! scope="row"| 5
 | 11/18
 | Implement Alexa basic functionality
-| -
+| - All basic voice interactions
 |-
 ! scope="row"| 6

@@ Line 30: / Line 30: @@
 {| class="wikitable"
 |-
-! scope="col"| Week#
+! scope="col"| Week
 ! scope="col"| Date
 ! scope="col"| Task
@@ Line 38: / Line 38: @@
 | 10/21
 | Rough System Design
-| - Raspberry Pi3to run Amazon Alexa
+| - Raspberry Pi3 to run Amazon Alexa
 - SJSUOne Board used to control car motors
 |-
@@ Line 61: / Line 61: @@
 | Implement Alexa basic functionality
 | -
 |}

← Older revision	Revision as of 19:46, 17 January 2017
(No difference)

@@ Line 20: / Line 20: @@
 === Team Members & Responsibilities ===
-*  Yaron Alexandrovich
+*  Sanjay Agarwal
 **
 == Schedule ==