WO2016063363A1

WO2016063363A1 - Feeder management device and management method

Info

Publication number: WO2016063363A1
Application number: PCT/JP2014/078023
Authority: WO
Inventors: 淳郎高桑; 晋吾藤村; 瑞穂山本
Original assignee: 富士機械製造株式会社
Priority date: 2014-10-22
Filing date: 2014-10-22
Publication date: 2016-04-28
Also published as: JP6449901B2; JPWO2016063363A1

Abstract

The objective of the present invention is to provide feeder management device and management method allowing a feeder firmware update process to be executed efficiently while preventing a decrease in the production efficiency of a part mounting machine. The feeder management device comprises a version acquisition unit for acquiring the current version of the feeder firmware, a requirement determination unit for determining whether or not an update process is required for the firmware, a required time acquisition unit for acquiring the required time that is needed for the update process, and a process management unit for controlling the firmware update process on the basis of the required time and a feeder down time.

Description

Feeder management apparatus and management method

The present invention relates to a management apparatus and a management method for managing firmware incorporated in a feeder used in a component mounter.

The component mounter is a device that mounts electronic components on a board. As shown in Patent Document 1, the component mounter includes a plurality of feeders that are mounted in a replaceable manner. Firmware corresponding to a required function is incorporated in each of the plurality of feeders. The feeder in the component mounter executes firmware according to a signal input from the control device, and controls, for example, a feeding operation of a loaded component tape.

∙ The firmware of such feeders may need to be upgraded as new functions are added. Patent Document 2 discloses a configuration in which firmware update processing is automatically executed when the firmware for update stored in the component mounter is a newer version than the firmware of the feeder.

JP 2012-080003 A JP 2010-182768 A

Here, when updating the firmware of the feeder in the component mounter, the feeder needs to operate while the update process is being executed, so the electronic component mounting process cannot be executed. For this reason, there is a possibility that the production efficiency in the component mounter may be reduced by executing the firmware update process.

The present invention has been made in view of such circumstances, and provides a feeder management apparatus and management method capable of efficiently executing feeder firmware update processing while preventing a reduction in production efficiency in a component mounter. The purpose is to provide.

The feeder management apparatus according to claim 1 manages firmware incorporated in the feeder for a feeder that is replaceably mounted on a component mounter. The management device includes a version acquisition unit that acquires a current version of the firmware of the feeder that is communicably connected to the management device, the acquired current version, and the firmware that is designated by an update processing instruction for the feeder A necessity determination unit that determines whether or not the firmware update process is necessary based on the specified version, a required time acquisition unit that acquires a time required for the firmware update process for the feeder, and the necessity When the determination unit determines that the update process is necessary, the firmware is based on the required time and the pause time in which the feeder is connected to the management device so as to be communicable and the feeder is kept in a paused state. A process management unit for controlling the update process.

The feeder management method according to claim 8 manages the firmware incorporated in the feeder for a feeder that is replaceably mounted on the component mounter. The management method includes a version acquisition step of acquiring a current version of the firmware of the feeder that is communicably connected to the management apparatus, the acquired current version, and the firmware specified by an update processing instruction for the feeder A necessity determination step for determining whether or not the firmware update process is necessary based on the specified version, a required time acquisition step for acquiring a time required for the firmware update process for the feeder, and the necessity When it is determined in the determination step that the update process is necessary, the firmware is based on the required time and the pause time in which the feeder is communicably connected to the management device and the feeder is kept in a paused state. And a process management step for controlling the update process.

According to the configuration of claims 1 and 8, the firmware update process of the feeder is appropriately executed based on the time required for the update process and the pause time of the feeder. In other words, the firmware of the feeder is updated when a sufficient time exceeding the required time can be secured until the feeder operates in the mounting process by the component mounting machine. On the other hand, when the feeder operates and component supply is required in the mounting process by the component mounter, the mounting process is given priority and the firmware is not updated. Therefore, it is possible to efficiently execute the firmware update process of the feeder while preventing a decrease in production efficiency in the component mounter.

