Gearbox fault processing strategy generation method and system, vehicle-mounted terminal and vehicle

Abstract

The invention relates to the field of vehicle fault processing, and particularly provides a gearbox fault processing strategy generation method and system, a vehicle-mounted terminal and a vehicle, and the method comprises the steps: responding to the activation flag bit signal setting of at least one fault, and based on a preset mapping relation between the fault and a fault processing strategy identifier, determining the fault processing strategy identifier; determining and outputting a corresponding application layer fault processing strategy activation signal; acquiring an underlying fault processing strategy activation signal triggered by the diagnosis system of the underlying software based on the fault code; and on the basis of a first configurable calibration variable, selecting the bottom layer fault processing strategy activation signal or a result obtained by performing logic or operation on the application layer and the bottom layer fault processing strategy activation signal as a final fault processing strategy signal. According to the method, silent fault-tolerant processing of accidental faults, decoupling optimization of software architecture and differentiated flexible response to different levels of faults are realized.

Description

Technical Field

[0001] This invention relates to the field of vehicle fault handling, specifically to a method, system, vehicle terminal, and vehicle for generating a transmission fault handling strategy. Background Technology

[0002] The current fault handling strategy in transmission software is triggered only when a fault code is detected. This means that after determining the fault condition and confirming its existence after a period of time, a fault code is reported, triggering a series of post-fault processing actions, such as illuminating warning lights, triggering the fault handling strategy, and saving freeze frame data. This post-fault processing relies on a reported fault code. However, for some faults that do not affect transmission function or vehicle driving safety, such as occasional fluctuations in the speed sensor signal due to external environmental interference, the existing software logic will report a fault code if the fault conditions are met. However, the cause is difficult to find in the aftermarket, increasing unnecessary repair costs.

[0003] The transmission control software is architecturally divided into low-level software and application-level software. In fault diagnosis, the low-level software is responsible for implementing the diagnostic function architecture, while the application-level software is responsible for implementing the diagnostic logic and the specific implementation of fault handling strategies. The low-level software has a diagnostic management system. When the application-level software logic identifies a fault, it transmits the fault status flag signal to the low-level software. The low-level software then triggers a series of actions by the diagnostic management system, such as recording fault codes, recording freeze frame data, and triggering fault handling strategies. The implementation of the fault handling strategy is determined by the association set by the low-level software. For example, for fault code DFC1, the application-level software logic sets its fault establishment flag to flg_ErrDebASWDFC1. The low-level software sets a calibration variable DINH_*DFC1 for fault code DFC1, which can be calibrated as FID_Cus_TIRS_001 (in the application-level software, this is associated with triggering the limp-home strategy, and is a Unit32 type data; for FID_Cus_TIRS_001, its value is defined as bit0=1). When flg_ErrDebASWDFC1 is set to 1, the application layer passes flg_ErrDebASWDFC1 to the underlying software through an interface function. Upon receiving the signal, the underlying software triggers a series of actions by the diagnostic management system. The underlying software's diagnostic management system, while triggering the recording of fault code DFC1, simultaneously passes the activated status value of the fault handling strategy FID_Cus_TIRS_001 to the application layer software variable fhd_b_FaultReactionsBSW, i.e., the fault handling strategy signal. The application layer software implements the corresponding fault handling strategy based on the obtained value of the fault handling strategy signal fhd_b_FaultReactionsBSW. A drawback of the current technical solution is that the fault handling strategy cannot be triggered through the underlying software's fault diagnostic management system when no fault code is reported. In other words, the prerequisite for triggering the fault handling strategy through the underlying software's fault diagnostic management system is that a fault code must be reported.

[0004] The proposed solutions trigger fault handling strategies through a single fault signal, meaning that each fault signal is associated with a fault handling measure. This increases the amount of software code significantly, obscures the software architecture hierarchy, and results in extremely poor software flexibility, extremely high maintenance costs, and an inability to cope with complex or unknown fault scenarios. Summary of the Invention

[0005] To address the aforementioned issues, this invention provides a method, system, vehicle terminal, and vehicle for generating transmission fault handling strategies, enabling silent fault-tolerant handling of intermittent faults, decoupling optimization of the software architecture, and differentiated and flexible responses to faults of different levels.

[0006] In a first aspect, the technical solution of the present invention provides a method for generating a transmission fault handling strategy, which is executed by application layer software and includes the following steps: In response to the activation flag signal of at least one fault being set, the corresponding application layer fault handling strategy activation signal is determined and output based on the predetermined mapping relationship between faults and fault handling strategy identifiers. Obtain the activation signal of the underlying fault handling strategy triggered by the diagnostic system of the underlying software based on the fault code; Based on the first configurable calibration variable, the activation signal of the underlying fault handling strategy is selected, or the result of a logical OR operation between the activation signal of the application layer and the activation signal of the underlying fault handling strategy is selected as the final fault handling strategy signal.

[0007] Secondly, the technical solution of the present invention provides a transmission fault handling strategy generation system, which is configured in application layer software and includes: The application layer fault handling strategy activation signal generation module is used to determine and output the corresponding application layer fault handling strategy activation signal in response to the setting of the activation flag signal of at least one fault, based on the predetermined mapping relationship between faults and fault handling strategy identifiers. The underlying fault handling strategy activation signal acquisition module is used to acquire the underlying fault handling strategy activation signal triggered by the diagnostic system of the underlying software based on the fault code. The final fault handling strategy signal determination module is used to select, based on a first configurable calibration variable, the activation signal of the underlying fault handling strategy, or the result of a logical OR operation between the activation signal of the application layer and the activation signal of the underlying fault handling strategy, as the final fault handling strategy signal.

[0008] Thirdly, the technical solution of the present invention provides a vehicle-mounted terminal, comprising: Memory, used to store the gearbox fault handling strategy generation program; A processor is configured to implement the steps of the transmission fault handling strategy generation method as described above when executing the transmission fault handling strategy generation program.

[0009] Fourthly, the technical solution of the present invention provides a vehicle equipped with the above-mentioned vehicle-mounted terminal.

