Vehicle window learning execution method and device, vehicle and storage medium

Abstract

The invention provides a vehicle window learning execution method and device, a vehicle and a storage medium, the method is applied to the field of vehicle control, and the method comprises the steps that a detection instruction for a vehicle window anti-pinch parameter packet is acquired; wherein the car window anti-pinch parameter packet is used for realizing an anti-pinch function of a car window; in response to the detection instruction, detecting whether a serial number of a preset position in a target storage area is a target serial number; and when it is determined that the serial number of the preset position is the target serial number, car window learning is allowed to be executed. According to the method, a car window learning mechanism based on car window anti-pinch parameter package numbers is introduced, on the premise that hardware cost is not increased, correct starting of car window learning, rapid verification of a production line and parameter configuration isolation are achieved, and the safety and reliability of a car window system are remarkably improved.

Description

Technical Field

[0001] This application relates to the field of vehicle control, and more specifically, to a method, apparatus, vehicle, and storage medium for performing window learning in the field of vehicle control. Background Technology

[0002] In vehicle electronic control systems, the anti-pinch function for windows is typically implemented by a controller integrated into the door module. This function relies on a set of anti-pinch parameters closely related to the physical characteristics of the entire vehicle, including but not limited to the travel length of the window glass, the mechanical resistance characteristics of the lifting mechanism, the compression force of the sealing strip, and the motor current response curve. Due to significant differences in the overall vehicle styling and window structure design among different vehicle models, the aforementioned anti-pinch parameters also vary, requiring the development of independent software variants for the controller software for each vehicle model.

[0003] To reduce the number of software variants and improve platform integration, a strategy of "unified basic software and production line calibration parameter package writing" is now widely adopted. This means that during vehicle manufacturing, the corresponding window anti-pinch parameter package is written into the door module's storage area based on the specific vehicle model. Only after successfully writing the anti-pinch parameter package and executing the window learning process can the controller accurately establish a baseline model for window operation, thereby ensuring the normal operation of the anti-pinch function.

[0004] If the door module completes window learning before successfully writing the anti-pinch parameter package, the operating benchmark established by the controller will be seriously inconsistent with the actual physical characteristics, causing the anti-pinch function of the window to fail, which may lead to safety hazards such as personal injury or property damage. Summary of the Invention

[0005] This application provides a method, apparatus, vehicle, and storage medium for performing window learning. The method can determine that the window anti-pinch parameters have been successfully written into the door module before window learning is performed, thereby improving the success rate of window learning.

[0006] Firstly, a method for learning and executing vehicle window learning is provided, the method comprising: Obtain detection instructions for the anti-pinch parameter package for vehicle windows; wherein, the anti-pinch parameter package for vehicle windows is used to implement the anti-pinch function of vehicle windows; In response to the detection command, detect whether the number at a preset location in the target storage area is the target number; When the preset location number is determined to be the target number, window learning is allowed.

[0007] Through the above technical solution, window learning is only allowed after the preset position number in the target storage area is the target number, indicating that the window anti-pinch parameter package has been successfully written. Without increasing hardware costs, the correct start of window learning, rapid production line verification, and parameter configuration isolation are achieved. This avoids the window anti-pinch function from failing when the vehicle does not have the window anti-pinch parameter package, which could cause personal injury or property damage during subsequent use. This significantly improves the safety and reliability of the window system.

[0008] In conjunction with the first aspect, in some possible implementations, after responding to the detection instruction and detecting whether the number at a preset location in the target storage area is the target number, the method further includes: When it is determined that the number of the preset location is not the target number, a manual window learning instruction is received; In response to the manual window learning command, only the window driver is activated, and no data corresponding to the window learning is generated.

[0009] The above technical solution determines that the window anti-pinch parameter package has not been successfully written when the number of the preset position is not the target number. Therefore, window learning is not performed. However, when a manual window learning command is given, the window movement is allowed to be driven based on the manual window learning command, such as performing the window raising or lowering action. This takes into account the user's need to manually raise and lower the window and ensures the user's basic ability to operate the window. However, no data corresponding to window learning is generated to prevent window learning from being performed.

[0010] In combination with the first aspect and the above implementation methods, in some possible implementation methods, after responding to the detection instruction and detecting whether the number at a preset location in the target storage area is the target number, the method further includes: When it is determined that the number of the preset position is not the target number, an automatic window learning instruction is received, and the window is not driven to move.

[0011] By using the above technical solution, when the number at the preset position is not the target number, it is determined that the window anti-pinch parameter package has not been successfully written. Therefore, window learning is not performed, and the window is not driven to move when the automatic window learning command is received. This allows the production line equipment to quickly identify the target vehicle with a fault of missing window anti-pinch parameter package, significantly shortening the troubleshooting time and improving the efficiency of writing the window anti-pinch parameter package for target vehicles with missing parameters.

[0012] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the step of obtaining the window anti-pinch parameter package detection instruction includes: Receive a window learning instruction, and obtain a window anti-pinch parameter package detection instruction based on the window learning instruction; wherein, the window learning instruction includes at least one of a manual window learning instruction and an automatic window learning instruction; Alternatively, it can obtain the window anti-pinch parameter package detection instruction based on a preset detection cycle.

[0013] The above technical solution obtains a window anti-pinch parameter package detection command upon receiving a window learning command or a preset detection cycle. The detection method responding to the window learning command ensures that the validity of the window anti-pinch parameters is verified in real time before window learning, avoiding window learning based on incorrect parameters. The timed detection based on the preset cycle can periodically verify whether the stored window anti-pinch parameter package is still valid without user intervention, for example, preventing parameter damage due to memory aging or accidental overwriting. Through the triggering methods of these two detection methods, both real-time requirements are met, and the vehicle is equipped with maintenance capabilities, constructing a dual safety defense covering both "use-triggered" and "time-triggered" mechanisms.

