WO2012111202A1

WO2012111202A1 - Component-mounting machine

Info

Publication number: WO2012111202A1
Application number: PCT/JP2011/076092
Authority: WO
Inventors: 聖一寺岡
Original assignee: 富士機械製造株式会社
Priority date: 2011-02-14
Filing date: 2011-11-11
Publication date: 2012-08-23
Also published as: CN103314657B; CN103314657A; DE112011104888T5; JP5737989B2; JP2012169394A

Abstract

This component-mounting machine is equipped with: a substrate transport device; a component supply device; a component transfer device; and an imaging/monitoring device, which has an imaging unit that obtains image data by capturing an image when a suction nozzle has picked up a component, a storage unit that saves the image data, and a determination unit that determines the state of the suction nozzle with respect to the picking up of a component and determines component defects on the basis of the image data. When an event that causes a change in the operating state of the component supply device or the component transfer device occurs (Yes in S41), the imaging/monitoring device saves the image data for a prescribed period of time before and after the causal event, or a prescribed quantity of image data, as the image data to be saved in the storage unit (S44), and deletes image data other than the image data to be saved after this other data has been used by the determination unit to make a determination (No in S41). Thus, only the image data before and after the occurrence of an event that causes a change in the operating state of the component supply device or the component transfer device is selected and saved for a long period of time, which enables efficient clarification of the event and efficient diagnosis of the cause when a defective substrate occurs or an equipment error occurs.

Description

Component mounter

The present invention relates to a component mounter for mounting an electronic component or the like on a substrate, and more particularly, to a component mounter provided with an imaging monitoring device that images a component suction state of a suction nozzle to determine pass / fail.

As a facility for producing a board on which a large number of components are mounted, it is common to construct a board production line by connecting a screen printing machine, a component mounting machine, a reflow machine, etc. with a transport device. Among these components, the component mounter is configured to include a substrate transfer device, a component supply device, a component transfer device, and an imaging monitoring device. The component transfer device is also called a component mounting robot, and has a component mounting head and a head driving mechanism. The component mounting head has a suction nozzle having a suction mechanism capable of controlling air pressure, sucks and collects a component from the component supply device using negative pressure, and mounts the component at a predetermined position on the board. . The component mounting head is driven by, for example, a head drive mechanism that enables movement in two orthogonal directions.

An imaging monitoring device is used for the purpose of confirming that the suction nozzle is picking up components in the correct state. The imaging monitoring device includes an imaging unit (imaging camera) that captures an image of a component suction state of the suction nozzle to obtain image data, a storage unit that stores image data, and a component suction state and components of the suction nozzle based on the image data It is common to have a determination unit that determines whether or not the quality is good. In addition to the above-mentioned applications, the image data obtained by the imaging monitoring device can be used as an important clue when elucidating an event or investigating the cause when a defective board occurs or a device abnormality occurs in a component mounter. Often done.

An example of a component mounter equipped with this type of imaging monitoring apparatus is disclosed in Patent Document 1. The component mounting apparatus disclosed in Patent Document 1 captures a chip component sucked by a suction nozzle with an imaging camera and recognizes the position of the component from an image, and stores the image when the position of the component cannot be recognized. Storage means for displaying, and display means for displaying the stored image. Thereby, it is supposed that a picked-up image by the picking-up camera in which parts cannot be mounted can be seen, and the suction state at that time can be known.

Also, the applicant of the present application discloses an image processing verification system that can be incorporated into a component mounter in Patent Document 2. The image processing verification system includes means for storing data that can reproduce image processing in a database, and means for acquiring the data and reproducing and verifying image processing. This eliminates the need to actually repeat the production process using a trial-and-error method when a defective substrate occurs or when a device abnormality occurs, so that accurate verification can be easily performed. According to the fourth aspect of the present invention, the image data meeting the specified conditions and the parameters necessary for the image processing are stored, and there is an advantage that the data can be automatically stored in the database during actual production. . The conditions to be specified are set in advance by combining the operation conditions on the mounting machine side, for example, the device number of the medium (feeder or tray) that supplies the components, the type of suction nozzle, the image processing algorithm, etc. To do.

Japanese Patent No. 2698258 JP 2008-197772 A

By the way, the device of Patent Document 1 is a method of storing an image when the position of a component cannot be recognized, in other words, a method of storing data when a failure occurs. However, in the verification work of defects and abnormalities, the verification accuracy is remarkably improved by grasping the progress from the normal operation state before the occurrence of the defects and abnormalities. Even if all the image data is to be stored for this purpose, the image data has a large data size, so that the storage location and storage area are insufficient. As a result, old image data is deleted, and there is a problem that efficient verification work cannot be performed.

Further, in Patent Document 2, the image data to be stored can be saved by specifying the conditions to save the storage area, but the old image data is deleted as time passes. In addition, no image data remains if a defect or abnormality occurs under conditions other than the specified conditions.

