Intelligent tightening data acquisition method based on part identification code

Abstract

The invention discloses an intelligent tightening data acquisition method based on a part identification code, and relates to the technical field of data acquisition. According to the method, a tightening result is obtained by scanning a part identification code at a sub-packaging station, a sub-packaging tightening data packet is generated, and a sub-packaging timestamp is recorded; and the same part identification code and the VIN code of the whole vehicle are scanned again at the main line assembly station, compliance verification is carried out on the part identification code based on the BOM list corresponding to the VIN code, only the compliance part is allowed to enter the main line data cache region, and the assembly timestamp is recorded. And through a time window matching algorithm, a matching interval is constructed according to the average transfer time length and the standard deviation of the part types between sub-packaging and assembling, sub-packaging and assembling data are automatically matched, and data verification is executed. And after matching succeeds, binding the subpackage tightening data with the VIN code of the whole vehicle, if a multi-version record exists, executing version control and generating a version chain, and finally uploading the tightening associated data of the whole vehicle to a tightening server.

Description

TECHNICAL FIELD

[0001] The present application relates to the field of data collection, in particular to an intelligent tightening data collection method based on part identification code. BACKGROUND

[0002] Tightening data is a key information that needs to be collected in a digital and intelligent factory, and plays a key role in subsequent quality problem investigation and after-sales quality problem tracing. Different vehicle factories use different data collection technologies. Currently, the data collection technologies widely used in the industry mainly include scanning the vehicle body VIN by a code scanning gun and uploading the VIN on the vehicle panel by a code scanning gun. Since some parts need to be packaged away from the production line and then transported to the line side for assembly, the tightening data in the packaging process cannot be bound to the vehicle VIN because there is no vehicle VIN code in the packaging area. Therefore, an intelligent tightening data collection technology based on part identification code needs to be developed to bind the tightening data in the packaging process to the vehicle VIN. SUMMARY

[0003] The purpose of the present application is to provide an intelligent tightening data collection method based on part identification code, which aims to solve the problem that the tightening data in the packaging process cannot be bound to the vehicle VIN. Through the present application, the tightening data in the packaging process can be bound to the vehicle VIN, the tightening data of the parts in the packaging area can be collected, and the traceability of the tightening data can be ensured.

[0004] The present application provides the following scheme:

[0005] According to one aspect of the present application, an intelligent tightening data collection method based on part identification code is provided, comprising:

[0006] At the packaging station, the part identification code is collected by a code scanning gun, and the tightening operation is performed on the part by a tightening machine controller to obtain the tightening result;

[0007] The part identification code and the tightening result form a packaging tightening data package, which is stored in the packaging data cache area of the all-in-one machine and records the packaging timestamp;

[0008] At the main line assembly station, the same part identification code and vehicle VIN code are collected again by a code scanning gun, and the all-in-one machine queries the corresponding BOM list according to the vehicle VIN code to verify the compliance of the part identification code;

[0009] When the BOM verification is passed, the part identification code and the corresponding vehicle VIN code are written into the main line data cache area of the all-in-one machine, and the assembly timestamp is recorded;

[0010] The all-in-one machine performs a time window matching algorithm between the packaging data cache area and the main line data cache area based on the part identification code, and performs consistency verification on the matching result;

[0011] When the matching is successful, the whole vehicle VIN code is bound with the disassembled tightening data, version control is performed if there are multiple version records, whole vehicle tightening association data is formed, and the data is uploaded to the tightening server.

[0012] Preferably, the compliance verification is implemented through bitmap matching, and the bitmap matching comprises:

[0013] A part identification code bitmap is established for the BOM list corresponding to the whole vehicle VIN code, each bit corresponds to whether a part exists in the list, and a bit value of 1 indicates that the part type exists in the BOM list, and a bit value of 0 indicates that the part type does not exist in the BOM list;

[0014] The part type code of the part identification code obtained by scanning is extracted, the corresponding bit in the bitmap is located, and it is judged whether the part belongs to the assembly part set of the whole vehicle.

