Component mounting system, data management method, and data management program

Abstract

The present invention provides a component mounting system, etc., that can ensure appropriate traceability in a control device that manages a component mounting line. [Solution] The component mounting system comprises a component mounting device 10 that mounts components onto a substrate to produce a component mounting substrate, and a higher-level device that manages or controls the component mounting device 10. The component mounting device 10 has a storage unit that stores production-related information regarding the production of component mounting substrates, and an output unit that outputs production-related information to the higher-level device. The higher-level device includes a management device 30 that manages the component mounting device 10. The management device 30 has a management acquisition unit that acquires production-related information, and an update unit 32 that changes the version of the software stored in the management device 30. When the update unit 32 finishes changing the software version, the production-related information during the version change period is output to the management device 30.

Description

Technical Field

[0001] The present disclosure relates to a component mounting system, a data management method, and a data management program.

Background Art

[0002] In the field of component mounting lines that constitute component mounting devices for mounting components on substrates, for traceability, a management device for managing the component mounting line acquires and stores data on production history and the operation of the component mounting device. In the management device, a program related to production is executed by the installed software. In the software installed in the management device, update processes such as adding new functions, improving functions, and fixing defects are executed.

[0003] For example, Patent Document 1 discloses a software update method for updating software executed by a plurality of component mounting machines constituting a production line of substrate products to different versions. The software update method includes a specifying step in which the version of the software applied to the production process by the component mounting machine can be individually specified for each of the plurality of component mounting machines, and an updating step in which the software to be applied to the next production process that the component mounting machine is scheduled to execute is updated to the version specified by the specifying step.

[0004] According to this software update method, the software executed by the component mounting machine in the production process can be updated to the specified version at an appropriate timing according to the operating status of the component mounting machine.

Prior Art Documents

Patent Documents

[0005]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0006] However, the aforementioned software update method has the drawback that it becomes difficult to ensure traceability to the component mounting machine while the software installed on both the component mounting machine and the management device that manages the component mounting machine is being updated.

[0007] Therefore, the purpose of this disclosure is to provide a component mounting system, etc., that can ensure appropriate traceability in a control device that manages a component mounting line. [Means for solving the problem]

[0008] A component mounting system according to one aspect of the present disclosure comprises a component mounting apparatus for producing a component mounting substrate by mounting components onto a substrate, and a higher-level apparatus for managing or controlling the component mounting apparatus, wherein the component mounting apparatus has a storage unit for storing production-related information relating to the production of the component mounting substrate, and an output unit for outputting the production-related information to the higher-level apparatus, the higher-level apparatus includes a management device for managing the component mounting apparatus, the management device has a management acquisition unit for acquiring the production-related information, and an update unit for changing the version of the software stored in the management device, and when the update unit finishes changing the version of the software, the production-related information during the version change period is output to the management device.

[0009] Furthermore, a component mounting system according to one aspect of the present disclosure includes a control device for controlling a component mounting apparatus that mounts components onto a substrate to produce a component mounting substrate, and a management device for managing the component mounting apparatus via the control device, wherein the control device has a control acquisition unit for acquiring production-related information relating to the production of the component mounting substrate and an output unit for outputting the production-related information to the management device, the management device has a management acquisition unit for acquiring the production-related information and an update unit for changing the version of the software stored in the management device, the control acquisition unit acquires production-related information relating to the production of the component mounting substrate from the component mounting apparatus regardless of the version change in the management device, and the management acquisition unit acquires the production-related information when the version change is completed.

[0010] Furthermore, a data management method according to one aspect of the present disclosure is a data management method executed by a component mounting system comprising a component mounting apparatus for producing component mounting boards by mounting components onto a substrate, and a higher-level device for managing or controlling the component mounting apparatus, wherein a storage unit of the component mounting apparatus stores production-related information relating to the production of the component mounting board, an output unit of the component mounting apparatus outputs the production-related information to the higher-level device, a management acquisition unit of the higher-level device acquires the outputted production-related information, an update unit of a management device included in the higher-level device that manages the component mounting apparatus changes the software version, and when the update unit finishes the version change, the production-related information during the version change period is output to the management device.

[0011] Furthermore, a data management program relating to one aspect of this disclosure is a data management program that causes a computer to execute a data management method. [Effects of the Invention]

[0012] According to one aspect of this disclosure, a component mounting system, etc., can ensure appropriate traceability in a management device that manages a component mounting line. [Brief explanation of the drawing]

[0013] [Figure 1] Figure 1 is a block diagram showing a production system according to an embodiment. [Figure 2] Figure 2 is a block diagram of a component mounting device. [Figure 3] Figure 3 is a block diagram showing another production system according to an embodiment. [Figure 4] Figure 4 is a flowchart showing an example of the operation of the control device 1. [Figure 5] Figure 5 is a flowchart showing examples of operation when an event occurs in multiple production devices of the control device according to the embodiment. [Figure 6] Figure 6 is a flowchart showing examples of operation during production in multiple production devices of the control device according to the embodiment. [Figure 7] Figure 7 is a flowchart showing an example of the operation of the second control unit when it receives a start notification from the management device indicating that it is starting a software version change in the control device according to the embodiment. [Figure 8] Figure 8 is a flowchart showing an example of the operation of the second control unit when it receives a termination notification from the management device indicating that the software version change has been completed in the control device according to the embodiment. [Modes for carrying out the invention]

