Data management device

Abstract

To reduce time and effort for management of component data.SOLUTION: A data management device 20 manages a plurality of mounting devices 12 having different models, the mounting devices 12 adsorb, recognize and mount components W to a substrate P according component data, the component data is a set of parameters, and the data management device 20 determines whether an individual parameter included in component data of a model which acquires an actual production result that satisfies predetermined determination reference can be commonized between different models.SELECTED DRAWING: Figure 6

Description

Technical Field

[0001] The present invention relates to a technique for managing component data of a mounting device.

Background Art

[0002] A mounting device has a mounting head for sucking components, and sucks, recognizes, and mounts components according to component data set for each component type. As a document related to the mounting device, there is Patent Document 1.

Prior Art Document

Patent Document

[0003]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0004] Component data is an aggregate of parameters used when mounting components on a substrate using a mounting device. Parameters for reducing the defect rate in the mounting process may vary depending on the model. When individually managing parameters for each model of the mounting device, it takes time to manage the data. For example, when changing parameters, change work is required for each individual model.

[0005] An object of the present invention is to automatically determine whether parameters can be shared among different models and reduce the labor of managing component data by sharing the parameters.

Means for Solving the Problems

[0006] A data management device that manages a plurality of mounting devices of different models determines whether individual parameters included in the component data of a model for which production results satisfying a predetermined determination criterion have been obtained can be shared among different models.

Effects of the Invention

[0007] According to the present invention, by sharing parameters, the labor of managing component data can be reduced.

Brief Description of the Drawings

[0008]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Modes for Carrying Out the Invention

[0009] <Embodiment 1> 1. Overall configuration of the production system FIG. 1 is a system configuration diagram of a production system S. The production system S includes a production line 10 and a data management device 20.

[0010] The production line 10 includes a printing machine 11, a mounting device 12, and an inspection device 13. The printing machine 11, the mounting device 12, and the inspection device 13 are connected by a conveyor, and the substrate P that has completed the work is sequentially conveyed from the upstream-side device (the left side in FIG. 1) to the downstream-side device (the right side in FIG. 1).

[0011] The printing machine 11 is a device that screen-prints solder paste on the pattern of the substrate P. The mounting device 12 is a device that mounts the component W on the substrate P after the printing process.

[0012] The inspection device 13 is a device that inspects the mounting state of the component W on the substrate P. As a result of the inspection, if there is no abnormality in the mounting state of the component W, the substrate P proceeds to the reflow process, and if there is an abnormality, the substrate P is treated as a defective substrate separately from the normal substrates.

[0013] The data management device 20 includes a management computer 21 and a database 30. The management computer 21 is provided with an input unit 22 such as a mouse and a keyboard, a display unit 23 such as a liquid crystal panel and a touch panel, a CPU, and a memory. The database 30 stores the component data of each mounting device 12.

[0014] The production line 10 and the data management device 20 are communicably connected via a wired or wireless communication network 14, and data can be transmitted and received between the two.

[0015] In this embodiment, three production lines 10 are connected to one data management device 20 via the communication network 14. The three production lines 10 may be production lines managed by one administrator or production lines managed by separate administrators. The number of production lines 10 connected to one data management device 20 may be one or a plurality.

[0016] 2. Configuration of the mounting device 12 As shown in FIGS. 2 and 3, the mounting device 12 includes a base 40, four component supply devices 41, a conveyor 42, a head unit 43, an X beam 51, a Y beam 52, a head moving unit 44, a substrate camera 45, two component cameras 46, a side camera 47, etc.

[0017] The substrate P is conveyed from the upstream side (the left side in FIG. 2) by the conveyor 42, and when the mounting of the component W is completed at the working position 48, it is conveyed to the downstream side (the right side in FIG. 2).

[0018] A plurality of feeders 49 are attached to the component supply device 41. Each feeder 49 supplies the component W to be mounted on the substrate P.

[0019] The head unit 43 supports a plurality of mounting heads 50 so as to be movable up and down and rotatable about an axis.

[0020] The X beam 51 supports the head unit 43 so as to be reciprocally movable in the X-axis direction. The Y beam 52 supports the X beam 51 so as to be reciprocally movable in the Y-axis direction.