It is a lineblock diagram showing typically a substrate production line in an embodiment. It is a block diagram which shows the management apparatus of a feeder. It is a flowchart which shows the update control of firmware. It is a time chart which shows the relationship between the required time of an update process, and rest time. It is a time chart which shows the pause time before and after the optimization process.

Hereinafter, an embodiment in which the feeder management apparatus and the management method of the present invention are embodied will be described with reference to the drawings. A component mounter using a feeder is a device for mounting electronic components on a substrate. The component mounting machine constitutes a board production line used for manufacturing board products such as integrated circuits. The feeder management apparatus and management method target the firmware incorporated in the feeder.

<Embodiment>
(Whole board production line configuration)
In this embodiment, as shown in FIG. 1, the board production line 1 includes a screen printing machine 2, a plurality of component mounting machines 3, a reflow machine 4, a board transfer device 5, and a fixed point buffer device 6 (an “external device” of the present invention). And an automatic conveyance device 7. These devices constituting the substrate production line 1 are communicably connected to the host computer 40 via a network.

The screen printing machine 2 prints paste-like solder on the electronic component mounting position on the board that has been loaded. The component mounting machine 3 mounts an electronic component on the solder of the board conveyed from the screen printing machine 2 side. In the present embodiment, a plurality of component mounters 3 are arranged in the board conveyance direction. The detailed configuration of the component mounter 3 will be described later. The reflow machine 4 heats the board conveyed from the component mounting machine 3 side, melts the solder on the board, and performs soldering. The substrate transport device 5 is configured by a belt conveyor or the like, and sequentially transports the substrates in the transport direction (the left-right direction in FIG. 1).

The fixed point buffer device 6 accommodates the feeders 30 used in the plurality of component mounting machines 3 constituting the board production line 1. Further, the fixed point buffer device 6 displays, for example, on the display unit 6a so as to load the component packaging tape of the component type designated by the host computer 40 on the feeder 30, and guides the loading operation to the operator. . The automatic conveyance device 7 conveys the feeder 30 between each component mounter 3 and the fixed point buffer device 6. Based on the command of the host computer 40, the automatic transfer device 7 carries in the feeder 30 loaded with the supply reel to the component mounter 3, and unloads the feeder 30 used in the component mounter 3 to fix the fixed point. Return to buffer device 6.

The above-described feeder 30 is a cassette type in this embodiment, and is mounted with a supply reel wound with a component packaging tape. The component packaging tape includes a carrier tape that stores electronic components of a specific component type at a predetermined pitch, and a top tape that is bonded to the upper surface of the carrier tape and covers the electronic component. The feeder 30 is supplied with electric power while being held in the fixed point buffer device 6, a component supply device 11 of the component mounter 3 to be described later, and the buffer device 12, and can communicate with the component mounter 3 and the host computer 40. It becomes a state.

The feeder 30 includes a control unit 31 that controls the operation of each unit of the feeder. The control unit 31 is mainly composed of a CPU, various memories, and a control circuit. The control unit 31 incorporates firmware that performs electronic component supply control and the like. The control unit 31 executes the firmware based on a control signal input from the outside, a set value stored in the memory, and the like. Thereby, the feeder 30 pitch-feeds the component packaging tape withdrawn from the supply reel by the pitch feeding mechanism of the feeder body.

Then, the feeder 30 peels the top tape from the carrier tape to expose the electronic component. The feeder 30 supplies the electronic component so that the suction nozzle (not shown) of the component transfer device in the component mounter 3 can suck the electronic component by the supply control of the electronic component as described above.

The host computer 40 monitors the operation status of the board production line 1 and controls the component mounter 3 and the like. The host computer 40 has a storage device 41 composed of a hard disk, a flash memory, or the like. The storage device 41 stores various data for controlling the component mounter 3. Specifically, the storage device 41 stores a production plan including a type of board to be produced and a production quantity, an operation program for causing the component mounter 3 to execute a production process, and the like.

(Configuration of component mounter 3)
The plurality of component mounting machines 3 constituting the board production line 1 includes a component supply device 11, a buffer device 12, an automatic exchange device 13, and a control device 20. In the component supply device 11, a plurality of feeders 30 are respectively attached to a plurality of slot portions on the main body portion in a replaceable manner.

