Method for generating component data and generation device

Abstract

To provide an improvement for generating and registering correct component data by reducing user's input errors and workload.SOLUTION: A method for generating component data as information on a component to be mounted on a substrate by a component mounting machine, includes: a component number reception step of receiving an input of a component number of a target component being one of components; a code extraction step of analyzing the component number associated with the input and extracting a code included in the component number; an attribute information acquisition step of acquiring attribute information corresponding to the extracted code by making reference to a code table that associates codes possibly included in component numbers of components with attribute information of components; a component data generation step of generating component data associated with the target component on the basis of the acquired attribute information; and a registration step of registering the generated component data to a library stored in a prescribed storage unit.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The technology disclosed in this specification relates to a method and device for generating part data. [Background technology]

[0002] Systems that manage component mounters have libraries in which component data, which is information about the components mounted on boards by the mounters, is registered. Conventionally, when creating new component data and registering it in a library, users would manually enter the data or create a CSV file from detailed component information published by the component manufacturer and import it into the library. In addition, data such as component shape obtained by analyzing image data generated by taking photos of the actual components with a camera could also be entered into the library.

[0003] Patent Document 1 discloses a component type classification device that converts component part numbers into component types. This device inputs the part number of an electrical component and acquires component attribute information from a component part number information database based on the part number. It then refers to a component type conversion table and extracts component type names that match the acquired attribute information, thereby converting the component part number into a component type. [Prior art documents] [Patent documents]

[0004] [Patent Document 1] Japanese Patent Application Laid-Open No. 2004-134505 Summary of the Invention [Problem to be solved by the invention]

[0005] As mentioned above, the method of having users manually input data or generate CSV files is prone to input errors and places a heavy burden on the user. Furthermore, when photographing components, if there are distortions specific to each component or the captured image quality is unstable, accurate component design data will not be registered in the library. In light of these circumstances, there is a need for improvements that minimize user input errors and workload while generating and registering accurate component data. [Means for solving the problem]

[0006] This specification discloses a method for generating component data, which is information related to components to be mounted on a board by a component mounter. The method includes a part number receiving step for receiving an input of a part number of a target component, which is one of the components, and a code extraction step for analyzing the input part number and extracting a code contained in the part number. The method further includes an attribute information acquisition step for acquiring attribute information corresponding to the extracted code by referencing a code table that associates codes that may be contained in the part number of the component with attribute information of the component, a component data generation step for generating the component data associated with the target component based on the acquired attribute information, and a registration step for registering the generated component data in a library stored in a predetermined storage unit.

[0007] According to this generation method, when a user inputs the part number of a target part, a series of steps are automatically executed, including part number analysis, code extraction from the part number, acquisition of attribute information by referencing a code table, part data generation, and registration in the library. This reduces input errors and reduces the workload of the user, enabling accurate part data generation and registration. [Brief explanation of the drawings]

[0008] [Figure 1] FIG. 1 is a block diagram simply illustrating the configuration of a generating device according to an embodiment of the present invention. [Figure 2] 10 is a flowchart showing a part of a part data generation and registration process. [Figure 3] 3 is a flowchart showing the part data generation and registration process, continuing from FIG. 2; [Figure 4] FIG. 10 is a diagram showing an example of a shape code table. [Figure 5] FIG. 10 is a diagram showing an example of a packaging code table. DETAILED DESCRIPTION OF THE INVENTION

[0009] The main features of the embodiments described below are listed below. Note that the technical elements described below are independent technical elements that exhibit technical utility alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing.

[0010] According to the generation method disclosed in this specification, the code extraction step may involve extracting, as the code, a character or character string at a specific position from a character string that constitutes the product number, based on predetermined rules that define the composition of the product number. According to the above configuration, the code can be easily and accurately extracted from the character string that constitutes the product number.

[0011] According to the generation method disclosed in this specification, the attribute information acquisition step may acquire the shape information corresponding to the extracted code by referring to the code table in which shape information of the part is described as the attribute information. According to the above configuration, it is possible to acquire shape information as a type of attribute information of a part during the process of generating and registering part data.

[0012] According to the generation method disclosed in this specification, the shape information may include, in addition to the dimensions of the part, tolerances for errors in the dimensions. According to the above configuration, it is possible to acquire shape information including dimensions of a part and tolerances for dimensional errors as a type of attribute information of the part.

