Control system and network collaborative design tool chain
Through Pareto optimization design method and automation tool chain, the design problems of the electrical/electronic architecture of automotive systems under the network parameter limitation are solved, efficient and effective architectural design is achieved, cost and labor demand is reduced, and design and debugging process is simplified. .
Patent Information
- Application Number
- CN202311391170.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Priority Date
- 2023-05-08
- Filing Date
- 2023-10-24
- Publication Date
- 2024-11-08
AI Technical Summary
The electrical/electronic (E/E) architecture of existing automotive systems is difficult to design efficiently under network parameters limitations, resulting in increased development costs and complex design and debugging.
Using Pareto optimization design method, combining device models and control goals, generate multiple expected software controller combinations, explore Ethernet parameters, generate Pareto frontier and selected software controllers, optimize electrical/electronic architecture, and automated collaborative design Toolchain, reduce labor and disrupt existing workflows.
It realizes efficient and effective electrical/electronic architecture design, reduces development and commissioning costs, improves design efficiency, reduces labor demand, and simplifies the architecture conversion process.
Smart Images

Figure CN118915427A_ABST
Abstract
Description
Technical Field
[0001] The present disclosure relates to a control system and network collaborative design tool chain. Background Art
[0002] This Background Art generally presents the context of the present disclosure. No work by the presently designated inventors is admitted, either explicitly or implicitly, to be prior art to the present disclosure, to the extent it is described in this Background Art and insofar as it may not qualify as prior art at the time of filing.
[0003] Most automotive systems include an electrical / electronic (E / E) architecture. The EE architecture may be limited by network parameters. Therefore, it is useful to develop a method and system for designing an E / E architecture for an automotive system. Summary of the invention
[0004] The present application describes a method for designing an electrical / electronic architecture. The method includes receiving a system model of an automotive system, wherein the system model includes an initial electrical / electronic architecture; receiving a control objective of the automotive system; and designing a new electrical / electronic architecture using Pareto optimization based on the control objective and the system model. The method described in this paragraph improves the automotive system by producing an efficient and effective electrical / electronic architecture.
[0005] The system model includes a device model, and the device model can be expressed using the following equation: Where: t is time; is the time derivative of x(t); x(t) is a vector-valued function representing the state of the device at time t; u(t) is a vector-valued function representing the control input applied at time t; a is the state transition matrix; and b is the input matrix. The control objectives include rise time, settling time, and a quadratic function expressed as follows: J = ∫(x T Qx+u TRu)dt, j is the quadratic control cost; q is the cost coefficient matrix of state errors; r is the cost coefficient matrix of input errors; x is the state of the device; u is the control input; and t is time. Designing a new electrical / electronic architecture includes generating multiple expected software controllers for the device model, wherein each of the expected software controllers includes a sampling rate and a feedback gain value. Designing a new electrical / electronic architecture includes exploring a combination of multiple expected software controllers to control the device model and network (Ethernet) parameters using Pareto optimization, wherein the network parameters include packet priority, transmission delay, and buffer size. Designing a new electrical / electronic architecture includes generating a Pareto frontier of a selected software controller and selected Ethernet network parameters as a result of exploring a combination of multiple expected software controllers. Designing a new electrical / electronic architecture includes designing a new electrical / electronic architecture using the Pareto frontier of the selected software controller and the selected Ethernet network parameters.
[0006] The present disclosure also describes a tangible, non-transitory machine-readable medium including machine-readable instructions, which, when executed by a processor, cause the processor to perform the above method. The present disclosure also describes a system including a controller. The controller is programmed to perform the above method.
[0007] Further application areas of the present disclosure will become apparent from the detailed description provided below. It should be understood that the detailed description and specific examples are only for illustrative purposes and are not intended to limit the scope of the present disclosure.
[0008] The above features and advantages and other features and advantages of the presently disclosed systems and methods are apparent from the detailed description, including the claims and exemplary embodiments, taken in conjunction with the accompanying drawings. BRIEF DESCRIPTION OF THE DRAWINGS
[0009] The present disclosure will become more fully understood based on the detailed description and accompanying drawings, in which:
[0010] Figure 1 is a block diagram depicting an embodiment of a system for designing electrical / electronic architecture; and
[0011] Figure 2 Is a flow chart used to design electrical / electronic architecture. DETAILED DESCRIPTION
[0012] Reference will now be made in detail to several examples of the present disclosure illustrated in the accompanying drawings. Whenever possible, the same or similar reference numerals are used in the drawings and the description to refer to the same or similar parts or steps.
[0013] Figure 1A system or tool chain 10 for designing electrical / electronic (E / E) architectures is shown. The system 10 includes a controller or computing device 34, which includes at least one processor 44 and a non-transitory computer-readable storage device or medium 46. The processor 44 can be a custom or commercially available processor, a central processing unit (CPU), a graphics processing unit (GPU), an auxiliary processor of several processors associated with the controller 34, a semiconductor-based microprocessor (in the form of a microchip or chipset), a macroprocessor, a combination thereof, or generally a device for executing instructions. The computer-readable storage device or medium 46 can include volatile and non-volatile memory such as read-only memory (ROM), random access memory (RAM), and keep-alive memory (KAM). KAM is a permanent or non-volatile memory that can be used to store various operating variables when the processor 44 is powered off. The computer readable storage device or medium 46 may be implemented using a variety of storage devices, such as a PROM (programmable read only memory), an EPROM (electrical PROM), an EEPROM (electrically erasable PROM), flash memory, or other electrical, magnetic, optical, or combination storage device capable of storing data, some of which represents executable instructions used by the controller 34 in controlling the vehicle 10. The controller 34 of the vehicle 10 may be referred to as a vehicle controller and may be programmed to perform the method 100 ( Figure 2 ), as described in detail below.
[0014] The instructions may include one or more separate programs, each of which includes an ordered list of executable instructions for implementing logical functions. The instructions, when executed by the processor 44, perform logic, calculations, methods and / or algorithms. Figure 1 A single controller 34 is shown in FIG. 1 , but embodiments of the vehicle 10 may include multiple controllers 34 that communicate via a suitable communication medium or combination of communication mediums and cooperate to process sensor signals, execute logic, calculations, methods and / or algorithms, and generate control signals.
[0015] Toolchain 10 automates the co-design of control systems and underlying Ethernet architectures with minimal disruption to existing workflows. Toolchain 10 integrates with other design tools to produce abstract specifications. Toolchain 10 then solves a co-optimization problem to produce controller, processor scheduling, and Ethernet network parameter(s) configurations to best implement the system design. Toolchain 10 is an automated approach to exploring efficient designs, giving engineers a wider range of implementation options than is currently possible. Use of toolchain 10 will require less manpower than our current process.
[0016] Figure 21 is a flow chart of a method 100 for designing an (E / E) architecture. Some controllers are designed without considering the implementation of the architecture. This results in a model / implementation separation that is resolved in an iterative process using x-in the loop simulation and debugging. As automotive E / E architectures continue to evolve, the cost of this process is increasing. Therefore, it is desirable to address this issue by developing a tool chain that uses controller parameters and their associated implementation parameters (e.g., task mapping and scheduling) to co-design and automatically synthesize automotive E / E architectures. This will likely reduce design and debug effort and allow for an easier transition to E / E architectures.
[0017] The method 100 begins at block 102 and block 104. At block 102, the controller 34 receives a system model of an automotive system. The system model may be a model of a physical, tangible automotive system, such as a propulsion system (e.g., an electric motor) or a steering system of a vehicle. As a non-limiting example, the device model may be in the form of a linear differential equation. For example, the device model may be represented using the following equation:
[0018]
[0019] in:
[0020] t is time;
[0021] is the time derivative of x(t);
[0022] x(t) is a vector-valued function representing the state of the device (i.e., the physical system) at time t;
[0023] u(t) is a vector-valued function representing the control input applied at time t;
[0024] A is the state transition matrix; and
[0025] B is the input matrix.
[0026] The system model can include device models, the layout of the initial E / E architecture, and the layout of the hardware connections. The initial E / E architecture layout includes the Ethernet network parameters with constraints and the microprocessors where the software tasks of the control system will be executed. From the abstract model, the tool chain generates a real-time task model for the sensing, control, and actuation tasks on all relevant processors as well as the Ethernet network parameters and the expected mapping of tasks to processors.
[0027] At block 104, the controller 34 receives a control target for an automotive system (e.g., a propulsion system or a steering system of a vehicle). The control target may include a rise time, a settling time, and a quadratic function expressed as follows:
[0028] J = ∫(x T Qx+u T Ru)dt
[0029] J is the secondary control cost;
[0030] Q is the cost coefficient matrix of state errors;
[0031] R is the cost coefficient matrix of input errors;
[0032] x is the state of the device (i.e., the physical system);
[0033] u is the control input; and
[0034] t is the time.
[0035] The method 100 then proceeds to box 106. At box 106, the controller 34 stores a system description, which includes a system model and control objectives. The method 100 then proceeds to box 110.
[0036] At box 108, the controller (e.g., computing device) 34 uses Pareto optimization (i.e., multi-objective optimization) to design one or more software architectures (e.g., software controllers) for the physical system based on the system description. First, the controller 34 generates a set of expected controllers for each device model, which includes sampling rate and feedback gain values. Second, the controller 34 explores the combination of expected controllers that control all devices and Ethernet network parameters (including packet priority, transmission delay, and buffer size). Then, the method 100 continues to box 110. At box 110, the controller 34 determines whether the software controller (e.g., software architecture) meets the control goal. If the software controller does not meet the control goal, the method 100 returns to box 108. If the software controller meets the control goal, the method 100 continues to box 112.
[0037] At block 112, the controller 34 updates the Pareto front. The method 100 then proceeds to block 114. At block 114, the controller 34 determines whether more software controllers should be tested. If more software controllers should be tested, the method 100 returns to block 108. If no more software controllers need to be tested, the method 100 proceeds to block 116. At block 116, the controller 34 stores the updated Pareto front. The method 100 then proceeds to block 118.
[0038] At block 118, the controller (e.g., computing device) 34 designs another software architecture (e.g., software controller) for the physical system based on the system description. As described above, the system description includes a system model and a control objective. The controller 34 may design the software controller using Pareto optimization (i.e., multi-objective optimization). The method 100 then proceeds to block 120. At block 120, the controller 34 determines whether the software controller (e.g., software architecture) satisfies the control objective (i.e., is feasible). If the software controller does not satisfy the control objective, the method 100 returns to block 118. If the software controller satisfies the control objective, the method 100 proceeds to block 122.
[0039] At box 122, the controller 34 updates the Pareto front. Then, the method 100 continues to box 124. At box 124, the controller 34 determines whether more design combinations should be tested. If more design combinations should be tested, the method 100 returns to box 108. If there are no more design combinations to be tested, the method 100 proceeds to box 126. At box 126, the controller 34 stores the updated Pareto front. In other words, at box 126, the controller 34 returns the controller's Pareto front and the associated Ethernet network parameters on the space of control targets and network utilization. The controller 34 then selects a design solution and completes the controller design and Ethernet network parameter configuration (including partial network specifications) using the Pareto front and associated Ethernet network parameters of the selected software controller. Therefore, the controller 34 designs a new E / E architecture for the automotive system using the Pareto front and associated Ethernet network parameters of the selected software controller.
[0040] Although exemplary embodiments are described above, it is not intended that these embodiments describe all possible forms included in the claims. The words used in the specification are descriptive rather than restrictive, and it should be understood that various changes can be made without departing from the spirit and scope of the present disclosure. As previously mentioned, the features of the various embodiments can be combined to form another embodiment of the currently disclosed system and method that may not be explicitly described or shown. Although various embodiments may have been described as providing advantages or being superior to other embodiments or prior art implementations in terms of one or more desired characteristics, it is recognized by those of ordinary skill in the art that one or more features or characteristics may be compromised to achieve the desired overall system properties, depending on the specific application and implementation. These properties may include, but are not limited to, cost, strength, durability, life cycle cost, marketability, appearance, packaging, size, applicability, weight, manufacturability, ease of assembly, etc. Therefore, embodiments described as being less ideal than other embodiments or prior art implementations in terms of one or more features are not outside the scope of the present disclosure and may be ideal for specific applications.
[0041] The accompanying drawings are in simplified form and are not drawn to exact scale. Directional terms such as top, bottom, left, right, above, over, above, below, below, rear, and front may be used with respect to the accompanying drawings for the purpose of convenience and clarity only. These and similar directional terms should not be construed as limiting the scope of the present disclosure in any way.
[0042] Embodiments of the present disclosure are described herein. However, it should be understood that the disclosed embodiments are merely examples, and other embodiments may take various alternative forms. The drawings are not necessarily drawn to scale; some features may be enlarged or reduced to show the details of specific components. Therefore, the specific structural and functional details disclosed herein should not be interpreted as limiting, but merely as a representative basis for teaching those skilled in the art to use the currently disclosed systems and methods in different ways. As will be understood by those of ordinary skill in the art, the various features shown and described with reference to any of the figures may be combined with the features shown in one or more of the other figures to produce embodiments that are not explicitly shown or described. The combination of features shown provides representative embodiments of typical applications. However, for specific applications or implementations, various combinations and modifications of features consistent with the teachings of the present disclosure may be required.
[0043] Embodiments of the present disclosure may be described in terms of functional and / or logical block components and various processing steps. It should be understood that such block components may be implemented by multiple hardware, software and / or firmware components, which are configured to perform specified functions. For example, embodiments of the present disclosure may employ various integrated circuit components, such as memory elements, digital signal processing elements, logic elements, lookup tables, etc., which may perform various functions under the control of one or more microprocessors or other control devices. In addition, those skilled in the art will appreciate that embodiments of the present disclosure may be practiced in conjunction with multiple systems, and the systems described herein are merely exemplary embodiments of the present disclosure.
[0044] For the sake of brevity, technologies related to signal processing, data fusion, signal transmission, control and other functional aspects of the system (as well as the various operating components of the system) may not be described in detail herein. In addition, the connecting lines shown in the various figures contained herein are intended to represent example functional relationships and / or physical couplings between the various elements. It should be noted that alternative or additional functional relationships or physical connections may exist in the embodiments of the present disclosure.
[0045] This description is merely illustrative in nature and is in no way intended to limit the present disclosure, its application, or uses. The broad teachings of the present disclosure can be implemented in many forms. Therefore, although the present disclosure includes specific examples, the true scope of the present disclosure should not be so limited, as other modifications will become apparent upon studying the drawings, the specification, and the appended claims.
Claims
1. A method for designing an electrical / electronic architecture, comprising: receiving a system model of an automotive system, wherein the system model includes an initial electrical / electronic architecture; receiving a control objective of a vehicle system; and Based on the control objective and the system model, a new electrical / electronic architecture is designed for the automotive system through Pareto optimization.
2. The method according to claim 1, wherein: The system model includes a device model, and the device model can be expressed using the following equation: in: t is time; is the time derivative of x(t); x(t) is a vector-valued function representing the state of the device at time t; u(t) is a vector-valued function representing the control input applied at time t; A is the state transition matrix; and B is the input matrix.
3. The method according to claim 2, wherein: The control objectives include rise time, settling time and a quadratic function expressed as follows: J=∫(x T Qx+u T Ru)dt J is the secondary control cost; Q is the cost coefficient matrix of state errors; R is the cost coefficient matrix of input errors; x is the state of the device; u is the control input; and t is the time.
4. The method according to claim 3, wherein: Designing the new electrical / electronic architecture includes generating a plurality of expected software controllers for the device model, wherein each of the expected software controllers includes a sampling rate and a feedback gain value.
5. The method according to claim 4, wherein: Designing the new electrical / electronic architecture includes exploring combinations of the plurality of contemplated software controllers to control the device models and Ethernet network parameters through the Pareto optimization, wherein the Ethernet network parameters include packet priority, transmission delay, and buffer size.
6. The method according to claim 5, wherein: Designing the new electrical / electronic architecture includes generating a Pareto front of selected software controllers and selected Ethernet network parameters as a result of exploring the combinations of the plurality of contemplated software controllers.
7. The method according to claim 6, wherein: Designing the new electrical / electronic architecture includes designing the new electrical / electronic architecture by selecting a Pareto front of a software controller and selecting Ethernet network parameters.
8. A tangible, non-transitory machine-readable medium comprising machine-readable instructions that, when executed by a processor, cause the processor to: A system model of a receiving vehicle system, where The system model includes an initial electrical / electronic architecture; receiving a control objective of a vehicle system; and Based on the control objective and the system model, a new electrical / electronic architecture is designed for the automotive system through Pareto optimization.
9. The tangible, non-transitory machine-readable medium of claim 8, wherein: The system model includes a device model, and the device model can be expressed using the following equation: in: t is time; is the time derivative of x(t); x(t) is a vector-valued function representing the state of the device at time t; u(t) is a vector-valued function representing the control input applied at time t; A is the state transition matrix; and B is the input matrix.
10. The tangible, non-transitory machine-readable medium of claim 9, wherein: The control objectives include rise time, settling time and a quadratic function expressed as follows: J=∫(x T Qx+u T Ru)dt J is the secondary control cost; Q is the cost coefficient matrix of state errors; R is the cost coefficient matrix of input errors; x is the state of the device; u is the control input; and t is the time.
