Data management device and data management system

Abstract

To provide a data management device and the like which can update component data for recognizing a component more easily than a conventional technique.SOLUTION: A data management device 100 comprises: a data creation unit 120 which creates first component data used for recognition of a component from an image of the component imaged by an imaging unit 110; and a recognition unit 142 which recognizes the component included in the image of the component imaged by the imaging unit 141 by using the first component data. When the recognition unit 142 cannot recognize the component by using the first component data, on the basis of second component data suitable to recognition of the component created on the basis of the first component data and recognition error information indicating the content of an error generated when the recognition unit 142 recognizes the component, the data creation unit 120 updates at least the first component data of the one or more pieces of component data including the first component data created by the data creation unit 120.SELECTED DRAWING: Figure 3

Description

[Technical Field]

[0001] The present invention relates to a data management device that manages part data used to recognize parts, and a data management system that includes a plurality of such data management devices. [Background technology]

[0002] Conventionally, a technique has been proposed for automating the creation of part data used to recognize parts (see, for example, Patent Document 1).

[0003] Patent Document 1 discloses a method for creating component data suitable for component recognition by correcting existing component data based on information input by an operator indicating whether or not correction is required. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] International Publication No. 2018 / 146818 Summary of the Invention [Problem to be solved by the invention]

[0005] It is desirable that this type of part data be easily updated even after it has been created. The present invention provides a data management device and the like that can update part data for recognizing parts more easily than before. [Means for solving the problem]

[0006] A data management device according to one embodiment of the present invention includes a data creation unit that creates first component data used to recognize a component from an image of the component captured by a first imaging unit, and a recognition unit that recognizes the component included in the image of the component captured by a second imaging unit using the first component data. If the recognition unit is unable to recognize the component using the first component data, the data creation unit updates at least the first component data among one or more component data including the first component data created by the data creation unit, based on second component data created based on the first component data, the second component data being suitable for recognizing the component, and recognition error information indicating the content of an error that occurred when the recognition unit recognized the component.

[0007] Furthermore, a data management system according to one aspect of the present invention includes the plurality of data management devices described above, and a server device connected to the plurality of data management devices via a communication network, wherein the server device has a shared data storage, a communication unit for communicating with the plurality of data management devices, and a control unit for receiving, via the communication unit, component data stored in the data storage of each of the plurality of data management devices and the recognition error information linked to the component data, and storing the component data in the shared data storage, wherein the recognition error information includes progress information indicating a recognition result by the recognition unit using updated component data that is component data updated by the data creation unit, and wherein the control unit When the control unit receives the updated part data from one of the plurality of data management devices via the communication unit, it determines whether or not to update the part data corresponding to the updated part data that is stored in the data storage owned by another of the plurality of data management devices, based on the history information linked to the updated part data, and if it determines to update, it transmits the updated part data and instruction information indicating an instruction to update the part data corresponding to the updated part data that is stored in the data storage owned by the other data management device to the updated part data to the other data management device via the communication unit.

[0008] These comprehensive or specific aspects may be realized as a system, a method, an integrated circuit, a computer program, or a computer-readable recording medium such as a CD-ROM, or may be realized as any combination of a system, a method, an integrated circuit, a computer program, and a recording medium. [Effects of the Invention]

[0009] According to the present invention, it is possible to provide a data management device or the like that can update part data for recognizing parts more easily than before. [Brief explanation of the drawings]

[0010] [Figure 1] FIG. 1 is a schematic diagram showing a specific example of a data management system according to an embodiment. [Figure 2] FIG. 2 is a schematic diagram showing a specific example of a production system according to an embodiment. [Figure 3] FIG. 3 is a block diagram showing the configuration of a data management system according to an embodiment. [Figure 4] FIG. 4 is a diagram illustrating an example of part data according to the embodiment. [Figure 5] FIG. 5 is a flowchart illustrating a processing procedure of the data management device according to the embodiment. [Figure 6] FIG. 6 is a flowchart showing a part data update process executed by the data management device according to the embodiment. [Figure 7] FIG. 7 is a diagram for explaining the part data update process executed by the data management device according to the embodiment. [Figure 8] FIG. 8 is a flowchart showing the processing procedure of the data management system according to the embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0011] The following describes in detail a data management device and the like according to an embodiment of the present invention with reference to the drawings. Each of the embodiments described below represents a specific example of the present invention. Therefore, the numerical values, shapes, materials, components, component arrangements and connection configurations, steps, and step sequences shown in the following embodiments are merely examples and are not intended to limit the present invention. Therefore, among the components in the following embodiments, components that are not described in the independent claims that represent the highest concept of the present invention will be described as optional components.

[0012] Furthermore, each drawing is a schematic diagram and is not necessarily drawn to precise scale, dimensions, etc. Furthermore, in each drawing, substantially the same components are given the same reference numerals, and duplicated explanations may be omitted or simplified.

[0013] (Embodiment) [composition] First, the configuration of the data management system according to the embodiment will be described.

[0014] FIG. 1 is a schematic diagram showing a specific example of a data management system 300a according to an embodiment.

[0015] The data management system 300a is a system that manages component data for recognizing components included in images (also called component images) generated by capturing images of components by the production system 500. Managing component data here means creating component data, updating the created component data, storing this component data, etc.

[0016] The data management system 300a includes a server device 200 and one or more production systems 500. Although two production systems 500 are illustrated in Fig. 1, the number of production systems 500 included in the data management system 300a may be one, or three or more.

[0017] The production system 500 is a component mounting system that recognizes components based on an image (also called a component image) generated by capturing an image of the component and component data, and mounts the component on a board based on the recognition result.

[0018] Examples of components include chip components, IC (Integrated Circuit) components, BGA (Ball Grid Array) components, connector components, mini-mold components, and irregular-shaped components.

[0019] The substrate may be, for example, a printed wiring board.

[0020] The production system 500 is a system that manufactures various circuit boards such as control circuits and power supply circuits by mounting components on the boards.

[0021] In this embodiment, the production system 500 is described as being used to manufacture circuit boards, but the present invention is not limited to this and may be used for various operations for manufacturing various products such as electronic devices, automobiles, etc. For example, the production system 500 may be used for various operations such as press-fitting an element into a board, processing an element to attach an element to a board, and fastening an element.

[0022] FIG. 2 is a schematic diagram showing a specific example of a production system 500 according to an embodiment.

[0023] The production system 500 includes, for example, an imaging unit (first imaging unit) 110, data storage 130, production equipment 140A, 140B, and 140C, and computers 510A and 510B. In this embodiment, the imaging unit 110 and production equipment 140A, 140B, and 140C are connected to the computers 510A and 510B and data storage 130 via a communication network.