[0010] As can be seen from the above technical solutions, this application has the following advantages: (1) By establishing an independent triggering channel based on the fault activation flag signal in the application layer software, the system can start the corresponding fault handling strategy in the early stage when the fault is logically confirmed, or even when it is decided not to report the fault code. In addition, the OR operation with the underlying generation processing strategy can be used to complete the necessary fault tolerance processing without generating and recording fault codes for occasional faults that do not affect core safety or driving functions. This ensures vehicle operation safety and system stability, and avoids after-sales misjudgment and maintenance costs caused by unnecessary fault codes, thus achieving the optimal balance between safety and economy. (2) To avoid code clutter caused by bypassing fault code binding, a standardized fault handling strategy identifier is used as an intermediate abstraction layer. Each FID represents a standard handling measure. Through a preset mapping relationship, multiple faults can point to the same FID (strategy reuse), and a single fault can also be associated with multiple FIDs (combined strategy). This decouples the fault diagnosis logic from the specific fault handling execution logic. The application layer only needs to manage the mapping, activation, and transmission of FIDs, while the specific execution module responds to the standardized FID instructions. This changes the original architecture that directly drives the actuator through a large number of independent signal lines, thereby reducing the amount of code, making the architecture layer clear, and enhancing maintainability and readability. (3) Through the first configurable calibration variable, the fault handling path can be flexibly selected. It can use only the traditional fault code-based underlying channel or enable the application layer independent channel to make the two channels work in parallel, providing differentiated handling modes for faults of different severity levels and different scenarios. Attached Figure Description

[0011] To more clearly illustrate the technical solution of this application, the accompanying drawings used in the description will be briefly introduced below. Obviously, the accompanying drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0012] Figure 1 This is a schematic flowchart of a method for generating a transmission fault handling strategy according to an embodiment of the present invention.

[0013] Figure 2 This is a schematic block diagram of a transmission fault handling strategy generation system provided in an embodiment of the present invention.

[0014] Figure 3 This is a schematic diagram of the structure of a vehicle-mounted terminal provided in an embodiment of the present invention. Detailed Implementation

[0015] To make the purpose, features, and advantages of this application more apparent and understandable, specific embodiments and accompanying drawings will be used to clearly and completely describe the technical solution protected by this application. Obviously, the embodiments described below are only some embodiments of this application, and not all embodiments. Based on the embodiments in this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0016] Unless otherwise defined, all technical and scientific terms used in this application have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. The terminology used in this application and in the specification of this invention is for the purpose of describing particular embodiments only and is not intended to be limiting of the invention.

[0017] The key terms used in this invention will be explained below.

[0018] FID: Function Identifier, refers to the identifier that locks the normal function and enables the backup function when a fault occurs, i.e., the fault handling strategy identifier.

[0019] Figure 1 This is a schematic flowchart illustrating a method for generating a transmission fault handling strategy according to an embodiment of the present invention. Figure 1 The executing entity can be a transmission fault handling strategy generation system. The transmission fault handling strategy generation method provided in this embodiment of the invention is executed by a computer device; correspondingly, the transmission fault handling strategy generation system runs on the computer device. Depending on different requirements, the order of the steps in this flowchart can be changed, and some steps can be omitted.

[0020] like Figure 1 As shown, the method includes the following steps.

[0021] S1, in response to the activation flag signal of at least one fault being set, determines and outputs the corresponding application layer fault handling strategy activation signal based on the predetermined mapping relationship between faults and fault handling strategy identifiers.

[0022] The trigger for this step is "the activation flag signal of the fault is set", not "the fault code is recorded". This means that the software may have already captured the fault event in the early stages of the fault diagnosis logic confirmation, before the delay or conditions for reporting the fault code have been met.

[0023] At this point, the system no longer needs to wait for or rely on the underlying diagnostic management system to complete the "recording fault codes" action, and can immediately enter the policy processing flow. Thus, the actions of "fault handling" and "fault code reporting" are decoupled in terms of both time and logic.

[0024] Meanwhile, an intermediate abstraction layer called "Fault Handling Strategy Identifier" was constructed. FID is a standardized "instruction set". Multiple different faults can be mapped to the same FID. For example, "signal unreliable" is mapped to the "use alternative signal" strategy. A fault can also be mapped to multiple FIDs (combined strategies), thereby realizing the reuse and unified management of strategies. This makes the application layer software architecture clear and the logic centralized, avoids code bloat, and reduces maintenance difficulty.

[0025] S2, obtain the activation signal of the underlying fault handling strategy triggered by the diagnostic system of the underlying software based on the fault code.

[0026] This embodiment retains a reliable processing path based on fault codes. For serious faults that truly require recording and alerting, the traditional strategy is still employed. Therefore, this embodiment constructs a dual-channel fault handling system by simultaneously acquiring two sets of signals: one is a fast response channel at the application layer, and the other is a formal recording channel at the lower level, ensuring the solution's safety, redundancy, and backward compatibility.

[0027] S3, based on the first configurable calibration variable, select either the activation signal of the underlying fault handling strategy or the result of a logical OR operation between the application layer and the activation signal of the underlying fault handling strategy as the final fault handling strategy signal.

[0028] This embodiment uses a configurable calibration variable as a decision switch, and the system can be configured accordingly to: Use only the underlying channel: Select the underlying fault handling strategy activation signal as the final signal; corresponding to the traditional mode, it is suitable for scenarios where all faults need to be reported; Dual-channel fusion: The two activation signals from the application layer and the underlying layer are logically ORed, and the result is used as the final signal.

[0029] In the "fusion dual-channel" mode, the final fault handling strategy signal is the result of an OR operation between the application layer signal and the underlying signal. This means that as long as either the application layer signal or the underlying signal indicates that a fault handling strategy needs to be activated, that strategy will be executed. For faults configured to "not report fault codes but require handling," the activation flag bit of the fault will be set, triggering the application layer to generate the corresponding fault handling strategy signal (corresponding bit=1). Since no fault code is reported, the underlying diagnostic system will not generate the corresponding underlying fault handling strategy signal (corresponding bit=0). Furthermore, in the "fusion dual-channel" mode, after performing an OR operation on these two signals, the bit in the final signal corresponding to the strategy will be 1. Therefore, even if the underlying signal is 0 (no fault code), as long as the application layer signal is 1, the corresponding fault handling strategy will still be activated and executed, thus achieving the function of not reporting fault codes but performing fault handling.