[0021] The head moving unit 44 includes an X-axis motor 44X that moves the head unit 43 in the X-axis direction with respect to the X beam 51, and a Y-axis motor 44Y that moves the X beam 51 in the Y direction with respect to the Y beam 52.

[0022] The head unit 43 can be moved to an arbitrary position on the base 40 by driving the X-axis motor 44X and the Y-axis motor 44Y. The head unit 43 has a Z-axis motor 44Z (see FIG. 4) that moves the mounting head 50 in the Z direction with respect to the head unit 43.

[0023] As shown in FIG. 3, the mounting head 50 includes a shaft-shaped head shaft 55 and a suction nozzle 56. The head shaft 55 has a hollow shape, and an air supply path is provided in the axial center portion. The suction nozzle 56 is detachably attached to the tip (lower end) of the head shaft 55.

[0024] Negative pressure or positive pressure is supplied to the suction nozzle 56 from an air supply device (not shown) via the head shaft 55. The mounting head 50 adsorbs the component W using the suction nozzle 56 by supplying negative pressure, and releases the adsorbed component W by supplying positive pressure.

[0025] The substrate camera 45 is attached to the side surface of the head unit 43, and has an imaging element such as an image sensor, illumination such as an LED, and an optical system that forms an image of the light reflected by the imaging object on the light receiving surface of the imaging element. The component camera 46 and the side camera 47 have the same configuration.

[0026] The substrate camera 45 faces downward its imaging surface and shoots the substrate P from above. The position of the substrate P and the position of the lands for mounting the components W can be confirmed by the substrate camera 45.

[0027] The component camera 46 shoots the component W adsorbed by the mounting head 50 from below. The side camera 47 shoots the component W adsorbed by the mounting head 50 from the side. The size and adsorption state (adsorption position, adsorption angle, success or failure of adsorption) of the component W adsorbed by the mounting head 50 can be confirmed by the component camera 46 and the side camera 47.

[0028] FIG. 4 is a block diagram showing the electrical configuration of the mounting apparatus 12. The controller 60 is a control device of the mounting apparatus 12. The controller 60 has a CPU 61 and a memory 63.

[0029] To the controller 60, each device such as the conveyor 42, the motor control unit 65, the substrate camera 45, the component camera 46, the side camera 47, and the operation panel 64 is connected.

[0030] The memory 63 stores a mounting program for executing the mounting operation of the component W on the substrate P and a conveyance program for the substrate P.

[0031] After the start of production of the substrate P, the controller 60 controls the conveyor 42 and the head unit 43 according to the conveyance program and the mounting program. The conveyor 42 sends the substrate P to the working position 48 at the center of the base, and the head unit 43 performs the mounting operation of the component W on the substrate P. Note that production means manufacturing a substrate P with components mounted thereon by mounting the component W on the substrate P without components mounted.

[0032] 3. Component Data and Its Commonization On the substrate P, a large number of components W such as chip resistors, capacitors, and ICs are mounted. In the database 30, the initial values of the component data are stored for each component type.

[0033] Component data is data for performing the "suction operation", "recognition operation", and "mounting operation" of component W in the mounting apparatus 12, and is a collection of parameters. Specific examples of the parameters are shown below.

[0034] (1) Size X (2) Size Y (3) XY Speed (4) Suction Speed (5) Mounting Speed (6) Nozzle Used (7) Disposal Method (8) Illumination Level

[0035] The above (1) Size X and (2) Size Y are the dimensions of component W in the X direction and Y direction, respectively. The (3) XY Speed is the speed at which the head unit 43 supplied with component W from the feeder 49 moves above the mounting position on the substrate P. The XY Speed is expressed as a percentage of the capacity of the mounting apparatus 12, and a value in 10% increments is selected.

[0036] (4) The suction speed and (5) the mounting speed are the speeds at which the suction nozzle 56 rises or falls when component W is being suctioned or mounted. The (6) nozzle used is information such as the type and lot number of the suction nozzle 56 used when mounting component W. The (7) disposal method is the method of disposing of component W that has failed to be mounted. The (8) illumination level is a numerical value (%) representing the intensity of the light emitted by the lighting devices provided in each camera 45 to 47.