[0014] In combination with the first aspect and the above implementation methods, in some possible implementation methods, the step of detecting whether the number at a preset location in the target storage area is a target number in response to the detection instruction includes: In response to the detection command, based on the vehicle configuration information associated with the window, it is detected whether the number at a preset location in the target storage area is a target number that matches the vehicle configuration information; wherein, different vehicle configuration information corresponds to different numbers.

[0015] Through the above technical solution, the vehicle configuration information is matched with the number of the parameter package representing the anti-pinch window. Different vehicle configuration information is associated with different numbers, which solves the problem of parameter consistency and adaptation accuracy of the platform ECU in multiple models and configuration scenarios. It avoids the vehicle from learning the window based on the wrong anti-pinch window parameter package after the wrong anti-pinch window parameter package is flashed, and improves the compatibility and efficiency of multi-model mixed production line.

[0016] In combination with the first aspect and the above implementation methods, in some possible implementation methods, after responding to the detection instruction and detecting whether the number at a preset location in the target storage area is the target number, the method further includes: When it is determined that the number of the preset location is not the target number, a diagnostic fault code representing the verification failure is generated, and the diagnostic fault code is sent to the target device.

[0017] Through the above technical solution, when it is determined that the number of the preset position is not the target number, a diagnostic fault code indicating verification failure is actively sent to the target device. This enables target devices such as production line electrical inspection equipment to promptly detect the problem of the window anti-pinch parameter package failure in the target vehicle, quickly locate the source of the fault and solve the problem, significantly shorten the troubleshooting time and reduce the risk of manufacturing defects escaping.

[0018] In combination with the first aspect and the above implementation methods, in some possible implementation methods, after generating a diagnostic fault code representing the verification failure and sending the diagnostic fault code to the target device when it is determined that the number of the preset location is not the target number, the method further includes: When a deletion instruction is received for the diagnostic fault code, a detection instruction for the anti-pinch parameter package of the window is obtained based on the deletion instruction.

[0019] The above technical solution receives a deletion command for diagnostic fault codes and obtains a detection command for the anti-pinch parameter package for the windows based on the deletion command. This initiates a verification process to check whether the anti-pinch parameter package is written to the target storage area, ensuring that the diagnostic fault codes can only be cleared if the anti-pinch parameter package is valid. This prevents the diagnostic fault codes from being accidentally deleted or forcibly cleared, ensuring the authenticity of the fault repair.

[0020] Secondly, a vehicle window learning execution device is provided, the vehicle window learning execution device comprising: The detection and acquisition module is used to acquire detection instructions for the anti-pinch parameter package of the vehicle window; wherein, the anti-pinch parameter package of the vehicle window is used to realize the anti-pinch function of the vehicle window; The number detection module is used to respond to the detection command and detect whether the number at a preset position in the target storage area is the target number; The window learning module is used to allow window learning to be performed when the preset position number is determined to be the target number.

[0021] Thirdly, a vehicle is provided, including a memory for storing executable program code; A processor is configured to call and run the executable program code from the memory, causing the vehicle to execute any of the aforementioned window learning execution methods.

[0022] Fourthly, a computer program product is provided, comprising: computer program code, which, when run on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof.

[0023] Fifthly, a computer-readable storage medium is provided that stores computer program code, which, when executed on a computer, causes the computer to perform the methods described in the first aspect or any possible implementation thereof. Attached Figure Description

[0024] Figure 1 This is a flowchart illustrating the architecture of a vehicle window learning execution method provided in an embodiment of this application. Figure 2 This is a flowchart illustrating a method for learning and executing vehicle window data according to an embodiment of this application. Figure 3 This is a flowchart illustrating a method for learning and executing vehicle window data according to an embodiment of this application. Figure 4 This is a flowchart illustrating a method for learning and executing vehicle window data according to an embodiment of this application. Figure 5 This is a flowchart illustrating a method for learning and executing vehicle window data according to an embodiment of this application. Figure 6 This is a schematic diagram of the structure of a car window learning execution device provided in an embodiment of this application; Figure 7 This is a schematic diagram of the structure of a vehicle provided in an embodiment of this application. Detailed Implementation

[0025] The technical solutions in this application will be clearly and thoroughly described below with reference to the accompanying drawings. In the description of the embodiments of this application, unless otherwise stated, " / " means "or," for example, A / B can mean A or B. "And / or" in the text is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, and B existing alone. Furthermore, in the description of the embodiments of this application, "multiple" refers to two or more than two.

