Universal Diagnostic Device for Multi-Protocol ECU Communication

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The automotive industry faces challenges in standardizing communication protocols for diagnosing and reprogramming engine control units (ECUs), leading to a need for multiple diagnostic devices and hindering efficient carbon emission reduction efforts.

Innovation Solution

A cloud-based system utilizing a J2534 compliant hardware device with a SAE J1962 OBDII connector, enabling communication across various ECU protocols through a unified application and API, allowing for remote diagnostics, updates, and carbon offset calculations.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If multiple diagnostic devices are used to support different communication protocols, then compatibility with various ECUs is improved, but device complexity increases

Engineering Contradiction:
Improveprotocol compatibilityVSAvoidnumber of diagnostic devices
Core Design Contradiction:
Adaptability or versatilityVSDevice complexity

Solution Approach 1:

The patent implements a universal diagnostic device that can communicate with multiple ECU types through different communication protocols (CAN, LIN, FlexRay, Ethernet). The system uses a single hardware platform with integrated protocol handlers and a unified API layer, eliminating the need for multiple specialized diagnostic tools while maintaining full protocol compatibility.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent introduces an intermediary software layer (unified API and protocol translator) that sits between the hardware interface and the diagnostic applications. This intermediary handles protocol-specific communication details and presents a standardized interface to users, allowing a single device to support multiple protocols without requiring separate specialized tools for each protocol.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Measurement precision

If traditional diagnostic methods are used for carbon emission monitoring, then existing infrastructure is maintained, but efficiency and accuracy of carbon offset calculations deteriorate

Engineering Contradiction:
Improvecarbon emission measurement accuracyVSAvoidcarbon offset calculation efficiency
Core Design Contradiction:
Measurement precisionVSProductivity

Solution Approach 1:

The patent replaces manual carbon emission monitoring and calculation processes with automated electronic systems. The ECU continuously monitors emission-related parameters (fuel injection quantity, air intake, exhaust gas composition) and automatically transmits this data through the diagnostic interface to a processing system that calculates carbon offsets, eliminating manual measurement and calculation methods.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The system enables the ECU and diagnostic device to automatically perform carbon emission monitoring, data transmission, and offset calculations without requiring external manual intervention. The integrated system self-manages the entire carbon accounting process from data collection through to certification, improving both accuracy and efficiency.

Inventive Principle:
Principle #25Self-service

Data Source

PatentUS11210874B2System and method for calculation and communication of carbon offsets
Publication Date: 2021.12.28 EZ LYNK SEZC
  • US11210874B2 patent drawing
  • US11210874B2 patent drawing
  • US11210874B2 patent drawing

AI summary

Disclosed are methods, systems, and apparatus for determining, and reporting vehicle carbon emissions using a local device, a client device, and a system server. The local device is connected to the automotive controller and is wirelessly connected to the client device. The client device is connected to the system server. The local device receives engine data from the automotive controller and determines and stores fuel consumption over a period of time. The client device receives the fuel consumption data from the local device and sends the data to the system server. The system server determines the carbon emissions based on the fuel consumption and reports the emissions data to a third-party to certify carbon offset.