[0015] Preferably, when the BOM verification fails, the following steps are performed:

[0016] Error prompt information is displayed on the operation terminal, and the error prompt information includes the scanned part identification code, the corresponding whole vehicle VIN code, and the correct part identification code list;

[0017] The data writing function of the current station is locked to prevent error data from entering the main line data buffer area;

[0018] The BOM verification failure event is recorded to an exception database, and the record content includes a timestamp, a station identifier, an operator identifier, a part identification code, a whole vehicle VIN code, and a failure reason.

[0019] Preferably, the execution time window matching algorithm comprises:

[0020] The average transit time and the standard deviation of the part type corresponding to the part identification code from disassembly to assembly are calculated according to historical data;

[0021] An effective matching time window is set according to the disassembly timestamp, and the relationship between the assembly timestamp and the time window is judged.

[0022] Preferably, if the assembly timestamp falls within the time window, automatic matching is performed; if the assembly timestamp exceeds the time window but is less than a preset time threshold, matching is performed after manual confirmation is prompted; if the assembly timestamp exceeds the preset time threshold, it is marked as an exception and an exception handling process is triggered.

[0023] Preferably, the consistency verification of the matching result comprises:

[0024] Part code format verification: Verify the legality of the encoding structure of the part identification code, including character length range check, character type verification, and check bit calculation verification;

[0025] Data integrity verification: Verify the existence and validity of required fields in the sub-package tightening data packet, including the integrity of tightening torque value, tightening angle value, tightening result determination and timestamp;

[0026] Workstation correspondence verification: Based on the preset process routing table, verify that there is a valid assembly path relationship between the sub-assembly workstation identifier and the main line workstation identifier.

[0027] Preferably, the implementation of version control includes:

[0028] For multiple tightening records with the same part identification code, assign incremental version numbers in chronological order;

[0029] Select the record with the highest version number and bind it to the vehicle's VIN code;

[0030] All version records are uploaded to the tightening server as a version chain.

[0031] According to a second aspect of the present invention, an intelligent tightening data acquisition system based on part identification codes is provided, comprising:

[0032] The tightening result acquisition module is used to collect the part identification code by a barcode scanner at the sub-assembly station, and the tightening machine controller performs tightening operation on the parts to obtain the tightening result;

[0033] The sub-assembly timestamp acquisition module is used to combine the part identification code and tightening result to form a sub-assembly tightening data packet, store it in the sub-assembly data cache area of ​​the all-in-one machine and record the sub-assembly timestamp;

[0034] The BOM verification module is used at the main assembly station to collect the same part identification code and vehicle VIN code again by scanning the barcode. The all-in-one machine queries the corresponding BOM list based on the vehicle VIN code and performs compliance verification on the part identification code.

[0035] The assembly timestamp acquisition module writes the part identification code and its corresponding vehicle VIN code into the main data cache area of ​​the integrated machine when the BOM verification passes, and records the assembly timestamp.

[0036] The matching and verification module is used by the all-in-one machine to perform a time window matching algorithm between the sub-assembly data cache area and the main data cache area based on the part identification code, and to verify the consistency of the matching results.

[0037] The data upload module is used to bind the vehicle VIN code with the sub-assembly tightening data when the match is successful. If there are multiple version records, version control is performed to form the vehicle tightening association data and upload it to the tightening server.

[0038] According to three aspects of the present invention, an electronic device is provided, comprising: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0039] The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of an intelligent tightening data acquisition method based on part identification codes.

[0040] According to four aspects of the present invention, a computer-readable storage medium is provided, comprising: storing a computer program executable by an electronic device, wherein when the computer program is run on the electronic device, the electronic device performs the steps of a smart tightening data acquisition method based on a part identification code.

[0041] The above solution achieves the following beneficial technical effects:

[0042] This application utilizes part identification codes to achieve automatic data matching between the sub-assembly and mainline assembly stations, avoiding association errors caused by manual data entry and improving the accuracy of vehicle quality traceability.