[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 technical features indicated. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature.

[0027] Figure 1 This is a flowchart illustrating the architecture of a vehicle window learning execution method provided in an embodiment of this application. Figure 1 It includes at least a server 101 that sends instructions such as window learning commands, and a vehicle 102 that executes the window learning execution method. It is understood that... Figure 1The number, type, and connection method of the servers and vehicles shown are for illustrative purposes only, and this application embodiment does not impose any limitations on them.

[0028] The aforementioned server 101 can be a standalone server device, such as a rack-mounted, blade, tower, or cabinet-type industrial-grade server device, or it can be a workstation, mainframe computer, or other hardware device with strong computing and communication capabilities; or it can be a server cluster composed of multiple servers, in which each server can be deployed symmetrically, wherein each server is functionally and equally important in the task processing chain, and each server can independently provide services to the outside world, that is, it can complete the task of sending instructions and interacting with data without relying on the collaborative support of other servers.

[0029] Specifically, in this embodiment, server 101 is a dedicated control device on the production line used to send window learning commands to vehicle 102. Its main function is to send automatic window learning commands to vehicle 102 through standard communication protocols (such as CAN, LIN, or Ethernet) during the vehicle assembly or electrical inspection stage, triggering the door module installed on vehicle 102 to perform anti-pinch parameter verification and learning processes. The specific type of server 101 can be a production line PLC controller, industrial PC (IPC), diagnostic test bench, or a remote control terminal integrated into the MES system. Its operating environment is usually deployed in the final assembly workshop or electrical inspection station of an automobile manufacturing plant.

[0030] In this embodiment, the vehicle 102 is equipped with a window structure, and the window should have a lifting function and be driven by an electronic control system and / or a manual control system. The window can be a power window, including but not limited to front door windows, rear door windows, or sunroofs, and its structure typically includes glass, guide rails, a lifting motor, a position sensor, and an anti-pinch detection unit. The window control module (such as a door control module) is responsible for receiving window learning instructions from the server 101, verifying the validity of the internally stored window anti-pinch parameter package, and executing the window learning process when the conditions are met to establish or update the anti-pinch benchmark model. It is understood that vehicle 102 may also have other on-board systems or functional modules, such as body control module (BCM), instrument panel, and on-board network (CAN / LIN / Ethernet), to support communication and interaction with server 101. Furthermore, since vehicle 102 is located in a production line or testing environment in this embodiment, its power state, communication interface, and safety locking mechanism must be configured to allow external devices to intervene in control, so as to successfully complete the writing and verification process of the window anti-pinch parameter package.

[0031] Vehicle 102 and server 101 can communicate via a communication link established through a communication protocol. For example, the network can be a wireless network or a wired network. Wireless networks include, but are not limited to, cellular networks, wireless LANs, infrared networks, or Bluetooth networks. Wired networks include, but are not limited to, Ethernet, universal serial bus (USB), or controller area networks. In one or more embodiments of the specification, technologies and / or formats including Hyper Text Markup Language (HTML), Extensible Markup Language (XML), etc., are used to represent data exchanged over the network (such as target compressed packets). Furthermore, conventional encryption technologies such as Secure Socket Layer (SSL), Transport Layer Security (TLS), Virtual Private Network (VPN), and Internet Protocol Security (IPsec) can be used to encrypt all or some of the links. In other embodiments, customized and / or dedicated data communication technologies can be used to replace or supplement the aforementioned data communication technologies.

[0032] Because the door module is assembled on the door of vehicle 102, and the door is assembled at the last station of the vehicle assembly line, the window anti-pinch parameter package is written at a very late stage on the vehicle production line. Furthermore, during the writing of the window anti-pinch parameter package software on the vehicle production line, there are instances of missed writing or writing failures. All of these factors contribute to the vehicle not having the correct window anti-pinch parameters. Additionally, the door assembly line is a separate assembly line. At the last station of the door assembly line, door electrical testing is performed. During this testing, server 101 sends instructions to the door module of vehicle 102 to close the windows. This process may involve window learning. All of these processes result in the door module performing window learning before the correct window anti-pinch parameters are matched, thus causing the window anti-pinch function to malfunction.

[0033] To address the aforementioned problems, this application provides a method for learning and executing vehicle window learning techniques. In one embodiment, as follows: Figure 2 The diagram shown is a flowchart illustrating a method for detecting anti-pinch parameter packages for vehicle windows according to an embodiment of this application. This method can be implemented using a computer program and can run on a window learning execution device based on the von Neumann architecture. The computer program can be integrated into the application or run as a standalone utility application.

[0034] Specifically, the learning and execution method for the car window includes: S101. Obtain the detection command for the anti-pinch parameter package for the vehicle window.

[0035] The anti-pinch parameter package is used to implement the anti-pinch function of the windows. If the anti-pinch parameter package is missing, damaged, or incompatible with the current vehicle configuration, even if window learning is performed, it may result in the window not retracting when a hand is pinched (safety hazard) or retracting erroneously when there is no obstruction (functional malfunction).

[0036] The specific contents of a window anti-pinch parameter package typically include, but are not limited to, the following information: anti-pinch parameter package code, a unique code used to identify the vehicle model, door position (e.g., front left, rear right), glass type, and motor model to which the window anti-pinch parameter package belongs; current-position reference curve, describing the ideal reference trajectory of motor current changing with glass position during normal window raising and lowering; lock threshold (Pinch Threshold), the critical value of current or torque for determining whether pinching occurs, which can be set in segments according to position; guide rail friction coefficient compensation parameters, used to correct friction fluctuations caused by aging of sealing strips, temperature changes, etc.; motor characteristic parameters, such as back electromotive force constant, resistance, inertia, etc., used to build an accurate motor dynamics model; and learning permission flag, indicating whether the window anti-pinch parameter package has been verified and window learning is allowed.

[0037] The detection command for the anti-pinch parameter package is used to detect whether the anti-pinch parameter package is stored in the vehicle's preset storage area, that is, whether the anti-pinch parameter package has been successfully written to the vehicle. In this embodiment, the successful writing of the anti-pinch parameter package is verified by detecting whether the number at the preset location in the target storage area is the target number.

[0038] In one embodiment, obtaining the window anti-pinch parameter package detection instruction includes: receiving a window learning instruction and obtaining the window anti-pinch parameter package detection instruction based on the window learning instruction.

[0039] A window learning command is a control signal used to trigger a complete window lifting and lowering stroke to establish or update the anti-pinch reference model. Window learning is a prerequisite for window learning and activating the anti-pinch function. After initial window installation, door module replacement, software or parameter package updates, a window learning process must be performed to collect data such as motor current, position, and speed during actual operation, constructing a normal operating curve that matches the current mechanical state. Subsequently, during routine window lifting and lowering checks, the normal operating curve is compared in real time. If an abnormal deviation is detected (such as a sudden increase in current), it is identified as a pinching event, triggering the window to retract, thus achieving the anti-pinch function.

[0040] Window learning commands include at least one of the following: manual window learning commands and automatic window learning commands. Manual window learning commands are learning requests actively triggered by the user through physical operation of the window switches. Automatic window learning commands are control commands automatically sent by external devices (such as server 101) or the system to trigger window learning in batches.

[0041] For example, window learning commands can also include power-on self-learning commands, triggered by the vehicle's controller based on a power-on signal. Alternatively, window learning commands can include an OTA (Over-The-Air) remote learning module, where the vehicle's onboard communication module (T-Box) receives window learning commands from the cloud.

[0042] In this embodiment, after the vehicle controller receives the window learning instruction, it obtains the window anti-pinch parameter package detection instruction based on the window learning instruction.

[0043] In another embodiment, the window anti-pinch parameter package detection instruction is obtained based on a preset detection cycle.

[0044] In this embodiment, the vehicle's storage unit is equipped with a timer or task scheduling unit, which periodically generates a window anti-pinch parameter package detection instruction according to a pre-configured detection cycle.

[0045] The preset testing cycle can be set in several ways. For example, a fixed testing cycle can be calibrated at the factory, with a default cycle value written during the ECU software compilation stage, such as obtaining a window anti-pinch parameter package testing command every 100 hours. Another example is by updating the testing cycle online, dynamically adjusting the testing cycle during after-sales service or OTA updates via UDS service. Yet another example is by triggering the testing cycle through event linkage, binding the cycle testing to specific vehicle events, such as each time the door module is powered on, each time the vehicle enters a sleep / wake-up process, or obtaining a window anti-pinch parameter package testing command after accumulating 1000 kilometers of driving.

[0046] Understandably, the testing cycle can be flexibly configured based on the configuration information, safety level, usage environment, or reliability requirements of different vehicles.

[0047] In this embodiment, upon receiving a window learning command or a preset detection cycle, a window anti-pinch parameter package detection command is obtained. The detection method responding to the window learning command ensures that the validity of the window anti-pinch parameters is verified in real time before window learning, avoiding window learning based on incorrect parameters. Meanwhile, the timed detection based on the preset cycle can periodically verify whether the stored window anti-pinch parameter package is still valid without user intervention, for example, preventing parameter damage due to memory aging or accidental overwriting. By using these two detection triggering methods, both real-time requirements are met, and the vehicle is equipped with maintenance capabilities, constructing a dual safety defense line covering both "use-triggered" and "time-triggered" mechanisms.

[0048] In another embodiment, the parameter verification process can be explicitly triggered in response to a dedicated testing request from a server (such as a production line control terminal) or a diagnostic instrument.

[0049] S102. In response to the detection command, detect whether the number at the preset location in the target storage area is the target number.

[0050] The target storage area can be the address space within the Door Control Module (DCM)'s internal non-volatile memory (such as Flash, EEPROM, or FRAM) that stores the number indicating whether the window anti-pinch parameter package has been successfully written. This target storage area can also store the window anti-pinch parameter package itself. This storage area is defined during the ECU software design phase, has a fixed starting address and length, and is usually controlled by a write protection mechanism to prevent accidental overwriting during runtime.

[0051] Within this target storage area, the preset location specifically refers to one or more pre-agreed byte offset addresses used to store a number that identifies whether the window anti-pinch parameter package has been successfully flashed. At the factory, this preset location in the target storage area stores an initial number; for example, by default, 15 0x46s or 15 0xFFs are written to this preset location as the initial number.

[0052] In response to the detection command, the system reads the currently stored number from a preset location in the target storage area, and checks whether the current number is the initial number and whether it is the target number. The target number can be a number pre-stored in the local storage area that indicates the window anti-pinch parameter package associated with the vehicle has been successfully flashed.

[0053] S103. When the preset position number is determined to be the target number, window learning is allowed.

[0054] If the preset location number is determined to be the target number, it indicates that the window anti-pinch parameter package associated with the vehicle has been successfully flashed, unlocking the software lock on the window learning function and enabling the vehicle's system to execute the complete window learning process. If the preset location number is not the target number, the vehicle remains in a state where it does not have window learning capabilities.

[0055] For example, to disable the learning function, the DCM usually has a "Learn_Enable_Flag" which is initially 0. Only after the number verification is successful will this flag be set to 1, and subsequent window learning trigger conditions can be responded to.

[0056] Through the above technical solution, window learning is only allowed after the preset position number in the target storage area is the target number, indicating that the window anti-pinch parameter package has been successfully written. Without increasing hardware costs, the correct start of window learning, rapid production line verification, and parameter configuration isolation are achieved. This avoids the window anti-pinch function from failing when the vehicle does not have the window anti-pinch parameter package, which could cause personal injury or property damage during subsequent use. This significantly improves the safety and reliability of the window system.

[0057] In one embodiment, such as Figure 3 The diagram shown is a flowchart illustrating a method for detecting anti-pinch parameter packages for vehicle windows according to an embodiment of this application. This method can be implemented using a computer program and can run on a window learning execution device based on the von Neumann architecture. The computer program can be integrated into the application or run as a standalone utility application.

[0058] Specifically, the learning and execution method for the car window includes: S201. Obtain the detection command for the anti-pinch parameter package for vehicle windows.

[0059] See S101 above; it will not be repeated here.

[0060] S202. In response to the detection command, detect whether the number at the preset location in the target storage area is the target number.

[0061] See S102 above, which will not be repeated here.

[0062] S203. When the preset position number is determined to be the target number, window learning is allowed.

[0063] See S103 above, which will not be repeated here.

[0064] S204. When the number at the preset location is not the target number, receive the manual window learning instruction.

[0065] Manual window learning commands refer to learning requests actively triggered by the user through physical operation of the window switches. For example, a user can send and receive a manual window learning command by pressing and holding the window up / down switch for more than a preset time (e.g., pressing continuously for more than 3 seconds), or by performing a "one-key up / down reset" operation under a specific power state, or by detecting operations such as combination buttons or preset gestures.

[0066] S205: In response to the manual window learning command, only drive the window to move, without generating corresponding data for window learning.

[0067] When the number at the preset location is not the target number, it indicates that the vehicle's storage area does not contain the window anti-pinch parameter package, or the window anti-pinch parameter package does not match the vehicle. In response to the manual window learning command, the window is only driven to move, and no data corresponding to window learning is generated.

[0068] For example, the system controls the car window to complete a full mechanical stroke (e.g., from bottom to top) in a specified direction (which could be upward) until it reaches the top stop and operates for a period of time. During this process, the system does not generate data corresponding to the window learning process by not activating the data acquisition module (e.g., not sampling motor current, Hall sensor pulses, position encoder signals, or voltage / temperature data), not running the window learning algorithm (e.g., not calculating the current-position curve, not updating the stall threshold, and not fitting the friction model), and not changing the functional status flags (e.g., keeping the status bits such as "anti-pinch function not activated" and "learning not completed" unchanged).

[0069] The above technical solution determines that the window anti-pinch parameter package has not been successfully written when the number of the preset position is not the target number. Therefore, window learning is not performed. However, when a manual window learning command is given, the window movement is allowed to be driven based on the manual window learning command, such as performing the window raising or lowering action. This takes into account the user's need to manually raise and lower the window and ensures the user's basic ability to operate the window. However, no data corresponding to window learning is generated to prevent window learning from being performed.

[0070] S206. When the number at the preset position is not the target number, receive the automatic window learning instruction and do not drive the window to move.

[0071] Automatic window learning commands refer to control commands automatically sent by external devices or systems to trigger window learning in batches. For example, during vehicle assembly, production line servers or test benches send automatic window learning commands to vehicles via CAN / LIN / Ethernet buses; maintenance personnel use specialized equipment (such as ODIS, Tech2, etc.) to send automatic window learning commands via after-sales diagnostic tools after replacing vehicle door modules; or after vehicle software upgrades, the vehicle's central gateway or OTA management system automatically issues automatic window learning commands to initialize the anti-pinch function of the windows.

[0072] When the number of the preset position is not the target number, it indicates that there is no window anti-pinch parameter package in the vehicle's storage area, or that the window anti-pinch parameter package is not compatible with the vehicle. When receiving the automatic window learning command, the window is not driven to move. For example, the drive signal is not output to the window motor, the window glass is kept in a stationary state, and window learning or data acquisition operations are not performed.

[0073] By using the above technical solution, when the number at the preset position is not the target number, it is determined that the window anti-pinch parameter package has not been successfully written. Therefore, window learning is not performed, and the window is not driven to move when the automatic window learning command is received. This allows the production line equipment to quickly identify the target vehicle with a fault of missing window anti-pinch parameter package, significantly shortening the troubleshooting time and improving the efficiency of writing the window anti-pinch parameter package for target vehicles with missing parameters.

[0074] In one embodiment, such as Figure 4 The diagram shown is a flowchart illustrating a method for detecting anti-pinch parameter packages for vehicle windows according to an embodiment of this application. This method can be implemented using a computer program and can run on a window learning execution device based on the von Neumann architecture. The computer program can be integrated into the application or run as a standalone utility application.

[0075] Specifically, the learning and execution method for the car window includes: S301, Obtain the detection command for the anti-pinch parameter package for vehicle windows.

[0076] See S101 above; it will not be repeated here.

[0077] S302. In response to the detection command, based on the vehicle configuration information associated with the window, detect whether the number in the preset location in the target storage area is a target number that matches the vehicle configuration information.

[0078] Vehicle configuration information associated with vehicle windows refers to a set of vehicle attributes that characterize the mechanical or electrical properties of the vehicle's windows, directly affecting the calibration parameters required for the anti-pinch function of the windows (such as stall threshold, friction compensation, motor response curve, etc.). For example, vehicle configuration information may include one or more of the following: window position information, vehicle model information, glass configuration information, motor model information, and function configuration level.

[0079] Different vehicle configuration information corresponds to different anti-pinch parameter packages for windows, and different anti-pinch parameter packages are associated with different numbers. For example, if a vehicle configuration includes model A and motor model M101, the corresponding anti-pinch parameter package includes X parameters and the corresponding target number is 0×5A3F. If a vehicle configuration includes model B and motor signal M102, the corresponding anti-pinch parameter package includes Y parameters and the corresponding target number is 0×7C21.

[0080] The vehicle configuration information associated with the windows can be obtained by pre-setting, such as recording it to the door module's storage area at the time the vehicle's ECU is manufactured, or by obtaining it through CAN messages from the vehicle control module (BCM) or gateway, or by other methods.

[0081] In response to a detection command, based on the vehicle configuration information associated with the window, it checks whether the number in a preset location in the target storage area matches the target number in the vehicle configuration information. For example, if the target number is determined to be 0×5A3F based on the vehicle configuration information associated with the window, it checks whether the number in the preset location in the target storage area matches the aforementioned target number.

[0082] In this embodiment, the vehicle configuration information is matched with the number of the parameter package representing the anti-pinch window. Different vehicle configuration information is associated with different numbers, which solves the problem of parameter consistency and adaptation accuracy of the platform-based ECU in multiple vehicle models and configuration scenarios. It avoids the vehicle from learning the window based on the wrong anti-pinch window parameter package after the wrong anti-pinch window parameter package is flashed, and improves the compatibility and efficiency of multi-model mixed production line.

[0083] S303. When the preset position number is determined to be the target number, window learning is allowed.

[0084] If the number at the preset location is not the target number, it can be determined that the vehicle's storage area does not contain the window anti-pinch parameter package, or that the flashed window anti-pinch parameter package does not match the vehicle. Based on the incorrect window anti-pinch parameter package, window learning will not be performed.

[0085] Through the above technical solution, window learning is only allowed after the preset position number in the target storage area is the target number, indicating that the window anti-pinch parameter package has been successfully written. Without increasing hardware costs, the correct start of window learning, rapid production line verification, and parameter configuration isolation are achieved. This avoids the window anti-pinch function from failing when the vehicle does not have the window anti-pinch parameter package, which could cause personal injury or property damage during subsequent use. This significantly improves the safety and reliability of the window system.

[0086] In one embodiment, such as Figure 5 The diagram shown is a flowchart illustrating a method for detecting anti-pinch parameter packages for vehicle windows according to an embodiment of this application. This method can be implemented using a computer program and can run on a window learning execution device based on the von Neumann architecture. The computer program can be integrated into the application or run as a standalone utility application.

[0087] Specifically, the learning and execution method for the car window includes: S401, Obtain the detection command for the anti-pinch parameter package for vehicle windows.

[0088] See S101 above; it will not be repeated here.

[0089] S402. In response to the detection command, detect whether the number at the preset location in the target storage area is the target number.

[0090] See S102 above, which will not be repeated here.

[0091] S403. When it is determined that the number of the preset location is not the target number, generate a diagnostic fault code indicating that the verification failed, and send the diagnostic fault code to the target device.

[0092] When it is determined that the number of the preset location is not the target number, a diagnostic fault code (DTC) is generated to characterize the invalid or mismatched parameters of the window anti-pinch system. The diagnostic fault code is stored in the vehicle's memory, and the diagnostic fault code is reported to one or more target devices according to the preset communication strategy.

[0093] Diagnostic fault codes (DTCs) are a set of standardized codes defined according to international standards (such as ISO 15031-6 and SAE J2012) to identify specific types of faults occurring in a vehicle's electronic systems. A DTC typically consists of 5 alphanumeric characters. The first digit indicates the system type (B=body, C=chassis, P=powertrain, U=network), the second digit indicates the fault type (1=manufacturer-defined, 0=general standard), and the last three digits are the specific fault number. For example, a generated DTC might be B2001, where B represents the body system, 2 represents manufacturer-defined, and 001 is a preset specific fault ID. Alternatively, a DTC might be B2A3F, indicating a mismatch in window learning parameters.

[0094] The target device refers to the device capable of receiving, processing, or displaying the diagnostic fault code. Examples of target devices include in-vehicle human-machine interfaces, after-sales diagnostic instruments, production line test benches, and remote servers.

[0095] For example, if a vehicle's left front door module is replaced at a dealership but the anti-pinch window parameter package is not flashed, when the vehicle is started, the controller executes the window learning execution method and detects that the number in the preset location in the target storage area is not the target number, i.e., the verification fails. The controller generates a diagnostic fault code DTC B2001 and stores it in the storage unit, and also sends the diagnostic fault code to the ODIS diagnostic tool so that the ODIS diagnostic tool's display device displays the fault code, thus allowing the user to discover that the vehicle has a problem with the anti-pinch window parameter package flashing failure.

[0096] In this embodiment, when it is determined that the number of the preset location is not the target number, a diagnostic fault code indicating verification failure is actively sent to the target device. This enables the target device, such as the production line electrical inspection equipment, to promptly detect the problem of the window anti-pinch parameter package being written to the target vehicle, quickly locate the source of the fault and resolve the problem, significantly shorten the troubleshooting time and reduce the risk of manufacturing defects escaping.

[0097] In one embodiment, when a deletion instruction for a diagnostic fault code is received, a detection instruction for the window anti-pinch parameter package is obtained based on the deletion instruction.

[0098] The generated diagnostic fault codes are stored in the vehicle's storage unit, and these codes are also associated with auxiliary information (also known as "DTC snapshots" or "freeze frames"). This auxiliary information may include one or more of the following: fault occurrence time (number of power-ups, operating hours), vehicle identification number (VIN) fragment, current door position (LF / RF, etc.), preset position number read value (e.g., Current_ID = 0x0000), target number (e.g., Target_ID = 0x5A3F), and trigger conditions for the window anti-pinch parameter package detection command (e.g., window learning command cycle detection). By storing diagnostic fault codes in association with auxiliary information, repair personnel can better understand the fault occurrence.

[0099] Deletion commands for diagnostic fault codes are typically initiated by external devices or systems to clear stored diagnostic fault codes from the memory unit. They can also be used to clear auxiliary information associated with the diagnostic codes. Deletion commands can be obtained from after-sales diagnostic instruments, production line testing systems, or remote servers. Deletion commands can be implemented based on standard diagnostic protocols, such as the ClearDiagnosticInformation service in UDS (ISO 14229), whose request message contains a mask or specific number of the diagnostic fault code to be cleared.

[0100] Since diagnostic codes are generated due to missing or mismatched anti-pinch window parameter packages, their removal requires the correct anti-pinch window parameter package to be successfully flashed. Allowing direct deletion of diagnostic codes without verifying the validity of the current anti-pinch window parameter package could lead to the mistaken belief that the fault has been fixed when the anti-pinch function is still unusable, thus masking the true safety risks.

[0101] Therefore, upon receiving a deletion command, the vehicle's controller does not immediately clear the diagnostic fault codes. Instead, it first performs a window anti-pinch parameter package check. This means that based on the deletion command, it obtains a check command for the window anti-pinch parameter package. The fault code is only cleared if the number in the preset location of the detection target storage area matches the target number. If the check still fails, the fault code is refused to be cleared, or a new fault code and associated auxiliary information are generated after clearing the fault code.

[0102] In this embodiment, when a deletion instruction for a diagnostic fault code is received, a detection instruction for the window anti-pinch parameter package is obtained based on the deletion instruction, thereby initiating a verification process to determine whether the window anti-pinch parameter package has been written to the target storage area. This ensures that the diagnostic fault code is cleared only if the window anti-pinch parameter package is valid, preventing the diagnostic fault code from being accidentally deleted or forcibly cleared, and ensuring the authenticity of the fault repair.

[0103] The following are embodiments of the apparatus described in this application, which can be used to execute the embodiments of the method described in this application. For details not disclosed in the apparatus embodiments of this application, please refer to the embodiments of the method described in this application.

[0104] Please see Figure 6 This illustration shows a schematic diagram of a window learning execution device provided in an exemplary embodiment of this application. The window anti-pinch parameter package detection can be implemented through software, hardware, or a combination of both, and can be considered all or part of the window learning execution device. The window learning execution device includes a detection acquisition module 501, a number detection module 502, and a window learning module 503.

[0105] The detection acquisition module 501 is used to acquire detection instructions for the anti-pinch parameter package of the vehicle window; wherein, the anti-pinch parameter package of the vehicle window is used to realize the anti-pinch function of the vehicle window; The number detection module 502 is used to detect whether the number at a preset position in the target storage area is the target number in response to the detection command; The window learning module 503 is used to allow window learning to be performed when the preset position number is determined to be the target number.

[0106] In one or more embodiments, the window learning execution device further includes: The manual learning module is used to receive a manual window learning instruction when it is determined that the number of the preset position is not the target number; The motion drive module, in response to the manual window learning command, only drives the window to move without generating data corresponding to the window learning process. In one or more embodiments, the window learning execution device further includes: An automatic learning module is used to receive an automatic window learning instruction and not drive the window to move when it is determined that the number of the preset position is not the target number.

[0107] In one or more embodiments, the detection acquisition module 501 includes: The first acquisition unit is used to receive a window learning instruction and acquire a window anti-pinch parameter package detection instruction based on the window learning instruction; wherein, the window learning instruction includes at least one of a manual window learning instruction and an automatic window learning instruction; Alternatively, the second unit is used to obtain the window anti-pinch parameter package detection instruction based on a preset detection cycle.

[0108] In one or more embodiments, the number detection module 502 includes: A configuration matching unit is configured to respond to the detection command and, based on the vehicle configuration information associated with the window, detect whether the number at a preset location in the target storage area is a target number that matches the vehicle configuration information; wherein different vehicle configuration information corresponds to different numbers.

[0109] In one or more embodiments, the window learning execution device further includes: The fault diagnosis module is used to generate a diagnostic fault code indicating that the verification failed when it is determined that the number of the preset location is not the target number, and to send the diagnostic fault code to the target device.

[0110] In one or more embodiments, the window learning execution device further includes: The detection module is used to receive a deletion instruction for the diagnostic fault code and, based on the deletion instruction, obtain a detection instruction for the anti-pinch parameter package of the vehicle window.

[0111] In this application, window learning is only allowed after the preset location number in the target storage area is the target number, indicating that the window anti-pinch parameter package has been successfully written. Without increasing hardware costs, the correct start of window learning, rapid production line verification, and parameter configuration isolation are achieved. This avoids the window anti-pinch function from failing when the vehicle does not have the window anti-pinch parameter package, which could cause personal injury or property damage during subsequent use. This significantly improves the safety and reliability of the window system.

[0112] It should be noted that the window learning execution device provided in the above embodiments is only illustrated by the division of the above functional modules when executing the window learning execution method. In practical applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the window learning execution device and the window learning execution method embodiments provided in the above embodiments belong to the same concept, and the implementation process is detailed in the method embodiments, which will not be repeated here.

[0113] In addition, the device provided in the embodiments of this application may specifically be a chip, component or module. The chip may include a connected processor and a memory. The memory is used to store instructions. When the processor calls and executes the instructions, the chip can execute a window learning execution method provided in the above embodiments.

[0114] This embodiment also provides a computer-readable storage medium storing computer program code. When the computer program code is run on a computer, the computer executes the above-described related method steps to implement the window learning execution method provided in the above embodiment.

[0115] This embodiment also provides a computer program product that, when run on a computer, causes the computer to perform the aforementioned related steps to implement the window learning execution method provided in the above embodiment.

[0116] In this embodiment, the device, computer-readable storage medium, computer program product, or chip are all used to execute the corresponding methods provided above. Therefore, the beneficial effects they can achieve can be referred to the beneficial effects in the corresponding methods provided above, and will not be repeated here.

[0117] The sequence numbers of the embodiments in this application are for descriptive purposes only and do not represent the superiority or inferiority of the embodiments.

[0118] Please see Figure 7 This provides a structural schematic diagram of a vehicle according to an embodiment of this application. Figure 7 As shown, vehicle 600 may include: at least one processor 601, at least one network interface 604, user interface 603, memory 605, and at least one communication bus 602.

[0119] The communication bus 602 is used to enable communication between these components.

[0120] The user interface 603 may include a display screen and a camera. Optionally, the user interface 603 may also include a standard wired interface and a wireless interface.

[0121] The network interface 604 may optionally include a standard wired interface or a wireless interface (such as a Wi-Fi interface).

[0122] The processor 601 may include one or more processing cores. The processor 601 connects to various parts of the vehicle 600 via various interfaces and lines, and performs various functions and processes data of the vehicle 600 by running or executing instructions, programs, code sets, or instruction sets stored in the memory 605, and by calling data stored in the memory 605. Optionally, the processor 601 may be implemented using at least one hardware form of Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), or Programmable Logic Array (PLA). The processor 601 may integrate one or a combination of several of the following: a Central Processing Unit (CPU), a Graphics Processing Unit (GPU), and a modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content to be displayed on the screen; and the modem handles wireless communication. It is understood that the modem may also not be integrated into the processor 601 and may be implemented as a separate chip.

