View source for F16: Spartan and Furious

== 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 ==
*  Android and Communication Bridge:
** [http://www.linkedin.com/in/manali-deshmukh-a8a33994 Manali Deshmukh]<br>
*  Geographical Controller:
** [http://linkedin.com/in/sreeharshagorantla Harsha Gorantla]<br>
** [http://www.linkedin.com/in/shauryajai Shaurya Jain]<br>
*  Master Controller:
** [http://www.linkedin.com/in/ankita151 Ankita Singhal]
** [http://www.linkedin.com/in/sukriti-choudhary-16550b104 Sukriti Choudhary]<br>
*  Motor Controller
** [http://www.linkedin.com/in/srinivasanshilpa Shilpa Srinivasan]<br>
*  Sensor and I/O Controller:
** [http://www.linkedin.com/in/bhushanmuthiyan Bhushan Muthiyan]<br>
** [http://www.linkedin.com/in/kparameswaran Karthik Parameswaran]<br>

== Schedule ==
Legend <font color="blue"> Motor Controller <font>,<font color="clouds"> Master Controller <font>,<font color="green"> Android Controller<font>,<font color="CARROT"> Geo Controller,<font color="orange"> Sensor and I/O Controller <font>, <font color="black"> Team Goal <font> 
{| class="wikitable"
|-
! scope="col"| Week#
! scope="col"| Date
! scope="col"| Task
! scope="col"| Actual
! scope="col"| Status
|-
! scope="row"| 1
| 9/17/2016
|
* Purchasing RC car.
| 
* Purchased RC car.
| Complete
|-
! scope="row"| 2
| 9/24/2016
|
* Individual module distribution
* Project report setup
* Git setup
* Order components for individual modules
| 
* Members identified for modules
* Wikipage project report template and Git were setup
* Ordered GPS module and CAN transceivers
| Complete
|-
! scope="row"| 3
| 10/01/2016
|
* Define scope of each module
* Determine Git flow
* Follow up on component procurement
*<font color="blue"> Determining and analyzing the duty cycle for servomotor and DC motor of the car.
</font>
*<font color="clouds">Implement basic CAN communication CAN between two SJ-One Boards</font>

| 
* Initial flow of each module defined
* Identified the branches and decided on merge process
* Ordered additional ultrasonic sensors and LCD
| Complete
|-
! scope="row"| 4
| 10/08/2016
|
* Create branches in Git
* Follow up on component procurement
*<font color="blue"> Basic testing of Servo and DC motor.<br></font>
*<font color="blue"> Testing speed of car with variable PWM.</font>
*<font color="clouds">Research on the CAN bus, tasks and scheduling.<br></font>
* <font color="clouds">Decision regarding flow of the master controller.</font>
| 
*Created Master branch on Git
*All ordered parts received on 10/07
| Complete
|-
! scope="row"| 5
| 10/15/2016
|
* <font color="blue"> Developing drivers for both motors. </font>

* <font color="blue"> Testing the car with developed drivers. </font>

*<font color="green">Android app prototype</font>

*<font color="CARROT"> Parse GPS data and format the data to be transmitted</font>

* <font color="CARROT">Test code to get compass reading information</font>

*<font color="clouds">Decision making regarding Node address and message ID's for CAN controller.</font>

*<font color="orange">Design basic sensor algorithm for obstacle detection. </font>

*<font color="orange">Download software for LCD. </font>

| 
*Created Master branch on Git
*All ordered parts received on 10/07
| Complete
|-
! scope="row"| 6
| 10/22/2016
|
*Prepare CAN DBC file
* <font color="blue"> Establishing basic CAN communication.<br> </font>

* <font color="blue"> Interfacing with Master Controller with Motor.</font>

*<font color="green">Interface Bluetooth module with SJ-One board </font>

* <font color="CARROT">Interfacing GPS and compass to SJ-One board</font>

*<font color="clouds">Interfacing master controller with Sensor Controller module.</font>

* <font color="orange">Design layout for LCD screen</font>

* <font color="orange">Mount ultrasonic sensor on car and test it. </font>

| 
| 
|-
! scope="row"| 7
| 10/29/2016
|
*Designing of CAN hardware.
*Testing and debugging.
* <font color="blue"> Fine tuning motor control code.</font>

*<font color="green">Transmitting and receiving messages between Android App and SJ-One board.</font>

*<font color="CARROT"> Initial Algorithm development of GPS module for distance calculation</font>

* <font color="CARROT">Establishing basic CAN communication</font>

* <font color="clouds">Basic interfacing of master controller with motor module.</font>

*<font color="orange">Establishing basic CAN communication. </font>

*<font color="orange"> Integrate IR sensor for gauging speed. </font>

| 
| 
|-
! scope="row"| 8
| 11/05/2016
|
*Integration of modules for first demo.
* <font color="blue"> Testing and debugging.</font>

*<font color="green">Testing and debugging.</font>

* <font color="CARROT">Collaborating with other modules for first demo</font>

*<font color="clouds">Interface with the motor and Sensor module for the first demo.</font>

* <font color="clouds">Testing and debugging.</font>

*<font color="orange"> Collaborating with other modules for first demo. </font>

* <font color="orange">Fine-tuning algorithms for sensor and IR. </font>

| 
| 
|-
! scope="row"| 9
| 11/12/2016
|
*<font color="blue"> Design of Feedback Control mechanism for car.</font>

*<font color="green">Establishing CAN communication with peripheral modules.</font>

* <font color="CARROT">Algorithm for distance and heading calculation-H</font>

* <font color="CARROT">Coding and Calibration of GPS module</font>

*<font color="clouds">Interface of master controller with GPS module.</font>

* <font color="clouds">Develop kill switch mechanism.</font>

*<font color="orange">Develop LCD code for displaying all sensor information and car vitals. </font>

*<font color="orange">Decide upon additional I/O such as lights. </font>
| 
| 
|-
! scope="row"| 10
| 11/19/2016
|
* <font color="blue"> Speed synchronization of car using IR sensor and testing.</font>

*<font color="green">Enhancing UI of the Android App.</font>

* <font color="CARROT">Coding and Calibration of GPS module</font>

* <font color="CARROT">Individual Unit Testing</font>

*<font color="clouds">Develop heartbeat mechanism to check health of each of the modules.</font>

*<font color="clouds"> Integrate master controller with android module.</font>

*<font color="orange">Integrate sensor and I/O code. </font>

*<font color="orange">Facilitate Motor module to test with IR sensor. </font>

| 
| 
|-
! scope="row"| 11
| 11/26/2016
|
*Testing and debugging for second demo.

* <font color="green">Interfacing with GPS module and testing.</font>

* <font color="CARROT">Integration of GPS and compass modules</font>

*<font color="CARROT"> Interfacing GPS with Android, Master and IO controllers</font>

*<font color="clouds">Integration of I/O module. </font>

|
| 
|-
! scope="row"| 12
| 12/03/2016
|
* <font color="blue"> Fine tuning, debugging and integration. </font>

*<font color="green">Final integration, testing and debugging.</font>

* <font color="CARROT">Complete System Testing</font>

*<font color="clouds">Fine tuning, debugging and integration.</font>

|
| 
|-
! scope="row"| 13
| 12/10/2016
|
*Final Testing and fine tuning 
*Report preparation
| 
| 
|-
|}

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

== ECUs ==
== Motor Controller ==
==== Group Members ====
*'''''[http://www.linkedin.com/in/srinivasanshilpa Shilpa Srinivasan]<br> '''''

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

== Android and Communication Bridge ==
==== Group Members ====
*'''''[http://www.linkedin.com/in/manali-deshmukh-a8a33994 Manali Deshmukh]<br> '''''

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

==Geographical Controller==
==== Group Members ====
*'''''[http://linkedin.com/in/sreeharshagorantla Harsha Gorantla]<br> '''''
*'''''[http://www.linkedin.com/in/shauryajai Shaurya Jain]<br> '''''

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

==Sensor and  I/O ==
==== Group Members ====
*'''''[http://www.linkedin.com/in/bhushanmuthiyan Bhushan Muthiyan]<br> '''''
*'''''[http://www.linkedin.com/in/kparameswaran Karthik Parameswaran]<br>'''''

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

== Master Controller ==
==== Group Members ====
*'''''[http://www.linkedin.com/in/ankita151 Ankita Singhal]<br> '''''
*'''''[http://www.linkedin.com/in/sukriti-choudhary-16550b104 Sukriti Choudhary]<br> '''''

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

== 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://gitlab.com/ankitas/spartan_and_furious Gitlab 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.