[0030] As a refinement and extension of the specific implementation of the above embodiments, in order to fully explain the specific implementation process of this embodiment, the following will provide possible embodiments to describe the specific implementation of the above steps in a non-limiting manner.

[0031] In some optional implementations, regarding step S1, when generating the application layer fault handling strategy activation signal, for each fault, the application layer software sets its fault handling strategy calibration variable fhc_b_FIDASWDFC_X* (where * takes values ​​of 1, 2, 3, ... representing the first fault, the second fault, ...). This calibration variable is of data type Unit32, and each bit represents a fault handling strategy. A fault can be calibrated with one or more fault handling strategies, and Unit32 data means that a fault can match up to 32 handling strategies. When one or more fault activation flag signals flg_ErrDebASWDFC* are set to 1, it indicates that one or more faults have occurred. The fault handling strategy signal fhc_b_FIDASWDFC_X* corresponding to the fault will be output, and after performing a bitwise OR operation, the total number of fault handling strategy signals fhd_b_FIDASWDFC (Unit32, each bit representing a fault handling strategy) activated in the current software will be obtained. When the fault activation flag signal flg_ErrDebASWDFC* is 0, fhd_b_FIDASWDFC outputs 0, indicating that the fault handling strategy has not been triggered. Furthermore, the application layer software sets a fault handling strategy identifier FID_* for each fault handling strategy, such as FID_Cus_TIRS_004 (representing the strategy of cutting off the main oil circuit pressure control, defined as bit3=1), FID_Cus_TITS_005 (using engine coolant temperature instead of transmission oil temperature, defined as bit4=1), etc. Each FID represents a fault handling strategy. Each FID is a Unit32 type value (each FID corresponds to one bit). The software performs a bitwise AND operation between fhd_b_FIDASWDFC and the fault handling strategy identifier FID_* to obtain the current application layer fault handling strategy activation signal fhd_b_FaultReactionsASW.

[0032] Specifically, step S1 includes the following steps S1.1 to S1.5.

[0033] S1.1, Set a fault handling strategy requirement identifier for each fault. This identifier contains N bits, and each bit represents a fault handling strategy.

[0034] For each diagnosable fault defined in the transmission control system, a dedicated fault handling strategy requirement identifier is configured in the application layer software. This requirement identifier is stored in bitmask form; in a preferred embodiment, its data type is a 32-bit unsigned integer (Unit32), totaling N=32 bits. Each independent bit predefines a standardized fault handling strategy; for example, bit 0 corresponds to "entering limp-home mode," bit 1 corresponds to "using engine speed instead of input shaft speed," etc. For any specific fault, if a certain handling strategy needs to be triggered when it occurs, the bit corresponding to that strategy is marked as a logic "1" in the corresponding requirement identifier; otherwise, it is marked as "0." Thus, this marking variable constitutes a static mapping relationship between the fault and one or more possible triggered fault handling strategies, denoted as the first mapping relationship. This mapping relationship is configured during the software calibration phase, possessing configurability and flexibility.

[0035] S1.2, Construct a mapping relationship between the fault activation flag signal and the corresponding fault handling strategy requirement identifier, denoted as the first mapping relationship.

[0036] The diagnostic logic module in the application layer software runs continuously, monitoring the fulfillment of various preset fault conditions in real time. When a fault condition is determined to be met, for example, when a sensor signal continuously exceeds the limit for a preset confirmation time, the corresponding fault activation flag signal flg_ErrDebASWDFC1 flips from logic "0" to logic "1". Setting this flag indicates that the fault has been confirmed as active by the application layer logic at the current moment.

[0037] S1.3, respond to the fault activation flag signal set, and locate the corresponding fault handling strategy requirement identifier based on the first mapping relationship.

[0038] When one or more fault activation flags are detected to be set, the software logic responds immediately. Based on the first mapping relationship established in step S201, the system quickly locates the fault handling strategy requirement identifier corresponding to each set fault.

[0039] S1.4 Perform a bitwise OR operation on the fault handling strategy requirement identifiers located by all currently set fault activation flag signals to obtain the comprehensive fault handling strategy signal.

[0040] All fault handling strategy requirement identifiers located by the currently set fault activation flags are read out. Then, a bitwise OR operation is performed on all the read bitmask values. The logic of this operation is: if a fault is associated with a certain handling strategy, then regardless of whether other faults are also associated with that strategy, the bit representing that strategy in the final result will be set to "1" after the OR operation. The result of the bitwise OR operation generates a unified bitmask signal summarizing the handling strategies required by all currently active faults, namely the comprehensive fault handling strategy signal fhd_b_FIDASWDFC.

[0041] S1.5 performs a bitwise AND operation between the comprehensive fault handling strategy signal and the standardized fault handling instruction identifiers of various predefined fault handling strategies to obtain the fault handling strategy activation signal, and outputs the signal as the application layer fault handling strategy activation signal.

[0042] A complete library of standardized fault handling instruction identifiers is predefined. Each identifier FID_* represents a specific fault handling action that has been defined and implemented in the engineering process. Each FID_* is defined in the software as a constant of type Unit32, and its value is constructed such that only the specific bit representing its corresponding action is 1, and the remaining bits are 0. For example, FID_Cus_TIRS_004 may be defined as the constant 0x00000008 (only bit 3=1).

[0043] The fhd_b_FIDASWDFC obtained in the previous step is then subjected to a bitwise logical AND operation with each predefined FID_*. This is used to determine whether a bit in fhd_b_FIDASWDFC that is "1" corresponds to a real and valid standardized processing instruction. For a given FID_*, if the result of fhd_b_FIDASWDFC&FID_* is not equal to 0, it indicates that the synthesis requirement signal contains a request for this standardized instruction, and that the instruction is real and valid. At this point, the standard processing strategy represented by this FID_* is officially confirmed and activated.

