Third-Party OBD II Detection to Prevent CAN Bus Conflicts
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing OBD II compliant devices can interfere with vehicle diagnostics by sending conflicting data requests on the CAN bus, leading to communication conflicts and abnormal ECU behavior.
Innovation Solution
A monitoring device listens to electronic messages on the CAN bus to detect and address third-party devices, modifying its own messages based on detected addresses and learned models to avoid redundant requests.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If multiple OBD II devices are connected to the CAN bus simultaneously, then device versatility and data collection capability are improved, but communication conflicts and diagnostic interference occur
Solution Approach 1:
The monitoring device performs preliminary detection of the CAN bus environment before initiating data requests. It listens to electronic messages exchanged on the bus, detects third-party devices by analyzing their addresses, and monitors their request patterns in advance. This preliminary action allows the system to predict potential conflicts and adjust its communication strategy proactively, preventing communication conflicts before they occur.
Solution Approach 2:
The system continuously monitors the CAN bus for electronic messages, detects third-party device addresses and request patterns, and uses this feedback information to dynamically modify its own communication behavior. The monitoring device adjusts its data request timing and content based on real-time observations of third-party device activity, creating a closed-loop control system that adapts to the bus environment and maintains reliable communication.
2Measurement precision
If a service tool is used to diagnose vehicle problems, then diagnostic accuracy is improved, but the process requires uninstalling aftermarket devices and manual reconnection
Solution Approach 1:
The monitoring device acts as an intermediary on the CAN bus, intelligent enough to detect when a service tool is present and actively communicating with the ECU. It monitors the bus for service tool activity and automatically pauses or adjusts its own data requests to avoid interfering with diagnostic operations. This intermediary role allows the system to maintain both diagnostic accuracy and operational convenience without requiring physical disconnection of devices.
3Productivity
If devices send data requests back-to-back without coordination, then data collection speed is improved, but communication conflicts and ECU response failures occur
Solution Approach 1:
The monitoring device performs preliminary monitoring of third-party device request patterns and timing before sending its own requests. By analyzing the timing of requests from other devices on the bus, it can identify gaps and optimal moments to transmit data requests without causing conflicts, thus maintaining both high data collection efficiency and protocol compliance.
Solution Approach 2:
The system uses periodic monitoring and adaptive timing adjustments based on observed third-party device patterns. It collects data at optimized intervals that respect ECU response times and avoid overlapping requests, balancing data collection efficiency with reliable communication through the CAN bus.
Data Source
AI summary
Embodiments of the disclosure provide for detecting and avoiding conflicts with a device on a communications bus. According to one embodiment, avoiding redundant or conflicting communications can comprise listening to electronic messages exchanged on the communications bus and detecting a second device a second device communicating on the communications bus based on the electronic messages exchanged on the communication bus. The electronic messages can comprise requests for data and responses to the requests for data. For example, the communications bus can comprise a Controller Area Network (CAN) bus within a vehicle and the first device and the second device can comprise On-Board Diagnostic (OBD) II devices. Detecting the second device communicating on the communications bus can comprise detecting an address used by the second device.