[0024] The imaging unit 110 is a camera that captures images of components to create component data. The imaging unit 110 is, for example, an offline camera device that is not connected to the production equipment 140A-140C as a device for producing products. The imaging unit 110, for example, captures an image of the component to generate an image (image data) including the component, and transmits the generated image to the computer 510A. The image generated by the imaging unit 110 is used to create information used in the production system 500, such as component data used in the production equipment 140A-140C.

[0025] It should be noted that the imaging unit 110 does not have to be an offline camera device.

[0026] Data storage 130 is a storage device that stores information used in production system 500, such as component data. Data storage 130 is realized, for example, by an HDD (Hard Disk Drive). For example, data storage 130 stores component data, production data, image data, and the like. The production data specifies, for each component, the mounting position and mounting angle of the component on the board. The image data stores multiple pieces of image information that associate images of components captured by imaging unit 110 and imaging unit 141 (see FIG. 3 ) with information that identifies the image, such as the type of component, the device that captured the image, and the date and time of capture.

[0027] The production equipment 140A, 140B, and 140C are devices that produce products. The production equipment 140A, 140B, and 140C are, for example, mounting devices that mount components on boards. For example, the production equipment 140A, 140B, and 140C picks up components supplied by a feeder using a nozzle provided in a mounting head, generates an image by capturing an image of the component held by the nozzle using a component recognition camera, recognizes the component based on the image and component data stored in the data storage 130 (more specifically, recognizes the position, shape, orientation, etc. of the component), and mounts the component on the board based on the recognition result. Note that the component recognition camera may be provided in another device connected to the production equipment 140A to 140C.

[0028] It should be noted that the production equipment 140A, 140B, and 140C do not have to be mounting devices.

[0029] Furthermore, although Figure 2 shows three units of production equipment 140A, 140B, and 140C, the number of units of production equipment 140A, 140B, and 140C may be one, two, or four or more, and is not particularly limited.

[0030] Computer 510A is a data creation device for creating information used in production system 500, such as parts data used in production facilities 140A to 140C.

[0031] The computer 510B is a control device for controlling the production equipment 140A, 140B, and 140C. For example, the computers 510A and 510B are each a personal computer having a mouse, a keyboard, a display, etc., and are equipped with a communication interface for communicating with the imaging unit 110, the data storage 130, the production equipment 140A, 140B, and 140C, etc., a non-volatile memory in which a program is stored, a volatile memory that is a temporary storage area for executing the program, an input / output port for transmitting and receiving signals, a processor for executing the program, etc.

[0032] Computer 510A creates component data based on, for example, an image acquired from imaging unit 110 and information indicating the position, shape, etc. of a component included in the image received from an operator, etc. (for example, information regarding the position, shape, etc. of a characteristic portion such as an electrode of the component). Computer 510A stores the created component data in data storage 130 and transmits it to computer 510B.

[0033] Computer 510B controls production equipment 140A, 140B, and 140C so that production equipment 140A, 140B, and 140C recognize the type of component, as well as the position and orientation of the component, by recognizing the characteristic parts of the component in the image using the received component data, and then mounts the recognized component on a board.

[0034] Although two computers 510A and 510B are shown in FIG. 2, the processes executed by computers 510A and 510B may be performed by a single computer.

[0035] Each production system 500 creates component data for recognizing components, recognizes the components based on the created component data, and mounts the components on a board. Each production system 500 also transmits image data (for example, image data captured by at least one of the imaging units 110 and 141), the created component data, information indicating the content of an error that occurred when recognizing the components (recognition error information), and information regarding quality, in other words, information indicating the mounting quality (mounting state) of the mounted components, to a cloud storage device, a server device, or the like.

[0036] Each production system 500 may transmit this information not to a server device on the cloud, but to a server device within the factory where the production system 500 is located, or to a server device outside the factory (for example, a server device contracted by the factory, or a server device owned by the vendor of the production system 500).

[0037] In this embodiment, the server device 200 is described as having a storage (shared data storage 230, which will be described later).

[0038] The server device 200 collects (receives) information such as part data and recognition error information from each production system 500, selects part data that is appropriate for recognizing the part (for example, has the highest success rate of recognition) based on the part data and recognition error information received from each production system 500, and transmits the selected part data to each production system 500 as the analysis result.

[0039] When each production system 500 receives the part data from the server device 200, it changes (updates) the created part data to the received part data.

[0040] As a result, the most appropriate part data among the part data created by each production system 500 is shared among the production systems 500. Therefore, parts can be appropriately recognized across all of the multiple production systems 500 included in the data management system 300a.

[0041] FIG. 3 is a block diagram showing the functional configuration of a data management system 300 according to an embodiment.

[0042] The data management system 300 includes a plurality of data management devices 100 and a server device 200. The plurality of data management devices 100 and the server device 200 are communicably connected via a communication network 400 such as the Internet.

[0043] The data management devices 100 and the server device 200 may be connected to each other so as to enable wired or wireless communication. The communication standard used for communication via the communication network 400 may be determined arbitrarily and is not particularly limited.

[0044] Although FIG. 3 shows two data management devices 100 included in the data management system 300, the number of data management devices 100 included in the data management system 300 is not particularly limited.

[0045] The data management device 100 is, for example, the production system 500 shown in Figures 1 and 2, and is a device that recognizes components using images generated by capturing images of the components and component data, and performs predetermined processing on the recognized components, such as mounting the recognized components on a board.

[0046] The data management device 100 includes an imaging unit 110 , a data creation unit 120 , a data storage 130 , a recognition device 140 , and a communication unit 150 .

[0047] The imaging unit 110 is a camera that captures an image of a component to generate an image for creating component data.

[0048] Data creation unit 120 is a processing unit that creates component data using images generated by imaging unit 110. Data creation unit 120 creates, for example, one or more component data items including first component data used to recognize a component from an image of the component captured by imaging unit 110. For example, imaging unit 110 captures images of multiple components individually to generate multiple images, each including a component. Data creation unit 120 creates component data corresponding to each of the multiple images. In this way, data creation unit 120 creates, for example, multiple component data items.

[0049] The number of pieces of component data created by data creation unit 120 may be one or more. Data creation unit 120 may create component data for the number of component types recognized by recognition device 140, which will be described later.

[0050] The data creation unit 120 is, for example, the computer 510A shown in FIG.

[0051] FIG. 4 is a diagram illustrating an example of part data according to the embodiment.

[0052] The part data includes, for example, part shape data, part feature data, and recognition operation parameters.

[0053] The component shape data is information (parameters) that indicates the shape of a component. The component shape data includes, for example, type information that indicates the type of the component, information on the shape of the component body (e.g., external dimensions), and information on the shape of the electrodes provided on the component (e.g., leads, bumps). The type information includes, for example, information on the component manufacturer, information on the component lot (e.g., model, specifications, destination, etc.), etc.