[0044] Collect all FID_* that have been confirmed to be activated in step S242, and generate a unified structured bitmask signal through logical operations. This signal is the application layer fault handling strategy activation signal fhd_b_FaultReactionsASW. Each bit that is "1" in fhd_b_FaultReactionsASW uniquely corresponds to an executable standardized fault handling instruction identifier.

[0045] The application layer fault handling strategy activation signal drives the transmission control unit to execute the corresponding physical control action. The physical control action corresponds one-to-one with the handling strategy represented by the standardized fault handling instruction identifier, including at least one of the following: entering limp home mode, enabling alternative signals, cutting off specific solenoid valve control, and limiting output torque.

[0046] For example, the fault identifier is set to DFC_InputSpeedSens_Fault, and its corresponding fault activation flag signal is flg_ErrDebASWDFC_10. A 32-bit fault handling strategy requirement identifier is configured for this fault, denoted as fhc_b_FIDASWDFC_X10. Assume that the system predefines 32 standardized handling strategies, where: bit 0 (value 0x00000001) corresponds to strategy FID_Cus_TIRS_001, which activates limp-home mode; bit 1 (value 0x00000002) corresponds to strategy FID_Cus_TITS_002, which uses engine speed instead of input shaft speed. For this "input shaft speed sensor fault," the engineer's evaluation concludes that: 1) engine speed should be used instead (strategy bit 1); 2) limp-home does not need to be activated immediately (bit 0 is not enabled). Therefore, fhc_b_FIDASWDFC_X10 is calibrated as 0x00000002, which is binary...0010.

[0047] During vehicle operation, the input shaft speed signal is lost for more than the preset diagnostic time due to momentary interference in the wiring harness. The application layer diagnostic logic confirms that the fault condition is met and sets the fault activation flag signal flg_ErrDebASWDFC_10 from 0 to 1. According to the preset first mapping relationship, the system immediately locates the demand identifier fhc_b_FIDASWDFC_X10 corresponding to the fault, with a value of 0x00000002. At this time, assuming that only this one fault is activated in the system, the system reads the demand identifier located by all currently set faults, i.e., fhc_b_FIDASWDFC_X10. Since there is only one identifier, the result of the bitwise OR operation is itself. Therefore, the comprehensive fault handling strategy signal fhd_b_FIDASWDFC=0x00000002 is generated. The predefined standardized instruction identifiers FID_* include FID_Cus_TIRS_001 (limp home) which is defined as the constant 0x00000001 (bit 0 only = 1), and FID_Cus_TITS_002 (engine speed substitution) which is defined as the constant 0x00000002 (bit 1 only = 1). `fhd_b_FIDASWDFC(0x00000002)&FID_Cus_TIRS_001(0x00000001)=0x00000000`, indicating that the limp home strategy is not activated. `fhd_b_FIDASWDFC(0x00000002)&FID_Cus_TITS_002(0x00000002)=0x00000002` (not equal to 0), indicating that the "engine speed substitution" strategy is confirmed to be activated. The value of FID_Cus_TITS_002 (0x00000002) that confirms activation will be output, forming the application layer fault handling strategy activation signal fhd_b_FaultReactionsASW=0x00000002.

[0048] In some optional implementations, a dynamic strategy adjustment step is also set for the standardized fault handling instruction identifier, so that the triggering of the fault handling strategy is not only based on the fault itself, but also dynamically optimized and adjusted in combination with the current vehicle operating status, realizing environmental perception and adaptive decision-making. This enables the system to select the optimal or adjust the strategy parameters according to the real-time operating conditions, thereby improving the intelligence level of fault-tolerant control and the overall resilience of the system. Specifically, this includes the following steps a) to c).

[0049] Step a) Set several partitions for the target real-time operating parameters of the vehicle, and predefine one or more strategy adjustment tables for each partition; the index of the strategy adjustment table is a combination of fault identifier and standardized fault handling instruction identifier, and the table entry content is the adjusted control parameter value or strategy enable flag adapted to the operating state partition.

[0050] Step b) Within the current software scheduling cycle, obtain the target's real-time running status parameters and determine its current running status partition. Based on the current running status partition, look up at the predefined policy adjustment table to obtain at least one of the following information: the adjustment value of the fault handling policy requirement identifier corresponding to the currently active fault, and the adjustment control parameter value of the standardized fault handling instruction identifier corresponding to the currently activated or pending activation.

[0051] Step c) The obtained adjustment information is logically ANDed / ORed with the intermediate result of the fault handling strategy requirement identifier generated according to the original logic in the current cycle, or the application layer fault handling strategy activation signal, and the parameters are fused. The fused result is used as the final fault handling strategy signal or control parameter output to drive the actuator.

[0052] Example 1: Differentiated handling of shift solenoid valve faults based on vehicle speed zones.

[0053] Assume a "shift solenoid valve A drive circuit open circuit" fault occurs. In static mapping, this fault is always associated with FID_Cus_TIRS_020, defined as "locking the current gear and prohibiting shifting into a specific gear". Set vehicle speed (V) zones: low speed zone (V<30km / h), medium-high speed zone (V>=30km / h).

[0054] Low-speed zone strategy adjustment table: For the combination (Fault X, FID_Cus_TIRS_020), the table entry is: {Latch flag: Yes, Target gear: 2nd gear}. This means that at low speeds, the vehicle will be gently locked in 2nd gear to ensure basic mobility.

[0055] Medium-to-high speed zone strategy adjustment table: For the same combination, the table entry is: {Latch flag: Yes, Target gear: Highest gear, Additional activation: FID_Cus_TIRS_001 (Limp home)}. This means that at high speeds, to avoid the risk of power interruption, the vehicle directly enters the highest gear and simultaneously activates the limp home strategy to smoothly reduce the speed to a safe range.