[0123] The memory 605 may include random access memory (RAM) or read-only memory. Optionally, the memory 605 may include a non-transitory computer-readable storage medium. The memory 605 may be used to store instructions, programs, code, code sets, or instruction sets. The memory 605 may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory 605 may also be at least one storage device located remotely from the aforementioned processor 601. Figure 7 As shown, the memory 605, which serves as a computer storage medium, may include an operating system, a network communication module, a user interface module, and an EPS automated testing application.

[0124] exist Figure 7In the vehicle 600 shown, the user interface 603 is mainly used to provide an input interface for the user and to obtain the user input data; while the processor 601 can be used to call the window anti-pinch parameter package detection application stored in the memory 605, and specifically perform the following operations: Obtain detection instructions for the anti-pinch parameter package for vehicle windows; wherein, the anti-pinch parameter package for vehicle windows is used to implement the anti-pinch function of vehicle windows; In response to the detection command, detect whether the number at a preset location in the target storage area is the target number; When the preset location number is determined to be the target number, window learning is allowed.

[0125] In one or more embodiments, after the processor 601 executes the detection instruction in response to detect whether the number at a preset location in the target storage area is a target number, it further executes: When it is determined that the number of the preset location is not the target number, a manual window learning instruction is received; In response to the manual window learning command, only the window is driven to move, without generating the data corresponding to the window learning.

