A body-in-white interface matching inspection method and system

Abstract

The application discloses a body-in-white interface matching inspection method and system, comprising collecting data required for inspection of the body-in-white and other systems, creating a standard database comprising a structure tree and physical three-dimensional data; making an interface matching table: performing a collision inspection, automatically obtaining matching information, and making the matching conditions between the body-in-white and other system parts into the interface matching table; making an interface matching inspection table: on the basis of the interface matching table, further verifying the interface matching conditions, recording the information of non-matching, and creating the interface matching inspection table. The application improves the development efficiency in the virtual design stage by automatically inspecting the body-in-white interface matching, avoids false detection, reduces the probability of subsequent real vehicle installation errors, thereby reducing the modification cost, and ensures that the automobile project can be put into production on time.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of automobile development simulation, and particularly relates to a body-in-white interface matching inspection method and system. BACKGROUND

[0002] In the design and development process of an automobile project, virtual design is often needed in a digital model, and problems are constantly checked and improved, so as to reduce problems in the subsequent real vehicle link, reduce modification costs, and ensure that the project is put into production on schedule.

[0003] The body-in-white is a load-bearing component of an automobile, and many parts of other systems (electronic systems, power systems, exterior systems, and interior systems) are installed on the body-in-white. The installation mode provides a standard part for other systems, and the body-in-white provides a corresponding standard part or mounting hole at the corresponding interface position. In the virtual design process, the matching conditions of each standard part are checked one by one by manual checking of the digital model, and then the problems found are recorded in a check table for modification and improvement of the part digital model.

[0004] However, the body-in-white has a large number of mounting points, and the method has low operation efficiency and cannot meet the requirements of short project cycles and fast pace. Moreover, because it is not intuitive, there may be incorrect checking, which leads to incorrect matching of the standard part, so that the real vehicle is produced according to the incorrect matching mode, which leads to incorrect installation of the real vehicle interface, affects the project cycle, and causes change costs. SUMMARY

[0005] In view of the problems described in the background, the purpose of the application is to provide an automatic body-in-white interface matching inspection method and system to improve development efficiency, reduce errors, and ensure on-time production.

[0006] To achieve the above purpose, in a first aspect, the body-in-white interface matching inspection method designed by the application comprises the following steps:

[0007] S1, collecting data required for inspection of the body-in-white and other systems, and creating a standard database including a structure tree and physical three-dimensional data;

[0008] S2, making an interface matching table: performing a collision check, automatically obtaining matching information, and making an interface matching table of the matching conditions between the body-in-white and other system parts;

[0009] S3, making an interface matching inspection table: further verifying the interface matching conditions on the basis of the interface matching table, recording the non-matching information, and creating an interface matching inspection table.

[0010] Preferably, in step S1, the other systems include one or more of an electronic system, a power system, an exterior system, and an interior system.

[0011] Preferably, in step S1, the establishment of the standard database is based on existing physical three-dimensional data of real vehicles.

[0012] As a preferred embodiment, step S2 includes:

[0013] S21, Create an interface matching table: The interface matching table includes three columns of information: the name of the required part, the name of the interface part, and the collision value; where:

[0014] Required component name: refers to the name of the component in other systems;

[0015] Interface component name: refers to the name of the corresponding interface component on the body-in-white;

[0016] Collision value: A numerical value or indicator used during collision checks to identify whether there is a conflict between two parts;

[0017] S22, The collision check module of the simulation software is called to automatically check the original data and generate matching information;

[0018] S23, For each row of matching information, first determine whether the parts on other systems are standard parts. If not, continue to check the next row. If they are, record the part names on other systems in the "Required Part Name" column of the interface matching table, record the part names on the body-in-white in the "Interface Part Name" column, and then proceed to the next step.

[0019] S24. If the parts in other systems are non-standard parts, record the part names in the "Required Part Name" column and the corresponding collision values ​​in the "Collision Value" column.

[0020] S25. Repeat steps S23 to S24 to judge and record each line in the matching information until all lines are checked, and finally obtain the complete interface matching table.

[0021] Preferably, in step S22, the collision inspection module can automatically identify standard parts and non-standard parts.