[0037] Figure 5 is a diagram showing the procedure for expanding component data for the mounting apparatus 12. In this embodiment, the case of expanding component data for three models of mounting apparatuses 12A, 12B, and 12C will be described. Also, for the sake of simplicity, the case will be described assuming that the parameters included in the component data are the three above (1) to (3).

[0038] The database 30 stores the initial values of the component data. The initial values of the component data are commonly applied to all models.

[0039] Before starting production, the management computer 21 accesses the database 30 to read the initial values of the component data and sends them to each mounting device. That is, it sends them to the mounting devices for model A, model B, and model C. Hereinafter, the mounting devices 12A to 12C for each model will be abbreviated as each model A to C.

[0040] When the operator receives the component data for each of models A to C, the operator uses the component data to perform a trial placement of component W and tunes the component data to be suitable for each of models A to C. In FIG. 5, "PartsA0" represents the initial value of the component data, and "PartsA1" to "PartsA3" represent the component data after tuning. The component data after tuning is stored in the memory 62 of each mounting device 12.

[0041] In this embodiment, when producing the substrate P using the component data after tuning and there is a model for which a production result satisfying a predetermined determination criterion is obtained, the commonization of the component data is determined for the component data of that model.

[0042] The determination criterion can be determined based on, for example, the following two elements. (A) The number of mounting points N (B) The defective rate Q

[0043] In this embodiment, N = 1,000,000 and Q = 5 ppm. That is, when 1 million points of the same component W are mounted and the number of components determined to be mounting defects is 5 or less, it is determined that the production result satisfies the determination criterion.

[0044] Then, as shown in FIG. 5, when a production result satisfying the determination criterion is obtained for a certain model, the commonization of the component data is determined for that model.

[0045] Hereinafter, with reference to FIG. 6, an example of sharing component data will be described. In the database 30, component data (PartsA0) specific to the type of component W is registered as the initial value of the shared component data. The shared component data is component data that is commonly applied among different models. The shared component data is an aggregate of common parameters that are commonly applied among different models.

[0046] After production starts, when a model whose production results meet the criteria appears, the management computer 21 reads out the component data applied to that model. In the example of FIG. 6, model A first meets the criteria, and the management computer 21 reads out the component data (PartsA1) of model A.

[0047] Then, the management computer 21 rewrites the shared component data (PartsA0) registered in the database 30 with the read component data (PartsA1).

[0048] In the example of FIG. 6, for the shared component data, size X is rewritten from "1.10" to "1.00", size Y is rewritten from "0.60" to "0.50", and the XY speed does not change from "100".

[0049] Also, since the component data of model A is common with the shared component data, for the component data of model A, size X is registered as "common", size Y is registered as "common", and the XY speed is registered as "common".

[0050] After that, when the production results of another model meet the criteria, the management computer 21 reads out the component data of that model and determines whether to share the component data.

[0051] In the example of FIG. 6, following model A, model B meets the criteria, and the management computer 21 reads out the component data (PartsA2) of model B.

[0052] Then, the management computer 21 compares the parts data (PartsA2) of model B with the common parts data (PartsA1) registered in the database 30, and determines the commonality of each parameter. Specifically, for each parameter, if they are the same, they are registered as common parameters, and if they are different, they are registered as unique parameters of model B.

[0053] Here, "the same" includes both cases where the two parameters to be compared are exactly the same and cases where the two parameters are within a pre-specified error range. For example, in the case of a parameter of the type where one is selected from multiple options, if the same option is selected, it can be determined as the same parameter. For example, since the XY speed is selected from values in 10% increments, it is a parameter of the type to be selected.

[0054] On the other hand, the part sizes (size X and size Y) are measurement values obtained from the images taken by the part camera 46, and it is rare for them to be exactly the same. Therefore, the error range is set to, for example, 10%, and if one measurement value is within the range of ±10% of the other, it is determined to be the same. Which measurement value to adopt as the common parameter when it is determined to be the same can be arbitrarily determined by the operator.

[0055] When comparing the parameters of the common parts data that have already been determined for commonality with the parameters of the parts data that have not been determined for commonality, the parameters of the common parts data may be adopted as the common parameters.

