Bidirectional Interface Pinout for Additional Transceiver Data
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current automotive systems, such as those using CAN, LIN, and FlexRay protocols, face challenges in exchanging additional data like functional safety data between transceivers and microcontrollers without modifying the standardized pinout or implementing protocol controllers, as existing methods rely on bus idle detection and require hardware changes.
Innovation Solution
A system and method that enable additional bidirectional communication between transceivers and microcontrollers using an additional pin and associated IO cell, allowing for serial or parallel data transmission without modifying the pinout, and without the need for a protocol controller, by employing additional data handling circuitry and switch devices to manage different communication modes.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If additional pins are used for additional communication between transceiver and microcontroller, then communication functionality is improved, but pinout standardization is violated
Solution Approach 1:
The patent applies multi-functionality by enabling existing standardized pins to serve dual purposes: traditional communication functions and additional communication functions. The transceiver and microcontroller use mode indication signals to switch between different communication modes (first communication and second communication) over the same pinout, allowing one pin to perform multiple functions without violating standardization.
Solution Approach 2:
The patent implements dynamic switching between communication modes using mode indication signals. The system can dynamically transition from first communication to second communication and back, allowing the communication interface to adapt its functionality in real-time based on operational needs, rather than being fixed to a single mode.
2Ease of operation
If protocol controllers are implemented for additional communication, then communication control is improved, but device complexity is increased
Solution Approach 1:
The patent extracts the protocol control functionality from dedicated hardware protocol controllers and implements it through software or firmware logic in the microcontroller. The mode indication mechanism and communication switching are handled through logical operations rather than complex hardware controllers, reducing hardware complexity while maintaining communication control capabilities.
Solution Approach 2:
The patent replaces mechanical/hardware-based protocol control with software/firmware-based control. Instead of using dedicated protocol controller hardware, the system uses programmable logic and software routines to manage communication modes, switch between protocols, and handle data transmission, thereby reducing hardware complexity.
3Device complexity
If existing communication interfaces are used for additional data transmission, then hardware overhead is reduced, but data transmission reliability is compromised
Solution Approach 1:
The patent applies preliminary action by establishing clear mode indication protocols before actual data transmission begins. The system uses predefined mode indication signals to negotiate and confirm the communication mode in advance, ensuring both devices are synchronized and ready for reliable data transmission without requiring additional hardware for mode negotiation.
Solution Approach 2:
The patent introduces mode indication signals as intermediaries that facilitate reliable communication over existing interfaces. These intermediary signals carry metadata about the communication mode, allowing the receiving device to properly interpret and process incoming data according to the correct protocol, thereby maintaining reliability without additional dedicated data channels.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
Disclosed is a first communication device (200) for transmitting and receiving regular data via a first predetermined regular bidirectional interface (201), respectively, to and from a second communication counterpart device (250), and for transmitting and receiving additional data via a first predetermined additional bidirectional interface (221), respectively, to and from the second communication counterpart device (250). The device (200) has a predetermined pinout comprising a predetermined regular pinout (202, 206), which corresponds to the predetermined regular bidirectional interface (201) configured to support regular bidirectional communication of regular data with the second communication counterpart device (250), and a predetermined additional pinout (220) comprising at least one additional pin (220), which corresponds to the predetermined additional bidirectional interface (221) configured to support additional bidirectional communication of additional data with the second communication counterpart device (250). The device (200) has: (i) a first additional default data handling circuitry (228), which is communicatively coupled to the additional pin (220), and which is configured to transmit and receive additional default data via the additional pin, when a default mode is active; and (ii) a first additional function data handling circuitry (230), which is communicatively coupled to the additional pin (220), and which is configured to transmit and receive additional function data via the additional bidirectional interface (221), when an additional function mode is active.