[0022] Further preferably, when creating the data, the standard part uses a specific character as the beginning of the standard part name; the part is identified as a standard part by recognizing whether the beginning of the part name contains the set specific character.

[0023] As another preferred embodiment, step S3 includes:

[0024] S31, Create an interface matching check table: The interface matching check table includes five columns of information: Required part name, Interface part name, Collision value, Interface part name in the corresponding interface matching table, and Collision value in the corresponding interface matching table.

[0025] Required component name: refers to the name of the component in other systems;

[0026] Interface component name: refers to the name of the corresponding interface component on the body-in-white;

[0027] Collision value: A numerical value or indicator used during collision checks to identify whether there is a conflict between two parts;

[0028] The corresponding interface component name in the interface matching table is the name of the interface component recorded in the interface matching table, which is used to compare it with the currently checked component.

[0029] Collision value in the corresponding interface matching table: This is the collision value recorded in the interface matching table, which is also used for comparison;

[0030] S32, call the collision check module of the simulation software to automatically detect the data that needs to be checked and generate new matching information;

[0031] S33, for each line of the matching information:

[0032] S331, Determine whether parts in other systems are standard parts.

[0033] If not, continue checking the next line;

[0034] If so, record the part names from other systems in the "Required Part Name" column of the interface matching checklist, and proceed to the next step;

[0035] S332, Check whether the interface parts of the body-in-white are also standard parts.

[0036] If so, record the part names on the body-in-white in the "Interface Part Names" column;

[0037] If not, record the corresponding collision value in the "Collision Value" column;

[0038] Next step;

[0039] S34, retrieve the part name recorded in S331 from the "Required Part Name" column of the interface matching table.

[0040] S341, if the corresponding part name is found in the "Required Part Name" column of the interface matching table, then further search for the "Interface Part Name" or "Collision Value" of the corresponding row of the interface matching table for the required part name.

[0041] S342, compare the retrieved "interface part name" or "collision value" with the interface part name of the body-in-white in the new matching information:

[0042] If the part names are the same, ignore them; if they are different, record the retrieved part names in the "Interface Part Name in Corresponding Interface Matching Table" column.

[0043] If the values ​​are equal, ignore them; if they are not equal, record the retrieved values ​​in the "Collision Values ​​in Corresponding Interface Matching Table" column.

[0044] S35. Repeat steps S33 to S34 to judge, retrieve, compare and record each line in the new matching information until all lines are checked and a complete interface matching check table is obtained.

[0045] Secondly, the body-in-white interface matching inspection system designed in this invention includes:

[0046] The data collection module is used to collect data from the body-in-white and other systems, and to create a standard database;

[0047] The collision detection module is used to perform collision checks on parts and generate matching information;

[0048] The interface matching table generation module is used to create an interface matching table containing the name of the required part, the name of the interface part, and the collision value.

[0049] The interface matching checklist generation module is used to create an interface matching checklist that includes the part name of the required part, the part name of the interface part, the collision value, the corresponding part name of the interface part in the interface matching table, and the collision value in the corresponding interface matching table.

[0050] Preferably, the data collection module collects data from other systems, including data from one or more systems such as electronic systems, power systems, exterior systems, and interior systems.

[0051] Preferably, the data collection module creates a standard database based on existing physical 3D data of real vehicles.

[0052] Preferably, the collision detection module can automatically identify standard parts and non-standard parts.

[0053] In a further preferred embodiment, when generating data, the standard part uses a specific character as the beginning of the standard part name; the collision detection module identifies whether a part is a standard part by recognizing whether the beginning of the part name contains the set specific character.

[0054] The beneficial effects of this invention are: by automating the inspection of the interface matching of the body-in-white, this invention improves the development efficiency of the virtual design stage, avoids false detection, reduces the probability of subsequent installation errors in actual vehicles, thereby reducing modification costs and ensuring that the automotive project can be put into production on time.

[0055] This invention achieves systematic and automated interface matching checks by constructing a standard database and generating interface matching tables and checklists, effectively solving the problems of low efficiency and frequent errors in traditional methods. It not only saves time and costs but also improves the overall reliability and production efficiency of projects, and has significant application value for body-in-white design in the automotive manufacturing process.

