CAN Bus Error Logging via Ethernet Bridge
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional error logging systems for CAN buses require multiple diagnostic devices to be physically connected to each bus, leading to increased costs and complexity, especially in large systems where error detection and logging across multiple buses become cumbersome.
Innovation Solution
Implementing an error logging mechanism that uses an Ethernet bridge to remotely collect and encapsulate error information from CAN buses into IEEE 1722a frames, allowing a single error logging device to log errors from multiple buses via an Ethernet network, reducing the need for multiple physical connections.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a diagnostic device is physically connected to each CAN bus to detect errors, then error detection reliability is improved, but device complexity and cost increase significantly
Solution Approach 1:
An Ethernet bridge is introduced as an intermediary device that connects multiple CAN buses to a single remote error logging device. The bridge receives error information from multiple CAN controllers, encapsulates it in Ethernet frames, and forwards it to the logging device, thereby reducing the number of physical connections needed while maintaining error detection capability.
Solution Approach 2:
The error logging device is designed to handle errors from multiple CAN buses simultaneously through a single connection. By implementing a universal logging mechanism that can process error frames from any connected CAN bus, the system eliminates the need for dedicated logging devices for each bus, reducing overall system complexity.
2Reliability
If multiple error logging devices are deployed for multiple CAN buses, then error logging coverage is improved, but cost increases
Solution Approach 1:
Multiple error logging functions are merged into a single remote error logging device. The device consolidates error information from multiple CAN buses by receiving encapsulated error frames through the Ethernet network, eliminating the need for multiple separate logging devices while maintaining comprehensive error coverage.
Solution Approach 2:
The Ethernet bridge acts as a mediator that aggregates error information from multiple CAN controllers and forwards it to a single logging device. This intermediary function allows one logging device to serve multiple buses, reducing the quantity of logging devices required.
3Measurement precision
If physical connections are made from each CAN bus to a logging device, then error detection accuracy is improved, but ease of operation deteriorates
Solution Approach 1:
Physical mechanical connections (wires and ports) are replaced with an Ethernet network-based communication system. Error information is transmitted digitally through the network infrastructure using standardized Ethernet frames, eliminating the need for complex physical wiring while preserving error detection accuracy through reliable digital communication.
Data Source
AI summary
Embodiments described herein provide a method for an error logging mechanism operated with controller area network (CAN) buses within an Ethernet network. A first interrupt request indicative of a first error condition that occurs at the first CAN bus is received at an Ethernet bridge and from a first CAN controller connected to a first CAN bus. In response to the first interrupt request, the first interrupt request is serviced by retrieving, from a first error register at the first CAN controller, information relating to the first error condition. The information relating to the first error condition is encapsulated in a first frame in compliance with a layer 2 transport protocol for time-sensitive applications. The encapsulated first frame is then sent, via an Ethernet switch, to an error logging device installed at a location remote to the first CAN bus.