Difference between revisions of "S19: Tech Savy"

From Embedded Systems Learning Academy
Jump to: navigation, search
(→‎Design & Implementation)
(→‎Introduction)
Line 28: Line 28:
 
* Bridge Controller
 
* Bridge Controller
 
* Android Application
 
* Android Application
 +
 +
===Objective===
  
 
=== Team Members & Responsibilities ===
 
=== Team Members & Responsibilities ===

Revision as of 21:31, 2 April 2019

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

TECH SAVY

Abstract

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

Introduction

The project is divided into 7 modules:

  • Master Controller
  • LCD Controller
  • Sensor Controller
  • Motor Controller
  • Geographical Controller
  • Bridge Controller
  • Android Application

Objective

Team Members & Responsibilities

<Team Picture>

Gitlab Project Link - [1]

Technical Responsibilities

  • Master Controller
    • Aakash Chitroda
    • Halak Vyas
  • LCD controller (UI)
    • Vidushi Jain
    • Aakash Chitroda
  • Sensors Controller
    • Halak Vyas
    • Aakash Chitroda
  • Motor Controller
    • Vatsal Makani
    • Jay Parsana
  • Geographic Controller
    • Vidushi Jain
    • Prashant Gandhi
  • Bluetooth Controller
    • Jay Parsana
    • Saumil Shah
    • Akshata Kulkarni
  • Android 
    • Saumil Shah
    • Akshata Kulkarni
  • Hardware Integration PCB
    • Prashant Gandhi
    • Vatsal Makani
  • CAN Communication
    • Halak Vyas
    • Akshata Kulkarni

Administrative Roles

  • Finance Manager
    • Aakash Chitroda
  • Wiki Report Manager
    • Halak Vyas
    • Vidushi Jain
  • Component Purchase Manager
    • Vatsal Makani
    • Jay Parsana
  • Git Repository Manager
    • Vatsal Makani

Schedule

Show a simple table or figures that show you're 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.

Week Start Date End Date Task Details Status
1 26 Feb 2019 4 March 2019
  • Create and establish GitLab repository
  • Establish slack channel and invite Preet
  • Look through previous years projects and study it
  • Distribute major roles among team members
 Completed
Completed
Completed
Completed
2 05 March 2019 12 March 2019
  • Create a Bill of Materials.
  • Select and order an RC car.
  • Make Repo on Gitlab for all modules - Follow Naming Convention.
 Completed
Completed
Completed
3 13 March 2019 19 March 2019
  • Select Part Number for Sensors (Halak, Akash)
  • Designing and deciding PCB tool(Prashant, Vatsal)
  • Finalizing GPS module by doing some research (Vidushi)
  • Finalize and order LCD (Akash, Vidushi)
  • Finalize Motor and Order it (Vatsal)
  • Environmental setup of Android (Saumil)
 Completed
Completed
Completed
Completed
Completed
Completed
4 20 March 2019 26 March 2019
  • Understand DBC and implement the DBC file compatible with all the controllers.
  • Finish motor controller API. Test motor driving in different situations, begin to listen to CAN for controls.
  • Establish communication across all the CAN controllers over CAN bus based on the DBC file.
  • Verify the power-up interactions and configurations between Master and the other controllers.
  • 03/26/2019 DBC File
  • 03/26/2019 DEMO: CAN communication between controllers
 Completed
Completed
Completed
Completed
Completed
Completed
5 27 March 2019 08 April 2019
  • Check and Resolve power issue for RC Car.
  • Finalize high-level system block diagram and control scheme.
  • Circuit Simulation in Proteus Tool
  • PCB Layout Design in Diptrace Tool
  • Finalize Components placement on PCB
  • Establish a connection over Bluetooth and Android app.
  • Establish a communication between Bluetooth devices.
  • Interfacing of ultrasonic sensors to the SJOne board and check for basic functionality.
  • Configure GPS device baud rate and interface it with SJOne board using UART.
  • Chalk out the Message IDs based on the priority of the messages and the data to be sent across nodes.
  • Interface of Servo & DC motor to the SJOne board and check for basic functionality.
  • Interface Compass module with SJOne board using I2C serial bus.
  • Interface Compass module with SJOne board using I2C serial bus.
  • Explore UI designing of LCD.
 In Progress
6
7
8

Parts List & Cost

Item# Part Desciption Vendor Qty Cost
1 RC Car - Traxxas 1/10 Slash 2WD Amazon 1 $229
2 Traxxas 2872X 5000mAh 11.1V 3S 25C LiPo Battery [2] 1 $69.95
3 Traxxas 7600mAh 7.4V 2-Cell 25C LiPo Battery Amazon 1 $74.95
4 Traxxas 2970 EZ-Peak Plus 4-Amp NiMH/LiPo Fast Charger Amazon 1 $49.95
5 Bluetooth Module HC-05 Amazon 1 $8.49
6 4D systems 32u LCD 4D systems 1 $79.00
7 LV Maxsonar EZ0 Ultrasonic sensors Robotshop 5 $134.75
8 LIDAR Sensor [3] 1 $100
9 GNSS Taoglas GPS Antenna From Taoglas Vendor 1 Free
10 CAN tranceivers Microchip Samples 10 Free
11 SJOne Boards Provided by Preet 5 $400.0
12 CMPS11 Compass DFRobot 1 $29.90
13 RPM Sensor Amazon 1 $10.0
14 1000C PowerBoost Board Adafruit 2 $40.0
15 3.7v Li-Po Battery Adafruit 2 $30.0

Total cost: $900.94

Printed Circuit Board

<Picture and information, including links to your PCB>

CAN Communication

<Talk about your message IDs or communication strategy, such as periodic transmission, MIA management etc.>

Hardware Design

<Show your CAN bus hardware design>

DBC File

<Gitlab link to your DBC file> <You can optionally use an inline image>



Sensor ECU

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Unreliable sonor sensors

<Problem Summary> <Problem Resolution>


Motor ECU

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Unreliable Servo Motors

<Problem Summary> <Problem Resolution>


Geographical Controller

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Unreliable GPS lock

<Problem Summary> <Problem Resolution>


Communication Bridge Controller & LCD

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Insane Bug

<Problem Summary> <Problem Resolution>


Master Module

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Improper Unit Testing

<Problem Summary> <Problem Resolution>



Mobile Application

<Picture and link to Gitlab>

Hardware Design

Software Design

<List the code modules that are being called periodically.>

Technical Challenges

<Bullet or Headings of a module>

Wifi Link Reliability

<Problem Summary> <Problem Resolution>


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 the 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 the exact code, but you may show pseudocode and fragments of code. Keep in mind that you are showing the DESIGN of your software, not the inner workings of it.


TechSavy High Level Software Architecture

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

Testing & Technical Challenges

Describe the challenges of your project. What advise would you give yourself or someone else if your project can is started from scratch again? Make a smooth transition to the testing section and described what it took to test your project.

Include sub-sections that list out a problem and solution, such as:

<Bug/issue name>

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

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=S19:_Tech_Savy&oldid=52085"