[0043] This application uses a fast BOM verification mechanism based on bitmap matching, which can determine whether a part belongs to a specified vehicle configuration in milliseconds, significantly reducing the rate of incorrect assembly.

[0044] This application establishes a dynamic time window by introducing average transfer time and standard deviation, thereby improving the stability and robustness of cross-workstation data matching and reducing anomaly misjudgment. Attached Figure Description

[0045] Figure 1 This is a flowchart of an intelligent tightening data acquisition method based on part identification codes provided by one or more embodiments of the present invention.

[0046] Figure 2 This is a structural diagram of an intelligent tightening data acquisition system based on part identification codes provided by one or more embodiments of the present invention.

[0047] Figure 3 This is a structural block diagram of an electronic device for an intelligent tightening data acquisition method based on part identification codes, provided by one or more embodiments of the present invention. Detailed Implementation

[0048] The technical solution of the present invention will now be clearly and completely described with reference to the accompanying drawings. Obviously, the described embodiments are only some, not all, of the embodiments of the present invention. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0049] Figure 1 This is a flowchart of an intelligent tightening data acquisition method based on part identification codes provided by one or more embodiments of the present invention.

[0050] like Figure 1 The intelligent tightening data acquisition method based on part identification codes shown includes:

[0051] S1. At the sub-assembly station, the part identification code is collected by the barcode scanner, and the tightening machine controller performs the tightening operation on the parts to obtain the tightening result;

[0052] S2. Combine the part identification code and tightening result to form a sub-assembly and tightening data package, store it in the sub-assembly data cache area of ​​the all-in-one machine and record the sub-assembly timestamp;

[0053] S3. At the main assembly station, the same part identification code and vehicle VIN code are collected again by scanning the barcode. The all-in-one machine queries the corresponding BOM list based on the vehicle VIN code and performs compliance verification on the part identification code.

[0054] S4. When the BOM verification passes, write the part identification code and its corresponding vehicle VIN code into the main data cache area of ​​the integrated machine, and record the assembly timestamp.

[0055] S5: The all-in-one machine performs a time window matching algorithm between the sub-assembly data cache area and the main data cache area based on the part identification code, and performs consistency verification on the matching results.

[0056] S6. Upon successful matching, the vehicle VIN code is bound to the sub-assembly tightening data. If multiple version records exist, version control is executed to form the vehicle tightening association data, which is then uploaded to the tightening server.

[0057] In this embodiment, the compliance verification is implemented through bitmap matching, which includes:

[0058] Establish a part identification code bitmap for the BOM list corresponding to the VIN code of the whole vehicle. Each bit corresponds to whether a part exists in the list. A bit value of 1 indicates that the part type exists in the BOM list, and a bit value of 0 indicates that it does not exist.

[0059] The part type code is extracted by scanning the part identification code, the corresponding bit is located in the bit map, and it is determined whether the part belongs to the assembly parts set of the whole vehicle.

[0060] Specifically, after the main workstation scans and obtains the vehicle's VIN code, the integrated machine queries the corresponding BOM (Bill of Materials) list based on the VIN code. The BOM list includes the part identification codes and type information of all components to be assembled in the vehicle. The part types of all part identification codes in the BOM list are numbered or mapped, and a bit is allocated in memory for each part type to construct a part identification code bitmap. If a part type exists in the BOM list, the corresponding bit value is set to 1; otherwise, the corresponding bit value is set to 0.

[0061] The barcode scanner scans the part identification code of the component to be assembled. The integrated machine extracts the part type code from the part identification code, which is used to locate the corresponding bit in the bitmap. Based on the extracted part type code, the corresponding bit is located in the bitmap. If the bit value is 1, it indicates that the part type belongs to the vehicle BOM list, and the verification passes. When the verification passes, the part identification code and the vehicle VIN code are written to the main data cache, and the assembly timestamp is recorded.

[0062] In this embodiment, when the BOM verification fails, the following steps are performed:

