CAN-CANFD Bridge Synchronizing Frame End Timing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The incompatibility between Classical CAN and CAN-FD protocols causes errors and communication disruptions when CAN-C controllers receive CAN-FD messages, making it challenging to integrate CAN-FD modules with existing Classical CAN systems without significant redesign and validation, which is time-consuming and costly.
Innovation Solution
A bridge or filter device is used to detect CAN-FD frames and convert them into Classical CAN frames, preventing error flags and delays by synchronizing the end of CAN-FD and mimicked CAN-C frames using overload frames, allowing CAN-FD modules to operate with older CAN-C modules with reduced error occurrences.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If a filter is inserted to intercept CAN-FD communications before they reach CAN-C modules, then CAN-C modules are protected from receiving incompatible frames, but this causes either error messages or delays that interfere with communication arbitration
Solution Approach 1:
The patent introduces a bridge device as an intermediary component between CAN-FD and CAN-C modules. This bridge translates CAN-FD frames into CAN-C compatible frames, allowing seamless communication without requiring filters that would disrupt arbitration. The bridge acts as a mediator that converts the high-speed CAN-FD protocol into the classical CAN protocol, enabling CAN-C modules to communicate with CAN-FD modules without direct exposure to incompatible frame formats.
Solution Approach 2:
The bridge device creates a copy of the CAN-FD communication stream and translates it into CAN-C compatible format. By copying and transforming the frame data rather than directly filtering CAN-FD frames from the bus, the system maintains the original CAN-FD communication integrity while providing a translated version for CAN-C modules, avoiding arbitration interference.
2Productivity
If CAN-FD modules are integrated into existing Classical CAN systems, then communication speed and data capacity are improved, but this causes error conditions and communication disruptions due to protocol incompatibility
Solution Approach 1:
The bridge device serves as an intermediary that enables high-speed CAN-FD communication while maintaining stability for CAN-C modules. It translates CAN-FD frames into CAN-C compatible format, allowing CAN-C modules to operate reliably without directly encountering incompatible high-speed frames, thus preserving communication stability while enabling productivity improvements.
Solution Approach 2:
The bridge device changes the protocol parameters of CAN-FD frames to match CAN-C specifications. It transforms the frame format, bit rate, and other parameters to be compatible with classical CAN modules, enabling high-speed communication capability while maintaining reliable operation for legacy modules through parameter adaptation.
3Adaptability or versatility
If CAN-C controllers directly receive CAN-FD messages, then protocol compatibility is maintained, but this causes unrecoverable Error conditions
Solution Approach 1:
The bridge device acts as an intermediary that maintains protocol compatibility by translating CAN-FD frames into CAN-C format. This allows CAN-C controllers to receive and process messages from CAN-FD modules without directly encountering incompatible frame structures, thereby maintaining adaptability while ensuring error-free operation through protocol transformation.
Data Source
AI summary
A filter or bridge device allows CAN-FD modules to communicate on a communication bus having classic CAN modules without generating error modules by sensing for CAN-FD frames. In response to detecting a CAN-FD frame, the filter or bridge device sends a mimic classic CAN message or frame instead of the original CAN-FD frame to classic CAN modules. An additional feature may include the filter or bridge device adding bits such as CAN overload frames onto the CAN-FD frame, mimicked classic CAN frame, or both to have the two messages end at about a same time to avoid timing errors when the modules begin to send new message frames.