[0056] This invention improves development efficiency in the virtual design phase, reduces errors from manual inspection, lowers the probability of errors in actual vehicle interface installation, reduces modification costs, and ensures that automotive projects can be put into production on time. Detailed Implementation

[0057] The following are some optional embodiments of the present invention to further describe the technical solutions (including preferred technical solutions) of the present invention in detail. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. All other embodiments obtained by those skilled in the art based on the embodiments of the present invention without creative effort are within the scope of protection of the present invention.

[0058] The body-in-white interface matching inspection method designed in this invention includes the following steps:

[0059] S1: Data Collection and Setup

[0060] Collect data that needs to be checked on the body-in-white and other systems, and create a standard database that includes a tree structure and physical 3D data.

[0061] In some alternative embodiments of the present invention, other systems include one or more of electronic systems, power systems, exterior systems, and interior systems.

[0062] In some alternative embodiments of the present invention, the standard database is established based on existing physical 3D data of real vehicles.

[0063] S2: Create an interface matching table

[0064] The system performs collision checks, automatically acquires matching information, and creates an interface matching table that shows the matching status between the body-in-white and other system parts.

[0065] S21, Create an interface matching table: The interface matching table includes three columns of information: the name of the required part, the name of the interface part, and the collision value; where:

[0066] Required component name: refers to the name of the component in other systems;

[0067] Interface component name: refers to the name of the corresponding interface component on the body-in-white;

[0068] Collision value: A numerical value or indicator used during collision checks to identify whether there is a conflict between two parts;

[0069] S22, The collision check module of the simulation software is called to automatically check the original data and generate matching information;

[0070] In some optional embodiments of the present invention, the collision check module of CATIA software is used to automatically check the raw data. This check is to detect potential conflicts or mismatches between the body-in-white and other system parts. After the check is completed, the CATIA software generates a list containing conflict information; although the software refers to it as a "conflict list," it actually refers to "matching information" here.

[0071] The operation process of CATIA software is as follows:

[0072] Identify and click the collision check module → Select the "Select all except" option → Select the body-in-white model → Click Apply → Generate a collision list.

[0073] The collision detection module can automatically identify standard and non-standard parts.

[0074] In some optional embodiments of the present invention, when generating data, the standard part uses a specific character as the beginning of the standard part name; whether the part is a standard part is determined by identifying whether the beginning of the part name contains the set specific character.

[0075] S23, For each row of matching information, first determine whether the parts on other systems are standard parts. If not, continue to check the next row. If they are, record the part names on other systems in the "Required Part Name" column of the interface matching table, record the part names on the body-in-white in the "Interface Part Name" column, and then proceed to the next step.

[0076] S24. If the parts in other systems are non-standard parts, record the part names in the "Required Part Name" column and the corresponding collision values ​​in the "Collision Value" column.

[0077] In CATIA software, starting from the first line of the conflict list, it checks whether the part name of Product 2 is a standard part: standard parts are usually named starting with Q or F, while non-standard parts start with other letters.

[0078] If Product 2 (i.e., the part on other systems) is a standard part, then check Product 1 (i.e., the interface part of the body-in-white); otherwise, continue to the next line.

[0079] If product 1 is a standard part, write the part name of product 2 into the "Required Part Name" column of the interface matching table, and write the part name of product 1 into the "Interface Part Name" column.

[0080] If product 1 is not a standard part, write the part name of product 2 into the "Required Part Name" column and write the collision value into the "Collision Value" column.

[0081] S25. Repeat steps S23 to S24 to judge and record each line in the matching information until all lines are checked, and finally obtain the complete interface matching table.

[0082] required part name interface part name collision value Q033014 Q011377 F600095260 Q011306-0514 f640043j-g0103 Q011434-0512 F2892380 -1.89

[0083] S3: Create an interface matching checklist

[0084] Based on the interface matching table, further verify the interface matching status, record the information of mismatches, and create an interface matching check table.

[0085] S31, Create an interface matching check table: The interface matching check table includes five columns of information: Required part name, Interface part name, Collision value, Interface part name in the corresponding interface matching table, and Collision value in the corresponding interface matching table.

[0086] Required component name: refers to the name of the component in other systems;

[0087] Interface component name: refers to the name of the corresponding interface component on the body-in-white;