In an actual production line, switching of the type of board to be produced, parts breaks, equipment maintenance, etc. are the causative events, and board defects and equipment abnormalities tend to occur immediately after that. Therefore, the image data immediately before and immediately after the causal event is more important than the image data when a good operating state continues. Further, when an abnormality determination (image processing abnormality) of the component suction state of the suction nozzle by the imaging monitoring device or an abnormality determination by other state monitoring sensors is performed, the image data before and after that is particularly important. In this way, assuming a causal event that may cause a defect or abnormality and selectively saving important image data before and after the occurrence has not been performed by conventional component mounters.

The present invention has been made in view of the above problems of the background art, and selects only image data before and after the occurrence of a causal event that can change the operating status of the component supply device or the component transfer device, and stores it for a long period of time. Therefore, it is an object to be solved to provide a component mounting machine that can efficiently clarify an event and investigate the cause when a defective board occurs or when an apparatus abnormality occurs.

The invention of a component mounting machine according to claim 1 for solving the above-described problems includes a substrate carrying device that carries a substrate into a component mounting position, positions and carries it out, a component supply device that supplies a plurality of types of components, and the component supply device. A component transfer device having a suction nozzle that is mounted on the substrate that is positioned by sucking and positioning the component supplied from the image pickup unit, and an imaging unit that captures an image of a state in which the suction nozzle sucks the component and obtains image data; And a storage unit that stores the image data, and an imaging monitoring device that includes a determination unit that determines a component suction state of the suction nozzle and the quality of the component based on the image data. The imaging monitoring device is configured to perform a predetermined time before or after the causal event when a causal event that may change an operating state of the component feeding device or the component transfer device occurs. Stored in the storage unit the image data as a storage object image data of a constant, characterized by erasing the image data other than the store target image data after used for the determination by the determining unit.

According to a second aspect of the present invention, the imaging monitoring apparatus according to the first aspect of the present invention relates to a causal event whose occurrence timing can be predicted, after the occurrence of the causal event from the predetermined time or the predetermined number before the predicted occurrence timing. The image data until the predetermined time or the predetermined number elapses is stored as the storage target image data.

According to a third aspect of the present invention, in the second aspect of the present invention, the cause event that can predict the occurrence timing includes a break of the part in the part supply device and a replacement of a medium for supplying the part, and a periodicity in the part transfer device It includes at least one event of maintenance, automatic cleaning of the suction nozzle, and switching of the type of the substrate.

According to a fourth aspect of the present invention, the imaging monitoring apparatus according to any one of the first to third aspects, wherein the imaging monitoring device receives image data corresponding to the predetermined time or more or the predetermined number or more with respect to a cause event whose generation timing cannot be predicted. Temporarily stored and updated sequentially, and the latest image data corresponding to the predetermined time or the predetermined number is stored in the storage unit as the storage target image data in the temporary storage when the cause event occurs In addition, image data until the predetermined time or the predetermined number elapses after the occurrence of the cause event is stored as the storage target image data.

According to a fifth aspect of the present invention, in the fourth aspect, the cause event in which the occurrence timing cannot be predicted is the replacement and readjustment of the device constituent members for recovering the failure of the component supply device or the component transfer device, and the An abnormality determination of the operation state of the suction nozzle by the imaging monitoring device, an abnormality determination by a state monitoring sensor provided in the component supply device, the component transfer device, or the imaging monitoring device, and at least one event of the substrate type switching It is characterized by including.

According to a sixth aspect of the present invention, the imaging monitoring apparatus according to any one of the first to fifth aspects, wherein the storage unit is prioritized according to a predetermined priority order when the storage unit is full of the storage target image data. It is characterized in that the image data to be saved is deleted in order from the lowest priority.

According to a seventh aspect of the present invention, in any one of the first to sixth aspects, the imaging monitoring device captures a predetermined characteristic state different from a state in which the suction nozzle sucks the part, and features image data And the feature image data before and after the occurrence of the causal event is stored as storage target image data.

In the invention of the component mounter according to the first aspect, the imaging monitoring device of the component mounter is configured to perform a predetermined process before and after the cause event when a cause event that may change the operation status of the component supply device or the component transfer device occurs. Time or a predetermined number of pieces of image data are stored as storage target image data in the storage unit, and image data other than the storage target image data is used for determination by the determination unit and then deleted. Therefore, only important image data before and after the causal event can be selected and stored for a long time within the limited storage capacity of the storage unit. In addition, by referring to the stored image data, it is possible to grasp the progress of the component suction state of the suction nozzle from before the occurrence of the cause event to after it has occurred. Research can be done efficiently.

