A method for recording a rear door opening and closing process

Abstract

This invention patent discloses a method for recording the opening and closing process of a rear door. By embedding data points within conventional software, and ensuring the software meets communication protocols and diagnostic specifications, it tracks the sender of the specified rear door opening / closing event and simultaneously records the event time. If the rear door is accidentally opened again, maintenance personnel can quickly retrieve key information, taking a crucial step in identifying and resolving the cause of the accidental opening.

Description

Technical Field

[0001] This invention belongs to the field of automotive parts technology, specifically relating to a method for recording the opening and closing process of a tailgate. Background Technology

[0002] Some vehicle models have experienced accidental opening of the tailgate when the opening conditions are not met, occurring during high-speed driving and when the vehicle is fully locked. Furthermore, after the problem occurs, users often open and close the tailgate again, causing the accidental opening message to be overwritten, making it impossible to trace the cause. Such issues have a significant negative impact on both user safety and the brand. Therefore, the design of recording the origin of commands during the opening and closing of the power tailgate is urgently needed. Summary of the Invention

[0003] The purpose of this invention is to record the sender of the electric tailgate opening and closing command, and at the same time, store it as a local triggering condition.

[0004] To achieve the above-mentioned objective, the present invention provides a method for recording the opening and closing process of a rear tailgate, characterized in that the trunk controller includes a FIFO and an EEPROM, and includes the following steps:

[0005] Step 1: Upon receiving the opening command from the BCM in the fully closed position, start timing. The luggage controller determines whether the luggage is opened according to the opening command. If yes, record source: bit_2 = 1; otherwise, proceed to step 2.

[0006] Step 2: The trunk controller determines whether the rear door lock is actually open. If it is, record source: bit_0 = 1; otherwise, proceed to step 5.

[0007] Step 3: The luggage controller determines whether the lock is opened according to the BCM's opening command. If yes, record source: bit_1 = 1; if no, record source: bit_1 = 0.

[0008] Step 4: The luggage controller writes the data to the FIFO according to the source value, and then executes Steps 5 and 6.

[0009] Arrangement 5: Set the luggage controller open source indicator.

[0010] Step Six: Refresh the FIFO, then proceed to Steps Seven and Eight.

[0011] Step 7: Determine if there is new data to be written to the FIFO. If yes, write it to the EEPROM; otherwise, end the process.

[0012] Step 8: The luggage controller determines whether to read the embedded data. If yes, it encapsulates the embedded data and sends it out via the data cable; otherwise, the process ends.

[0013] Furthermore, it also includes step nine, where the vehicle power-on initialization synchronizes the last written data point in the EEPROM to the FIFO, and then executes step five.

[0014] Furthermore, the source value is stored in local storage space.

[0015] Furthermore, the local storage space stores the opening and closing information of the rear door in the last 5 times, and the information follows the first-in-first-out principle and is constantly overwritten and updated.

[0016] This invention incorporates embedded data points in the software to ensure that the time of each electric tailgate opening and the initiator of the command are recorded. In the event of an accidental opening of the electric tailgate, the information can be accurately captured, providing crucial guidance for problem-solving. Attached Figure Description

[0017] To more clearly illustrate the technical solution of this invention, the logic in this example is shown below. The following figures only show some embodiments of the invention and should not be considered as limiting the scope. For those skilled in the art, other related figures can be obtained from these figures without any inventive effort.

[0018] Figure 1 This is a schematic diagram of the logic of the present invention. Detailed Implementation

[0019] The present invention will now be described in further detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of the present invention and not intended to limit it. Furthermore, it should be noted that, for ease of description, the accompanying drawings show only the parts relevant to the present invention and not all the logic.

[0020] like Figure 1 As shown, this invention patent embeds a tracking component within conventional software. Based on the software's compliance with communication protocols and diagnostic specifications, it tracks the sender of the specified event for the rear door opening / closing and simultaneously records the event time. If the rear door is accidentally opened again, it facilitates maintenance personnel in quickly retrieving crucial information, taking a critical step in identifying and resolving the cause of the accidental opening.

[0021] This invention provides a solution for adding embedded points to the software design of a luggage controller, which can record the sender of each rear door opening / closing command and the time of the event.

[0022] According to the architecture requirements, the only initiator of the tailgate opening command is the BCM. Theoretically, the BCM is not allowed to send an opening command to the trunk controller, whether the vehicle is locked or driving at high speed.