[0013] According to the generation method disclosed in this specification, the attribute information acquisition step may acquire the packaging information corresponding to the extracted code by referring to the code table in which packaging information of the part is described as the attribute information. According to the above configuration, it is possible to acquire packaging information as a type of attribute information of a part during the process of generating and registering part data.

[0014] According to the generation method disclosed in this specification, the packaging information may include at least one of the size, the number of components contained, the component housing intervals, and the material of the container that houses the components. According to the above configuration, it is possible to acquire packaging information including at least one of the size of the container, the number of contained components, the component containing intervals, and the material as a type of attribute information of the components.

[0015] The category of the technology disclosed in this specification is not limited to the generation method, and various other technologies, such as an apparatus or system that executes the generation method, are also understood by this specification. For example, a generation device that generates component data, which is information about components to be mounted on a board by a component mounter, includes an input receiving unit, a control unit, and a storage unit. The input receiving unit receives an input of a part number of a target component, which is one of the components. The control unit is capable of executing a code extraction process that analyzes the input part number and extracts a code contained in the part number, an attribute information acquisition process that acquires attribute information corresponding to the extracted code by referencing a code table that associates codes that may be contained in the component part number with attribute information of the component, a component data generation process that generates the component data associated with the target component based on the acquired attribute information, and a registration process that registers the generated component data in a library stored in the storage unit. [Example]

[0016] The embodiments will be described with reference to the drawings. Each drawing is merely an example, and the present embodiment is not limited to the contents shown in the drawings. Also, since each drawing is an example, some parts may be omitted.

[0017] FIG. 1 shows a simplified block diagram of the configuration of a generating device 10 according to this embodiment. The generating device 10 executes a method for generating component data, which is information relating to components (hereinafter referred to as components) to be mounted on a board by a component mounter. The component mounter is also called a chip mounter, a surface mounter, etc. The generating device 10 is mainly composed of a computer capable of executing the method for generating component data. The generating device 10 may be mainly composed of a single computer, or may be composed of multiple computers connected to each other so as to be able to communicate with each other.

[0018] The generation device 10 includes a control unit 12, an input reception unit 14, a storage unit 16, a display unit 18, etc. The control unit 12 has a processor such as a CPU and a memory, and the processor controls the generation device 10 by executing arithmetic processing in accordance with a program 12a stored in the memory, etc. The display unit 18 is a means for displaying visual information. The input reception unit 14 is a means for receiving input from a user, such as a keyboard, a mouse, switches, etc. If the display unit 18 also functions as a so-called touch panel, the display unit 18 also corresponds to an example of the input reception unit 14. Furthermore, the input reception unit 14 may include a scanner, etc., capable of reading barcodes, two-dimensional codes, etc.

[0019] The storage unit 16 is configured with a storage device such as a hard disk drive (HDD) or a solid state drive (SSD). A portion of the memory of the control unit 12 may be considered as at least a portion of the storage unit 16. The storage unit 16 stores various data and programs required by the control unit 12 for various processes executed by the generation device 10. In this embodiment, the storage unit 16 also stores various types of information such as a library 20, a code table 22, a shape DB 24, a packaging DB 26, etc. DB is an abbreviation for database.

[0020] The memory unit 16 may include one or more storage devices. Some of the information, such as the code table 22, the shape DB 24, and the packaging DB 26, may be stored in a storage device or server external to the generating device 10 and accessible by the control unit 12. In addition, the generating device 10 may have various functions that a computer generally has, such as a function for communicating with external communication devices, as appropriate.

[0021] 2 and 3 are flowcharts showing the component data generation and registration process executed by the control unit 12 in accordance with the program 12a. An explanation of at least a part of the flowchart will explain the component data generation method according to this embodiment. Here, the explanation will be made assuming a situation in which a user attempts to newly register component data for a certain component (hereinafter, the component of interest) in the library 20. The user operates the input accepting unit 14 to input a component data number for identifying the component data of the component of interest in the library 20. The control unit 12 generates a component data number for the component of interest in accordance with this input (step S100). The component data number may be, for example, a serial number assigned to each component in the library 20.

[0022] The user inputs the part number of the target part by operating the input receiving unit 14. The part number is simply called a part number. The part number is information that is made public by the part manufacturer that produced the part. For example, the user inputs the part number of the target part to the generating device 10 by having a scanner, which is a type of input receiving unit 14, read a barcode or two-dimensional code that records the part number of the target part. In step S110, the control unit 12 acquires the part number of the target part that is accepted by the input receiving unit 14. Step S110 corresponds to an example of a "part number accepting process."