In the invention according to claim 2, with respect to the cause event for which the occurrence timing can be predicted, a predetermined time or a predetermined number of image data before and after the predicted occurrence timing is stored as the image data to be stored. Further, in the invention according to claim 3, the cause event that can predict the occurrence timing includes parts breakage in the parts supply device and replacement of the medium for supplying the parts, and periodic maintenance in the parts transfer device and automatic cleaning of the suction nozzle, In addition, at least one event of substrate type switching is included. With respect to the causal events for which the occurrence timing can be predicted, by storing only the image data before and after the occurrence timing, the storage period can be significantly prolonged as compared with the case of storing all the image data.

In the invention according to claim 4, with respect to a cause event whose occurrence timing cannot be predicted, image data corresponding to a predetermined time or more or a predetermined number or more is temporarily stored and sequentially updated, and temporarily stored when the cause event occurs. The latest image data corresponding to a predetermined time or a predetermined number is stored, and a predetermined time or a predetermined number of image data after the occurrence of the causal event is stored. Further, in the invention according to claim 5, the cause event for which the generation timing cannot be predicted is the replacement and readjustment of the device constituent members for recovering the failure of the component supply device or the component transfer device, and the suction nozzle by the imaging monitoring device And at least one event of abnormality determination by a state monitoring sensor provided in a component supply device, a component transfer device, or an imaging monitoring device, and a substrate type switching. Regarding the causal events whose generation timing cannot be predicted, a predetermined time or a predetermined number of image data immediately before the causal event is temporarily stored in the storage unit. Therefore, even if the cause event cannot be predicted, the image data before the cause event can be selected and stored. Also, by storing only the image data before and after the generation timing, the storage period can be extended significantly compared to when all the image data is stored.

In the invention according to claim 6, when the storage unit is full of the storage target image data, the storage target image data is deleted in order from a lower priority according to a predetermined priority order. When the storage unit is full of storage target image data, the latest storage target image data can be stored by deleting the storage target image data having a low priority. As prioritization, there are a method of setting the priority of the old image data to be saved low in time series, a method of setting the priority for each type of cause event, and the like.

In the invention according to claim 7, the feature image data is obtained by imaging a predetermined feature state different from the state in which the suction nozzle sucks the component, and the feature image data before and after the cause event is generated is saved as the save target image data. To do. As a result, the types of image data before and after the occurrence of the causal event increase and become multifaceted. Therefore, when a defective substrate occurs or when an apparatus abnormality occurs, event elucidation and cause investigation can be performed more efficiently.

It is a perspective view which shows the apparatus structure of the component mounting machine of 1st Embodiment. It is a figure explaining the component mounting flow in the component mounting machine of 1st Embodiment. It is a figure explaining the preservation | save condition management flow which determines whether image data is preserve | saved by the image preservation | save process of step S7 in the component mounting flow of FIG. It is a figure of the list explaining the cause event, the preservation trigger generation condition, and the deletion trigger generation condition by way of example. It is a figure explaining the detailed flow of the image preservation | save process of step S7 in the component mounting flow of FIG. It is a figure explaining the storage condition management flow which determines whether image data is preserve | saved or deleted in 2nd Embodiment. It is a figure explaining the detailed flow of the image preservation | save process of step S7 in 2nd Embodiment in the component mounting flow of FIG.

The component mounter according to the first embodiment of the present invention will be described with reference to FIGS. FIG. 1 is a perspective view showing a device configuration of a component mounter 1 according to the first embodiment. The component mounter 1 assembles the board transfer device 3, the component supply device 4, the component transfer device 5, and the imaging monitoring device 6 on the base 2, and controls each device 3 to 6 from a control computer (not shown). Configure. Further, as indicated by the XYZ coordinate axes in FIG. 1, the horizontal width direction of the component mounter 1 (the direction from the upper left to the lower right in FIG. 1) is the X axis direction, and the horizontal longitudinal direction of the component mounter 1 (see FIG. 1). 1 is a Y-axis direction, and a vertical height direction is a Z-axis direction.

The board transfer device 3 is provided in the middle of the component mounting machine 1 in the longitudinal direction. The substrate transfer device 3 is a so-called double conveyor type device in which the first transfer device 31 and the second transfer device 32 are arranged in parallel, and the two substrates 9 are operated in parallel to carry in and position in the X-axis direction. Take it out. The first transport device 31 is guided by a pair of

guide rails

31A and 31B and

guide rails

31A and 31B arranged in parallel on the base 2 in the X-axis direction, and a pair of substrates 9 is placed and transported. Conveyor belt (not shown) or the like. In addition, the first transport device 31 is provided with a clamp device (not shown) that pushes up and positions the substrate 9 transported to the component mounting position from the base 2 side. The second transport device 32 is configured in the same manner as the first transport device 31.