[0126] In one or more embodiments, after the processor 601 executes the detection instruction in response to detect whether the number at a preset location in the target storage area is a target number, it further executes: When it is determined that the number of the preset position is not the target number, an automatic window learning instruction is received, and the window is not driven to move.

[0127] In one or more embodiments, the processor 601 executes the instruction to obtain the anti-pinch parameter package detection for the vehicle window, specifically performing the following: Receive a window learning instruction, and obtain a window anti-pinch parameter package detection instruction based on the window learning instruction; wherein, the window learning instruction includes at least one of a manual window learning instruction and an automatic window learning instruction; Alternatively, it can obtain the window anti-pinch parameter package detection instruction based on a preset detection cycle.

[0128] In one or more embodiments, the processor 601 executes the detection instruction in response to detect whether the number at a preset location in the target storage area is a target number, specifically performing: In response to the detection command, based on the vehicle configuration information associated with the window, it is detected whether the number at a preset location in the target storage area is a target number that matches the vehicle configuration information; wherein, different vehicle configuration information corresponds to different numbers.

[0129] In one or more embodiments, after the processor 601 executes the detection instruction in response to detect whether the number at a preset location in the target storage area is a target number, it further executes: When it is determined that the number of the preset location is not the target number, a diagnostic fault code representing the verification failure is generated, and the diagnostic fault code is sent to the target device.