[0014] The embodiments will be described in detail below with reference to the drawings.

[0015] The embodiments described below are all general or specific examples. The numerical values, shapes, materials, components, arrangement and connection configurations of components, steps, and the order of steps shown in the following embodiments are examples only and are not intended to limit this disclosure. Furthermore, any components in the following embodiments that are not described in an independent claim will be described as optional components.

[0016] Also, each figure is a schematic diagram and is not necessarily drawn precisely. Also, in each figure, the same reference numerals are assigned to the same components.

[0017] (Embodiment) <Configuration and Function> First, the configuration and function of the production system 1 will be described while referring to FIGS. 1 to 3.

[0018] FIG. 1 is a block diagram showing the production system 1 according to the embodiment. FIG. 2 is a block diagram showing the component mounting apparatus 10. FIG. 3 is a block diagram showing another production system 1 according to the embodiment.

[0019] As shown in FIG. 1, the production system 1 is a system for producing a product. For example, the product is a mounted substrate or the like on which components and the like are mounted on a substrate. The substrate is a circuit board for forming an electronic circuit. Mounting components and the like on the substrate means that the solder printed on the substrate and the components mounted on this solder are joined by reflow. Components are a general term for electronic components other than solder.

[0020] The production system 1 includes a component mounting line L, a control device 20, and a management device 30. The control device 20 and the management device 30 are examples of upper-level devices. The component mounting system may be composed of the control device 20 and the component mounting line L, or may be composed of the control device 20 and the management device 30.

[0021] The component mounting line L is a line for producing a product and is managed by the control device 20 and the management device 30. For example, when the product is a mounted substrate, the component mounting line L is a line for mounting components on the substrate to produce the product. The component mounting line L includes a plurality of production devices M1 to M9 and produces a product by working in order among the plurality of production devices M1 to M9.

[0022] Each of the multiple production devices M1 to M9 is a device for producing a product. The product is produced through multiple processes carried out by the multiple production devices M1 to M9. For example, if the product is a mounted circuit board, production device M1 is a loading device that supplies the circuit board to the component mounting line L, production device M2 is a printing device that prints solder onto the circuit board, each of the multiple production devices M3 to M6 is a component mounting device 10 that mounts components onto the circuit board to produce a component mounted circuit board, production device M7 is an inspection device that inspects the position and mounting state of the components mounted on the circuit board, production device M8 is a reflow oven that melts the solder printed on the circuit board, and production device M9 is an unloader that unloads the mounted circuit board from the component mounting line L. Note that the production devices may also include inspection devices such as an inspection camera and an image recognition processing unit that inspect the solder printed on the circuit board and the product.

[0023] For example, production system 1 may consist of only one production device, rather than multiple devices. Therefore, production devices M1 to M9 are merely examples.

[0024] Each of the multiple production devices M1 to M9 includes a work unit 11, a first control unit 12, a first display unit 13, a mounting storage unit 15, and a first output unit 14.

[0025] For example, in the case of production device M1, the work unit 11 may be a loader or the like that transports the circuit boards mounted in the magazine. In the case of production device M2, the work unit 11 may be a mask and squeegee or the like that that print solder onto the surface of the circuit board. In the case of multiple production devices M3 to M6, the work unit 11 may be at least one of a mounting head that moves components and mounts them onto the circuit board, a nozzle that holds components, and a feeder that supplies components. In the case of production device M7, the work unit 11 may be an inspection camera and an image recognition processing unit or the like that that inspects the position and mounting state of components mounted on the circuit board. In the case of production device M8, the work unit 11 may be a heating furnace or the like that that heats and melts the solder printed on the surface of the circuit board. In the case of production device M9, the work unit 11 may be a product removal machine or the like.

[0026] For example, in the case of production device M1, the first control unit 12 may supply the substrates from the magazine to the component mounting line L by controlling the work unit 11 in accordance with control instructions from the control device 20. In the case of production device M2, the first control unit 12 may hold the substrates and masks and slide the squeegee by controlling the work unit 11 in accordance with control instructions from the control device 20. In the case of multiple production devices M3 to M6, the first control unit 12 controls the movement of the nozzles provided on the head by controlling the work unit 11 in accordance with control instructions from the control device 20 to mount components onto the substrates. In the case of production device M7, the first control unit 12 inspects the position and mounting state of the components mounted on the substrates by controlling the work unit 11 in accordance with control instructions from the control device 20. In the case of production device M8, the first control unit 12 controls the work unit 11 in accordance with control instructions from the control device 20 to perform appropriate temperature control to melt the solder and join the components and the substrates with solder. In the case of production equipment M9, the first control unit 12 controls the work unit 11 in response to control instructions from the control device 20, causing the picking machine to pick up and transport the products. If the production equipment includes an inspection device, the first control unit 12 may also control the work unit 11 in response to control instructions from the control device 20 to inspect the solder printed on the circuit board and the appearance of the products.

[0027] The first display unit 13, under the control of the first control unit 12, displays event data and trace data stored in the implementation memory unit 15, and displays operation screens, input screens, etc., for operating multiple production devices M1 to M9. The first display unit 13 is a display device such as a liquid crystal panel.

