Project Advising: Vehicle Display with CAN Interface

From Embedded Systems Learning Academy
Revision as of 00:15, 2 March 2014 by Spa user4 (talk | contribs) (→‎Status)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search

This is your wiki page that you can edit and will serve as a method of communication between us. Every week, you should add a quick status of what work got accomplished, and share any problem(s) you may encounter.


Abstract

Cars are complex vehicles with many intricate and advanced computer systems. They provide a wealth of data and information on a vehicle's status and condition. There is a need for access to the information reported by these computer systems. Many companies offer solutions of devices that can interface with the vehicle and interpret the data. Currently Griffin offers a bluetooth enabled device that plugs into an OBD II port on the car and interfaces with an android/iOS app to display check engine codes and vehicle readiness. It also features an SD card for logging relevant vehicle data.

The objective of this project is to deliver an in-vehicle controller that relays diagnostic information to an Android application. The in-vehicle controller will interface with the vehicle via the CAN bus, collect and store relevant data retrieved from this bus into it’s own storage. It will make this data available via a wireless uplink to an android application. The android application will interface with the controller via a wireless connection, display real time vehicle information retrieved from the CAN bus, and allow the display of logged data stored on the controller.

The automotive repair industry has needs for both quick access to a vehicle CAN bus as well as a history of the mechanical operation of the car. A log of engine data allows mechanic to diagnose and repair intermittent issues that they are unable to reproduce. The project will allow quick diagnosis of mechanical problems though a wireless interface to the CAN bus. Additionally the controller will give a mechanic vehicle history by logging engine data. This project will require the use of PCB design, CAN bus, embedded CPU software and hardware design, and Android application development.



Status

Roadblocks & Problems

  • Item 1
  • Item 2

Done Goals

  • Get MCP2551 prototype board ready.
  • Get LPC1758 board and dev. environment ready

Next Goals

  • Establish communication with car
  • Establish Bluetooth communication with board


September 16

  • Purchase SJone Board
  • Obtain signed abstract
  • Register senior project

September 9

  • Finish Abstract

March 1

  • Board done
  • Continue work on CAN drivers and Android App

March 14

-Communicate with Car

Retrieved from "http://socialledge.com/sjsu/index.php?title=Project_Advising:_Vehicle_Display_with_CAN_Interface&oldid=5603"