[0056] In the example of FIG. 6, among the parts data (PartsA2) of model B, size X and size Y are common with the common parts data (PartsA1), so they are registered as "common". Since the XY speed is different, it is registered as "90" as a unique parameter that cannot be made common. The parts data including the unique parameters branches off from the common parts data and is registered as unique parts data.

[0057] After that, when another model meets the criteria, the management computer 21 reads out the parts data of that model, compares it with the common parts data, and determines whether the parts data can be shared.

[0058] Figure 7 shows an example of sharing parts data that is different from that in Figure 6. In the example of Figure 6, the common parts data (PartsA0) registered in the database 30 was rewritten with the parts data (PartsA1) of model A whose production record first met the criteria.

[0059] In the example of Figure 7, the common parts data (PartsA0) registered in the database 30 is not rewritten. For the parts data (PartsA1) of model A that first meets the criteria, it is compared with the common parts data to determine whether the parts data can be shared. That is, similar to the parts data of model B that second meets the criteria in Figure 6, sharing is determined.

[0060] In the example of Figure 7, when model A first meets the criteria, the parts data (PartsA1) of model A is compared with the common parts data (PartsA0). Among the parts data (PartsA1) of model A, since the sizes X and Y are different from the values of the common parts data (PartsA0), these are registered as unique parameters. Since the XY speed has the same value as the common parts data, it is registered as "common". The parts data of model A including the unique parameters is registered as unique parts data.

[0061] After that, when model B meets the criteria, the parts data (PartsA2) of model B is compared with the common parts data (PartsA0). Since each parameter included in the parts data of model B is not the same as each parameter of the common parts data, all parameters of PartsA2 are registered as unique parameters. The parts data of model B including the unique parameters is registered as unique parts data.

[0062] FIG. 8 is a flowchart of the component data sharing process. The component data sharing process consists of seven steps S10 to S70.

[0063] The management computer 21 reads the shared component data of the component W to be mounted from the database 30 (S10). This shared component data serves as the initial value. Next, the results of parameter adjustment performed for each model are reflected in the component data (S20). Specifically, based on the tuning results described above, the component data for each of the models A to C is rewritten.

[0064] Next, the operator inputs and sets a predetermined criterion into the management computer 21 (S30). Next, the mounting apparatus 12 produces the substrate P (S40). Each mounting apparatus mounts the component W based on the component data tuned for each model. The production results obtained by aggregating the mounting results are transmitted to the management computer 21.

[0065] The management computer 21 determines for each model whether the production results have achieved the criterion (S50). If the criterion is not satisfied (S50: NO), the process returns to S40. If the criterion is satisfied (S50: YES), the process proceeds to S60.

[0066] The management computer 21 compares the component data applied to the models that have satisfied the criterion with the shared component data, and determines whether each parameter can be shared (S60).

[0067] Next, the management computer 21 registers the parameters that can be shared as common parameters in the database 30 (S70), and ends the sharing of the component data.

[0068] <Effect> Implementation devices of different models may have different performances. For example, in Model A and Model B, the maximum moving speed of the head unit 43 may be different. In this case, even if the parameter "XY speed" included in the component data is set to 50%, the speed as an absolute value is different between 50% of the maximum value of Model A and 50% of the maximum value of Model B. Also, when the performances and positional relationships of cameras and lighting devices are different between Model A and Model B, even if the sizes of the same components are measured, the same measurement results may not be obtained.

[0069] Therefore, when the implementation device owned by the user includes multiple models, even if the component data with good production results for a certain model is directly expanded to other models, the component data may not be suitable for other models.

[0070] If component data is created and individually managed for each model, production can be carried out using the optimal component data for each model. However, if there are many models and types of parameters included in the component data, it is time-consuming to manage the component data.

[0071] In the configuration of the present invention, the data management device 20 automatically determines the generalization of individual parameters included in the component data between different models. When the parameters are generalized, when changing the values of the parameters, the changed parameters can also be deployed to the implementation devices of different models. Thereby, compared with the case of individually managing the component data, the labor of managing the component data can be reduced.

[0072] <Embodiment 2> In Embodiment 1, when the production results of any one model meet the judgment criteria, the generalization of the component data was carried out each time. Embodiment 2 is different from Embodiment 1 in that the generalization of the component data is carried out when the production results of multiple models meet the judgment criteria.