[0028] The mounting storage unit 15, under the control of the first control unit 12, stores, for example, data related to the production of component-mounted substrates. Each piece of data includes event data, which is information related to events that occurred in the component mounting apparatus 10, and trace data, which is information related to component-mounted substrates produced by the component mounting apparatus 10. Each piece of data also includes event data and trace data that occurred in production equipment other than the component mounting apparatus 10. The trace data shows, for example, the production history such as mounting points, component part numbers, lot numbers, and correction amounts. The event data shows, for example, events that occurred when creating a product, such as the start of the production equipment, the stop of the production equipment, errors that occurred in the production equipment, and the status of component mounting on the substrate.

[0029] The mounting storage unit 15 may, for example, include trace data showing the production history of loading the substrate into the component mounting line L, and event data showing events that occurred when loading the substrate into the component mounting line L, in the data of production equipment M1. The mounting storage unit 15 may, for example, include trace data showing the production history of printing solder onto the substrate, and event data showing events that occurred when printing solder onto the substrate. The data of production equipment M3 to M6 may include trace data showing the production history of mounting each component onto the substrate, and event data showing events that occurred when mounting each component onto the substrate. The data of production equipment M7 may include trace data showing the production history of inspecting the position and mounting state of the substrate on which the components are placed, and event data showing events that occurred when inspecting the position and mounting state of the substrate on which the components are placed. The data of production equipment M8 may include trace data showing the production history of creating a product by reflowing the substrate on which the components are placed, and event data showing events that occurred when reflowing the substrate on which the components are placed. The data of the production device M9 includes trace data showing the production history of the products being shipped out, and event data showing events that occurred when the products were shipped out. If the production device includes an inspection device, the data of the production device may also include trace data showing the production history of inspecting the solder printed on the board and the products, and event data showing events that occurred when printing solder on the board and when inspecting the solder condition between the reflowed components and the board. The mounting storage unit 15 is an example of a storage unit. Trace data and event data are examples of production-related information.

[0030] The physical components of the data storage unit 35 may include not only memory but also an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

[0031] The first output unit 14 is an interface for outputting trace data and event data corresponding to each of the multiple production devices M1 to M9 stored in the implementation memory unit 15 to the control device 20. The first output unit 14 outputs the trace data and event data for each of the multiple production devices M1 to M9 to the management device 30. Specifically, the first output unit 14, under the control of the first control unit 12, outputs the respective trace data and event data corresponding to each of the multiple production devices M1 to M9 to the management device 30 via the control device 20. The first output unit 14 is an example of an output unit.

[0032] The control device 20 controls multiple production devices M1 to M9 in the component mounting line L. The control device 20 also monitors each of the automatically operating production devices M1 to M9 in real time. For example, the control device 20 monitors each of the production devices M1 to M9 in real time by acquiring trace data and event data measuring the status of each production device. The control device 20 can also control the production devices M1 to M9 based on the acquired trace data and event data. Note that, for example, the control device 20 does not need to control all of the production devices M1 to M9; it may control only at least one of them.

[0033] Each control device 20 includes a second acquisition unit 21, a second control unit 22, a second display unit 23, a control storage unit 25, and a second output unit 24.

[0034] The second acquisition unit 21 is an interface for acquiring each data output by the component mounting line L. For example, the second acquisition unit 21 acquires each trace data and each event data output by each of the multiple production devices M1 to M9. There may be cases where the control device 30 is temporarily unable to acquire each trace data and each event data due to a version change, but the second acquisition unit 21 acquires the trace data and event data output by each of the multiple production devices M1 to M9 regardless of the version change in the control device 30. The second acquisition unit 21 is an example of a control acquisition unit.

[0035] The second control unit 22 stores each trace data and event data acquired by the second acquisition unit 21 in the control storage unit 25, associating them with each of the multiple production devices M1 to M9. In other words, each time the second control unit 22 acquires trace data and event data associated with each of the multiple production devices M1 to M9, it further stores the acquired trace data and event data in the control storage unit 25.

[0036] Furthermore, the second control unit 22 can output control instructions to control multiple production devices M1 to M9. In other words, the second control unit 22 can control each of the multiple production devices M1 to M9 by outputting control instructions to each of them. For example, the second control unit 22 outputs a control instruction to production device M1 to load a circuit board into the component mounting line L. The second control unit 22 outputs a control instruction to production device M2 to print solder onto the circuit board. The second control unit 22 also outputs control instructions to production devices M3 to M6 to mount components onto the circuit board. The second control unit 22 also outputs a control instruction to production device M7 to inspect the position and mounting status of components placed on the solder of the circuit board. The second control unit 22 also outputs a control instruction to production device M8 to reflow the circuit board with the components on it to create a product. The second control unit 22 also outputs a control instruction to production device M9 to remove and ship the product.

[0037] The second display unit 23 displays trace data and event data stored in the control memory unit 25, and also displays operation screens, input screens, etc., for operating the control device 20. The second display unit 23 is a display device such as a liquid crystal panel.