[0130] In one or more embodiments, after the processor 601 executes the steps of generating a diagnostic fault code indicating the verification failure when it is determined that the number at the preset location is not the target number, and sending the diagnostic fault code to the target device, it further executes: When a deletion instruction is received for the diagnostic fault code, a detection instruction for the anti-pinch parameter package of the window is obtained based on the deletion instruction.

[0131] In this application, window learning is only allowed after the preset location number in the target storage area is the target number, indicating that the window anti-pinch parameter package has been successfully written. Without increasing hardware costs, the correct start of window learning, rapid production line verification, and parameter configuration isolation are achieved. This avoids the window anti-pinch function from failing when the vehicle does not have the window anti-pinch parameter package, which could cause personal injury or property damage during subsequent use. This significantly improves the safety and reliability of the window system.

[0132] Through the above description of the embodiments, those skilled in the art will understand that, for the sake of convenience and brevity, only the division of the above functional modules is used as an example. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above.

[0133] In the embodiments provided in this application, it should be understood that the disclosed apparatus and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another apparatus, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0134] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for learning and executing vehicle window operation, characterized in that, The method includes: Obtain detection instructions for the anti-pinch parameter package for vehicle windows; wherein, the anti-pinch parameter package for vehicle windows is used to implement the anti-pinch function of vehicle windows; In response to the detection command, detect whether the number at a preset location in the target storage area is the target number; When the preset location number is determined to be the target number, window learning is allowed.