[0063] The operating terminal displays an error message, which includes the scanned part identification code, the corresponding vehicle VIN code, and a list of correct part identification codes.

[0064] Lock the data write function of the current workstation to prevent erroneous data from entering the main data cache;

[0065] BOM verification failure events are recorded in the exception database. The record includes timestamp, workstation identifier, operator identifier, part identifier code, vehicle VIN code, and reason for failure.

[0066] Specifically, when the BOM verification fails, the integrated machine will automatically display an error message box. The error message includes the scanned part identification code, the corresponding vehicle VIN code, and the correct BOM list information for the incorrect part identification code. The list shows which vehicle model and assembly location the part should belong to. The operator checks the part information according to the prompts to ensure that errors are detected and corrected in a timely manner.

[0067] Simultaneously, the data writing function for the current workstation is automatically disabled when the BOM verification fails. With writing disabled, erroneous data cannot be written to the main data buffer, ensuring that invalid or incorrect part data is not processed or uploaded, thus preventing contamination of subsequent assembly data. This locking function can be automatically released after operator confirmation and correction of the error, or unlocked via the user interface after manual confirmation.

[0068] Subsequently, the all-in-one machine will record the BOM verification failure event to the exception database. The event record includes the following information: event timestamp, workstation identifier, operator identifier, part identifier code, vehicle VIN code, and the reason for failure, such as "part identifier code does not match the BOM list" or "part does not belong to this vehicle model".

[0069] In this embodiment, the execution time window matching algorithm includes:

[0070] Calculate the average transit time and standard deviation from sub-packaging to assembly for the part type corresponding to the part identification code based on historical data;

[0071] Set an effective matching time window based on the disassembly timestamp, and determine the relationship between the assembly timestamp and the time window.

[0072] In this embodiment, if the assembly timestamp falls within the time window, automatic matching is performed; if the assembly timestamp exceeds the time window but is less than the preset duration threshold, manual confirmation is prompted before matching is performed; if the assembly timestamp exceeds the preset duration threshold, it is marked as abnormal and an abnormal handling process is triggered.

[0073] Specifically, the disassembly timestamps and corresponding assembly timestamps for multiple part types are extracted from historical production data. For the same part type, the transfer time for each production run is calculated, which is the assembly timestamp minus the disassembly timestamp. The transfer times for all parts of this type are then statistically analyzed to calculate the average transfer time. and standard deviation .

[0074] Based on the obtained records, the timestamps are packaged. Based on historical statistics, a matching time window is calculated for the current part type. ,in The statistical distribution can cover 99.7% of the normal processing time, ensuring both matching accuracy and sufficient error tolerance.

[0075] After scanning the same part identification code at the main assembly station, the system records the assembly timestamp. . judge Relationship with the time window:

[0076] like If the condition falls within the time window, it is considered that the matching condition is met, and the consistency verification phase begins.

[0077] like Exceeding the time window but not exceeding the preset duration threshold The system will then display a prompt message asking the operator to confirm whether manual matching is required.

[0078] like Exceed If the match is deemed abnormal, the system will record the reason for the abnormality and refuse to match automatically.

[0079] As an optional implementation, when a match is successful, the system will record the transit time. Add it to the statistics for this part type. Recalculate periodically thereafter, or when the data reaches a set quantity. and This enables automatic learning and updating of the time window, making the matching algorithm more closely aligned with the actual production line rhythm.

[0080] In this embodiment, the consistency verification of the matching results includes:

[0081] Part code format verification: Verify the legality of the encoding structure of the part identification code, including character length range check, character type verification, and check bit calculation verification;

[0082] Data integrity verification: Verify the existence and validity of required fields in the sub-package tightening data packet, including the integrity of tightening torque value, tightening angle value, tightening result determination and timestamp;

[0083] Workstation correspondence verification: Based on the preset process routing table, verify that there is a valid assembly path relationship between the sub-assembly workstation identifier and the main line workstation identifier.

