Debuggy

Team Name

 OBD-II

Timeline

Summer 2022 – Fall 2022

Students

  • Leonardo Hernandez
  • Chance Huddleston
  • Zain Khan
  • Nicholas Kinney
  • Zaky Qalawi

Abstract

The project is a tool to interface with your car’s diagnostic computer. It will allow users to view and clear their diagnostic codes. Individual queries can be sent as well

Background

The goal of this project was to make a tool to maintain your car with. It intends to have a web client user interface, and a raspberry pi serving both the website and a restful interface for the OBD-II reader. The goal is to give the DIY community pre-made tools to tinker with their cars and their computers, along with documentation to ensure that they can use everything.

Project Requirements

  • Must be FLOSS (Freely Licensed Open Source Software)
  • Must interface with standard OBD-II port
  • Must expose a client through a web interface
  • Must be runnable on a raspberry pi
  • Must have documentation for building/running
  • Must have the ability to schedule jobs
  • Must have the ability to interface with a database
  • Must have a way to submit issues and pull requests
  • Must have a logging capability
  • Must have documentation for debugging the software

System Overview

Results

Ultimately we were able to get the live system monitoring portion of the backend working, and the frontend and middleware required for getting the information to the user is working as well.

Future Work

The repository will be made public and licensed such that anyone can fork it and improve on it. This will allow future work to be done by anyone interested, and for any features that are missing to be added. The primary missing feature is the ability to read and clear the DTCs, the codes which prompt your check engine light.

Project Files

Project Charter (link)

System Requirements Specification (link)

Architectural Design Specification (link)

Detailed Design Specification (link)

Poster (link)

nak7009