Methods, systems, media, and products for thermal management actuator control and status feedback
By using PWM control and status feedback methods with single-line interface nodes, the complexity and cost issues in thermal management systems are solved, efficient actuator status feedback and diagnosis are achieved, and the reliability and integrated design of the system are improved.
Patent Information
- Application Number
- CN202611576948.0
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2026-10-13
- Publication Date
- 2026-11-10
AI Technical Summary
In existing thermal management actuator control and status feedback technologies, multi-line communication increases system complexity and cost, independent feedback pin resources are insufficient, and the accuracy and real-time performance of analog-to-digital converters are poor, making it difficult to achieve efficient integrated design.
The PWM speed control command and status feedback are implemented through a single-line interface node. The drive segment is divided using the timing reference of the local PWM instruction, the input edge event is captured and its category is determined, local edge interference is eliminated, the actual pull-down action status is accumulated, and the actuator status is decoded by querying the status window mapping table.
Reduce hardware costs and wiring weight, improve system reliability and stability, accurately distinguish between command signals and feedback signals, support multi-state decoding and protocol adaptation, and reduce false alarms and state transitions.
Smart Images

Figure CN123067306A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of thermal management control, and in particular to a method, system, medium, and product for controlling and providing status feedback of thermal management actuators. Background Technology
[0002] With the continuous development of automotive technology and the increasing demands for vehicle performance, thermal management systems are crucial for ensuring the stable operation of key components such as engines. Proper thermal management can effectively improve engine efficiency, reduce energy consumption and emissions, while also extending component lifespan and enhancing the driving experience.
[0003] Currently, in terms of thermal management actuator control and status feedback, the conventional approaches mainly include using multi-line communication for information exchange, which requires additional wiring harnesses, increasing system complexity and cost; another approach is to connect to the thermal management actuator through an interface with independent feedback pins to achieve data and status transmission, but this approach uses more pin resources and is not conducive to system integration design; yet another approach is to use analog-to-digital converters to acquire simple analog signals to obtain status, but the accuracy and real-time performance are often poor. Summary of the Invention
[0004] This application provides a method, system, medium, and product for controlling and providing status feedback of thermal management actuators, which accurately controls thermal management actuators and obtains status feedback, effectively avoids false alarms, filters status jumps, and improves the reliability and stability of thermal management systems.
[0005] In a first aspect, this application provides a method for controlling and providing status feedback of a thermal management actuator, applied to a thermal management controller, wherein the thermal management controller is connected to the thermal management actuator via a single-wire interface node, the method comprising: According to the control request, the local PWM command is output to the thermal management actuator through the single-line interface node. Based on the predetermined level switching time of the local PWM command, each complete cycle of the local PWM command is divided into multiple consecutive drive segments. Within each of the drive segments, the input edge events on the single-line interface node are captured, and the line level of the single-line interface node is read. Based on the timing reference corresponding to the current drive segment and the line level, determine the category of the input edge event captured in the current drive segment. The category includes the local edge generated by the local PWM instruction flipping and the external feedback edge generated by the thermal management actuator pulling down the single-line interface node. Based on the classification result, the local edge is removed, and the actual pull-down action state of the thermal management actuator in the current drive segment is extracted; The feature parameters of the actual pull-down action state on the time axis are accumulated to obtain the duration of the external pull-down activity. Based on the duration of the external pull-down activity, a preset state window mapping table is queried, and the current diagnostic state of the thermal management actuator is decoded.
[0006] By adopting the above technical solution, PWM speed control command issuance and actuator status feedback can be realized simultaneously through the same single-wire interface node, reducing the number of controller pins, connector terminals, and wiring harness cores, thereby reducing the hardware cost, wiring weight, and interface failure points of the thermal management system. Using the timing reference of the local PWM command as a reference, each PWM cycle is divided into multiple drive segments. Within each segment, the input edge events are classified, accurately distinguishing between the local edge generated by the local PWM flip and the external feedback edge generated by the actuator pull-down. After eliminating local edge interference, the true actuator pull-down action state is extracted, thus achieving reliable separation and high-fidelity decoding of command signals and feedback signals on a single-wire physical medium.
[0007] In some embodiments, determining the category of the input edge event captured within the current drive segment based on the timing reference corresponding to the current drive segment and the line level specifically includes: If the input edge event is detected within the current drive segment, it is determined that the input edge event is associated with the timing transition of the local PWM instruction, and the category of the input edge event is marked as a local edge. If the input edge event is not detected in the current drive segment, the logic level corresponding to the line level is read, and the external pull-down state independently maintained by the thermal management actuator is determined based on the logic level. Combining the determination conclusions regarding the local edge or external pull-down state within the current driving segment, and the determination conclusions of the previous adjacent driving segment, the final category of the input edge event captured within the current driving segment is determined according to preset rules. After completing the falling and rising edge processing of the native PWM command for a full cycle, the input capture flag corresponding to the current cycle is cleared so that edge capture and classification can be performed again in the drive segment of the next cycle.
[0008] By employing the above technical solution, input edge events are correlated with local PWM timing transitions for identification. Combined with the comprehensive determination of adjacent drive segments, a spatiotemporal two-dimensional edge attribution comprehensive identification mechanism is formed. This mechanism accurately distinguishes between local edges generated by local PWM switching and external feedback edges generated by actuator feedback, eliminating attribution ambiguity caused by edge overlap or crosstalk between adjacent segments. This ensures accurate classification of input edge events within each drive segment. After handling falling and rising edges within a complete PWM cycle, the input capture flag for the current cycle is cleared. The next cycle re-performs edge capture and attribution determination, establishing an independent discrimination benchmark for each cycle and achieving independence and consistency in discrimination logic between cycles.
[0009] In some embodiments, the step of accumulating the feature parameters of the actual pull-down action state on the time axis to obtain the duration of the external pull-down activity, and querying a preset state window mapping table based on the duration of the external pull-down activity to decode and obtain the current diagnostic state of the thermal management actuator specifically includes: The extracted actual pull-down action state is discretized and sampled according to a preset fixed time sampling period; When the actual pull-down action state is sampled as an external pull-down activity, the activity counter is incremented; when the actual pull-down action state is sampled as a non-external pull-down activity, the inactivity counter is incremented. When the actual drop-down action state is detected to change from active to inactive or from inactive to active, the transition edge is used as the settlement trigger condition. The current count values of the activity counter and the inactive counter are read respectively, and each is multiplied by the fixed time sampling period to calculate the external drop-down activity duration and the external inactive duration. The duration of the external drop-down activity is matched one by one with multiple preset state intervals in the state window mapping table. When the duration of the external drop-down activity falls into the target state interval in the state window mapping table, the state corresponding to the target state interval is decoded as the current diagnostic state of the thermal management actuator.
[0010] By employing the above technical solution, the settlement trigger condition is triggered by using the transition edge rather than a fixed period, ensuring that the start and end boundaries of each feedback sequence are perfectly aligned with the actual feedback pulses output by the actuator, thus avoiding duration measurement deviations caused by fixed period truncation. The external drop-down activity duration obtained from the settlement is used as the query key, and matched against multiple preset state intervals in the state window mapping table, rather than relying on a single threshold comparison or instantaneous level judgment. The corresponding diagnostic state is decoded by utilizing the interval range into which the activity duration falls, achieving flexible adaptation of a single decoding framework to multiple states and protocols.
[0011] In some embodiments, the method further includes: Detect whether the external inactivity duration or external pull-down activity duration of the actual pull-down action state exceeds a preset no-input timeout threshold; If the external inactivity duration or the external pull-down activity duration exceeds the no-input timeout threshold, then the target duty cycle parameter of the current local PWM instruction is read, and the target duty cycle parameter is compared with the preset drive threshold duty cycle. When the target duty cycle parameter is greater than the drive threshold duty cycle, it is determined that the current driving state is effective, and candidate fault states including no input disconnection or frequency abnormality are generated. When the target duty cycle parameter is less than or equal to the drive threshold duty cycle, it is determined that the current state is in the zero command or stop interval, the generation of the candidate fault state is suppressed, and the current diagnostic state is maintained as the stop or idle state.
[0012] By employing the above technical solution, candidate faults are generated only when a timeout occurs and the system is in an effective driving state. Even if a timeout occurs within a zero-command or stop interval, fault generation is suppressed, and the system remains in a stop / idle state. This solves the industry-wide problem of false alarms for disconnection or frequency anomalies due to lack of actuator feedback in the stop state, a common issue in traditional solutions. This ensures that the diagnostic results match the actual operating state of the actuator. When a timeout occurs while the system is in an effective driving state, candidate faults are categorized into two main types: "no input disconnection" and "frequency anomaly," providing preliminary fault characterization guidance and shortening fault location time.
[0013] In some embodiments, reading the target duty cycle parameter of the current local PWM instruction and comparing the target duty cycle parameter with a preset drive threshold duty cycle specifically includes: The target logic duty cycle of the current cycle is read from the control request, and the physical duty cycle of the current actual output is read. The target logic duty cycle and the physical duty cycle are checked for consistency. When the absolute value of the deviation between the target logic duty cycle and the physical duty cycle is less than the preset duty cycle deviation tolerance, the physical duty cycle is used as the effective duty cycle to participate in the subsequent threshold comparison. Obtain a set of drive threshold parameters that matches the type of thermal management actuator connected to the current channel. The set of drive threshold parameters includes a main drive threshold and a minimum sustain drive threshold, wherein the main drive threshold is greater than the minimum sustain drive threshold. If the effective duty cycle is greater than the main drive threshold, it is determined that the current state is strong drive and the no-input diagnostic function is fully enabled. If the effective duty cycle is between the main drive threshold and the minimum sustain drive threshold, it is determined that the current state is weak drive, and no-input diagnosis is performed with reduced diagnostic sensitivity. The reduced diagnostic sensitivity is achieved by multiplying the no-input timeout threshold by a preset sensitivity reduction factor. If the effective duty cycle is less than or equal to the minimum sustain drive threshold, it is determined that the current state is non-drive, the no-input diagnostic function of the current channel is turned off, the current diagnostic state is kept in standby or idle state, and the accumulated candidate fault counter is cleared.
[0014] By employing the above technical solution, the consistency verification between the target logic duty cycle requested by the upper layer and the physical duty cycle actually output by the timer solves the blind zone problem caused by abnormal PWM hardware output, which leads to false alarms of actuator no input disconnection due to "software believing it is driving, but the hardware is not actually outputting," thus improving the underlying reliability of the diagnostic logic. Through two levels of thresholds—the main drive threshold and the minimum sustain drive threshold—matched to the actuator type, the drive state is divided into three levels: strong drive, weak drive, and no drive, achieving a fine-grained match between the drive state and diagnostic sensitivity.
[0015] In some embodiments, after decoding to obtain the current diagnostic status of the thermal management actuator, the method further includes a power-on shielding and continuous consistency confirmation step, specifically including: During the preset shielding period after the thermal management controller is powered on and initialized, the extraction and accumulation of the actual pull-down action state are continuously performed, and the external output of the fault state is shielded. The current diagnostic state is set to the normal state and a normal mask is output to avoid false alarms caused by power-up transients. After the preset blocking period ends, the query permission for the status window mapping table is enabled, and the diagnostic status obtained from each query is cached as a candidate diagnostic status. Within each control cycle, the candidate diagnostic status cached in the current cycle is compared with the candidate diagnostic status cached in the previous control cycle for consistency. If the candidate diagnostic state cached in this cycle is consistent with the candidate diagnostic state cached in the previous control cycle, the consistency counter is incremented until the count value of the consistency counter reaches the preset consecutive confirmation number threshold. The candidate diagnostic state is then determined as the final confirmation state and output to the outside. If the candidate diagnostic state cached in this cycle is inconsistent with the candidate diagnostic state cached in the previous control cycle, the consistency counter is reset to filter out state jumps caused by edge jitter and window boundary fluctuations.
[0016] By employing the above technical solution, during the preset shielding period after power-on, the extraction and accumulation of the actual pull-down action status are continuously performed, but the current diagnostic status is forcibly set to normal and a normal mask is output. This avoids false fault code reports due to unstable power supply, unready actuators, and unestablished line bias in the initial power-on phase of the controller, while also ensuring that feedback measurement data during the startup phase is not lost due to shielding. This achieves a balance between transient isolation during startup and continuity of status measurement. Through majority consistency filtering in the time dimension, frequent jumps in the diagnostic status caused by line edge jitter, timer capture fluctuations, and critical values at the status window boundaries are effectively suppressed, ensuring the stability and reliability of the output status.
[0017] In some embodiments, the method further includes: Obtain the output comparison event interrupt signal output when the local PWM instruction triggers a toggle in the output comparison unit, and lock the trigger time of the output comparison event interrupt signal as the absolute segmentation time beacon of the current complete cycle; Based on the target duty cycle parameter of the currently output local PWM command, the left region of the absolute segmented time beacon on the time axis is divided into a first phase segment, and the right region of the absolute segmented time beacon on the time axis is divided into a second phase segment. Read the preset interface output polarity configuration parameters of the single-line interface node, and convert the logic levels of the first phase segment and the second phase segment into the corresponding expected theoretical line level values according to the interface output polarity configuration parameters. When capturing the input edge event, if the arrival time of the input edge event is within a preset range of the time boundaries of the first phase segment and the second phase segment, and the changed line level is consistent with the expected value of the theoretical line level, the input edge event is pre-judged as the local edge and marked for rejection.
[0018] By adopting the above technical solution, the triggering time of the interrupt signal generated when the output comparator unit triggers its flip is locked as the absolute segmentation time beacon of the current complete cycle. Hardware interrupt events, rather than software calculations or timer overflows, are used as the timing basis for cycle segmentation. By utilizing the physical determinism of the output comparator interrupt triggered at the instant of PWM waveform level switching, the influence of software loop delay, interrupt response jitter, and timer read errors on cycle boundary positioning is eliminated. This provides an absolute time reference with microsecond-level precision for PWM cycle division, ensuring that the time boundaries of multiple drive segments within each cycle are physically perfectly aligned with the actual PWM waveform.
[0019] In a second aspect, embodiments of this application provide a computer system including a memory, a processor, and a computer program stored in the memory; the processor executes the computer program to implement the steps of the method described in any possible implementation of the first aspect.
[0020] Thirdly, embodiments of this application provide a computer-readable storage medium having a computer program / instructions stored thereon, which, when executed by a processor, implement the steps of the method described in any possible implementation of the first aspect.
[0021] Fourthly, embodiments of this application provide a computer program product, including a computer program / instructions, which, when executed by a processor, implement the steps of the method described in any possible implementation of the first aspect.
[0022] It is understood that the computer system provided in the second aspect, the storage medium provided in the third aspect, and the computer program product provided in the fourth aspect are all used to execute the method provided in this application. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods, and will not be repeated here.
[0023] One or more technical solutions provided in the embodiments of this application have at least the following technical effects or advantages: 1. Simultaneously implement PWM speed control command issuance and actuator status feedback through the same single-line interface node, reducing the number of controller pins, connector terminals and wire harness cores, thereby reducing the hardware cost, wiring weight and interface failure points of the thermal management system; 2. By combining timing reference and line level judgment, the local edge generated by the PWM flip and the external feedback edge generated by the actuator pull-down are accurately distinguished. After eliminating the interference of the local edge, the true actuator pull-down action state is extracted. This fundamentally solves the inherent problem of the local output edge being misidentified as the feedback edge in the traditional single-line parallel connection scheme, and realizes the fidelity separation of command signal and feedback signal on the single-line physical medium. 3. Based on the cumulative characteristic parameters (external pull-down activity duration) of the actual external pull-down action state on the time axis, the current diagnostic status of the actuator is obtained by querying the preset status window mapping table. Different time window intervals in which the activity duration falls are used to distinguish various operating and fault states such as normal heartbeat, dry running, stalled running, overcurrent, and overtemperature. High tolerance decoding is achieved by windowed matching rather than a single threshold comparison, and the window parameters can be recalibrated to adapt to the differentiated feedback protocols of actuators from different manufacturers. Attached Figure Description
[0024] Figure 1 This is a flowchart illustrating the method for controlling and providing status feedback of the thermal management actuator in an embodiment of this application; Figure 2 This is a schematic diagram of the single-line PWM multiplexing control and feedback system structure in an embodiment of this application; Figure 3 This is a schematic diagram of the external pull-down timing for the local PWM phase correlation in an embodiment of this application; Figure 4 This is a schematic diagram of the feedback timing, status decoding and fault confirmation process in an embodiment of this application; Figure 5 This is a schematic diagram of an exemplary hardware structure of a computer system in an embodiment of this application. Detailed Implementation
[0025] The terminology used in the following embodiments of this application is for the purpose of describing particular embodiments only and is not intended to be limiting of this application. As used in the specification and appended claims of this application, the singular expressions “a,” “an,” “the,” “the,” “the,” and “this” are intended to include the plural expressions as well, unless the context clearly indicates otherwise. It should also be understood that the term “and / or” as used in this application refers to any or all possible combinations including one or more of the listed items.
[0026] Hereinafter, the terms "first" and "second" are used for descriptive purposes only and should not be construed as implying or suggesting relative importance or implicitly indicating the number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature, and in the description of the embodiments of this application, unless otherwise stated, "multiple" means two or more.
[0027] The following is combined Figure 1 The method of the embodiments of this application will be described below.
[0028] Please see Figure 1 This is a flowchart illustrating the method for controlling and providing status feedback of the thermal management actuator in an embodiment of this application. Figure 1 As shown, the method includes the following steps: S101. According to the control request, the local PWM instruction is output to the thermal management actuator through the single-line interface node. The predetermined level switching time of the local PWM instruction is used as the timing reference to divide each complete cycle of the local PWM instruction into multiple continuous drive segments. S102. Within each of the driving segments, capture the input edge event on the single-line interface node and read the line level of the single-line interface node; S103. Based on the timing reference corresponding to the current drive segment and the line level, determine the category of the input edge event captured in the current drive segment. The category includes the local edge generated by the flipping of the local PWM instruction and the external feedback edge generated by the thermal management actuator pulling down the single-line interface node. S104. Based on the classification result, remove the edge of the machine and extract the actual pull-down action state of the thermal management actuator in the current drive segment; S105. Accumulate the feature parameters of the actual pull-down action state on the time axis to obtain the duration of the external pull-down activity. Based on the duration of the external pull-down activity, query the preset state window mapping table and decode to obtain the current diagnostic state of the thermal management actuator.
[0029] Based on the upper-level control request, a native Pulse Width Modulation (PWM) command is output to the thermal management actuator via a single-wire interface node. The duty cycle of the native PWM command corresponds to the actuator's target speed or target opening degree, and the actuator obtains the speed control command by receiving this PWM signal. Using the predetermined level switching moments of the native PWM command as a timing reference, each complete cycle of the native PWM command is divided into multiple consecutive drive segments. Specifically, the predetermined level switching moments include the moments when the native PWM signal switches from high to low (falling edge) and from low to high (rising edge), which serve as absolute time beacons within the PWM cycle. Based on these time beacons, a complete PWM cycle is divided into multiple drive segments on the time axis, for example, into high-level segments and low-level segments, or further subdivided into more sub-segments as needed. Each drive segment has known time boundaries and expected logic level states, providing a timing reference for subsequent edge attribution determination.
[0030] Within each drive segment, the input edge events occurring on the single-line interface node are captured by the input capture unit, and the current line level of the single-line interface node is read. Input edge events include both rising and falling edges. When a signal level transition occurs on the single-line interface node, the input capture unit records the transition event and its occurrence time. Simultaneously, the line logic level (high or low) of the node is read to obtain the actual level state of the single-line interface node at the current moment. It should be noted that since the single-line interface node simultaneously carries the controller's output PWM command and potential external pull-down feedback from the actuator, edge events occurring on this node may originate from two different sources: one is the level flipping of the local PWM command itself at a predetermined level switching time, and the other is the feedback signal actively applied by the actuator by pulling the node low. Therefore, the attribution of an edge event cannot be directly determined solely by the edge event itself.
[0031] Based on the timing reference corresponding to the current drive segment and the read line level, the classification of input edge events captured within the current drive segment is determined. There are two classification categories: native edges generated by the toggle of the native PWM command, and external feedback edges generated by the thermal management actuator pulling down a single-wire interface node. The specific determination principle is as follows: Since the predetermined level switching time of the native PWM command is known, the occurrence position of native edges on the time axis is definite and predictable. When the occurrence time of an input edge event coincides with the predetermined level switching time of the native PWM command, the edge should be classified as a native edge. Conversely, when the occurrence time of an input edge event is not near any predetermined switching time of the native PWM, and the edge causes the line level to change to a low level, the edge should be classified as an external feedback edge generated by the actuator's external pull-down. Furthermore, the line level reading results also provide auxiliary basis for classification. For example, detecting a low level within a drive segment that is expected to be high may indicate that the actuator is actively pulling the line low to transmit feedback information. By combining the timing reference and line level, it is possible to effectively distinguish between two types of edge events from different sources on the same physical line.
[0032] Based on the classification results, local edges are removed, and the actual pull-down action state of the thermal management actuator within the current drive segment is extracted. Specifically, all input edge events identified as local edges are signal transitions generated when the controller outputs PWM commands and do not represent any feedback intention from the actuator, therefore they are removed. Only events identified as external feedback edges reflect the feedback action actively applied by the actuator by pulling down the single-wire interface node. After the above removal process, external pull-down action information generated solely by the actuator is separated from the edge signals mixed on the same physical line. This actual pull-down action state reflects whether the actuator is actively pulling the line low to transmit status information and is the original data source for subsequent status decoding.
[0033] The characteristic parameters of the actual pull-down action state on the time axis are accumulated to obtain the duration of the external pull-down activity. Based on the duration of the external pull-down activity, a preset state window mapping table is queried to decode the current diagnostic state of the thermal management actuator. The characteristic parameters include at least the duration of the external pull-down activity. Since the actuator encodes different operating or fault states by pulling the line low for different durations (e.g., 400-600ms low indicates normal heartbeat, 900-1100ms low indicates dry running, 1400-1600ms low indicates stall or overcurrent, etc.), the duration of the actual pull-down action state is the key basis for decoding the actuator state. Specifically, the extracted actual pull-down action state is time-measured, and the duration of its active state (i.e., the line is pulled low) is accumulated to obtain the duration of the external pull-down activity. Then, this duration of the external pull-down activity is matched one by one with multiple state intervals recorded in the preset state window mapping table. The status window mapping table pre-stores the activity duration intervals corresponding to various diagnostic states. For example, the normal state corresponds to the first time interval, the dry run state corresponds to the second time interval, the stalled state corresponds to the third time interval, the overcurrent state corresponds to the fourth time interval, and the overtemperature state corresponds to the fifth time interval. When the externally pulled activity duration falls into a certain state interval, the state corresponding to that interval is decoded as the current diagnostic state of the thermal management actuator.
[0034] Figure 2 This is a schematic diagram of the single-wire PWM multiplexing control and feedback system structure in an embodiment of this application, as shown below. Figure 2As shown, the system includes a thermal management controller and a thermal management actuator. The thermal management controller and the thermal management actuator are electrically connected via the same physical line (single-line interface node). This same physical line is used to transmit PWM speed control commands sent from the controller to the actuator, as well as status feedback signals returned from the actuator to the controller. The thermal management controller integrates: a PWM command generation unit, used to generate local PWM commands based on upper-level control requests; outputting these local PWM commands to the thermal management actuator via the single-line interface node to achieve speed control of the actuator's rotational speed or opening degree; an input edge capture unit, used to capture input edge events occurring on the single-line interface node and read the line level of the single-line interface node; and a timing, decoding, and diagnostic unit, used to classify the captured input edge events, extract the actual pull-down action state of the actuator, accumulate time characteristic parameters, and decode the current diagnostic state of the actuator by querying the status window mapping table. The thermal management controller outputs local PWM commands through the single-line interface node and simultaneously receives feedback signals applied by the thermal management actuator via external pull-down, achieving bidirectional information exchange on the same physical line. Thermal management actuators include, but are not limited to, cooling fans and electric water pumps. Each thermal management actuator has a controllable pull-down element that can actively pull down a single-wire interface node based on its operating status (normal, dry run, locked run, overcurrent, overtemperature, etc.) to return a corresponding status code signal to the thermal management controller.
[0035] In some embodiments, determining the category of the input edge event captured within the current drive segment based on the timing reference corresponding to the current drive segment and the line level specifically includes: If the input edge event is detected within the current drive segment, it is determined that the input edge event is associated with the timing transition of the local PWM instruction, and the category of the input edge event is marked as a local edge. If the input edge event is not detected in the current drive segment, the logic level corresponding to the line level is read, and the external pull-down state independently maintained by the thermal management actuator is determined based on the logic level. Combining the determination conclusions regarding the local edge or external pull-down state within the current driving segment, and the determination conclusions of the previous adjacent driving segment, the final category of the input edge event captured within the current driving segment is determined according to preset rules. After completing the falling and rising edge processing of the native PWM command for a full cycle, the input capture flag corresponding to the current cycle is cleared so that edge capture and classification can be performed again in the drive segment of the next cycle.
[0036] Figure 3This is a schematic diagram of the external pull-down timing for the local PWM phase correlation in an embodiment of this application, as shown below. Figure 3 As shown, the timing diagram sequentially displays the local PWM comparison event signal, the single-wire interface node level signal, and the input capture flag signal from top to bottom. The local PWM comparison event signal indicates the moment when the local PWM command triggers a toggle in the output comparison unit; its vertical solid line indicates the predetermined level switching moment. The single-wire interface node level signal represents the actual line level waveform on the single-wire interface node, vertically divided into multiple drive segments. The input capture flag signal indicates whether the input capture unit has captured an input edge event within each drive segment. At the end of each complete PWM cycle, the input capture flag for the current cycle is cleared so that edge capture and classification can be performed again in the next cycle. Combined with... Figure 3 The timing relationship shown indicates that the controller determines the time boundary and theoretical expected level of each drive segment based on the occurrence time of the local PWM comparison event. Based on this, it classifies the captured input edge events. Edges belonging to the local PWM toggle are marked as local edges and suppressed, while edges belonging to the actuator's external pull-down are extracted as the actual pull-down action state for subsequent decoding.
[0037] If an input edge event is detected by the input capture unit within the current drive segment, it is first determined that the occurrence time of the input edge event corresponds to the predetermined level switching time of the local PWM command. Specifically, since the time boundary of the current drive segment is based on the predetermined level switching time of the local PWM command, the input edge event captured within this segment is highly likely to correspond to the level flip of the local PWM command at that switching time. Based on this, the input edge event is categorized as a local edge. It should be noted that a local edge refers to the signal transition generated when the controller outputs a PWM command. Its occurrence time is near the predetermined level switching time of the local PWM command. It is an edge signal generated by the controller's own output behavior on the single-wire interface node and does not represent any feedback intention of the actuator.
[0038] If no input edge event is detected within the current drive segment, the logic level corresponding to the current line level of the single-line interface node is read, and the existence of an external pull-down state independently maintained by the thermal management actuator is determined based on this logic level. Specifically, when the local PWM command is in the high-level output range, if the line level is actually low, it indicates that the actuator is actively pulling the line low, i.e., an external pull-down state exists; when the local PWM command is in the low-level output range, if the line level is actually high, it also indicates that the actuator is transmitting status information by releasing the pull-down. Since no edge event is captured within this drive segment, it means that the change in line level did not occur within this segment, but rather that the actuator had pulled the line low or released it at some point in the past and maintained it until now. In this state, the actuator's pull-down action is a continuous state independent of the local PWM switching behavior.
[0039] In actual operation, the signal state changes on a single-line interface node are continuous in time, and there may be a timing correlation between the edge state of the current drive segment and the edge state of the previous drive segment. For example, if an external pull-down state has been determined in the previous drive segment, and a rising edge from low to high is detected in the current drive segment, this rising edge should be comprehensively determined as a feedback edge generated by the actuator releasing the pull-down, rather than a local edge generated by the local PWM flip. Conversely, if a local edge is determined in the previous drive segment, and an edge event is detected in the current drive segment, it is necessary to re-determine based on the timing reference of the current segment. By introducing the determination conclusions of adjacent segments as a reference factor for comprehensive judgment, the critical situation where the edge event happens to occur near the boundary of two drive segments can be effectively handled, avoiding misclassification due to one-sided judgment within a single segment.
[0040] Since each PWM cycle contains a falling edge and a rising edge (corresponding to the switching between high and low level segments), the current PWM cycle is considered complete when both predetermined level switching moments have been processed. At this point, the capture flags accumulated in the current cycle in the input capture unit are cleared, resetting the state of the capture unit. At the start of the next PWM cycle, based on the initial state cleared in the previous cycle, edge capture and category determination are re-performed in the new drive segment. Through the above cycle-end clearing mechanism, it is ensured that the determination logic for each PWM cycle is established independently, avoiding cumulative interference from edge events or capture flags left over from the previous cycle, and guaranteeing the accuracy and consistency of category determination within each cycle.
[0041] In some embodiments, the step of accumulating the feature parameters of the actual pull-down action state on the time axis to obtain the duration of the external pull-down activity, and querying a preset state window mapping table based on the duration of the external pull-down activity to decode and obtain the current diagnostic state of the thermal management actuator specifically includes: The extracted actual pull-down action state is discretized and sampled according to a preset fixed time sampling period; When the actual pull-down action state is sampled as an external pull-down activity, the activity counter is incremented; when the actual pull-down action state is sampled as a non-external pull-down activity, the inactivity counter is incremented. When the actual drop-down action state is detected to change from active to inactive or from inactive to active, the transition edge is used as the settlement trigger condition. The current count values of the activity counter and the inactive counter are read respectively, and each is multiplied by the fixed time sampling period to calculate the external drop-down activity duration and the external inactive duration. The duration of the external drop-down activity is matched one by one with multiple preset state intervals in the state window mapping table. When the duration of the external drop-down activity falls into the target state interval in the state window mapping table, the state corresponding to the target state interval is decoded as the current diagnostic state of the thermal management actuator.
[0042] After edge culling and extraction of the actual pull-down action state, this state is represented on the time axis as a continuous, time-varying sequence, with values falling into either "external pull-down activity" or "non-external pull-down activity." To facilitate digital measurement of these states by the controller, this continuous state sequence needs to be discretized at fixed time intervals. Specifically, a fixed sampling period Ts is set, and the current actual pull-down action state is sampled and read every Ts. Through this discretization, the continuously changing state signal on the time axis is converted into a series of discrete sampling points, each recording the specific value of the actual pull-down action state at that moment. The value of Ts determines the time resolution of the measurement; a smaller Ts results in higher measurement accuracy but also increases the computational resource consumption of the controller; a larger Ts reduces resource consumption but may lose details of short state pulses. In practical applications, the value of Ts can be determined comprehensively based on the actuator's feedback pulse width, the controller's processing capability, and real-time requirements.
[0043] Two independent counters are set up: an active counter (CounterA) and an inactive counter (CounterI). At the end of each sampling period Ts, a judgment is made based on the actual pull-down action state obtained from the current sampling: if the state is an active pull-down, CounterA increments by 1, while CounterI remains unchanged; if the state is not an active pull-down, CounterI increments by 1, while CounterA remains unchanged. If either the active or inactive counter reaches its maximum value, it remains unchanged. Through this dual-counter accumulation mechanism, starting from the moment the actual pull-down action state is successfully extracted, the two counters independently accumulate the "number of samples in the active state" and the "number of samples in the inactive state." Since each sampling period Ts is fixed and known, the product of CounterA and Ts is the duration of the active pull-down, Ta, and the product of CounterI and Ts is the duration of the inactive pull-down, Ti.
[0044] The actuator encodes different diagnostic states by pulling the single-line interface node low for varying durations. This means that a complete feedback message is expressed as a sequence consisting of an "active period" and its subsequent "inactive period." Obtaining only the activity duration at a single moment is insufficient to understand the complete state information transmitted by the actuator; it is necessary to determine the start and end boundaries of each feedback pulse. Therefore, this application uses the moment when the actual pull-down action state transitions to a transition edge as the settlement trigger condition. The transition edge includes two scenarios: the actual pull-down action state transitions from external pull-down activity to non-external pull-down activity (i.e., rising edge, actuator releases pull-down), and transitions from non-external pull-down activity to external pull-down activity (i.e., falling edge, actuator actively pulls the line low). When either of these transition edges is detected, it means that the currently ongoing active or inactive period has ended, and a new period is about to begin. Therefore, this transition edge is the appropriate time to perform duration settlement. When the transition edge arrives, the current count values of the activity counter CounterA and the inactive counter CounterI are read respectively. Multiply CounterA by the sampling period Ts to obtain the external pull-down activity duration Ta; multiply CounterI by the sampling period Ts to obtain the external inactivity duration Ti. After calculation, both counters can be reset to zero to begin measuring the next set of active / inactive sequences, or the current values can be retained for subsequent calculations as needed.
[0045] The status window mapping table is a set of configuration parameters pre-stored in the thermal management controller, containing activity duration intervals corresponding to various diagnostic states. Each diagnostic state corresponds to a continuous duration interval, the upper and lower limits of which can be calibrated and configured according to the specific feedback protocol of the actuator. Taking a specific embodiment applied to an electric water pump as an example, the status window mapping table can be configured as follows: an activity duration interval of 400ms to 600ms corresponds to the normal heartbeat state; an activity duration interval of 900ms to 1100ms corresponds to the dry running state; an activity duration interval of 1400ms to 1600ms corresponds to the locked rotor or overcurrent state; an activity duration interval of 1900ms to 2100ms corresponds to the overtemperature state; and an activity duration interval of 2400ms to 2600ms corresponds to other fault states. In another embodiment applied to a cooling fan, the status window mapping table can be configured as follows: 800ms–1200ms corresponds to the normal state; 1800ms–2200ms corresponds to the stalled state; 2800ms–3200ms corresponds to the overcurrent state; and 3800ms–4200ms corresponds to the internal fault state. After calculating the duration Ta of the external pull-down activity, Ta is compared sequentially with each state interval in the status window mapping table. When Ta falls within the range of a certain state interval (i.e., the lower limit of the interval ≤ Ta ≤ the upper limit of the interval), the diagnostic state corresponding to that state interval is decoded as the current diagnostic state of the thermal management actuator. If Ta fails to fall within any state interval in the status window mapping table, the current diagnostic state can be determined as an unknown state, a frequency abnormal state, or the state confirmed in the previous cycle can be maintained. The specific processing method can be configured according to the actual application requirements.
[0046] In some embodiments, the method further includes: Detect whether the external inactivity duration or external pull-down activity duration of the actual pull-down action state exceeds a preset no-input timeout threshold; If the external inactivity duration or the external pull-down activity duration exceeds the no-input timeout threshold, then the target duty cycle parameter of the current local PWM instruction is read, and the target duty cycle parameter is compared with the preset drive threshold duty cycle. When the target duty cycle parameter is greater than the drive threshold duty cycle, it is determined that the current driving state is effective, and candidate fault states including no input disconnection or frequency abnormality are generated. When the target duty cycle parameter is less than or equal to the drive threshold duty cycle, it is determined that the current state is in the zero command or stop interval, the generation of the candidate fault state is suppressed, and the current diagnostic state is maintained as the stop or idle state.
[0047] Under normal operating conditions, the thermal management actuator periodically returns status information to the controller by pulling down the single-line interface node according to its feedback protocol. This feedback information is represented on the timeline as a series of alternating periods of external pull-down activity and external inactivity. Therefore, neither the duration of external pull-down activity nor external inactivity should continue indefinitely without a state transition. The no-input timeout threshold is a pre-configured time threshold in the controller, which physically means the maximum allowable time for the actual pull-down action state to remain in the same state (continuous activity or continuous inactivity) without transitioning, under the condition that the actuator should be operating normally. When the duration of the actual pull-down action state continuously in the active state (i.e., the line is pulled low for a long time) or continuously in the inactive state (i.e., the line is released for a long time) exceeds this threshold, it indicates that the actuator may have stopped returning valid feedback signals, triggering the no-input anomaly detection condition.
[0048] Timeout itself does not directly equate to actuator failure, because there is an important non-fault scenario: the controller actively sends a PWM command with zero or extremely low duty cycle to the actuator, which means instructing the actuator to stop operating or enter standby mode. When the actuator is in a stopped or standby state, it naturally will not return periodic heartbeat or status feedback signals. Therefore, even if the line is inactive for a long time (Ta remains 0 or Ti continuously increases), this is normal and should not be diagnosed as a no-input fault. Therefore, to accurately distinguish between the fault scenario of "no feedback when feedback is expected" and the stop scenario of "no feedback when feedback is unnecessary," the duty cycle of the current local PWM command needs to be introduced as a joint judgment condition in addition to timeout detection. Only when both the timeout condition and the drive condition are met simultaneously does a valid no-input fault trigger condition exist. Specifically, the target duty cycle parameter Dcmd of the current local PWM command is read from the controller's PWM command generation unit. The target duty cycle is the PWM output value calculated by the controller based on upper-level requests (such as target speed, target water temperature, etc.), reflecting the strength of the controller's current drive command to the actuator. The preset drive threshold duty cycle Dth is a pre-calibrated boundary value, whose physical meaning is: the minimum PWM duty cycle value required for the actuator to exit the stop state and enter the normal working state. When the actual output PWM duty cycle is greater than this threshold, it indicates that the controller has issued a valid working command to the actuator, and the actuator should be in operation and return a feedback signal; when the actual output PWM duty cycle is less than or equal to this threshold, it indicates that the controller has not issued a valid working command to the actuator, and the actuator is in a stop or standby state.
[0049] In this situation, the controller has issued a valid operating command to the actuator (Dcmd>Dth), but the actuator fails to return a valid feedback signal for a period exceeding the no-input timeout threshold (Ta or Ti continuously times out). The combination of these two factors reasonably suggests an actuator malfunction. Specifically, this malfunction may stem from various fault causes: for example, a broken actuator power supply line causing complete inoperability (wire breakage fault); damage to the actuator's feedback drive circuit preventing it from pulling the line low (feedback failure fault); or internal jamming of the actuator preventing both operation and the return of a heartbeat signal (mechanical fault). Although these different fault causes differ in their physical origins, they all manifest as "no valid feedback waveform returned for a long time" at the single-line interface node, thus falling under the category of no-input malfunction. Furthermore, in some cases, although the external inactivity duration or external pull-down activity duration exceeds the no-input timeout threshold, extremely brief and irregular level transitions still occur at the single-line interface node, failing to form a complete and valid feedback pulse sequence that meets the requirements of the state window mapping table. This situation is typically categorized as a frequency anomaly, distinct from a disconnection fault where no edge events occur. Preferably, the two scenarios can be output separately: if no input edge events are detected during the timeout period, a disconnection fault candidate is generated; if sporadic edge events are detected during the timeout period but cannot form a valid status pulse, a frequency anomaly fault candidate is generated. Both are collectively referred to as candidate fault states for further processing by subsequent confirmation mechanisms.
[0050] When Dcmd ≤ Dth, the PWM command currently issued by the controller instructs the actuator to be in a zero-speed or stopped state. In this state, the actuator does not receive a valid working command, and even if it is intact, it will not actively return a heartbeat signal or periodic status feedback. This is the normal behavior of the actuator in the stopped state, not an abnormal performance. Therefore, even if Ta or Ti is detected to exceed the no-input timeout threshold at this time, no no-input fault state should be generated. Specifically, the generation of candidate fault states is suppressed by logical judgment, that is, the fault state assignment process is skipped, no fault code is written to the fault state register, and the current diagnostic state is forcibly maintained as the stopped or idle state to ensure that the system will not erroneously trigger fault alarms due to the silent performance of the actuator during normal shutdown. In addition, while suppressing the generation of candidate faults, the accumulated active counter CounterA and inactive counter CounterI can be cleared or frozen to avoid the value overflow caused by the continuous accumulation of the counter in the stopped state, and the metering will restart with the initial state after clearing when entering the next effective drive state.
[0051] In some embodiments, reading the target duty cycle parameter of the current local PWM instruction and comparing the target duty cycle parameter with a preset drive threshold duty cycle specifically includes: The target logic duty cycle of the current cycle is read from the control request, and the physical duty cycle of the current actual output is read. The target logic duty cycle and the physical duty cycle are checked for consistency. When the absolute value of the deviation between the target logic duty cycle and the physical duty cycle is less than the preset duty cycle deviation tolerance, the physical duty cycle is used as the effective duty cycle to participate in the subsequent threshold comparison. Obtain a set of drive threshold parameters that matches the type of thermal management actuator connected to the current channel. The set of drive threshold parameters includes a main drive threshold and a minimum sustain drive threshold, wherein the main drive threshold is greater than the minimum sustain drive threshold. If the effective duty cycle is greater than the main drive threshold, it is determined that the current state is strong drive and the no-input diagnostic function is fully enabled. If the effective duty cycle is between the main drive threshold and the minimum sustain drive threshold, it is determined that the current state is weak drive, and no-input diagnosis is performed with reduced diagnostic sensitivity. The reduced diagnostic sensitivity is achieved by multiplying the no-input timeout threshold by a preset sensitivity reduction factor. If the effective duty cycle is less than or equal to the minimum sustain drive threshold, it is determined that the current state is non-drive, the no-input diagnostic function of the current channel is turned off, the current diagnostic state is kept in standby or idle state, and the accumulated candidate fault counter is cleared.
[0052] In PWM output, there are two different duty cycle parameters: the first is the target logical duty cycle, Dcmd, which originates from the ideal duty cycle request value calculated by the upper-level control algorithm (such as a PID controller, lookup table calibration value, etc.) based on the current control requirements and is stored in the controller's software variable; the second is the physical duty cycle, Dact, which originates from the actual duty cycle of the PWM waveform output from the timer hardware unit to the single-line interface node and is determined by the configuration value of the timer compare register. Under normal circumstances, these two should remain consistent or have only a very small numerical deviation. However, in actual engineering, the following reasons may cause deviations: timer configuration errors leading to untimely updates of the shadow register, hardware failures in the PWM output channel, misalignment of the duty cycle update time with the timer period boundary leading to update loss, and electromagnetic interference under extreme operating conditions. When Dcmd and Dact show a significant deviation, it means that the "duty cycle that the controller believes it is outputting" is inconsistent with the "duty cycle that the controller is actually outputting." If only Dcmd is used as the basis for comparing the drive threshold at this time, the following misjudgment may occur: Dcmd is greater than the drive threshold (the software considers it to be driving), while Dact is less than or equal to the drive threshold (the hardware does not actually output a valid drive), causing the controller to falsely report a no-input fault when the actuator has no feedback, while the real reason is that the controller's own output channel is abnormal. To avoid the above blind spot, this application first performs a consistency check of the software and hardware duty cycle before performing the drive threshold comparison. Specifically, Dcmd and Dact are read simultaneously, and the absolute value of their deviation ΔD=|Dcmd-Dact| is calculated. Then, ΔD is compared with the preset duty cycle deviation tolerance ΔDth. ΔDth is a pre-calibrated allowable deviation threshold, the value of which takes into account engineering factors such as timer resolution, duty cycle update delay, and measurement quantization error. When ΔD < ΔDth, the current duty cycle output is determined to be normal, and Dact is used as the effective duty cycle Dvalid for subsequent threshold comparisons; when ΔD ≥ ΔDth, the current duty cycle output is determined to be abnormal. At this time, the no-input diagnostic function is paused and the PWM output channel is reported as abnormal to avoid misjudging the actuator as having no input due to the controller's own output failure.
[0053] Different types of thermal management actuators have different drive characteristics. For example, cooling fans typically require a high PWM duty cycle to overcome static friction and start operating, while electric water pumps can start and maintain circulation with a lower duty cycle. Furthermore, the same actuator has different drive requirements at different operating stages; a higher duty cycle is needed to overcome inertia during startup, while a lower duty cycle is sufficient to maintain the current speed during maintenance. Therefore, using a single fixed drive threshold cannot meet the differentiated diagnostic needs of multiple actuator types and operating stages. To address this, this application pre-stores drive threshold parameter sets corresponding to each actuator type in the controller. The drive threshold parameter set contains two different levels of threshold values: the main drive threshold Dth1 and the minimum maintenance drive threshold Dth2, where Dth1 > Dth2. The main drive threshold Dth1 corresponds to the minimum duty cycle threshold required for normal actuator operation. When the effective duty cycle is greater than Dth1, the actuator should be in full-function operation and return complete feedback signals (including periodic heartbeats and various status pulses). The minimum sustaining drive threshold Dth2 corresponds to the minimum duty cycle threshold required for the actuator to maintain its current state without performing any active actions. When the effective duty cycle is between Dth1 and Dth2, the actuator is in the critical operating region, and its feedback behavior may be uncertain—it may return a partial feedback signal or stop feedback due to insufficient driving force.
[0054] When Dvalid > Dth1, it indicates that the PWM command output by the controller has sufficient driving capability to enable the actuator to enter a stable, fully functional operating state. In this state, the actuator should operate normally and periodically return heartbeat signals and various status feedbacks according to its feedback protocol. If a no-input timeout is detected at this time, it is considered with high confidence that the actuator has a genuine fault and should not be suppressed or reduced. Therefore, in the strong drive state, the no-input diagnostic function operates with full sensitivity, i.e., using the default no-input timeout threshold (without any reduction). Once Ta or Ti is detected to exceed this threshold, a candidate fault state is immediately generated. This ensures that under conditions where the actuator truly needs to operate, any feedback anomalies can be detected and reported promptly and sensitively, without missing faults due to insufficient sensitivity.
[0055] When Dth2<Dvalid≤Dth1, it indicates that the PWM command output by the controller is in the critical driving interval, and this duty ratio is sufficient to enable the actuator to start or maintain basic operation, but may not be sufficient to support the actuator to stably return a complete feedback signal under all working conditions. In this state, the following situation may exist: the actuator itself is intact, but due to insufficient driving voltage or current, its internal circuit is in an unstable working region, resulting in the feedback signal being intermittent or the feedback pulse width deviating from the normal range. If the no-input diagnosis is performed with full sensitivity, the aforementioned feedback instability caused by insufficient driving may be misjudged as an actuator fault. To solve the above problem, the present application performs the no-input diagnosis with a reduced diagnostic sensitivity in the weak driving state. Specifically, a reduced timeout threshold T'timeout=Ttimeout×k is obtained by multiplying the preset no-input timeout threshold Ttimeout by a sensitivity reduction factor k (where 0<k<1). Since k is less than 1, the reduced threshold is more lenient than the original threshold (that is, a longer no-feedback time is allowed without triggering a fault), thereby reducing the sensitivity of detecting actuator feedback anomalies in the weak driving state. The specific value of the reduction factor k can be calibrated according to the feedback characteristics of the actuator in the weak driving interval. For actuators whose feedback signals are still relatively stable in the critical driving interval, k can take a larger value (close to 1) with only a small amount of reduction; for actuators whose feedback signals fluctuate greatly in the critical driving interval, k can take a smaller value to provide more lenient diagnostic conditions.
[0056] When Dvalid ≤ Dth2, it indicates that the current output PWM command of the controller is lower than the minimum duty cycle threshold required for the actuator to maintain operation, and the actuator is in a stopped or standby state. In this state, the actuator does not receive a valid working command and will not actively return any feedback signal; its feedback pin is in a high-impedance state or a silent state. If no-input diagnostics are enabled at this time, a timeout will inevitably be detected and a fault will be triggered, resulting in a false alarm. Therefore, this application completely disables the no-input diagnostic function of the current channel in the non-drive state, that is, it suspends the timeout monitoring of Ta and Ti and does not perform any timeout threshold comparison operations. At the same time, the current diagnostic state is forcibly maintained in the standby or idle state to ensure that the diagnostic output is consistent with the actual operating condition of the actuator. In addition, during the long period when the actuator is in the non-drive state, the cumulative values of the active counter CounterA and the inactive counter CounterI may have accumulated to a large value. If these historical cumulative values are not cleared when entering the drive state in the next cycle, it may cause a false fault to be triggered immediately when entering the drive state due to the historical cumulative value exceeding the threshold. Therefore, this application clears all accumulated candidate fault counters to zero while disabling the diagnostic function. Candidate fault counters include, but are not limited to, the active counter CounterA, the inactive counter CounterI, and various candidate state counters used for continuous and consistent acknowledgment. By clearing the counters, it is ensured that all counters begin measuring with initial zero values the next time a strong or weak drive state is entered, avoiding momentary false alarms caused by interference from historical accumulated values.
[0057] In some embodiments, after decoding to obtain the current diagnostic status of the thermal management actuator, the method further includes a power-on shielding and continuous consistency confirmation step, specifically including: During the preset shielding period after the thermal management controller is powered on and initialized, the extraction and accumulation of the actual pull-down action state are continuously performed, and the external output of the fault state is shielded. The current diagnostic state is set to the normal state and a normal mask is output to avoid false alarms caused by power-up transients. After the preset blocking period ends, the query permission for the status window mapping table is enabled, and the diagnostic status obtained from each query is cached as a candidate diagnostic status. Within each control cycle, the candidate diagnostic status cached in the current cycle is compared with the candidate diagnostic status cached in the previous control cycle for consistency. If the candidate diagnostic state cached in this cycle is consistent with the candidate diagnostic state cached in the previous control cycle, the consistency counter is incremented until the count value of the consistency counter reaches the preset consecutive confirmation number threshold. The candidate diagnostic state is then determined as the final confirmation state and output to the outside. If the candidate diagnostic state cached in this cycle is inconsistent with the candidate diagnostic state cached in the previous control cycle, the consistency counter is reset to filter out state jumps caused by edge jitter and window boundary fluctuations.
[0058] After the controller is powered on and initialized, a preset shielding period timer is started. The duration of the preset shielding period, Tb, is pre-calibrated and its value should be greater than the total time required for the controller and actuator to power on and establish. In one embodiment of the present invention, the preset shielding period Tb is set to 4000ms, which is sufficient to cover the power-on establishment process of most thermal management controllers and actuators. Within the preset shielding period Tb, on the one hand, the input capture unit continues to work, and the extraction and accumulation operations of the actual pull-down action state are performed normally. The continuity of all feedback data during power-on is ensured through "uninterrupted measurement," avoiding the loss of feedback information during the startup phase due to measurement starting only after the shielding period ends. On the other hand, the query results of the status window mapping table are either shielded or forcibly overwritten. Regardless of the actual decoding result, the current diagnostic state is forcibly set to the normal state, and this normal state is output externally in the form of a normal mask. The normal mask is a standard encoded value indicating that the actuator is in a normal state, such as a status byte with a specific value in some communication protocols.
[0059] After the preset shielding period Tb expires, the power supplies of both the controller and actuator have stabilized, and the signals of the single-line interface nodes have entered normal operating condition, thus meeting the conditions for outputting valid diagnostic results. Therefore, query permissions for the status window mapping table are granted, enabling the window matching decoding in step S105 to execute normally, and storing the diagnostic state obtained from each decoding as a candidate diagnostic state in the buffer. The candidate diagnostic state is an intermediate state value that has not yet been finally confirmed, representing the decoding conclusion obtained based on a single window matching result at the current moment. Since a single decoding may be affected by edge jitter or window boundary fluctuations, resulting in random deviations, this candidate state is not directly output but is used as input for subsequent continuous and consistent confirmation processes. The buffer stores at least the candidate diagnostic states of the current control cycle and the previous control cycle to support inter-cycle comparison operations.
[0060] The control cycle is a fixed time interval for the thermal management controller to execute the upper-layer application, typically consistent with or an integer multiple of the fixed sampling cycle Ts mentioned in the preceding steps. At the arrival of each control cycle, the candidate diagnostic state Statecurr (decoded in the current control cycle) and the candidate diagnostic state Stateprev (decoded in the previous control cycle) are read from the buffer and compared. Since the diagnostic state of the thermal management actuator does not physically undergo extremely frequent jumps—for example, the actuator cannot jump from a normal state to a stalled state and back to a normal state within a few milliseconds—the diagnostic states between adjacent control cycles should be physically consistent. When Statecurr and Stateprev are the same, it indicates that the conclusions obtained from two consecutive decodings are consistent, and this state has high reliability. When Statecurr and Stateprev are different, it indicates that at least one decoding may have been affected by interference or window boundary fluctuations, requiring further observation.
[0061] A consistency counter CounterC is set with an initial value of 0, for accumulating the number of consecutive consistency times of the candidate diagnostic state. After completing the above consistency comparison in each control cycle, the following branches are executed according to the comparison result: when Statecurr is consistent with Stateprev, increment CounterC by 1, and compare the incremented count value with a preset consecutive confirmation count threshold M. If CounterC < M, the current candidate state remains in an unconfirmed state and is not output externally; if CounterC ≥ M, it indicates that the candidate diagnostic state has been consistent for M consecutive times and has sufficient confidence, at this time, the candidate diagnostic state is determined as the final confirmed state and output externally. The consecutive confirmation count threshold M is configured according to the feedback period of the actuator and the system's requirements for the safety level. In one embodiment of the present invention, M is set to 2. When Statecurr is inconsistent with Stateprev, it indicates that the consecutive consistency is broken, which may be that the previous state is misjudged due to jitter, the current state is misjudged due to window boundary fluctuation, or the actuator indeed undergoes state switching. Regardless of the reason, since the consistency has been destroyed, the consistency counter CounterC is cleared, and the accumulation is restarted. Through the reset operation, any state must re-meet the condition of M consecutive consistencies before becoming the final confirmed state. Through the above consecutive consistency confirmation mechanism, candidate state jumps caused by single occasional edge jitter, timer capture errors or window boundary value fluctuations are effectively filtered out because they cannot meet the condition of M consecutive consistencies, and will not be output externally. For a real actuator state switch, since the new state is continuously and stably decoded, it will be confirmed and output after M consecutive control cycles, ensuring the timeliness of state switching. At the same time, for the situation near the boundary of adjacent windows in the state window mapping table, for example, the upper limit of the normal state window is 600ms, and the lower limit of the locked-rotor state window is 900ms, when the actual feedback duration fluctuates in the undefined interval between 600ms and 900ms, the decoding result may jump back and forth between the normal state and the unknown state. Through the consecutive consistency confirmation mechanism, such boundary fluctuations are effectively suppressed, and state values that jump frequently will not be output externally.
[0062] Figure 4 is a schematic diagram of the feedback timing, state decoding and fault confirmation process in the embodiment of the present application, as shown in Figure 4As shown, the process includes the following steps: Discretize and sample the extracted actual pull-down action state according to a preset fixed control cycle. When an external pull-down activity is sampled, increment the activity duration Ta; when a non-external pull-down activity is sampled, increment the inactivity duration Ti. In each control cycle, detect whether the actual pull-down action state has a configured transition edge. If a transition edge is detected (the "Yes" branch in the diagram), use the transition edge as the settlement trigger condition. Query the state window mapping table based on the currently accumulated activity duration Ta, and decode the state corresponding to the state interval into which Ta falls as the actuator's diagnostic state. Simultaneously, calculate the feedback equivalent duty cycle Dfb = Ti / (Ta+Ti)×100% based on the activity duration Ta and the inactivity duration Ti. If no transition edge is detected (the "No" branch in the diagram), check whether the currently accumulated activity duration Ta or the inactivity duration Ti exceeds a preset no-input timeout threshold, and whether the target duty cycle of the PWM instruction meets the preset drive conditions. If both conditions are met, a candidate fault state is generated; if the PWM instruction does not meet the driving conditions (i.e., it is in the zero command or stop interval), fault generation is suppressed, and the current diagnostic state is maintained as stop or idle. During the preset masking period after the thermal management controller is powered on, the update operation of the active duration Ta and the inactive duration Ti is continuously executed, but the external output of the fault state is masked. After the preset masking period ends, the candidate state obtained from each decoding is continuously and consistently confirmed. When the number of consecutively consistent candidate states reaches a preset number M, the candidate state is determined as the final confirmed state and output externally; if the candidate state changes in any control cycle, the consistency counter is reset.
[0063] In some embodiments, the method further includes: Obtain the output comparison event interrupt signal output when the local PWM instruction triggers a toggle in the output comparison unit, and lock the trigger time of the output comparison event interrupt signal as the absolute segmentation time beacon of the current complete cycle; Based on the target duty cycle parameter of the currently output local PWM command, the left region of the absolute segmented time beacon on the time axis is divided into a first phase segment, and the right region of the absolute segmented time beacon on the time axis is divided into a second phase segment. Read the preset interface output polarity configuration parameters of the single-line interface node, and convert the logic levels of the first phase segment and the second phase segment into the corresponding expected theoretical line level values according to the interface output polarity configuration parameters. When capturing the input edge event, if the arrival time of the input edge event is within a preset range of the time boundaries of the first phase segment and the second phase segment, and the changed line level is consistent with the expected value of the theoretical line level, the input edge event is pre-judged as the local edge and marked for rejection.
[0064] In the PWM generation mechanism of a microcontroller, the output comparator unit is a hardware module responsible for triggering a level transition when a predetermined count value matches. Specifically, a timer increments at a fixed frequency. When the count value reaches a preset comparison match value, the output comparator unit automatically toggles the level of the PWM output pin (from high to low or from low to high), and simultaneously generates an output comparator event interrupt signal to notify the CPU that the transition event has occurred. The trigger moment of the output comparator event interrupt signal is the instant at which the local PWM instruction physically transitions at the predetermined level switching time. Because this interrupt signal is directly triggered by the hardware comparison match event, without indirect calculation through software polling or timer overflow, its trigger moment has high accuracy and determinism; it precisely corresponds to the instant when the PWM waveform undergoes a level transition on the physical pin. This application locks this trigger moment as the absolute segmentation time beacon of the current complete cycle. An absolute segmentation time beacon refers to a time boundary point used to divide a complete PWM cycle into different regions or segments on the time axis. Since the rising and falling edges of the local PWM command are the only two predetermined level switching moments within a cycle, these two moments constitute natural time boundaries within that cycle. These boundaries are locked using an output compare interrupt signal, providing a hardware-level time reference for subsequent phase segmentation.
[0065] After locking the absolute time beacon of the current complete cycle, the entire cycle of the local PWM instruction near that beacon is divided into two adjacent drive segments, using the time point where the beacon is located as the dividing line. Taking a complete cycle of the local PWM instruction as the object of consideration, this cycle consists of two parts: a high-level segment and a low-level segment. In a complete cycle of the local PWM instruction, the ratio of the duration of the high-level segment to the cycle is the duty cycle, and the ratio of the duration of the low-level segment to the cycle is 1 minus the duty cycle. Since the target duty cycle parameter D is known, the time widths of both the high-level and low-level segments are known and can be calculated. The left and right regions of the absolute time beacon correspond to the time intervals before and after the occurrence of the time beacon, respectively. Taking the falling edge time beacon as an example, its left region is the time interval before the occurrence of the falling edge (i.e., the end of the high-level segment), and its right region is the time interval after the occurrence of the falling edge (i.e., the beginning of the low-level segment). Using the above division method, a complete cycle of the local PWM instruction is divided into two adjacent phase segments with the predetermined level switching time as the dividing point, one corresponding to the phase before the level switching and the other corresponding to the phase after the level switching.
[0066] In practical thermal management control systems, different actuator manufacturers or different communication protocols may have different requirements for the polarity of PWM signals. Some actuators use positive logic (active high, i.e., a higher duty cycle corresponds to a higher speed), while others use inverse logic (active low, i.e., a lower duty cycle corresponds to a higher speed). Accordingly, the controller's single-wire interface node needs to be configured with corresponding output polarity parameters to adapt to different types of actuators. The interface output polarity configuration parameter is used to indicate the output polarity mode of the current channel. When configured for positive output, the timer compares and matches, outputting a high level; when compared and mismatches, outputting a low level. When configured for inverted output, the timer compares and matches, outputting a low level; when compared and mismatches, outputting a high level. Under different output polarity configurations, the same phase segment (e.g., the interval before the falling edge) may correspond to different actual line levels. For example, under a positive output configuration, the line level corresponding to the interval before the falling edge (the high-level segment) should be high; while under an inverted output configuration, the line level corresponding to the interval before the falling edge (the original high-level segment output after inversion) should be low. Therefore, it is necessary to read the preset interface output polarity configuration parameters of the current channel and convert the logic levels of the first and second phase segments into the corresponding expected values of the actual line theoretical levels based on these parameters. Specifically, based on the logic level of the PWM waveform under ideal conditions, the conversion is performed in conjunction with the output polarity configuration. If the current configuration is positive output, the logic level directly corresponds to the line level; if the current configuration is negative output, the logic level is inverted to obtain the line level.
[0067] Using the acquired absolute time beacon and the expected theoretical line level, a dual-verification prediction is performed on the captured input edge events. The first verification in this dual-verification is a time-domain position verification: determining whether the arrival time of the input edge event is within a preset range of the time boundaries of the first and second phase segments. As mentioned earlier, the first and second phase segments are separated by the absolute time beacon, and the predetermined level switching time of the local PWM command is precisely this boundary point. Therefore, ideally, the local edge should occur precisely at the time boundary of the first and second phase segments. Considering engineering factors such as timer resolution and hardware delay, the verification condition is relaxed to be within a preset range of the time boundaries of the first and second phase segments, meaning that it can be determined to pass the time-domain verification within a tolerance window before and after the time boundary. Conversely, the occurrence time of the external feedback edge generated by the actuator feedback is determined by the internal logic of the actuator and has no fixed phase correlation with the local PWM timing, and usually will not fall near the aforementioned predetermined time boundary. The second layer of verification is logic level verification: determining whether the line level after an edge transition matches the calculated expected theoretical line level. Each level transition of the local PWM instruction follows predetermined logic rules. If the current output polarity is configured as positive, the level should be high after the rising edge and low after the falling edge; if the current output polarity is configured as inverted, the level should be low after the rising edge and high after the falling edge. Therefore, the line level in the stable state after a local edge transition must be definite and predictable. When the level after an edge transition matches the expected theoretical line level for that phase segment, the edge passes the level verification. When an input edge event passes both the time-domain position verification and the logic level verification simultaneously—that is, when its arrival time is near a predetermined time boundary and the level after the transition matches the expected theoretical value—then the input edge event is pre-judged as a local edge and marked for rejection. Edge events marked as to be rejected will be prioritized for identification in the classification determination in step S103, and will be directly rejected without being processed as feedback signals of the actuator when the actual pull-down action state is extracted in step S104.
[0068] The above describes the method for controlling and providing status feedback of the thermal management actuator in the embodiments of this application. The computer system in the embodiments of this application will be described in detail below in conjunction with the above method for controlling and providing status feedback of the thermal management actuator.
[0069] Please see Figure 5 This is a schematic diagram of an exemplary hardware structure of a computer system in an embodiment of this application.
[0070] In some embodiments, the computer system 500 includes a computer device, which may be a terminal device. The computer device includes a processor 501, a memory 502, a sensor module 503, a communication module 504, an input device 505, and an output device 506 connected via a system bus. The processor 501 of the computer device provides computing and control capabilities. The memory 502 of the computer device includes a non-volatile storage medium and internal memory. The non-volatile storage medium stores an operating system, computer programs, and a database. The internal memory provides an environment for the operation of the operating system and computer programs in the non-volatile storage medium. The database is used to store data.
[0071] Those skilled in the art will understand that Figure 5 The structure shown is merely a block diagram of a portion of the structure related to the present application and does not constitute a limitation on the computer device to which the present application is applied. Specific computer devices may include more or fewer components than those shown in the figure, or combine certain components, or have different component arrangements.
[0072] In some embodiments of this application, a computer-readable storage medium is provided, including instructions that, when executed on a computer system 500, cause the computer system 500 to perform the thermal management actuator control and status feedback method of the embodiments of this application.
[0073] In some embodiments of this application, a computer program product is also provided, which, when run on a computer system 500, causes the computer system 500 to execute the thermal management actuator control and status feedback method of the embodiments of this application.
[0074] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit it. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of this application.
[0075] In the above embodiments, implementation can be achieved entirely or partially through software, hardware, firmware, or any combination thereof. When implemented using software, it can be implemented entirely or partially in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., coaxial cable, fiber optic, digital subscriber line) or wireless (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that integrates one or more available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium (e.g., solid-state drive), etc.
[0076] Those skilled in the art will understand that all or part of the processes in the methods of the above embodiments can be implemented by a computer program instructing related hardware. This program can be stored in a computer-readable storage medium, and when executed, it can include the processes described in the above method embodiments. The aforementioned storage medium includes various media capable of storing program code, such as ROM or random access memory (RAM), magnetic disks, or optical disks.
Claims
1. A method for controlling and providing status feedback of a thermal management actuator, characterized in that, Applied to a thermal management controller, wherein the thermal management controller is connected to a thermal management actuator via a single-wire interface node, the method includes: According to the control request, the local PWM command is output to the thermal management actuator through the single-line interface node. Based on the predetermined level switching time of the local PWM command, each complete cycle of the local PWM command is divided into multiple consecutive drive segments. Within each of the drive segments, the input edge events on the single-line interface node are captured, and the line level of the single-line interface node is read. Based on the timing reference corresponding to the current drive segment and the line level, determine the category of the input edge event captured in the current drive segment. The category includes the local edge generated by the local PWM instruction flipping and the external feedback edge generated by the thermal management actuator pulling down the single-line interface node. Based on the classification result, the local edge is removed, and the actual pull-down action state of the thermal management actuator in the current drive segment is extracted; The feature parameters of the actual pull-down action state on the time axis are accumulated to obtain the duration of the external pull-down activity. Based on the duration of the external pull-down activity, a preset state window mapping table is queried, and the current diagnostic state of the thermal management actuator is decoded.
2. The method according to claim 1, characterized in that, The step of determining the category of the input edge event captured in the current drive segment based on the timing reference corresponding to the current drive segment and the line level specifically includes: If the input edge event is detected within the current drive segment, it is determined that the input edge event is associated with the timing transition of the local PWM instruction, and the category of the input edge event is marked as a local edge. If the input edge event is not detected in the current drive segment, the logic level corresponding to the line level is read, and the external pull-down state independently maintained by the thermal management actuator is determined based on the logic level. Combining the determination conclusions regarding the local edge or external pull-down state within the current driving segment, and the determination conclusions of the previous adjacent driving segment, the final category of the input edge event captured within the current driving segment is determined according to preset rules. After completing the falling and rising edge processing of the native PWM command for a full cycle, the input capture flag corresponding to the current cycle is cleared so that edge capture and classification can be performed again in the drive segment of the next cycle.
3. The method according to claim 1, characterized in that, The feature parameters of the actual pull-down action state on the time axis are accumulated to obtain the duration of the external pull-down activity. Based on the duration of the external pull-down activity, a preset state window mapping table is queried, and the current diagnostic state of the thermal management actuator is decoded to obtain the current diagnostic state of the thermal management actuator, specifically including: The extracted actual pull-down action state is discretized and sampled according to a preset fixed time sampling period; When the actual pull-down action state is sampled as an external pull-down activity, the activity counter is incremented; when the actual pull-down action state is sampled as a non-external pull-down activity, the inactivity counter is incremented. When the actual drop-down action state is detected to change from active to inactive or from inactive to active, the transition edge is used as the settlement trigger condition. The current count values of the activity counter and the inactive counter are read respectively, and each is multiplied by the fixed time sampling period to calculate the external drop-down activity duration and the external inactive duration. The duration of the external drop-down activity is matched one by one with multiple preset state intervals in the state window mapping table. When the duration of the external drop-down activity falls into the target state interval in the state window mapping table, the state corresponding to the target state interval is decoded as the current diagnostic state of the thermal management actuator.
4. The method according to claim 3, characterized in that, The method further includes: Detect whether the external inactivity duration or external pull-down activity duration of the actual pull-down action state exceeds a preset no-input timeout threshold; If the external inactivity duration or the external pull-down activity duration exceeds the no-input timeout threshold, then the target duty cycle parameter of the current local PWM instruction is read, and the target duty cycle parameter is compared with the preset drive threshold duty cycle. When the target duty cycle parameter is greater than the drive threshold duty cycle, it is determined that the current driving state is effective, and candidate fault states including no input disconnection or frequency abnormality are generated. When the target duty cycle parameter is less than or equal to the drive threshold duty cycle, it is determined that the current state is in the zero command or stop interval, the generation of the candidate fault state is suppressed, and the current diagnostic state is maintained as the stop or idle state.
5. The method according to claim 4, characterized in that, The step of reading the target duty cycle parameter of the current local PWM instruction and comparing the target duty cycle parameter with the preset drive threshold duty cycle specifically includes: The target logic duty cycle of the current cycle is read from the control request, and the physical duty cycle of the current actual output is read. The target logic duty cycle and the physical duty cycle are checked for consistency. When the absolute value of the deviation between the target logic duty cycle and the physical duty cycle is less than the preset duty cycle deviation tolerance, the physical duty cycle is used as the effective duty cycle to participate in the subsequent threshold comparison. Obtain a set of drive threshold parameters that matches the type of thermal management actuator connected to the current channel. The set of drive threshold parameters includes a main drive threshold and a minimum sustain drive threshold, wherein the main drive threshold is greater than the minimum sustain drive threshold. If the effective duty cycle is greater than the main drive threshold, it is determined that the current state is strong drive and the no-input diagnostic function is fully enabled. If the effective duty cycle is between the main drive threshold and the minimum sustain drive threshold, it is determined that the current state is weak drive, and no-input diagnosis is performed with reduced diagnostic sensitivity. The reduced diagnostic sensitivity is achieved by multiplying the no-input timeout threshold by a preset sensitivity reduction factor. If the effective duty cycle is less than or equal to the minimum sustain drive threshold, it is determined that the current state is non-drive, the no-input diagnostic function of the current channel is turned off, the current diagnostic state is kept in standby or idle state, and the accumulated candidate fault counter is cleared.
6. The method according to claim 1, characterized in that, After decoding to obtain the current diagnostic status of the thermal management actuator, the process further includes a power-on shielding and continuous consistency confirmation step, specifically including: During the preset shielding period after the thermal management controller is powered on and initialized, the extraction and accumulation of the actual pull-down action state are continuously performed, and the external output of the fault state is shielded. The current diagnostic state is set to the normal state and a normal mask is output to avoid false alarms caused by power-up transients. After the preset blocking period ends, the query permission for the status window mapping table is enabled, and the diagnostic status obtained from each query is cached as a candidate diagnostic status. Within each control cycle, the candidate diagnostic status cached in the current cycle is compared with the candidate diagnostic status cached in the previous control cycle for consistency. If the candidate diagnostic state cached in this cycle is consistent with the candidate diagnostic state cached in the previous control cycle, the consistency counter is incremented until the count value of the consistency counter reaches the preset consecutive confirmation number threshold. The candidate diagnostic state is then determined as the final confirmation state and output to the outside. If the candidate diagnostic state cached in this cycle is inconsistent with the candidate diagnostic state cached in the previous control cycle, the consistency counter is reset to filter out state jumps caused by edge jitter and window boundary fluctuations.
7. The method according to claim 1, characterized in that, The method further includes: Obtain the output comparison event interrupt signal output when the local PWM instruction triggers a toggle in the output comparison unit, and lock the trigger time of the output comparison event interrupt signal as the absolute segmentation time beacon of the current complete cycle; Based on the target duty cycle parameter of the currently output local PWM command, the left region of the absolute segmented time beacon on the time axis is divided into a first phase segment, and the right region of the absolute segmented time beacon on the time axis is divided into a second phase segment. Read the preset interface output polarity configuration parameters of the single-line interface node, and convert the logic levels of the first phase segment and the second phase segment into the corresponding expected theoretical line level values according to the interface output polarity configuration parameters. When capturing the input edge event, if the arrival time of the input edge event is within a preset range of the time boundaries of the first phase segment and the second phase segment, and the changed line level is consistent with the expected value of the theoretical line level, the input edge event is pre-judged as the local edge and marked for rejection.
8. A computer system comprising a memory, a processor, and a computer program stored in the memory, characterized in that, The processor executes the computer program to implement the steps of the method according to any one of claims 1-7.
9. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-7.
10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1-7.