The buffer device 12 is disposed outside the component supply device 11, and temporarily holds the plurality of feeders 30 before and after the replacement of the feeders 30. Further, the buffer device 12 holds the feeder 30 that is in a standby state for carrying out by the automatic conveyance device 7. In the component mounter 3, the feeder 30 held in the component supply device 11 or the buffer device 12 is supplied with electric power and can communicate with the control device 20 and the host computer 40 of the component mounter 3.

The automatic exchange device 13 moves the feeder 30 between the component supply device 11 and the buffer device 12. More specifically, the automatic exchange device 13 takes out the feeder 30 from the buffer device 12 based on a command from the control device 20 and mounts the feeder 30 in the slot portion of the component supply device 11. In addition, the automatic changer 13 includes, for example, a feeder 30 in which electronic components need to be replenished in the component supply device 11 or a feeder 30 loaded with a component packaging tape of a component type that has become unnecessary based on a production plan. It is taken out from the component supply device 11 and moved to the buffer device 12.

The control device 20 is mainly composed of a CPU, various memories, and a control circuit. The control device 20 is communicably connected to the component supply device 11, the feeder 30, and the host computer 40 via a communication interface. The control device 20 controls operations of the component supply device 11 and the component transfer device based on the mounting process information such as the production plan and the operation program. With such a configuration, the component mounter 3 controls the mounting process of the electronic component, and mounts the electronic component on the solder of the board.

(Configuration of feeder 30 management device)
In the present embodiment, the control device 20 of the component mounter 3 constitutes a management device of the feeder 30 (hereinafter, the control device is also referred to as “management device”). Specifically, management control is performed with respect to execution of the firmware update process for the firmware incorporated in the feeder 30. Here, “firmware update” is an update from the current version to a different version, and includes version upgrade and version down.

The management device 20 includes a version acquisition unit 21, a necessity determination unit 22, a required time acquisition unit 23, a downtime calculation unit 24, a process management unit 25, and an information editing unit 26, as shown in FIG. When the feeder 30 is communicably connected to the management apparatus 20, the version acquisition unit 21 acquires the current version of the firmware incorporated in the feeder 30. That is, the version acquisition unit 21 acquires the current version when the feeder 30 is held in the component supply device 11 or the buffer device 12. Here, the “current version” of the firmware is the version of the firmware incorporated in the feeder 30 at the current time.

Also, there are various modes for obtaining the current version of the firmware. In the present embodiment, the version acquisition unit 21 employs an acquisition method using the management data M1 stored in the host computer 40. In the management data M1, information that associates an ID (identification code) that identifies the feeder 30 with the current version of the firmware of the feeder 30 and the time required for update processing to be described later is recorded.

More specifically, the version acquisition unit 21 first acquires an ID assigned to the feeder 30 through communication with the feeder 30. Next, the version acquisition unit 21 acquires the current version of the firmware of the feeder 30 based on the acquired ID and management data M1. The version acquisition unit 21 stores the acquired current version of the component device in the memory of the management apparatus 20.

The necessity determination unit 22 determines whether the firmware update process is necessary based on the acquired current version and the specified version specified by the update process instruction for the feeder 30. Here, for example, the update processing command specifies the firmware version for each type of feeder 30 or for each production process in the production plan. For the designated version, for example, a method of designating a specific version, the latest version, a higher version than the specific version, or the like is adopted.

The necessity determination unit 22 determines that the firmware update process is necessary, for example, when the compared current version and the specified version are different. Further, the necessity determination unit 22 determines that the update process is unnecessary when, for example, a minor specification change or a function addition is performed and the necessity for the update process is low based on a predesignated condition. May be.

The required time acquisition unit 23 acquires the required time required for the firmware update process for the feeder 30. Here, the “required time” required for the update process mainly includes a time for transferring the firmware update program M2 to the feeder 30 and a time for deploying the update program M2 and incorporating it as firmware. In addition, the required time appropriately includes a time required for restarting the feeder 30 for the update process, a delay time provided in consideration of the extension of the update process due to various factors, and the like.