[0088] Collision value: A numerical value or indicator used during collision checks to identify whether there is a conflict between two parts;

[0089] The corresponding interface component name in the interface matching table is the name of the interface component recorded in the interface matching table, which is used to compare it with the currently checked component.

[0090] Collision value in the corresponding interface matching table: This is the collision value recorded in the interface matching table, which is also used for comparison;

[0091] S32, call the collision check module of the simulation software to automatically detect the data that needs to be checked and generate new matching information;

[0092] In some optional embodiments of the present invention, the collision check module of CATIA software is used to automatically check the raw data. This check is to detect potential conflicts or mismatches between the body-in-white and other system parts. After the check is completed, the CATIA software generates a list containing conflict information; although the software refers to it as a "conflict list," it actually refers to "matching information" here.

[0093] The operation process of CATIA software is as follows:

[0094] Identify and click the collision check module → Select the "Select all except" option → Select the body-in-white model → Click Apply → Generate a collision list.

[0095] The collision detection module can automatically identify standard and non-standard parts.

[0096] S33, for each line of the matching information:

[0097] S331, Determine whether parts in other systems are standard parts.

[0098] If not, continue checking the next line;

[0099] If so, record the part names from other systems in the "Required Part Name" column of the interface matching checklist, and proceed to the next step;

[0100] S332, Check whether the interface parts of the body-in-white are also standard parts.

[0101] If so, record the part names on the body-in-white in the "Interface Part Names" column;

[0102] If not, record the corresponding collision value in the "Collision Value" column;

[0103] Next step;

[0104] S34, retrieve the part name recorded in S331 from the "Required Part Name" column of the interface matching table.

[0105] S341, if the corresponding part name is found in the "Required Part Name" column of the interface matching table, then further search for the "Interface Part Name" or "Collision Value" of the corresponding row of the interface matching table for the required part name.

[0106] S342, compare the retrieved "interface part name" or "collision value" with the interface part name of the body-in-white in the new matching information:

[0107] If the part names are the same, ignore them; if they are different, record the retrieved part names in the "Interface Part Name in Corresponding Interface Matching Table" column.

[0108] If the values ​​are equal, ignore them; if they are not equal, record the retrieved values ​​in the "Collision Values ​​in Corresponding Interface Matching Table" column.

[0109] S35. Repeat steps S33 to S34 to judge, retrieve, compare and record each line in the new matching information until all lines are checked and a complete interface matching check table is obtained.

[0110]

[0111] The interface matching table in this invention is created to record the matching status between the body-in-white and other system parts. It provides basic matching information, including which parts are required components, which are interface components, and their matching status (collision value). The interface matching checklist is created based on the interface matching table for further verification and inspection. Its purpose is to discover and record mismatch issues, providing specific data support for design corrections.

[0112] It will be readily understood by those skilled in the art that the above are merely preferred embodiments of the present invention and are not intended to limit the present invention. Any modifications, combinations, substitutions, improvements, etc., made under the spirit and principles of the present invention are included within the protection scope of the present invention.

Claims

1. A method for checking interface matching of a body-in-white, characterized in that, Includes the following steps: S1, collect data that needs to be checked on the body-in-white and other systems, and create a standard database including a tree structure and physical 3D data; S2, Create an interface matching table: Perform collision checks, automatically obtain matching information, and create an interface matching table showing the matching status between the body-in-white and other system parts. Step S2 includes: S21, Create an interface matching table: The interface matching table includes three columns of information: the name of the required part, the name of the interface part, and the collision value; where: Required component name: refers to the name of the component in other systems; Interface component name: refers to the name of the corresponding interface component on the body-in-white; Collision value: A numerical value or indicator used during collision checks to identify whether there is a conflict between two parts; S22, The collision check module of the simulation software is called to automatically check the original data and generate matching information; S23, For each row of matching information, first determine whether the parts on other systems are standard parts. If not, continue to check the next row. If they are, record the part names on other systems in the "Required Part Name" column of the interface matching table, record the part names on the body-in-white in the "Interface Part Name" column, and then proceed to the next step. S24, determine whether the interface parts on the body-in-white are standard parts. If the interface parts on the body-in-white are non-standard parts, record the part names of other systems in the "Required Part Name" column and record the corresponding collision values ​​in the "Collision Value" column. S25, Repeat steps S23 to S24 to judge and record each line in the matching information until all lines have been checked, and finally obtain the complete interface matching table. S3, Create an interface matching checklist: Based on the interface matching table, further verify the interface matching status, record the information of mismatches, and create an interface matching checklist.