[0056] When a fault occurs, the system monitors the vehicle speed in real time. If the vehicle is in a low-speed zone, low-speed zone adjustment parameters are applied; if it is in a medium-to-high-speed zone, high-speed zone adjustment parameters and additional strategies are applied. This is achieved by modifying the mapping logic or by directly ORing an additional FID into the final execution signal.

[0057] Example 2: Parameter optimization of sensor signal replacement strategy based on oil temperature.

[0058] Assuming a "output shaft speed sensor signal failure" fault occurs, the static mapping associated with FID_Cus_TITS_010 is defined as "using the output shaft speed estimated by the calculation model as a substitute". The transmission oil temperature (T) zones are set as follows: low temperature zone (T<50°C), normal zone (50°C<=T<120°C), and high temperature zone (T>=120°C).

[0059] Pre-set model parameter calibration tables for different oil temperature zones for FID_Cus_TITS_010. For example: Low temperature region: Due to the viscosity of the oil, the transmission efficiency model parameter K needs to be multiplied by a correction factor of 0.9; Normal region: Use nominal model parameters; High-temperature zone: Considering thermal decay, the model parameter K needs to be multiplied by a correction factor of 1.1, and the filtering intensity of the estimated value should be increased.

[0060] When the FID is activated, the system loads model parameters from the corresponding calibration table based on the current oil temperature zone. These parameters are provided to the speed estimation module in real time, ensuring that the substitution signal maintains high accuracy under different temperatures, thereby optimizing the shift smoothness in limp-home mode.

[0061] Example 3: Enabling / Disabling Dynamic Fault Strategy Based on Torque Request.

[0062] Some fault handling strategies can severely impact driving performance or safety when the vehicle is under high load. For example, "limiting engine torque request" can affect performance or safety during high-load conditions such as climbing hills or rapid acceleration.

[0063] Real-time monitoring of engine torque request or throttle opening. Setting a "high load flag". When the "high load flag" is true, the system temporarily modifies the bitmask of the fault handling strategy requirement identifier (fhc_b_FIDASWDFC_XF) for fault F, clearing the bit representing the "torque limiting" strategy (assuming it corresponds to bit 5). This is achieved through the following bitwise operations: Dynamic demand identifier = Original demand identifier & (~(High load flag * (1<<5))) The high load flag is a Boolean value (1 or 0). Therefore, under high load conditions, even if fault F is activated, torque limiting will not be triggered. Instead, other redundancy strategies (such as downshifting) will be used to ensure basic functions. Once the load decreases, the torque limiting strategy will be restored to protect the hardware.

[0064] In this embodiment, the activation signal of the underlying fault handling strategy triggered by the diagnostic system of the underlying software based on the fault code is simultaneously acquired, ensuring compatibility between the application layer and the underlying fault handling path and constructing system safety redundancy. In the transmission controller software architecture, the underlying software (BSW) has an independent diagnostic event manager and diagnostic communication module. When the diagnostic logic of the application layer software confirms that a certain fault continuously meets the preset confirmation conditions, it will report a diagnostic fault code, such as DFC_InputSpeedSens_Err, to the underlying diagnostic management system through an interface function. While recording the fault code and storing the freeze frame data, the underlying diagnostic system will trigger the corresponding fault handling strategy identifier according to the preset association relationship in the underlying data.

[0065] For example, in the underlying calibration data, the fault code DFC_InputSpeedSens_Err is associated with the fault handling strategy variable DINH_*DFC1, and this variable is calibrated as FID_Cus_TIRS_001.

[0066] The underlying software transmits the activated FID set to the application layer software via the software bus or global variable interface in the form of a unified 32-bit unsigned integer bitmask signal. This signal is the underlying fault handling strategy activation signal, denoted as fhd_b_FaultReactionsBSW. In this signal, any bit being "1" indicates that the underlying diagnostic system formally requests the execution of the corresponding standardized fault handling strategy.

[0067] In this embodiment, a final fault handling strategy signal is selected and generated based on a first configurable calibration variable. The first configurable calibration variable is a one-bit flag variable. When it is calibrated to a first value, the final fault handling strategy signal is the underlying fault handling strategy activation signal. When it is calibrated to a second value, the final fault handling strategy signal is the result of a logical OR operation between the application layer fault handling strategy activation signal and the underlying fault handling strategy activation signal.

[0068] Specifically, in the application layer software, a one-bit flag variable is set as the first configurable calibration variable, for example, named fhc_flg_FIDASWDFCEnable. A value of "0" defines the traditional mode, in which the system completely relies on the underlying diagnostic and processing channels, equivalent to the behavior of existing technical solutions. A calibration value of "1" defines the fusion mode, in which the system enables a fast channel triggered independently by the application layer and merges its output with the output of the underlying channel.

[0069] Within a software scheduling cycle, the system reads the value of fhc_flg_FIDASWDFCEnable and executes the following conditional logic: When fhc_flg_FIDASWDFCEnable=0, only the underlying fault handling strategy activation signal is selected as the final output. That is, the final fault handling strategy signal fhd_b_FaultReactions=fhd_b_FaultReactionsBSW. This mode is suitable for scenarios with conservative fault handling or where all faults must be reported and logged, ensuring full backward compatibility with traditional systems. When fhc_flg_FIDASWDFCEnable=1, the application layer fault handling strategy activation signal and the underlying fault handling strategy activation signal are performed using a bitwise logical OR operation, and the result is used as the final output. That is: fhd_b_FaultReactions=fhd_b_FaultReactionsASW OR fhd_b_FaultReactionsBSW The sum of the union of the OR operation implementation strategies means that as long as either the application layer signal fhd_b_FaultReactionsASW or the underlying signal fhd_b_FaultReactionsBSW indicates that a certain fault handling strategy needs to be activated (corresponding bit is 1), then that strategy will be activated in the final signal (corresponding bit is 1).