[0084] Specifically, based on the enterprise coding specifications or supply chain coding rules, the valid format definition of the part identification code is obtained, including the allowed character length range, character type requirements, and the location of special fields. During length verification, it is determined whether the length of the scanned part identification code is within the specified range; if not, the format is deemed invalid. During character type verification, the character type at each position is verified according to the coding rules, such as the first character being a letter and the last three being numbers. During check digit verification, the check digits of the part identification code are recalculated according to a preset algorithm, such as Mod-11, and compared with the scan result; if they do not match, the part code format is deemed invalid.

[0085] Read the tightening data packet corresponding to the part identification code from the sub-assembly data cache and confirm that it contains the required fields: tightening torque value, tightening angle value, tightening result judgment, and sub-assembly timestamp. Then, verify the validity of these key fields, such as: whether the tightening torque value is within the process range, whether the tightening angle is a positive number, whether the tightening result judgment is an enumerated value allowed by the system, and whether the timestamp is valid and has not been tampered with.

[0086] Based on the vehicle model and current production batch, the system queries the preset process routing table in the backend. This table defines which sub-assembly stations each part should be processed at, which main line stations it should be assembled at, and the legal process paths between sub-assembly stations and main line stations. During verification, the system reads the sub-assembly station identifiers from the sub-assembly data and the assembly station identifiers recorded during scanning at the main line end, and determines whether there is a corresponding relationship between the two. If the station combination exists in the process routing table, the verification passes; if it does not exist, such as a part that should be sub-assembled at station A appearing at main line station C, it is considered abnormal.

[0087] In this embodiment, the execution of version control includes:

[0088] For multiple tightening records with the same part identification code, assign incremental version numbers in chronological order;

[0089] Select the record with the highest version number and bind it to the vehicle's VIN code;

[0090] All version records are uploaded to the tightening server as a version chain.

[0091] Specifically, when the sub-assembly station scans the same part identification code multiple times or repeatedly tightens the same part, multiple tightening data packets will be generated for that part in the sub-assembly data buffer. These data packets are clustered based on the part identification code to identify all tightening records belonging to the same part. Subsequently, multiple tightening records under the same part identification code are sorted from earliest to latest by the sub-assembly timestamp and assigned incremental version numbers. For example, the earliest generated record is assigned a version number... The next record will be assigned a version number. And so on, until the latest record is assigned a version number. .

[0092] When the main assembly station scans the same part identification code and passes the time window matching and consistency verification, the tightening record with the largest version number under that part identification code is automatically selected as the final valid data. Subsequently, all tightening records under that part identification code are formed into a version chain in version number order, and the tightening record with the largest version number is bound to the vehicle VIN code as the final tightening result of the vehicle assembly record. At the same time, the complete version chain is uploaded to the tightening server for quality traceability, rework analysis, and data auditing.

[0093] Figure 2 This is a structural diagram of an intelligent tightening data acquisition system based on part identification codes provided by one or more embodiments of the present invention.

[0094] like Figure 2 The intelligent tightening data acquisition system based on part identification codes shown includes:

[0095] The tightening result acquisition module is used to collect the part identification code by a barcode scanner at the sub-assembly station, and the tightening machine controller performs tightening operation on the parts to obtain the tightening result;

[0096] The sub-assembly timestamp acquisition module is used to combine the part identification code and tightening result to form a sub-assembly tightening data packet, store it in the sub-assembly data cache area of ​​the all-in-one machine and record the sub-assembly timestamp;

[0097] The BOM verification module is used at the main assembly station to collect the same part identification code and vehicle VIN code again by scanning the barcode. The all-in-one machine queries the corresponding BOM list based on the vehicle VIN code and performs compliance verification on the part identification code.

[0098] The assembly timestamp acquisition module writes the part identification code and its corresponding vehicle VIN code into the main data cache area of ​​the integrated machine when the BOM verification passes, and records the assembly timestamp.

[0099] The matching and verification module is used by the all-in-one machine to perform a time window matching algorithm between the sub-assembly data cache area and the main data cache area based on the part identification code, and to verify the consistency of the matching results.