2. The method for checking interface matching of body-in-white according to claim 1, characterized in that: In step S1, other systems include one or more of the following: electronic system, powertrain system, exterior system, and interior system.

3. The method for checking the interface matching of a body-in-white according to claim 1 or 2, characterized in that: In step S1, the establishment of the standard database is based on existing physical 3D data of real vehicles.

4. The method for checking interface matching of body-in-white according to claim 1, characterized in that: In step S22, the collision inspection module can automatically identify standard parts and non-standard parts.

5. The method for checking interface matching of body-in-white according to claim 4, characterized in that: When creating data, standard parts use specific characters as the beginning of their part names; whether a part is a standard part is determined by identifying whether the beginning of the part name contains the specified characters.

6. The method for checking the interface matching of a body-in-white according to claim 1 or 4, characterized in that: Step S3 includes: S31, Create an interface matching check table: The interface matching check table includes five columns of information: Required part name, Interface part name, Collision value, Interface part name in the corresponding interface matching table, and Collision value in the corresponding interface matching table. Required component name: refers to the name of the component in other systems; Interface component name: refers to the name of the corresponding interface component on the body-in-white; Collision value: A numerical value or indicator used during collision checks to identify whether there is a conflict between two parts; The corresponding interface component name in the interface matching table is the name of the interface component recorded in the interface matching table, which is used to compare it with the currently checked component. Collision value in the corresponding interface matching table: This is the collision value recorded in the interface matching table, which is also used for comparison; S32, call the collision check module of the simulation software to automatically detect the data that needs to be checked and generate new matching information; S33, for each line of the matching information: S331, Determine whether parts in other systems are standard parts. If not, continue checking the next line; If so, record the part names from other systems in the "Required Part Name" column of the interface matching check table, and proceed to the next step; S332, Check whether the interface parts of the body-in-white are also standard parts. If so, record the part names on the body-in-white in the "Interface Part Names" column; If not, record the corresponding collision value in the "Collision Value" column; Next step; S34, retrieve the part name recorded in S331 from the "Required Part Name" column of the interface matching table. S341, if the corresponding part name is found in the "Required Part Name" column of the interface matching table, then further search for the "Interface Part Name" or "Collision Value" of the corresponding row of the interface matching table for the required part name. S342, compare the retrieved "interface part name" or "collision value" with the interface part name of the body-in-white in the new matching information: If the part names are the same, ignore them; if they are different, record the retrieved part names in the "Interface Part Name in Corresponding Interface Matching Table" column. If the values ​​are equal, ignore them; if they are not equal, record the retrieved values ​​in the "Collision Values ​​in Corresponding Interface Matching Table" column. S35. Repeat steps S33 to S34 to judge, retrieve, compare and record each line in the new matching information until all lines are checked and a complete interface matching check table is obtained.

7. A body-in-white interface matching inspection system applying the inspection method of any one of claims 1 to 6, characterized in that, include: The data collection module is used to collect data from the body-in-white and other systems, and to create a standard database; The collision check module is used for collision checks of parts and generates matching information. The collision check module can automatically identify standard parts and non-standard parts. When generating data, standard parts use a specific character as the beginning of the standard part name. The collision check module distinguishes whether a part is a standard part by recognizing whether the beginning of the part name contains the set specific character. The interface matching table generation module is used to create an interface matching table containing the name of the required part, the name of the interface part, and the collision value. The interface matching checklist generation module is used to create an interface matching checklist that includes the part name of the required part, the part name of the interface part, the collision value, the corresponding part name of the interface part in the interface matching table, and the collision value in the corresponding interface matching table.

8. The body-in-white interface matching inspection system according to claim 7, characterized in that: The data collection module collects data from other systems, including one or more systems such as electronic systems, powertrain systems, exterior systems, and interior systems; the data collection module creates a standard database based on existing physical 3D data of real vehicles.

Images