Embedded System Adapter with Programmable XCP Interface Layer
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Developing adapters for connecting embedded systems to control computers is complex and costly, especially for older control units or those with less common microcontrollers, due to the need for individual interface development and compliance with protocols like XCP, which requires significant time and resources.
Innovation Solution
An adapter is designed with two subcircuits: a first subcircuit that implements a standard protocol like XCP and remains permanently configured, and a second subcircuit that is programmable and adaptable, allowing users to implement specific elementary functions using a programmable logic device and user-writable memory, reducing the need for full protocol implementation and enabling flexible configuration.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If a dedicated adapter is developed for each individual control unit with less common microcontroller, then compatibility with that specific control unit is achieved, but development time and cost increase significantly
Solution Approach 1:
The adapter is designed with a standardized interface architecture that can work with multiple different control unit types. The first subcircuit implements a universal standard protocol (XCP) that serves as a common communication layer, while the second subcircuit provides configurable adaptability to specific control units through programmable logic devices. This universal design allows the same adapter hardware to support various control unit models without requiring dedicated development for each type.
Solution Approach 2:
The adapter is divided into two distinct subcircuits: a first subcircuit that handles the standardized protocol implementation and a second subcircuit that provides control unit-specific interfacing. This segmentation allows the standardized portion to be developed once and reused, while only the specific interfacing portion needs adaptation for different control units, significantly reducing overall development time.
2Reliability
If full protocol implementation is implemented in the adapter, then complete protocol functionality is achieved, but device complexity and resource requirements increase
Solution Approach 1:
The protocol implementation is extracted and separated into a dedicated first subcircuit that handles only the standard protocol layer. This extraction allows the complex protocol functionality to be isolated and managed independently, while the second subcircuit focuses solely on the simpler task of interfacing with the control unit. This separation reduces the complexity burden on any single component.
Solution Approach 2:
The first subcircuit acts as an intermediary layer between the control computer and the second subcircuit. It translates and handles the complex protocol requirements, presenting a simplified interface to the second subcircuit. This intermediary approach allows complete protocol functionality to be achieved without requiring the entire adapter to be designed for maximum complexity.
3Ease of manufacture
If standardized protocol interface is used for all control units, then development cost is reduced, but compatibility with older or specialized control units may be compromised
Solution Approach 1:
The adapter implements different levels of specialization at different locations: the first subcircuit maintains uniform standardized protocol handling across all applications, while the second subcircuit provides localized adaptation to specific control unit requirements. This local quality approach allows cost-effective standardized manufacturing for the majority of the adapter while providing targeted compatibility enhancements where needed.
Data Source
AI summary
An adapter for connecting an embedded system to a control computer having a standard interface, in particular a network interface, a first subcircuit, and a second subcircuit, the first subcircuit being designed to communicate with the control computer via the standard interface by means of a standard protocol, preferably XCP. The first subcircuit is designed to convert a protocol functionality requested in the standard protocol via the standard interface, out of a set of supported protocol functionalities into the call for one or more elementary functions out of a defined overall set of elementary functions. The first subcircuit is connected to the second subcircuit via an internal interface, wherein the second subcircuit has a programmable computing module which is configured to provide at least one elementary function out of the overall set of elementary functions which can be called up via the internal interface by means of a call.