[0023] In step S120, the control unit 12 extracts, as a shape code, a character or character string at a specific position from the character string constituting the part number of the input target component, based on a predetermined rule that defines the composition of the part number. A part number is composed of characters or character strings, each with a specific meaning, arranged according to a predetermined rule. For example, a part number is composed of characters or character strings representing the product series, shape code, temperature characteristics, rated voltage, capacitance, and packaging code, arranged according to a predetermined rule. Therefore, according to the predetermined rule, it can be inferred that the shape code is located at a first specific position in the part number, such as a range from the first character to a certain character. The shape code is also called a size code.

[0024] Therefore, in step S120, the control unit 12 extracts, as a shape code, a character string at a first specific position from the character strings constituting the part number of the target part. Step S120 as described above and step S240 described later correspond to an example of a "code extraction step (process)" that analyzes the input part number and extracts the code included in the part number.

[0025] In step S130, the control unit 12 searches for the shape code extracted in step S120 from the shape code table 22a. The shape code table 22a is a type of code table 22 that associates codes that can be included in product numbers with attribute information of parts. The shape code table 22a describes the shape information of parts as attribute information.

[0026] FIG. 4 shows an example of the shape code table 22a. The shape code table 22a defines the correspondence between shape codes, detailed shape information of components, and component identifiers. The shape code table 22a defines shape codes corresponding to the EIA standard and the JIS standard. The EIA standard is a standard established by the Electronic Industries Alliance.

[0027] Among the shape information, "L" represents the length of the part, "W" the width of the part, and "T" the thickness of the part, indicating the dimensions of the part. Length is the length in the longitudinal direction of the part, and width is the length in the lateral direction of the part. Furthermore, among the shape information, "a" and "b" are the tolerances for the error in the dimensions of the part. The unit of this shape information is millimeters.

[0028] In step S140, the control unit 12 branches the process depending on the search result in step S130. That is, if a shape code matching the shape code extracted in step S120 is defined in the shape code table 22a, the process proceeds to step S150 based on the determination of "Yes," and if the shape code extracted in step S120 is not in the shape code table 22a, the process proceeds to step S160 based on the determination of "No."

[0029] In step S150, the control unit 12 searches the shape code table 22a for a part identifier corresponding to the shape code extracted in step S120. The part identifier is, for example, an identifier defined by the part manufacturer. The part identifier may also be part of the information constituting the part number.

[0030] On the other hand, in step S160, the control unit 12 adds a new shape code. That is, the control unit 12 adds the shape code extracted in step S120 to the shape code table 22a as a new shape code. In the following step S170, the control unit 12 accepts input of shape information such as the length, width, and thickness of the target component. Steps S160 and S170 are executed in response to a user operation.

[0031] For example, the user is notified that the determination result in step S140 is "No" through a display on the display unit 18, etc. The user, recognizing the notification, operates the input receiving unit 14 to instruct that the shape code extracted in step S120 from the part number of the target part should be newly added to the shape code table 22a, and the control unit 12 executes step S160 in response to the instruction. Next, the user operates the input receiving unit 14 to input the above-mentioned shape information, and the control unit 12 accepts this input shape information (step S170). Of course, the shape information of the target part input by the user may include a tolerance for dimensional error. The control unit 12 can add the shape information input in step S170 to the shape code table 22a in association with the shape code newly added in step S160.

[0032] After step S150 or step S170, in step S180, the control unit 12 determines whether a component identifier corresponding to the shape code extracted in step S120 is defined in the shape code table 22a. In this case, if step S150 was executed from "Yes" in step S140, the component identifier corresponding to the shape code extracted in step S120 is in the shape code table 22a, so the control unit 12 determines "Yes" in step S180 and proceeds to step S200. On the other hand, if steps S160 and S170 were executed from "No" in step S140, the control unit 12 determines "No" in step S180 and proceeds to step S190.

[0033] In step S190, the control unit 12 adds a new component identifier. Step S190 is executed in response to a user operation. The user inputs the component identifier of the component of interest by operating the input receiving unit 14, and the input component identifier is received by the control unit 12. The control unit 12 then adds this component identifier to the shape code table 22a in association with the shape code newly added in step S160.

