Method and device for automatically processing PCB design data file, equipment and medium

Abstract

The invention discloses a method, device and equipment for automatically processing PCB design data files and a medium. The method comprises the steps that a file storage path catalog is retrieved regularly, versions of all ODB + + files in a storage path are recognized, whether the version of any ODB + + file is higher than or equal to a version threshold value or not is judged, and a first judgment result is obtained; if the first judgment result is yes, pre-installed high-version CAM auxiliary software is controlled and started, and ODB + + files with versions higher than or equal to a version threshold value are sequentially imported into the high-version CAM auxiliary software; sequentially exporting the ODB + + files of which the versions are higher than or equal to the version threshold value as low-version ODB + + files based on the high-version CAM auxiliary software; wherein the version of the low-version ODB + + file is lower than the version threshold value. The method is executed through a program, the version of the ODB + + file is automatically retrieved and reduced, and the working efficiency is greatly improved.

Description

Technical Field

[0001] The present invention relates to the field of PCB production data processing, and particularly to a method, device, equipment and medium for automatically processing PCB design data files. Background Art

[0002] The ODB++ (Open Database++) file is an XML-based open database format used to describe various data in the harness and PCB manufacturing processes, supporting data exchange throughout the entire life cycle from product design to production manufacturing, including geometric information, connection relationships, bills of materials, etc. of the harness and PCB, and enabling seamless data exchange between different software platforms.

[0003] In the field of PCB design, using the ODB++ format can simplify the design process and ensure accurate data transmission. However, compatibility issues may be encountered during the design conversion process. When the ODB++ data version is too high, it cannot be compatible with low-version CAM auxiliary software, and it is necessary to manually switch to a high-version CAM auxiliary software for manual downgrading to ensure data transmission.

[0004] Manually converting and downgrading files in a high-version CAM auxiliary software has problems such as low efficiency, easy error-proneness, strong dependence, and resource waste. Summary of the Invention

[0005] Embodiments of the present invention provide a method, device, equipment and medium for automatically processing PCB design data files, aiming to solve the problem of low efficiency in manually converting and downgrading files in a high-version CAM auxiliary software in the prior art method.

[0006] In a first aspect, embodiments of the present invention provide a method for automatically processing PCB design data files, which is executed by a program and is used to automatically lower the version of ODB++ files. The method includes:

[0007] Regularly retrieve the file storage path directory, identify the versions of all ODB++ files in the storage path, and determine whether the version of any of the ODB++ files is higher than or equal to a version threshold to obtain a first judgment result;

[0008] If the first judgment result is yes, control and start the pre-installed high-version CAM auxiliary software, and sequentially import the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software;

[0009] Based on the high-version CAM auxiliary software, sequentially export the ODB++ files with versions higher than or equal to the version threshold as low-version ODB++ files; wherein, the version of the low-version ODB++ file is lower than the version threshold.

[0010] In a second aspect, an embodiment of the present invention further provides a device for automatically processing PCB design data files, including:

[0011] A timing retrieval and judgment unit, configured to retrieve the file storage path directory at regular intervals, identify the versions of all ODB++ files in the storage path, and judge whether the version of any of the ODB++ files is higher than or equal to a version threshold to obtain a first judgment result;

[0012] An import unit, configured to, if the first judgment result is yes, control and start a pre-installed high-version CAM auxiliary software, and sequentially import the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software; and

[0013] An export unit, configured to sequentially export the ODB++ files with versions higher than or equal to the version threshold as low-version ODB++ files based on the high-version CAM auxiliary software;

[0014] wherein the version of the low-version ODB++ file is lower than the version threshold

[0015] In a third aspect, an embodiment of the present invention further provides a computer device, which includes a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete communication with each other through the communication bus;

[0016] The memory is used to store a computer program;

[0017] The processor, when executing the program stored in the memory, implements the steps of the method for automatically processing PCB design data files described in the first aspect

[0018] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, on which a computer program is stored. When the computer program is executed by a processor, it implements the steps of the method for automatically processing PCB design data files described in the first aspect.

[0019] An embodiment of the present invention provides a method, device, equipment and medium for automatically processing PCB design data files. The method includes: regularly retrieving the file storage path directory, identifying the versions of all ODB++ files in the storage path, determining whether the version of any of the ODB++ files is higher than or equal to a version threshold to obtain a first judgment result; if the first judgment result is yes, controlling and starting a pre-installed high-version CAM auxiliary software, and sequentially importing the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software; based on the high-version CAM auxiliary software, sequentially exporting the ODB++ files with versions higher than or equal to the version threshold as low-version ODB++ files; wherein, the version of the low-version ODB++ file is lower than the version threshold. By executing this method through a program, the version of the ODB++ file is automatically retrieved and reduced, greatly improving the work efficiency. Description of the Drawings

[0020] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the accompanying drawings required for the description of the embodiments will be briefly introduced below. Obviously, the accompanying drawings in the following description are some embodiments of the present invention. For those of ordinary skill in the art, other accompanying drawings can be obtained based on these drawings without creative efforts.

[0021] Figure 1 It is a flowchart of the method for automatically processing PCB design data files provided by an embodiment of the present invention;

[0022] Figure 2 It is an application scenario diagram of the method for automatically processing PCB design data files provided by an embodiment of the present invention;

[0023] Figure 3 It is a sub-flowchart of the method for automatically processing PCB design data files provided by an embodiment of the present invention;

[0024] Figure 4 It is a sub-flowchart of the method for automatically processing PCB design data files provided by an embodiment of the present invention;

[0025] Figure 5 It is a sub-flowchart of the method for automatically processing PCB design data files provided by an embodiment of the present invention;

[0026] Figure 6 It is a sub-flowchart of the method for automatically processing PCB design data files provided by an embodiment of the present invention;

[0027] Figure 7 It is another flowchart of the method for automatically processing PCB design data files provided by an embodiment of the present invention;

[0028] Figure 8Schematic block diagram of the device for automatically processing PCB design data files provided by the embodiments of the present invention;

[0029] Figure 9 Schematic block diagram of the computer device provided by the embodiments of the present invention. Detailed implementation manners

[0030] Next, the technical solutions in the embodiments of the present invention will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present invention. Obviously, the described embodiments are some, but not all, of the embodiments of the present invention. All other embodiments obtained by those of ordinary skill in the art based on the embodiments of the present invention without creative efforts shall fall within the protection scope of the present invention.

[0031] It should be understood that when used in this specification and the appended claims, the terms "comprises" and "comprising" indicate the presence of the described features, wholes, steps, operations, elements, and / or components, but do not preclude the presence or addition of one or more other features, wholes, steps, operations, elements, components, and / or their combinations.

[0032] It should also be understood that the terms used in the specification of the present invention are only for the purpose of describing specific embodiments and are not intended to limit the present invention. As used in the specification of the present invention and the appended claims, unless the context clearly indicates otherwise, the singular forms "a", "an", and "the" are intended to include the plural forms.

[0033] It should be further understood that the term " / and / or" used in the specification of the present invention and the appended claims refers to any combination and all possible combinations of one or more of the associated listed items, and includes these combinations.

[0034] It should also be noted that, unless otherwise clearly stipulated and defined, terms such as "installation", "connection", "linkage", "fixation", "setting" should be understood in a broad sense. For example, it can be a fixed connection, a detachable connection, or an integral one; it can be a mechanical connection or an electrical connection; it can be a direct connection or an indirect connection through an intermediate medium, and it can be the communication inside two components or the interaction relationship between two components. When one component is referred to as "on" or "under" another component, the component can be "directly" or "indirectly" located above the other component, or there may also be one or more intermediate components. The terms "first", "second", "third", etc. are only for the convenience of describing the present technical solution and cannot be understood as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. Thus, the features defined with "first", "second", "third", etc. may explicitly or implicitly include one or more of such features. For those of ordinary skill in the art, the specific meanings of the above terms in the present invention can be understood according to specific circumstances.

[0035] Please refer to Figure 1 and Figure 2, embodiments of the present invention provide a method for automatically processing PCB design data files. Among them, the ODB++ (Open Database++) file is an XML-based open database format used to describe various data in the wire harness and PCB manufacturing processes, supporting data exchange throughout the entire life cycle from product design to production manufacturing, including geometric information, connection relationships, bills of materials, etc. of wire harnesses and PCBs, and enabling seamless data exchange between different software platforms. However, when engineers exchange data at each stage, the following problems may occur: First, different software versions are used among engineers, resulting in different versions of the generated ODB++ files. When the version of the generated ODB++ file is too high, engineers using low-version software cannot open the high-version ODB++ file and need to trouble engineers with high-version software to manually lower the version, which affects work efficiency and, over time, affects the PCB production process. Second, although installing high-version software for all employees can, to a certain extent, solve the problem of being unable to open high-version ODB++ files, the CAM software used to open ODB++ files has a license restriction, that is, authentication permission is required and it needs to be paid to use. Therefore, installing high-version CAM software for all engineers requires a certain cost expenditure, and not every engineer needs the updated and iterative functions of the CAM software. Therefore, installing high-version CAM software for all engineers at any time is not an effective solution. The method for automatically processing PCB design data files provided by the embodiments of the present invention is implemented through one or more intelligent background programs, which can automatically lower the version of the ODB++ file so that engineers using low-version software within the enterprise can all open the ODB++ file.

[0036] As Figure 1 and Figure 2 shown, an embodiment of the invention provides a method for automatically processing PCB design data files, including steps S1 to S3.

[0037] S1. Regularly retrieve the file storage path directory, identify the versions of all ODB++ files in the storage path, and determine whether the version of any of the ODB++ files is higher than or equal to the version threshold to obtain a first judgment result.

[0038] In this embodiment, the file storage path is a storage path that can be accessed by all engineers of a company through their computer devices. Engineer A who processes the previous stage, such as the product design stage, can store the ODB++ file, which is a data file related to PCB production, in the directory of this file storage path. The file storage path is the file server transfer station, and the file storage path directory is the first storage directory of the file server transfer station. Engineer B or Engineer C who processes the next stage, such as production and manufacturing, can download the ODB++ file from this file storage path by themselves. The intelligent background program used to execute this method can be stored in one or more computer devices of the company. The computer device storing this intelligent background program can also access the above-mentioned file storage path. When the intelligent background program is stored in one computer device of the company, this computer device is dedicated to executing this intelligent background program. When this computer device executes the intelligent background program, it scans the directory of the file storage path regularly, that is, scans and retrieves the directory under the file storage path once every time period. This time period can be 15s, 30s, 45s or 1min, to identify the versions of all ODB++ files stored in this file storage path, and judge whether they are higher than or equal to the version threshold. If the version of any ODB++ file is higher than or equal to the version threshold, the first judgment result is output as yes, otherwise, the first judgment result is output as no.

[0039] Among them, the version threshold can be 8.0, and the versions of ODB++ files higher than the version threshold can be 8.1, 8.2, 8.3, 8.4, etc.

[0040] As Figure 3 shown, in a further embodiment, step S1 includes sub-steps S11 to S14.

[0041] S11. Control the pre-installed text editor to open all ODB++ files in the storage path in sequence.

[0042] In this embodiment, the pre-installed text editor can be an editor such as VS Code that has the function of editing the file code of ODB++ files. The text editor and the intelligent background program used to execute the method for automatically processing PCB design data files are installed in the same computer device. A certain part or unit of this intelligent background program is used to realize automatically controlling the text editor to open all ODB++ files in sequence.

[0043] S12. Scan the file code of the ODB++ file and judge whether the version number of the ODB++ file can be obtained.

[0044] In this embodiment, by scanning the file code of the ODB++ file, it is determined whether it includes character segments of "VERSION", "Version", or "version", so as to determine whether the version number of the ODB++ file can be obtained. If any of "VERSION", "Version", or "version" is scanned in its code, a result indicating that the version number can be obtained is output; otherwise, a result indicating that the version number cannot be obtained is output. After the result indicating that the version number can be obtained is output, the Arabic numerals after the character segments of "VERSION", "Version", or "version" and on the same line as them are obtained, and the Arabic numerals are the version number of the ODB++ file, such as 6.0, 7.0, 8.0, 8.1, 8.2, etc.

[0045] S13. If the version number of the ODB++ file can be obtained, determine whether the version number is greater than or equal to the version threshold; S14. If the version number is greater than or equal to the version threshold, then output that the first judgment result is yes.

[0046] In this embodiment, if the version number of the ODB++ file can be obtained, the version number of the ODB++ file is obtained, and it is determined whether the version number of the file is greater than the version threshold 8.0. If the version number is greater than or equal to the version threshold, the first output judgment result is yes; if the version number is less than the version threshold 8.0, the first judgment result is output as no.

[0047] As Figure 4 shown, in a further embodiment, after step S12, step S1 further includes sub-steps S15 to S17.

[0048] S15. If the version number of the ODB++ file cannot be obtained, scan the original directory of the ODB++ file for which the version number cannot be obtained; S16. Determine whether the original directory contains the directory unique to the ODB++ file corresponding to the version threshold, and the unique directory is Azonesfile; S17. If the original directory contains the directory unique to the ODB++ file corresponding to the version threshold, then output that the first judgment result is yes.

[0049] In this embodiment, it is considered that if the version number of the ODB++ file cannot be obtained, it may be due to an unexpected situation that causes the code corresponding to the version number of the ODB++ file to be lost, resulting in S12 being unable to obtain the version number of the ODB++ file. The original directory of the ODB++ file usually appears as several subdirectories under a root directory. When the design software exports the ODB++ file, each subdirectory of the ODB++ file is attached with its directory name. Among them, the file data stored in some subdirectories corresponds to the function of the ODB++ file data. Among them, taking version 8.0 as an example, only the original directory of the ODB++ file with a version higher than or equal to version 8.0 includes "Azonesfile", and the data in Azonesfile is used to define the area of the middle layer material of the circuit board. By scanning whether the original directory of the ODB++ file whose version number cannot be obtained includes Azonesfile, it is judged whether the version of the ODB++ file is higher than or equal to the version threshold. If the original directory contains the directory unique to the ODB++ file corresponding to the version threshold, the first judgment result is output as yes. This embodiment does not need to directly obtain the version number in the code of the ODB++ file, and can also judge whether the version of the ODB++ file is higher than or equal to the version threshold, avoiding incorrect judgment when some codes are lost.

[0050] If the directory unique to the ODB++ file corresponding to the version threshold cannot be obtained, the first judgment result is output as no.

[0051] S2. If the first judgment result is yes, control and start the pre-installed high-version CAM auxiliary software, and sequentially import the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software.

[0052] In this embodiment, the high-version CAM auxiliary software is installed on the same computer device as the above text editor and intelligent background program. The high-version CAM auxiliary software is a design software that can open ODB++ files with versions higher than or equal to the version threshold. For example, it can open GENESIS2000 10.08, InCAM, InCAMPRO with versions 8.0 and above. Automatically control and start the pre-installed high-version CAM auxiliary software, and sequentially import the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software.

[0053] Such as Figure 5 As shown, in a further embodiment, step S2 includes sub-steps S21 to S25.

[0054] S21. Download all ODB++ files with a version higher than or equal to the version threshold from the file storage path directory, where the file storage path directory is the first storage directory in the file server transfer station.

[0055] In this embodiment, the file server transfer station can be a server dedicated to the company's internal work materials, and both the computer devices used by engineers and the computer devices storing the above intelligent background program can access it. After all engineers generate the ODB++ file materials for the work stages they are responsible for, they can upload the modified ODB++ files to the first storage directory of the file server transfer station. The first storage directory is the above-mentioned file storage path directory. When performing step S1, it also retrieves and scans this first storage directory.

[0056] S22. Open the downloaded ODB++ files in sequence and set the opening method to the high-version CAM auxiliary software pre-installed locally; S23. Determine whether the ODB++ file import is successful; S24. If the ODB++ file import fails, record the import failure information and upload the import failure information to the file server transfer station; S25. If the ODB++ file import is successful, obtain the imported successful ODB++ file.

[0057] In this embodiment, if the ODB++ file import fails, record the import failure information and upload the import failure information to the file server transfer station. The import failure information includes the name of the ODB++ file with import failure, the time of import failure, and the IP address of the computing device causing the failure, so as to facilitate subsequent manual troubleshooting of the specific reasons for the import failure.

[0058] S3. Based on the high-version CAM auxiliary software, export the ODB++ files with a version higher than or equal to the version threshold to low-version ODB++ files in sequence, where the version of the low-version ODB++ file is lower than the version threshold.

[0059] In this embodiment, a low-version ODB++ file can be opened by a low-version CAM auxiliary software. The version of the low-version ODB++ file is two major versions lower than the version threshold. For example, if the version threshold is 8.0 and the version of the low-version ODB++ file is 6.0, the low-version ODB++ file can be opened by the CAM auxiliary software GENESIS9.07b2. The purpose of reducing the version of the ODB++ file by two major versions is to process the ODB++ file data in place as much as possible by executing a program once, so that the CAM auxiliary software installed on all engineers' computers can open the ODB++ file with the reduced version, avoiding that only reducing one version still causes some engineers to open the ODB++ file for the next PCB production work; at the same time, avoiding reducing the version of the ODB++ file too low, resulting in the loss of the basic functions required by engineers in the current PCB field for PCB design or manufacturing.

[0060] As Figure 6 shown, in a further embodiment, step S3 includes sub-steps: S31 to S34.

[0061] S31. Based on the file export function of the high-version CAM auxiliary software, sequentially export the successfully imported ODB++ file as a low-version ODB++ file in the TGZ format; S32. Determine whether the ODB++ file export is successful; S33. If the ODB++ file export is successful, obtain the successfully exported low-version ODB++ file; S34. If the ODB++ file export fails, record the export failure information and upload the export failure information to the file server transfer station.

[0062] In this embodiment, the file export function is a built-in function of the CAM auxiliary software. Only by editing the version number of the exported ODB++ file, such as 6.0, in the code of the intelligent background program that executes this method, the ODB++ file can be exported as a version of 6.0. Among them, TGZ is the default compression format exported by the CAM auxiliary software, which is convenient for uploading and downloading. If the ODB++ file export fails, record the export failure information and upload the export failure information to the file server transfer station. The export failure information includes the name of the ODB++ file that failed to be exported, the time of export failure, and the IP address of the computing device where the export failed, which is convenient for subsequent manual troubleshooting of the specific reasons for the export failure.

[0063] As Figure 7 shown, in a further embodiment, the method for automatically processing PCB design data files further includes: S4 to S5.

[0064] S4. Upload the successfully exported low-version ODB++ file to the second storage directory in the file server transfer station.

[0065] In this embodiment, the second storage directory and the first storage directory are not the same root directory in the file server. That is, the ODB++ files automatically processed by this method are stored in the second storage directory. When the engineer uploads his own ODB++ files, when the engineer needs to download the ODB++ files he needs from the file server transfer station, it can be avoided that the high-version ODB++ files in the first storage directory are not completely processed, resulting in his downloading unprocessed ODB++ files.

[0066] S5. Delete the high-version ODB++ files stored in the first storage directory; wherein, the high-version ODB++ files are the original files corresponding to the low-version ODB++ files.

[0067] In this embodiment, after uploading the low-version ODB++ files to the second storage directory in the file server transfer station, the high-version ODB++ files stored in the first storage directory are deleted. Since this method for automatically processing PCB design data files retrieves the file storage path directory automatically at regular intervals when executing step S1, if the high-version ODB++ files are still stored in this storage path directory, that is, the first storage directory, it will cause the intelligent background program to repeatedly execute S1 to S4, resulting in the program running meaninglessly. Therefore, a module or unit for deleting high-version ODB++ files is also written in the code of the intelligent background program.

[0068] An embodiment of the present invention discloses a method for automatically processing PCB design data files. The program for executing the method is stored in a computer device. The computer device can access a file server transfer station. The computer device is installed with a high-version CAM auxiliary software. The method includes: retrieving the file storage path directory regularly, identifying the versions of all ODB++ files in the storage path, determining whether the version of any ODB++ file is higher than or equal to a version threshold to obtain a first determination result; if the first determination result is yes, controlling and starting the pre-installed high-version CAM auxiliary software, and sequentially importing the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software; based on the high-version CAM auxiliary software, sequentially exporting the ODB++ files with versions higher than or equal to the version threshold as low-version ODB++ files; wherein, the version of the low-version ODB++ file is lower than the version threshold. By automatically retrieving and reducing the version of ODB++ files through the background program, the work efficiency is greatly improved, providing a strong guarantee for the smooth transfer of PCB design data and the smooth progress of the production process.

[0069] An embodiment of the present invention also provides an apparatus for automatically processing PCB design data files. Specifically, please refer to Figure 8 , Figure 8Schematic block diagram of the device for automatically processing PCB design data files provided by the embodiments of the present invention.

[0070] As Figure 8 shown, the device for automatically processing PCB design data files includes:

[0071] A timing retrieval and judgment unit 110, configured to retrieve the file storage path directory at regular intervals, identify the versions of all ODB++ files in the storage path, judge whether the version of any of the ODB++ files is higher than or equal to a version threshold, and obtain a first judgment result;

[0072] An import unit 120, configured to, if the first judgment result is yes, control and start the pre-installed high-version CAM auxiliary software, and sequentially import the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software; and

[0073] An export unit 130, configured to sequentially export the ODB++ files with versions higher than or equal to the version threshold as low-version ODB++ files based on the high-version CAM auxiliary software; wherein, the version of the low-version ODB++ file is lower than the version threshold.

[0074] Further, the device for automatically processing PCB design data files further includes:

[0075] An upload unit 140, configured to upload the successfully exported low-version ODB++ files to a second storage directory in the file server transfer station;

[0076] A deletion unit 150, configured to delete the high-version ODB++ files stored in the first storage directory; wherein, the high-version ODB++ files are the original files corresponding to the low-version ODB++ files.

[0077] The above-mentioned device for automatically processing PCB design data files can be implemented in the form of a computer program, that is, the above-mentioned intelligent background program, and this computer program can run on a computer device as Figure 9 shown.

[0078] Please refer to Figure 9 , Figure 9 which is a schematic block diagram of the computer device provided by the embodiments of the present invention. This computer device can be used to execute the method for automatically processing PCB design data files.

[0079] Referring to Figure 9 , this computer device 500 includes a processor 502, a memory, and a network interface 505 connected through a communication bus 501, wherein the memory may include a storage medium 503 and an internal memory 504.

[0080] The storage medium 503 can store an operating system 5031 and a computer program 5032. When the computer program 5032 is executed, it can cause the processor 502 to execute a method for automatically processing PCB design data files. Among them, the storage medium 503 can be a volatile storage medium or a non-volatile storage medium.

[0081] The processor 502 is used to provide computing and control capabilities to support the operation of the entire computer device 500.

[0082] The internal memory 504 provides an environment for the operation of the computer program 5032 in the storage medium 503. When the computer program 5032 is executed by the processor 502, it can cause the processor 502 to execute a method for automatically processing PCB design data files.

[0083] The network interface 505 is used for network communication, such as providing the transmission of data information, etc. Those skilled in the art can understand that Figure 9 the structure shown in is only a block diagram of some structures related to the solution of the present invention, and does not constitute a limitation on the computer device 500 to which the solution of the present invention is applied. The specific computer device 500 may include more or fewer components than those shown in the figure, or combine some components, or have a different component layout.

[0084] Among them, the processor 502 is used to run the computer program 5032 stored in the memory to implement the corresponding functions in the above method for automatically processing PCB design data files.

[0085] Those skilled in the art can understand that Figure 9 the embodiments of the computer device shown in do not constitute a limitation on the specific composition of the computer device. In other embodiments, the computer device may include more or fewer components than those shown in the figure, or combine some components, or have a different component layout. For example, in some embodiments, the computer device may only include a memory and a processor. In such an embodiment, the structures and functions of the memory and the processor are the same as those in Figure 9 the shown embodiment and will not be described in detail here.

[0086] It should be understood that in the embodiments of the present invention, the processor 502 may be a central processing unit (CPU), and the processor 502 may also be other general-purpose processors, digital signal processors (DSPs), application specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. Among them, the general-purpose processor may be a microprocessor or the processor may also be any conventional processor, etc.

[0087] In another embodiment of the present invention, a computer-readable storage medium is provided. The computer-readable storage medium may be a volatile or non-volatile computer-readable storage medium. The computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the steps included in the above method for automatically processing PCB design data files are implemented.

[0088] Those skilled in the art can clearly understand that for the convenience and brevity of description, the specific working processes of the above-described devices, apparatuses, and units can refer to the corresponding processes in the foregoing method embodiments, and will not be described herein again. Those of ordinary skill in the art can realize that the units and algorithm steps of the examples described in conjunction with the embodiments disclosed herein can be implemented by electronic hardware, computer software, or a combination of the two. To clearly illustrate the interchangeability of hardware and software, the components and steps of the examples have been generally described according to their functions in the above description. Whether these functions are executed in a hardware or software manner depends on the specific application and design constraints of the technical solution. Professional technicians can use different methods to implement the described functions for each specific application, but such implementation should not be considered to exceed the scope of the present invention.

[0089] In the several embodiments provided by the present invention, it should be understood that the disclosed devices, apparatuses, and methods can be implemented in other ways. For example, the device embodiments described above are merely illustrative. For example, the division of the units is only a logical function division, and there may be other division methods in actual implementation. Units with the same function can also be aggregated into a unit. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. In addition, the displayed or discussed couplings or direct couplings or communication connections to each other can be indirect couplings or communication connections through some interfaces, devices, or units, and can also be electrical, mechanical, or other forms of connection.

[0090] The unit described as a separation component may or may not be physically separated. The component displayed as a unit may or may not be a physical unit, that is, it may be located in one place or distributed to multiple network units. Some or all of the units can be selected according to actual needs to achieve the purpose of the solution of the embodiments of the present invention.

[0091] In addition, each functional unit in various embodiments of the present invention may be integrated in a processing unit, may exist separately as individual physical units, or two or more units may be integrated in one unit. The above-mentioned integrated unit can be implemented in the form of hardware or in the form of a software functional unit.

[0092] If the above-mentioned integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on such an understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a computer-readable storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The aforementioned computer-readable storage medium includes: various media such as USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), magnetic disks, or optical discs that can store program codes.

[0093] As described above, it is only the specific implementation manners of the present invention, but the protection scope of the present invention is not limited thereto. Any person skilled in the art within the technical scope disclosed by the present invention can easily think of various equivalent modifications or substitutions, and these modifications or substitutions should be covered within the protection scope of the present invention. Therefore, the protection scope of the present invention should be subject to the protection scope of the claims.

Claims

1. A method for automatically processing PCB design data files, which is executed by a program and is used to automatically reduce the version of ODB++ files, characterized in that, The method includes: Periodically retrieve the file storage path directory, identify the versions of all ODB++ files in the storage path, determine whether the version of any of the ODB++ files is higher than or equal to the version threshold, and obtain a first judgment result; If the first judgment result is yes, control and start the pre-installed high-version CAM auxiliary software, and sequentially import the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software; Based on the high-version CAM auxiliary software, sequentially export the ODB++ files with versions higher than or equal to the version threshold as low-version ODB++ files; wherein, the version of the low-version ODB++ file is lower than the version threshold.

2. The method for automatically processing a PCB design data file according to claim 1, wherein The version threshold is 8.0, and the version of the low-version ODB++ file is 6.

0.

3. The method for automatically processing a PCB design data file according to claim 1, wherein, The periodically retrieving the file storage path directory, identifying the versions of all ODB++ files in the storage path, and determining whether the version of any of the ODB++ files is higher than or equal to the version threshold to obtain a judgment result includes: Control the pre-installed text editor to sequentially open all ODB++ files in the storage path; Scan the file code of the ODB++ file to determine whether the version number of the ODB++ file can be obtained; If the version number of the ODB++ file is obtained, determine whether the version number is greater than or equal to the version threshold; If the version number is greater than or equal to the version threshold, then output that the first judgment result is yes.

4. The method for automatically processing a PCB design data file according to claim 3, wherein After scanning the file code of the ODB++ file to determine whether the version number of the ODB++ file can be obtained, it further includes: If the version number of the ODB++ file cannot be obtained, scan the original directory of the ODB++ file for which the version number cannot be obtained; Determine whether the original directory contains the directory unique to the ODB++ file corresponding to the version threshold; wherein, the unique directory is Azonesfile; If the original directory contains the directory unique to the ODB++ file corresponding to the version threshold, then output that the first judgment result is yes.

5. The method for automatically processing a PCB design data file according to claim 1, wherein The if the first judgment result is yes, control and start the pre-installed high-version CAM auxiliary software, and sequentially import the ODB++ files with versions higher than or equal to the version threshold into the high-version CAM auxiliary software includes: Download all ODB++ files higher than or equal to the version threshold from the file storage path directory to the local; wherein, the file storage path directory is the first storage directory in the file server transfer station; Sequentially open the downloaded ODB++ files and set the opening method to the pre-installed high-version CAM auxiliary software on the local; Determine whether the import of the ODB++ file is successful; If the import of the ODB++ file fails, record the import failure information and upload the import failure information to the file server transfer station; If the import of the ODB++ file is successful, obtain the successfully imported ODB++ file.

6. The method for automatically processing a PCB design data file according to claim 5, characterized in that, The based on the high-version CAM auxiliary software, sequentially export the ODB++ files with versions higher than or equal to the version threshold as low-version ODB++ files includes: Based on the file export function of the high-version CAM auxiliary software, sequentially export the successfully imported ODB++ file as a low-version ODB++ file in the TGZ format; Judge whether the export of the ODB++ file is successful; If the export of the ODB++ file is successful, obtain the successfully exported low-version ODB++ file; If the export of the ODB++ file fails, record the export failure information and upload the export failure information to the file server transfer station.

7. The method for automatically processing a PCB design data file according to claim 6, wherein After sequentially exporting the ODB++ files with a version higher than or equal to the version threshold based on the high-version CAM auxiliary software, further include: Upload the successfully exported low-version ODB++ file to the second storage directory in the file server transfer station; Delete the high-version ODB++ file stored in the first storage directory; wherein, the high-version ODB++ file is the original file corresponding to the low-version ODB++ file.

8. An apparatus for automatically processing a PCB design data file, characterized in that, Include: A timing retrieval and judgment unit, configured to periodically retrieve the file storage path directory, identify the versions of all ODB++ files in the storage path, and judge whether the version of any ODB++ file is higher than or equal to the version threshold to obtain a first judgment result; An import unit, configured to, if the first judgment result is yes, control and start the pre-installed high-version CAM auxiliary software, and sequentially import the ODB++ files with a version higher than or equal to the version threshold into the high-version CAM auxiliary software; And An export unit, configured to sequentially export the ODB++ files with a version higher than or equal to the version threshold as low-version ODB++ files based on the high-version CAM auxiliary software; Wherein, the version of the low-version ODB++ file is lower than the version threshold.

9. A computer device, characterized in that, The device includes a processor, a communication interface, a memory, and a communication bus. Among them, the processor, the communication interface, and the memory complete mutual communication through the communication bus; The memory is used to store computer programs; The processor, when executing the program stored on the memory, implements the steps of the method for automatically processing PCB design data files as described in any one of claims 1-7.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method for automatically processing PCB design data files as described in any one of claims 1-7.

Images