S19: Lightfury

From Embedded Systems Learning Academy
Revision as of 03:19, 14 March 2019 by Proj user16 (talk | contribs) (Schedule)

Jump to: navigation, search

Project Title

LightFury

Abstract

LightFury is an autonomous electric car that takes GPS location as a destination from an Android smartphone application and navigates with the help of sensors (sonar, compass) to the provided coordinates. The car uses SJOne boards based on LPC 1758 Microcontrollers. This page is a represents design report for the project.

Introduction

The project was divided into 7 modules:

  • Master Controller
  • Motor Controller
  • Sensor Controller
  • GPS Controller
  • Android application and Bluetooth Connectivity
  • Hardware (PCB designing)
  • Testing

Team Members & Responsibilities

<Team Picture>

Project Gitlab

<Provide ECU names and members responsible> <One member may participate in more than one ECU>


Schedule

Week# Start Date Task Status Completion Date
1 02/12/2019
  • Form Teams and decide group name. Also look up past projects and learn about the autonomous car design.
Completed 02/12/2019
2 02/19/2019
  • Setup Gitlab
  • Order CAN Transceivers. Study CAN communication.
  • Commit and raise merge request by each member to get hold over Gitlab basics
Completed 02/19/2019
3 02/26/2019
  • Setup Gitlab master branch for Project Light Fury. Create and merge branches for development tracking.
Completed 02/26/2019
4 03/05/2019
  • Read previous projects, gather information and discuss among the group members.
  • Distribute modules to each team member.
  • Divide the applications in different module for independent development.
  • Identify the baseline application.
Completed 03/09/2019
5 03/12/2019
  • Identify components required for the project
  • Allocated budget for the project
  • Order Components
In Progress 03/19/2019
5 03/19/2019
  • Sensor: Perused the datasheet to get started with development
  • GPS: Went through the datasheet and circuitry details for GPS module(no.)
  • Compass & LCD: Read the respective datasheets and manuals
  • Motor: Getting hold of the specification and the user manuals
  • Android: Design the basic template of the Application
  • BLE: Thorough understanding of the module
Planned 03/26/2019
6 03/26/2019
  • Sensor: Successful interfaced ultrasonic/Lidar with LPC to get raw data
  • GPS: Successful interfaced ultrasonic/Lidar with LPC to get raw data
  • Compass & LCD: Successful interfacing between Compass and Lidar
  • Motor: Basic motor controlled vehicle orientation
  • Android: Interfacing with other modules
  • BLE: Successful interfaced BLE module with LPC to get raw data
  • Unit-testing for each module
Planned 04/02/2019
7 04/02/2019
  • ----SPRING BREAK-----
Completed 04/09/2019
8 04/09/2019
  • Sensor: Parsed the raw data to achieve useful data
  • GPS: Parsing of raw data to get meaningful values
  • Compass & LCD: Integrating GPS co-ordinates with the compass to display on LCD
  • Motor: Speed control and angle control precision testing
  • Android: Adding each module functionality and status indicators
  • BLE:
Planned 04/16/2019
9 04/16/2019
  • Sensor: Parsed the raw data to achieve useful data
  • GPS: Parsing of raw data to get meaningful values
  • Compass & LCD: Integrating GPS co-ordinates with the compass to display on LCD
  • Motor: Speed control and angle control precision testing
  • Android: End-to-end testing with other modules
  • BLE:
Planned 04/23/2019
10 04/23/2019
  • Sensor: Parsed the raw data to achieve useful data
  • GPS: Parsing of raw data to get meaningful values
  • Compass & LCD: Integrating GPS co-ordinates with the compass to display on LCD
  • Motor: Speed control and angle control precision testing
  • Android: End-to-end testing with other modules
  • BLE:
  • Master: Interfacing all modules together
Planned 04/30/2019

Parts List & Cost

Item# Part Desciption Vendor Qty Cost
1 RC Car Traxxas 1 $250.00
2 CAN Transceivers MCP2551-I/P Microchip [1] 8 Free Samples
3 Semtec GPS Microchip [2] 8 Free Samples

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>



Conclusion

<Organized summary of the project>

<What did you learn?>

Project Video

Project Source Code

Advise for Future Students

<Bullet points and discussion>

Acknowledgement

References