[0034] After step S180 or step S190, in step S200, the control unit 12 searches the shape DB 24 for shape information similar to the shape information corresponding to the target component. The "shape information corresponding to the target component" referred to in steps S200 to S220 refers to either the shape information specified in the shape code table 22a corresponding to the shape code extracted in step S120 or the shape information input received in step S170. Naturally, "similar" also includes matching. When there is no match, various considerations can be made regarding the degree of similarity to be included in the range of similarity. For example, if only one of the dimensions—length, width, or thickness—differs within the tolerance for error, the search in the shape DB 24 is deemed similar. Alternatively, the range of similarity may be set to 0, and the search in the shape DB 24 may be deemed successful only if substantially all dimensions of the shape information match.

[0035] The shape DB 24 stores shape information for each of various parts. There are no particular limitations on the data structure of the shape DB 24. For example, in the shape DB 24, a unique name is assigned to the shape information for each part. In addition, in the shape DB 24, a part identifier may be associated with the shape information for each part. Therefore, the control unit 12 can search the shape DB 24 for shape information similar to the shape information corresponding to the target part based on the part identifier.

[0036] In step S210, the control unit 12 branches the process depending on the search result of step S200. That is, if shape information similar to the shape information corresponding to the target component is present in the shape DB 24, the process proceeds to step S230 based on the determination of "Yes," whereas if shape information similar to the shape information corresponding to the target component is not present in the shape DB 24, the process proceeds to step S220 based on the determination of "No."

[0037] In step S220, the control unit 12 newly adds shape information corresponding to the target component to the shape DB 24. At this time, the control unit 12 can add the shape information to the shape DB 24 together with a new name and a corresponding component identifier.

[0038] After step S210 or step S220, in step S230, the control unit 12 associates the shape information corresponding to the target component with the component data number of the target component. The "shape information corresponding to the target component" in step S230 refers to either the shape information searched from the shape DB 24 in step S200 or the shape information newly added to the shape DB 24 in step S220.

[0039] In step S240 shown in FIG. 3, the control unit 12 extracts, as a packaging code, a character or character string at a specific position from the character string that constitutes the part number of the input target component, based on a predetermined rule that defines the composition of the part number. According to the predetermined rule, it can be inferred that the packaging code is located at a second specific position, such as the number from the first character in the part number. Therefore, in step S240, the control unit 12 extracts, as a packaging code, a character or character string at a second specific position from the character string that constitutes the part number of the target component.

[0040] In step S250, the control unit 12 searches the packaging code table 22b for the packaging code extracted in step S240. The packaging code table 22b is also a type of code table 22, and describes packaging information of the part as attribute information.

[0041] FIG. 5 shows an example of the packaging code table 22b. The packaging code table 22b defines the correspondence between packaging codes, detailed packaging information for components, and component identifiers. In the packaging information, "W" indicates the size of the container that contains the components, and "P" indicates the component spacing in the container, both in millimeters. Here, we assume that the container is a reel. Therefore, the container size is the width of the reel, and the component spacing is the spacing between components in the longitudinal direction of the reel. The packaging information also includes information such as the number of components contained in the container and the material of the container.

[0042] In step S260, the control unit 12 branches the process depending on the search result in step S250. That is, if a packaging code matching the packaging code extracted in step S240 is specified in the packaging code table 22b, the process proceeds to step S270 based on the determination of "Yes," and if the packaging code extracted in step S240 is not included in the packaging code table 22b, the process proceeds to step S280 based on the determination of "No."

[0043] In step S270, the control unit 12 searches the packaging code table 22b for a component identifier corresponding to the packaging code extracted in step S240. Meanwhile, in step S280, the control unit 12 adds a new packaging code. That is, the control unit 12 adds the packaging code extracted in step S240 to the packaging code table 22b as a new packaging code. In the following step S290, the control unit 12 accepts input of packaging information such as the size of the container for the target component, the number of components housed, the component housing intervals, and the material. Steps S280 and S290 are executed in response to user operations.

[0044] For example, the user is notified that the determination result in step S260 is "No" through a display on the display unit 18, etc. The user, recognizing this notification, operates the input receiving unit 14 to instruct that the packaging code extracted in step S240 from the part number of the target part should be newly added to the packaging code table 22b, and the control unit 12 executes step S280 in response to this instruction. Next, the user operates the input receiving unit 14 to input the above-mentioned packaging information, and the control unit 12 accepts this input packaging information (step S290). The control unit 12 can add the packaging information input in step S290 to the packaging code table 22b in association with the packaging code newly added in step S280.