Also, there are various modes for obtaining the time required for the update process. For example, the required time acquisition unit 23 may calculate and acquire the required time based on the size of the update program M2, the performance of the feeder 30, and the like. In the present embodiment, the required time acquisition unit 23 employs a method of acquiring the required time using the management data M1. In the management data M1, the required time calculated in advance in consideration of the performance of the feeder 30 and the delay time is associated with the ID of the feeder 30. Thus, the required time acquisition unit 23 is configured to be able to acquire the required time for the update process by referring to the host computer 40 for the ID.

The downtime calculation unit 24 calculates downtime based on the mounting process information including the production plan M3 and the operation program M4. Here, the “pause time” corresponds to a time during which the feeder 30 is connected to the management apparatus 20 so as to be communicable and the feeder 30 is kept in a dormant state. For example, when the feeder 30 is communicably connected to the component supply apparatus 11, the electronic component supply operation is started based on the operation program M4 after the feeder 30 is mounted on the component supply apparatus 11. The time from the completion of the supply operation to the start of the next supply operation corresponds to the pause time.

For example, when the feeder 30 is connected to the buffer device 12 so as to be communicable, the unloading starts after the feeder 30 is loaded into the buffer device 12 by the automatic transfer device 7 or the automatic exchange device 13 based on the mounting process information. The time until it is carried out, or the time from the present to the start of unloading corresponds to the pause time. During this pause time, the feeder 30 is in a state of being supplied with power, and the firmware update process by the control unit 31 is possible.

The process management unit 25 controls the firmware update process based on the required time and the suspension time when the necessity determination unit 22 determines that the update process is necessary. More specifically, the process management unit 25 determines that the firmware update process can be executed when the suspension time is longer than the required time, and issues an update process execution command to the control unit 31 of the feeder 30. Send it out. As a result, the control unit 31 of the feeder 30 downloads the update program M2 from the host computer 40 or the management apparatus 20, and executes the expansion process.

Further, the process management unit 25 notifies the information indicating the feeder 30 or the information of the update process when the firmware update process of the feeder 30 is being executed. More specifically, the process management unit 25 uses the position and number of the slot portion of the component supply apparatus 11 as information that can identify the feeder 30 that is executing the update process among the plurality of feeders 30, and information about the update process. Informs about the contents and progress of the process. As a notification method, for example, display on a monitor unit of the component mounting machine 3 or lighting of a notification lamp provided in each part is adopted. With this configuration, the process management unit 25 prevents an erroneous operation in which the feeder 30 that is executing the update process is removed from the slot part.

The information editing unit 26 changes the execution order of a plurality of production processes in the production plan M3 or changes the mounting order of electronic components in the operation program M4 so that a pause time longer than the required time is secured. Optimize processing information. As described above, even when the necessity determination unit 22 determines that the update process is necessary, the process management unit 25 notifies the control unit 31 of the feeder 30 when the time required for the update process exceeds the pause time. Do not send update processing execution instructions.

On the other hand, the time at which the feeder 30 to be managed operates or the time at which the feeder 30 is carried out from the buffer device 12 changes the execution order of a plurality of production processes in the production plan M3, or the electronic component mounting order in the operation program M4. Fluctuates by replacing Therefore, the information editing unit 26, for example, delays the production process that requires the operation of the feeder 30 to be managed or the mounting of the electronic components supplied by the feeder 30 so that the update process can be performed sufficiently. Secure.

(Management control of feeder 30)
Management control of the feeder 30 by the management device 20 will be described with reference to FIGS. The version acquisition unit 21 and the process management unit 25 of the management device 20 execute each process at an arbitrary timing. For example, when the feeder 30 is carried into the component supply device 11 or the buffer device 12 or when the power is turned on to the component mounter 3, the timing at which each process is executed is determined based on the production plan. For example, when it is migrated.

