Chassis domain control system and vehicle
By designing a chassis domain control system in the vehicle chassis system, and using the chassis domain controller and sensors to jointly control each execution subsystem, the problem of difficulty in executing a system in the chassis system is solved, and the vehicle's handling performance and fluency are improved.
Patent Information
- Application Number
- CN202420043992.5
- Authority / Receiving Office
- CN · China
- Patent Type
- Utility models(China)
- Current Assignee / Owner
- Filing Date
- 2024-01-08
- Publication Date
- 2024-11-05
- Estimated Expiration
- 2034-01-08
AI Technical Summary
The execution system and software functions in the vehicle chassis system cannot be controlled in a coordinated manner, resulting in difficulty in coordination and poor functional coupling.
Design a chassis domain control system, including a chassis domain controller, independent sensors and execution subsystems, collect vehicle status signals through sensors, and the chassis domain controller calculates and transmits control instructions to the corresponding execution subsystems to ensure the Coordinated control.
The reasonable smoothness and performance improvement of vehicle control are achieved, and each execution subsystem is coordinated to control the vehicle status and execution capabilities.
Smart Images

Figure CN221954366U_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the field of automobile technology, and in particular to a chassis domain control system and a vehicle. Background Art
[0002] With the continuous development of automotive electronic technology, automotive mechanical systems are gradually being transformed into more intelligent electronic control systems. The intelligent electronic control system in the vehicle can monitor the vehicle status through a large number of sensors and then realize electronic control adjustment through electrical signals. Compared with the mechanical system, the electronic control adjustment is faster and more accurate. At present, the chassis system in the vehicle is composed of multiple electronic control systems with different functions working together to realize the control of the whole vehicle. However, when each electronic control system is independent, it is easy to have problems of coordination difficulties and poor functional coupling. Therefore, a chassis domain control system that can coordinate multiple execution systems in the chassis is needed to realize the centralized control of the intelligent electronic control system. Utility Model Content
[0003] The present application provides a chassis domain control system and a vehicle, which can solve the technical problem in the related art that various execution systems and software functions in the chassis system cannot be controlled in a coordinated manner.
[0004] In a first aspect, an embodiment of the present application provides a chassis domain control system, the system comprising: a chassis domain controller, at least one independent sensor, and at least one execution subsystem;
[0005] The output end of each independent sensor is connected to the input end of the chassis domain controller, and each independent sensor collects a vehicle status signal of the vehicle, and the vehicle status signal is transmitted to the chassis domain controller through the output end of each independent sensor;
[0006] The output end of the chassis domain controller is connected to the input end of each execution subsystem, and the chassis domain controller determines the control instruction of the vehicle based on the vehicle state signal, and the control instruction is transmitted to the execution subsystem corresponding to the control instruction through the output end of the chassis domain controller;
[0007] The execution subsystem corresponding to the above control instructions receives and executes the above control instructions to adjust the above vehicle.
[0008] In combination with the first aspect, in some possible implementations, the chassis domain controller includes a signal receiver and a domain processor; the input end of the signal receiver is connected to the output end of each independent sensor, the signal receiver receives the vehicle status signal transmitted by each independent sensor, and processes the vehicle status signal to obtain target status data; the input end of the domain processor is connected to the output end of the signal receiver, the domain processor determines the current control scenario according to the target status data transmitted by the signal receiver, and calculates the control instructions corresponding to the current control scenario.
[0009] In combination with the first aspect, in some possible implementations, the chassis domain controller also includes an arbitration calculator; the input end of the arbitration calculator is connected to the output end of the domain processor, the arbitration calculator receives the control instruction transmitted by the domain processor, and determines whether the control instruction meets the preset stability condition; the output end of the arbitration calculator is connected to the input end of each execution subsystem, and when the control instruction meets the preset stability condition, the control instruction is transmitted to the execution subsystem corresponding to the control instruction through the output end of the arbitration calculator.
[0010] In combination with the first aspect, in some possible implementations, at least one execution subsystem is a first-type execution subsystem, and the first-type execution subsystem includes: an actuator, a unit internal sensor, and a processor; the output end of the unit internal sensor is connected to the first input end of the processor, the unit internal sensor collects a vehicle status signal of the vehicle, and the vehicle status signal is transmitted to the processor through the output end of the unit internal sensor; the first output end of the processor is connected to the input end of the chassis domain controller, the processor processes the vehicle status signal to obtain target status data, and the target status data is transmitted to the chassis domain controller through the first output end of the processor; the second input end of the processor is connected to the output end of the chassis domain controller to receive the control instruction transmitted by the chassis domain controller; the input end of the actuator is connected to the second output end of the processor to receive the control instruction transmitted by the processor and execute the control instruction.
[0011] In combination with the first aspect, in some possible implementations, each independent sensor is connected to the chassis domain controller via a hard line; and the first type of execution subsystem is connected to the chassis domain controller via a local area network bus.
[0012] In combination with the first aspect, in some possible implementations, at least one execution subsystem is a second-type execution subsystem, and the second-type execution subsystem includes: an actuator; an input end of the actuator is connected to an output end of the chassis domain controller to receive the control instructions transmitted by the chassis domain controller and execute the control instructions.
[0013] In combination with the first aspect, in some possible implementations, each of the above-mentioned independent sensors is connected to the above-mentioned chassis domain controller via a hard line, and the above-mentioned second type of execution subsystem is connected to the above-mentioned chassis domain controller via a hard line.
[0014] In combination with the first aspect, in some possible implementations, the above-mentioned execution subsystem includes at least one of a front-wheel steering system, a rear-wheel steering system, a braking system, an active suspension system, and a power system.
[0015] In combination with the first aspect, in some possible implementations, the front-wheel steering system is a non-wire-controlled front-wheel steering system or a wire-controlled front-wheel steering system; the rear-wheel steering system is a non-wire-controlled rear-wheel steering system or a wire-controlled rear-wheel steering system; and the braking system is a non-wire-controlled braking system or a wire-controlled braking system.
[0016] In a second aspect, an embodiment of the present application provides a vehicle, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the computer program is suitable for being loaded by the processor and executing the steps of the above method.
[0017] The beneficial effects brought about by the technical solutions provided by some embodiments of the present application include at least:
[0018] The present application provides a chassis domain control system, comprising: a chassis domain controller, at least one independent sensor, and at least one execution subsystem; the output end of each independent sensor is connected to the input end of the chassis domain controller, each independent sensor collects a vehicle status signal of the vehicle, and the vehicle status signal is transmitted to the chassis domain controller through the output end of each independent sensor; the output end of the chassis domain controller is connected to the input end of each execution subsystem, the chassis domain controller determines a control instruction of the vehicle based on the vehicle status signal, and the control instruction is transmitted to the execution subsystem corresponding to the control instruction through the output end of the chassis domain controller; the execution subsystem corresponding to the control instruction receives and executes the control instruction to adjust the vehicle. Since the chassis domain control system of the vehicle is composed of a chassis domain controller, sensors, and execution subsystems, the sensors are responsible for collecting and transmitting signals; the chassis domain controller is responsible for performing logical calculations on the signals to obtain the control instructions currently required by the vehicle, and then the chassis domain controller can determine the execution subsystem used to execute the control instructions from all execution subsystems. When the chassis domain controller sends the control instructions to the execution subsystem, the execution subsystem can execute the control instructions to adjust the vehicle. In this process, the chassis domain controller focuses on the vehicle's own status and the execution capabilities of each execution subsystem, and coordinates the control of each execution subsystem each time a control instruction is generated and executed, making the vehicle control more reasonable and smooth, thereby improving vehicle performance. BRIEF DESCRIPTION OF THE DRAWINGS
[0019] In order to more clearly illustrate the embodiments of the present application or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For those skilled in the art, other drawings can be obtained based on these drawings without paying any creative work.
[0020] Figure 1 A system architecture diagram of a chassis domain control system provided in an embodiment of the present application;
[0021] Figure 2 A schematic diagram of the structure of a chassis domain controller provided in an embodiment of the present application;
[0022] Figure 3 A system architecture diagram of a chassis domain control system provided by another embodiment of the present application;
[0023] Figure 4 A schematic diagram of the structure of a first type of execution subsystem provided in an embodiment of the present application;
[0024] Figure 5 A system architecture diagram of a chassis domain control system provided in another embodiment of the present application. DETAILED DESCRIPTION
[0025] In order to make the features and advantages of the present application more obvious and easy to understand, the technical solutions in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work are within the scope of protection of the present application.
[0026] When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.
[0027] With the continuous development of automotive electronic technology, automotive mechanical systems are gradually being transformed into more intelligent electronic control systems. As people's requirements for traffic safety and comfort become higher and higher, automotive intelligent technology is attracting more and more attention from consumers. At the same time, OEMs and suppliers are also paying more and more attention to the intelligence level of their products. On the one hand, market demand and on the other hand, technological progress have made automotive intelligence the development direction of the automotive industry.
[0028] As an important part of the automobile, the chassis system has realized more and more functions and its design has become more and more complex in the process of vehicle intelligence. The number of chassis electronic control systems and functional modules are also increasing (rear-wheel steering, active stabilizer bar, electronic differential, etc.). Each system is usually distributed and processed and responded separately, resulting in insufficient interaction and coordination between systems and poor coupling. With the development of software functions in each system, there may be repeated development between software functions. In addition, on the other hand, compared with distributed chassis systems, more advanced driving assistance functions and autonomous driving functions require chassis systems that can coordinate and control multiple execution systems.
[0029] Therefore, the embodiment of the present application provides a chassis domain control system and a vehicle, the chassis domain control system includes: a chassis domain controller, at least one independent sensor, and at least one execution subsystem; the output end of each independent sensor is connected to the input end of the chassis domain controller, each independent sensor collects the vehicle status signal of the vehicle, and the vehicle status signal is transmitted to the chassis domain controller through the output end of each independent sensor; the output end of the chassis domain controller is connected to the input end of each execution subsystem, the chassis domain controller determines the control instruction of the vehicle based on the vehicle status signal, and the control instruction is transmitted to the execution subsystem corresponding to the control instruction through the output end of the chassis domain controller; the execution subsystem corresponding to the control instruction receives and executes the control instruction. This solves the technical problem that the various execution systems and software functions in the chassis system cannot be controlled collaboratively.
[0030] See also Figure 1 , Figure 1 A system architecture diagram of a chassis domain control system provided in an embodiment of the present application.
[0031] like Figure 1 As shown, in order to facilitate the description of the specific system architecture of the chassis domain control system 100, the present application embodiment takes the connection diagram between the modules in the chassis domain control system 100 as an example for introduction. It should be noted that the chassis domain control system 100 can also have other specific architectures that can be implemented when it is specifically applied. Figure 1 The system architecture diagram of the chassis domain control system should not be understood as the only feasible system architecture approach for the chassis domain control system 100 .
[0032] like Figure 1 As shown, the chassis domain control system 100 includes at least a chassis domain controller 110, at least one independent sensor 120, and at least one execution subsystem 130. The chassis domain control system 110 can be applied to a vehicle to coordinately control other execution subsystems in the vehicle chassis, making the vehicle control more reasonable and smooth, and improving the vehicle performance.
[0033] Specifically, in the chassis domain control system 100, for at least one independent sensor 120, the output end of each independent sensor 120 is connected to the input end of the chassis domain controller 110, each independent sensor 120 collects a vehicle status signal of the vehicle, and the vehicle status signal is transmitted to the chassis domain controller 110 through the output end of each independent sensor 120, so that the chassis domain controller 110 receives the vehicle status signal collected and sent by each independent sensor 120 through the input end.
[0034] Optionally, the signals collected by the independent sensor 120 are various signals of the vehicle itself and the environment. For example, when the independent sensor 120 collects signals related to the front wheel steering information of the vehicle, the chassis domain controller 110 can receive the steering wheel angle signal, steering wheel torque signal, etc. collected by the independent sensor 120; when the independent sensor 120 collects signals related to the rear wheel steering information of the vehicle, the chassis domain controller 110 can receive the rear wheel angle signal, etc. collected by the independent sensor 120; when the independent sensor 120 collects signals related to the vehicle braking information, the chassis domain controller 110 can receive the independent sensor 120. The independent sensor 120 collects vehicle speed signals, wheel speed signals, brake master cylinder pressure signals, brake pedal travel signals, etc.; when the independent sensor 120 collects signals related to the vehicle's active suspension information, the chassis domain controller 110 can receive the height signal, acceleration signal, air tank pressure signal, etc. collected by the independent sensor 120; when the independent sensor 120 collects signals related to the vehicle's power information, the chassis domain controller 110 can receive the throttle opening degree signal, the gear position signal of the gearbox, the yaw angular velocity signal, the acceleration signal, the ADAS request signal, etc. collected by the independent sensor 120.
[0035] Optionally, the chassis domain controller 110 has the protocol conversion function of the gateway 140, and can use the local area network bus 150 (CAN network) of the local area network to receive the driver's control instructions or intelligent driving instructions, as well as the information of all sensors related to the dynamic characteristics of the vehicle; on the other hand, the chassis domain controller 110 is connected to all the execution subsystems 130 in the domain through the CAN network, and the chassis domain controller 110 runs the highest level of chassis control strategy and control logic, including driver intention recognition, fault diagnosis and degradation processing, etc. The chassis domain controller 110 can comprehensively balance and coordinate the various execution subsystems 130 in the vehicle, reasonably divide the work of the various execution subsystems 130 of the vehicle chassis, and use the best method to complete the dynamic control and stability of the vehicle.
[0036] Then in the embodiment of the present application, after the chassis domain controller 110 receives the vehicle status signal collected and sent by each independent sensor 120, the chassis domain controller 110 determines the control instruction of the vehicle based on the vehicle status signal, and the execution subsystem 130 corresponding to the control instruction is the execution subsystem 130 that needs to execute the control instruction this time, so the output end of the chassis domain controller 110 is also connected to the input end of each execution subsystem 130, so that the control instruction is transmitted to the execution subsystem 130 corresponding to the control instruction through the output end of the chassis domain controller 110. After the input end of the execution subsystem 130 corresponding to the control instruction receives the control instruction sent by the chassis domain controller 110, it executes the control instruction and adjusts the vehicle according to the instruction of the control instruction, and finally realizes the coordinated control of each execution subsystem 130 through the chassis domain controller 110, and realizes the reasonable allocation of execution resources in the vehicle.
[0037] Optionally, the execution subsystem 130 includes at least one of a front-wheel steering system, a rear-wheel steering system, a braking system, an active suspension system, and a power system. The front-wheel steering system and the rear-wheel steering system may be a non-wire-controlled front-wheel steering system and a non-wire-controlled rear-wheel steering system, and the non-wire-controlled steering system may be implemented using an electric power steering system (Electric Power Steering System, EPS); the front-wheel steering system and the rear-wheel steering system may also be a wire-controlled front-wheel steering system and a wire-controlled rear-wheel steering system, and the wire-controlled steering system may be implemented using a wire-controlled steering system (Steering by Wire, SBW). The wire-controlled steering system (Steering by Wire, SBW) includes two parts: a steering feedback actuator (or a hand-feel unit) (Steering Feedback Actuator, SFA) and a wheel actuator (Road Wheel Actuator, RWA), and these two parts interact with each other using a private LAN bus in the wire-controlled steering system to achieve steering control. Similarly, the braking system can be a non-wire-controlled braking system, which can be implemented through the Electronic Stability Program (ESP); or a wire-controlled braking system, which can be implemented through the Electric Mechanical Brake (EMB).
[0038] The present application provides a chassis domain control system, comprising: a chassis domain controller, at least one independent sensor, and at least one execution subsystem; the output end of each independent sensor is connected to the input end of the chassis domain controller, each independent sensor collects a vehicle status signal of the vehicle, and the vehicle status signal is transmitted to the chassis domain controller through the output end of each independent sensor; the output end of the chassis domain controller is connected to the input end of each execution subsystem, the chassis domain controller determines a control instruction of the vehicle based on the vehicle status signal, and the control instruction is transmitted to the execution subsystem corresponding to the control instruction through the output end of the chassis domain controller; the execution subsystem corresponding to the control instruction receives and executes the control instruction to adjust the vehicle. Since the chassis domain control system of the vehicle is composed of a chassis domain controller, sensors, and execution subsystems, the sensors are responsible for collecting and transmitting signals; the chassis domain controller is responsible for performing logical calculations on the signals to obtain the control instructions currently required by the vehicle, and then the chassis domain controller can determine the execution subsystem used to execute the control instructions from all execution subsystems. When the chassis domain controller sends the control instruction to the execution subsystem corresponding to the control instruction, the execution subsystem corresponding to the control instruction can execute the control instruction to adjust the vehicle; in this process, the chassis domain controller focuses on the vehicle's own status and the execution capabilities of each execution subsystem, and coordinates the control of each execution subsystem each time a control instruction is generated and executed, making the vehicle control more reasonable and smooth, thereby improving vehicle performance.
[0039] See also Figure 2 , Figure 2 A schematic diagram of the structure of a chassis domain controller provided in an embodiment of the present application.
[0040] like Figure 2 As shown, the chassis domain controller 110 may specifically include a signal receiver 1101 and a domain processor 1102. In the prior art, the signal receiver 1101 is used to receive signals transmitted by sensors. In the embodiment of the present application, when the chassis domain controller 110 is connected to each independent sensor 120 in the vehicle, the input end of the signal receiver 1101 is specifically connected to the output end of each independent sensor 120, so that the signal receiver 1101 can receive the vehicle status signal transmitted by each independent sensor 120. In addition, the signal receiver 1101 can also process the vehicle status signal to obtain target status data. Generally speaking, the vehicle status signal is a signal in the raw data format collected by the sensor. Then the signal receiver 1101 in the chassis domain controller 110 can perform certain preprocessing and analysis on the signal after receiving the signal to obtain the target status data that the chassis domain controller 110 can directly use for calculation.
[0041] Optionally, the output end of the signal receiver 1101 is connected to the input end of the domain processor 1102, and the signal receiver 1101 transmits the target state data to the domain processor 1102 through the output end. The domain processor 1102 further determines the current control scenario of the vehicle according to the received target state data, and calculates the corresponding control instructions of the vehicle under the current control scenario. The current control scenario describes the current working condition, vehicle condition, driver intention, etc. of the vehicle. When the domain processor 1102 determines the current control scenario, that is, the domain processor 1102 determines the current working condition of the vehicle according to the target state data. For example, the domain processor 1102 can confirm whether the current vehicle is in a straight state or a turning state through vehicle steering related signals such as lateral acceleration signals, yaw angular velocity signals, and steering wheel angle signals; the domain processor 1102 also confirms whether the vehicle is currently in an acceleration state or a deceleration state through longitudinal acceleration signals, throttle pedal opening signals, brake pedal travel signals, etc.; or, the domain processor 1102 can also determine whether the state of each wheel is slipping or locking through yaw angular velocity signals and tire slip rate signals. According to the current control scenario in which the vehicle is currently located, the domain processor 1102 can calculate the corresponding control instructions.
[0042] Optionally, the chassis domain controller 110 also includes an arbitration calculator 1103, and the input end of the arbitration calculator 1103 is connected to the output end of the domain processor 1102. After the domain processor 1102 in the chassis domain controller 110 calculates the control instruction, considering that the current state of the vehicle may be changed after the control instruction is executed, in order to prevent the stability of the vehicle from being destroyed, before the control instruction is executed, the arbitration calculator 1103 can receive the control instruction calculated and output by the domain processor 1102, and determine whether the control instruction meets the preset stability condition. The preset stability condition is the stability boundary calculated in advance for the vehicle. When the stability parameter exceeds the stability boundary, the vehicle is unstable.
[0043] Furthermore, when the output end of the chassis domain controller 110 is connected to the input end of each execution subsystem 130, specifically, the output end of the arbitration calculator 1103 is connected to the input end of each execution subsystem 130, when the arbitration calculator 1103 determines that the control instruction meets the preset stability condition, it means that the control instruction will not cause the vehicle to become unstable. At this time, the control instruction is transmitted to the execution subsystem 130 corresponding to the control instruction through the output end of the arbitration calculator 1103, so that the execution subsystem 130 corresponding to the control instruction receives and executes the control instruction, and adjusts the vehicle according to the instructions of the control instruction, and finally realizes the coordinated control of each execution subsystem 130 through the chassis domain controller 110, and realizes the reasonable allocation of execution resources in the vehicle.
[0044] The present application provides a chassis domain controller, including: a signal receiver, a domain processor, and an arbitration calculator; wherein the signal receiver is used to receive a vehicle state signal transmitted by an independent sensor and process the vehicle state signal to obtain target state data; the signal receiver is also connected to the domain processor, and the domain processor determines the current control scenario according to the target state data transmitted by the signal receiver, and calculates the control instruction corresponding to the current control scenario; the arbitration calculator is connected to the domain processor, and the arbitration calculator receives the control instruction transmitted by the domain processor, determines whether the control instruction meets the preset stability condition, and when the control instruction meets the preset stability condition, transmits the control instruction to the execution subsystem corresponding to the control instruction through the connection with each execution subsystem. The chassis domain controller can receive all information related to the dynamic characteristics of the vehicle; connected with all the execution subsystems in this domain, the chassis domain controller can comprehensively balance and coordinate the various execution subsystems in the vehicle, reasonably divide the work of the various execution subsystems of the vehicle chassis, and use the best method to complete the dynamic control and stability of the vehicle.
[0045] See also Figure 3 , Figure 3 A system architecture diagram of a chassis domain control system provided in another embodiment of the present application.
[0046] like Figure 3 As shown, the execution subsystem 130 in the chassis domain control system 100 may be a first type of execution subsystem 1301. For the first type of execution subsystem 1301, refer to Figure 4 , Figure 4 A schematic diagram of the structure of a first type of execution subsystem provided in an embodiment of the present application is shown in FIG. Figure 4 As shown, the first type of execution subsystem 1301 includes: an actuator 13011, a unit internal sensor 13012, and a processor 13013. Since the first type of execution subsystem 1301 has the unit internal sensor 13012, it can also collect the vehicle signals required by itself, and at the same time has the processor 13013, in which some software logic can be integrated, so it can also support the calculation of some software functions.
[0047] Alternatively, if Figure 4 As shown, in the first type of execution subsystem 1301, the unit internal sensor 13012 can collect the vehicle status signal, and the output end of the unit internal sensor 13012 is connected to the first input end of the processor 13013. After the unit internal sensor 13012 collects the vehicle status signal of the vehicle, the vehicle status signal is transmitted to the processor 13013 through the output end of the unit internal sensor 13012, so that the processor 13013 can process the vehicle status signal.
[0048] Alternatively, if Figure 4As shown, the processor 13013 may have software computing capabilities, so the vehicle status signal can be preliminarily preprocessed and analyzed, that is, the processor 13013 can process the vehicle status signal to obtain target status data, and the first output end of the processor 13013 is connected to the input end of the chassis domain controller 110, and the target status data can be transmitted to the chassis domain controller 110 through the first output end of the processor 13013, so that the chassis domain controller 110 can directly use the target status data transmitted by the processor 13013 to calculate the control instructions.
[0049] Alternatively, if Figure 4 As shown, the second input end of the processor 13013 is connected to the output end of the chassis domain controller 110. After the chassis domain controller 110 calculates the control instruction, the chassis domain controller 110 will also send the control instruction to the processor 13013, so that the processor 13013 receives the control instruction. At the same time, the input end of the actuator 13011 is connected to the second output end of the processor 13013. After receiving the control instruction, the processor 13013 transmits the control instruction to the actuator 13011, so that the actuator 13011 receives and executes the control instruction.
[0050] For further information, please refer to Figure 3 In the chassis domain control system 100, each independent sensor 120 directly connected to the chassis domain controller 110 can be directly connected to the chassis domain controller 110 through a hard line 160 because the independent sensor 120 only performs signal acquisition and transmission and does not have software functions. In automotive electronic systems, communication links are often connected through hard lines to achieve signal transmission. In hard-line communication links, fixed hard lines are used between controllers and automotive electronic components. Hard-line signals can transmit various signals in automotive electronic systems, such as temperature signals, pressure signals, accelerator pedal position signals, etc. The first type of execution subsystem 1301 has software functions, so it needs to be connected to the chassis domain controller 110 through a local area network bus 150 (CAN bus). The CAN bus can support the use of information transmission protocols. When CAN signals transmit signals between controllers and automotive electronic components, they can carry more information data and have a faster transmission rate.
[0051] The present application provides a chassis domain control system, wherein the execution subsystem is a first-class execution subsystem, and the first-class execution subsystem includes: an actuator, a unit internal sensor, and a processor; wherein the unit internal sensor is connected to the processor, and the unit internal sensor collects the vehicle status signal and transmits it to the processor; the processor is connected to the chassis domain controller, and the processor processes the vehicle status signal to obtain the target status data, and transmits the target status data to the chassis domain controller, and the chassis domain controller transmits the control instructions calculated based on the target status data to the processor; the processor is connected to the actuator, and the control instructions are transmitted to the actuator, so that the actuator receives and executes the control instructions. At this time, the processor of the first-class execution subsystem has certain software functions, and can receive, process, transmit, and execute data. Therefore, the first-class execution subsystem needs to be connected to the chassis domain controller through a local area network bus, and the independent sensor that only collects and transmits the original signal is connected to the chassis domain controller through a hard line.
[0052] See also Figure 5 , Figure 5 A system architecture diagram of a chassis domain control system provided in another embodiment of the present application.
[0053] like Figure 5 As shown, the execution subsystem 130 in the chassis domain control system 100 can also be a second type of execution subsystem 1302, and the second type of execution subsystem 1302 includes: an actuator 13021. Since the second type of execution subsystem 1302 only has the actuator 13021, it means that it only has execution capabilities but no software functions. At this time, the chassis domain controller 110 can directly integrate the software functions required by each execution subsystem.
[0054] In the embodiment of the present application, the input end of the actuator 13021 is directly connected to the output end of the chassis domain controller 110 to receive the control instructions transmitted by the chassis domain controller 110 and execute the control instructions. In this case, since the actuator 13021 only receives and executes control instructions, it only has execution capabilities and does not have software functions, so the actuator 13021 and the chassis domain controller 110 can also be directly connected through the hard line 160. Similarly, the independent sensor 120 only performs signal acquisition and transmission work, does not have software functions, and the independent sensor 120 and the chassis domain controller 110 are also directly connected through the hard line 160.
[0055] The present application provides a chassis domain control system, wherein the execution subsystem is a second-type execution subsystem, and the second-type execution subsystem includes: an actuator; wherein the actuator is connected to the chassis domain controller to receive control instructions transmitted by the chassis domain controller and execute the control instructions. At this time, the second-type execution subsystem only has execution capability and is directly connected to the chassis domain controller through a hard line, and the independent sensor that only collects and transmits raw signals is also connected to the chassis domain controller through a hard line.
[0056] The present application also provides a vehicle, which includes any one of the above-mentioned chassis domain control systems, thereby achieving the same effect as the chassis domain control system in the above-mentioned embodiment.
[0057] In the several embodiments provided in the present application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of modules is only a logical function division. There may be other division methods in actual implementation, such as multiple modules or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or modules, which can be electrical, mechanical or other forms.
[0058] The modules described as separate components may or may not be physically separated, and the components shown as modules may or may not be physical modules, that is, they may be located in one place or distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the solution of this embodiment.
[0059] In the above embodiments, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it can be implemented in whole or in part in the form of a computer program product. The above computer program product includes one or more computer instructions. When the above computer program instructions are loaded and executed on a computer, the above process or function according to the embodiment of this specification is generated in whole or in part. The above computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable devices. The above computer instructions can be stored in a computer-readable storage medium or transmitted by the above computer-readable storage medium. The above computer instructions can be transmitted from a website site, computer, server or data center to another website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (Digital Subscriber Line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode. The above computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server, data center, etc. that contains one or more available media integrated. The above-mentioned available media can be magnetic media (for example, floppy disks, hard disks, tapes), optical media (for example, digital versatile discs (DVD)), or semiconductor media (for example, solid state drives (SSD)), etc.
[0060] It should be noted that, for the above-mentioned method embodiments, for the sake of simplicity of description, they are all expressed as a series of action combinations, but those skilled in the art should be aware that the present application is not limited by the described action sequence, because according to the present application, certain steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also be aware that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily required by the present application.
[0061] In the above embodiments, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, reference can be made to the relevant descriptions of other embodiments.
[0062] The above is a description of a chassis domain control system and a vehicle provided in the present application. For technicians in this field, according to the ideas of the embodiments of the present application, there may be changes in the specific implementation methods and application scopes. In summary, the content of this specification should not be understood as a limitation on the present application.
Claims
1. A chassis domain control system, characterized in that: The chassis domain control system includes: a chassis domain controller, at least one independent sensor, and at least one execution subsystem; The output end of each independent sensor is connected to the input end of the chassis domain controller, and each independent sensor collects a vehicle status signal of the vehicle, and the vehicle status signal is transmitted to the chassis domain controller through the output end of each independent sensor; The output end of the chassis domain controller is connected to the input end of each execution subsystem, and the chassis domain controller determines the control instruction of the vehicle based on the vehicle state signal, and the control instruction is transmitted to the execution subsystem corresponding to the control instruction through the output end of the chassis domain controller; The execution subsystem corresponding to the control instruction receives and executes the control instruction to adjust the vehicle.
2. The chassis domain control system according to claim 1, characterized in that: The chassis domain controller includes a signal receiver and a domain processor; The input end of the signal receiver is connected to the output end of each independent sensor, and the signal receiver receives the vehicle state signal transmitted by each independent sensor, and processes the vehicle state signal to obtain target state data; The input end of the domain processor is connected to the output end of the signal receiver. The domain processor determines a current control scenario according to the target state data transmitted by the signal receiver, and calculates a control instruction corresponding to the current control scenario.
3. The chassis domain control system according to claim 2, characterized in that: The chassis domain controller also includes an arbitration calculator; The input end of the arbitration calculator is connected to the output end of the domain processor, and the arbitration calculator receives the control instruction transmitted by the domain processor and determines whether the control instruction meets a preset stability condition; The output end of the arbitration calculator is connected to the input end of each execution subsystem. When the control instruction meets the preset stability condition, the control instruction is transmitted to the execution subsystem corresponding to the control instruction through the output end of the arbitration calculator.
4. The chassis domain control system according to claim 1, characterized in that: At least one execution subsystem is a first type execution subsystem, and the first type execution subsystem includes: an actuator, a unit internal sensor, and a processor; The output end of the unit internal sensor is connected to the first input end of the processor, the unit internal sensor collects a vehicle state signal of the vehicle, and the vehicle state signal is transmitted to the processor through the output end of the unit internal sensor; The first output terminal of the processor is connected to the input terminal of the chassis domain controller, the processor processes the vehicle state signal to obtain target state data, and the target state data is transmitted to the chassis domain controller through the first output terminal of the processor; The second input terminal of the processor is connected to the output terminal of the chassis domain controller to receive the control instruction transmitted by the chassis domain controller; The input end of the actuator is connected to the second output end of the processor to receive the control instruction transmitted by the processor and execute the control instruction.
5. The chassis domain control system according to claim 4, characterized in that: Each independent sensor is connected to the chassis domain controller via a hard line; the first type of execution subsystem is connected to the chassis domain controller via a local area network bus.
6. The chassis domain control system according to claim 1, characterized in that: At least one execution subsystem is a second type of execution subsystem, and the second type of execution subsystem includes: an actuator; The input end of the actuator is connected to the output end of the chassis domain controller to receive the control instruction transmitted by the chassis domain controller and execute the control instruction.
7. The chassis domain control system according to claim 6, characterized in that: Each of the independent sensors is connected to the chassis domain controller via a hard line, and the second type of execution subsystem is connected to the chassis domain controller via a hard line.
8. The chassis domain control system according to claim 1, characterized in that: The execution subsystem includes at least one of a front wheel steering system, a rear wheel steering system, a braking system, an active suspension system, and a power system.
9. The chassis domain control system according to claim 8, characterized in that: The front wheel steering system is a non-wire-controlled front wheel steering system or a wire-controlled front wheel steering system; the rear wheel steering system is a non-wire-controlled rear wheel steering system or a wire-controlled rear wheel steering system; the braking system is a non-wire-controlled brake system or a wire-controlled brake system.
10. A vehicle, characterized in that: The vehicle comprises the chassis domain control system according to any one of claims 1 to 9 above.
Citation Information
Cited By
Mobile equipment control system, method and equipment and storage medium
CN121635304A