[0038] The control memory unit 25 stores, for example, data relating to multiple production devices M1 to M9. This data also stores trace data and event data. Specifically, the control memory unit 25 stores printing machine data, mounting machine data (M3) to (M6), inspection machine data, etc. The printing machine data corresponds to production device M2, which is a printing device, and includes trace data such as board information to identify the board, solder information printed on the board, and location information of the printed solder, as well as event data such as the start of the printing device, the stop of the printing device, and errors that occurred in the printing device. The mounting machine data (M3) to (M6) corresponds to production devices M3 to M6, which are component mounting devices 10, and includes trace data such as mounting points, part numbers, lot numbers, and correction amounts, as well as event data such as the start of the component mounting device 10, the stop of the component mounting device 10, errors that occurred in the component mounting device 10, and the status of component mounting on the board. The inspection machine data corresponds to the production machine M7, which is a mounting inspection device, and includes trace data related to the inspection of the mounting status of components, as well as event data such as the start of the inspection device, the stop of the inspection device, and errors that occurred in the inspection device.

[0039] The control memory unit 25 may also store input data, reflow data, output data, etc. Input data corresponds to the production equipment M1, which is the input device, and includes trace data showing the production history of inputting the substrate to the component mounting line L, and event data showing events that occurred when inputting the substrate to the component mounting line L. Reflow data corresponds to the production equipment M8, which is the reflow oven, and includes trace data showing the production history of creating a product by reflowing a substrate with components on it, and event data showing events that occurred when reflowing a substrate with components on it. Output data corresponds to the production equipment M9, which is the output device, and includes trace data showing the production history of the output product, and event data showing events that occurred when outputting the product.

[0040] The physical components of the control memory unit 25 may include not only memory but also an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

[0041] The second output unit 24 is an interface for outputting trace data and event data corresponding to each of the multiple production devices M1 to M9 stored in the control memory unit 25 to the management device 30. The second output unit 24 is an example of an output unit.

[0042] The second output unit 24 outputs trace data and event data for each of the multiple production devices M1 to M9 to the management device 30, according to the status of the management device 30.

[0043] For example, if the software installed in the management device 30 is updated, the second output unit 24 will be controlled by the second control unit 22 and will not output each trace data and each event data to the management device 30.

[0044] Furthermore, for example, if the software installed in the management device 30 is updated to a new version, and the component mounting device 10 stops while producing a component mounting board, the second output unit 24, under the control of the second control unit 22, will not output event data generated when the component mounting device 10 stopped to the management device 30. Naturally, the second output unit 24, under the control of the second control unit 22, will output trace data and event data for the period during which the component mounting device 10 is operating to the management device 30.

[0045] Furthermore, for example, if the software installed in the management device 30 is being updated, and the component mounting device 10 is preparing to produce a component mounting board, the second output unit 24 is controlled by the second control unit 22 to not output event data that occurred during the preparation of the component mounting device 10 to the management device 30.

[0046] The management device 30 is a device that manages the component mounting device 10 via the control device 20. The management device 30 includes a third acquisition unit 31, a processing unit 36, an input / output unit 33, an update unit 32, a management storage unit 35, and a notification unit 37.

[0047] The third acquisition unit 31 is an interface for acquiring each data output by the component mounting line L, and acquires each data from the component mounting line L via the control device 20. For example, the third acquisition unit 31 acquires each trace data and each event data output by each of the multiple production devices M1 to M9 from the control device 20 during periods other than the software version change period. During the software version change period, the management device 30 cannot acquire each trace data and each event data, but once the software version change is complete, the third acquisition unit 31 acquires each trace data and each event data accumulated during the version change period from the control device 20. The third acquisition unit 31 is an example of a management acquisition unit.

[0048] The processing unit 36 ​​stores each trace data and event data acquired by the third acquisition unit 31 in the management storage unit 35, associating them with each of the multiple production devices M1 to M9. In other words, each time the processing unit 36 ​​acquires trace data and event data associated with each of the multiple production devices M1 to M9, it adds the acquired trace data and event data to the management storage unit 35 and stores it there. As a result, the management storage unit 35 can acquire trace data and event data that occurred during the entire period in which the multiple production devices M1 to M9 were in operation.

[0049] The input / output unit 33 can receive input from the user, display trace data and event data stored in the management storage unit 35, and display operation screens, input screens, etc., for operating the control device 20. The input / output unit 33 is, for example, a touch panel display in which a touch panel and a display unit such as a monitor are integrated. Alternatively, the input / output unit 33 may consist of an input unit such as a keyboard and a display unit such as a monitor.

[0050] The update unit 32 manages the software stored in the management storage unit 35. For example, the update unit 32 performs a process to change the version of the software stored in the management device 30. In other words, the update unit 32 updates the current version of the software to a newer version. The software is firmware incorporated into the management storage unit 35 for the control device 20 to control the operation of the component mounting line L.

[0051] The management memory unit 35 stores software for the control device 20 to control the operation of the component mounting line L. The management memory unit 35 also stores trace data and event data corresponding to each of the multiple production devices M1 to M9. The physical components of the management memory unit 35 may include not only memory but also an HDD (Hard Disk Drive) or an SSD (Solid State Drive).

[0052] The notification unit 37 notifies the component mounting device 10 of the start of the software version change when the update unit 32 starts changing the software version (start notification). The notification unit 37 also notifies the component mounting device 10 of the completion of the software version change when the update unit 32 finishes changing the software version (completion notification).

[0053] In this embodiment, the configuration is shown as one in which multiple production devices M1 to M9 and the control device 20 are connected in a communicative manner, and the control device 20 and the management device 30 are connected in a communicative manner. However, the configuration is not limited to the above. For example, as shown in Figure 3, the management device 30 may be connected in a communicative manner to multiple production devices M1 to M9. In this case, when the management device 30 changes the software version, the multiple production devices M1 to M9 receive information from the management device 30 indicating the start of the version change, and each trace data and event data from each of the multiple production devices M1 to M9 may be stored in the implementation storage unit 15. Then, when the management device 30 finishes the software version change, the multiple production devices M1 to M9 receive information from the management device 30 indicating the end of the version change, and each trace data and event data that occurred during this version change period and are stored in the implementation storage unit 15 may be output to the management device 30.

[0054] <Example of operation 1> Next, with reference to Figure 4, we will describe example 1 of the operation of the control device 30.

[0055] Figure 4 is a flowchart showing an example of operation 1 of the management device 30 according to the embodiment.

[0056] First, we will explain an example of how to change the software version of the management device 30.

[0057] First, the update unit 32 of the management device 30 determines whether or not there is software to be updated (S11). In other words, the update unit 32 determines whether or not there is software that can be updated from among the one or more software programs stored in the management storage unit 35.

[0058] If the update unit 32 determines that there is no software to change the version of (NO in S11), it repeats the process in step S11.

[0059] On the other hand, if the update unit 32 determines that there is software to be changed (YES in S11), the notification unit 37, under the control of the processing unit 36, sends a start notification to the control device 20, which is information indicating the start of the software version change, before starting the version change (S12).

[0060] Next, the update unit 32 starts changing the version of the relevant software while the component mounting line L is in production (S13).

[0061] The control device 20 stores the trace data and event data output from multiple production devices M1 to M9 that constitute the component mounting line L in the control storage unit 25, and outputs the trace data and event data acquired from the multiple production devices M1 to M9 to the management device 30 at predetermined intervals. However, when the control device 20 receives a start notification from the management device 30, it temporarily stops outputting the trace data and event data of each of the multiple production devices M1 to M9 to the management device 30 and accumulates the trace data and event data. In other words, when information indicating the start of a version change is output (in this embodiment, when the control device 20 receives information indicating the start of a version change), the second output unit 24 does not output the trace data and event data to the management device 30. Even in this case, since the control device 20 acquires the trace data and event data of each of the multiple production devices M1 to M9, the control storage unit 25 of the control device 20 accumulates the trace data and event data of each of the multiple production devices M1 to M9 during the period in which the software version is being changed.

[0062] Next, when the update unit 32 finishes changing the software version, the notification unit 37, under the control of the processing unit 36, sends a completion notification to the control device 20, which is a notification indicating the completion of the software version change (S14).

[0063] The control device 20, upon receiving a completion notification from the management device 30, outputs to the management device 30 each trace data and each event data accumulated during the period in which the software version was being changed. Specifically, the second control unit 22 causes the second output unit 24 to output to the management device 30 each trace data and each event data accumulated in the control storage unit 25 between the time the start notification is received and the time the completion notification is received. In other words, when information indicating the end of the version change is output (in this embodiment, when the control device 20 receives information indicating the end of the version change), the second output unit 24 outputs to the management device 30 each trace data and each event data accumulated in the control storage unit 25 during the period in which the software version was being changed.

[0064] As a result, even if the software version is changed, the management device 30 can acquire the trace data and event data for each of the multiple production devices M1 to M9 that could not be acquired during the software version change. In this way, the management storage unit 35 of the management device 30 can store the trace data and event data that occurred during the entire period in which the multiple production devices M1 to M9 were operated, so that even if there is a period of software version change in the management device 30, the trace data and event data will be supplemented.

[0065] <Example of operation 2> Next, we will explain example 2 of the operation of the control device 20 with reference to Figures 5 to 8.

[0066] First, referring to Figure 5, we will explain an example of the operation of the control device 20 when event data is generated in multiple production devices M1 to M9.

[0067] Figure 5 is a flowchart showing examples of operations when an event occurs in multiple production devices M1 to M9 of the control device 20 according to the embodiment.

[0068] First, the control unit 30 determines whether or not it has started a software version change (S21). In other words, the second control unit 22 determines whether or not it has received a start notification from the control unit 30 indicating that it has started a software version change. If it has received a start notification, it turns on a flag indicating that it has started a version change. The flag indicating that it has started a version change remains ON until it receives a termination notification indicating that it has finished changing the software version.

[0069] If the second control unit 22 determines that it has received a start notification from the management device 30 indicating that a software version change is to begin (YES in S21), it stores the event data for each of the multiple production devices M1 to M9 that occur during transmission in the control storage unit 25 (S22) and terminates this flow.

[0070] On the other hand, if the second control unit 22 determines that it has not received a start notification from the management device 30 indicating that a software version change has started (NO in S21), in other words, if the flag indicating that a version change has started is in the OFF state, it determines whether the event data of each of the multiple production devices M1 to M9 acquired by the control storage unit 25 is being transmitted from the multiple production devices M1 to M9 to the management device 30 (S23).

[0071] Next, if the second control unit 22 is not currently transmitting any event data (NO in S23), it sends the event data to the management device 30 (S24) and terminates this flow.

[0072] On the other hand, if the second control unit 22 has transmitted event data (YES in S23), it proceeds to step S22 and terminates this flow. For example, if the component mounting line L is in the process of preparing to produce component mounting boards or is temporarily stopped, trace data is not generated because production is stopped, but event data such as errors that occurred in the production equipment and the status of component mounting on the board are generated.

[0073] Next, with reference to Figure 6, we will explain an example of the operation of the control device 20 when trace data is generated in multiple production devices M1 to M9.

[0074] Figure 6 is a flowchart showing examples of operation during production in multiple production devices M1 to M9 of the control device 20 according to the embodiment.

[0075] First, the control unit 30 determines whether or not it has started a software version change (S31). That is, the second control unit 22 determines whether or not it has received a start notification from the control unit 30 indicating that it has started a software version change, and if it has received a start notification, it turns ON a flag indicating that it has started a version change. The flag indicating that it has started a version change remains ON until it receives a termination notification indicating that it has finished changing the software version.

[0076] If the second control unit 22 determines that it has received a start notification from the management device 30 indicating that it is starting a software version change (YES in S31), it stores the trace data of each of the multiple production devices M1 to M9 that are generated during transmission in the control storage unit 25 (S32) and terminates this flow.

[0077] On the other hand, if the second control unit 22 determines that it has not received a start notification from the management device 30 indicating the start of a software version change (NO in S31), it determines whether the trace data (each data) of each of the multiple production devices M1 to M9 acquired by the control storage unit 25 is being transmitted from the multiple production devices M1 to M9 to the management device 30 (S33).

[0078] Next, if the second control unit 22 is not currently transmitting any trace data (NO in S33), it sends event data to the management device 30 (S34) and terminates this flow.

[0079] On the other hand, if the second control unit 22 has not transmitted any trace data (YES in S33), it proceeds to step S32 and terminates this flow.

[0080] Next, with reference to Figures 7 and 8, an example of the operation of the second control unit 22 when it receives a start notification from the management device 30 indicating the start of a software version change and an end notification indicating that the software version change has been completed will be described.

[0081] Figure 7 is a flowchart showing an example of the operation of the second control unit 22 when it receives a start notification from the management device 30 indicating that it is starting a software version change in the control device 20 according to the embodiment.

[0082] First, when the second control unit 22 receives a start notification from the management device 30 indicating that a software version change has begun, it turns on a flag indicating that a version change has begun (S41) and terminates this flow. The flag indicating that a version change has begun remains ON until a termination notification indicating that the software version change has ended is received.

[0083] Figure 8 is a flowchart showing an example of the operation of the second control unit 22 in the control device 20 according to the embodiment when it receives a termination notification from the management device 30 indicating that the software version change has been terminated.

[0084] First, the second control unit 22 turns ON a "transmission in progress" flag, which is a flag for transmitting each trace data or event data of each of the multiple production devices M1 to M9 that are stored in the control storage unit 25 and occur while the management device 30 is changing the software version and transmitting each trace data or event data (S51).

[0085] Next, the second control unit 22 controls the second output unit 24 during the period from the start notification to the end notification, or while each trace data or each event data is being transmitted, to output the event data or trace data of the multiple production devices M1 to M9 acquired by the control storage unit 25 to the management device 30 (S52).

[0086] Next, the second control unit 22 turns OFF the transmission flag when it has finished sending event data or trace data of multiple production devices M1 to M9 acquired by the control storage unit 25 to the management device 30 between the start notification and the end notification (S53).

[0087] Next, the second control unit 22 turns off the flag indicating that a version change has started, in conjunction with turning off the transmission flag (S54). As a result, the management storage unit 35 of the management device 30 can store each trace data and event data generated during the entire period in which the multiple production devices M1 to M9 were operated, so that each event data or trace data of each of the multiple production devices M1 to M9 that occurred during the software version change period of the management device 30 is complemented.

[0088] <Effects and Effects> Next, the effects of the component mounting system, data management method, and data management program in this embodiment will be described.

[0089] As described above, the component mounting system of Technology 1 according to this embodiment comprises a component mounting device 10 that mounts components onto a substrate to produce a component mounting substrate, and a higher-level device that manages or controls the component mounting device 10. The component mounting device 10 has a storage unit (mounting storage unit 15) that stores production-related information (trace data and event data) related to the production of component mounting substrates, and an output unit (first output unit 14) that outputs production-related information (trace data and event data) to the higher-level device. The higher-level device includes a management device 30 that manages the component mounting device 10. The management device 30 has a management acquisition unit (third acquisition unit 31) that acquires production-related information (trace data and event data), and an update unit 32 that changes the version of the software stored in the management device 30. When the update unit 32 finishes changing the software version, the production-related information (trace data and event data) during the version change period is output to the management device 30.

[0090] According to this, even if the component mounting line L, i.e., the component mounting device 10, continues to operate during the period in which the software in the management device 30 is being updated, the mounting storage unit 15 can store trace data and event data from the component mounting device 10 during this period. Once the software update in the management device 30 is complete, the management device 30 can retrieve the trace data and event data from the component mounting device 10 stored in the mounting storage unit 15 during this period.

