Pebli
Skill Set Development - Electrical engineering, control system design, Arduino, Arduino IDE, SolidWorks, 3D printing, automotive industry expertise
Project Role - Lead Design/Testing Engineer, Business Plan Developer
The Big Idea
A single-source system that creates manufacturer, service provider, and end-user benefits through a proactive automotive on-board diagnostics platform.
The Facts
Since 1996, nearly every car sold in the USA contains an OBDII port, which is linked to the on-board diagnostics (OBD) computer. All information on mileage, emissions, speed, and other systems of a given vehicle that is gathered by the central diagnostics computer can be relayed via this 16-pin dock.
Though the automotive industry has seen significant technological advancement, typical end-users are still relatively unaware of their car’s systems performance, and a lack of interpretable clarity when car issues arise means that end-consumers are at the service provider’s mercy when the check engine light comes on.
Local dealerships and repair shops alike struggle to maintain business throughout a car’s life, as competitive market landscapes between vendors and challenging service differentiation can drive down profitability as well as customer engagement.
Vehicle manufacturers’ are always searching to derive meaningful design and marketing feedback from both qualitative customer response and quantitative vehicle performance. However, once the car is sold, the manufacturer’s interaction with the customer and vehicle significantly decline, with little leeway to gain the information that could significantly contribute to future business decisions and vehicle design.
The Development
Microcontroller Hardware Design
Arduino was chosen as the ideal prototyping platform, as their IDE software is open-sourced and modular parts for prototype construction were readily available. The prototype goal was to have a full-stack microcontroller unit that could connect to OBDII port, inquire for and consume vehicle diagnostic codes, merge/match codes to vehicle code database, generate relevant translated codes, and output translated code information.
For proof-of-concept simplicity, the prototype distributed codes via cellular network to a chosen mobile phone number.
Arduino evolution shown below.
Hardware Case Design
A minimum-tolerance case was designed using SolidWorks, and then printed using a MakerBot 3D printer, in order to provide safe handling and protection for the Arduino unit.
3D-printed case progress shown below.
Software Development
Native Arduino IDE software platform was used to develop functions that connected to vehicle on-board computer, extracted OBD codes, and translated codes into readable text for cellular network distribution.
Iterative prototype design proved successful in a relatively short time period, though further goals of a cloud-based manufacturer codes database were not fully realized within the scope of this project.
The Results
Minimum Viable Product
The full-stack Pebli microcontroller unit was tested on a 1997 Toyota Corolla with a displayed “Check Engine” light on, so as to ensure that error codes already existed within the on-board diagnostics computer. In the first test, the product successfully called codes from the OBDII port, processed the codes into readable format, and transmitted codes via text message to a cell phone, thus proving the prototype’s success.
Business Plan Framework
The framework of the Pebli platform value proposition is a three-pronged approach, based on client-type.
End-user (vehicle owner)
OBDII code export: precise or “most likely” interpretations of on-board diagnostics error codes - clarity of vehicle issues to customer, protection against being taken advantage of from repair shops
Connection to local dealerships, repair shops, and parts providers based on interpreted vehicle OBD codes (example: error codes of engine overheating and fan system not running, link to fan parts/modules based on vehicle type and local service providers that specialize in vehicle type)
Discount codes for sponsored shop parts/labor
Dealerships / Repair Shops
Expanded touch points with customers to drive engagement
With customer opt-in, dealership/repair shop notified when customer’s car issues error codes, ability to follow up with customer to generate remote point of sale
Ability to generate discount codes or other service initiatives to motivate intelligent customer retention
Vehicle error code metadata can aid in inventory management, client base retention, effectiveness of marketing/advertising campaigns, market demand analysis, etc…
Manufacturers
Vehicle error code metadata can aid in design/performance feedback
Qualitative customer response input can clarify brand perception, customer satisfaction