[0070] For faults configured as "requiring handling but not reporting fault codes," the fault activation flag flg_ErrDebASWDFC* is set to 1, triggering the application layer to generate the corresponding fhd_b_FaultReactionsASW signal. Since the reporting conditions are not met or the fault is actively masked, the underlying diagnostic system will not record the fault code, and therefore will not generate the corresponding fhd_b_FaultReactionsBSW signal. In fusion mode, fhd_b_FaultReactionsASW(bit1=1) OR fhd_b_FaultReactionsBSW(bit1=0) is executed. The final result in fhd_b_FaultReactions will be 1 for the corresponding bit1. Even if the underlying signal is 0 (representing no formal fault code record), as long as the application layer signal is 1 (representing early diagnostic confirmation of needing handling), the corresponding fault handling strategy will still be activated and executed, thus achieving silent fault-tolerant handling without fault code reporting.

[0071] In some optional implementations, the software is developed to its maximum functionality for platform-based management before generating the final fault handling strategy signal, but this functionality is not applicable to all vehicle models. Some FID settings are related to the current transmission controller hardware configuration and software functionality. To match different vehicle configurations, the application-layer fault handling strategy signal is further processed according to the vehicle configuration, including: setting a second configurable calibration variable, which is a bitmask containing N bits; wherein the i-th bit of the second configurable calibration variable is used to enable or disable the i-th standardized fault handling instruction identifier; performing a bitwise AND operation between the application-layer fault handling strategy activation signal and the second configurable calibration variable to obtain the application-layer fault handling strategy signal allowed by the project configuration in the current cycle.

[0072] Specifically, the application layer software includes a Unit32 type calibration variable, fhc_b_FIDASWEnable. This Unit32 variable enables the corresponding FID only when the corresponding bit is set to 1. For example, bit 0 = 1 enables FID_Cus_TIRS_001, and bit 0 = 0 disables it. For instance, some transmission controllers lack internal acceleration sensors, so FID_Cus_TIRS_030 (disabling vehicle weight calculation and hill start / downhill mode switching) needs to be disabled. Similarly, for some vehicle models with transmissions lacking position sensors, FID_Cus_TIRS_028 (blind control) needs to be disabled.

[0073] For example, FID_Cus_TIRS_001 is predefined as the constant 0x00000001 (bit0 only = 1), representing "activating limp home mode". This is a basic safety policy required for all models. Therefore, in fhc_b_FIDASWEnable, bit0 is always calibrated to 1. FID_Cus_TITS_030 is predefined as the constant 0x20000000 (assuming only bit29 = 1), representing "disabling vehicle weight calculation and disabling hill start / downhill mode switching". This policy relies on signals provided by the accelerometer. For high-end models equipped with accelerometers, this policy is effective, and bit29 in fhc_b_FIDASWEnable is calibrated to 1. For low-end models without accelerometers, the hardware required for this policy does not exist, and triggering it will cause functional malfunctions. Therefore, in fhc_b_FIDASWEnable, bit29 must be calibrated to 0 to disable this policy. FID_Cus_TIRS_028 is predefined as the constant 0x08000000 (assuming only bit 27 = 1), representing a "blind control" strategy (using an estimated value when the position sensor fails). This strategy is meaningless if a vehicle model's transmission does not have a physical position sensor installed. Similarly, bit 27 needs to be set to 0 in fhc_b_FIDASWEnable.

[0074] Within each software scheduling cycle, after the application layer software generates the initial application layer fault handling strategy activation signal fhd_b_FaultReactionsASW, the system immediately performs an enable filtering operation: fhd_b_FaultReactionsASW is subjected to a bitwise logical AND operation with the second configurable calibration variable fhc_b_FIDASWEnable. The operation logic is as follows: The application-layer fault handling policy signal allowed by the project configuration within the current cycle is: fhd_b_FaultReactionsASW&fhc_b_FIDASWEnable Suppose that due to a fault in the current cycle, the application layer requests activation of FID_Cus_TITS_030 (bit 29=1), and bit 29 in the generated fhd_b_FaultReactionsASW is also set to 1. For a high-spec model (bit 29=1 in fhc_b_FIDASWEnable): bit 29=1)&(bit 29=1)=1, and bit 29 in the filtered signal remains 1, so the policy is allowed and transmission continues. For a low-spec model (bit 29=0 in fhc_b_FIDASWEnable): (bit 29=1)&(bit 29=0)=0, and bit 29 in the filtered signal is forcibly cleared to zero. Even if logically necessary, this policy is effectively masked, preventing erroneous instructions from being issued to non-existent hardware.

[0075] In actual transmission operation, some faults may exhibit transient or intermittent characteristics. For example, poor wiring harness contact caused by road bumps may cause the "shift solenoid valve open circuit" fault to repeatedly appear and disappear within a short period of time. If the corresponding protection strategy is immediately deactivated as soon as the fault disappears, and then reactivated as soon as the fault reappears, it will lead to frequent switching of control logic, hardware shocks and wear, etc., which may cause severe fluctuations in gear position, oil pressure and other controls, seriously affecting driving smoothness and safety. The high-frequency switching of actuators between "enabled" and "disabled" states may accelerate their mechanical or electrical aging. To this end, this embodiment sets up a configurable fault handling strategy latching process. For some critical or serious faults, once a handling strategy is triggered, even if the fault temporarily disappears within the current driving cycle, the strategy should be "latched" and remain in effect until the end of the current ignition cycle. This process includes: setting a third configurable calibration variable, which is a bitmask containing N bits, each bit indicating whether the corresponding standardized fault handling instruction identifier is prohibited from recovery within the current driving cycle; in each software scheduling cycle, performing the following operations to generate the final fault handling strategy execution signal: performing a bitwise AND operation between the final fault handling strategy signal and the third configurable calibration variable; if the bitwise AND result is not zero, then maintaining the fault handling strategy with the corresponding bit set to 1 in the final fault handling strategy execution signal of the previous scheduling cycle in the final fault handling strategy execution signal of the current scheduling cycle; if the bitwise AND result is zero, then updating the value of the corresponding bit in the final fault handling strategy execution signal of the current scheduling cycle based on the final fault handling strategy signal.