[0091] Therefore, according to this embodiment, appropriate traceability can be ensured in the management device 30 that manages the component mounting line L.

[0092] Furthermore, the component mounting system of Technology 2 according to this embodiment is the component mounting system described in Technology 1. In this case, the management device 30 includes a notification unit 37 that outputs information indicating the start of a software version change and information indicating the end of a version change (start notification and end notification). When information indicating the start of a version change (start notification) is output, no production-related information is output to the management device 30, and when information indicating the end of a version change (end notification) is output, production-related information (trace data and event data) is output to the management device 30.

[0093] According to this, the component mounting device 10 can understand the period from when it receives a start notification to when it receives a termination notification, that is, the period during which the software version in the management device 30 is changed. For this reason, the component mounting device 10 can store trace data and event data for that period and, after receiving a termination notification, can transmit the trace data and event data accumulated during that period to the management device 30. As a result, according to this disclosure, more appropriate traceability can be ensured in the management device 30 that manages the component mounting line L.

[0094] Furthermore, the component mounting system of Technology 3 according to this embodiment is the component mounting system described in Technology 2. In this case, the production-related information includes information (event data) related to events that occur in the component mounting device 10.

[0095] According to this, the management device 30 will be able to acquire event data from the component mounting device 10 during the period in which the software version is changed. Therefore, appropriate traceability can be ensured in the management device 30 that manages the component mounting line L.

[0096] Furthermore, the component mounting system of Technology 4 according to this embodiment is the component mounting system described in Technology 2 or 3. In this case, the production-related information includes information (trace data) related to the component mounting board produced by the component mounting device 10.

[0097] According to this, the management device 30 will be able to acquire trace data from the component mounting device 10 during the period in which the software version is changed. Therefore, appropriate traceability can be ensured in the management device 30 that manages the component mounting line L.

[0098] Furthermore, the component mounting system of Technology 5 according to this embodiment is the component mounting system described in Technology 3. In this case, if the component mounting device 10 stops (temporarily stops) while producing a component mounting board, information regarding the event that occurred in the component mounting device 10 (event data) is output to the management device 30.

[0099] According to this, even if the control device 30 changes the software version when the component mounting device 10 stops, the mounting storage unit 15 can store the event data that occurred in the component mounting device 10. Therefore, appropriate traceability can be ensured in the control device 30 that manages the component mounting line L.

[0100] Furthermore, the component mounting system of Technology 6 according to this embodiment is the component mounting system described in Technology 3. In this case, when the component mounting device 10 is preparing to produce a component mounting board (pre-production preparation), information regarding events that occur in the component mounting device 10 (event data) is output to the management device 30.

[0101] According to this, even if the control device 30 changes the software version while the component mounting device 10 is preparing for production, the mounting storage unit 15 can store the event data that occurred in the component mounting device 10. Therefore, appropriate traceability can be ensured in the control device 30 that manages the component mounting line L.

[0102] Furthermore, the component mounting system of Technology 7 according to this embodiment includes a control device 20 that controls a component mounting apparatus 10 that mounts components onto a substrate to produce component mounting substrates, and a management device 30 that manages the component mounting apparatus 10 via the control device 20. The control device 20 has a control acquisition unit (second acquisition unit 21) that acquires production-related information regarding the production of component mounting substrates, and an output unit (second output unit 24) that outputs production-related information to the management device 30. The management device 30 has a management acquisition unit (third acquisition unit 31) that acquires production-related information, and an update unit 32 that changes the version of the software stored in the management device 30. The control acquisition unit (second acquisition unit 21) acquires production-related information regarding the production of component mounting substrates from the component mounting apparatus 10 regardless of the version change in the management device 30, and the management acquisition unit (third acquisition unit 31) acquires production-related information when the version change is completed.

[0103] According to this, even if the component mounting line L, i.e., the component mounting device 10, continues to operate during the period in which the software in the management device 30 is being updated, the control storage unit 25 can store trace data and event data of the component mounting device 10 during this period. Once the software update in the management device 30 is complete, the management device 30 can acquire the trace data and event data of the component mounting device 10 stored in the control storage unit 25 during this period from the control device 20.

[0104] Therefore, according to this embodiment, appropriate traceability can be ensured in the management device 30 that manages the component mounting line L.

[0105] Furthermore, the data management method of Technology 8 according to this embodiment is a data management method executed by a component mounting system comprising a component mounting apparatus 10 that mounts components onto a substrate to produce a component mounting substrate, and a higher-level device that manages or controls the component mounting apparatus 10. The storage unit of the component mounting apparatus 10 stores production-related information (trace data and event data) related to the production of component mounting substrates, the output unit of the component mounting apparatus 10 outputs the production-related information (trace data and event data) to the higher-level device, the management acquisition unit (third acquisition unit 31) of the higher-level device acquires the outputted production-related information (trace data and event data), the update unit 32 of the management device 30 which manages the component mounting apparatus 10 included in the higher-level device changes the software version, and when the update unit 32 finishes the version change, the production-related information (trace data and event data) during the version change period is output to the management device 30.

