Control methods, devices, equipment and storage media for vehicle thermal management
By deploying two controllers in the vehicle and utilizing bus and Ethernet communication, dual redundant control of the thermal management system is achieved, solving the single point of failure problem of a single controller design and ensuring the reliability and safety of the thermal management system.
Patent Information
- Application Number
- CN202510966116.9
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2025-07-14
- Publication Date
- 2026-11-17
- Estimated Expiration
- 2045-07-14
AI Technical Summary
In existing vehicle thermal management systems, the design of a single controller poses a single point of failure risk, which can lead to thermal management control failure, failure to cool down in time, and increase the risk of overheating of heat-generating components such as batteries and electric drives, thus affecting vehicle safety.
Two controllers are deployed in the vehicle and communicate via a pre-set bus and Ethernet. The first controller is responsible for normal control, and the second controller takes over control when the first controller malfunctions. By analyzing message information and transmission paths, the type of malfunction is identified and targeted control is performed to ensure the continuous and reliable operation of the thermal management components.
It achieves reliable control of the vehicle's thermal management, reduces the risk of overheating and spontaneous combustion, and improves vehicle safety and the availability of the thermal management system.
Smart Images

Figure CN120802746B_ABST
Abstract
Description
Technical Field
[0001] This invention relates to the field of automotive thermal management technology, and more specifically to a control method, device, equipment, and storage medium for vehicle thermal management. Background Technology
[0002] With the increasing prevalence of electric vehicles equipped with high-voltage batteries, public concern about their safety is growing. Vehicles typically include thermal management components such as water heaters and compressors to control the overall vehicle's thermal performance. If the vehicle's thermal management system fails, the risk of overheating in heat-generating components such as the battery, electric drive system, and electronic control system increases significantly.
[0003] Therefore, we need to ensure the reliability of vehicle thermal management control to improve vehicle safety. Summary of the Invention
[0004] The purpose of this invention is to provide a control method, device, equipment, and storage medium for vehicle thermal management, so as to improve the safety of vehicle thermal management control.
[0005] In a first aspect, the present invention provides a control method for vehicle thermal management. The method is applied to a vehicle, in which a first controller, a second controller, and a thermal management component are deployed. The thermal management component is communicatively connected to the first controller and the second controller via a preset bus. The first controller and the second controller are communicatively connected via Ethernet. The first controller controls the thermal management component, and the second controller takes over control of the thermal management component when the first controller malfunctions. The method includes:
[0006] The second controller receives message information sent by the first controller and determines the transmission path of the message information; wherein the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller;
[0007] The anomaly type of the first controller is determined based on the message information and the transmission path of the message information;
[0008] Based on the anomaly type of the first controller, the thermal management component is controlled by the second controller.
[0009] Secondly, the present invention provides a control device for vehicle thermal management. This device is applied to a vehicle, in which a first controller, a second controller, and a thermal management component are deployed. The thermal management component is communicatively connected to the first and second controllers via a preset bus. The first and second controllers are communicatively connected via Ethernet. The first controller controls the thermal management component, and the second controller takes over control of the thermal management component when the first controller malfunctions. The device includes:
[0010] The path determination unit is used to receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller;
[0011] A type determination unit is used to determine the anomaly type of the first controller based on the message information and the transmission path of the message information;
[0012] A thermal management control unit is used to control the thermal management component via a second controller based on the anomaly type of the first controller.
[0013] Thirdly, the present invention provides an electronic device, comprising: a processor, and a memory communicatively connected to the processor;
[0014] The memory stores computer-executed instructions;
[0015] The processor executes computer execution instructions stored in the memory to implement the method as described in the first aspect.
[0016] Fourthly, the present invention provides a computer-readable storage medium storing computer-executable instructions, which, when executed by a processor, are used to implement the method described in the first aspect.
[0017] Fifthly, the present invention provides a computer program product, including a computer program that, when executed by a processor, implements the method described in the first aspect.
[0018] This invention provides a control method, apparatus, device, and storage medium for vehicle thermal management. Two controllers, a first controller and a second controller, are deployed in the vehicle, with the first controller preferentially controlling the thermal management components. The first and second controllers communicate via a preset bus or Ethernet. The first controller can send message information to the second controller through different channels. Based on the content and transmission path of the message information, it can be determined whether the first controller has an anomaly and the type of anomaly. For different anomaly types, the second controller can take over the thermal management components in different ways, ensuring continuous control of the thermal management components while improving control accuracy. This achieves reliable control of the vehicle's thermal management, reducing the risk of overheating or even spontaneous combustion, and improving vehicle safety. Attached Figure Description
[0019] The accompanying drawings, which are incorporated in and form part of this specification, illustrate embodiments consistent with the invention and, together with the description, serve to explain the principles of the invention.
[0020] Figure 1 A schematic flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention;
[0021] Figure 2 This is a schematic diagram illustrating the connection relationship between the controller and the thermal management component in a vehicle according to an embodiment of the present invention;
[0022] Figure 3 A schematic flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention;
[0023] Figure 4 A schematic flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention;
[0024] Figure 5 This is a schematic diagram of the structure of a vehicle thermal management system provided in an embodiment of the present invention;
[0025] Figure 6 This is a schematic diagram of the thermal management limp hardware provided in an embodiment of the present invention;
[0026] Figure 7 A schematic flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention;
[0027] Figure 8 A schematic flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention;
[0028] Figure 9 A structural block diagram of a vehicle thermal management control device provided in an embodiment of the present invention;
[0029] Figure 10 A structural block diagram of an electronic device provided in an embodiment of the present invention;
[0030] Figure 11 This is a structural block diagram of an electronic device provided in an embodiment of the present invention.
[0031] The accompanying drawings have illustrated specific embodiments of the invention, which will be described in more detail below. These drawings and descriptions are not intended to limit the scope of the invention in any way, but rather to illustrate the concept of the invention to those skilled in the art through reference to particular embodiments. Detailed Implementation
[0032] The embodiments of the present invention will be described below with reference to the accompanying drawings and preferred embodiments. Those skilled in the art can easily understand other advantages and effects of the present invention from the content disclosed in this specification. The present invention can also be implemented or applied through other different specific embodiments, and various details in this specification can also be modified or changed based on different viewpoints and applications without departing from the spirit of the present invention. It should be understood that the preferred embodiments are only for illustrating the present invention and not for limiting the scope of protection of the present invention.
[0033] It should be noted that the illustrations provided in the following embodiments are only schematic representations of the basic concept of the present invention. Therefore, the drawings only show the components related to the present invention and are not drawn according to the actual number, shape and size of the components in the actual implementation. In the actual implementation, the form, quantity and proportion of each component can be arbitrarily changed, and the layout of the components may also be more complex.
[0034] In the description of this invention, it should be understood that the terms "first," "second," "third," etc., are used only to distinguish similar objects and are not necessarily used to describe a specific order or sequence, nor should they be construed as indicating or implying relative importance. Those skilled in the art can understand the specific meaning of the above terms in this invention according to the specific circumstances. Furthermore, in the description of this invention, unless otherwise stated, "multiple" refers to two or more. "And / or" describes the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. The character " / " generally indicates that the preceding and following related objects have an "or" relationship.
[0035] It should be noted that, due to space limitations, this specification does not exhaustively list all possible implementation methods. Those skilled in the art, after reading this specification, should be able to deduce that any combination of technical features can constitute an optional implementation method, provided that the technical features do not contradict each other. The following provides a detailed description of each embodiment.
[0036] With the rapid development of new energy vehicle technology, electric vehicles equipped with high-voltage batteries are becoming increasingly popular. However, in recent years, news of spontaneous combustion incidents involving high-voltage batteries in electric vehicles has been frequently reported, raising serious concerns about the safety of electric vehicles. As a key system ensuring safe vehicle operation, the reliability of the vehicle's thermal management system directly affects the temperature control of core heat-generating components such as the battery, electric drive, and electronic control system. If the thermal management system fails, the risk of these heat-generating components overheating will increase significantly, potentially affecting vehicle performance or even leading to serious safety accidents.
[0037] Currently, vehicle thermal management systems typically employ a single controller for management and control, an architecture with a significant risk of single point of failure. When the controller malfunctions—for example, due to hardware failure or communication link interruption—the entire thermal management system loses control and cannot effectively cool heat-generating components in a timely manner. This design flaw is particularly problematic under conditions of high-speed electric vehicle operation or extreme environments, potentially leading to delayed system response, difficulty in detecting and addressing controller anomalies, and consequently impacting the stable operation of the thermal management system.
[0038] The present invention provides a control method, device, equipment and storage medium for vehicle thermal management, which aims to solve the above-mentioned technical problems in the prior art.
[0039] The technical solution of the present invention and how the technical solution of the present invention solves the above-mentioned technical problems are described in detail below with specific embodiments. These specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described again in some embodiments. The embodiments of the present invention will now be described with reference to the accompanying drawings.
[0040] Figure 1 This is a flowchart illustrating a vehicle thermal management control method according to an embodiment of the present invention. The method can be executed by a vehicle thermal management control device. The method is applied to a vehicle, which includes a first controller, a second controller, and a thermal management component. The thermal management component is communicatively connected to the first and second controllers via a preset bus. The first and second controllers are also communicatively connected via Ethernet. The first controller controls the thermal management component, and the second controller takes over control of the thermal management component when the first controller malfunctions. Figure 1 As shown, the method includes the following steps:
[0041] S101. Receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein, the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller.
[0042] For example, two controllers are deployed in the vehicle, namely a first controller and a second controller. For instance, multiple controllers can be physically divided within the vehicle, each responsible for managing electronic devices within a specific area of the vehicle. The controllers within the vehicle may include a left domain controller and a right domain controller. In this embodiment, the right domain controller can be used as the first controller, and the left domain controller as the second controller.
[0043] The vehicle may also be equipped with thermal management components that can control the temperature of heat-generating components in the vehicle. For example, heat-generating components in the vehicle may include batteries, motors, etc. The thermal management components may include water heaters, compressors, front electric drive controllers, rear electric drive controllers, power controllers, high-voltage battery management systems, automatic grilles, evaporator electronic expansion valves, battery cooling electronic expansion valves, multi-way valves, etc.
[0044] The thermal management component can communicate with two controllers via a preset bus. The preset bus refers to the standard communication bus within the vehicle, such as a controller area network (CAN) bus, used for transmitting control commands and status information. The preset bus can include CAN (Controller Area Network), CANFD (CAN with Flexible Data-Rate), LIN (Local Interconnect Network), etc. For example, both the first and second controllers can connect to and communicate with the water heater and compressor via a CAN network. Both the first and second controllers can have CAN network terminating resistors. Both controllers can receive and send signals to the water heater and compressor to control them. As another example, both the first and second controllers can connect to and communicate with the front electric drive controller, rear electric drive controller, power controller, and high-voltage battery management system via a CANFD network. Both controllers can have terminating resistors. In this embodiment, the terminating resistor can be 120 ohms. Both the first and second controllers can receive signals from the front electric drive controller, rear electric drive controller, power controller, and high-voltage battery management system. For example, both the first and second controllers can be interconnected and communicate with the automatic grille, evaporator electronic expansion valve, battery cooling electronic expansion valve, and multi-way valve via LIN. Both the first and second controllers can receive signals from the automatic grille, evaporator electronic expansion valve, battery cooling electronic expansion valve, and multi-way valve, and can also send signals to these devices to control them.
[0045] An Ethernet communication link can be established between the first controller and the second controller. An HPC (High Performance Computing, central computer) can also be deployed in the vehicle. The first controller, the second controller, and the HPC are connected to form a ring Ethernet communication link through Ethernet, ensuring that there is a communication link between any two of the three, thereby improving redundancy. Figure 2 This is a schematic diagram showing the connection relationship between the controller and the thermal management components in a vehicle. Figure 2 In this vehicle, the controllers can include a first controller and a second controller. The first and second controllers can be connected via Ethernet, or each can be connected to an HPC (Hypercomputer) via Ethernet. The HPC can then be connected to the vehicle's infotainment screen. The first and second controllers can be connected to the water heater and compressor respectively via a CAN network. Termination resistors, components of the CAN network, are installed on both the first and second controllers to enable CAN network communication. The first and second controllers can also be connected to the front electric drive controller, rear electric drive controller, power controller, and high-voltage battery management system respectively via CANFD. Termination resistors, components of the CANFD network, are also installed on both the first and second controllers to enable CANFD network communication. Furthermore, the first and second controllers can be connected via LIN to the automatic grille, evaporator electronic expansion valve, battery cooling electronic expansion valve, and multi-way valve respectively.
[0046] The first controller may contain thermal management software, which is a program used for thermal management. Through this software, the first controller can control the thermal management components. Specifically, the first controller can perform routine control of the thermal management components, such as cooling them. In this embodiment, the control functions of the thermal management software are not specifically limited. The first controller is the primary controller for thermal management; therefore, it is the first controller that is preferentially used to control the thermal management components. When the first controller malfunctions, a second controller can be used to control the thermal management components, improving the reliability of the vehicle's thermal management control system and ensuring basic thermal management of the battery-electric drive even in the event of thermal management software failure.
[0047] The first controller can send message information to the second controller, and the second controller can receive message information from the first controller in real time or periodically. The second controller can determine the transmission path of the message information; for example, the transmission path can be CAN, CANFD, LIN, Ethernet, etc. That is, the first controller can send message information through CAN, CANFD, LIN, Ethernet, etc., and the second controller can receive message information through the corresponding path; this path is the transmission path. The message information can characterize the working status of the first controller; for example, it can characterize whether the thermal management software in the first controller has crashed, whether there are abnormalities in the CAN network communication of the first controller, whether there are abnormalities in the CANFD communication of the first controller, whether there are abnormalities in the LIN communication of the first controller, and whether there are abnormalities in the sensor data acquisition of the first controller. In this embodiment, the content and triggering form of the message information are not specifically limited. For example, the message information contains controller operating status data, which can specifically be in the form of periodic heartbeat messages or event-triggered messages to reflect the real-time working status of the controller. The identification of the transmission path can be achieved by parsing the physical layer characteristics of the data frame; specifically, the source channel of the message information can be determined based on the data receiving port.
[0048] In this embodiment, the second controller can continuously monitor message information, i.e., communication data, from the first controller. For example, this may include data transmitted via a preset bus and handshake response signals transmitted via Ethernet.
[0049] S102. Determine the anomaly type of the first controller based on the message information and the transmission path of the message information.
[0050] For example, after receiving the message information and its transmission path, the second controller can analyze the content of the message information and, based on the content and transmission path, determine whether the first controller has an anomaly. If no anomaly is found, the second controller continues to receive and analyze message information, and the first controller continues to control the thermal management component; if an anomaly is found, the type of anomaly in the first controller needs to be determined.
[0051] In this embodiment, multiple anomaly types can be preset. Based on the content and transmission path of the message information, the anomaly type corresponding to that content and transmission path can be determined. For example, the timestamp in the message information can be analyzed. If the message information reception timeout is determined based on the timestamp, the first controller can be considered to have an anomaly. As another example, when a message on the preset bus is detected to have timed out and not been updated, cross-validation is performed using the communication status of the Ethernet channel. If the Ethernet channel can still receive a valid response, the anomaly type is determined to be a preset bus communication anomaly; if both channels fail simultaneously, the anomaly type is determined to be a first controller failure, meaning the first controller is malfunctioning and crashing. For the handshake signal transmitted by the first controller via Ethernet, the second controller can identify the operating status of the thermal management software in the first controller by verifying the random number matching and counter continuity in the handshake signal, thereby obtaining the anomaly type. This dual-channel cross-validation mechanism effectively distinguishes between communication link failures and controller failures, establishing a multi-dimensional status monitoring system and providing accurate judgment criteria for control switching.
[0052] In this embodiment, a large model can be pre-trained. Message information and transmission paths are input into the large model, which outputs the probability of existence for various anomaly types. The anomaly type with the highest probability is determined as the current anomaly type for the first controller. In this embodiment, the model architecture of the large model is not specifically limited.
[0053] S103. Based on the fault type of the first controller, the thermal management component is controlled by the second controller.
[0054] For example, after obtaining the anomaly type of the first controller, it can be determined in which aspect the first controller is unable to control the thermal management component, that is, the part that the second controller needs to take over, so that the second controller can selectively control the thermal management component. That is, for the normal parts of the first controller, the first controller can still perform thermal management control, maintaining the capability of the first controller. In other words, the second controller determines the anomaly type by analyzing the message transmission path and content, and selectively takes over control of the thermal management component based on the determination result.
[0055] For example, if the first controller experiences a CAN communication failure, the second controller can obtain information from the water heater and compressor via the CAN network and then send the received information back to the first controller. The first controller then determines how to control the system and sends control commands to the second controller, which in turn sends them to the water heater and compressor. In other words, only the CAN communication part is handled by the second controller; the thermal management decision-making part is still executed by the first controller.
[0056] This embodiment achieves accurate identification and classification of abnormal states of the first controller, ensuring timely switching of control under different fault modes. When an abnormality is detected in the first controller, the second controller can take over control within milliseconds, preventing the thermal management components from malfunctioning. In communication link failure scenarios, the second controller can temporarily assume the signal relay function, maintaining the control capability of the first controller. This hierarchical fault handling mechanism significantly improves the availability of the thermal management system and effectively prevents the risk of overheating of heat-generating components such as batteries and electric drives due to control interruptions.
[0057] In this embodiment of the invention, two controllers are deployed in the vehicle: a first controller and a second controller. The first controller is preferentially used to control the thermal management components. The first and second controllers can communicate via a preset bus or Ethernet. The first controller can send message information to the second controller through different channels. Based on the content and transmission channel of the message information, it can be determined whether the first controller has an anomaly and the type of anomaly. For different anomaly types, the second controller can take over the thermal management components in different ways, ensuring continuous control of the thermal management components while improving the control accuracy. This achieves reliable control of the vehicle's thermal management, reduces the risk of overheating or even spontaneous combustion, and improves vehicle safety.
[0058] Figure 3 This is a flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention. This embodiment is an optional embodiment based on the above embodiment.
[0059] In this embodiment, determining the anomaly type of the first controller based on the message information and the transmission path of the message information includes: determining the anomaly judgment logic corresponding to the transmission path of the message information based on a preset association relationship; wherein, the preset association relationship represents the association relationship between the transmission path and the anomaly judgment logic, and the anomaly judgment logic is used to determine the anomaly type of the first controller; and determining the anomaly type of the first controller based on the message information and the anomaly judgment logic corresponding to the transmission path of the message information.
[0060] like Figure 3 As shown, the method includes the following steps:
[0061] S301. Receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein, the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller.
[0062] For example, this step can refer to step S101 above, and will not be repeated here.
[0063] S302. Based on a preset association relationship, determine the anomaly judgment logic corresponding to the transmission path of the message information; wherein, the preset association relationship represents the association relationship between the transmission path and the anomaly judgment logic, and the anomaly judgment logic is used to determine the anomaly type of the first controller.
[0064] For example, the preset association relationship refers to the mapping relationship between transmission paths and anomaly judgment logic, whereby the anomaly judgment logic determines the anomaly type of the first controller. Specifically, this can be implemented using a lookup table that maps transmission paths to anomaly judgment logic; for example, an Ethernet path might correspond to handshake verification logic, and a preset bus path might correspond to communication interval detection logic. This association relationship allows anomaly detection for different transmission paths to match corresponding verification mechanisms, improving the accuracy of anomaly type determination.
[0065] In this embodiment, the anomaly judgment logic refers to the controller status verification rules designed for a specific transmission path. The anomaly judgment logic contains verification rules for message information. For example, in an Ethernet path, the operating status of the first controller can be verified by matching the timestamp of the handshake signal or by matching random numbers; in a preset bus path, the communication status of the first controller can be determined by detecting the message information reception interval.
[0066] S303. Based on the message information and the anomaly judgment logic corresponding to the transmission path of the message information, determine the anomaly type of the first controller.
[0067] For example, after determining the corresponding exception judgment logic, the message information is specifically verified according to this logic to obtain the exception type of the first controller. For instance, the exception judgment logic includes message information corresponding to various exception types. The received message information is then judged to determine whether it matches the message information in the exception judgment logic to obtain the corresponding exception type.
[0068] For example, when message information is transmitted via Ethernet, the message information is a handshake signal. By calculating the time difference between sending and receiving the handshake signal and verifying the random number in the handshake signal, it is determined whether the first controller has experienced an operational abnormality. When message information is transmitted via a preset bus, it is determined whether the communication of the preset bus is interrupted by monitoring whether the time interval between receiving two adjacent message information exceeds a threshold. Independent judgment logic is used for different transmission paths, avoiding the risk of misjudging different abnormality types by a single detection mechanism.
[0069] This embodiment solves the problem of misjudgment caused by the single judgment logic of the abnormality type under different transmission paths by establishing the correlation between the transmission path and the abnormal judgment logic. It adds the verification of the controller's operating status in Ethernet communication, realizing the dynamic verification of the controller's operating status in Ethernet communication scenarios. It strengthens the real-time detection in bus communication, realizing the accurate monitoring of the real-time transmission of messages in bus communication scenarios, which improves the identification accuracy of communication link failure and controller failure respectively, effectively distinguishes between controller downtime and bus failure, and ensures the reliability of fault switching control of thermal management system.
[0070] In this embodiment, the transmission path is Ethernet. The message information represents the response signal fed back by the first controller after receiving the handshake signal sent by the second controller. The handshake signal includes a random number and a count value. The count value represents the number of times the second controller sends the handshake signal to the first controller. Based on the message information and the anomaly judgment logic corresponding to the transmission path of the message information, the anomaly type of the first controller is determined, including: determining the sending time of the handshake signal and the receiving time of the response signal by the second controller; if the time difference between the sending time of the handshake signal and the receiving time of the response signal is less than a preset first difference threshold, then the random number and count value in the handshake signal and the random number and count value in the response signal are obtained; if the random number in the handshake signal is inconsistent with the random number in the response signal, or the count value in the handshake signal is inconsistent with the count value in the response signal, then the anomaly type of the first controller is determined to be an operational anomaly; wherein, the operational anomaly represents the first controller crashing.
[0071] Specifically, the handshake signal can refer to a signal sent by the second controller to the first controller to verify the operating status of the first controller. In this embodiment, verifying the operating status of the first controller can refer to verifying the operating status of the thermal management software in the first controller. Upon receiving the handshake signal, the first controller can send back a reply signal, which the second controller can receive. This reply signal is the message information received by the second controller. Both the handshake signal and the reply signal can be transmitted via Ethernet.
[0072] The handshake signal can include dynamically generated random numbers and an incrementing counter value. Generating dynamic random numbers helps prevent signal spoofing. The random number is an unpredictable value generated in each handshake signal, which can be implemented using a pseudo-random number generation algorithm. The random number is used to verify the legitimacy of the reply signal. The counter value is a record of the number of times the second controller has sent handshake signals, which can be implemented using an accumulator counter. It is used to verify whether the reply signal is a valid response for the current session. The handshake signal includes a random number and a counter value, and the reply signal can also include a random number and a counter value. That is, after receiving the handshake signal, the first controller can extract the random number and counter value from the handshake signal, add them to the reply signal, and send it to the second controller.
[0073] Specifically, the second controller periodically sends a handshake signal to the first controller via Ethernet. This signal carries a dynamically generated random number and the current cumulative number of transmissions. Upon receiving the handshake signal, the first controller must return a reply signal containing the same random number and count value within a preset time window. The second controller records the transmission time of the handshake signal and determines the reception time of the reply signal upon receipt, calculating the time difference between the transmission and reception times. A first difference threshold is preset, representing the maximum allowable communication delay. This threshold can be set to a millisecond value, such as 50ms, depending on the network environment, to eliminate misjudgments caused by network fluctuations. If the calculated time difference is less than the first difference threshold, it indicates that the communication delay is within the normal range. In this case, the random number and count value in the reply signal are further compared to those in the handshake signal. If the random number in the handshake signal is inconsistent with the random number in the reply signal, or if the count value in the handshake signal is inconsistent with the count value in the reply signal, the first controller's anomaly type can be considered an operational anomaly, indicating an anomaly in the thermal management software of the first controller. An operational anomaly can signify that the thermal management software of the first controller has crashed and cannot execute. If the random number in the handshake signal is consistent with the random number in the reply signal, and the count value in the handshake signal is consistent with the count value in the reply signal, the thermal management software of the first controller can be considered to be operating normally. When the random numbers do not match, it can be determined that the first controller may have experienced a memory error or restart leading to data loss. When the count values do not match, it can be indicated that the first controller has not correctly processed the current session request. Both of these situations point to an operational anomaly in the first controller, triggering the second controller to take over control. If the calculated time difference is equal to or greater than the first difference threshold, or if the second controller does not receive a reply signal within the first difference threshold, the first controller's anomaly type can be considered an operational anomaly.
[0074] In this embodiment, thermal management limp software can be deployed in the second controller. This software can be a program that determines whether the first controller is malfunctioning and performs thermal management takeover control. The second controller sends a handshake signal to the first controller; that is, the thermal management limp software periodically sends a handshake signal to the thermal management software via Ethernet. The handshake signal contains a random number and a count value generated before each transmission. After receiving the handshake signal, the thermal management software deployed in the first controller needs to send the received random number and count value back to the thermal management limp software deployed in the second controller. If the thermal management limp software receives a reply signal from the thermal management software within a preset timeout period, and the random number and count value in the reply signal are consistent with those sent in the handshake signal, then the thermal management software in the first controller is considered to be operating normally. If the thermal management limp software does not receive a reply signal from the thermal management software within the preset timeout period, or the received random number or count value is incorrect, then the thermal management software in the first controller is considered to be operating abnormally.
[0075] The beneficial effect of this setup is that it constructs a multi-layered anomaly detection mechanism by combining time difference verification and dual data verification. Dynamic random numbers effectively prevent the replay of historical data and the forgery of response signals, incremental count values ensure session continuity and validity, and time difference thresholds eliminate network jitter interference. The synergistic effect of these three elements enables accurate identification of operational anomalies. It also solves the problem of misjudgment of controller failure in Ethernet communication scenarios. When the first controller experiences a software crash, the second controller is promptly triggered to take over, maintaining continuous control of thermal management and avoiding the risk of battery overheating caused by thermal management failure due to misjudgment or missed judgment.
[0076] In this embodiment, the transmission path is a preset bus; based on the message information and the anomaly judgment logic corresponding to the transmission path of the message information, the anomaly type of the first controller is determined, including: determining the message information reception time through the second controller; if the time difference between the message information reception time and the current time is greater than a preset second difference threshold, and no new message information is received, then the anomaly type of the first controller is determined to be a communication anomaly; wherein, the communication anomaly represents the preset bus anomaly of the first controller.
[0077] Specifically, the message reception time refers to the moment when the data packet arrives at the second controller. This can be achieved by using an embedded system clock module to generate a timestamp, which is then used to establish a communication timing reference. The first controller can continuously send CAN network messages through its own terminating resistor. These messages can be used to send monitoring requests to the thermal management components in the CAN network. Upon receiving the messages, the thermal management components in the CAN network can send their own status information back to the first controller. Since the second controller is also in the CAN network, it can also receive messages from the CAN network. The first controller can also continuously send messages according to the message period specified by the CAN bus protocol to verify the continuity of the communication link.
[0078] The second controller can continuously acquire the current time and calculate the time difference between the current time and the reception time of the latest message. A second difference threshold is preset, which refers to the length of a preset time window. Specifically, it can be dynamically adjusted according to the bus load rate, for example, set to 5 seconds, to distinguish between instantaneous communication delays and persistent faults.
[0079] If the time difference exceeds a preset second difference threshold, and the second controller does not receive new message information—that is, if the second controller does not receive new message information within the time limit specified by the second difference threshold for receiving message information—it can be determined that the preset bus of the first controller has malfunctioned, i.e., the malfunction type is communication malfunction. Communication malfunction refers to a persistent fault state at the bus physical layer or protocol layer; for example, it can characterize a substantial interruption of the communication link.
[0080] In other words, the thermal management limp software deployed in the second controller monitors the message information sent by the first controller through CAN, CANFD, LIN and other means. If it finds that the message information of the first controller is not received in any of the three networks of CAN, CANFD and LIN, exceeding the second difference threshold, it is considered that the communication status related to thermal management of the first controller is abnormal.
[0081] The beneficial effect of this setup is that by introducing a message continuity verification mechanism, a dual verification system based on timing characteristics and data flow characteristics is constructed. For example, in scenarios with intermittent bus failures, even if individual messages are lost, as long as a new message arrives within the time window, the system still maintains normal communication status, thereby significantly improving the accuracy of fault identification. It effectively solves the problem of thermal management status monitoring failure caused by abnormal bus communication. Through the dual verification mechanism, it accurately identifies persistent bus faults, ensuring timely triggering of control switching when the communication link is interrupted. This avoids the risk of thermal management system runaway due to loss of status information and maintains the real-time controllability of the thermal management component's operating status.
[0082] In this embodiment, the transmission path is a preset bus. A thermal management sensor is deployed in the first controller. The thermal management sensor is used to collect the working status information of the thermal management component. The message information represents the collected working status information of the thermal management component. Based on the message information and the anomaly judgment logic corresponding to the transmission path of the message information, the anomaly type of the first controller is determined, including: if the second controller determines that the working status information in the message information does not meet the preset conditions, then the anomaly type of the first controller is determined to be a collection anomaly. The collection anomaly represents an anomaly of the thermal management sensor in the first controller.
[0083] Specifically, the preset bus refers to a dedicated data transmission channel within the vehicle used for communication between the controller and the thermal management components. It can be implemented using CAN, CANFD, or LIN buses, and its function is to ensure the stability and real-time performance of data transmission between the controller and the thermal management components. Thermal management sensors are devices used to monitor the operating parameters of the thermal management components. They can be implemented using temperature sensors, pressure sensors, or flow sensors, etc., and their function is to collect real-time information about the operating status of the thermal management components. In this embodiment, the preset bus is CANFD, and the thermal management sensors are pressure sensors and temperature sensors, etc., which can collect data such as compressor outlet pressure, compressor outlet temperature, battery cooler outlet pressure, battery cooler outlet temperature, motor inlet water temperature, and battery inlet water temperature.
[0084] Both the first and second controllers are equipped with thermal management sensors. The thermal management sensor of the first controller is used preferentially. After acquiring the operating status information of the thermal management component, the first controller adds the operating status information to the message information and sends it out through the preset bus. The second controller can receive the message information through the preset bus and extract the operating status information from the message information.
[0085] Preset conditions refer to the parameter ranges pre-defined under normal operating conditions of the thermal management component. These can be implemented using temperature threshold ranges, pressure fluctuation ranges, or flow rate change rates, providing a quantitative standard for determining whether sensor data is abnormal. When the first controller sends the operating status information collected by the thermal management sensor to the second controller via a preset bus, the second controller parses the received message and extracts the parameters of the operating status information. For example, if the thermal management component is a battery cooling system, the preset conditions can be set to a coolant temperature between 20°C and 40°C. If the second controller detects that the coolant temperature value in the message continuously exceeds this range, such as reaching 50°C or falling below 10°C, it determines that the operating status information does not meet the preset conditions. In this case, since the transmission path is the preset bus and the communication link is normal, the cause of the anomaly is identified as a malfunction of the thermal management sensor in the first controller, rather than communication delay or controller malfunction. Therefore, the second controller marks the anomaly type as a data acquisition anomaly, triggering subsequent control strategy adjustments.
[0086] In other words, the thermal management limp-loop software deployed in the second controller monitors the compressor outlet pressure, compressor outlet temperature, battery cooler outlet pressure, battery cooler outlet temperature, motor inlet water temperature, and battery inlet water temperature sent by the thermal management software in the first controller via networks such as CANFD, to determine whether the sensor acquisition status related to thermal management in the first controller is abnormal. The first controller can also, after receiving the operating status information of the thermal management components, determine whether there is an acquisition anomaly based on preset conditions before sending the judgment result to the second controller. For example, if the thermal management limp-loop software deployed in the second controller detects via CANFD that the thermal management software in the first controller has sent a compressor outlet pressure fault, compressor outlet temperature fault, battery cooler outlet pressure fault, battery cooler outlet temperature fault, motor inlet water temperature fault, or battery inlet water temperature fault, then it considers the sensor acquisition status related to thermal management in the first controller to be abnormal.
[0087] The advantage of this setup is that, through a joint judgment mechanism using preset bus transmission paths and preset conditions, data anomalies and communication anomalies are decoupled, allowing sensor faults to be identified independently. This enables rapid diagnosis and isolation of thermal management sensor faults, avoiding misjudgments of the thermal management component's status due to sensor failure. When the sensor in the first controller experiences drift, open circuit, or data distortion, the second controller can accurately identify the source of the anomaly and immediately activate backup control strategies, such as switching to the sensor built into the second controller for data acquisition, thereby maintaining the basic operational control of the thermal management component and preventing safety hazards caused by temperature runaway in the battery or electric drive system.
[0088] S304. Based on the fault type of the first controller, the thermal management component is controlled by the second controller.
[0089] For example, this step can refer to step S103 above, and will not be repeated here.
[0090] In this embodiment of the invention, two controllers are deployed in the vehicle: a first controller and a second controller. The first controller is preferentially used to control the thermal management components. The first and second controllers can communicate via a preset bus or Ethernet. The first controller can send message information to the second controller through different channels. Based on the content and transmission channel of the message information, it can be determined whether the first controller has an anomaly and the type of anomaly. For different anomaly types, the second controller can take over the thermal management components in different ways, ensuring continuous control of the thermal management components while improving the control accuracy. This achieves reliable control of the vehicle's thermal management, reduces the risk of overheating or even spontaneous combustion, and improves vehicle safety.
[0091] Figure 4 This is a flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention. This embodiment is an optional embodiment based on the above embodiment.
[0092] In this embodiment, a thermal management sensor is deployed in the second controller. The thermal management sensor is used to collect the operating status information of the thermal management component, including the temperature information of the thermal management component. According to the anomaly type of the first controller, the second controller controls the thermal management component, including: if the anomaly type of the first controller is an operational anomaly, the thermal management sensor in the second controller collects the operating status information of the thermal management component; if the temperature information in the operating status information of the thermal management component is greater than a preset temperature threshold, the second controller sends a control signal to the thermal management component based on a preset bus; wherein, the control signal is used to control the thermal management component.
[0093] like Figure 4 As shown, the method includes the following steps:
[0094] S401. Receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein, the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller.
[0095] For example, this step can refer to step S101 above, and will not be repeated here.
[0096] S402. Determine the anomaly type of the first controller based on the message information and the transmission path of the message information.
[0097] For example, this step can refer to step S102 above, and will not be repeated here.
[0098] S403. If the anomaly type of the first controller is an operational anomaly, the working status information of the thermal management component is collected through the thermal management sensor in the second controller.
[0099] For example, a thermal management sensor refers to a temperature detection device, pressure detection device, or other sensor deployed in the second controller. Specifically, it can be implemented using thermocouples or thermistors, and is used to directly acquire real-time temperature and pressure data of the thermal management component. In this embodiment, the thermal management sensor can refer to a temperature sensor that can collect temperature information from the thermal management component.
[0100] When the anomaly type of the first controller is determined to be an operational anomaly, it can be assumed that the thermal management software in the first controller has completely crashed. In this case, the second controller takes over control of the thermal management component. The second controller can collect the operating status information of the thermal management component through thermal management sensors. The operating status information can include the temperature information of the thermal management component, that is, the current temperature of the thermal management component.
[0101] S404. If the temperature information in the working status information of the thermal management component is greater than the preset temperature threshold, then the second controller sends a control signal to the thermal management component based on the preset bus; wherein, the control signal is used to control the thermal management component.
[0102] For example, a temperature threshold is preset. This preset temperature threshold refers to a pre-defined safe temperature critical value, which can be determined through experimental testing or theoretical calculation. For instance, it can be set to 60 degrees Celsius. The preset temperature threshold can be used to determine whether emergency control needs to be activated. The preset bus refers to a communication link independent of the first controller. It can be implemented using a CAN bus, CANFD bus, or LIN bus, etc., to ensure that signal transmission between the second controller and the thermal management component is not affected by a failure of the first controller. The control signal refers to the instruction used to adjust the operating state of the thermal management component. It can be implemented using PWM signals or digital switch signals. For example, the control signal can control the speed of the cooling fan or the start / stop of the cooling pump.
[0103] When the first controller malfunctions and fails to operate normally, the thermal management sensor integrated within the second controller is activated to continuously collect the operating status information of the thermal management component. The second controller acquires the temperature information from this status information and compares it to a preset temperature threshold. When the detected temperature exceeds the preset threshold, the second controller sends a control signal to the thermal management component whose temperature exceeds the threshold via a preset bus. In other words, the control signal can be sent directly to the thermal management component via a separate communication link. This process bypasses the malfunctioning first controller, forming a closed-loop control system through the second controller's built-in sensor and dedicated communication channel, ensuring timely cooling operations in emergency situations.
[0104] In other words, the thermal management limp-loop software of the second controller collects data such as compressor outlet pressure, compressor outlet temperature, battery cooler outlet pressure, battery cooler outlet temperature, motor inlet water temperature, and battery inlet water temperature. When the temperature exceeds the expected threshold, the thermal management limp-loop software can send control signals to the automatic grille, evaporator electronic expansion valve, battery cooling electronic expansion valve, multi-way valve, and compressor via buses such as LIN, to control the temperature. The thermal management limp-loop software can also accept all thermal management request signals related to the front electric drive, rear electric drive, power system, and battery system from buses such as CANFD. When a thermal management request signal is received, the management limp-loop software sends control signals to the automatic grille, evaporator electronic expansion valve, battery cooling electronic expansion valve, multi-way valve via LIN, and to the compressor via CAN, to control the temperature of the electric drive, power supply, and battery systems within a suitable range. The thermal management request signal is an active signal from the three electric systems to control the temperature.
[0105] This embodiment integrates independent sensors into the second controller, enabling direct monitoring of the thermal management component's operating status and avoiding data link disruptions caused by main controller failure. Simultaneously, a dedicated bus is used for control signal transmission, eliminating the impact of main controller communication anomalies on emergency control paths. This ensures effective control based on real-time temperature data even in the event of complete main controller failure, preventing thermal management component malfunction due to overheating. The independent sensor acquisition and communication link design ensures the redundancy and reliability of the control system, avoiding the risk of thermal runaway caused by a single controller failure.
[0106] In this embodiment, a microprocessor (MCU) and a cooling device are deployed in the vehicle. The MCU is used to send pulse width modulation (PWM) signals, and the cooling device is connected to a first controller. The cooling device is used to cool the thermal management components by rotating. The method also includes: if the first controller has an abnormality type of operation abnormality, the MCU sends a PWM signal to the cooling device; wherein the PWM signal is used to control the rotation of the cooling device.
[0107] Specifically, the first controller deploys thermal management limp-out hardware, which is a hardware device that can take over thermal management control when the thermal management software crashes. This thermal management limp-out hardware includes an MCU (Microcontroller Unit), an embedded control chip with independent computing capabilities. Its independent power supply and computing characteristics can mitigate the impact of first controller software failures. The first controller is externally connected to various cooling devices, such as cooling fans, electric cooling water pumps, battery-powered cooling water pumps, and heating water pumps. The MCU can be directly connected to the drive modules of these cooling devices via hardware circuitry, forming a signal transmission channel independent of the thermal management software.
[0108] Figure 5 This is a schematic diagram of the vehicle's thermal management system. Figure 5 As shown, in the vehicle's thermal management system, the first controller is connected to the HPC via Ethernet, the first controller and the second controller are connected via Ethernet, and the second controller and the HPC are connected via Ethernet. The first controller, the second controller, and the central computer (HPC) are connected to form a ring Ethernet communication link, ensuring that there is a communication link between any two of these three components, thus improving redundancy.
[0109] The first controller, the second controller, the WPTC (water heater), and the ACP (compressor) are connected and communicate with each other via a CAN network. Termination resistors are set on the first controller and the second controller, respectively. Both the first controller and the second controller can receive signals from the WPTC and the ACP, and can also send control signals to the WPTC and the ACP.
[0110] The first controller, second controller, FMIPU (Front Drive Controller), RMIPU (Rear Drive Controller), PDU (Power Controller), and BCU (Battery Management Unit) are connected and communicate with each other via a CANFD network. Termination resistors are set on the first and second controllers respectively. Both the first and second controllers can receive signals from the FMIPU, RMIPU, PDU, and BCU.
[0111] The first controller, the second controller, AGS (Automatic Grille), EEXV (Evaporator Electronic Expansion Valve), CEXV (Battery Cooling Electronic Expansion Valve), and MTV (Multi-way Valve) are interconnected and communicate with each other via LIN. Both the first and second controllers can receive signals from AGS, EEXV, CEXV, and MTV, and can also send control signals to AGS, EEXV, CEXV, and MTV.
[0112] ACoP (compressor outlet pressure sensor), ACoT (compressor outlet temperature sensor), ChlroP (battery cooler outlet pressure sensor), ChlroT (battery cooler outlet temperature sensor), MotInT (motor inlet water temperature sensor), and HVBatInT (battery inlet water temperature sensor) are simultaneously connected to the first controller and the second controller. Both the first controller and the second controller can collect the signals from the above sensors.
[0113] The thermal management limp-out hardware is located on the first controller. When the thermal management software on the first controller crashes, the thermal management limp-out hardware takes over control. The CoolingFan, MotorPump, HVBatPump, and HeatPump, all driven by PWM signals, are connected to the first controller. When the thermal management software of the first controller crashes, the thermal management limp-out hardware starts working, driving the CoolingFan, MotorPump, HVBatPump, and HeatPump to rotate at high speed according to the preset PWM frequency and duty cycle.
[0114] The control terminal of the single-pole double-throw relay of the HtThrWValv (heating tee) is connected to the first controller. The bridge drive output signal of the HtThrWValv is switched between the first and second controllers by the single-pole double-throw relay. The thermal management software is deployed on the first controller, and the thermal management limp-out software is deployed on the second controller.
[0115] PWM (Pulse Width Modulation) signals are electrical signals that control the power output of a device by adjusting its duty cycle. Specifically, they can be implemented using square wave signals with a frequency of 10kHz-20kHz. This signal type is compatible with the motor drive circuit built into the cooling device. In other words, a PWM signal can refer to a square wave signal that controls the device's power by adjusting its duty cycle. Specifically, a timer module can generate electrical signals with variable duty cycles to achieve precise adjustment of the cooling device's speed. The cooling device can simultaneously connect to the hardware interfaces of both the first controller and the microprocessor. Specifically, a relay switching circuit can be used to switch control, retaining the normal control authority of the first controller while establishing an emergency control channel, thus achieving a dual-access architecture.
[0116] When a malfunction is detected in the first controller, i.e., a failure of the thermal management software control function, the MCU of the thermal management limp hardware immediately initiates a hardware-level emergency control procedure. The MCU generates a PWM signal of a preset frequency via a built-in timer, which is transmitted to the motor drive module of the cooling unit through an isolation circuit. Since the PWM signal directly affects the motor speed control circuit, it eliminates the need for software parsing by the first controller, triggering the cooling unit to enter basic operating mode within milliseconds. The cooling unit maintains its minimum speed based on the received preset duty cycle PWM signal, thus ensuring that the thermal management components still receive basic heat dissipation even under extreme conditions.
[0117] Figure 6 This is a schematic diagram of the thermal management limp-out hardware. The thermal management limp-out hardware is located on the first controller. Figure 6 As shown, the thermal management limp hardware mainly includes an MCU (microprocessor), an SBC (system base chip), a TIMER (timer), four AngSw (analog switches), one AND gate, and five LSD (low-side drivers). The four analog switches are AngSw1, AngSw2, AngSw3, and AngSw4, and the five low-side drivers are LSD1, LSD2, LSD3, LSD4, and LSD5. The specific connection relationship is as follows:
[0118] The MCU's PWM_O6 output is connected to the WKAKE input of the system base chip SBC. The MCU's PWM_O1 output is connected to the NC pin of analog switch AngSw1. The MCU's PWM_O2 output is connected to the NC pin of analog switch AngSw2. The MCU's PWM_O3 output is connected to the NC pin of analog switch AngSw3. The MCU's PWM_O4 output is connected to the NC pin of analog switch AngSw4. The MCU's PWM_O5 output is connected to pin 1A of the AND gate.
[0119] The fault output port FO (output signal network PWM_KEEP) of the system base chip SBC is connected to the 1B input of the AND gate.
[0120] The fault output port FO (output signal network PWM_KEEP) of the system base chip SBC is connected to the common terminal of the lower end of resistor R48, the left end of resistor R51, and the left end of resistor R53; the common terminal of the upper end of resistor R48 and the upper end of resistor R47 is connected to the power supply VCC. The right end of resistor R51, the lower end of resistor R47, and the collector of transistor Q4 are connected to and output the signal network PWM_KEEP_N. The signal network PWM_KEEP_N is connected to the VIN pins of analog switches AngSw1, AngSw2, AngSw3, and AngSw4, respectively. The right end of resistor R53 is connected to the base of transistor Q4. The emitter of transistor Q4 is connected to ground GND.
[0121] The TRIG and THRE pins of the timer are connected to the lower end of resistor R55 and the upper end of capacitor C34. The upper end of resistor R55 is connected to the DISC pin of the timer and the lower end of resistor R49. The upper end of resistor R49 is connected to the power supply VCC. The lower end of capacitor C34 is connected to ground GND. The CONT pin of the timer is connected to the upper end of capacitor C35, and the lower end of capacitor C35 is connected to ground. The VDD pin of the timer is connected to VCC. The RESRT pin of the timer is connected to the PWM_KEEP_N signal network. The OUT pin of the timer is connected to the left end of resistor R52. The right end of resistor R52 is connected to the upper end of resistor R57 and the base of transistor Q3. The collector of transistor Q3 is connected to the lower end of resistor R46 and outputs a signal network, which can be called PWMFSpdLimpCtrl_TmrO. This signal network PWMFSpdLimpCtrl_TmrO is connected to the NO pins of analog switches AngSw1, AngSw2, AngSw3, and AngSw4, respectively. The emitter of transistor Q3 is connected to ground (GND). The upper end of resistor R46 is connected to VCC.
[0122] The VCC pin of analog switch AngSw1 is connected to VCC and the upper end of capacitor C34, while the lower end of capacitor C34 is connected to ground (GND). The COM pin of analog switch AngSw1 is connected to the left end of resistor R79, and the right end of resistor R79 is connected to the G pin of low-side driver LSD1. The GND pin of analog switch AngSw1 is connected to ground (GND).
[0123] The VCC pin of analog switch AngSw2 is connected to VCC and the upper end of capacitor C35, while the lower end of capacitor C35 is connected to ground (GND). The COM pin of analog switch AngSw2 is connected to the left end of resistor R80, and the right end of resistor R80 is connected to the G pin of low-side driver LSD2. The GND pin of analog switch AngSw2 is connected to ground (GND).
[0124] The VCC pin of analog switch AngSw3 is connected to VCC and the upper end of capacitor C36, while the lower end of capacitor C36 is connected to ground (GND). The COM pin of analog switch AngSw3 is connected to the left end of resistor R81, and the right end of resistor R81 is connected to the G pin of low-side driver LSD3. The GND pin of analog switch AngSw3 is connected to ground (GND).
[0125] The VCC pin of analog switch AngSw4 is connected to VCC and the upper end of capacitor C37, while the lower end of capacitor C37 is connected to ground (GND). The COM pin of analog switch AngSw4 is connected to the left end of resistor R82, and the right end of resistor R82 is connected to the G pin of low-side driver LSD4. The GND pin of analog switch AngSw4 is connected to ground (GND).
[0126] The VCC pin of the AND gate is connected to VCC and the upper end of C38. The GND pin of the AND gate is connected to the lower end of C38 and ground (GND). The 1Y pin of the AND gate is connected to the upper end of resistor R73 and the left end of resistor R71. The lower end of resistor R73 is connected to GND. The right end of resistor R71 is connected to the G pin of LSD5.
[0127] The S pin of the low-side driver LSD1 is connected to ground (GND), and the D pin of the low-side driver LSD1 is connected to the lower end of resistor R75 and the upper end of capacitor D23, outputting a signal network that can be used as PWMFFanSpdCtrl_O. The upper end of resistor R75 is connected to VCC, and the lower end of capacitor D23 is connected to ground (GND).
[0128] The S pin of the low-side driver LSD2 is connected to ground (GND), and the D pin of the low-side driver LSD2 is connected to the lower end of resistor R76 and the upper end of capacitor D24, outputting a signal network as MotorPumpSpdCtrl_O. The upper end of resistor R76 is connected to VCC, and the lower end of capacitor D24 is connected to ground (GND).
[0129] The S pin of the low-side driver LSD3 is connected to ground (GND), and the D pin of the low-side driver LSD3 is connected to the lower end of resistor R77 and the upper end of capacitor D25, and outputs the signal network HVBatPumpSpdCtrl_O. The upper end of resistor R77 is connected to VCC, and the lower end of capacitor D25 is connected to ground (GND).
[0130] The S pin of the low-side driver LSD4 is connected to ground (GND), and the D pin of the low-side driver LSD4 is connected to the lower end of resistor R78 and the upper end of capacitor D26, forming an output signal network as HeatPumpSpdCtrl_O. The upper end of resistor R78 is connected to VCC, and the lower end of capacitor D26 is connected to ground (GND).
[0131] The S pin of the low-side driver LSD5 is connected to ground (GND), and the D pin of the low-side driver LSD5 is connected to the lower end of resistor R68 and the upper end of capacitor C38, and outputs the signal network HeatThrVlvRlyCtrl_O. The upper end of resistor R68 is connected to VCC, and the lower end of capacitor C38 is connected to ground (GND).
[0132] like Figure 6 As shown, when the software deployed on the first controller is running normally, the MCU's PWM_O6 outputs a high level to the WAKE pin of the system base chip SBC. The SBC detects the high level input on the WAKE pin, and the SBC's fault output pin FO outputs the PWM_KEEP signal network as high, the transistor Q4 is turned on, and the signal network PWM_KEEP_N is low.
[0133] Because the signal network PWM_KEEP_N is low, the COM output of analog switch AngSw1 is the PWMFFanSpdCtrl_MCUO signal network output by the MCU's PWM_O1 pin, and drives LSD1 to output the cooling fan control signal PWMFFanSpdCtrl_O.
[0134] Because the signal network PWM_KEEP_N is low, the COM output of analog switch AngSw2 is the MotorPumpSpdCtrl_MCUO signal network output by the PWM_O2 pin of the MCU, and drives LSD2 to output the electric drive cooling water pump control signal MotorPumpSpdCtrl_O.
[0135] Because the signal network PWM_KEEP_N is low, the COM output of the analog switch AngSw3 is the HVBatPumpSpdCtrl_MCUO signal network output by the MCU's PWM_O3 pin, and drives LSD3 to output the battery cooling water pump control signal HVBatPumpSpdCtrl_O.
[0136] Because the signal network PWM_KEEP_N is low, the COM output of the analog switch AngSw4 is the HeatPumpSpdCtrl_MCUO signal network output by the MCU's PWM_O4 pin, and drives LSD4 to output the heating water pump control signal HeatPumpSpdCtrl_O.
[0137] Because the signal network PWM_KEEP is high, the 1Y output of the AND gate outputs the HeatThrVlvRlyCtrl_MCUO signal (high level) according to the MCU's PWM_O5, which drives LSD5 to output the heating three-way relay control signal HeatThrVlvRlyCtrl_O. The heating three-way relay control signal HeatThrVlvRlyCtrl_O is low level to control the relay to be energized. At this time, the first controller controls the rotation of the heating three-way.
[0138] When the software deployed on the first controller crashes, the MCU's PWM_O6 outputs a low level to the WAKE pin of the system base chip SBC. The SBC detects the low level input on the WAKE pin, and the SBC's fault output pin FO outputs the PWM_KEEP signal network at a low level. Transistor Q4 is not turned on, and the signal network PWM_KEEP_N is at a high level.
[0139] Because the signal network PWM_KEEP_N is high, the COM output of analog switch AngSw1 controls the PWMFSpdLimpCtrl_TmrO signal network output of transistor Q3 collector according to the OUT pin of timer TIMER, and drives LSD1 to output the cooling fan control signal PWMFFanSpdCtrl_O, controlling the cooling fan to run at high speed according to the frequency and duty cycle set by the limp hardware.
[0140] Because the signal network PWM_KEEP_N is high, the COM output of analog switch AngSw2 controls the PWMFSpdLimpCtrl_TmrO signal network output of transistor Q3 collector according to the OUT pin of timer TIMER, and drives LSD2 to output the electric drive cooling water pump control signal MotorPumpSpdCtrl_O, controlling the electric drive cooling water pump to run at high speed according to the frequency and duty cycle set by the limp hardware.
[0141] Because the signal network PWM_KEEP_N is high, the COM output of analog switch AngSw3 controls the PWMFSpdLimpCtrl_TmrO signal network output of transistor Q3 collector according to the OUT pin of timer TIMER, and drives LSD3 to output the battery cooling water pump control signal HVBatPumpSpdCtrl_O, controlling the battery cooling water pump to run at high speed according to the frequency and duty cycle set by the limp hardware.
[0142] Because the signal network PWM_KEEP_N is high, the COM output of the analog switch AngSw4 controls the PWMFSpdLimpCtrl_TmrO signal network output of the collector of transistor Q3 according to the OUT pin of the timer TIMER, and drives LSD4 to output the heating water pump control signal HeatPumpSpdCtrl_O, controlling the heating water pump to run at high speed according to the frequency and duty cycle set by the limp hardware.
[0143] Because the signal network PWM_KEEP is low, the 1Y output of the AND gate is low, and the LSD5 output heating tee relay control signal HeatThrVlvRlyCtrl_O is high, the control relay is not energized, and the first controller controls the rotation of the heating tee.
[0144] The advantage of this setup is that by establishing an independent hardware control layer, redundant transmission of control signals is achieved at the physical circuit level, ensuring that the cooling device can still receive drive signals even when the thermal management software completely fails. This hardware-level emergency mechanism overcomes the response speed limitations of traditional software fault-tolerant solutions, effectively solving the problem of heat dissipation interruption caused by controller software anomalies. It ensures that the cooling device maintains its basic heat dissipation function, preventing a rapid temperature rise in the thermal management components due to heat dissipation interruption. This technical solution bypasses the impact of software system failure through an independent hardware control channel, maintaining the safe operation of the thermal management system even under extreme conditions of complete thermal management software shutdown, without relying on the software functions or communication bus status of the first controller.
[0145] In this embodiment of the invention, two controllers are deployed in the vehicle: a first controller and a second controller. The first controller is preferentially used to control the thermal management components. The first and second controllers can communicate via a preset bus or Ethernet. The first controller can send message information to the second controller through different channels. Based on the content and transmission channel of the message information, it can be determined whether the first controller has an anomaly and the type of anomaly. For different anomaly types, the second controller can take over the thermal management components in different ways, ensuring continuous control of the thermal management components while improving the control accuracy. This achieves reliable control of the vehicle's thermal management, reduces the risk of overheating or even spontaneous combustion, and improves vehicle safety.
[0146] Figure 7 This is a flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention. This embodiment is an optional embodiment based on the above embodiment.
[0147] In this embodiment, the thermal management component is controlled by the second controller according to the anomaly type of the first controller. This includes: if the anomaly type of the first controller is a communication anomaly, the second controller acquires the demand signal emitted by the thermal management component based on a preset bus and sends the demand signal to the first controller via Ethernet; wherein the demand signal represents the control demand of the thermal management component for itself; the first controller determines a control signal based on the demand signal and sends the control signal to the second controller via Ethernet; wherein the control signal is used to control the thermal management component; and the second controller sends the control signal to the thermal management component based on the preset bus.
[0148] like Figure 7 As shown, the method includes the following steps:
[0149] S701. Receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein, the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller.
[0150] For example, this step can refer to step S101 above, and will not be repeated here.
[0151] S702. Determine the anomaly type of the first controller based on the message information and the transmission path of the message information.
[0152] For example, this step can refer to step S102 above, and will not be repeated here.
[0153] S703. If the anomaly type of the first controller is a communication anomaly, then the second controller acquires the demand signal issued by the thermal management component based on the preset bus, and sends the demand signal to the first controller via Ethernet; wherein, the demand signal represents the control demand of the thermal management component for itself.
[0154] For example, a communication anomaly refers to a failure in the pre-defined bus communication link between the first controller and the thermal management component. For instance, this could be due to a faulty terminating resistor at the first controller. A demand signal refers to a request for its own operating parameters actively issued by the thermal management component, i.e., a real-time control request from the thermal management component. For example, the thermal management component can encode the request signal using the standard data frame format in the CAN bus and then transmit it through the CAN network. The demand signal can include control parameters such as coolant flow rate requests and cooling fan speed setpoints. The second controller is also connected to the thermal management component via the pre-defined bus; therefore, the second controller can also receive the demand signal from the thermal management component. If the first controller's communication is normal, it will process the received demand signal. While the second controller can also receive the demand signal, it will not process it.
[0155] The second controller continuously captures the demand signals emitted by the thermal management component. When a communication anomaly is detected in the first controller, since the first controller only has a communication anomaly and the thermal management software can still operate normally, the second controller can transmit the demand signal to the first controller via Ethernet after receiving the demand signal, for example, it can be transmitted to the thermal management software of the first controller.
[0156] For example, if CANFD communication fails, the thermal management limp software of the second controller forwards the thermal management demand signals of the front electric drive controller, rear electric drive controller, power controller, and high-voltage battery management system on the CANFD to the thermal management software in the first controller via Ethernet, and the thermal management software in the first controller can continue to work normally.
[0157] If CAN communication fails, the second controller can forward the demand signals from the water heater and compressor on the CAN bus to the thermal management software in the first controller via Ethernet. The first controller can also send the signals sent to the water heater and compressor to the thermal management limp software in the second controller via Ethernet. The thermal management limp software then sends the signals to the water heater and compressor via CAN, and the thermal management software can continue to work normally.
[0158] If LIN communication fails, the thermal management limp software can forward the demand signals sent by the automatic grille, evaporator electronic expansion valve, battery cooling electronic expansion valve, and multi-way valve on the LIN to the thermal management software in the first controller via Ethernet. The first controller then sends the signals sent to the electronic expansion valve, battery cooling electronic expansion valve, and multi-way valve to the thermal management limp software in the second controller via Ethernet. The thermal management limp software then sends the signals to the automatic grille, evaporator electronic expansion valve, battery cooling electronic expansion valve, and multi-way valve via LIN, and the thermal management software can continue to work normally.
[0159] S704. The first controller determines the control signal based on the demand signal and sends the control signal to the second controller via Ethernet; wherein the control signal is used to control the thermal management component.
[0160] For example, the first controller maintains normal operational functions and generates corresponding control signals based on the received demand signals. For instance, it can calculate the PWM duty cycle parameters that meet the heat dissipation requirements. The control signals can be instructions for controlling the thermal management components. In this embodiment, the process of determining the control signals, i.e., the logic of the thermal management software, is not specifically limited.
[0161] The first controller returns the control signal to the second controller via Ethernet. That is, after receiving the control signal, the first controller does not directly control the thermal management component, but controls it through the second controller.
[0162] S705: Through the second controller, control signals are sent to the thermal management component based on the preset bus.
[0163] For example, the second controller receives a control signal, converts it into a preset bus protocol format, and sends the control signal to the actuator of the thermal management component through a preset bus physical layer interface, thereby forming a complete closed-loop control circuit. The thermal management component receives the control signal and adjusts its own parameters accordingly.
[0164] Traditional solutions typically switch directly to a backup controller for full-function takeover in the event of a bus communication failure, resulting in idle computing resources for the main controller. This embodiment addresses this by constructing a dual-channel collaborative mechanism. While maintaining the computing power of the first controller, the second controller performs signal relay functionality under abnormal conditions. This effectively solves the problem of thermal management runaway caused by pre-set bus communication anomalies, maintaining closed-loop control of the thermal management components even in the event of a bus link failure. Bidirectional transmission of demand and control signals is achieved via an Ethernet channel, ensuring full utilization of the first controller's computing resources while avoiding system reconfiguration delays caused by the second controller's full-function takeover. This improves the operational reliability of the thermal management system under communication anomalies and ensures the temperature control stability of critical heat-generating components.
[0165] In this embodiment of the invention, two controllers are deployed in the vehicle: a first controller and a second controller. The first controller is preferentially used to control the thermal management components. The first and second controllers can communicate via a preset bus or Ethernet. The first controller can send message information to the second controller through different channels. Based on the content and transmission channel of the message information, it can be determined whether the first controller has an anomaly and the type of anomaly. For different anomaly types, the second controller can take over the thermal management components in different ways, ensuring continuous control of the thermal management components while improving the control accuracy. This achieves reliable control of the vehicle's thermal management, reduces the risk of overheating or even spontaneous combustion, and improves vehicle safety.
[0166] Figure 8 This is a flowchart illustrating a vehicle thermal management control method provided in an embodiment of the present invention. This embodiment is an optional embodiment based on the above embodiment.
[0167] In this embodiment, a thermal management sensor is deployed in the second controller. The thermal management sensor is used to collect the operating status information of the thermal management component. According to the anomaly type of the first controller, the second controller controls the thermal management component, including: if the anomaly type of the first controller is a collection anomaly, the thermal management sensor in the second controller collects the operating status information of the thermal management component and sends the collected operating status information to the first controller via Ethernet; the first controller sends a control signal to the thermal management component according to the operating status information of the thermal management component; wherein, the control signal is used to control the thermal management component.
[0168] like Figure 8 As shown, the method includes the following steps:
[0169] S801. Receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein, the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller.
[0170] For example, this step can refer to step S101 above, and will not be repeated here.
[0171] S802. Determine the anomaly type of the first controller based on the message information and the transmission path of the message information.
[0172] For example, this step can refer to step S102 above, and will not be repeated here.
[0173] S803. If the anomaly type of the first controller is acquisition anomaly, the working status information of the thermal management component is acquired through the thermal management sensor in the second controller, and the acquired working status information is sent to the first controller via Ethernet.
[0174] For example, the thermal management sensor is used to collect the operating status information of the thermal management component, which is the current operating status of the thermal management component. A data acquisition anomaly refers to a malfunction of the thermal management sensor inside the first controller, resulting in the inability to acquire valid data from the thermal management component. This anomaly can be identified by pre-setting bus communication timeouts or data verification failures. For instance, a pre-set bus message reception interval threshold judgment mechanism can be used; if no valid operating status information is received for three consecutive communication cycles, an anomaly judgment is triggered. The thermal management sensor is a device used to monitor the operating parameters of the thermal management component, which characterize the operating status. Specifically, it can be implemented using a combination of temperature sensors, pressure sensors, or flow sensors. The thermal management sensor deployed in the second controller can have the same measurement range and accuracy level as the thermal management sensor in the first controller.
[0175] When the first controller fails to acquire the operating status information of the thermal management components due to sensor malfunction, the thermal management sensor in the second controller immediately activates its data acquisition function. The acquired parameters, such as temperature and pressure, are transmitted to the thermal management software of the first controller via Ethernet. Since the first controller only experiences an acquisition malfunction, while the thermal management software can still operate normally, the second controller, upon receiving the operating status information, can transmit this information back to the first controller via Ethernet; that is, it can send it to the thermal management software of the first controller.
[0176] In other words, the thermal management limp software of the second controller collects information such as compressor outlet pressure, compressor outlet temperature, battery cooler outlet pressure, battery cooler outlet temperature, motor inlet water temperature, and battery inlet water temperature, and forwards it to the thermal management software in the first controller via Ethernet, so that the thermal management software in the first controller can continue to work normally.
[0177] S804. The first controller sends a control signal to the thermal management component based on the working status information of the thermal management component; wherein the control signal is used to control the thermal management component.
[0178] For example, since the thermal management software of the first controller does not malfunction, it can execute existing control logic to generate control signals based on the received information. These control signals are sent to the corresponding thermal management component actuators via a preset bus, such as a cooling water pump or a cooling fan. During this process, the first controller maintains direct control over the thermal management components, with only the data source switching to the thermal management sensor of the second controller, thus avoiding the system oscillation risk caused by the switch in control.
[0179] Traditional thermal management systems typically switch directly to a backup controller for full-function takeover when a sensor failure is detected in the main controller. This requires the backup controller to have complete control algorithms and hardware interfaces, significantly increasing system complexity. In contrast, this embodiment uses cross-controller data transmission of sensor data, enabling the first controller to maintain its original control logic based on the second controller even when a sensor fails. This reduces the configuration requirements for the second controller and avoids issues such as actuator response delays that may arise from control strategy switching.
[0180] Through the above technical solution, this embodiment can continuously provide effective monitoring data using the thermal management sensor of the second controller when the thermal management sensor of the first controller fails, ensuring that the generation of thermal management control commands is not affected by the failure of a single sensor. By maintaining the control master status of the first controller, the risk of system instability caused by control switching is avoided. At the same time, the high bandwidth characteristics of Ethernet ensure the real-time data transmission across controllers, enabling the thermal management system to maintain continuous and stable operation even when the sensor layer fails.
[0181] In this embodiment of the invention, two controllers are deployed in the vehicle: a first controller and a second controller. The first controller is preferentially used to control the thermal management components. The first and second controllers can communicate via a preset bus or Ethernet. The first controller can send message information to the second controller through different channels. Based on the content and transmission channel of the message information, it can be determined whether the first controller has an anomaly and the type of anomaly. For different anomaly types, the second controller can take over the thermal management components in different ways, ensuring continuous control of the thermal management components while improving the control accuracy. This achieves reliable control of the vehicle's thermal management, reduces the risk of overheating or even spontaneous combustion, and improves vehicle safety.
[0182] Figure 9 This is a structural block diagram of a vehicle thermal management control device provided in an embodiment of the present invention. For ease of explanation, only the parts relevant to the embodiments of this disclosure are shown. The device is applied to a vehicle, which includes a first controller, a second controller, and a thermal management component. The thermal management component is communicatively connected to the first and second controllers via a preset bus. The first and second controllers are communicatively connected via Ethernet. The first controller controls the thermal management component, and the second controller takes over control of the thermal management component when the first controller malfunctions. (Refer to...) Figure 9 The vehicle thermal management control device 900 includes: a path determination unit 901, a type determination unit 902, and a thermal management control unit 903.
[0183] The path determination unit 901 is used to receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller;
[0184] The type determination unit 902 is used to determine the anomaly type of the first controller based on the message information and the transmission path of the message information;
[0185] The thermal management control unit 903 is used to control the thermal management component via the second controller according to the fault type of the first controller.
[0186] In one example, type determination unit 902 includes:
[0187] The path determination unit is used to receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller;
[0188] A type determination unit is used to determine the anomaly type of the first controller based on the message information and the transmission path of the message information;
[0189] A thermal management control unit is used to control the thermal management component via a second controller based on the anomaly type detected by the first controller.
[0190] A logic determination module is used to determine the anomaly judgment logic corresponding to the transmission path of the message information based on a preset association relationship; wherein, the preset association relationship represents the association relationship between the transmission path and the anomaly judgment logic, and the anomaly judgment logic is used to determine the anomaly type of the first controller.
[0191] The type determination module is used to determine the exception type of the first controller based on the message information and the exception judgment logic corresponding to the transmission path of the message information.
[0192] In one example, the transmission path is Ethernet, and the message information represents the response signal fed back by the first controller after receiving the handshake signal from the second controller. The handshake signal includes a random number and a count value, and the count value represents the number of times the second controller sends the handshake signal to the first controller. The type determination module is specifically used for:
[0193] The second controller determines the sending time of the handshake signal and the receiving time of the reply signal.
[0194] If the time difference between the sending time of the handshake signal and the receiving time of the reply signal is less than a preset first difference threshold, then the random number and count value in the handshake signal and the random number and count value in the reply signal are obtained.
[0195] If the random number in the handshake signal is inconsistent with the random number in the reply signal, or the count value in the handshake signal is inconsistent with the count value in the reply signal, then the abnormality type of the first controller is determined to be an operational abnormality; wherein, the operational abnormality indicates that the first controller has crashed.
[0196] In one example, the transmission path is a preset bus; the type determination module is specifically used for:
[0197] The second controller determines the reception time of the message information.
[0198] If the time difference between the received message and the current time is greater than a preset second difference threshold, and no new message is received, then the abnormality type of the first controller is determined to be a communication abnormality; wherein, the communication abnormality represents a preset bus abnormality of the first controller.
[0199] In one example, the transmission path is a preset bus, and a thermal management sensor is deployed in the first controller. The thermal management sensor is used to collect the operating status information of the thermal management component, and the message information represents the collected operating status information of the thermal management component; the type determination module is specifically used for:
[0200] If the second controller determines that the working status information in the message does not meet the preset conditions, then the abnormality type of the first controller is determined to be a data acquisition abnormality; wherein, the data acquisition abnormality indicates that the thermal management sensor in the first controller is abnormal.
[0201] In one example, a thermal management sensor is deployed in the second controller. This sensor is used to collect operating status information of the thermal management component, including temperature information of the thermal management component. The thermal management control unit 903 is specifically used for:
[0202] If the anomaly type of the first controller is an operational anomaly, the working status information of the thermal management component is collected through the thermal management sensor in the second controller;
[0203] If the temperature information in the working status information of the thermal management component is greater than a preset temperature threshold, then the second controller sends a control signal to the thermal management component based on a preset bus; wherein, the control signal is used to control the thermal management component.
[0204] In one example, the thermal management control unit 903 is specifically used for:
[0205] If the first controller's anomaly type is a communication anomaly, then the second controller acquires the demand signal emitted by the thermal management component based on the preset bus, and sends the demand signal to the first controller via Ethernet; wherein, the demand signal represents the thermal management component's control demand for itself;
[0206] The first controller determines a control signal based on the demand signal and sends the control signal to the second controller via Ethernet; wherein the control signal is used to control the thermal management component;
[0207] The second controller sends control signals to the thermal management component via the preset bus.
[0208] In one example, a thermal management sensor is deployed in the second controller to collect operating status information of the thermal management components; the thermal management control unit 903 is specifically used for:
[0209] If the first controller's anomaly type is a data acquisition anomaly, then the thermal management sensor in the second controller acquires the operating status information of the thermal management component, and sends the acquired operating status information to the first controller via Ethernet.
[0210] The first controller sends a control signal to the thermal management component based on the operating status information of the thermal management component; wherein the control signal is used to control the thermal management component.
[0211] In one example, the vehicle is equipped with a microprocessor (MCU) and a cooling device. The MCU is used to output pulse width modulation (PWM) signals, and the cooling device is connected to the first controller. The cooling device is used to cool thermal management components by rotation. The device also includes:
[0212] A signal sending unit is configured to send a PWM signal to the cooling device via the MCU if the first controller's fault type is an operational fault; wherein the PWM signal is used to control the rotation of the cooling device.
[0213] Figure 10 A structural block diagram of an electronic device provided in an embodiment of this application, such as... Figure 10 As shown, the electronic device includes: a memory 1001 and a processor 1002; the memory 1001 is a memory used to store instructions executable by the processor 1002.
[0214] The processor 1002 is configured to perform the method provided in the above embodiments.
[0215] The electronic device also includes a receiver 1003 and a transmitter 1004. The receiver 1003 is used to receive instructions and data sent by other devices, and the transmitter 1004 is used to send instructions and data to external devices.
[0216] Figure 11 This is a block diagram illustrating an electronic device according to an exemplary embodiment. The device may be a mobile phone, computer, digital broadcasting terminal, messaging device, game console, tablet device, personal digital assistant, etc.
[0217] The device 1100 may include one or more of the following components: a processing component 1102, a memory 1104, a power supply component 1106, a multimedia component 1108, an audio component 1110, an input / output (I / O) interface 1112, a sensor component 1114, and a communication component 1116.
[0218] Processing component 1102 typically controls the overall operation of device 1100, such as operations associated with display, telephone calls, data communication, camera operation, and recording operations. Processing component 1102 may include one or more processors 1120 to execute instructions to perform all or part of the steps of the methods described above. Furthermore, processing component 1102 may include one or more modules to facilitate interaction between processing component 1102 and other components. For example, processing component 1102 may include a multimedia module to facilitate interaction between multimedia component 1108 and processing component 1102.
[0219] Device 1100 may include one or more of the following components: processing component 1102, memory 1104, power supply component 1106, multimedia component 1108, audio component 1110, input / output (I / O) interface 1112, sensor component 1114, and communication component 1116.
[0220] Memory 1104 is configured to store various types of data to support the operation of device 1100. Examples of such data include instructions for any application or method operating on device 1100, contact data, phonebook data, messages, pictures, videos, etc. Memory 1104 can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as static random access memory (SRAM), electrically erasable programmable read-only memory (EEPROM), erasable programmable read-only memory (EPROM), programmable read-only memory (PROM), read-only memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.
[0221] Power supply component 1106 provides power to various components of device 1100. Power supply component 1106 may include a power management system, one or more power supplies, and other components associated with generating, managing, and distributing power to device 1100.
[0222] Multimedia component 1108 includes a screen that provides an output interface between the device 1100 and the user. In some embodiments, the screen may include a liquid crystal display (LCD) and a touch panel (TP). If the screen includes a touch panel, the screen may be implemented as a touchscreen to receive input signals from the user. The touch panel includes one or more touch sensors to sense touches, swipes, and gestures on the touch panel. The touch sensors may sense not only the boundaries of the touch or swipe action but also the duration and pressure associated with the touch or swipe operation. In some embodiments, multimedia component 1108 includes a front-facing camera and / or a rear-facing camera. When the device 1100 is in an operating mode, such as a shooting mode or a video mode, the front-facing camera and / or the rear-facing camera may receive external multimedia data. Each front-facing camera and rear-facing camera may be a fixed optical lens system or have focal length and optical zoom capabilities.
[0223] Audio component 1110 is configured to output and / or input audio signals. For example, audio component 1110 includes a microphone (MIC) configured to receive external audio signals when device 1100 is in an operating mode, such as call mode, recording mode, and voice recognition mode. The received audio signals may be further stored in memory 1104 or transmitted via communication component 1116. In some embodiments, audio component 1110 also includes a speaker for outputting audio signals.
[0224] I / O interface 1112 provides an interface between processing component 1102 and peripheral interface modules, such as keyboards, click wheels, buttons, etc. These buttons may include, but are not limited to, home buttons, volume buttons, power buttons, and lock buttons.
[0225] Sensor assembly 1114 includes one or more sensors for providing status assessments of various aspects of device 1100. For example, sensor assembly 1114 may detect the on / off state of device 1100, the relative positioning of components such as the display and keypad of device 1100, changes in the position of device 1100 or a component of device 1100, the presence or absence of user contact with device 1100, the orientation or acceleration / deceleration of device 1100, and temperature changes of device 1100. Sensor assembly 1114 may include a proximity sensor configured to detect the presence of nearby objects without any physical contact. Sensor assembly 1114 may also include a light sensor, such as a CMOS or CCD image sensor, for use in imaging applications. In some embodiments, sensor assembly 1114 may also include an accelerometer, a gyroscope, a magnetometer, a pressure sensor, or a temperature sensor.
[0226] Communication component 1116 is configured to facilitate wired or wireless communication between device 1100 and other devices. Device 1100 can access wireless networks based on communication standards, such as WiFi, 2G, or 3G, or combinations thereof. In one exemplary embodiment, communication component 1116 receives broadcast signals or broadcast-related information from an external broadcast management system via a broadcast channel. In one exemplary embodiment, communication component 1116 also includes a near-field communication (NFC) module to facilitate short-range communication. For example, the NFC module may be implemented based on radio frequency identification (RFID) technology, Infrared Data Association (IrDA) technology, ultra-wideband (UWB) technology, Bluetooth (BT) technology, and other technologies.
[0227] In an exemplary embodiment, the apparatus 1100 may be implemented by one or more application-specific integrated circuits (ASICs), digital signal processors (DSPs), digital signal processing devices (DSPDs), programmable logic devices (PLDs), field-programmable gate arrays (FPGAs), controllers, microcontrollers, microprocessors, or other electronic components to perform the methods described above.
[0228] In an exemplary embodiment, a non-transitory computer-readable storage medium including instructions is also provided, such as a memory 1104 including instructions, which can be executed by a processor 1120 of the device 1100 to perform the above-described method. For example, the non-transitory computer-readable storage medium may be a ROM, random access memory (RAM), CD-ROM, magnetic tape, floppy disk, and optical data storage device, etc.
[0229] A non-transitory computer-readable storage medium, wherein instructions in the storage medium, when executed by a processor of an electronic device, enable the electronic device to perform the aforementioned vehicle thermal management control method.
[0230] Other embodiments of this application will readily occur to those skilled in the art upon consideration of the specification and practice of the invention disclosed herein. This application is intended to cover any variations, uses, or adaptations of this application that follow the general principles of this application and include common knowledge or customary techniques in the art not disclosed herein. The specification and examples are to be considered exemplary only, and the true scope and spirit of this application are indicated by the following claims.
[0231] The above embodiments are merely preferred embodiments provided to fully illustrate the present invention, and the scope of protection of the present invention is not limited thereto. Equivalent substitutions or modifications made by those skilled in the art based on the present invention are all within the scope of protection of the present invention.
Claims
1. A control method of vehicle thermal management, characterized by, The method is applied to a vehicle, which is equipped with a first controller, a second controller, and a thermal management component. The thermal management component is communicatively connected to both the first controller and the second controller via a preset bus. The first controller and the second controller are communicatively connected via Ethernet. The first controller controls the thermal management component, and the second controller takes over control of the thermal management component when the first controller malfunctions. The method includes: The second controller receives message information sent by the first controller and determines the transmission path of the message information; wherein the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller; The anomaly type of the first controller is determined based on the message information and the transmission path of the message information; Based on the anomaly type of the first controller, the thermal management component is controlled via the second controller; Based on the message information and the transmission path of the message information, the anomaly type of the first controller is determined, including: Based on a preset association relationship, an anomaly judgment logic corresponding to the transmission path of the message information is determined; wherein, the preset association relationship represents the association relationship between the transmission path and the anomaly judgment logic, and the anomaly judgment logic is used to determine the anomaly type of the first controller. Based on the message information, and using the anomaly detection logic corresponding to the transmission path of the message information, the anomaly type of the first controller is determined.
2. The method of claim 1, wherein, The transmission path is Ethernet, and the message information represents the reply signal fed back by the first controller after receiving the handshake signal sent by the second controller. The handshake signal includes a random number and a count value, and the count value represents the number of times the second controller sends the handshake signal to the first controller. Based on the message information, and using the anomaly detection logic corresponding to the transmission path of the message information, the anomaly type of the first controller is determined, including: The second controller determines the sending time of the handshake signal and the receiving time of the reply signal. If the time difference between the sending time of the handshake signal and the receiving time of the reply signal is less than a preset first difference threshold, then the random number and count value in the handshake signal and the random number and count value in the reply signal are obtained. If the random number in the handshake signal is inconsistent with the random number in the reply signal, or the count value in the handshake signal is inconsistent with the count value in the reply signal, then the abnormality type of the first controller is determined to be an operational abnormality; wherein, the operational abnormality indicates that the first controller has crashed.
3. The method of claim 1, wherein, The transmission path is a preset bus; based on the message information and the anomaly judgment logic corresponding to the transmission path of the message information, the anomaly type of the first controller is determined, including: The second controller determines the reception time of the message information. If the time difference between the received message and the current time is greater than a preset second difference threshold, and no new message is received, then the abnormality type of the first controller is determined to be a communication abnormality; wherein, the communication abnormality represents a preset bus abnormality of the first controller.
4. The method of claim 1, wherein, The transmission path is a preset bus. A thermal management sensor is deployed in the first controller. The thermal management sensor is used to collect the working status information of the thermal management component. The message information represents the collected working status information of the thermal management component. Based on the message information, and using the anomaly detection logic corresponding to the transmission path of the message information, the anomaly type of the first controller is determined, including: If the second controller determines that the working status information in the message does not meet the preset conditions, then the abnormality type of the first controller is determined to be a data acquisition abnormality; wherein, the data acquisition abnormality indicates that the thermal management sensor in the first controller is abnormal.
5. The method of claim 1, wherein, The second controller is equipped with a thermal management sensor, which is used to collect the operating status information of the thermal management component, including the temperature information of the thermal management component. Based on the anomaly type of the first controller, the second controller controls the thermal management component, including: If the anomaly type of the first controller is an operational anomaly, the working status information of the thermal management component is collected through the thermal management sensor in the second controller; If the temperature information in the working status information of the thermal management component is greater than a preset temperature threshold, then the second controller sends a control signal to the thermal management component based on a preset bus; wherein, the control signal is used to control the thermal management component.
6. The method of claim 1, wherein, Based on the anomaly type of the first controller, the thermal management component is controlled via the second controller, including: If the first controller's anomaly type is a communication anomaly, then the second controller acquires the demand signal emitted by the thermal management component based on the preset bus, and sends the demand signal to the first controller via Ethernet; wherein, the demand signal represents the thermal management component's control demand for itself; The first controller determines a control signal based on the demand signal and sends the control signal to the second controller via Ethernet; wherein the control signal is used to control the thermal management component; The second controller sends control signals to the thermal management component via the preset bus.
7. The method according to claim 1, characterized in that, The second controller is equipped with a thermal management sensor, which is used to collect the operating status information of the thermal management component. Based on the anomaly type of the first controller, the second controller controls the thermal management component, including: If the first controller's anomaly type is a data acquisition anomaly, then the thermal management sensor in the second controller acquires the operating status information of the thermal management component, and sends the acquired operating status information to the first controller via Ethernet. The first controller sends a control signal to the thermal management component based on the operating status information of the thermal management component; wherein the control signal is used to control the thermal management component.
8. The method according to any one of claims 1-7, characterized in that, The vehicle is equipped with a microprocessor (MCU) and a cooling device. The MCU is used to generate pulse width modulation (PWM) signals, and the cooling device is connected to the first controller. The cooling device is used to cool the thermal management components by rotating. The method further includes: If the first controller's exception type is an operational exception, then the MCU sends a PWM signal to the cooling device; wherein the PWM signal is used to control the rotation of the cooling device.
9. A control device for vehicle thermal management, characterized in that, The device is applied to a vehicle, in which a first controller, a second controller, and a thermal management component are deployed. The thermal management component is communicatively connected to the first controller and the second controller via a preset bus. The first controller and the second controller are communicatively connected via Ethernet. The first controller is used to control the thermal management component, and the second controller is used to take over control of the thermal management component when the first controller malfunctions. The device includes: The path determination unit is used to receive message information sent by the first controller through the second controller and determine the transmission path of the message information; wherein the transmission path is a preset bus or Ethernet, and the message information represents the working status of the first controller; A type determination unit is used to determine the anomaly type of the first controller based on the message information and the transmission path of the message information; A thermal management control unit is used to control the thermal management component via a second controller based on the type of fault in the first controller. The type determination unit includes: A logic determination module is used to determine the anomaly judgment logic corresponding to the transmission path of the message information based on a preset association relationship; wherein, the preset association relationship represents the association relationship between the transmission path and the anomaly judgment logic, and the anomaly judgment logic is used to determine the anomaly type of the first controller. The type determination module is used to determine the exception type of the first controller based on the message information and the exception judgment logic corresponding to the transmission path of the message information.
10. An electronic device, characterized in that, include: A processor, and a memory communicatively connected to the processor; The memory stores computer-executed instructions; The processor executes computer execution instructions stored in the memory to implement the method as described in any one of claims 1-8.
11. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores computer-executable instructions, which, when executed by a processor, are used to implement the method as described in any one of claims 1-8.
12. A computer program product, characterized in that, Includes a computer program that, when executed by a processor, implements the method of any one of claims 1-8.
Citation Information
Patent Citations
Automobile thermal management control system, method and device, storage medium and electronic device
CN118833019A