[0023] This invention incorporates embedded tracking in the software. Specifically, the logic for opening the power tailgate is as follows: the lock first receives the opening command, then the electric strut rotates under the drive command of the trunk controller, opening the tailgate. Therefore, obtaining the source of the unlocking command received by the lock from the locked state is the unique information recording the tailgate opening command. Theoretically, there are two scenarios for sending the opening command to the trunk controller: one is an opening command conforming to the architecture design originating from the BCM, and the other is an opening command not conforming to the architecture design originating from the trunk controller itself. The embedded tracking design addresses these two scenarios by reading messages, with the specific steps as follows:

[0024] Step 1: Upon receiving the opening command from the BCM in the fully closed position, start timing. The luggage controller determines whether the luggage is opened according to the opening command. If yes, record source: bit_2 = 1; otherwise, proceed to step 2.

[0025] Step 2: The trunk controller determines whether the rear door lock is actually open. If it is, record source: bit_0 = 1; otherwise, proceed to step 5.

[0026] Step 3: The luggage controller determines whether the lock is opened according to the BCM's opening command. If yes, record source: bit_1 = 1; if no, record source: bit_1 = 0, that is, manually open it.

[0027] Step 4: The luggage controller writes the data to the FIFO according to the source value, and then executes Steps 5 and 6.

[0028] Arrangement 5: Set the luggage controller open source indicator.

[0029] Step Six: Refresh the FIFO, then proceed to Steps Seven and Eight.

[0030] Step 7: Determine if there is new data to be written to the FIFO. If yes, write to the EEPROM; otherwise, end.

[0031] Step 8: The luggage controller determines whether to read the embedded data. If yes, it encapsulates the embedded data and sends it out via the data cable; otherwise, the process ends.

[0032] Step 9: When the vehicle is powered on and initialized, the last recorded data point written to the EEPROM is synchronized to the FIFO. Then, proceed with Step 5.

[0033] After the software is completed, it needs to be manually tested. One method is to send an open tailgate command through the BCM to confirm whether the accurate command information can be stored. Another method is to send an open tailgate command through the trunk controller itself to confirm whether the correct command information can be stored, further verifying the effectiveness of the software.

[0034] Because information related to the opening and closing of the tailgate is stored locally, and local storage capacity is limited, calculations show that the allowed storage capacity and durability can only accommodate the last 5 tailgate opening and closing records. Furthermore, this information follows a first-in, first-out (FIFO) principle, constantly being overwritten and updated. This necessitates that users report any problems to maintenance personnel as soon as possible.

[0035] The above software measures ensure that the time of each electric tailgate opening and the initiator of the command are recorded. Once the electric tailgate is accidentally opened, the information can be accurately captured, which plays a crucial guiding role in solving the problem.

[0036] Note that the above description is merely a preferred embodiment and the technical principles employed in this invention. Those skilled in the art will understand that this invention is not limited to the specific embodiments described herein, and various obvious changes, readjustments, and substitutions can be made without departing from the scope of protection of this invention. Therefore, although the invention has been described in detail through the above embodiments, it is not limited to these embodiments. Many other equivalent embodiments may be included without departing from the concept of this invention, and the scope of this invention is determined by the appended claims.

Claims

1. A method of recording an opening and closing process of a back door, characterized by, The luggage controller includes a FIFO and an EEPROM, and includes the following steps: Step 1: Upon receiving the opening command from the BCM in the fully closed position, the timer starts. The luggage controller determines whether the luggage is opened according to the opening command. If so, it records source: bit_2 = 1. If not, proceed to step two; Step 2: The trunk controller determines whether the rear door lock is actually open. If it is, record source: bit_0 = 1; otherwise, proceed to step 5. Step 3: The luggage controller determines whether the lock is opened according to the BCM's opening command. If yes, record source: bit_1 = 1; if no, record source: bit_1 = 0. Step 4: The luggage controller writes the data to the FIFO based on the source value, and then executes steps 5 and 6; Arrangement 5: Set the luggage compartment controller open position indicator; Step Six: Refresh the FIFO, then proceed to Steps Seven and Eight; Step 7: Check if there is new data to be written to the FIFO. If yes, write it to the EEPROM; otherwise, end the process. Step 8: The luggage controller determines whether to read the embedded data. If yes, it encapsulates the embedded data and sends it out via the data cable; otherwise, the process ends.

2. The method of claim 1, wherein, It also includes step nine, where the vehicle power-on initialization synchronizes the last written data point in the EEPROM to the FIFO, and then executes step five.

3. The method of claim 1, wherein, The source value is stored in local storage space.

4. The method of claim 1, wherein, The local storage space stores the opening and closing information of the rear door in the last 5 times, and the information follows the first-in-first-out principle and is constantly overwritten and updated.

Images