The component supply device 4 is a feeder-type device, and is provided at the front portion in the longitudinal direction of the component mounter 1 (left front side in FIG. 1). The component supply device 4 is configured by arranging a plurality of cassette type feeders 41 in parallel on the base 2. Each cassette-type feeder 41 includes a main body 42 that is detachably attached to the base 2, a supply reel 43 that is rotatably and detachably attached to a rear portion of the main body 42, and a component supply that is provided at the tip of the main body 42. Part 44. The supply reel 43 is a medium for supplying parts, and is wound with a carrier tape (not shown) holding a predetermined number of parts at regular intervals. The leading end of the carrier tape is pulled out to the component supply unit 44, and different components are supplied for each carrier tape.

The component transfer device 5 is a so-called XY robot type device that can move in the X-axis direction and the Y-axis direction, and supplies components from the rear part (right rear side in FIG. 1) in the longitudinal direction of the component mounting machine 1 to the front part. It is arranged above the device 4. The component transfer device 5 includes a pair of Y-

axis rails

51A and 51B, a Y-axis slider 52, a Y-axis motor 53, an X-axis motor, a Z-axis motor, a component mounting head 54, and the like. The pair of Y-axis rails 51 </ b> A and 51 </ b> B are juxtaposed in parallel to the Y-axis direction and extend above the board transfer device 3 and the component supply device 4. A Y-axis slider 52 is movably suspended on the Y-

axis rails

51A and 51B. The Y-axis slider 52 is driven by a Y-axis motor 53 and moves on the Y-

axis rails

51A and 51B in the Y-axis direction. A component mounting head 54 is disposed on the Y-axis slider 52 so as to be movable in the X-axis direction. The component mounting head 54 is driven by an unillustrated X-axis motor and moves in the X-axis direction.

A suction nozzle having a symbol is arranged downward from the component mounting head 54. The suction nozzle is driven by a Z-axis motor (not shown) to move up and down (move in the Z-axis direction). Further, the suction nozzle has a suction mechanism capable of controlling the air pressure, and picks up and picks up components from the component supply device 4 using negative pressure. Then, after picking up an image of the component suction state by the imaging monitoring device 6 to acquire and correct the positional deviation between the suction nozzle and the center of the component, the suction nozzle mounts the component on the substrate 9. Usually, the component transfer device 5 repeatedly executes a component mounting loop described later to mount a large number of components on the substrate 9.

The imaging monitoring device 6 is a device that determines the component suction state of the suction nozzle of the component transfer device 5 and the quality of the component, and is disposed in the vicinity of the component supply unit 44 of the component supply device 4. The imaging monitoring device 6 includes an imaging unit that captures an image of a state in which the suction nozzle has attracted a component to obtain image data, a storage unit that stores image data, and a determination unit that determines pass / fail based on the image data. ing. For example, the determination unit determines that there is an abnormality when the component is displaced and sucked and it is difficult to correct the position, or when the component shape obtained from the image is different from the reference shape (image processing abnormality).

A disposal box 7 is disposed in the vicinity of the imaging monitoring device 6 on the base 2. The disposal box 7 is a place where the components that are picked up by the component transfer device 5 are discarded when the imaging monitoring device 6 determines that the image processing is abnormal.

The substrate transfer device 3, the component supply device 4, the component transfer device 5, and the imaging monitoring device 6 operate according to instructions from the control computer while appropriately exchanging information with a control computer (not shown).

Next, the operation of the component mounter 1 according to the first embodiment configured as described above will be described. FIG. 2 is a diagram illustrating a component mounting flow in the component mounter 1 according to the first embodiment. As shown in step S <b> 1 of the component mounting flow, first, the board 9 is carried in and positioned by the board transfer device 3. Next, in step S2, initial processing such as confirmation of the position of the substrate 9 and confirmation of reading of the substrate ID is performed. Next, in step S3, a component mounting loop is started.

In step S4 in the component mounting loop, the component mounting head 54 of the component transfer device 5 moves to the component supply unit 44 of the component supply device 4, and the suction nozzle sucks the component. Next, in step S5, the component mounting head 54 moves to the vicinity of the imaging monitoring device 6, and the imaging monitoring device 6 captures the state in which the suction nozzle sucks the component and obtains image data. In step S6, the imaging monitoring apparatus 6 performs predetermined image processing on the image data. For example, the position is corrected by obtaining the amount of deviation between the suction nozzle and the center of the component, the presence or absence of rotation or inclination of the component with respect to the suction nozzle, or the outer shape of the sucked component is confirmed. Thereby, when the component suction state of the suction nozzle is abnormal or when the component shape itself is abnormal, it is determined that the image processing is abnormal. Next, in the image saving process in step S7, the imaging monitoring apparatus 6 saves or deletes the image data according to a detailed flow described later.

