Dual Interface Engine Control Data Transmission

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The existing data transmission methods between engine control devices and development tools in the automotive sector face bandwidth limitations during the development phase, leading to potential delays and misinterpretation of malfunctions, especially when using the CAN protocol, which is not suitable for high-bandwidth applications.

Innovation Solution

Implementing a dual communication interface system, where a first interface (e.g., asynchronous serial interface) is used during development for high-speed unidirectional data transfer with the development tool, and a second interface (e.g., CAN bus) is used for bidirectional communication with function units, allowing for a switch between protocols based on transmission needs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If the CAN protocol is used for data transmission between the control device and development tool, then bidirectional communication and fault tolerance are achieved, but the protocol overhead significantly restricts the available bandwidth

Engineering Contradiction:
Improvefault toleranceVSAvoiddata transmission bandwidth
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The communication system is segmented into two distinct interfaces: a first interface (e.g., USB, serial) dedicated to high-speed data transfer with the development tool during the development phase, and a second interface (CAN bus) for bidirectional communication with function units. This segmentation allows each interface to be optimized for its specific purpose without compromising the other.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The control device is designed with multi-functionality to handle different communication needs through different interfaces. The first interface serves dual purposes: high-speed data transfer during development and can be repurposed for CAN communication after development, demonstrating adaptability and universal design.

Inventive Principle:
Principle #6Universality (Multi-functionality)

2Productivity

If a second interface (e.g., USB or Fire-Wire) is provided for communication with the development tool, then larger transmission capacity is achieved without impairing real-time response, but the cost increases significantly

Engineering Contradiction:
Improvedata transmission capacityVSAvoidhardware cost
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The system dynamically adapts its communication configuration based on the operational phase. During the development phase, the first interface is configured for high-speed data transfer with the development tool. After development, the same interface can be reconfigured for CAN communication, providing flexibility and eliminating the need for permanent dual hardware configurations.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The first interface (e.g., USB) is temporarily dedicated to development purposes and then discarded from its development function, being recovered and repurposed for CAN communication. This approach eliminates the need to maintain separate dedicated hardware for development, reducing overall system cost.

Inventive Principle:
Principle #34Discarding and recovering

3Productivity

If the available bandwidth on the CAN bus is exhausted by communication with function units, then sufficient transmission capacity is no longer available for communication with the development tool, but assigning high priority to development tool communication compromises real-time response requirements

Engineering Contradiction:
Improvedata transmission to development toolVSAvoidreal-time response
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The communication burden is segmented between two interfaces: the CAN bus handles real-time communication with function units, while the first interface (USB/serial) handles high-volume data transfer with the development tool. This segmentation eliminates the need to prioritize development tool communication on the CAN bus, preserving real-time response reliability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS8065464B2Method for transmitting data from and to a control device
Publication Date: 2011.11.22 ROBERT BOSCH GMBH
  • US8065464B2 patent drawing
  • US8065464B2 patent drawing
  • US8065464B2 patent drawing

AI summary

A method for transmitting data from and to a control device, in particular an engine control device for a motor vehicle that has a first communication interface and a second communication interface, the method having the following steps: connecting the first communication interface to a development tool, and connecting the second communication interface to one or more function units during the development phase of the control device, transmitting data from the control device to the development tool via the first communication interface using a first communication protocol, transmitting data from the development tool to the control device via the first communication interface using the first communication protocol, breaking the connection between the first communication interface and the development tool, connecting the first communication interface to one or more additional 20 function units, and transmitting data between the control device and the other function unit or function units via the first communication interface using a second communication protocol.