[0076] Specifically, a third configurable calibration variable is set in the application layer software, for example, named fhc_b_FIDRecoveryDisable. This variable is a 32-bit unsigned integer (Unit32) bitmask, with a total of N=32 bits. Its i-th bit (biti) corresponds one-to-one with the i-th standardized fault handling instruction identifier (FID_i). If a certain FID_i is calibrated to be latched within the current driving cycle (i.e., the policy does not exit after fault recovery), then the corresponding i-th bit in the fhc_b_FIDRecoveryDisable variable is calibrated to 1. If a certain FID_i is calibrated to be allowed to recover within the current driving cycle (i.e., the policy can exit after the fault disappears), then the corresponding i-th bit is calibrated to 0.

[0077] For example, FID_Cus_TIRS_012 (assuming corresponding bit11=1) means "when the shift solenoid is open, cut off the valve control and lock the current gear". Since this fault may recover transiently, but the strategy switch will cause gear misalignment, bit11 in fhc_b_FIDRecoveryDisable is usually set to 1 to require latching. FID_Cus_TITS_002 (corresponding to bit1=1) means "replace the input shaft speed with engine speed". After the transient disturbance of the input shaft speed signal recovers, switching back to the normal speed signal is almost imperceptible to the driver, so bit1 can be set to 0, allowing the strategy to exit immediately upon fault recovery.

[0078] The latching decision is executed once per software scheduling cycle, and its inputs include: Final_Strategy_Curr: The final fault handling strategy signal for the current cycle generated by step S3. It represents the set of strategies the system "hopes" to activate based on the current fault state; Final_Execute_Prev: The final fault handling policy execution signal of the previous scheduling cycle. It represents the set of policies (including latching policies) that the system "determines" to execute at the end of the previous cycle. fhc_b_FIDRecoveryDisable: The third configurable calibration variable.

[0079] The Final_Execute_Curr signal is generated through steps A and B.

[0080] Step A: Identify the policy bits that need to be latched.

[0081] Perform a bitwise AND operation between the current cycle's strategy request Final_Strategy_Curr and the latch configuration variable fhc_b_FIDRecoveryDisable: Lock_Candidate_Mask=Final_Strategy_Curr&fhc_b_FIDRecoveryDisable The result of the operation, Lock_Candidate_Mask, is a bitmask where the bits that are "1" represent the policy currently requested and configured to require locking. These are the policy bits that may need to inherit state from history.

[0082] Step B: Generate the final execution signal.

[0083] For policy bits that need to be latched, i.e. bits that are 1 in Lock_Candidate_Mask, they should remain active in this cycle as long as they have been activated to 1 in the Final_Execute_Prev execution signal of the previous cycle, regardless of whether they are requested in the current cycle.

[0084] Specifically, the values ​​of those bits in Final_Execute_Prev that correspond to Lock_Candidate_Mask being 1 are directly assigned to the corresponding bits in Final_Execute_Curr. This can be achieved by combining a bitwise AND operation and a bitwise OR operation, or by using a conditional loop.

[0085] For strategy bits that are not latched or not currently requested (i.e., bits in Lock_Candidate_Mask that are 0), their state is entirely determined by the request in the current cycle. Specifically, the value of the corresponding bit in Final_Strategy_Curr is assigned to the corresponding bit in Final_Execute_Curr.

[0086] In other words, Final_Execute_Curr=(Final_Execute_Prev&Lock_Candidate_Mask)|(Final_Strategy_Curr&(~Lock_Candidate_Mask)) The final execution signal = (the bits that were executed in the previous cycle and need to be latched) or (the bits that were requested in the current cycle and do not need to be latched).

[0087] The foregoing has described in detail an embodiment of a method for generating a transmission fault handling strategy. Based on the transmission fault handling strategy generation method described in the above embodiment, this invention also provides a transmission fault handling strategy generation system corresponding to the method.

[0088] Figure 2 This is a schematic block diagram of a transmission fault handling strategy generation system provided in an embodiment of the present invention. In this embodiment, the transmission fault handling strategy generation system 200 can be divided into multiple functional modules according to the functions it performs. A module, as referred to in this invention, is a series of computer program segments that can be executed by at least one processor and perform a fixed function, and is stored in memory.

[0089] The application layer fault handling strategy activation signal generation module 210 is used to determine and output the corresponding application layer fault handling strategy activation signal in response to the setting of the activation flag signal of at least one fault, based on a predetermined mapping relationship between faults and fault handling strategy identifiers.

[0090] The underlying fault handling strategy activation signal acquisition module 220 is used to acquire the underlying fault handling strategy activation signal triggered by the diagnostic system of the underlying software based on the fault code.

[0091] The final fault handling strategy signal determination module 230 is used to select, based on a first configurable calibration variable, the activation signal of the underlying fault handling strategy, or the result of a logical OR operation between the activation signal of the application layer and the activation signal of the underlying fault handling strategy, as the final fault handling strategy signal.

[0092] The transmission fault handling strategy generation system of this embodiment is used to implement the aforementioned transmission fault handling strategy generation method. Therefore, the specific implementation of this system can be found in the embodiment section of the transmission fault handling strategy generation method above. Thus, the specific implementation can be referred to the description of the corresponding embodiments, and will not be elaborated here.

[0093] Furthermore, since the gearbox fault handling strategy generation system in this embodiment is used to implement the aforementioned gearbox fault handling strategy generation method, its function corresponds to the function of the above method, and will not be repeated here.

[0094] Figure 3 A schematic diagram of a vehicle-mounted terminal 300 provided in an embodiment of the present invention includes: a processor 310, a memory 320, and a communication unit 330. The processor 310 is used to implement the process steps of the above-described embodiment of the transmission fault handling strategy generation method when implementing the transmission fault handling strategy generation program stored in the memory 320.

[0095] The present invention also provides a vehicle equipped with the above-described vehicle terminal 300.

