Remote ECU Reprogramming Through J2534 OBDII Protocol Mediation
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 is inefficient for technicians and increases costs.
Innovation Solution
A cloud-based system that uses a J2534 compliant hardware device connected via a SAE J1962 OBDII connector, allowing communication with any vehicle ECU regardless of protocol through universal functions, enabling remote access and updates via a client device, technician device, and server, facilitating standardized emissions-related services.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple diagnostic devices are used for different communication protocols, then compatibility with various vehicle systems 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, J1939) through a single integrated system. The device uses a standardized hardware interface (SAE J1962 OBDII connector) combined with software-based protocol handling, allowing one physical device to perform functions that previously required multiple separate devices. This resolves the contradiction by achieving protocol compatibility through multi-functional software rather than through multiple separate hardware devices.
2Adaptability or versatility
If multiple diagnostic devices are used for different communication protocols, then coverage of vehicle systems is improved, but technician efficiency deteriorates
Solution Approach 1:
The diagnostic device provides comprehensive vehicle system coverage through a single unified interface. Technicians interact with one standardized SAE J1962 OBDII connector and a single device that automatically handles protocol selection and communication, eliminating the need to switch between multiple specialized devices. This improves technician efficiency by reducing device switching time and simplifying the diagnostic workflow while maintaining full vehicle system coverage through multi-protocol support.
Solution Approach 2:
The patent introduces a standardized hardware interface (SAE J1962 OBDII connector) as an intermediary between the diagnostic device and various vehicle communication protocols. This intermediary layer handles protocol-specific communication details, allowing the main diagnostic system to operate universally across different protocols without requiring protocol-specific hardware variations. This mediator approach enables full vehicle system coverage while maintaining technician efficiency through a unified interface.
3Reliability
If protocol-specific diagnostic devices are used, then communication reliability for specific protocols is improved, but system complexity increases
Solution Approach 1:
The SAE J1962 OBDII connector serves as a standardized intermediary interface that separates the diagnostic device from protocol-specific communication requirements. The hardware interface remains constant and reliable, while protocol-specific communication handling is managed through software layers that translate between the standardized interface and various vehicle protocols. This mediator architecture maintains communication reliability for each protocol while avoiding the complexity of having separate hardware devices for each protocol.
Data Source
AI summary
Disclosed are methods, systems, and apparatus for remote reprogramming of an automotive controller using J2534 communications protocol, a local device, a client device, a technician 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 technician device through a system server. Programming configurations, including firmware, settings, and parameter updates, are selected from a technician device, sent to the system server, and uploaded to local device using J2534 communication protocol. The client device receives reprogramming data from the system server and sends the reprogramming data to the local device.