[0045] After step S270 or step S290, in step S300, the control unit 12 determines whether a component identifier corresponding to the packaging code extracted in step S240 is specified in the packaging code table 22b. In this case, if step S270 was executed from "Yes" in step S260, the component identifier corresponding to the packaging code extracted in step S240 is in the packaging code table 22b, so the control unit 12 determines "Yes" in step S300 and proceeds to step S320. On the other hand, if steps S280 and S290 were executed from "No" in step S260, the control unit 12 determines "No" in step S300 and proceeds to step S310.

[0046] In step S310, the control unit 12 adds a new component identifier. Step S310 is executed in response to a user operation. The user operates the input receiving unit 14 to input the component identifier of the component of interest, and the control unit 12 receives this input component identifier. The control unit 12 then adds this component identifier to the packaging code table 22b in association with the packaging code newly added in step S280. Of course, the user's operations required for steps S190 and S310 can be performed together in a single operation.

[0047] After step S300 or step S310, in step S320, the control unit 12 searches the packaging DB 26 for packaging information similar to the packaging information corresponding to the target part. The "packaging information corresponding to the target part" referred to in steps S320 to S340 refers to either the packaging information specified in the packaging code table 22b corresponding to the packaging code extracted in step S240, or the packaging information input accepted in step S290. "Similar" naturally also includes a match. When there is no match, there are various possibilities for the degree of similarity to be included in the range of similarity. Alternatively, the range of similarity may be set to 0, and the search from the packaging DB 26 may be deemed successful only if substantially all of the packaging information matches.

[0048] Packaging information for various parts is registered in the packaging DB 26. There are no particular limitations on the data structure of the packaging DB 26; for example, in the packaging DB 26, a unique name is assigned to the packaging information for each part. Furthermore, in the packaging DB 26, a part identifier may be associated with the packaging information for each part. Therefore, the control unit 12 can search the packaging DB 26 for packaging information similar to the packaging information for the target part based on the part identifier.

[0049] In step S330, the control unit 12 branches the process depending on the search result of step S320. That is, if the packing DB 26 contains packing information similar to the packing information corresponding to the target part, the process proceeds to step S350 based on the determination of "Yes," whereas if the packing DB 26 does not contain packing information similar to the packing information corresponding to the target part, the process proceeds to step S340 based on the determination of "No."

[0050] In step S340, the control unit 12 newly adds the packaging information corresponding to the target part to the packaging DB 26. At this time, the control unit 12 can add the packaging information to the packaging DB 26 together with the new name and the corresponding part identifier.

[0051] After step S330 or step S340, in step S350, the control unit 12 associates the packaging information corresponding to the target part with the component data number of the target part. The "packaging information corresponding to the target part" referred to in step S350 is either the packaging information searched from the packaging DB 26 in step S320 or the packaging information newly added to the packaging DB 26 in step S340.

[0052] In step 360, the control unit 12 registers the component data number of the component of interest and the shape information and packaging information associated with it in steps S230 and S350 as component data in the library 20. This completes the process of the flowcharts shown in FIGS.

[0053] The interpretation of the flowcharts in Figures 2 and 3 is not limited to the above description. For example, the execution order of the steps does not have to be as described above. For convenience, the processing of steps S120 to S230 will be referred to as the "shape information association processing," and the processing of steps S240 to S350 will be referred to as the "packaging information association processing." For example, the execution order of the shape information association processing and the packing information association processing may be reversed. Alternatively, the control unit 12 may execute the shape information association processing and the packing information association processing in parallel. Alternatively, the control unit 12 may execute only one of the shape information association processing and the packing information association processing.

[0054] According to the above description, the control unit 12 acquires shape information corresponding to the target component from the shape DB 24 and associates it with the component data number. The control unit 12 also acquires packaging information corresponding to the target component from the packaging DB 26 and associates it with the component data number. However, the control unit 12 may acquire shape information and packaging information corresponding to the target component from the shape code table 22a or the packaging code table 22b based on the code, instead of from the shape DB 24 or the packaging DB 26, and associate the acquired shape information and packaging information with the component data number. In other words, it is not necessary to use the shape DB 24 or the packaging DB 26 to acquire component attribute information.

[0055] In any case, steps S130 to S220 of the shape information association process and steps S250 to S340 of the packaging information association process include an example of an "attribute information acquisition process (process)" that acquires attribute information corresponding to the extracted code by referring to code table 22. That is, in the attribute information acquisition process, control unit 12 ultimately acquires shape information corresponding to the extracted code by referring to shape code table 22a. Also, control unit 12 ultimately acquires packaging information corresponding to the extracted code by referring to packaging code table 22b.