[0106] This method also produces the same effects as described above.

[0107] Furthermore, the data management program of the technology 9 according to this embodiment causes a computer to execute a data management method.

[0108] This program also produces the same effects as described above.

[0109] (Other variations) The component mounting system and the like related to this disclosure have been described above based on the embodiments described above, but this disclosure is not limited to these embodiments. Various modifications to the embodiments that a person skilled in the art could conceive of may also be included in the scope of this disclosure, as long as they do not deviate from the spirit of this disclosure.

[0110] For example, each control unit, processing unit, and update unit included in the production system, which includes the component mounting system according to the above embodiment, are typically implemented as LSIs, which are integrated circuits. These may be individually integrated into a single chip, or some or all of them may be integrated into a single chip.

[0111] Furthermore, integrated circuit implementation is not limited to LSIs; it can also be achieved with dedicated circuits or general-purpose processors. Field Programmable Gate Arrays (FPGAs), which can be programmed after LSI manufacturing, or reconfigurable processors, which allow for the reconfiguration of the connections and settings of circuit cells within the LSI, may also be used.

[0112] In each of the above embodiments, each component may be implemented by dedicated hardware or by executing a software program suitable for each component. Each component may also be implemented 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 or semiconductor memory.

[0113] Furthermore, the division of functional blocks in the block diagram is just one example; multiple functional blocks can be implemented as a single functional block, a single functional block can be divided into multiple parts, or some functions can be moved to other functional blocks. In addition, the functions of multiple functional blocks with similar functions can be processed in parallel or time-sharing by a single piece of hardware or software.

[0114] Furthermore, this disclosure also includes forms obtained by applying various modifications to each of the above embodiments that a person skilled in the art could conceive, as well as forms realized by arbitrarily combining the components and functions of each embodiment without departing from the spirit of this disclosure. [Industrial applicability]

[0115] The component mounting system and the like described herein are useful in the field of mounting components onto a circuit board. [Explanation of Symbols]

[0116] 10. Component mounting equipment (component mounting system) 14. First Output Section (Output Section) 15. Implemented Memory Unit (Memory Unit) 20 Control devices (higher-level devices, component mounting systems) 21. Second acquisition unit (control acquisition unit) 24. Second Output Section (Output Section) 30. Management devices (higher-level devices, component mounting systems) 31 Third Acquisition Department (Management Acquisition Department) 32 Update section 37 Notification Department

Claims

1. A component mounting machine that produces component-mounted circuit boards by mounting components onto a circuit board, The system includes a higher-level device that manages or controls the aforementioned component mounting device, The aforementioned component mounting device is A storage unit that stores production-related information concerning the production of the aforementioned component mounting board, It has an output unit that outputs the production-related information to the aforementioned higher-level device, The aforementioned higher-level device includes a management device for managing the component mounting device, The aforementioned control device is A management and acquisition unit that acquires the aforementioned production-related information, The management device has an update unit that changes the version of the software stored in it. When the update unit completes the software version change, the production-related information during the version change period is output to the management device. Component mounting system.

2. The management device includes a notification unit that outputs information indicating the start of the version change of the software and information indicating the end of the version change. When the information indicating the start of the version change is output, the production-related information is not output to the management device. When information indicating the completion of the version change is output, the production-related information is output to the management device. The component mounting system according to claim 1.

3. The aforementioned production-related information includes information related to events that occurred in the component mounting device. The component mounting system according to claim 2.

4. The aforementioned production-related information includes information related to the component-mounted substrate produced by the component mounting apparatus. The component mounting system according to claim 2 or 3.

5. If the component mounting device stops while producing the component mounting board, information regarding the event that occurred in the component mounting device is output to the management device. The component mounting system according to claim 3.

6. When the component mounting apparatus is preparing to produce the component mounting board, information regarding the event that occurred in the component mounting apparatus is output to the management device. The component mounting system according to claim 3.

7. A control device that controls a component mounting machine that produces component-mounted circuit boards by mounting components onto a circuit board, The system includes a control device that manages the component mounting device via the control device, The control device is A control acquisition unit that acquires production-related information regarding the production of the aforementioned component mounting board, The system includes an output unit that outputs the production-related information to the management device, The aforementioned control device is A management and acquisition unit that acquires the aforementioned production-related information, The management device has an update unit that changes the version of the software stored in it. Regardless of the version change in the management device, the control acquisition unit acquires the production-related information regarding the production of the component mounting board from the component mounting device. The aforementioned management and acquisition unit acquires the production-related information once the version change is completed. Component mounting system.

8. A data management method executed by a component mounting system comprising a component mounting apparatus for producing component-mounted circuit boards by mounting components onto a circuit board, and a higher-level apparatus for managing or controlling the component mounting apparatus, The memory unit of the component mounting apparatus stores production-related information concerning the production of the component mounting board. The output unit of the component mounting device outputs the production-related information to the aforementioned higher-level device. The outputted production-related information is acquired by the management acquisition unit of the higher-level device. The update unit of the management device that manages the component mounting device included in the above-mentioned higher-level device changes the software version. When the update unit completes the version change, the production-related information during the version change period is output to the management device. Data management methods.

9. To cause a computer to execute the data management method described in claim 8. Data management program.

Images