[0073] An example of the generalization of component data in the data management device of Embodiment 2 will be described with reference to FIG. 9.

[0074] In the example of FIG. 9, in the initial state, for each of models A to C, component data is applied individually for each model. The component data to be applied is PartsA0 registered in the database 30. Then, tuning is performed for models A to C, and production is carried out using the component data after tuning.

[0075] Production is started for each model. Suppose that first, the production results of model A satisfy the judgment criteria. At this time, the management computer 21 determines whether the component data of model A contains unique parameters. In the example of FIG. 9, all the parameters of model A are unique parameters. At this time, the management computer 21 rewrites the component data of model A in the database 30 to the component data (PartsA1) used in model A. By doing so, since the component data when the production results satisfying the judgment criteria are obtained for model A can also be applied to model A hereafter, component data with proven performance can be retained for each model.

[0076] Next, when a model that satisfies the judgment criteria appears, the component data is read from that model. In the example of FIG. 9, as the second model, model B satisfies the judgment criteria. The management computer 21 reads the component data (PartsA2) applied to model B and rewrites the component data of model B in the database 30 to the component data.

[0077] Since multiple models (model A, model B) satisfy the judgment criteria, the management computer 21 creates common component data and determines whether the parameters of each model can be made common. In the example of FIG. 9, among the parameters included in the two component data (PartsA1, PartsA2) that satisfy the judgment criteria, size X is the same at "1.00". Size Y is also the same at "0.50".

[0078] The management computer 21 determines that size X "1.00" and size Y "0.50" are parameters that can be made common and registers them as the common parameters of the common component data.

[0079] Among the parameters, the XY speed is "100" for model A and "90" for model B. The management computer 21 determines that the XY speed is a parameter that is not the same and cannot be shared, and does not register it as a common parameter.

[0080] Among the parameters of model A, the values of size X and size Y are the same as the common component data, so they are each registered as "common" in the component data. The same applies to size X and size Y of model B. On the other hand, since there is no parameter for the common component data for the XY speed, it is registered as a unique parameter for each model.

[0081] In the configuration of Embodiment 2, when production results that meet the determination criteria are obtained for a plurality of models, the data management device 20 can automatically determine whether the parameters can be shared.

[0082] <Other Embodiments> (1) In the above embodiment, the mounting points N and the defect rate Q are used as the determination criteria. The determination criteria are not limited to these, and other criteria may be used.

[0083] (2) In the above embodiment, the case where the data management device 20 manages 3 types of models of the mounting device 12 and 3 units is illustrated, but the number of models and the number of units are not limited to these values.

Explanation of Reference Numerals

[0084] 10: Production line 11: Printer 12: Mounting device 12A, 12B, 12C: Mounting device 20: Data management device 21: Management computer 30: Database

Claims

1. A data management device for managing a plurality of mounting devices of different models, wherein the mounting device adsorbs, recognizes, and mounts components according to component data, the component data being an aggregate of a plurality of parameters, the data management device determines whether individual parameters included in the component data of a model for which production results satisfying a predetermined criterion are obtained can be shared among different models, determines initial values of shared component data to be applied among different models, when the production results for each model satisfy a predetermined criterion, among the parameters included in the component data of the model for which production results are obtained, parameters that can be shared with the parameters included in the initial values of the shared component data and parameters that cannot be shared are determined as unique parameters specific to the model for which production results are obtained, manages the unique parameters for each model, after production starts, when the production results for each model satisfy the predetermined criterion a plurality of times, compares the shared component data with the component data of models from the second model onwards for which production results are obtained, determines parameters that can be shared as common parameters, and determines parameters that cannot be shared as unique parameters of the model for which production results are obtained, a data management device.

2. The data management device according to claim 1, wherein when the production results for each model satisfy the predetermined criterion for the first time after production starts, the parameters included in the component data of the model for which production results are obtained are determined as the common parameters included in the shared component data, a data management device.

3. The data management device according to claim 1, wherein when the production results for each model satisfy the predetermined criterion for the first time after production starts, the component data of the model for which production results are obtained and the shared component data are compared, and parameters that cannot be shared are determined as unique parameters of the model for which production results are obtained, a data management device.

Images