In the next step S8, the result of the image processing in step S6 is confirmed. If the image processing is abnormal, the process proceeds to step S9, and if normal, the process proceeds to step S10. In step S <b> 9 when the image processing is abnormal, the component mounting head 54 moves above the disposal box 7, and the component adsorbed by the suction nozzle is discarded in the disposal box 7. Thereafter, the process returns to step S4, and the same part is retried. In the normal step S10, the component mounting head 54 moves above the substrate 9 and the component sucked by the suction nozzle is mounted on the substrate 9. Next, in step S11, it is confirmed whether or not all the necessary components are mounted on the substrate 9. If there are any unmounted components, the process returns to step S4 to move to the next component. If all components have been mounted in step S11, the component mounting loop is terminated in step S12, and the process proceeds to step S13. In step S13, the board 9 is unloaded and the component mounting flow for one board 9 is completed. The component mounting flow in FIG. 2 is repeated by the number of boards 9 to be produced.

FIG. 3 is a diagram for explaining a storage condition management flow for determining whether image data is stored or deleted in the image storage processing in step S7 in the component mounting flow of FIG. The storage condition management flow is performed in parallel with the component mounting flow of FIG. Step S31 of the storage condition management flow in FIG. 3 is a state of waiting for a trigger for changing the necessity of image data storage. When a storage trigger is generated in step S32, the storage flag is set to ON in step S33. If an erase trigger occurs in step S34, the save flag is set to OFF in step S35. The save flag is a parameter indicating whether the image data acquired at that time is the image data to be saved. After step S33 and step S35, the process returns to step S31 and waits for the next trigger.

The above save trigger and erase trigger are generated due to a cause event accompanying the progress of the component mounting flow of FIG. The cause event means an event that causes a change in the operating status of the component supply device 4 or the component transfer device 5, as illustrated in FIG. FIG. 4 is a table illustrating examples of cause events, storage trigger generation conditions, and deletion trigger generation conditions.

In FIG. 4, firstly, as a cause event, a break of a part can be exemplified. When the production of the substrate 9 progresses and there is no specific part of a certain supply reel 43 of the component supply device 4, the old supply reel 43 is taken out from the cassette type feeder 41 and a new supply reel 43 is set. Here, if the new supply reel 43 and the carrier tape are wrinkled or the setting method is bad, there is no possibility of causing a defective substrate or an apparatus abnormality. Therefore, before and after the reel replacement, the image data in which the suction nozzle sucks the specific component is stored as the storage target image data. For example, the time when the remaining number of parts on the old reel becomes A1 is set as a save trigger generation condition, and the time when the number of used parts on the new reel becomes A2 is set as an erase trigger generation condition. To do. To check the remaining number of parts on the old reel, you can detect the splice position of the old and new supply reel 43 with the carrier tape and convert it to the remaining number of parts, or count down each time you collect parts from the supply reel 43. A method of sequentially managing the remaining number of parts can be used.

Further, in the component mounter provided with the tray type component supply device instead of the component mounter 1 of the first embodiment, the timing at which the tray, which is a medium for supplying components, is changed can be a cause event. The time when the remaining number of parts in the old tray becomes B1 is set as a save trigger generation condition, and the time when the number of used parts in the new tray becomes B2 is set as an erase trigger generation condition. Furthermore, as a similar concept, the timing when the part lot is changed is a cause event, the time when the remaining number of parts in the old lot becomes C1 is set as a storage trigger generation condition, and the number of parts used in the new lot becomes C2. It is possible to set the erase trigger as a condition for generating an erase trigger. Lot changes often overlap with reel and tray replacement.

Next, periodic maintenance in the component transfer device 5 can be exemplified as a cause event. The control computer sets the period of this regular maintenance based on the operation time from the end of the previous regular maintenance, and issues maintenance guidance to the operator. Accordingly, the D1 minute before the maintenance guide can be set as a storage trigger generation condition, and the erasure trigger generation condition can be set at the time when D2 minutes have elapsed after the maintenance is completed or when E substrates 9 are produced after the maintenance is completed. Furthermore, automatic cleaning of the suction nozzle of the component transfer device 5 can also be considered as a cause event. For automatic cleaning of the suction nozzle, the F1 minute before the scheduled cleaning time is set as the save trigger generation condition, and the F2 minute elapses after the cleaning ends or the time when G parts are mounted after the cleaning ends is set as the erasure trigger generation condition. it can.

The cause event described so far is a cause event whose occurrence timing can be predicted. Therefore, a storage trigger can be generated before the cause event occurs, and an erase trigger can be generated after the cause event to store the image data before and after the cause event. Note that the number of stored image data (for example, A1 and A2) may be the same or different before and after the cause event occurs.