[0096] The above description of the disclosed embodiments enables those skilled in the art to make or use the invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the invention. Therefore, the invention is not to be limited to the embodiments shown herein, but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A method for generating a transmission fault handling strategy, characterized in that, This method is executed by application layer software and includes the following steps: In response to the activation flag signal of at least one fault being set, the corresponding application layer fault handling strategy activation signal is determined and output based on the predetermined mapping relationship between faults and fault handling strategy identifiers. Obtain the activation signal of the underlying fault handling strategy triggered by the diagnostic system of the underlying software based on the fault code; Based on the first configurable calibration variable, the activation signal of the underlying fault handling strategy is selected, or the result of a logical OR operation between the activation signal of the application layer and the activation signal of the underlying fault handling strategy is selected as the final fault handling strategy signal.

2. The method for generating a transmission fault handling strategy according to claim 1, characterized in that, Based on the predetermined mapping relationship between faults and fault handling strategies, the corresponding application-layer fault handling strategy activation signal is determined and output, specifically including: For each fault, a fault handling strategy requirement identifier is set. This identifier contains N bits, and each bit represents a fault handling strategy. Construct a mapping relationship between the fault activation flag signal and the corresponding fault handling strategy requirement identifier, denoted as the first mapping relationship; The fault activation flag is set in response to the first mapping relationship, and the corresponding fault handling strategy requirement identifier is located. Perform a bitwise OR operation on the fault handling strategy requirement identifiers located by all currently set fault activation flags to obtain the comprehensive fault handling strategy signal. The comprehensive fault handling strategy signal is bitwise ANDed with the standardized fault handling instruction identifiers of various predefined fault handling strategies to obtain the fault handling strategy activation signal. This signal is then output as the application layer fault handling strategy activation signal. The standardized fault handling instruction identifier contains N bits, with only the specific bit representing its corresponding action being 1 and the rest being 0.

3. The method for generating a transmission fault handling strategy according to claim 2, characterized in that, This method includes a dynamic policy adjustment step, specifically including: Several partitions are set for the target real-time operating parameters of the vehicle, and one or more policy adjustment tables are predefined for each partition; the index of the policy adjustment table is a combination of fault identifier and standardized fault handling instruction identifier, and the table entry content is the adjusted control parameter value or policy enable flag adapted to the operating state partition. Within the current software scheduling cycle, obtain the target's real-time running status parameters and determine its current running status partition. Based on the current running status partition, look up at the predefined policy adjustment table to obtain at least one of the following information: the adjustment value of the fault handling policy requirement identifier corresponding to the currently active fault, and the adjustment control parameter value of the standardized fault handling instruction identifier corresponding to the currently activated or pending activation. The acquired adjustment information is logically ANDed / ORed with the intermediate result of the fault handling strategy requirement identifier generated according to the original logic in the current cycle, or the application layer fault handling strategy activation signal, and the parameters are fused. The fused result is used as the final fault handling strategy signal or control parameter output to drive the actuator.

4. The method for generating a transmission fault handling strategy according to claim 2 or 3, characterized in that, The application layer fault handling strategy activation signal drives the transmission control unit to execute the corresponding physical control action. The physical control action corresponds one-to-one with the handling strategy represented by the standardized fault handling instruction identifier, including at least one of the following: entering limp home mode, enabling alternative signals, cutting off specific solenoid valve control, and limiting output torque.

5. The method for generating a transmission fault handling strategy according to claim 2, characterized in that, The method also includes: A second configurable calibration variable is set, which is a bitmask containing N bits; wherein, the i-th bit of the second configurable calibration variable is used to enable or disable the i-th normalized fault handling instruction identifier. Perform a bitwise AND operation between the application layer fault handling strategy activation signal and the second configurable calibration variable to obtain the application layer fault handling strategy signal that is allowed by the project configuration in the current period.

6. The method for generating a transmission fault handling strategy according to claim 1, characterized in that, The method also includes: Set a third configurable calibration variable, which is a bitmask containing N bits. Each bit is used to indicate whether the corresponding standardized fault handling instruction identifier is prohibited from recovery in the current driving cycle. Within each software scheduling cycle, the following operations are performed to generate the final fault handling strategy execution signal: the final fault handling strategy signal is bitwise ANDed with a third configurable calibration variable. If the bitwise AND result is not zero, the fault handling strategy with the corresponding bit set to 1 in the final fault handling strategy execution signal of the previous scheduling cycle is maintained in the final fault handling strategy execution signal of the current scheduling cycle. If the bitwise AND result is zero, the value of the corresponding bit in the final fault handling strategy execution signal of the current scheduling cycle is updated based on the final fault handling strategy signal.

7. The method for generating a transmission fault handling strategy according to claim 1 or 2, characterized in that, The first configurable calibration variable is a one-bit flag variable. When it is calibrated to the first value, the final fault handling strategy signal is the underlying fault handling strategy activation signal. When it is calibrated to the second value, the final fault handling strategy signal is the result of a logical OR operation between the application layer fault handling strategy activation signal and the underlying fault handling strategy activation signal.

8. A transmission fault handling strategy generation system, characterized in that, This system is configured in application layer software, including: The application layer fault handling strategy activation signal generation module is used to determine and output the corresponding application layer fault handling strategy activation signal in response to the setting of the activation flag signal of at least one fault, based on the predetermined mapping relationship between faults and fault handling strategy identifiers. The underlying fault handling strategy activation signal acquisition module is used to acquire the underlying fault handling strategy activation signal triggered by the diagnostic system of the underlying software based on the fault code. The final fault handling strategy signal determination module is used to select, based on a first configurable calibration variable, the activation signal of the underlying fault handling strategy, or the result of a logical OR operation between the activation signal of the application layer and the activation signal of the underlying fault handling strategy, as the final fault handling strategy signal.

9. A vehicle-mounted terminal, characterized in that, include: Memory, used to store the gearbox fault handling strategy generation program; A processor is configured to implement the steps of the transmission fault handling strategy generation method as described in any one of claims 1 to 7 when executing the transmission fault handling strategy generation program.

10. A vehicle, characterized in that, It is equipped with the vehicle-mounted terminal as described in claim 9.

Images