First, as shown in FIG. 3, the version acquisition unit 21 acquires the ID of the feeder 30 that is set in the component supply device 11 and the buffer device 12 and is in a communicable state (step 11 (hereinafter referred to as “step”). Next, the version acquisition unit 21 acquires the current version recorded in the management data M1 by referring to the host computer 40 for the ID of the feeder 30 acquired in S11 (S12). .

Also, the version acquisition unit 21 acquires the current version corresponding to each feeder 30 when the ID is acquired for a plurality of feeders 30. In this way, the version acquisition unit 21 acquires the current version of the feeder 30 that is the target of the firmware update process in the version acquisition step (S11, S12), and stores it in the memory of the management device 20.

Subsequently, in the necessity determination step (S13), the necessity determination unit 22 determines whether firmware update processing to the specified version is necessary based on the current version and the specified version. If the current version and the specified version are the same, the necessity determination unit 22 determines that it is not necessary to execute the update process because it has already been updated to the specified version (S13: No). Thereby, the management apparatus 20 complete | finishes the said management control.

On the other hand, if the current version and the specified version are different, the necessity determination unit 22 determines that the update process needs to be executed (S13: Yes). The required time acquisition unit 23 acquires the required time Tr of the update process recorded in the management data M1 by referring to the host computer 40 for the ID of the feeder 30 acquired in S11 in the required time acquisition step (S14). . Subsequently, the suspension time calculation unit 24 calculates the suspension time Td based on the mounting process information including the production plan M3 and the operation program M4 in the suspension time calculation step (S15).

Specifically, the downtime calculation unit 24 calculates the downtime Td for the patterns [A] to [C] as follows.
[A] When the feeder 30 is held in the component supply apparatus 11 (see the upper part of FIG. 4): The pause time calculation unit 24 first instructs the operation program M4 where the feeder 30 performs the supply operation of the electronic component. To extract. Next, the pause time calculation unit 24 refers to a pause time Td from the time when the feeder 30 is mounted on the component supply device 11 until the feeder 30 starts the electronic component supply operation due to the execution of the first command location. To do. When the pause time calculation unit 24 calculates the pause time Td, if the feeder 30 is already mounted on the component supply apparatus 11, the pause time calculation unit 24 starts the first supply operation by the feeder 30 from the present time. The time until this is taken is defined as a pause time Td.

Also, the pause time calculation unit 24 sets the pause time Td as the time from the completion of the electronic component supply operation by the feeder 30 to the start of the next supply operation by the feeder 30. Specifically, the pause time calculation unit 24 calculates a time interval between successive command locations among the extracted command locations, and sets the calculation result as the pause time Td.

[B] When the feeder 30 is in a state of waiting for the buffer device 12 to move to the component supply device 11 (see the middle part of FIG. 4): the pause time calculation unit 24 is set in the component supply device 11 Based on the remaining number of other feeders 30 that can supply the same kind of electronic components, the production plan M3, and the operation program M4, the feeder 30 that is on standby is started to move to the component feeder 11 by the automatic changer 13 Calculate the time. The pause time calculation unit 24 sets the pause time Td as the time from when the feeder 30 is held in the buffer device 12 to the calculated time.

[C] When the feeder 30 is moved from the component supply device 11 to the buffer device 12 and is waiting for unloading by the automatic conveyance device 7 (see the lower part of FIG. 4): Based on the operating state of M3 and the automatic conveyance device 7, the time when the feeder 30 in standby starts to be carried out to the fixed point buffer device 6 by the automatic conveyance device 7 is calculated. The pause time calculation unit 24 sets the pause time Td as the time from when the feeder 30 is held in the buffer device 12 to the calculated time.

The process management unit 25 determines whether the update process can be executed based on the required time Tr and the downtime Td (S16). If the required time Tr is shorter than the pause time Td, the process management unit 25 determines that the update process can be executed (S16: Yes). Therefore, the process management unit 25 executes a firmware update process for the feeder 30 (S17).

Specifically, in the process management process (S16, S17), the process management unit 25 first acquires an update program M2 corresponding to the specified version of firmware from the host computer 40. Next, the process management unit 25 communicates with the control unit 31 of the feeder 30 via the communication interface of the management device 20, and transfers the update program M2. The control unit 31 of the feeder 30 executes the expansion process of the transferred update program M2, and overwrites the existing firmware. As a result, the specified version of firmware is incorporated into the feeder 30. Note that, when the firmware update process of the feeder 30 is being executed (S17), the process management unit 25 notifies the information indicating the feeder 30 or the update process.

Subsequently, the process management unit 25 notifies the host computer 40 of the ID and current version (= designated version) of the feeder 30 to be updated in S17. The host computer 40 updates the management data M1 based on the information input from the process management unit 25 (S18). Thereby, in the management data M1, the feeder 30 that has been subjected to the update process records that the current version of the firmware is the designated version. Thereafter, the management device 20 ends the management control of the feeder 30.

In S16, when the required time Tr is longer than the pause time Td, the process management unit 25 determines that the update process cannot be executed (S16: No). Therefore, the process management unit 25 determines whether or not to execute the editing process for the production plan M3 or the operation program M4 in order to secure the downtime Td (S21). More specifically, the process management unit 25 performs the above determination based on, for example, the necessity for the change process to the specified version and whether there is room for editing the production plan M3 or the operation program M4.

When the process management unit 25 determines that the editing process is to be executed (S21: Yes), the information editing unit 26 changes the execution order of the plurality of production processes in the production plan M3, or the electronic component in the operation program M4. The mounting order is changed (S22). Specifically, as shown in FIG. 5, the information editing unit 26 edits and optimizes the operation program M4 so as to postpone the command location where the feeder 30 operates in the operation program M4.

The pause time calculation unit 24 calculates the pause time Td again based on the optimized operation program M4 (S15). When the suspension time Td longer than the required time Tr is secured by the optimization of the mounting process information by the information editing unit 26 (S16: Yes), the process management unit 25 controls the firmware update process ( Thereafter, the management data M1 is updated (S18). In S21, when the process management unit 25 determines that the editing process is not executed (S21: No), the process management unit 25 ends the management control of the feeder 30.

(Effects of the configuration of the embodiment)
The feeder management apparatus 20 according to the present embodiment manages the firmware incorporated in the feeder 30 for the feeder 30 that is replaceably mounted on the component mounter 3. The feeder management device 20 is designated by a version acquisition unit 21 that acquires the current version of the firmware of the feeder 30 that is communicably connected to the management device 20, the acquired current version, and an update processing instruction for the feeder 30. A necessity determination unit 22 that determines whether firmware update processing is necessary based on the designated version of the firmware, a required time acquisition unit 23 that acquires a required time Tr required for firmware update processing for the feeder 30, and When it is determined that the update process is necessary by the refusal determination unit 22, based on the required time Tr and the pause time Td in which the feeder 30 is communicably connected to the management device 20 and the feeder 30 is maintained in the paused state. And a process management unit 25 that controls firmware update processing.

According to such a configuration, the firmware update process of the feeder 30 is appropriately executed based on the required time Tr required for the update process and the pause time Td of the feeder 30. That is, the firmware of the feeder 30 is updated when a sufficient time exceeding the required time Tr can be secured until the feeder 30 operates in the mounting process by the component mounting machine 3. On the other hand, when the feeder 30 operates to supply components in the mounting process by the component mounting machine 3, the mounting process is prioritized and the firmware is not updated. Therefore, the firmware update process of the feeder 30 can be efficiently executed while preventing a reduction in production efficiency in the component mounter 3.

The component mounter 3 mounts electronic components on the board based on the mounting process information including the production plan M3 and the operation program M4. The management device 20 further includes a pause time calculation unit 24 that calculates the pause time Td based on the mounting process information.
According to such a configuration, the process management unit 25 can calculate the pause time Td based on the mounting process information, and thus can more accurately determine whether or not update processing is possible. Therefore, the management apparatus 20 can execute the firmware update process more efficiently.

In addition, the management device 20 changes the order of execution of a plurality of production processes in the production plan M3 or changes the order of mounting electronic components in the operation program M4 so that a pause time Td longer than the required time Tr is secured. And an information editing unit 26 for optimizing the mounting process information.
According to such a configuration, the information editing unit 26 optimizes the mounting process information, and the pause time Td of the feeder 30 is ensured. As a result, the firmware update process can be performed while securing the pause time Td even for the feeder 30 in which the pause time Td is shorter than the required time Tr and the update process cannot be executed in the mounting process information before editing. Therefore, it is possible to set the update process as a target while maintaining the production efficiency.

In addition, the component mounting machine 3 is disposed outside the component supply device 11 by operating a plurality of replaceable feeders 30 to supply electronic components, and before and after replacing the feeder 30. A buffer device 12 that temporarily holds the feeder 30 and an automatic changer device 13 that moves the feeder 30 between the component supply device 11 and the buffer device 12 are provided.
The management device 20 sets the feeder 30 held in the buffer device 12 as a management target. The pause time Td is the time from when the feeder 30 is held in the buffer device 12 until the automatic changer 13 starts moving to the component supply device 11 (see the middle part of FIG. 4).

According to such a configuration, the component mounter 3 performs replacement by automatically moving the feeder 30 between the component supply device 11 and the buffer device 12 by the automatic replacement device 13. Since the feeder 30 held in the buffer device 12 has a relatively long pause time Td, the management device 20 makes the feeder 30 a target of management, so that the pause time Td is effectively used to perform update processing. Can be executed.

Further, the buffer device 12 holds the feeder 30 in a standby state for unloading by the automatic transport device 7 that transports the feeder 30 between the component mounting machine 3 and the external device. The management device 20 sets the feeder 30 moved from the component supply device 11 to the buffer device 12 as a management target. The pause time Td is the time from when the feeder 30 is held in the buffer device 12 until the automatic conveying device 7 starts to carry out (see the lower part of FIG. 4).

According to such a configuration, the buffer device 12 automatically carries the feeder 30 in and out of the external device by the automatic conveyance device 7. Since the feeder 30 in the standby state for carrying out in the buffer device 12 has a relatively long pause time Td, the management device 20 makes the feeder 30 the object of management so that the pause time Td is effectively used. Update process.

In addition, the component mounter 3 includes a component supply device 11 that operates a plurality of feeders 30 that are replaceably mounted to supply electronic components.
The management device 20 targets the feeder 30 mounted on the component supply device 11 as a management target. The pause time Td is the time from when the feeder 30 is mounted on the component supply apparatus 11 until the electronic component supply operation is started, or the time from when the supply operation is completed until the next supply operation is started. (See the upper part of FIG. 4).

Depending on the execution order of production processing in the production plan M3 and the mounting order of electronic components in the operation program M4, the pause time Td of the feeder 30 mounted on the component supply device 11 may be longer than the required time Tr required for the update process. is there. Therefore, when the management apparatus 20 sets the feeder 30 as a management target, the update process can be executed by effectively using the downtime Td.

Further, when the firmware update process of the feeder 30 is being executed, the process management unit 25 notifies the information indicating the feeder 30 or the update process (S17).
According to such a configuration, it is possible to prevent the feeder 30 that has been executing the update process from being disconnected due to an erroneous operation or the like, thereby interrupting communication or power supply.

The feeder management method manages the firmware incorporated in the feeder 30 for the feeder 30 that is replaceably mounted on the component mounter 3. The feeder management method includes a version acquisition step (S11, S12) for acquiring the current version of the firmware of the feeder 30 that is communicably connected to the management apparatus 20, the acquired current version, and an update processing instruction for the feeder 30. Necessity determination step (S14) for determining whether or not the firmware update process is necessary based on the designated version of the specified firmware, and the required time acquisition for acquiring the required time Tr required for the firmware update process for the feeder 30 When it is determined in the step (S15) and the necessity determination step that the update process is required, the required time Tr and the feeder 30 are communicably connected to the management device 20 and the pause in which the feeder 30 is maintained in the paused state. Process management for controlling firmware update process based on time Td Comprising extent and (S16, S17), the.
According to such a configuration, the same effects as described above can be obtained. That is, the firmware update process of the feeder 30 can be efficiently executed while preventing a reduction in production efficiency in the component mounter 3.

<Modification of Embodiment>
In the embodiment, the version acquisition unit 21 acquires an ID from the feeder 30 that is communicably held in the component supply device 11 and the buffer device 12, and acquires the current version based on the ID and the management data M1 (S11). , S12). On the other hand, the version acquisition unit 21 may directly acquire the ID and the current version through communication with the feeder 30 regardless of the management data M1.

In the embodiment, the management device 20 is a control device for the component mounter 3. On the other hand, the units 21 to 26 constituting the management apparatus 20 are provided in either the component mounter 3 or the host computer 40 or an external device connected via a network as long as they can communicate with the feeder 30. It is good also as a structure. Specifically, the management device 20 is provided in, for example, the fixed point buffer device 6 or a tape loading device for loading a component packaging tape into the feeder 30 and performs firmware update processing in the fixed point buffer device 6 or the like. May be.

1: Board production line 2: Screen printing machine 3: Component mounting machine 4: Reflow machine 5: Board transfer device 6: Fixed point buffer device (external device) 6a: Display unit 7: Automatic transfer device 11: Component supply device , 12: buffer device, 13: automatic exchange device, 20: control device (management device)
21: Version acquisition unit, 22: Necessity determination unit 23: Required time acquisition unit, 24: Downtime calculation unit 25: Process management unit, 26: Information editing unit,
30: Feeder 31: Control unit 40: Host computer 41: Storage device M1: Management data M2: Update program M3: Production plan M4: Operation program Tr: Time required Td: Rest time

Claims

A feeder management device that manages firmware installed in a feeder for a feeder that is replaceably mounted on a component mounter.
A version acquisition unit that acquires a current version of the firmware of the feeder that is communicably connected to the management device;
Based on the acquired current version and the specified version of the firmware specified by the update processing command for the feeder, a necessity determination unit that determines whether the firmware update process is necessary,
A required time acquisition unit for acquiring a required time required for the update process of the firmware for the feeder;
When the necessity determination unit determines that the update process is necessary, based on the required time and a pause time during which the feeder is connected to the management apparatus so as to be communicable and the pause state of the feeder is maintained. A process management unit that controls the update process of the firmware;
Feeder management device comprising:
The component mounter mounts electronic components on a board based on mounting processing information including a production plan and an operation program,
The feeder management apparatus according to claim 1, further comprising a pause time calculation unit that calculates the pause time based on the mounting process information.
The mounting process information is switched by changing the execution order of the plurality of production processes in the production plan or by changing the mounting order of the electronic components in the operation program so that the suspension time longer than the required time is secured. The feeder management apparatus according to claim 2, further comprising an information editing unit that optimizes the information.
The component mounter is
A component supply device that operates a plurality of the replaceably mounted feeders to supply electronic components;
A buffer device disposed outside the component supply device and temporarily holding the feeder before and after replacement of the feeder;
An automatic changer that moves the feeder between the component supply device and the buffer device, and
The management device targets the feeder held in the buffer device as a management target,
The suspension time is a time from when the feeder is held in the buffer device to when the automatic changer starts moving to the component supply device. Feeder management device.
The buffer device holds the feeder in a standby state for unloading by an automatic transport device that transports the feeder between the component mounter and an external device,
The management device targets the feeder moved from the component supply device to the buffer device, and
The feeder management device according to claim 4, wherein the pause time is a time from when the feeder is held in the buffer device to when the automatic conveying device starts to be carried out.
The component mounter includes a component supply device that operates the plurality of feeders that are replaceably mounted to supply electronic components,
The management device targets the feeder mounted on the component supply device,
The pause time is the time from when the feeder is mounted on the component supply device until the electronic component supply operation is started, or until the next supply operation is started after the supply operation is completed. The feeder management apparatus according to any one of claims 1 to 5, wherein the feeder management time is equal to a predetermined time.
7. The process management unit according to claim 1, wherein when the update process of the firmware of the feeder is being executed, information indicating the feeder or information of the update process is notified. Feeder management device.
A feeder management method for managing firmware incorporated in a feeder for a feeder that is replaceably mounted on a component mounter,
A version acquisition step of acquiring a current version of the firmware of the feeder communicatively connected to the management device;
Based on the acquired current version and the specified version of the firmware specified by the update processing command for the feeder, a necessity determination step for determining whether the firmware update process is necessary,
A required time acquisition step of acquiring a required time required for the update process of the firmware for the feeder;
When it is determined in the necessity determination step that the update process is necessary, based on the required time and the pause time during which the feeder is connected to the management apparatus so as to be communicable and the pause state of the feeder is maintained. A process management step for controlling the update process of the firmware;
A feeder management method comprising: