Data management program, data management method, data management device, and circuit board inspection system
Patent Information
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- YAMAHA MOTOR CO LTD
- Filing Date
- 2022-10-19
- Publication Date
- 2026-08-03
AI Technical Summary
【0007】 上記の構成によれば、チューニングされる可能性が高い検査データのチューニング用データについてはデータ量が削減されないようにしつつ記憶部の空き容量を確保できる。
Smart Images

Figure 0007899040000001 
Figure 0007899040000002 
Figure 0007899040000003
Abstract
Description
Technical Field
[0005] , , , , ,
[0004] ,
[0001] The technology disclosed in this specification relates to a data management program, a data management method, a data management device, and a substrate inspection system for managing tuning data used for tuning inspection data used for inspecting a substrate on which components are mounted.
Background Art
[0002] Conventionally, inspection of a substrate on which components are mounted has been performed (for example, see Patent Document 1). The substrate inspection device described in Patent Document 1 performs three-dimensional measurement of a measurement target area and inspects the printed state of solder based on the measurement result. Although the substrate inspection device described in Patent Document 1 inspects the printed state of solder, a substrate inspection device for inspecting a substrate on which components are mounted is also known. A substrate inspection device for inspecting a substrate on which components are mounted is generally referred to as a post-mount appearance inspection device (or a post-mount appearance inspection machine).
Prior Art Documents
Patent Documents
[0003]
Patent Document 1
Summary of the Invention
Problems to be Solved by the Invention
[0004] When a substrate is inspected using inspection data in a substrate inspection device, if the inspection situation deviates from an ideal situation, it is possible that the inspection data is inappropriate. In such a case, an operator may tune (adjust) the inspection data using the tuning data stored in a storage unit. However, if the tuning data is left stored in the storage unit, the free capacity of the storage unit decreases.
[0005] This specification discloses a technique that ensures free storage space is available while preventing a reduction in the amount of data used for tuning inspection data that is likely to be tuned. [Means for solving the problem]
[0006] A data management program for managing tuning data used to tune inspection data used for inspecting circuit boards on which components are mounted, wherein the program causes a computer to perform a determination process to determine whether the inspection status using the inspection data satisfies predetermined conditions, and a reduction process to reduce the amount of tuning data stored in the memory unit if the determination process determines that the predetermined conditions are met. [Effects of the Invention]
[0007] With the above configuration, it is possible to ensure that the amount of data used for tuning the inspection data, which is likely to be tuned, is not reduced while still securing free space in the storage unit. [Brief explanation of the drawing]
[0008] [Figure 1] Block diagram showing the configuration of the component mounting system according to Embodiment 1 [Figure 2] Schematic diagram showing the configuration of the inspection device. [Figure 3] Block diagram showing the configuration of the server computer and management computer. [Figure 4] Schematic diagram of the parts inspection data creation screen [Figure 5] Schematic diagram to explain the creation of parts inspection data. [Figure 6] Schematic diagram of the parts inspection data registration screen [Figure 7] Schematic diagram of the inspection status summary screen [Figure 8A] Schematic diagram of a filtered image where the 3D shape is not distorted. [Figure 8B] Schematic diagram of a filtered image with distorted 3D shape. [Figure 9] Schematic diagram of the circuit board information setting screen [Figure 10] Schematic diagram of the inquiry screen [Figure 11] Flowchart of the process performed by the inspection device [Figure 12] Flowchart for the process of turning on the delete flag [Figure 13] Flowchart for the process of deleting the pre-filtered image [Figure 14] Flowchart for the process of deleting the pre-filtered image according to Embodiment 2 [Modes for carrying out the invention]
[0009] (Summary of the embodiment) (1) The data management program according to the embodiment is a data management program that manages tuning data used for tuning inspection data used for inspecting a circuit board on which components are mounted, and causes a computer to perform a determination process to determine whether the status of the inspection using the inspection data satisfies predetermined conditions, and a reduction process to reduce the amount of tuning data stored in the storage unit when the determination process determines that the predetermined conditions are satisfied.
[0010] If tuning data is stored in the memory unit, reducing the amount of tuning data used for inspection data that is unlikely to be tuned in the future will free up memory space while ensuring that the amount of tuning data for inspection data that is likely to be tuned is not reduced. However, it was difficult for operators to determine whether or not inspection data was unlikely to be tuned. The inventors of this invention, after considering this matter, found that if the inspection conditions using the inspection data are ideal, the likelihood of those inspection data being tuned in the future is low.
[0011] According to the data management program described in (1) above, when the inspection status using inspection data meets a predetermined condition, the data volume of the tuning data is reduced. Therefore, setting an ideal situation as the predetermined condition, and assuming that inspection data in an ideal inspection situation is less likely to be tuned in the future, the data volume of the tuning data for such inspection data is reduced, so that the data volume of the tuning data for inspection data that is highly likely to be tuned is not reduced, while ensuring the free capacity of the storage unit.
[0012] (2) The data management program described in (1) above, wherein the reduction process may be at least one of a process of deleting the tuning data, a process of compressing the tuning data, and a process of moving the tuning data to another storage unit.
[0013] According to the data management program described in (2) above, by deleting, compressing or moving the tuning data, the free capacity of the storage unit can be ensured.
[0014] (3) The data management program described in (1) or (2) above, wherein the inspection data is data for inspecting the part shape of the part, and the tuning data may be image data representing at least one of the two-dimensional shape and the three-dimensional shape of the part.
[0015] Generally, since image data has a large data volume, the effect of ensuring the free capacity of the storage unit becomes remarkable.
[0016] (4) The data management program described in (3) above, wherein in the storage unit, as the image data, the image data before noise removal processing and the image data created by performing the noise removal processing on the image data are stored, and the data management program may reduce the data volume of the image data before the noise removal processing in the reduction process.
[0017] According to the data management program described in (4) above, even if the inspection status using the inspection data meets the predetermined conditions, the image data created after noise reduction processing will not be deleted. Therefore, even if the inspection status using the inspection data meets the predetermined conditions, the operator can continue to tune the inspection data using the image data created after noise reduction processing stored in the memory unit.
[0018] (5) The data management program described in (1) or (2) above may cause the computer to perform a setting process that accepts the setting of the predetermined conditions from the operator.
[0019] The ideal level of testing varies from time to time. Therefore, if predetermined conditions are fixed, the amount of tuning data may not be reduced when it should be, or conversely, it may be reduced when it shouldn't be. According to the data management program described in (5) above, the operator can set predetermined conditions, thereby reducing the possibility that the amount of tuning data should be reduced but is not, or conversely, that it is reduced when it should not be.
[0020] (6) A data management program as described in (1) or (2) above, wherein in the reduction process, if the status of the inspection using the inspection data satisfies the predetermined conditions, the operator may select whether or not to reduce the amount of tuning data, and if the selection to reduce is made, the amount of data may be reduced.
[0021] Operators may want to avoid reducing the amount of tuning data even if the inspection conditions meet certain requirements. According to the data management program described in (6) above, the operator can choose whether or not to reduce the amount of tuning data even if the inspection status meets the specified conditions.
[0022] (7) The data management program described in (6) above, which, in the reduction process, accepts from the operator whether or not to reduce the amount of tuning data, may also inform the operator of the inspection status when the board is inspected using the inspection data.
[0023] According to the data management program described in (7) above, the operator can decide whether or not to reduce the amount of data used for tuning based on the inspection status.
[0024] (8) The data management program described in (6) above, wherein the control unit may, in the reduction process, accept an option from the operator whether or not to reduce the amount of tuning data if the operator has the authority to reduce the tuning data.
[0025] Regardless of the operator, if the amount of data used for tuning can be reduced, it's possible that the amount of data used for tuning that shouldn't be reduced will also be reduced. According to the data management program described in (8) above, if the operator has the authority to reduce tuning data, they are given the option to choose whether or not to reduce the amount of tuning data, thereby preventing the reduction of tuning data that should not be reduced.
[0026] (9) A data management method according to an embodiment is a data management method for managing tuning data used to tune inspection data used to inspect a circuit board on which components are mounted, and includes a determination step of determining whether the status of inspection using the inspection data satisfies predetermined conditions, and a reduction step of reducing the amount of tuning data stored in the storage unit when the determination step determines that the predetermined conditions have been met.
[0027] According to the data management method described in (9) above, it is possible to ensure that the amount of data used for tuning the inspection data that is likely to be tuned is not reduced, while also securing free space in the storage unit.
[0028] (10) A data management device according to an embodiment is a data management device for managing tuning data used to tune inspection data used to inspect a circuit board on which components are mounted, comprising a storage unit for storing the tuning data and a control unit, wherein the control unit performs a determination process to determine whether the status of inspection using the inspection data satisfies predetermined conditions, and a reduction process to reduce the amount of the tuning data stored in the storage unit if the determination process determines that the predetermined conditions are satisfied.
[0029] According to the data management device described in (10) above, it is possible to ensure that the amount of data used for tuning the inspection data, which is likely to be tuned, is not reduced, while still securing free space in the storage unit.
[0030] (11) A substrate inspection system according to an embodiment is a substrate inspection system for inspecting a substrate on which components are mounted, comprising a data management device as described in (10) above, and a substrate inspection device for inspecting the substrate using the inspection data.
[0031] According to the circuit board inspection system described in (11) above, it is possible to ensure that the amount of data used for tuning the inspection data that is likely to be tuned is not reduced, while also securing free space in the storage unit.
[0032] [Details of the embodiments of this disclosure] Embodiments of the present disclosure are described below. The present disclosure is not limited to these examples, but is indicated by the claims, and all modifications within the meaning and scope of the claims are intended to be included. Embodiments of the present disclosure can be implemented in various forms, such as apparatus, methods, computer programs for realizing the functions of such apparatus or methods, and recording media on which such computer programs are stored.
[0033] <Embodiment 1> Embodiment 1 will be described with reference to Figures 1 to 13. In the following description, reference numerals in the drawings may be omitted for identical components, with some exceptions.
[0034] (1) Component mounting system Referring to Figure 1, the component mounting system 1 according to Embodiment 1 will be described. The component mounting system 1 is a system for mounting components such as electronic components onto a circuit board. The component mounting system 1 comprises one or more mounting lines L for mounting components onto a circuit board, a server computer 2, and a management computer 3 (an example of a computer and data management device). The mounting lines L, server computer 2, and management computer 3 are connected to each other via a communication network 5.
[0035] The mounting line L includes a loader 70, a screen printing device 71, a print inspection device 72, a dispenser 73, one or more component mounting devices 74, a post-mounting visual inspection device 4 (an example of a substrate inspection device), a reflow device 75, a post-curing visual inspection device 76, and an unloader 77. These devices are arranged in a line via multiple conveyor devices 78. The post-mounting visual inspection device 4 is a device that inspects the quality of the component shape of components mounted on the circuit board by the component mounting device 74, using component inspection data (an example of inspection data). In the following description, the post-mounting visual inspection device 4 will simply be referred to as the inspection device 4.
[0036] Server computer 2 is a computer that stores various information related to the production of circuit boards. Management computer 3 is a computer that creates, stores, and tunes component inspection data, and stores and manages tuning data used for tuning component inspection data. The inspection device 4 and the management computer 3 constitute the substrate inspection system according to Embodiment 1.
[0037] (2) Configuration of the inspection device Referring to Figure 2, the configuration of the inspection device 4 will be outlined. The inspection device 4 includes a transport conveyor for transporting the substrate P to the inspection position, a main camera 11 positioned above the inspection position, four projectors 12 (12N, 12E, 12S, 12W) that project a sine wave pattern onto the substrate P from an oblique upward direction, a moving unit that moves the main camera 11 and projectors 12 in a direction parallel to the surface of the substrate P, and a control unit that controls each part of the inspection device 4. The inspection of component shapes by the inspection device 4 will be described later.
[0038] (3) Configuration of the server computer and management computer Referring to Figure 3, the configurations of the server computer 2 and the management computer 3 will be described. Since the configurations of the server computer 2 and the management computer 3 are substantially the same, the management computer 3 will be used as an example for this explanation. The management computer 3 is a so-called personal computer and is equipped with a control unit 21, a storage unit 22, a communication unit 23, a display unit 24, and an operation unit 25.
[0039] The control unit 21 has a CPU 21A and RAM 21B. The CPU 21A controls various parts of the management computer 3 by executing various programs stored in the memory unit 22. The memory unit 22 stores various programs and data executed by the CPU 21A. The communication unit 23 is a communication circuit for the CPU 21A to communicate with the server computer 2 and other devices via the communication network 5. The display unit 24 consists of a display device such as a liquid crystal display, a drive circuit to drive the display device, and so on. The operation unit 25 consists of a keyboard, mouse, touch panel, and so on.
[0040] The programs stored in the memory unit 22 of the management computer 3 include a data management program that manages tuning data (pre-filtered image 33 and post-filtered image 34, described later) used for tuning component inspection data. The data stored in the memory unit 22 of the management computer 3 includes component inspection data, tuning data, and the like.
[0041] (4) Parts inspection data and creation of parts inspection data The part inspection data will be explained with reference to Figure 4. The part inspection data creation screen 30 shown in Figure 4 is a screen displayed by the management computer 3 that runs the data management program. The part inspection data creation screen 30 displays the three-dimensional shape (hereinafter referred to as 3D shape) of part E. Figure 4 shows a top view of the rectangular part E as seen from above. The part inspection data creation screen 30 can also display the part shape when viewed from the left and right, or from the front and back. In Figure 4, the dashed-dot contour line 31 represents the part inspection data. The part inspection data represents the 3D shape of part E and is created for each type of part E.
[0042] Referring to Figure 2, the creation of component inspection data will be explained. Component inspection data is created using a phase shift method with the main camera 11 and four projectors 12 provided by the inspection device 4. The phase shift method involves projecting a sine wave pattern onto the area to be imaged (in this case, the area on the substrate P that includes the position where the component E, for which component inspection data is to be created, is mounted) using the projector 12, capturing the image with the main camera 11, and then analyzing the captured image to measure the height.
[0043] Here, if a sine wave pattern is projected onto the area to be imaged from only one direction, a blind spot will be created due to the shadow of part E. Therefore, the inspection device 4 projects sine wave patterns sequentially from four directions (N, S, W, E directions) using four projectors 12, and each time a sine wave pattern is projected by one projector 12, part E is imaged with the main camera 11. This results in the acquisition of four images. The inspection device 4 transmits the four acquired images to the management computer 3.
[0044] The control unit 21 of the management computer 3, for each of the four images received from the inspection device 4, determines the height of the corresponding position on the substrate P for each pixel that makes up the image, based on the sine wave pattern captured in the image. Then, as shown in Figure 5, the control unit 21 creates 3D images 32 (32N, 32E, 32S, 32W) with the determined height as the pixel value. For example, if one unit of the pixel value represents 0.1 mm, then the height represented by a pixel with a pixel value of 10 will be 1 mm.
[0045] The control unit 21 performs a merge process on the 3D images 32 created for each of the four images to create a merged image 33. The merge process is a process that creates a single 3D image (merged image 33) that represents the height of all positions in the area to be imaged by supplementing the height of blind spots in one 3D image 32 with another 3D image 32. Next, the control unit 21 applies noise reduction processing to the integrated image 33 to remove noise, thereby creating an integrated image 34 from which noise has been removed. Various methods are known for noise reduction processing, such as dilation and condensation processing and the use of spatial filters. An appropriate method can be used for noise reduction processing.
[0046] In the following explanation, the integrated image 33 before noise reduction processing will be referred to as the pre-filtered image 33 (an example of image data before noise reduction processing), and the integrated image 34 created by applying noise reduction processing to the pre-filtered image 33 will be referred to as the post-filtered image 34 (an example of image data created by applying noise reduction processing to the pre-filtered image 33). The pre-filtered image 33 and post-filtered image 34 are examples of tuning data.
[0047] At this point, after the pre-filtered image 33 is created, the four images captured for each direction, and the four 3D images 32 created from those four images, become unnecessary. The control unit 21 deletes these images from the storage unit 22 after creating the pre-filtered image 33. After creating the filtered image 34, the pre-filtered image 33 becomes unnecessary. However, in Embodiment 1, component inspection data may be tuned using the pre-filtered image 33 after production of the substrate P has started. For this reason, the control unit 21 does not immediately delete the pre-filtered image 33 even after creating the filtered image 34, but deletes it when the inspection status of the substrate P meets predetermined conditions described later.
[0048] As shown in Figure 4, the operator displays the 3D shape of part E represented by the created filtered image 34 on the part inspection data creation screen 30. The operator creates part inspection data by setting the contour line 31 surrounding part E while looking at the displayed 3D shape of part E.
[0049] Here, since there are tolerances in the part shape, if the 3D shape represented by the filtered image 34 is used directly as part inspection data, there is a possibility that part E, which should be judged as good, may be judged as defective if there is a difference in part shape within the tolerance range. For this reason, the operator creates part inspection data with a margin so that the 3D shape represented by the part inspection data is slightly larger than the 3D shape represented by the filtered image 34.
[0050] However, if the margin is too large, part E, which should be judged as defective, may be judged as good. Therefore, operators set the margin to allow tolerances while ensuring that part E, which should be judged as defective, is judged as defective. For this reason, creating appropriate part inspection data generally requires high skill and experience. Even operators with high skill and experience cannot always create appropriate part inspection data, and inappropriate part inspection data may be created.
[0051] (5) Registration of parts inspection data Referring to Figure 6, the registration of created component inspection data will be explained. The component inspection data registration screen 40 shown in Figure 6 is a screen displayed by the management computer 3 that runs the data management program. The component inspection data registration screen 40 is a screen for operators to register component inspection data to be used for inspecting components E mounted on board P of a specific model. The component inspection data registered on the component inspection data registration screen 40 is transmitted from the management computer 3 to the inspection device 4 and used for inspection.
[0052] (6) Inspection of parts using parts inspection data When the inspection device 4 inspects a component E mounted on a substrate P, it detects the 3D shape of the component E using a phase shift method with the main camera 11 and four projectors 12, similar to when creating component inspection data. It then determines whether the component shape is good or bad by determining whether the detected 3D shape is contained within the 3D shape represented by the component inspection data.
[0053] When production of a particular model is completed, the inspection device 4 transmits information regarding the inspections performed during the production of that model to the server computer 2. Specifically, the inspection information includes the number of circuit boards P inspected, the number of circuit boards P judged as good, the number of circuit boards P judged as defective, the number of components E inspected, the number of components E judged as good, and the number of components E judged as defective. The inspection information is not limited to these, and any other information necessary for compiling the inspection status, as described later, is transmitted. The server computer 2 stores the received inspection information in the storage unit 22.
[0054] (7) Summary of the status of the tests Referring to Figure 7, the aggregation of inspection status will be explained. When production of a particular model is completed, the control unit 21 of the management computer 3 obtains inspection information for that model from the server computer 2, aggregates the inspection status for each component inspection data, and registers the aggregated inspection status in the database. Specifically, the inspection status includes the number of boards inspected, first-pass rate, defect rate, over-judgment rate, number of defective boards, number of defective components, process capability CPK, repeatability GR&R, etc. The inspection status is not limited to these and can be determined as appropriate.
[0055] The first-pass rate is the percentage of parts E that passed inspection on the first attempt out of the total number of parts E inspected. The first-pass rate does not include parts E that were corrected by the operator after their shape was altered. The defect rate is the percentage (%) of the number of defective parts E out of the total number of parts E inspected. The over-judgment rate is the percentage of parts E that were initially judged as defective but were later found to be good after visual inspection by the operator. The number of defective circuit boards is the number of circuit boards P that were found to be defective during inspection. For example, a circuit board is considered defective if the ratio of the number of defective components E to the total number of components E mounted on the circuit board P exceeds a predetermined value. The number of defective parts is the number of parts E that were found to be defective during inspection. Process capability CPK is a numerical value that represents the control status of a process. Repeatability GR&R is a statistical method that represents the accuracy and bias of the inspection device 4.
[0056] The inspection status summary screen 50 shown in Figure 7 displays the inspection status of a model for which production has ended. The inspection status summary screen 50 is displayed by the management computer 3, which runs the data management program. After summarizing the inspection status, the control unit 21 of the management computer 3 reads the summary results from the database and displays them on the inspection status summary screen 50 when the operator instructs it to display the inspection status summary screen 50. The inspection status summary screen 50 displays a list of component inspection data used to inspect the manufactured circuit board P. The list displays the inspection status for each component inspection data.
[0057] (8) Tuning of parts inspection data As mentioned earlier, parts inspection data may not always be appropriate. Using inappropriate parts inspection data can cause inspection results to deviate from the ideal. Therefore, operators check the inspection status on the inspection status summary screen 50, and if the inspection status deviates from the ideal, they determine that the parts inspection data may be inappropriate and tune the parts inspection data accordingly.
[0058] There are several possible reasons why the part inspection data is inappropriate. For example, the margins may be too small or too large. In addition, it is possible that the noise reduction parameters used when creating the filtered image 34 were inappropriate, causing some of the 3D shape of part E to be distorted, and that the part inspection data was created based on the filtered image 34 with some of the 3D shape distorted.
[0059] Refer to Figures 8A and 8B to conceptually explain the deformation of 3D shapes during noise reduction processing. Noise reduction processing is performed according to pre-set parameters. If these parameters are not appropriate, even non-noise areas may be removed as noise, which can cause deformation of part of the 3D shape of component E. For example, Figure 8A conceptually represents the filtered image 34 that should be created. Component E shown in Figure 8A has a cylindrical shape with a cylindrical section rising from the center of a disc-shaped base. Figure 8B conceptually represents the filtered image 34 in which part of the 3D shape of component E has been distorted during the noise reduction process. In the example shown in Figure 8B, the cylindrical section of part E is distorted and lowered due to inappropriate parameters.
[0060] If part inspection data is created based on filtered image 34, in which the 3D shape of part E is partially distorted, the detected 3D shape of part E may not fit within the 3D shape represented by the part inspection data. As a result, part E, which should be judged as good, may be incorrectly judged as defective. This can lead to the inspection situation deviating from the ideal situation.
[0061] Therefore, if the inspection situation deviates from the ideal situation, the operator tunes the part inspection data on the part inspection data creation screen 30. Specifically, the operator displays the 3D shape represented by the filtered image 34 on the part inspection data creation screen 30 and checks whether the margins are appropriate and whether the 3D shape is distorted. If the 3D shape is distorted, the operator adjusts the noise reduction processing parameters and recreates the filtered image 34 from the pre-filtered image 33. Then, the operator tunes the part inspection data while looking at the 3D shape represented by the recreated filtered image 34. In tuning the part inspection data, the operator makes corrections to the contour lines 31 and margins, etc.
[0062] (9) Remembering and deleting pre-filtered images As described above, if the inspection conditions deviate from the ideal conditions, the filtered image 34 may be recreated from the pre-filtered image 33 in order to tune the part inspection data. In this case, if the pre-filtered image 33 is not stored in the storage unit 22, the inspection device 4 must re-image part E and recreate the pre-filtered image 33, which reduces work efficiency. For this reason, the control unit 21 keeps the pre-filtered image 33 stored in the storage unit 22 even after creating the filtered image 34 without deleting it.
[0063] The control unit 21 then determines, based on the inspection status, whether or not to delete (an example of reduction) the pre-filtered image 33 stored in the memory unit 22. Specifically, the control unit 21 determines whether or not the inspection status is ideal by determining whether or not the inspection status satisfies predetermined conditions. If the inspection status satisfies the predetermined conditions, the control unit 21 decides to delete the pre-filtered image 33. In Embodiment 1, the operator can set predetermined conditions on the board information setting screen 60, which will be described next.
[0064] Referring to Figure 9, the board information setting screen 60 will be explained. The board information setting screen 60 is a screen displayed by the management computer 3 that executes the data management program. The board information setting screen 60 is a screen for operators to set various information about board P for each model of board P. Various information includes board size and predetermined conditions. For example, if the first pass rate is 90% or higher, the inspection situation is considered ideal. In this case, "first pass rate of 90% or higher" is set as a predetermined condition (an example of setting process). Alternatively, if the over-judgment rate is 5% or lower, the inspection situation is considered ideal. In this case, "over-judgment rate of 5% or lower" is set as a predetermined condition (an example of setting process).
[0065] The specified conditions may be one or more. If there are two or more specified conditions, the pre-filtered image 33 may be deleted if any one of those two or more specified conditions is met, or the pre-filtered image 33 may be deleted if all two or more of those conditions are met.
[0066] However, in Embodiment 1, the control unit 21 does not immediately delete the pre-filtered image 33 even if the inspection status meets predetermined conditions. Instead, it deletes the pre-filtered image 33 when the component inspection data created using that pre-filtered image 33 is registered on the component inspection data registration screen 40 as component inspection data to be used for inspecting models produced later. Specifically, as mentioned above, when production of a particular model is completed, the control unit 21 aggregates the inspection status for each component inspection data and registers it in the database. At this time, the control unit 21 determines whether the inspection status of each component inspection data satisfies the predetermined conditions set on the board information setting screen 60. If the inspection status satisfies the predetermined conditions, the control unit 21 turns on the delete flag for that component inspection data. The delete flag is a flag attached to the component inspection data; turning it on means that the pre-filtered image 33 used to create that component inspection data may be deleted, and turning it off means that it cannot be deleted. The default value for the delete flag is off.
[0067] Then, when component inspection data is registered on the component inspection data registration screen 40, the control unit 21 determines whether the deletion flag for the registered component inspection data is turned on. For example, suppose that component inspection data registered on the component inspection data registration screen 40 was used in the past to inspect a certain model, and the inspection status of that component inspection data when that model was produced met the predetermined conditions set for that model. In that case, the deletion flag for that component inspection data is set to on. Therefore, after the production of that model has ended, when that component inspection data is registered on the component inspection data registration screen 40 as component inspection data to be used for the inspection of another model, it is determined that the deletion flag is turned on.
[0068] If the delete flag is turned on, the control unit 21 displays the inquiry screen 41 shown in Figure 10. The inquiry screen 41 is a screen that accepts the operator's selection as to whether or not to delete the pre-filtered image 33 (tuning data) used to create the registered parts inspection data. The inquiry screen 41 also displays (as an example of notification) the inspection status of the parts inspection data when a certain model was produced (in other words, the inspection status when the delete flag was turned on).
[0069] The operator looks at the displayed inspection status and determines the likelihood of tuning the part inspection data in the future. If the operator determines that tuning is unlikely, they select [Yes]. If the operator selects [Yes], the control unit 21 deletes the pre-filtered image 33 (tuning data) used to create the part inspection data from the storage unit 22. If the operator selects [No], the pre-filtered image 33 is not deleted.
[0070] (10) Processes performed by the inspection device Referring to Figure 11, the flow of the process performed by the inspection device 4 will be explained. This process starts when the production of substrate P begins. In S101, the inspection device 4 reads the component inspection data used to inspect the model being produced. In S102, the inspection device 4 determines whether the component shape of component E mounted on the circuit board P is good or bad using the component inspection data read in S101.
[0071] In S103, the inspection device 4 determines whether production of a particular model has ended. If it has ended, it proceeds to S104; otherwise, it returns to S102 and repeats the process. In S104, the inspection device 4 transmits inspection-related information to the server computer 2. The server computer 2 stores the received inspection-related information in the storage unit 22. In S105, the inspection device 4 determines whether or not to produce a substrate P of a different model. If it does not produce one, it terminates the process; if it does produce one, it returns to S101 and repeats the process.
[0072] (11) Processes performed by the management computer The following describes the processes performed by the management computer 3, which runs the data management program: the process of turning on the deletion flag for parts inspection data, and the process of deleting the pre-filtered image 33.
[0073] (11-1) Process to turn on the delete flag for parts inspection data Referring to Figure 12, the process of turning on the deletion flag will be explained. As mentioned above, when the production of a particular model is completed, the inspection device 4 sends information about the inspection to the server computer 2. The server computer 2 notifies the management computer 3 that the production of a particular model has been completed. This process starts when the management computer 3 is notified by the server computer 2 that the production of a particular model has been completed.
[0074] In S201, the control unit 21 of the management computer 3 acquires inspection-related information from the server computer 2. In S202, the control unit 21 aggregates the inspection status based on the inspection information, using the same unit of part inspection data and the type of numerical value representing the inspection status (such as first-pass rate, defect rate, over-judgment rate, etc.).
[0075] In S203, the control unit 21 determines whether the aggregated inspection status meets predetermined conditions (an example of a determination process). If the predetermined conditions are met, the control unit 21 proceeds to S204; otherwise, it terminates the process. In S204, the control unit 21 turns on the part inspection data deletion flag.
[0076] (11-2) Process to delete the image before filtering Referring to Figure 13, the process of deleting the pre-filtered image 33 will be explained. This process is executed each time component inspection data is registered on the component inspection data registration screen 40.
[0077] In S301, the control unit 21 determines whether the deletion flag for registered part inspection data is on or off. If it is on, the process proceeds to S302; otherwise, the process ends. In S302, the control unit 21 displays the inquiry screen 41. In S303, the control unit 21 proceeds to S304 if [Yes] is selected on the inquiry screen 41, and terminates the process if [No] is selected. In S304, the control unit 21 deletes the pre-filtered image 33 (i.e., tuning data used to tune the registered parts inspection data) used to create the registered parts inspection data from the storage unit 22 (an example of reduction processing).
[0078] (12) Effects of the embodiment According to the data management program of Embodiment 1, if the inspection status using parts inspection data meets predetermined conditions (if it is determined in S203 that the predetermined conditions are met), the pre-filtered image 33 is deleted (S304). Therefore, by setting the ideal situation as a predetermined condition and deleting the pre-filtered image 33 of parts inspection data whose inspection status is in the ideal situation, it is possible to ensure that the pre-filtered image 33 of parts inspection data that is likely to be tuned in the future is not deleted, while free space is secured in the storage unit 22.
[0079] According to the data management program, deleting the pre-filtered image 33 frees up space in the storage unit 22.
[0080] According to the data management program, the tuning data is the unfiltered image 33 (image data) representing the 3D shape of part E. Generally, image data is large in size, so the effect of freeing up storage space in the memory unit 22 is significant.
[0081] According to the data management program, if the inspection status using the parts inspection data meets the predetermined conditions, the pre-filtered image 33 is deleted, while the filtered image 34 is not deleted. Therefore, even if the inspection status using the parts inspection data meets the predetermined conditions, the operator can still tune the parts inspection data using the filtered image 34. To free up space in the storage unit 22, the pre-filtered image 33 and the filtered image 34 may be compressed and stored in the storage unit 22. Because the pre-filtered image 33 has a lot of noise, it is more difficult to compress than the filtered image 34, and the amount of data after compression may be nearly 30 times that of the filtered image 34. For this reason, simply deleting the pre-filtered image 33 can have a significant effect in freeing up space in the storage unit 22.
[0082] According to the data management program, operators can set predetermined conditions, thus reducing the possibility that pre-filtered images 33 may not be deleted when they should be, or conversely, that they may be deleted when they shouldn't be.
[0083] According to the data management program, even if the inspection status meets predetermined conditions, the operator can choose whether or not to delete the pre-filtered image 33.
[0084] According to the data management program, when the operator is given the option to delete the pre-filtered image 33, the program informs the operator of the inspection status when the substrate P was produced using the component inspection data. Therefore, the operator can decide whether or not to delete the pre-filtered image 33 based on the inspection status.
[0085] <Embodiment 2> Embodiment 2 is a modification of Embodiment 1. In Embodiment 1 described above, if the control unit 21 of the management computer 3 determines in S301, the process of deleting the pre-filtered image 33, that the part inspection data deletion flag is on, it displays an inquiry screen 41 that accepts the option of whether or not to delete the pre-filtered image 33 (S302). In response to this, the control unit 21 according to Embodiment 2 displays the inquiry screen 41 when the operator logged into the management computer 3 has the authority to delete the pre-filtered image 33 (an example of a reduction authority).
[0086] Referring to Figure 14, the process flow for deleting the pre-filtered image 33 according to Embodiment 2 will be described. Here, processes that are substantially the same as those in Embodiment 1 are denoted by the same reference numerals and their descriptions are omitted.
[0087] In S401, the control unit 21 determines whether the operator logged into the management computer 3 has the authority to delete the pre-filtered image 33. If the operator has the authority to delete, the control unit 21 proceeds to S302; otherwise, it terminates the process.
[0088] According to the data management program of Embodiment 2, if the operator has the authority to delete the pre-filtered image 33, the program accepts an option to delete the pre-filtered image 33 or not, thereby preventing the deletion of pre-filtered images 33 that should not be deleted.
[0089] <Other Embodiments> The technology disclosed herein is not limited to the embodiments described above in the description and drawings, and the following embodiments, for example, are also included in the technical scope disclosed herein.
[0090] (1) In the above embodiment, data for inspecting the 3D shape of part E was given as an example of part inspection data, but the part inspection data is not limited to this. For example, the part inspection data may be data for inspecting the two-dimensional shape (2D shape) of part E as viewed from above.
[0091] (2) In the above embodiment, the pre-filtered image 33 and the filtered image 34 were given as examples of tuning data. Alternatively, the four images used to create the pre-filtered image 33 and the four 3D images 32 may also be stored in the storage unit 22 as tuning data. It can be appropriately decided which images used to create the parts inspection data are to be stored in the storage unit 22 as tuning data. The part inspection data may be a two-dimensional image (2D image) for inspecting the two-dimensional shape (2D shape) of part E. In that case, the 2D image may be stored as tuning data.
[0092] (3) In the above embodiment, when the inspection status satisfies predetermined conditions, the pre-filtered image 33 is deleted, while the filtered image 34 is not deleted. In contrast, the filtered image 34 may also be deleted when the inspection status satisfies predetermined conditions.
[0093] (4) In the above embodiment, the case of deleting the pre-filtered image 33 was given as an example of reducing the amount of data of the pre-filtered image 33. Alternatively, the amount of data of the pre-filtered image 33 may be reduced by compressing it, or by moving the pre-filtered image 33 to the storage unit of another computer. For example, if the pre-filtered image 33 is stored in the storage unit 22 without compression, the amount of data can be reduced by compressing it. The compression may be lossless or lossy. Generally, lossy compression has a higher compression ratio than lossless compression, so it is more effective in reducing the amount of data of the pre-filtered image 33.
[0094] (5) In the above embodiment, an example was given in which the operator is allowed to set predetermined conditions, but the predetermined conditions may be fixed in the data management program in advance.
[0095] (6) In the above embodiment, an example was given in which the operator is given the option to delete the pre-filtered image 33 when the inspection status satisfies predetermined conditions. In contrast, when the inspection status satisfies predetermined conditions, the pre-filtered image 33 may be deleted without giving the operator the option to delete the pre-filtered image 33.
[0096] (7) In the above embodiment, an example was given in which the inspection status is displayed on the inquiry screen 41 that accepts the selection of whether or not to delete the pre-filtered image 33, but the inspection status does not have to be displayed.
[0097] (8) In the above embodiment, even if the inspection status satisfies predetermined conditions, the pre-filtered image 33 is not deleted immediately, but is deleted when the part inspection data created using the pre-filtered image 33 is registered on the part inspection data registration screen 40. In contrast, the pre-filtered image 33 may be deleted immediately when the inspection status satisfies predetermined conditions.
[0098] (9) In the above embodiment, component inspection data used to inspect the component shape of the mounted component E was given as an example of inspection data used to inspect the substrate P on which the component E is mounted. However, the inspection data may be data other than component inspection data, as long as it is used to inspect the substrate P on which the component E is mounted.
[0099] (10) In the above embodiment, image data was used as an example of tuning data, but the tuning data is not limited to image data and may be data in any format.
[0100] (11) In the above embodiment, the height of component E was exemplified by the detection of the height of component E by the phase shift method, but the method for detecting the height of component E can be determined as appropriate. For example, the height of component E may be detected by the light section method.
[0101] (12) In the above embodiment, the server computer 2 and the management computer 3 are shown as separate computers, but they may be a single computer. [Explanation of Symbols]
[0102] 3: Management computer (an example of a computer, data management device, and circuit board inspection system) 4. Post-assembly visual inspection equipment (an example of a circuit board inspection device and circuit board inspection system) 21: Control Unit 22: Storage section 33: Image before filtering (an example of image data before noise reduction processing) 34: Filtered image (an example of image data created after noise reduction processing) E: Parts P: Board
Claims
1. A data management program for managing tuning data used to tune inspection data used for inspecting circuit boards on which components are mounted, After the inspection is completed, a compilation process is performed to obtain information about the inspection and compile the status of the inspection. A determination process to determine whether the status of the inspections aggregated in the aforementioned aggregation process satisfies predetermined conditions that the status of the inspections is in an ideal state, If the determination process determines that the predetermined conditions are met, a reduction process is performed to reduce the amount of tuning data stored in the storage unit. A data management program that causes a computer to execute data.
2. A data management program according to claim 1, The reduction process is a data management program comprising at least one of the following: a process for deleting the tuning data; a process for compressing the tuning data; and a process for moving the tuning data to another storage unit.
3. A data management program according to claim 1 or claim 2, The aforementioned inspection data is data for inspecting the shape of the part, A data management program wherein the tuning data is image data representing at least one of the two-dimensional and three-dimensional shapes of the component.
4. A data management program according to claim 3, The storage unit stores, as image data, the image data before noise reduction processing and the image data created by applying the noise reduction processing to the image data. The data management program is a data management program that reduces the amount of data in the image data before the noise reduction process is applied in the reduction process.
5. A data management program according to claim 1 or claim 2, A data management program that causes the computer to perform a setting process to accept the setting of predetermined conditions from an operator.
6. A data management program according to claim 1 or claim 2, A data management program that, in the reduction process, receives a choice from the operator whether or not to reduce the amount of tuning data when the inspection status using the inspection data satisfies the predetermined conditions, and reduces the amount of data if the choice to reduce is made.
7. A data management program according to claim 6, A data management program that, when the operator selects whether or not to reduce the amount of tuning data in the reduction process, notifies the operator of the inspection status when the board is inspected using the inspection data.
8. A data management program according to claim 6, A data management program that, in the reduction process described above, accepts an option from the operator whether or not to reduce the amount of tuning data, if the operator has the authority to reduce the tuning data.
9. A data management method for managing tuning data used for tuning inspection data used for inspecting circuit boards on which components are mounted, After the inspection is completed, there is a compilation step of obtaining information about the inspection and compiling the status of the inspection, A determination step is to determine whether the inspection status compiled in the aforementioned aggregation step satisfies predetermined conditions that the inspection status is in an ideal state, If the determination step determines that the predetermined conditions are met, a reduction step is performed to reduce the amount of tuning data stored in the memory unit. Data management methods, including those mentioned above.
10. A data management device for managing tuning data used for tuning inspection data used for inspecting circuit boards on which components are mounted, A storage unit for storing the aforementioned tuning data, Control unit and Equipped with, The control unit, After the inspection is completed, a compilation process is performed to obtain information about the inspection and compile the status of the inspection. A determination process to determine whether the status of the inspections aggregated in the aforementioned aggregation process satisfies predetermined conditions that the status of the inspections is in an ideal state, If the determination process determines that the predetermined conditions are met, a reduction process is performed to reduce the amount of tuning data stored in the storage unit. A data management device that performs the following actions.
11. A circuit board inspection system for inspecting circuit boards on which components are mounted, A data management device according to claim 10, A substrate inspection apparatus that inspects the substrate using the aforementioned inspection data, A circuit board inspection system equipped with the following features.