JP7220679B2 - board working system - Google Patents

Description

This specification discloses a file management device and a board working system.

2. Description of the Related Art Conventionally, there has been known a method for managing files of images captured in relation to picking up and arranging of components when work is performed on a board such as picking up components and arranging them on the board. For example, in Patent Document 1, a file in which a tracking key is associated with an image is managed. This makes it possible to investigate the cause of defects.

Japanese Patent Publication No. 2009-538530

By the way, when a large number of images are captured, such as images captured by each of a plurality of work devices as described above, there is a possibility that files storing different images have the same file name. In particular, in recent years, as work quality has been required to improve, there has been an increasing need to capture as many images as possible to investigate the cause of defects, so the possibility of duplication of file names is also higher. become a thing. If the file name is duplicated, the image in the file overwritten and saved will be deleted, making it impossible to investigate the cause using the image.

A main object of the present disclosure is to prevent duplication of file names and appropriately manage image files.

The present disclosure has taken the following means to achieve the above-mentioned main objectives.

A file management device of the present disclosure is a file management device for managing a file of an image captured by a working device that performs a predetermined work on a board, and includes a file creation unit that creates a file that stores the image; A file name setting unit for setting a file name including identification information for uniquely identifying the file as the file name.

The file management device of the present disclosure sets a file name including identification information that uniquely identifies the file as the file name of the file storing the image captured by the working device. As a result, duplication of file names of files storing different images can be prevented, so that files can be prevented from being overwritten by mistake. Therefore, duplication of file names can be prevented and image files can be appropriately managed.

1 is an explanatory diagram showing an example of a schematic configuration of a substrate working system 10; FIG. FIG. 2 is a configuration diagram showing an outline of the configuration of the mounting apparatus 20; FIG. 4 is an explanatory diagram showing the electrical connection relationship among the mounting device 20, the management device 40, and the file server 50; 4 is a flowchart showing an example of an implementation processing routine; FIG. 4 is an explanatory diagram showing an example of an image file FL; 4 is an explanatory diagram of an image file FL stored in a storage unit 54 of the file server 50; FIG. FIG. 4 is an explanatory diagram of an image file FL of a modified example;

Next, embodiments of the present disclosure will be described with reference to the drawings. FIG. 1 is an explanatory diagram showing an example of the schematic configuration of the board working system 10, FIG. 2 is a schematic diagram showing the configuration of the mounting device 20, and FIG. 50 is an explanatory diagram showing the electrical connection relationship of 50. FIG. 1 and 2, the horizontal direction is the X-axis direction, the front-rear direction is the Y-axis direction, and the vertical direction is the Z-axis direction.

As shown in FIG. 1, the board working system 10 includes a printer 12, a print inspection device 14, a plurality of mounting devices 20, a mounting inspection device 30, a management device 40, and a file server 50. These are connected to LAN 18 as a network. The printing device 12 prints on the substrate S (see FIG. 2) by forcing solder into the pattern holes formed in the screen mask. The print inspection device 14 inspects the state of solder printed by the printer 12 . The mounting device 20 is arranged along the transport direction (X-axis direction) of the board S, and mounts components on the board S. As shown in FIG. The mounting inspection device 30 inspects the mounting state of the components mounted on the board S by the mounting device 20 . The management device 40 manages the board working system 10 as a whole. The file server 50 stores various files. The printing device 12, the printing inspection device 14, the plurality of mounting devices 20, and the mounting inspection device 30 are arranged in this order in the transport direction of the board S to form a production line. In addition to these devices, the production line may also include a reflow device for reflowing the board S on which components are mounted, and the mounting inspection device 30 may be arranged downstream of the reflow device. .

