Project
| # | Title | Team Members | TA | Documents | Sponsor |
|---|---|---|---|---|---|
| 100 | Driving Habits Feedback Module |
Anna Sako Elijah Sutton James Tang |
Lukas Dumasius | ||
| # Title Team Members: - Elijah Sutton (esutton3) - James Tang (jhtang2) - Anna Sako (sako2) # Problem According to the Department of Energy a simple change in habits can effect fuel economy by 10%-40% which translates to $0.38-$1.53/gallon saved! https://www.energy.gov/energysaver/driving-more-efficiently Although many drivers are concerned with fuel efficiency and eco-friendly driving, it is often difficult to understand the specific impact of driving habits on emissions. Especially in older vehicles, actionable driving feedback is limited and counter-intuitive. # Solution My idea is a small OBDII compatible module that can be retrofit into nearly any vehicle that collects driving data such as throttle, RPM, and speed. This data then be used to infer other data such as transmission state and braking. Collectively this data can be fed live into a lightweight ML model that classifies different driving styles and mistakes before relaying the data to the driver via a distraction-free LED display (RGB strip). The driver can then use this feedback to adjust their driving habits in an intuitive way and achieve the emissions savings that are possible. # Solution Components ## Subsystem 1 The first subsystem of the design is a PCB that is powered by and interfaces with the OBDII port in a car. This board would use the 12V chassis power stepped down with a buck. It would also use a CAN transceiver to communicate with the ECM of the car to collect data. The MCU on the board would control all communications enough and host a lightweight ML model. ## Subsystem 2 The second subsystem is a distraction-free intuitive LED display that provides the driver with feedback. It needs to be convenient enough to add to the dash of any car, discrete enough to not be distracting, and intuitive enough to give the driver actionable information. This piece of the device defines the entire user experience and is a potential source of danger if it becomes distracting; it is very important to be designed with lots of thought. ## Subsystem 3 The last subsystem is all software. After the MCU collects the data, it needs to process it in order to inform the display. We will start with a threshold / rule-based algorithm that classifies the drivers habits and provides feedback. This will then be developed into a lightweight ML model where improvements can be made. # Criterion For Success In order to be effective, this project will collect driving data via OBDII port, control the LED display, and be a self contained power system. At the highest level, this project will be deemed successful if we can improve the vehicles reported fuel-economy for a given trip based on feedback from the device. |
|||||