[0054] Parts of the same type are parts that have the same configuration, such as parts of the same model from the same manufacturer (e.g., parts with the same parameters such as dimensions and characteristics), parts with electrodes of the same shape and the same body shape, and parts with the same information indicating the characteristic parts of the parts (e.g., parts with the same position of the characteristic parts).

[0055] The component feature data is information (parameters) that indicates the position, spacing (pitch), size, etc. of the feature parts of the component in the image (leads, bumps, corners of the component's outer shape, etc.). For example, the component feature data includes information that indicates a shape class (lead, bump, corner, rectangle, etc.) that is pre-classified according to the feature parts. The information that indicates the shape class is, for example, information that indicates a component group.

[0056] The information indicating the part group is, for example, set for each part data and is information indicating a group of parts of the same type. For example, part data belonging to the same part group is part data common to parts of the same type for recognizing each of the parts of the same type. For example, part data for recognizing parts of the same type is part data in which at least one piece of information, such as the shape class and position, included in the part feature data is the same.

[0057] Note that the part data for recognizing parts of the same type is not limited to this, and may be part data including the same types of parameters for information such as part shape data.

[0058] The part group to which the part data belongs may be set arbitrarily. The part group may be set by a user, or may be set by a processing unit that uses AI (Artificial Intelligence) technology or the like and that is provided in the data management device 100.

[0059] For example, the one or more pieces of part data created by data creation unit 120 include multiple pieces of same-type part data for recognizing parts of the same type. In other words, the one or more pieces of part data created by data creation unit 120 include multiple pieces of part data belonging to the same part group. For example, the first part data and the same-type part data for recognizing parts of the same type as the part for which the first part data is used to recognize the part belong to the same part group.

[0060] The recognition operation parameters are information (parameters) that indicate the operating conditions of the imaging unit 141 and the like when recognizing components in the production equipment 140A to 140C. The recognition operation parameters include, for example, information that indicates the type of imaging unit 141, information that indicates the amount of light (illumination lamp value) of illumination when imaging the component by imaging unit 141, and information about the time required for recognition processing (recognition speed, which is the moving speed of the nozzle when imaging). Note that the information about the amount of light of illumination and the time required for recognition processing may be a numerical value (1% to 100%) or may be an option (high, low, high speed, slow speed, etc.).

[0061] For example, the data creation unit 120 displays an image on a display device such as a display (not shown) provided in the data management device 100. The operator checks the image and inputs the above-mentioned various parameters of the components included in the image by operating an operation device (not shown) such as a mouse or keyboard provided in the data management device 100. Based on the input parameters, the data creation unit 120 generates component data by converting the data format etc. so that the recognition device 140 can read it.

[0062] Alternatively, for example, the data creation unit 120 extracts feature parts (e.g., the above-mentioned parameters) of the component included in the image acquired from the imaging unit 110 using a machine learning model (inference model) that uses a neural network such as deep learning, and generates component data by associating the above-mentioned recognition operation parameters with information about the extracted feature parts. The data format of the information about the extracted feature parts may be different from a data format readable by the recognition device 140. In this case, the data creation unit 120 may generate component data by converting the information into a predetermined data format readable by the recognition device 140. The inference model is, for example, a model that receives an image including a component as input and outputs information about the feature parts of the component. The information about the feature parts is, for example, the above-mentioned component feature data, such as information indicating the type (lead, bump, etc.) of electrodes of the component, the number, position, size, arrangement pitch, etc.

[0063] The data creating unit 120 stores the created component data in the data storage 130 .

[0064] Data storage 130 is a storage device that stores the component data created by data creation unit 120. Furthermore, for example, data storage 130 stores at least one of image data, recognition error information, information on quality (more specifically, information indicating the mounting state of a component that has been recognized by recognition unit 142 using second component data described below on a board on which the component is mounted), and second component data described below.

[0065] The recognition device 140 is a device that recognizes a part using part data and executes a predetermined process on the part. The recognition device 140 is, for example, a computer 510B and a production facility 140A.

[0066] The recognition device 140 includes an imaging unit (second imaging unit) 141, a recognition unit 142, and an execution unit 143.

[0067] The imaging unit 141 is a camera that captures an image of a component and generates an image.

[0068] The recognition unit 142 is a processing unit that uses component data to recognize a component included in an image of the component captured by the imaging unit 141. For example, when the recognition unit 142 is unable to recognize a component (in other words, when a recognition error occurs), the recognition unit 142 generates recognition error information.

[0069] The recognition error information is information indicating the content of an error that occurs when the recognition unit 142 recognizes a component. The recognition error information is information indicating, for example, an abnormality such as an inability to detect the component's features, an abnormality related to the pitch of the electrodes of the component, or an abnormality in the number of the electrodes. If multiple abnormalities occur, such as an abnormality in the electrode pitch or the number of electrodes, the recognition error information may include information indicating multiple abnormalities.

[0070] Anomalies related to the pitch of electrodes on a component and anomalies related to the number of electrodes occur when the number and pitch of the component's characteristic features (e.g., electrodes) contained in the component image captured by the imaging unit 141 do not match the component data (e.g., component characteristic data). These anomalies may occur when the illumination lamp value is low or high. Therefore, the data creation unit 120 updates the illumination lamp value in the recognition operation parameters.

[0071] Furthermore, an abnormality such as an inability to detect a component feature occurs when the component feature contained in the component image captured by the imaging unit 141 does not match the component data. This abnormality may occur when the illumination lamp value is low or high, or when the information indicating the shape class (corner, rectangle, etc.) contained in the component feature data of the component is incorrect. Therefore, the data creation unit 120 updates the illumination lamp value of the recognition operation parameters or the information indicating the shape class contained in the component feature data.

[0072] The recognition error information may also be an abnormality related to the size of the component.

[0073] For example, an anomaly related to the size of a part occurs when the size (e.g., external dimensions) of the part contained in the image of the part captured by the imaging unit 141 does not match the part data. This anomaly may occur when information such as size contained in the part feature data of the part is incorrect. Therefore, the data creation unit 120 updates the part feature data.

[0074] The information indicating these abnormalities is not limited to terms that quantitatively or qualitatively express abnormalities such as abnormalities related to the size of the component, but may be generated as a predetermined code (e.g., a string of numbers and letters), or may indicate the size of the component that is the subject of the abnormality, the lead pitch, etc., using numerical data.

[0075] Furthermore, for example, the recognition error information includes information indicating the number of times an abnormality occurred during recognition by the recognition unit 142 using the same component data. The information indicating the number of times an abnormality occurred is, for example, information indicating the number of times the same abnormality occurred for each component data. Note that the "number of times" may be the frequency of occurrence, such as, for example, one abnormality related to the pitch of the electrodes of a component occurring during ten recognitions by the recognition unit 142.

[0076] Furthermore, when an abnormality occurs in the pitch of the electrodes of the component, the recognition error information may include information indicating the electrode that is the subject of the abnormality.

[0077] Furthermore, for example, the recognition error information includes progress information of updated component data, which is component data updated by data creation unit 120. The progress information includes, for example, information indicating a recognition rate (described later) which is progress information of the recognition result by recognition unit 142 using the updated component data, and / or information indicating an update history of component data based on the updated component data and component data before the update (for example, first component data) (for example, information summarizing, in chronological order, data on items that have been updated among the component shape data, component feature data, recognition operation parameters, etc.).

[0078] Here, when the recognition unit 142 is unable to recognize a part using part data (for example, first part data), the data creation unit 120 updates at least the first part data among the one or more part data including the first part data created by the data creation unit 120, based on second part data that is suitable for recognizing the part and that is created based on the first part data, and based on the second part data and recognition error information that indicates the content of an error that occurred when the recognition unit 142 recognized the part.

[0079] The second part data is data created based on the first part data. For example, the second part data is data created by an operator correcting the first part data so that the recognition unit 142 can recognize the part (i.e., data suitable for recognition).

[0080] For example, the data creation unit 120 displays the first component data and the recognition error information on a display device such as a display (not shown) provided in the data management device 100. The operator checks the first component data and the recognition error information, and operates an operation device such as a mouse or keyboard (not shown) provided in the data management device 100 to create second component data that updates (changes) the first component data.

[0081] The information on quality is information indicating the mounting state (mounting quality) of a recognized component on a board on which the component is mounted. For example, the information on quality is information indicating that the mounting quality is poor, or information indicating that the mounting quality is good. Information indicating that the mounting quality is poor includes, for example, information indicating that a lead-attached component mounted by production equipment 140A has bent leads, information indicating that a component mounted by production equipment 140A has been misaligned, etc.

[0082] The above-mentioned mounting quality defects may occur when the recognition unit 142 recognizes an element that is not an electrode but has a shape similar to that of an electrode as a characteristic part (i.e., the recognition unit 142 erroneously recognizes an element that is not an electrode as an electrode). An element that has a shape similar to that of an electrode is, for example, a mark or wiring pattern attached to a component that appears in an image. Furthermore, the above-mentioned mounting quality defects may occur when the recognition unit 142 recognizes an element of unstable component quality (e.g., an element with large component tolerance) as a characteristic part. If the characteristic part is inappropriate, the recognition unit 142 may not correctly recognize the component (e.g., recognize the component position, etc.), which may result in mounting quality defects.

[0083] Here, data creation unit 120 may further update component data (e.g., first component data) based on quality information indicating the mounting state of a component that recognition unit 142 was able to recognize using the second component data on a board on which the component is mounted. Furthermore, if recognition unit 142 is able to recognize a component using the second component data and the mounting quality of the component is poor, data creation unit 120 may acquire quality information, determine based on the acquired quality information whether the poor mounting quality has occurred due to the influence of recognition, and update the component data based on the determination result. Poor mounting quality caused by the influence of recognition is, for example, poor mounting quality caused by recognizing an element that is not an electrode as a feature, or by recognizing an element with unstable quality as a feature.

[0084] This allows the recognition device 140 to recognize component elements that are suitable as characteristic parts, compared to when only the second component data and the recognition error information are used, thereby enabling the recognition device 140 to reduce poor mounting quality caused by recognition.

[0085] Note that "updating" includes adding a part element included in the image that is not a feature part of the first part data as a new feature part, and deleting a part element that is a feature part of the first part data.

[0086] Furthermore, in the above description, the data creation unit 120 determines whether or not a mounting quality defect has occurred due to the influence of recognition based on information related to quality, but this determination may be made not by the data creation unit 120 but by an inspection device located downstream of the recognition device 140 and connected to the recognition device 140. In this case, for example, the data creation unit 120 updates the component data based on information indicating the determination result obtained from the inspection device.

[0087] Information indicating good mounting quality is, for example, information indicating that the mounting misalignment amount is within a tolerance. For example, if the data creation unit 120 is unable to recognize a component using the first component data (i.e., a recognition error has occurred), but is able to recognize the multiple components in the component group to which the component belongs using the first component data, that is, if the mounting quality is good, there is no need to update the first component data. As a result, the data creation unit 120 updates the component based on the recognition error that requires updating the first component data. This allows the recognition unit 142 to correctly recognize the component.

[0088] Furthermore, for example, the data creating unit 120 determines whether the first information included in each of the plurality of component data belonging to the component group to which the first component data and the same type component data (component data belonging to the same component group as the first component data) belong has been updated a first predetermined number of times or more. In this case, for example, if the data creating unit 120 determines that the first information has been updated a first predetermined number of times or more, it updates the first information included in each of the plurality of component data belonging to the component group. The first predetermined number of times is, for example, a first threshold value described later.

[0089] Alternatively, for example, data creating unit 120 determines whether the second information included in each of the one or more pieces of component data created by data creating unit 120 has been updated a second predetermined number of times or more. In this case, for example, when data creating unit 120 determines that the second information has been updated a second predetermined number of times or more, data creating unit 120 updates the second information included in each of the one or more pieces of component data.

[0090] The first information and the second information are, for example, any of the parameters described above. The second predetermined number of times is, for example, a second threshold value described below. The execution unit 143 is a device that executes a predetermined process on the component based on the recognition result of the recognition unit 142. The execution unit 143 is realized, for example, by a head for picking up the component and mounting it on the board, a drive mechanism for driving the head, and a control device for controlling the drive mechanism.

[0091] Note that recognition device 140 need not be a mounting device, as long as it is a device that captures an image of a component and executes a process of recognizing the component using component data. For example, recognition device 140 may be a sorting device that sorts components based on the recognition results, or an assembly device that assembles components based on the recognition results.

[0092] The communication unit 150 is a communication interface for communicating with the server device 200 via the communication network 400 .

[0093] For example, the communication unit 150 is realized by an antenna and a wireless communication circuit when the data management device 100 and the server device 200 communicate wirelessly via the communication network 400. Also, for example, when the data management device 100 and the server device 200 communicate via wired communication via the communication network 400, the communication unit 150 is realized by an adapter or the like to which a communication line is connected.

[0094] The processing units such as the data creation unit 120 and the recognition unit 142 are realized by a processor such as a CPU (Central Processing Unit) and a control program executed by the processor. Each processing unit may be realized by a single processor or by different processors.

[0095] The server device 200 is a device communicatively connected to the data management devices 100 via a communication network 400. The server device 200 is a computer that selects appropriate component data for recognizing components (e.g., component data with the highest recognition success rate) based on the component data and recognition error information received from each data management device 100, and transmits the selected component data to each data management device 100. The server device 200 is realized by, for example, a communication interface for communicating with each data management device 100, non-volatile memory in which programs are stored, volatile memory that is a temporary storage area for executing the programs, input / output ports for transmitting and receiving signals, a processor for executing the programs, and the like.

[0096] The server device 200 includes a communication unit 210, a control unit 220, and a shared data storage 230.

[0097] The communication unit 210 is a communication interface for communicating with each data management device 100 via the communication network 400 .

[0098] The communication unit 210 is realized by, for example, an antenna and a wireless communication circuit when each data management device 100 and the server device 200 communicate wirelessly via the communication network 400. Also, for example, when each data management device 100 and the server device 200 communicate via wired communication via the communication network 400, the communication unit 210 is realized by an adapter or the like to which a communication line is connected.

[0099] The control unit 220 is a processing unit that performs each process executed by the server device 200. For example, the control unit 220 stores the component data received from each data management device 100 via the communication unit 210 in the shared data storage 230. Specifically, the control unit 220 receives the component data stored in the data storage 130 of each of the multiple data management devices 100 and the recognition error information associated with the component data via the communication unit 210 and stores the received data in the shared data storage 230.

[0100] Furthermore, for example, the control unit 220 selects appropriate component data for recognizing components based on the component data and recognition error information received from each data management device 100 via the communication unit 210, and transmits the selected component data to each data management device 100 via the communication unit 210. For example, when the control unit 220 receives updated component data from one of the plurality of data management devices 100 via the communication unit 210, the control unit 220 determines whether or not to update component data corresponding to the updated component data stored in the data storage 130 of another of the plurality of data management devices 100, based on history information linked to the updated component data. The one data management device is, for example, the data management device 100 shown in FIG. 8, which will be described later, and the other data management device is, for example, the data management device 101 shown in FIG. 8, which will be described later. In this case, for example, when the control unit 220 determines to update, it transmits to the other data management device via the communication unit the updated component data and instruction information indicating an instruction to update component data corresponding to the updated component data stored in the data storage 130 of the other data management device to the updated component data. The component data corresponding to the updated component data is, for example, the same component data as the component data before the updated component data was updated (for example, used to recognize the same component).

[0101] The control unit 220 is realized by, for example, a processor such as a CPU and a control program executed by the processor.

[0102] The shared data storage 230 is a storage device that stores the component data received from each data management device 100. The shared data storage 230 is realized by, for example, an HDD or the like.

[0103] Note that component data may be stored in advance in the shared data storage 230, and the server device 200 may transmit the component data stored in the shared data storage 230 to the data management device 100. In this case, the data management device 100 may not create the component data. That is, the data management device 100 may not include the imaging unit 110 and the data creation unit 120. In this case, the server device 200 may include the imaging unit 110 and the data creation unit 120.

[0104] [Processing Procedure] Next, the processing procedure of the data management device 100 will be described.

[0105] Fig. 5 is a flowchart showing the processing procedure of the data management device 100 according to the embodiment. The flowchart shown in Fig. 5 shows the processing of determining whether the recognition unit 142 can recognize a component using the component data created by the data creation unit 120.

[0106] First, the data creation unit 120 creates component data (S101). For example, the imaging unit 110 captures an image of a component to create an image including the component, and the data creation unit 120 creates the component data based on the image created by the imaging unit 110.

[0107] If there are multiple types of parts, the data creating unit 120 may create part data for each of the multiple types of parts.

[0108] Next, the data creating unit 120 stores the created component data in the data storage 130 (S102).

[0109] Next, the recognition device 140 executes a recognition process for the component using the component data created by the data creation unit 120 (S103). For example, the imaging unit 141 captures an image of the component to generate an image including the component, and the recognition unit 142 executes a recognition process for the component using the image generated by the imaging unit 141 and the component data.

[0110] The recognition device 140 may execute processing such as mounting the component on a board based on the recognition result.

[0111] Next, the data creation unit 120 determines whether or not the recognition process of the component by the recognition device 140 has been successful (S104). In other words, the data creation unit 120 determines whether or not the recognition device 140 has been able to recognize the component using the component data.

[0112] Note that step S104 may be executed by the recognition device 140.

[0113] If the data creation unit 120 determines that the recognition process of the part by the recognition device 140 has been successful (Yes in S104), the recognition device 140 determines whether all of the part data created by the data creation unit 120 has been confirmed (S105).

[0114] When the recognition device 140 determines that all of the component data created by the data creation unit 120 has been confirmed (Yes in S105), the process ends.

[0115] On the other hand, if the recognition device 140 determines that not all of the component data created by the data creation unit 120 has been confirmed, that is, that some of the component data has not been used in the recognition process (No in S105), the recognition device 140 returns the process to step S103 and executes step S103 using the component data that has not been used in the recognition process.

[0116] Here, if the data creation unit 120 determines that the component recognition process by the recognition device 140 has failed (No in S104), it executes a component data update process, which is a process for updating (changing) the component data (S106), and returns the process to step S103. Furthermore, if the component recognition process by the recognition device 140 (for example, the recognition unit 142) has failed, it generates recognition error information indicating the details of the failure.

[0117] FIG. 6 is a flowchart showing the component data update process (step S106 shown in FIG. 5) executed by the data management device 100 according to the embodiment.

[0118] First, the data creation unit 120 acquires the component data used in step S103 shown in FIG. 5 (first component data, which is component data that cannot be used by the recognition unit 142 to recognize a component), the recognition error information generated by the recognition unit 142, and the second component data, which is component data suitable for component recognition (S201). For example, before step S201, the data creation unit 120 displays the first component data and the recognition error information on a display device, such as a display (not shown), provided in the data management device 100. The operator checks the first component data and the recognition error information and operates an operation device (not shown) provided in the data management device 100 to create second component data by updating the first component data. For example, the data creation unit 120 stores the second component data created by the operator in the data storage 130.

[0119] Next, the data creation unit 120 determines whether or not a parameter related to all of the part data (parts) stored in the data storage 130 has been updated, among one or more parameters (information) included in the first part data (S202). The part data may include a parameter related to only one part data, a parameter related to all of the part data belonging to the same part group (e.g., a shape class included in the part feature data), and a parameter related to all of the part data (e.g., an illumination lamp value). The data creation unit 120 determines whether or not a parameter related to all of the part data, for example, a parameter common to all of the part data, has been changed from the first part data in the second part data.

[0120] When it is determined that the parameters related to all of the component data among the one or more parameters included in the first component data have been updated (Yes in S202), the data creating unit 120 increments the number of parameter updates by one (S203). For example, the data creating unit 120 counts how many times the component data has been updated for each component data, and stores the count result (number of updates) in the data storage 130.

[0121] Next, the data creating unit 120 determines whether the number of updates of the component data exceeds a threshold value (first threshold value) (S204).

[0122] If the data creation unit 120 determines that the number of updates to the component data has exceeded the threshold value (first threshold value) (Yes in S204), it updates the parameters of all component data for the relevant parameters (parameters changed from the first component data) (S205) and terminates the processing (more specifically, returns the processing to step S103 shown in FIG. 5).

[0123] On the other hand, if the data creating unit 120 determines that the number of updates of the component data does not exceed the first threshold (No in S204), it updates the parameters of the relevant parameters (parameters changed from the first component data) individually, that is, the parameters of the target component data (in other words, the first component data) (S206), and ends the process. For example, the data creating unit 120 updates the first component data, which is component data stored in the data storage 130, to the second component data.

[0124] Furthermore, the data creation unit 120 determines whether or not a parameter related to part data that belongs to the same part group as the target part data (first part data) has been updated, among one or more parameters included in the first part data (S207).

[0125] When it is determined that a parameter related to component data belonging to the same component group as the first component data, among one or more parameters included in the first component data, has been updated (Yes in S207), the data creating unit 120 increments the number of parameter updates by one (S208). For example, the data creating unit 120 counts how many times the component data has been updated for each component data, and stores the count result (number of updates) in the data storage 130.

[0126] The number of updates may be the total number of updates for all parameters in the part data, or may be the number of updates for each parameter in the part data.

[0127] Next, the data creating unit 120 determines whether the number of updates of the component data exceeds a threshold value (second threshold value) (S209).

[0128] If the data creation unit 120 determines that the number of updates to the component data exceeds the second threshold (Yes in S209), it updates the parameters of the component data that belong to the same component group as the first component data for the relevant parameters (parameters changed from the first component data) (S210), and terminates the processing.

[0129] On the other hand, if the data creation unit 120 determines that, among one or more parameters included in the first part data, a parameter other than a parameter related to part data belonging to the same group as the first part data has been updated (No in S207), or if it determines that the number of updates to the part data does not exceed the threshold value (second threshold value) (No in S209), it updates the relevant parameters (parameters changed from the first part data) individually, that is, the parameters of the target part data (in other words, the first part data) (S206), and terminates the processing.

[0130] The number of times a parameter is updated may be the total number of times all parameters in the part data are updated, or may be the number of times each parameter in the part data is updated.

[0131] Furthermore, the thresholds (first threshold and second threshold) may be arbitrarily determined in advance and are not particularly limited. For example, information indicating the thresholds may be stored in the data storage 130 in advance.

[0132] The threshold value may be the same or different for each piece of component data, and may be the same or different for each parameter.

[0133] Furthermore, when updating the parameters of each piece of component data, data creation unit 120 may update the parameters to be the same as the parameters of the second component data, or may update the parameters of each piece of component data by the difference between the parameters of the first component data and the parameters of the second component data. For example, if the first parameter of the first component data is 0.5 and the first parameter of the second component data is 0.6, data creation unit 120 may add 0.1 to the first parameter of each piece of component data. Alternatively, if the first parameter of the first component data is 0.5 and the first parameter of the second component data is 0.6, data creation unit 120 may update the first parameter of each piece of component data to 0.6.

[0134] Furthermore, when updating component data, the data creation unit 120 may update the component data stored in the data storage 130, or may transmit the updated component data to the server device 200 so as to update the component data stored in the shared data storage 230 owned by the server device 200.

[0135] Furthermore, in some cases, the operator modifies not only one parameter but also multiple parameters of the first component data to create the second component data. In this case, for example, the data creating unit 120 may execute the processes of steps S202 to S210 for all the modified parameters.

[0136] Fig. 7 is a diagram illustrating the component data update process executed by the data management device 100 according to the embodiment. Fig. 7(a) is a diagram illustrating component data 131A, 131B, 131C, 131D, 131E, and 131F before the component data update process (the flowchart shown in Fig. 6) is executed, and Fig. 7(b) is a diagram illustrating component data 131A, 131B, 131C, 131D, 131E, and 131F after the component data update process is executed.

[0137] For example, the part data includes, in addition to parameters for recognizing the part, information indicating the part name, information indicating the part group, information indicating the creating device, and the like.

[0138] The information indicating the part name is information indicating the name of the part data (or the part for which the part data is used to recognize the part).

[0139] The information indicating the part group is information indicating the part group to which the part data belongs. For example, "part group: AA" indicates that the part data belongs to the part group AA.

[0140] The creation device is information indicating the device that created the component data. For example, "offline" indicates that the component data was created using the imaging unit 110 included in the data management device 100. Furthermore, "equipment X" is, for example, a name that is uniquely assigned to each recognition device 140. For example, "creation device: equipment X" indicates that the component data was updated because the component could not be recognized when recognition processing was performed by the recognition device 140 named "equipment X."

[0141] For example, consider a case where data creation unit 120 executes a component data update process for component data 131A belonging to component group AA. For example, in step S205 shown in Fig. 6, data creation unit 120 updates target parameters for component data 131A, 131B, 131C, 131D, 131E, and 131F. Also, for example, in step S210 shown in Fig. 6, data creation unit 120 updates target parameters for component data 131A and component data 131D belonging to component group AA. Also, for example, in step S206 shown in Fig. 6, data creation unit 120 updates target parameters only for component data 131A.

[0142] The updated part data is stored in the data storage 130 with information such as "creation device: equipment X" added to it.

[0143] Next, the processing procedure of the data management system 300 will be described.

[0144] Fig. 8 is a flowchart showing the processing procedure of the data management system 300 according to the embodiment. For the sake of explanation, Fig. 8 shows one of the multiple data management devices 100 included in the data management system 300 as the data management device 101.

[0145] First, the data management device 100 updates the component data by executing the processes of the flowcharts shown in FIGS. 5 and 6 (S301).

[0146] Next, the data management device 100 executes a recognition process for the component using the updated component data (S302). For example, the recognition device 140 executes the recognition process for the component using the component data with the imaging unit 141 and the recognition unit 142, and executes a predetermined process for the component based on the recognition result with the execution unit 143.

[0147] Next, the data management device 100 (for example, the recognition unit 142) generates progress information indicating, for example, the recognition result by the recognition unit 142 (S303). As described above, for example, the recognition device 140 executes a component recognition process using the component data with the imaging unit 141 and the recognition unit 142. Here, for example, the recognition device 140 (for example, the recognition unit 142) counts the number of times the component was successfully recognized using the component data with the imaging unit 141 and the recognition unit 142 and the number of times it was not possible to recognize the component, calculates the number of times recognition was successful relative to the number of times the recognition process was performed (recognition rate), and generates information indicating the calculated recognition rate as progress information.

[0148] Next, the data management device 100 transmits the updated component data and the recognition error information including the progress information to the server device 200 (S304). For example, the data creation unit 120 transmits the updated component data and the recognition error information including the progress information to the server device 200 via the communication unit 150. The server device 200 stores the updated component data and the recognition error information in the shared data storage 230.

[0149] Next, based on the received recognition error information, the server device 200 determines whether or not to update the component data stored in a data management device (e.g., data management device 101) different from the data management device 100 that transmitted the recognition error information (S305). For example, the control unit 220 determines whether or not the recognition rate exceeds a predetermined value based on progress information included in the recognition error information. The predetermined value may be determined arbitrarily and is not particularly limited. Information indicating the predetermined value is stored in advance in the shared data storage 230, for example.

[0150] For example, if the control unit 220 determines that the recognition rate does not exceed a predetermined value, the control unit 220 ends the process without updating the component data stored in the data management device 101.

[0151] On the other hand, if the control unit 220 determines that the recognition rate exceeds the predetermined value, it transmits instruction information instructing the data management device 101 to update the component data and the updated component data received from the data management device 100 to the data management device 101 via the communication unit 210 (S306).

[0152] Next, the data management device 101 updates the component data stored in the data storage 130 included in the data management device 101 to the updated component data received from the server device 200 (S307).

[0153] According to this, among the component data created (updated) by any of the multiple data management devices 100 provided in the data management system 300, component data with a high recognition rate (exceeding a predetermined value) will be used by each of the multiple data management devices 100.

[0154] [Effects, etc.] As described above, data management device 100 according to the embodiment includes data creation unit 120 that creates first component data used to recognize a component from an image of the component captured by imaging unit 110, and recognition unit 142 that recognizes the component included in the image of the component captured by imaging unit 141 using the first component data. When recognition unit 142 fails to recognize a component using the first component data, data creation unit 120 updates at least the first component data among one or more component data including the first component data created by data creation unit 120, based on second component data that is created based on the first component data and is suitable for component recognition, and recognition error information that indicates the content of an error that occurred when recognition unit 142 recognized the component. Data creation unit 120 updates the first component data stored in data storage 130, for example. Furthermore, data creation unit 120 updates the component data stored in shared data storage 230 included in server device 200, for example, by communicating with server device 200 via communication unit 150.

[0155] Conventionally, even if recognition unit 142 was unable to recognize a part when it performed a recognition process using part data, the part data was not automatically updated to a state appropriate for recognizing the part. Data management device 100 can update the first part data, which is part data for which the part could not be recognized, based on the second part data and recognition error information. Therefore, data management device 100 can update part data for recognizing parts more easily than conventional methods.

[0156] Furthermore, for example, the data creation unit 120 further updates at least the first component data among one or more component data including the first component data created by the data creation unit 120, based on information regarding the quality indicating the mounting state of the component that the recognition unit 142 was able to recognize using the second component data on the board on which the component is mounted.

[0157] This allows data creation unit 120 to more appropriately update information related to component elements suitable as feature portions for recognition by recognition unit 142, compared to when updating component data using only the second component data and recognition error information. Therefore, for example, recognition device 140, which recognizes components using component data updated in this way and mounts the components on a board or the like, can suppress poor mounting quality caused by recognition.

[0158] Furthermore, for example, the one or more component data described above may include same-type component data for identifying components of the same type as the component. In this case, for example, the data creation unit 120 determines whether the first information included in each of the plurality of component data belonging to the component group to which the first component data and the same-type component data belong has been updated a first predetermined number of times or more. For example, if the data creation unit 120 determines that the first information has been updated a first predetermined number of times or more, it updates the first information included in each of the plurality of component data belonging to the component group. For example, if the data creation unit 120 determines that the first information has not been updated a first predetermined number of times or more, it updates the first information included in the first component data, but does not update the first information included in each of the plurality of component data other than the first component data belonging to the component group.

[0159] This allows the part data belonging to a part group, among one or more part data created by the data creating unit 120, to be easily updated collectively.

[0160] Furthermore, for example, data creation unit 120 determines whether the second information included in each of the one or more pieces of component data has been updated a second predetermined number of times or more. For example, if data creation unit 120 determines that the second information has been updated a second predetermined number of times or more, it updates the second information included in each of the one or more pieces of component data. For example, if data creation unit 120 determines that the second information has been updated a second predetermined number of times or more, it updates the second information included in all of the component data stored in data storage 130. For example, if data creation unit 120 determines that the second information has not been updated a second predetermined number of times or more, it updates the second information included in the first component data, but does not update the second information included in all of the component data stored in data storage 130 except for the first component data.

[0161] This allows one or more pieces of part data created by the data creating unit 120 to be easily updated all at once.

[0162] Furthermore, for example, data management device 100 further includes data storage 130 that stores at least one of one or more pieces of component data, image data of images captured by at least one of imaging unit 110 and imaging unit 141, recognition error information, information on the quality indicating the mounting state of a component on a board on which the component that recognition unit 142 has been able to recognize using the second component data is mounted, and the second component data. For example, the one or more pieces of component data and the one or more pieces of recognition error information are each linked and stored by data creation unit 120 or the like.

[0163] This allows the image data, recognition error information, quality information, and second part data to be checked at any time, so even if many problems occur, such as the recognition unit 142 being unable to recognize parts even when updated part data is used, it is possible to check at any time whether the second part data is appropriate.

[0164] Moreover, a data management system 300 according to the embodiment includes a plurality of data management devices 100 and a server device 200 connected to the plurality of data management devices 100 via a communication network 400. The server device 200 includes a shared data storage 230, a communication unit 210 for communicating with the plurality of data management devices 100, and a control unit 220 for receiving, via the communication unit 210, component data stored in the data storage 130 of each of the plurality of data management devices 100 and recognition error information associated with the component data, and storing the received data in the shared data storage 230. For example, the recognition error information includes progress information indicating the recognition result by the recognition unit 142 using updated component data, which is component data updated by the data creation unit 120. For example, when the control unit 220 receives updated component data from one of the plurality of data management devices 100 (e.g., the data management device 100 shown in FIG. 8) via the communication unit 210, the control unit 220 determines whether or not to update component data corresponding to the updated component data stored in the data storage 130 of another of the plurality of data management devices 100 (e.g., the data management device 101 shown in FIG. 8) based on the history information associated with the updated component data. For example, when the control unit 220 determines to update the component data, the control unit 220 transmits the updated component data and instruction information indicating an instruction to update the component data corresponding to the updated component data stored in the data storage 130 of the other data management device to the updated component data to the other data management device via the communication unit 210. The component data corresponding to the updated component data is, for example, the component data in a state before the updated component data was updated.

[0165] According to this, if component data is created that increases the component recognition rate in at least one of the multiple data management devices 100, the component data can be used in all of the multiple data management devices 100, thereby easily improving the component recognition rate in each of the multiple data management devices 100 provided in the data management system 300.

[0166] (Other embodiments) Although the data management device and the like according to the present embodiment have been described based on the above-mentioned embodiments, the present invention is not limited to the above-mentioned embodiments.

[0167] For example, all or some of the components of the processing unit in the data management system may be configured with dedicated hardware, or may be realized by executing a software program appropriate for each component. Each component may be realized by a program execution unit such as a CPU or processor reading and executing a software program recorded on a recording medium such as a hard disk drive or semiconductor memory.

[0168] Furthermore, the components of the processing unit of the data management system may be configured with one or more electronic circuits, each of which may be a general-purpose circuit or a dedicated circuit.

[0169] The one or more electronic circuits may include, for example, a semiconductor device, an IC, or an LSI (Large Scale Integration). The IC or LSI may be integrated on a single chip or on multiple chips. Although the IC or LSI is referred to here as an IC or LSI, the name may vary depending on the degree of integration, and may be called a system LSI, a VLSI (Very Large Scale Integration), or an ULSI (Ultra Large Scale Integration). Also, a field programmable gate array (FPGA), which is programmed after the LSI is manufactured, can be used for the same purpose.

[0170] In addition, the present invention can be realized not only as a data management device, but also as a program that includes steps representing the processing performed by each component of the data management device, and a computer-readable recording medium such as a DVD (Digital Versatile Disc) on which the program is recorded.

[0171] Similarly, the present invention can be realized not only as a data management system, but also as a program that includes steps representing the processing performed by each component of the data management system, and a computer-readable recording medium such as a DVD on which the program is recorded.

[0172] In other words, the above-described comprehensive or specific aspects may be realized as a system, an apparatus, an integrated circuit, a computer program, or a computer-readable recording medium, or may be realized as any combination of a system, an apparatus, an integrated circuit, a computer program, and a recording medium.

[0173] For example, the data management device may be realized as a single device or as a system consisting of multiple devices. For example, the data creation unit and the recognition unit may be realized by different devices.

[0174] In addition, the present invention also includes forms obtained by applying various modifications to each embodiment that a person skilled in the art would think of, and forms realized by arbitrarily combining the components and functions of each embodiment within the scope of the present invention. [Industrial Applicability]

[0175] The data management device according to the present invention can be used in a device that creates component data used by a device that performs processing to recognize components, such as a mounting device. [Explanation of symbols]

[0176] 100, 101 Data management device 110 imaging unit (first imaging unit) 120 Data Creation Department 130 Data Storage 131A, 131B, 131C, 131D, 131E, 131F parts data 140 Recognition device 140A, 140B, 140C production equipment 141 Imaging unit (second imaging unit) 142 Recognition part 143 Executive Department 150, 210 Communications Department 200 Server device 220 Control Unit 230 Shared Data Storage 300, 300a Data Management System 400 Communication Network 500 Production System 510A, 510B Computer

Claims

1. a data creation unit that creates first component data used for recognizing a component from an image of the component captured by the first imaging unit; a recognition unit that recognizes the component included in an image of the component captured by a second imaging unit using the first component data, when the recognition unit is unable to recognize the component using the first component data, the data creation unit updates at least the first component data among the one or more component data including the first component data created by the data creation unit, based on second component data created based on the first component data and suitable for recognizing the component, and recognition error information indicating the content of an error that occurred when the recognition unit recognized the component; the one or more part data include similar part data for recognizing a part of the same type as the part; The data creation unit determining whether or not first information included in each of a plurality of part data belonging to a part group to which the first part data and the similar part data belong has been updated a first predetermined number of times or more; updating the first information included in each of the plurality of component data belonging to the component group when it is determined that the first information has been updated the first predetermined number of times or more; Data management device.

2. a data creation unit that creates first component data used for recognizing a component from an image of the component captured by the first imaging unit; a recognition unit that recognizes the component included in an image of the component captured by a second imaging unit using the first component data, when the recognition unit is unable to recognize the component using the first component data, the data creation unit updates at least the first component data among the one or more component data including the first component data created by the data creation unit, based on second component data created based on the first component data and suitable for recognizing the component, and recognition error information indicating the content of an error that occurred when the recognition unit recognized the component; The data creation unit determining whether or not the second information included in each of the one or more component data has been updated a second predetermined number of times or more; When it is determined that the second information has been updated the second predetermined number of times or more, the second information included in each of the one or more part data is updated; the one or more part data include similar part data for recognizing a part of the same type as the part; Data management device.

3. the data creation unit further updates at least the first component data among the one or more component data including the first component data created by the data creation unit, based on information on quality indicating a mounting state of the component that the recognition unit has been able to recognize using the second component data on a board on which the component is mounted.

3. The data management device according to claim 1 or 2.

4. further comprising a data storage that stores at least one of the one or more component data, image data of an image captured by at least one of the first imaging unit and the second imaging unit, the recognition error information, information on quality indicating a mounting state of a component on a board on which a component that the recognition unit has been able to recognize using the second component data is mounted, and the second component data. The data management device according to any one of claims 1 to 3.

5. A plurality of data management devices according to any one of claims 1 to 4; a server device connected to the plurality of data management devices via a communication network, The server device Shared data storage; a communication unit for communicating with the plurality of data management devices; a control unit that receives, via the communication unit, component data stored in a data storage included in each of the plurality of data management devices and the recognition error information associated with the component data, and stores the component data in the shared data storage; the recognition error information includes progress information indicating a recognition result by the recognition unit using updated component data, which is component data updated by the data creation unit, The control unit when the updated part data is received from one of the plurality of data management devices via the communication unit, determining whether or not to update part data corresponding to the updated part data that is stored in the data storage of another of the plurality of data management devices, based on the history information linked to the updated part data; If it is determined that the data should be updated, the updated part data and instruction information indicating an instruction to update part data corresponding to the updated part data stored in the data storage of the other data management device to the updated part data are transmitted to the other data management device via the communication unit. Data management system.

6. a plurality of data management devices; a server device connected to the plurality of data management devices via a communication network, Each of the plurality of data management devices a data creation unit that creates first component data used for recognizing a component from an image of the component captured by the first imaging unit; a recognition unit that recognizes the component included in an image of the component captured by a second imaging unit using the first component data, when the recognition unit is unable to recognize the component using the first component data, the data creation unit updates at least the first component data among the one or more component data including the first component data created by the data creation unit, based on second component data created based on the first component data and suitable for recognizing the component, and recognition error information indicating the content of an error that occurred when the recognition unit recognized the component; The server device Shared data storage; a communication unit for communicating with the plurality of data management devices; a control unit that receives, via the communication unit, component data stored in a data storage included in each of the plurality of data management devices and the recognition error information associated with the component data, and stores the component data in the shared data storage; the recognition error information includes progress information indicating a recognition result by the recognition unit using updated component data, which is component data updated by the data creation unit, The control unit when the updated part data is received from one of the plurality of data management devices via the communication unit, determining whether or not to update part data corresponding to the updated part data that is stored in the data storage of another of the plurality of data management devices, based on the history information linked to the updated part data; If it is determined that the data should be updated, the updated part data and instruction information indicating an instruction to update part data corresponding to the updated part data stored in the data storage of the other data management device to the updated part data are transmitted to the other data management device via the communication unit. Data management system.

Images