2. The vehicle window learning execution method according to claim 1, characterized in that, After responding to the detection command and detecting whether the number at a preset location in the target storage area is the target number, the method further includes: When it is determined that the number of the preset location is not the target number, a manual window learning instruction is received; In response to the manual window learning command, only the window is driven to move, without generating the data corresponding to the window learning.

3. The vehicle window learning execution method according to claim 1, characterized in that, After responding to the detection command and detecting whether the number at a preset location in the target storage area is the target number, the method further includes: When it is determined that the number of the preset position is not the target number, an automatic window learning instruction is received, and the window is not driven to move.

4. The vehicle window learning execution method according to claim 1, characterized in that, The instruction for obtaining the anti-pinch parameter package for the vehicle window includes: Receive a window learning instruction, and obtain a window anti-pinch parameter package detection instruction based on the window learning instruction; wherein, the window learning instruction includes at least one of a manual window learning instruction and an automatic window learning instruction; Alternatively, it can obtain the window anti-pinch parameter package detection instruction based on a preset detection cycle.

5. The window learning execution method according to claim 1, characterized in that, The step of responding to the detection command by detecting whether the number at a preset location in the target storage area is the target number includes: In response to the detection command, based on the vehicle configuration information associated with the window, it is detected whether the number at a preset location in the target storage area is a target number that matches the vehicle configuration information; wherein, different vehicle configuration information corresponds to different numbers.