As shown in FIG. 2, the mounting apparatus 20 includes a substrate conveying device 21 that conveys a substrate S, a feeder 22 that feeds a tape containing components at a predetermined pitch and supplies the components, and the components supplied by the feeder 22. A head 23 having a nozzle 24 (see FIG. 3) to be sucked and a head moving device 25 for moving the head 23 in the XY directions are provided. A plurality of feeders 22 are set in the mounting apparatus 20 so as to be able to supply a plurality of types of components. Although not shown, the head 23 is provided with one or more nozzle holders that exchangeably hold the nozzles 24 . The mounting apparatus 20 can be replaced with one of a plurality of types of heads 23 having different numbers of nozzle holders arranged therein, and can be replaced with one of the plurality of types of nozzles 24 suitable for the type of components to be picked up. there is The mounting apparatus 20 also includes a mark camera 26 , a parts camera 27 , a nozzle station 28 , and a mounting control device 29 (see FIG. 3 ) that controls the entire mounting apparatus 20 . The mark camera 26 is attached to the head 23, and captures an image of the reference mark, the board ID, and the like attached to the board S from above. The parts camera 27 is installed between the feeder 22 and the substrate transfer device 21, and images the parts sucked by the nozzle 24 from below. The nozzle station 28 accommodates a plurality of types of nozzles 24 that can be exchanged according to the type of component to be picked up.

The mounting control device 29 is composed of a well-known CPU, ROM, RAM, etc., and has a time stamp function of issuing a time stamp according to the time measured by the internal clock. Various application programs and the like are stored in the ROM of the mounting control device 29, including a program for generating a UUID (Universally Unique Identifier). Images from the mark camera 26 and the parts camera 27 are input to the mounting control device 29 . The mounting control device 29, for example, processes the image of the board S captured by the mark camera 26 to obtain the board ID, or recognizes the position of the board mark attached to the board S to determine the position of the board S. to recognize Further, the mounting control device 29 determines whether or not the component is sucked by the nozzle 24 based on the image captured by the parts camera 27, and determines the sucking posture of the component. Further, when the feeder 22, the head 23, and the nozzle 24 are attached, the mounting control device 29 acquires the feeder ID, the head ID, and the nozzle ID, respectively, and stores them in the RAM. The mounting control device 29 also outputs drive signals to the substrate transfer device 21, the head 23, the head moving device 25, and the like.

The management device 40 includes a management control device 42, a storage unit 44, an input device 46, and a display 48, as shown in FIG. The management control device 42 is configured as a microprocessor centering on a CPU. The storage unit 44 is a device such as an HDD that stores various information such as processing programs. The input device 46 includes a keyboard, mouse, etc. for inputting various commands by the operator. The display 48 is a liquid crystal display device that displays various information. The storage unit 44 also stores production job information. In each mounting device 20, the production job information includes information on the types of components to be mounted on the substrate S, information on the mounting order of each component, information on the mounting position of each component, information on the feeder 22 that supplies each component, and component mounting information. Information on the head 23 used for the production, information on the nozzle 24 for picking up components, information on the number of substrates S to be produced, etc. are determined. The management control device 42 is communicably connected to the mounting control device 29 via the LAN 18, receives information on the mounting status of the mounting device 20 from the mounting control device 29, and sends production job information to the mounting control device 29. or send. The management control device 42 is also communicably connected to each control device (not shown) of the printing device 12, the print inspection device 14, and the mounting inspection device 30 via the LAN 18, and receives information about work status from each device. or send work orders.

The file server 50 includes a storage control device 52 and a storage unit 54, as shown in FIG. The storage control device 52 is configured as a microprocessor centering on a CPU. The storage unit 54 is a device such as an HDD that stores files containing various information such as image files. The storage control device 52 is communicably connected to the management control device 42 and the mounting control device 29 via the LAN 18, stores the information file transmitted from the management control device 42 in the storage unit 54, and stores the information file transmitted from the management control device 42 to the mounting control device. 29 is stored in the storage unit 54 . The storage control device 52 is communicably connected to each control device of the printing device 12, the print inspection device 14, and the mounting inspection device 30 via the LAN 18, and stores various files transmitted from each control device. 54. Various files stored in the storage unit 54 of the file server 50 can be shared on the LAN 18 . Therefore, for example, the operator can use the input device 46 to input an instruction to read a file stored in the storage unit 54 of the file server 50 and display the contents of the file on the display 48 . Note that the file server 50 may be provided with a display and an input device, and the input device of the file server 50 may be used to input a file readout instruction to be displayed on the display of the file server 50 .

Next, the operation of the board working system 10 of this embodiment configured in this manner will be described. Here, the operation of mounting a component on the board S will be described. FIG. 4 is a flow chart showing an example of a mounting processing routine. This routine is executed by the mounting control device 29 of each mounting device 20 . When this routine is started, the mounting control device 29 first selects the feeder type, head type, nozzle type, component type, mounting position, etc. for the component to be mounted from the production job information transmitted from the management control device 42. Information necessary for mounting is acquired (S100). If the head type or nozzle type based on the current head ID or nozzle ID does not match the head type or nozzle type included in the production job information, the mounting control device 29 replaces the head 23 according to the production job information. and the nozzle 24 should be replaced as appropriate. Next, the mounting control device 29 controls the board conveying device 21 to carry the board S to the mounting work position, takes an image with the mark camera 26, and acquires the board ID (S110).

Subsequently, the mounting control device 29 moves the head 23 to the supply position of the feeder 22 for supplying components, and picks up (adsorbs) the components with the nozzle 24 (S120). Then, the mounting control device 29 moves the head 23 (nozzle 24) above the parts camera 27 and images the parts sucked by the nozzles 24 from below with the parts camera 27 (S130). The mounting control device 29 also performs image processing on the captured image (S140), and determines whether or not the component can be mounted (S150). In S140 and S150, the mounting control device 29 processes the picked-up image to detect the displacement of the picking position of the component with respect to the nozzle 24, the inclination of the picking posture, etc. Whether or not it can be implemented is determined based on whether or not there is. Further, when the mounting control device 29 determines that the mounting is possible, the mounting control device 29 performs a process of setting, for each component, a positional correction amount and a rotation correction amount for eliminating positional deviation and inclination of the component.

When the mounting control device 29 determines in S150 that the component can be mounted, it mounts the component on the board S based on the correction amount set in the image processing (S160), and displays the captured image of the mounted component and the completion of mounting. An image file FL is created in which the message and component mounting work information are stored (S170). Further, when the mounting control device 29 determines in S150 that the component cannot be mounted, it discards the component at a predetermined discard position (S180), and displays the captured image of the discarded component, the fact that it cannot be mounted (discarded), and the component mounting. An image file FL storing work information is created (S190). The mounting work information of S170 and S190 includes information based on the production job information of S100, information of the feeder ID, head ID, and nozzle ID, information of the substrate ID of S110, and the like.

After creating the image file FL in this way, the mounting control device 29 generates a UUID (Universally Unique Identifier) and sets it as the file name of the image file FL (S200), and stores the set file name in the image file FL ( S210). Here, the UUID is a 128-bit value that includes a time stamp generated in units of 100 nanoseconds and the MAC address assigned to the mounting device 20 (mounting control device 29), or generated by random numbers. be done. Therefore, as long as the same mounting control device 29 does not continuously generate UUIDs within 100 nanoseconds, there is almost no possibility of duplication of file names. As described above, the ROM of the mounting control device 29 or the like stores a program for generating a UUID, so that the UUID can be easily generated.

Here, FIG. 5 is an explanatory diagram showing an example of the image file FL. As shown in the figure, the image file FL has a file name with a UUID of, for example, "56995efd-38e0-413a-9975-e72bf8ba0a25". Further, as described above, the image file FL stores the image captured by the parts camera 27, the mounting work information, whether or not the mounting is possible, and the file name. The mounting work information includes the board ID of the board S on which the component is mounted, the mounting position of the component, the type of component, the feeder ID of the feeder 22 that supplied the component, the head ID of the head 23 that was used for mounting, the nozzle 24 that picked up the component. nozzle ID, etc.

Then, the mounting control device 29 transmits the image file FL to the file server 50 (S220). Upon receiving the image file FL, the storage control device 52 of the file server 50 stores the image file FL in the storage unit 54 . Next, the mounting control device 29 determines whether or not all the components to be mounted on the board S are mounted (S230), and if it is determined that they are not mounted, the process returns to S120 and repeats the process. On the other hand, when the mounting control device 29 determines that all the components have been mounted, the mounting control device 29 controls the board transfer device 21 to unload the board S (S240), and ends the mounting processing routine.

FIG. 6 is an explanatory diagram of the image file FL stored in the storage unit 54 of the file server 50. As shown in FIG. Image files FL are transmitted to the file server 50 from each of the mounting control devices 29 of the plurality of mounting devices 20, so that a large number of image files FL are stored in the storage unit 54 as shown. In this embodiment, since UUID is used for the file name of the image file FL, it is possible to prevent duplication of the file names of the stored image file FL and the newly stored image file FL. Therefore, the image file FL can be properly managed by preventing the image file FL from being overwritten by mistake. In addition, the operator can display an image of the component captured during the mounting work on the display 48 using information such as the component type and mounting position. Furthermore, since mounting work information is also stored in each image file FL, it is possible to display on the display 48 images of components during mounting work and mounting work information. Therefore, when a component mounting defect is detected in a post-mounting process using the mounting inspection device 30 or the like, the operator can not only check the component pickup state from the image during the mounting work, but also check the component pickup state. It is also possible to easily identify the feeder ID, head ID, and nozzle ID used for mounting and investigate the cause of the mounting failure. Also, the management device 40 is caused to create statistical information of the information of the inspection results of the plurality of components in the mounting inspection device 30 and the information such as the feeder ID, the head ID, and the nozzle ID included in the mounting work information of the image file FL. Thus, it is possible to investigate whether or not there is a correlation between the defective mounting of each component and the feeder 22, head 23, and nozzle 24. FIG.

Here, correspondence relationships between the components of the present embodiment and the components of the present disclosure will be clarified. The mounting device 20 of the present embodiment corresponds to the work device, and the mounting control device 29 that executes the processing of S170, S190, and S210 of the mounting processing routine corresponds to the file creation section, and executes the processing of S200 of the mounting processing routine. The mounting control device 29 corresponds to the file name setting unit, and the mounting control device 29 corresponds to the file management device. Further, the board working system 10 corresponds to the board working system, and the file server 50 corresponds to the file server.

In the mounting control device 29 of the present embodiment described above, a file name including identification information that uniquely identifies the image file FL is set as the file name of the image file FL storing the image picked up by the mounting device 20. . Therefore, duplication of file names of image files FL storing different images can be prevented, and overwriting of the image files FL can be prevented, so that the image files FL can be properly managed. In addition, since there is no risk of duplication, it is possible to increase the number of types and number of images stored in the file server 50, and to extend the storage period of images. can be done.

In addition, the mounting control device 29 generates a UUID along with the creation of the image file FL and sets the UUID to the file name, so it is possible to reliably prevent duplication of file names over a long period of time.

Further, since the mounting control device 29 stores the mounting work information in the image file FL, it is possible to easily link the mounting work information and the image and investigate the cause of the mounting failure.

In addition, since the mounting control device 29 stores the set file name in the image file FL, even if the file name is changed by mistake by an operator or the like, the uniqueness of the image file FL can be determined from the file name stored in the image file FL. You can keep your sexuality.

It goes without saying that the present disclosure is not limited to the above-described embodiments, and can be implemented in various forms as long as they fall within the technical scope of the present disclosure.

For example, in the above-described embodiment, the UUID generated along with the creation of the image file is set as the file name. and so on.

In the embodiment described above, the mounting control device 29 generates a UUID and sets the UUID to the file name of the image file FL in which the image is stored. However, the present invention is not limited to this. For example, the mounting control device 29 transmits an image captured by the parts camera 27 to the storage control device 52 of the file server 50, and the storage control device 52 that receives the image generates a UUID and stores the image file. A UUID may be set in the file name. Alternatively, the management control device 42 of the management device 40 may generate a UUID and set the UUID to the file name of the image file.

In the above-described embodiment, the image captured by the parts camera 27 provided in the mounting apparatus 20 is stored in the image file FL. Alternatively, the image may be stored in an image file FL. Also, an image captured by a camera provided in another working device that performs work on a board, such as the printing device 12, the print inspection device 14, or the mounting inspection device 30, may be stored in the image file. In doing so, the UUID may be set in the file name. Further, it is also possible to store work information related to predetermined work (printing work, print inspection work, mounting inspection work, etc.) performed on a board by another work device in an image file.

In the above-described embodiment, production job information and information indicating whether or not mounting is possible are stored in the image file FL as mounting work information. However, information other than these is stored in the image file FL. It can also be a thing. Alternatively, the mounting work information may not be stored in the image file FL.

In the above-described embodiment, the set file name is stored in the image file FL, but the present invention is not limited to this, and the file name may not be stored in the image file FL.