[0100] The data upload module is used to bind the vehicle VIN code with the sub-assembly tightening data when the match is successful. If there are multiple version records, version control is performed to form the vehicle tightening association data and upload it to the tightening server.

[0101] It is worth noting that although this system / device only discloses the tightening result acquisition module, the disassembly timestamp acquisition module, the BOM verification module, the assembly timestamp acquisition module, the matching verification module, and the data upload module, it does not mean that this device is limited to the above-mentioned basic functional modules. On the contrary, what this invention intends to express is that, based on the above-mentioned basic functional modules, those skilled in the art can arbitrarily add one or more functional modules in combination with the prior art to form an infinite number of embodiments or technical solutions. That is to say, this system / device is open rather than closed. It should not be assumed that the scope of protection of the claims of this invention is limited to the above-disclosed basic functional modules just because this embodiment only discloses a few basic functional modules.

[0102] In one specific embodiment, the various modules of the system interact with each other through the message bus inside the all-in-one machine, and jointly complete the tightening data association process from parts sub-assembly to mainline assembly. Specifically:

[0103] The tightening result acquisition module is connected to the tightening machine controller in real time via Ethernet or industrial fieldbus. When the barcode scanner reads the part identification code, the module triggers the tightening machine to execute the tightening program and automatically acquires data such as torque, angle and tightening result judgment after tightening is completed.

[0104] The sub-assembly timestamp acquisition module encapsulates the tightening result and part identification code into a standardized data packet, generates a sub-assembly timestamp based on the system time, writes it into the sub-assembly data cache, and generates a unique sub-assembly data index for easy and quick retrieval later.

[0105] The BOM verification module automatically retrieves the parts list corresponding to the vehicle model from the BOM server by scanning the vehicle's VIN code at the main assembly station. Then, it uses the part identification code to extract the part type and verifies whether the part belongs to the assembly set of the corresponding vehicle through bitmap matching or fast table lookup algorithm.

[0106] If the verification passes, the assembly timestamp acquisition module will write the part identification code and VIN code as associated items into the main data cache area and record the assembly timestamp for subsequent matching.

[0107] The matching and verification module performs time window matching in the sub-assembly buffer area and the main line buffer area based on the part identification code. It uses a dynamic matching window built based on the average transfer time ± standard deviation to filter the corresponding sub-assembly data records, and further performs part code format verification, data integrity verification and workstation correspondence verification to ensure the reliability of the matching relationship.

[0108] Once a match is successful, the data upload module binds the matched sub-assembly data to the vehicle's VIN code. If there are multiple versions of the same part's sub-assembly records, the version control algorithm is executed, selecting the record with the largest version number as the final binding record, and all versions are combined into a version chain and uploaded to the tightening server.

[0109] Through the above steps, the system in this embodiment can automatically associate tightening data across workstations and time periods, avoiding errors from manual copying or matching, and achieving full-process data traceability and high-reliability assembly control.

[0110] Figure 3 This is a structural block diagram of an electronic device for an intelligent tightening data acquisition method based on part identification codes, provided by one or more embodiments of the present invention.

[0111] like Figure 3 As shown, this application provides an electronic device, including: a processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus;

[0112] The memory stores a computer program, which, when executed by the processor, causes the processor to perform the steps of an intelligent tightening data acquisition method based on part identification codes.

[0113] This application also provides a computer-readable storage medium storing a computer program executable by an electronic device, which, when run on the electronic device, causes the electronic device to perform the steps of an intelligent tightening data acquisition method based on part identification codes.

[0114] The communication bus mentioned in the above electronic devices can be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus, etc. This communication bus can be divided into address bus, data bus, control bus, etc. For ease of illustration, only one thick line is used to represent it in the diagram, but this does not indicate that there is only one bus or one type of bus.