6. The vehicle window learning execution method according to claim 1, characterized in that, After responding to the detection command and detecting whether the number at a preset location in the target storage area is the target number, the method further includes: When it is determined that the number of the preset location is not the target number, a diagnostic fault code representing the verification failure is generated, and the diagnostic fault code is sent to the target device.

7. The vehicle window learning execution method according to claim 6, characterized in that, After generating a diagnostic fault code indicating verification failure and sending the diagnostic fault code to the target device when it is determined that the number of the preset location is not the target number, the method further includes: When a deletion instruction is received for the diagnostic fault code, a detection instruction for the anti-pinch parameter package of the window is obtained based on the deletion instruction.

8. A vehicle window learning execution device, characterized in that, The vehicle window learning execution device includes: The detection and acquisition module is used to acquire detection instructions for the anti-pinch parameter package of the vehicle window; wherein, the anti-pinch parameter package of the vehicle window is used to realize the anti-pinch function of the vehicle window; The number detection module is used to respond to the detection command and detect whether the number at a preset position in the target storage area is the target number; The window learning module is used to allow window learning to be performed when the preset position number is determined to be the target number.

9. A vehicle, characterized in that, The vehicles include: Memory, used to store executable program code; A processor for calling and running the executable program code from the memory, causing the vehicle to perform the method as described in any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program that, when executed, implements the method as described in any one of claims 1 to 7.

Images