In the above-described embodiment, the UUID itself is set as the file name, but the present invention is not limited to this, and the UUID plus other information may be set as the file name. Also, the file name is not limited to the UUID, and a file name including the identification information of the mounting device 20 and date/time information related to the image capturing date/time or the creation date/time of the image file FL may be set. FIG. 7 is an explanatory diagram of a modified image file FL. As shown in the drawing, the image file FL of the modified example has, as a file name, a device ID (D****) set for each mounting device 20, and information on the date and time when the image was taken or when the file was created. (20180130) and hour, minute, and second information (101342***) are set. Note that the device ID may be any ID that can be identified from other work devices in the board working system 10, and may be a MAC address. In addition, although the hour, minute, and second information is exemplified as information up to milliseconds, it may be information up to 100 nanoseconds, like the UUID. Alternatively, the information is not limited to the information including the identification information of the mounting apparatus 20 and the date and time information, and any file name including the identification information that uniquely identifies the image file FL may be set.

In the file management device of the present disclosure, the file name setting unit may set a file name including identification information of the working device and date/time information regarding the date/time of capturing the image or creating the date/time of the file. In this way, a file name including identification information that uniquely identifies a file can be set by simple processing. In addition, it is possible to prevent duplication of file names even for files of images captured at the same time by a plurality of work devices.

In the file management device of the present disclosure, the file name setting unit generates a UUID (Universally Unique Identifier) as the image is captured or the file is created, and sets a file name including the generated UUID. good too. By doing so, it is possible to prevent duplicate file names over a long period of time.

In the file management device of the present disclosure, the file creation unit may store work information related to the predetermined work performed by the work device in the file. In this way, the work information and the image can be linked, so that it is possible to easily investigate the relationship between the content of the work and the work state grasped from the image.

In the file management device of the present disclosure, the file creating section may store the file name set by the file name setting section in the file. In this way, even if the file name is changed by mistake, the uniqueness of the file can be maintained from the file name stored in the file.

A board working system according to the present disclosure is a board working system configured by a plurality of the working devices, and includes any one of the file management devices described above and the file storing the images captured by the different working devices. and a shared file server capable of storing a.

Since the substrate working system of the present disclosure includes any of the file management devices described above, even if files storing images captured by different working devices are stored in a shared file server, file names do not overlap. to prevent files from being overwritten by mistake. Therefore, duplication of file names can be prevented and image files can be appropriately managed.

INDUSTRIAL APPLICABILITY The present disclosure can be used, for example, for management of files captured by substrate working devices.

10 board working system 12 printing device 14 printing inspection device 18 LAN 20 mounting device 21 board transfer device 22 feeder 23 head 24 nozzle 25 head moving device 26 mark camera 27 parts camera 28 nozzle station, 29 mounting control device, 30 mounting inspection device, 40 management device, 42 management control device, 44 storage section, 46 input device, 48 display, 50 file server, 52 storage control device, 54 storage section, FL image file, S substrate.

Claims (6)

a mounting device for mounting the component sucked by the nozzle onto the substrate;
a file creation unit for creating a file storing an image of a component picked up by the nozzle in the mounting apparatus and information indicating whether or not the component can be mounted as determined by image processing of the image; a file name setting unit that sets a file name including identification information that uniquely identifies the file as the file name;
a file server capable of storing the files storing the images captured by the mounting apparatus;
a display for displaying the image and whether or not the component can be mounted ;
A board working system comprising: The board working system according to claim 1,
The file name setting unit sets a file name including identification information of the mounting apparatus and date/time information relating to date/time of capturing the image or creating date/time of the file. The board working system according to claim 1 or 2,
The file name setting unit generates a UUID (Universally Unique Identifier) as the image is captured or the file is created, and sets a file name including the generated UUID. The board working system according to any one of claims 1 to 3,
The board work system, wherein the file creation unit stores work information related to the mounting work performed by the mounting apparatus in the file. The board working system according to any one of claims 1 to 4,
The board working system, wherein the file creation unit stores the file name set by the file name setting unit in the file. The board working system according to any one of claims 1 to 5,
comprising a plurality of the mounting devices,
The board working system, wherein the file server is a shared file server capable of storing the files storing the images captured by the different mounting apparatuses.

Images