Next, examples of the cause event include switching the type of board to be produced. Board type switching is a causal event that can be predicted when the target board number is set and the number of mounted boards is counted up. As described above, a save trigger is generated before the causal event occurs. be able to. However, there is also a production form in which it is difficult to predict the generation timing. In this case, image data storage is started with the storage trigger generation condition immediately after switching the substrate type. Then, an erasure trigger generation condition can be set when H minutes have elapsed after switching or when stable operation has been confirmed.

Furthermore, the failure of the component supply device 4 and the component transfer device 5 is also a cause event whose generation timing cannot be predicted. In this case, the failure is usually recovered by replacing or re-adjusting the device constituent members (component units). Therefore, the storage trigger generation condition can be set immediately after failure recovery, and the erase trigger generation condition can be set when L minutes have elapsed after the failure recovery or when stable operation has been confirmed.

Further, if it is determined that the image processing result is abnormal in step S8 of the component mounting flow of FIG. 2 (abnormal image processing), it naturally becomes a cause event. In addition, another state monitoring sensor provided in the component mounter 1 may determine an abnormality (state monitoring abnormality). For example, an abnormality in which a component cannot be mounted on the substrate 9 without being separated from the suction nozzle is detected by a sensor other than the imaging monitoring device 6. For image processing abnormalities and state monitoring abnormalities, the storage trigger generation condition can be immediately after the abnormality determination, and the erase trigger generation condition can be when J minutes or K minutes have elapsed after the abnormality determination or when stable operation has been confirmed.

4. A save trigger and an erase trigger are generated according to the cause event illustrated in FIG. 4, respectively, and the save flag is switched on and off as shown in FIG. The storage flag is used for each cause event. For example, the number of storage flags equal to the number of supply reels 43 is used at the break of parts of the supply reel 43. Therefore, image data obtained by picking up the suction state of the part is a storage target at the break of the part, and image data of other parts that are not a cut is not a storage target. In the causal event other than the break of the parts, the image data of the parts of all types are stored. Each storage flag is referred to in the image storage processing in step S7 of the component mounting flow in FIG. FIG. 5 is a diagram for explaining a detailed flow of the image storage process in step S7 in the component mounting flow of FIG.

In step S41 in FIG. 5, the state of the save flag is first confirmed. When the save flag is off, the image saving process ends immediately. That is, the image data acquired in step S5 of FIG. 2 and used by the determination unit in the determination of image processing abnormality in step S6 is determined not to be stored, and is erased without being stored in the storage unit. When the save flag is on, the process proceeds to step S42 to check whether there is a save area in the storage unit. When there is no storage area, the process proceeds to step S43, and the image data with the lower priority among the stored areas is deleted to secure the storage area. In the first embodiment, it is set that the priority is lower as it is older in time series, and the image data is deleted in the oldest order. When there is a storage area in step S42 and after securing the storage area in step S43, the latest image data to be stored is stored in the storage unit in step S44.

As described above, the imaging monitoring apparatus 6 saves the image data when the save flag is on in the storage unit as the save target image data, and determines the image data when the save flag is off as the determination unit. Erase after using for judgment by. That is, only the image data before and after the occurrence of the predictable cause event in FIG. 4 and the image data after the occurrence of the unpredictable cause event are stored for a predetermined time or a predetermined number of ranges. Note that an alarm may be issued when the number of stored image data reaches a predetermined value, and the image data may be moved to a memory outside the apparatus to free up a storage area.

Therefore, according to the component mounter 1 of the first embodiment, only important image data before and after the causal event can be selected and stored within the limited storage capacity of the storage unit of the imaging monitoring apparatus 6, and all The storage period can be greatly extended compared to the case of storing the image data. In addition, by referring to the stored image data, it is possible to grasp the progress of the suction state of the suction nozzle components from before occurrence to after the occurrence of the predictable cause event, and the status of the suction status of the suction nozzle immediately after the occurrence of the unpredictable cause event. You can keep track of the progress. As a result, when a defective substrate occurs or when a device abnormality occurs, the event can be clarified and the cause can be efficiently investigated. For example, when it is assumed that the component suction state of the suction nozzle is the cause when a defect or abnormality occurs, the image data before and after the cause event that is evidence can be compared and confirmed. Further, when the component suction state of the suction nozzle does not change before and after the cause event, the emphasis on the event elucidation and cause investigation can be put elsewhere.

Next, the component mounter of the second embodiment will be described. The component mounter of the second embodiment has the same device configuration as that of the first embodiment, and is different in that image data corresponding to a predetermined time or a predetermined number before occurrence is stored even for a cause event whose generation timing cannot be predicted. The component mounting flow of the component mounting machine of the second embodiment is substantially the same as the flow of the first embodiment shown in FIG. 2, but the contents of the image storage processing in step S7 are different, and the storage condition management flow is also different. .

In the image saving process of the second embodiment, a method is adopted in which all image data is temporarily saved in the storage unit of the imaging monitoring apparatus 6 and is deleted in order from the data with the lowest priority when the saving area is exhausted. (Details will be described later with reference to FIG. 7). The cause event to be considered in the component mounter of the second embodiment is the same as the cause event shown in FIG. 4, and the same holds for setting the save flag on and off by the save trigger and the erase trigger. In the component mounter of the second embodiment, a label indicating whether or not storage is necessary is assigned to each image data, and storage condition management and image storage processing shown in FIGS. 6 and 7 are performed.

FIG. 6 is a diagram illustrating a storage condition management flow for determining whether to store or delete image data in the second embodiment. The storage condition management flow in FIG. 6 is performed in parallel with the component mounting flow in FIG. Step S51 in FIG. 6 is in a state of waiting for a trigger for changing the necessity of image data storage. When a save trigger is generated in step S52, a save flag is set on in step S53. When the image data is acquired in step S5 of the component mounting flow in FIG. 2, the imaging monitoring device 6 gives a label “deletable” to the image data if the storage flag is off, and if the storage flag is on. A label “save target” is assigned to the image data.

Next, when an erasure trigger is generated in step S54, lock target image data is set in step S55. In other words, when the causal event that generated the save trigger and the erase trigger is an event that can be predicted, the label of the image data acquired between the save trigger and the erase trigger is “Save Target”, and this is the “Lock”. Change to "Target". On the other hand, when the cause event that generated the save trigger and the erase trigger is an unpredictable event, the save trigger occurs immediately after the cause event, so the label of the image data acquired before the cause event is “deletable”. ing. Therefore, the label of the latest image data corresponding to a predetermined time or a predetermined number before the cause event is changed from “deletable” to “lock target”. Further, the label of the image data acquired between the occurrence of the unpredictable cause event and the erasure trigger is “storage object”, and this is changed to “lock object”. With the above setting, the label of the image data before and after the occurrence of the causal event becomes “lock target” regardless of whether or not the occurrence timing can be predicted. The “lock target” image data is also a kind of storage target image data.

Following step S55, the save flag is set to OFF in step S56. As a result, a label “deletable” is assigned to image data acquired thereafter. After step S53 and step S56, the process returns to step S51 and waits for the next trigger.

FIG. 7 is a diagram illustrating a detailed flow of the image saving process in step S7 in the component mounting flow of FIG. 2 in the second embodiment. In step S61 in FIG. 7, it is first checked whether the storage area of the storage unit of the imaging monitoring apparatus 6 is full. When the storage area is empty, the process immediately proceeds to step S70, and the latest image data is stored regardless of the type of label. When the storage area is full, the process proceeds to step S62, and a deletion data determination loop is started.

In step S63 in the deletion data determination loop, the image data in the storage unit is selected one by one in the oldest order. Then, it is checked whether or not the label of the image data selected in step S64 is “lock target”, and whether or not the label of the image data is “save target” is checked in step S65. When the label is “lock target” or “save target”, the process proceeds to step S66 to check whether or not all image data has been selected. If unselected image data remains, the process returns to step S63 to select the next oldest image data, and steps S63 to S66 are repeated.

In the middle of repetition, when image data that is neither “locking object” nor “storing object”, in other words, “deletable” label is found, the process proceeds to step S67 to delete the image data, Proceed to step S70. The image data to be deleted is the oldest image data with the label “deletable”.

If all the image data is selected and step S63 to S66 are repeated and no image data with the “deletable” label is found, the process proceeds from step S66 to step S68 to end the deletion data determination loop. Next, in step S69, the oldest image data among the labels to be “locked” is deleted. In step S67 or step S69, image data for any one data is deleted, and a storage area is secured. Therefore, the acquired latest image data can be stored in step S70.

In the second embodiment, as long as there is a storage area in the storage unit, all image data is stored regardless of the type of label. Then, when the storage area of the storage unit is filled with image data, the image data with lower priority is deleted in order. Here, the image data with the label “deletable” has a lower priority than the image data with the label “locked” or “saved”, and is preferentially deleted. Also, between image data to which the same kind of label is assigned, the new and old are prioritized and are deleted in order from the old image data.

For example, when the storage area is full and the acquired latest image data is “deletable”, the oldest “deletable” image data is deleted and replaced. This is equivalent to temporarily storing and sequentially updating image data corresponding to a predetermined time or more or a predetermined number or more. Further, for example, when the storage area is filled with image data with the label “lock target” or “storage target”, the oldest “lock target” image data is deleted. This is equivalent to deleting the image data to be saved in order of lower priority in accordance with a predetermined priority order.

The component mounter of the second embodiment temporarily stores and sequentially updates the image data with the label “deletable” for the cause event for which the occurrence timing cannot be predicted. When the unpredictable cause event occurs, the label of the latest image data corresponding to a predetermined time or a predetermined number before the cause event is changed from “deletable” to “lock target”. Thereby, even if it is a cause event which cannot predict generation | occurrence | production timing, the image data before generation | occurrence | production can be preserve | saved as preservation | save object image data. Therefore, it is possible to select and store only important image data before and after the causal event regardless of whether prediction is possible or not, and the storage period can be greatly prolonged compared to the case of storing all image data. In addition, by referring to the stored image data, it is possible to grasp the progress of the component suction state of the suction nozzle from before occurrence to after occurrence even if it is a cause event whose occurrence timing cannot be predicted. Elucidation of the event and investigation of the cause can be performed more efficiently when a device abnormality occurs.

It should be noted that it is also possible to obtain a feature image data by capturing a predetermined feature state different from the state in which the suction nozzle sucks the component, and save the feature image data before and after the cause event occurs as the save target image data. For example, the tip state of the suction nozzle that is not picking up the component can be imaged as the characteristic state. Thereby, when a component mounting defect occurs after the end of the automatic cleaning of the suction nozzle, it can be confirmed in a multifaceted manner whether it is caused by the suction nozzle or others. In this case, the image data to be stored may be one data before and after the automatic cleaning. It is also possible to set another feature state and take an image.

Furthermore, it is also possible to target causal events other than those illustrated in FIG. In the first and second embodiments, the imaging monitoring device 6 has a storage unit that stores image data. However, a storage unit of an control computer or an external storage device may be used in combination. In addition, the present invention can be variously applied and modified.

The present invention can be used for a component mounter for mounting electronic components on a substrate.

1: Component mounter 2: Base 3: Board transfer device 31: First transfer device 32: Second transfer device 4: Component supply device 41: Cassette feeder 42: Main body 43: Supply reel 44: Component supply unit 5:

Component transfer device

51A, 51B: Y-axis rail 52: Y-axis slider 53: Y-axis motor 54: Component mounting head 6: Imaging monitoring device 7: Waste box 9: Substrate

Claims

A substrate transport device that carries a substrate into a component mounting position, positions and unloads the component, a component supply device that supplies a plurality of types of components, and the component that is supplied from the component supply device by suction and is positioned on the substrate Based on a component transfer device having a suction nozzle to be mounted, an imaging unit that captures an image of a state in which the suction nozzle sucks the component and obtains image data, a storage unit that stores the image data, and the image data An imaging monitoring device having a determination unit that determines the component suction state of the suction nozzle and the quality of the component, and a component mounting machine comprising:
The imaging monitoring device includes:
When a cause event that may change the operation status of the component supply device or the component transfer device occurs, a predetermined time before or after the cause event or a predetermined number of the image data is stored in the storage unit as image data to be stored. Save and
A component mounting machine, wherein image data other than the image data to be stored is erased after being used for determination by the determination unit.
2. The imaging monitoring apparatus according to claim 1, wherein the predetermined time or the predetermined number after the occurrence of the causal event from the predetermined time or the predetermined number before the predicted generation timing is related to the cause event for which the generation timing can be predicted. The component mounting machine, wherein the image data until the lapse of time is stored as the storage target image data.
In Claim 2, the cause event which can predict the generation | occurrence | production timing is the replacement | exchange of the said component cut | interruption in the said component supply apparatus and the medium which supplies the said component, the regular maintenance in the said component transfer apparatus, and the automatic cleaning of the said suction nozzle , And at least one event of switching the type of the board.
4. The imaging monitoring apparatus according to claim 1, wherein the imaging monitoring apparatus temporarily stores and sequentially updates image data corresponding to the predetermined time or the predetermined number or more with respect to a cause event whose generation timing cannot be predicted. And storing the latest image data corresponding to the predetermined time or the predetermined number in the storage unit as the storage target image data while temporarily storing the cause event, and generating the cause event A component mounting machine that stores image data until the predetermined time or the predetermined number later as the image data to be stored.
5. The cause event in which the occurrence timing cannot be predicted is the replacement and readjustment of the apparatus constituent members for recovering the failure of the component supply apparatus or the component transfer apparatus, and the suction nozzle by the imaging monitoring apparatus. A component including at least one event of abnormality determination of an operating state, abnormality determination by a state monitoring sensor provided in the component supply device, the component transfer device, or the imaging monitoring device, and switching of the type of the substrate Mounting machine.
6. The imaging monitoring apparatus according to claim 1, wherein when the storage unit is full of the storage target image data, the imaging monitoring apparatus starts from the storage target image data having a low priority according to a predetermined priority order. A component mounter that is deleted in order.
7. The imaging monitoring device according to claim 1, wherein the imaging monitoring device captures a predetermined feature state different from a state in which the suction nozzle sucks the component to obtain feature image data, and the cause event occurs. A component mounting machine, wherein the feature image data before and after the storage is stored as storage target image data.