[0115] The electronic device comprises a hardware layer, an operating system layer running on top of the hardware layer, and an application layer running on the operating system. The hardware layer includes hardware such as a central processing unit (CPU), a memory management unit (MMU), and memory. The operating system can be any one or more computer operating systems that control the electronic device through processes, such as Linux, Unix, Android, iOS, or Windows. Furthermore, in this embodiment of the invention, the electronic device can be a smartphone, tablet computer, or other handheld device, or a desktop computer, portable computer, or other electronic device; there is no particular limitation in this embodiment.

[0116] In this embodiment of the invention, the executing entity for electronic device control can be an electronic device itself, or a functional module within an electronic device capable of calling and executing a program. The electronic device can obtain the firmware corresponding to the storage medium. This firmware is provided by the supplier, and different storage media may have the same or different firmware; no limitation is made here. After obtaining the firmware corresponding to the storage medium, the electronic device can write this firmware into the storage medium; specifically, it burns the firmware corresponding to the storage medium into the storage medium. The process of burning the firmware into the storage medium can be implemented using existing technology, and will not be elaborated upon in this embodiment of the invention.

[0117] Electronic devices can also obtain reset commands corresponding to the storage media. The reset commands corresponding to the storage media are provided by the supplier. The reset commands corresponding to different storage media can be the same or different, and no restrictions are imposed here.

[0118] At this time, the storage medium of the electronic device is a storage medium on which the corresponding firmware has been written. The electronic device can respond to the reset command corresponding to the storage medium on which the corresponding firmware has been written, thereby resetting the storage medium on which the corresponding firmware has been written according to the reset command. The process of resetting the storage medium according to the reset command can be implemented by existing technology and will not be described in detail in this embodiment of the invention.

[0119] For ease of description, the above devices are described separately by function as various units and modules. Of course, in implementing this application, the functions of each unit and module can be implemented in one or more software and / or hardware.

[0120] It will be understood by those skilled in the art that, unless otherwise defined, all terms used herein (including technical and scientific terms) have the same meaning as commonly understood by one of ordinary skill in the art to which this invention pertains. It should also be understood that terms such as those defined in general dictionaries should be understood to have the meaning consistent with their meaning in the context of the prior art, and should not be interpreted in an idealized or overly formal sense unless specifically defined.

[0121] For the sake of simplicity, the method embodiments are described as a series of actions. However, those skilled in the art should understand that the embodiments of the present invention are not limited to the described order of actions, because according to the embodiments of the present invention, some steps can be performed in other orders or simultaneously. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions involved are not necessarily essential to the embodiments of the present invention.

[0122] As can be seen from the above description of the embodiments, those skilled in the art can clearly understand that this application can be implemented by means of software plus necessary general-purpose hardware platforms. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, can be embodied in the form of a software product. This computer software product can be stored in a storage medium, such as ROM / RAM, magnetic disk, optical disk, etc., and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute the methods described in various embodiments or some parts of the embodiments of this application.

[0123] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some or all of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims

1. A method for intelligent tightening data acquisition based on a part identification code, characterized in that, The method comprises: At the subassembly station, a part identification code is collected by a code scanning gun, and a tightening operation is performed on the part by a tightening machine controller to obtain a tightening result; The part identification code and the tightening result constitute a subassembly tightening data packet, which is stored in a subassembly data cache area of the all-in-one machine and a subassembly timestamp is recorded; At the main assembly station, the same part identification code and the vehicle VIN code are collected again by the code scanning gun, the all-in-one machine queries the corresponding BOM list according to the vehicle VIN code, and the part identification code is checked for compliance; When the BOM check passes, the part identification code and the corresponding vehicle VIN code are written into the main data cache area of the all-in-one machine, and an assembly timestamp is recorded; The all-in-one machine performs a time window matching algorithm between the part identification code in the subassembly data cache area and the main data cache area, and checks the matching result for consistency; When the matching is successful, the vehicle VIN code is bound with the subassembly tightening data, version control is performed if there are multiple version records, whole vehicle tightening association data is formed, and the data is uploaded to the tightening server.