[0056] The component data number and the associated shape information correspond to at least a portion of the component data of the component of interest. Similarly, the component data number and the associated packaging information correspond to at least a portion of the component data of the component of interest. Therefore, steps S230 and S350 are examples of a "component data generation process (processing)" that generates component data associated with the component of interest based on the acquired attribute information. Step S360, which registers such component data of the component of interest in library 20, is an example of a "registration process (processing)" that registers the generated component data in library 20 stored in predetermined storage unit 16. The user can view the component data registered in library 20 at any time.

[0057] As described above, according to this embodiment, when a user inputs the part number of a target part that is publicly available from the part manufacturer, the generation device 10 automatically executes a series of steps, such as analyzing the part number, extracting a code from the part number, obtaining attribute information by referring to a code table, generating part data, and registering the part data in the library 20. This reduces input errors and the workload of the user compared to conventional methods, and enables accurate part data to be generated and registered.

[0058] The part data registered in the library 20 may be part data numbers and associated shape information and packaging information as described above, but may also be data that does not include actual attribute information such as shape information and packaging information. For example, the part data registered in the library 20 may be data that simply indicates the correspondence between part data numbers and the names of shape information in the shape DB 24 or the names of packaging information in the packaging DB 26.

[0059] In addition to shape information and packaging information, the attribute information of a part may also include the temperature characteristics, rated voltage, capacitance, etc. of the part. Therefore, in the attribute information acquisition step, the control unit 12 may also acquire the temperature characteristics, rated voltage, capacitance, etc. corresponding to the part of interest based on the analysis result of the part number of the part of interest, and may include them as part of the part data.

[0060] Although specific examples of the technology disclosed in this specification have been described in detail above, these are merely examples and do not limit the scope of the claims. The technology described in the claims includes various modifications and variations of the specific examples exemplified above. Furthermore, the technical elements described in this specification or drawings exhibit technical utility alone or in various combinations, and are not limited to the combinations described in the claims at the time of filing. Furthermore, the technology exemplified in this specification or drawings simultaneously achieves multiple objectives, and achieving one of those objectives itself has technical utility. [Explanation of symbols]

[0061] 10:Generation device 12: Control unit 12a: Program 14: Input reception section 16: Storage part 18: Display section 20: Library 22: Chord table 22a: Shape code table 22b: Packaging code table 24: Shape DB 26: Packaging DB

Claims

1. A method for generating component data that is information about components to be mounted on a board by a component mounter, comprising: a part number receiving step of receiving an input of a part number of a target part which is one of the parts; a code extraction step of analyzing the input product number and extracting a code contained in the product number; an attribute information acquisition step of acquiring the attribute information corresponding to the extracted code by referring to a code table that associates codes that may be included in the part number of the part with attribute information of the part; a component data generating step of generating the component data associated with the component of interest based on the acquired attribute information; a registration step of registering the generated part data in a library stored in a predetermined storage unit.

2. 2. The method according to claim 1, wherein the code extracting step extracts, as the code, a character or a character string at a specific position from a character string constituting the product number based on a predetermined rule that defines the configuration of the product number.

3. 2. The generation method according to claim 1, wherein the attribute information acquisition step acquires the shape information corresponding to the extracted code by referring to the code table in which shape information of the part is described as the attribute information.

4. The method of claim 3 , wherein the shape information includes dimensions of the part as well as tolerances for errors in the dimensions.

5. 2. The generation method according to claim 1, wherein the attribute information acquisition step acquires the packaging information corresponding to the extracted code by referring to the code table in which packaging information of the part is described as the attribute information.

6. The generating method according to claim 5 , wherein the packaging information includes at least one of the size, the number of components accommodated, the component accommodation interval, and the material of the container that accommodates the components.

7. A generation device that generates component data that is information about components to be mounted on a board by a component mounter, an input receiving unit; A control unit; a storage unit, the input receiving unit receives an input of a part number of a target part which is one of the parts; The control unit a code extraction process for analyzing the input product number and extracting a code contained in the product number; an attribute information acquisition process for acquiring the attribute information corresponding to the extracted code by referring to a code table that associates codes that may be included in the part number of the part with attribute information of the part; a part data generation process for generating the part data associated with the target part based on the acquired attribute information; a registration process for registering the generated part data in a library stored in the storage unit.

Images