Universal J2534 Diagnostic Device for Multi-Protocol ECU Reprogramming
Find Innovative SolutionsGenerate 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 for different protocols, which complicates aftermarket services and increases costs for technicians.
Innovation Solution
The implementation of a cloud-based system using a J2534 compliant hardware device with a SAE J1962 OBDII connector, enabling universal communication functions across various communication protocols, and a web-based application for remote access and software updates, allowing technicians to diagnose and reprogram ECUs efficiently through a unified platform.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple diagnostic devices are used for different communication protocols, then compatibility with various ECUs is improved, but device complexity and cost increase
Solution Approach 1:
The patent implements a universal diagnostic device that supports multiple communication protocols (ISO9141, ISO14230, J1850, CAN, ISO15765, SAE J2610, and J1939) through a single unit. The device incorporates a protocol selection interface that allows users to choose the appropriate protocol, enabling one device to perform the functions previously requiring multiple separate devices, thereby resolving the contradiction between protocol compatibility and device complexity
Solution Approach 2:
The patent introduces a standard interface layer between the diagnostic device and various ECUs that handles protocol translation and conversion. This intermediary mechanism allows the single diagnostic device to communicate with ECUs using different protocols by mediating the communication through standardized functions, thus achieving multi-protocol support without requiring multiple specialized devices
2Device complexity
If a single universal diagnostic device is used, then device complexity is reduced, but communication compatibility with different protocols may be compromised
Solution Approach 1:
The diagnostic device incorporates dynamic protocol selection capability where the communication protocol can be changed based on the specific ECU being diagnosed. The device includes a protocol selection interface that allows users to dynamically switch between different protocols (ISO9141, ISO14230, J1850, CAN, ISO15765, SAE J2610, and J1939), enabling the single device to adapt to different communication requirements without compromising compatibility
Solution Approach 2:
The patent implements parameter changes in the communication interface by allowing the diagnostic device to modify its communication parameters (protocol type, baud rate, data format) based on the target ECU. This parameter adaptability ensures that the single universal device can maintain full compatibility with different protocols by dynamically adjusting its operational parameters rather than being fixed to a single protocol
3Adaptability or versatility
If technicians service all vehicles with multiple protocol devices, then service coverage is improved, but technician workload and training requirements increase
Solution Approach 1:
The diagnostic device incorporates automatic protocol detection and selection capabilities that reduce the need for technician intervention in protocol configuration. The system can automatically identify the appropriate protocol for the connected ECU and configure communication parameters accordingly, thereby reducing technician workload while maintaining comprehensive service coverage across different vehicle protocols
Solution Approach 2:
By providing a single universal diagnostic device that handles all major communication protocols (ISO9141, ISO14230, J1850, CAN, ISO15765, SAE J2610, and J1939), the system enables technicians to service all vehicle types with one device rather than requiring multiple specialized devices. This universality simplifies technician workflows and reduces training requirements while expanding service coverage to include all protocol types
Data Source
AI summary
Disclosed are methods, systems, and apparatus for the monitoring and maintenance of an automotive controller using a local device, a display device, a third-party device, a fleet-manager device, a technician device, and an administrative server. The local device is connected to the automotive controller and is wirelessly connected to the display device. The local device is connected to the technician device, and fleet manager device through an administrative server. The local device logs vehicle data generated by the automotive controller, and driver data input into display device. The third-party device may access HOS and RODs located on the local device through the display device. The fleet manager device receives vehicle and driver data through the administrative server and may allow remote repair by a technician device.