2. The method of claim 1, wherein, The compliance check is implemented by bitmap matching, and the bitmap matching comprises: A part identification code bitmap is established for the BOM list corresponding to the vehicle VIN code, each bit corresponds to whether a part exists in the list, and a bit value of 1 indicates that the part type exists in the BOM list, and a bit value of 0 indicates that the part type does not exist in the BOM list; The part type code of the part identification code obtained by scanning is extracted, the corresponding bit in the bitmap is located, and it is judged whether the part belongs to the assembly part set of the vehicle.

3. The method of claim 1, wherein, When the BOM check fails, the following steps are performed: An error prompt is displayed on the operation terminal, and the error prompt includes the scanned part identification code, the corresponding vehicle VIN code, and the correct part identification code list; The data writing function of the current station is locked to prevent error data from entering the main data cache area; The BOM check failure event is recorded to an exception database, and the recording content includes a timestamp, a station identifier, an operator identifier, a part identification code, a vehicle VIN code, and a failure reason.

4. The method of claim 1, wherein, The time window matching algorithm comprises: The average transit time and the standard deviation of the part type corresponding to the part identification code from subassembly to assembly are calculated according to historical data; An effective matching time window is set according to the subassembly timestamp, and the relationship between the assembly timestamp and the time window is judged.

5. The method of claim 4, wherein, If the assembly timestamp falls within the time window, automatic matching is performed; if the assembly timestamp exceeds the time window but is less than a preset time threshold, matching is performed after manual confirmation; If the assembly timestamp exceeds the preset time threshold, it is marked as an exception and an exception handling process is triggered.

6. The method of claim 1, wherein, The consistency check on the matching result comprises: Part code format check: verifying the legality of the coding structure of the part identification code, including character length range check, character type check, and verification bit calculation verification; Data integrity check: verifying the existence and validity of the necessary fields in the subassembly tightening data packet, including tightening torque value, tightening angle value, tightening result determination, and timestamp integrity; Station correspondence check: verifying the existence of a legal assembly path relationship between the subassembly station identifier and the main station identifier according to a preset process routing table.

7. The method of claim 1, wherein, The execution version control comprises: For the same part identification code, multiple tightening records are assigned with increasing version numbers in chronological order; The record with the largest version number is selected and bound with the vehicle VIN code; All version records are uploaded to the tightening server as version chains.

8. An intelligent tightening data acquisition system based on part identification codes, characterized by, The system comprises: A tightening result acquisition module, configured to acquire a part identification code at a subassembly station by using a code scanner, and acquire a tightening result by performing a tightening operation on a component by a tightening machine controller; A subassembly timestamp acquisition module, configured to form a subassembly tightening data packet by using the part identification code and the tightening result, store the subassembly tightening data packet in a subassembly data cache of the all-in-one machine, and record a subassembly timestamp; A BOM verification module, configured to acquire the same part identification code and a vehicle VIN code at a main assembly station by using a code scanner, query a corresponding BOM list according to the vehicle VIN code, and perform a compliance verification on the part identification code; An assembly timestamp acquisition module, configured to write the part identification code and the corresponding vehicle VIN code into a main data cache of the all-in-one machine, and record an assembly timestamp when the BOM verification is passed; A matching verification module, configured to perform a time window matching algorithm between the subassembly data cache and the main data cache based on the part identification code, and perform a consistency verification on a matching result; A data upload module, configured to bind the vehicle VIN code with the subassembly tightening data when the matching is successful, perform a version control if there are multiple version records, form vehicle tightening associated data, and upload the vehicle tightening associated data to a tightening server.

9. An electronic device, comprising: The system comprises: A processor, a communication interface, a memory, and a communication bus, wherein the processor, the communication interface, and the memory communicate with each other through the communication bus; The memory stores a computer program, and when the computer program is executed by the processor, the processor executes the steps of the intelligent tightening data acquisition based on a part identification code according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that, The memory stores a computer program executable by the electronic device, and when the computer program runs on the electronic device, the electronic device executes the steps of the intelligent tightening data acquisition based on a part identification code according to any one of claims 1 to 7.

Images