JP2013012088A - Development support method and program - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a development support method enabling efficient development of a control program.SOLUTION: A development support method includes: a log acquisition step (S11) for acquiring a log output by a control program installed in a mounting substrate manufacturing apparatus from a log file; a test scenario creation step (S12) for creating a test scenario such as causing transitions of the state of a drive unit in an order written in the log acquired at the log acquisition step; and a test execution step (S13) for executing a control program for testing, according to the test scenario created at the test scenario creation step.

Description

  The present invention relates to a development support method, and more particularly to a method for supporting the development of a control program for controlling the operation of a drive unit of a mounting board manufacturing apparatus.

  In order to improve the efficiency of software development, a software design tool based on a state transition table design method for finding out more and more in advance has a function of automatically generating source code from a state transition table. Some of such software design tools further include a simulation test function (see, for example, Patent Document 1).

JP-A-11-102205

  However, in the above-described software design tool, if an actual simulation test is to be performed, a separate test module must be created using another development tool. In other words, each test module must be custom-created, and there is a problem that it is difficult to use as a development tool.

  The present invention has been made in view of the above problems, and an object thereof is to provide a development support method capable of efficiently developing a control program.

  A development support method according to an aspect of the present invention is a method of supporting development of a control program for controlling the operation of a drive unit of a mounting board manufacturing apparatus by a computer. The control program is executed by the drive unit for each of a state of the drive unit, an event generated as a result of processing executed outside the control program, and a combination of the state of the drive unit and the event. And the next state of the driving unit are generated based on a defined state transition table, and each time the state of the driving unit transitions, the result of the operation of the driving unit and the driving unit A log in which information specifying the next state is described is output to a log file. In the development support method, the log acquisition step of reading the log output by the control program incorporated in the mounting board manufacturing apparatus from the log file and the state of the drive unit are acquired in the log acquisition step. A test scenario creation step for creating a test scenario for transition in the order described in the recorded log, and a test execution for test execution of the control program according to the test scenario created in the test scenario creation step Steps.

  In this way, by executing test execution of the control program according to the test scenario created based on the log, the computer reproduces the situation in which the control program incorporated in the mounting board manufacturing apparatus actually operates the drive unit. can do. As a result, it is possible to quickly and accurately grasp the cause of the trouble occurring at the site and improve it.

  Furthermore, the operation time of the drive unit in each state on the state transition table may be described in the log. In the test scenario creating step, the control program instruction corresponding to each operation of the drive unit is matched with the operation time of the drive unit described in the log at the time of the test execution of the control program in the test execution step. The test scenario may be created such that the test scenario is executed. In the test execution step, the drive unit on the three-dimensional drawing of the mounting board manufacturing apparatus displayed on the display screen is moved so as to perform an operation corresponding to the instruction of the control program to be tested. You may let them.

  In the test execution step, the driving unit on the three-dimensional drawing displayed on the display screen is accelerated or decelerated so that the operation is completed within the operating time of the driving unit described in the log. You may move according to a curve. This makes it possible to faithfully reproduce troubles that occur at delicate timing on a computer.

  Further, the development support method is configured such that each time each instruction of the control program is test-executed in the test execution step, the current position on the state transition table corresponding to the instruction and the current position until the current position is reached. An output step of outputting a locus on the state transition table may be included. Thereby, for example, it is possible to provide the user with information for specifying the cause when the process ends abnormally.

  A program according to an aspect of the present invention causes a computer to execute the development support method described above.

  According to the present invention, by testing a control program according to a test scenario created based on a log, it is possible to quickly and accurately grasp and improve the cause of a trouble that has occurred in the field.

FIG. 1 is an external view of a component mounting system according to an embodiment of the present invention. FIG. 2 is a configuration diagram showing the main mechanical configuration inside the component mounter. FIG. 3 is a schematic diagram showing the positional relationship between the head and the component cassette. FIG. 4 is a diagram illustrating an example of a component tape and a reel that contain components. FIG. 5 is a functional block diagram of the component mounter in the present embodiment. FIG. 6 is a diagram illustrating an example of NC data. FIG. 7 is a diagram illustrating an example of a component library. FIG. 8 is a diagram illustrating an example of the mounting condition data. FIG. 9 is a diagram illustrating a hardware configuration of a computer that executes a development support program. FIG. 10 is a diagram illustrating an example of the state transition table. FIG. 11 is a diagram illustrating an example of source code generated from the state transition table of FIG. FIG. 12 is a flowchart showing the operation of the development support program. FIG. 13 is a diagram illustrating an example of a log written in the log file. FIG. 14 is a diagram illustrating an example of a test scenario. FIG. 15 is a diagram showing the execution order of the test scenario of FIG. FIG. 16 is a diagram illustrating an example of a screen displayed on the display unit when the test is executed.

  FIG. 1 is an external view of a component mounting system according to an embodiment of the present invention.

  A component mounting system 1000 according to the present embodiment includes a component mounter 100 and a control device 200 that controls the component mounter 100. In FIG. 1, the control device 200 is illustrated as a separate body from the component mounter 100, but the control device 200 may be provided in the component mounter 100.

  The component mounting machine 100 receives a board (circuit board) 20 from upstream, mounts a component on the board 20, and sends the board 20 on which the component is mounted downstream. In addition, the board | substrate 20 with which components were mounted by the component mounting machine 100 is hereafter called a mounting board.

  Specifically, the component mounter 100 includes two component supply units 115 a and 115 b that supply a plurality of types of components, and a carry-in port 130 that carries the board 20 into the component mounter 100. The component mounting machine 100 stops the board 20 carried in from the carry-in port 130 at a predetermined position. Then, the component mounter 100 sequentially takes out the components supplied from the component supply units 115a and 115b, and mounts the removed components on the board 20 stopped at a predetermined position.

  In addition, the component mounting machine 100 uses an imaging device or the like for the components supplied from the component supply units 115a and 115b, the substrate 20 before mounting the components, the state of the components after mounting on the substrate 20, and the like. Recognize.

  The control device 200 determines a component mounting condition or the like by the component mounting machine 100 and controls the component mounting machine 100 so that the mounting is performed according to the mounting condition.

  FIG. 2 is a configuration diagram showing a main mechanical configuration inside the component mounter 100.

  The component mounting machine 100 includes two mounting units 110a and 110b for mounting components on the substrate 20, a pair of substrate transport rails 122a and 122b for transporting the substrate 20, and a pair of beam driving robots 140. ing. The two mounting units 110a and 110b cooperatively mount components on the substrate 20 on the substrate transport rails 122a and 122b.

  The mounting unit 110a and the mounting unit 110b have the same configuration. That is, the mounting unit 110a includes a component supply unit 115a, a component inspection unit 116a, a head 112a, and a beam 121a. Similarly, the mounting unit 110b includes a component supply unit 115b, a component inspection unit 116b, a head 112b, and a beam 121b.

  Here, a detailed configuration of the mounting unit 110a will be described. The detailed configuration of the mounting unit 110b is the same as that of the mounting unit 110a, and will not be described.

  The component supply unit 115a includes an array of a plurality of component cassettes (feeders) 114 that store component tapes. In addition, the component cassettes 114 of the component supply unit 115a are arranged along the conveyance direction (X-axis direction) of the substrate 20. The component tape is, for example, a plurality of components of the same component type arranged on a tape (carrier tape) and supplied in a state of being wound on a reel or the like. The parts arranged (stored) on the part tape are, for example, chip parts, specifically, 0402 chip parts, 1005 chip parts, and the like.

  The head 112a is a head called a multi-mounted head, for example, and can include a plurality of suction nozzles (hereinafter simply referred to as nozzles). For example, ten components can be adsorbed from the component supply unit 115 a and mounted on the substrate 20. Such a head 112a is slidably attached to a beam 121a configured in a shaft shape. The head 112a moves along the beam 121a, for example, by driving an actuator such as a motor. The head 112a is provided with component inspection units 116a and 116b for inspecting the state of the substrate 20 before mounting the components, the state of the components after mounting on the substrate 20, and the like.

  The beam 121a is slidably mounted in the Y-axis direction on a pair of beam driving robots 140 arranged parallel to each other along a direction (Y-axis direction) perpendicular to the transport direction (X-axis direction) of the substrate 20. ing. Therefore, the beam 121a moves on the pair of beam driving robots 140 along the Y-axis direction by driving an actuator such as a motor. That is, the head 112a is moved in the X-axis direction and the Y-axis direction by the beam driving robot 140 and the beam 121a.

  The substrate transport rails 122a and 122b are arranged so as to be parallel to the X-axis direction. Here, the board conveyance rail 122a is fixed to the component supply unit 115a side. On the other hand, the substrate transport rail 122b moves in the Y-axis direction according to the size (width) of the substrate 20 to be transported. The board 20 carried in from the carry-in port 130 of the component mounting machine 100 is carried along the pair of board carrying rails 122a and 122b and stopped at a predetermined position by a stopper or the like.

  The component inspection unit 116a is used for two-dimensionally or three-dimensionally inspecting the shape and suction state of the component sucked by the head 112a. The component inspection unit 116a is disposed in the vicinity of the center along the X-axis direction in the component supply unit 115a.

  In the component mounting machine 100 configured as described above, the head 112a picks up the component supplied from the component supply unit 115a and moves it onto the substrate 20, and uses the sucked component at each mounting point of the substrate 20. A series of operations of mounting and moving on the component supply unit 115a is repeatedly executed. Similarly, the head 112b picks up the component supplied from the component supply unit 115b and moves it onto the substrate 20, attaches the sucked component to each mounting point of the substrate 20, and moves it onto the component supply unit 115b. A series of operations are repeatedly executed.

  A group of parts that are attracted to the head by a series of operations executed in this way or a series of operations per time will be referred to as a task hereinafter. The mounting point is a position where a component on the board 20 is to be mounted.

  An example of one task by the head 112a will be specifically described. First, the head 112a sucks components for one task supplied from each component cassette 114 of the component supply unit 115a while moving in the X-axis direction and the Y-axis direction. Thereafter, the head 112a moves on the component inspection unit 116a at a constant speed or temporarily stops, thereby causing the component inspection unit 116a to pick up an image of the adsorbed component, and a point before entering the mounting area of the substrate 20 Reach the rush point that is. Then, the head 112a starts moving at a predetermined timing from the entry point and enters the mounting area of the substrate 20. There may be a plurality of entry points.

  The mounting area is an area where mounting points of the substrate 20 exist, and may be a partial area or all areas of the substrate 20. The head 112a that has entered the mounting area mounts the sucked components on each mounting point while moving in the X-axis direction and the Y-axis direction. When the mounting of all components for one task is completed, the head 112a moves out of the mounting area of the substrate 20 and moves onto the component supply unit 115a.

  On the other hand, the head 112b also performs the same operation as that of the head 112a described above, but the heads 112a and 112b do not interfere with each other. Operate in cooperation with each other so as not to enter.

  FIG. 3 is a schematic diagram showing the positional relationship between the head 112a and the component cassette 114. As shown in FIG.

  As described above, for example, a maximum of 10 nozzles nz can be arranged and attached to the head 112a in the X-axis direction. For example, the head 112a to which the ten nozzles nz are attached can suck components from each of a maximum of ten component cassettes 114 sequentially or simultaneously (by one up and down movement). Similarly, the head 112b can be attached with, for example, a maximum of ten nozzles nz. In the present invention, the number of nozzles nz attached to the heads 112a and 112b may be other than ten, and a plurality of rows of nozzles nz along the X-axis direction may be attached in the Y-axis direction.

  FIG. 4 is a diagram illustrating an example of a component tape and a reel that contain components.

  A component 423d such as a chip-type electronic component is held by a carrier tape 424 shown in FIG. The carrier tape 424 is provided with a plurality of storage recesses 424a formed continuously at regular intervals. Parts are stored in the storage recess 424a. Further, a cover tape 425 is affixed to the upper surface of the carrier tape 424 (the side from which components are taken out). The carrier tape 424 to which the cover tape 425 is attached is supplied to the user in a taping form in which the carrier tape 424 is wound around the reel 426 by a predetermined number. Such a carrier tape 424 and a cover tape 425 constitute a component tape. The configuration of the component tape may be other than the configuration shown in FIG.

  In the component mounter 100 in the present embodiment, as described above, the heads 112a and 112b operate while emphasizing each other so that they do not simultaneously enter the interfering region on the mounting region of the substrate 20. As a result, the component mounting machine 100 executes so-called alternating and non-alternating. Alternating is an operation in which mounting of parts for one task by the head 112a and mounting of parts for one task by the head 112b are alternately performed. On the other hand, non-alternating is an operation in which mounting of parts for one task by the head 112a or the head 112b is repeatedly performed with the same head.

  FIG. 5 is a block diagram showing a functional configuration of a control system of the component mounter 100 in the present embodiment.

  The component mounter 100 according to the present embodiment includes an input unit 151, a display unit 152, a head control unit 153, a control unit 154, a communication unit 155, and a storage unit 156.

  The input unit 151 includes, for example, a keyboard and a mouse, receives an operation from an operator (user), and notifies the operation result to the head control unit 153, the control unit 154, and the like.

  The display unit 152 includes, for example, a liquid crystal display, and displays the operation state of the head control unit 153 or the like, or displays data stored in the storage unit 156 or the like.

  The control unit 154 controls the component inspection units 116a and 116b, the display unit 152, the head control unit 153, and the like according to the operation received by the input unit 151 and the data received by the communication unit 155. Further, the control unit 154 controls a motor or the like for transporting the substrate 20 and transports the substrate 20 to an appropriate position.

  The communication unit 155 communicates with the control device 200. For example, the communication unit 155 indicates NC data 156a indicating information on each mounting point of the board 20, a component library 156b indicating information on each component, and mounting conditions such as the arrangement of the component cassette 114 and the component mounting order. The mounting condition data 156c is acquired from the control device 200 and stored in the storage unit 156. 5 shows an example in which the control device 200 and the control unit 154 are configured separately, but the control device 200 is provided in the control unit 154 as a configuration in the control system of the component mounter 100. Also good. Further, the control device 200, the head control unit 153, and the control unit 154 may be collectively configured as a control unit.

  The storage unit 156 stores NC data 156a acquired by the communication unit 155, a component library 156b, mounting condition data 156c, and the like.

  FIG. 6 is a diagram illustrating an example of the NC data 156a.

  The NC data 156a indicates information related to mounting points of all components to be mounted on the board 20. One mounting point pi includes a component type ci, an X coordinate xi, a Y coordinate yi, control data φi, and a mounting angle θi. Here, the component type corresponds to a component name in the component library 156b (see FIG. 7). The X coordinate and the Y coordinate are the coordinates of the mounting point. The control data φi indicates constraint information related to the mounting of the component, for example, the type of nozzle nz that can be used, the maximum movement acceleration of the heads 112a and 112b, and the like. The mounting angle θi indicates an angle at which the nozzle nz that has picked up the component of the component type ci should rotate.

  FIG. 7 is a diagram illustrating an example of the component library 156b.

  The component library 156b is a library in which unique information for each of all component types that can be handled by the component mounter 100 is collected. As shown in FIG. 7, the component library 156b includes a component size (width, depth, thickness, etc.) for each component type (component name), tact in the component type, constraint information, and the like.

  The tact indicated by the component library 156b is a time specific to the component type required to mount the component on the board 20 under a certain condition. The constraint information is, for example, the type of nozzle nz that can be used (SX, SA, etc.), the recognition method (reflection, etc.) by the component inspection units 116a, 116b, and the maximum acceleration ratio of the heads 112a, 112b. FIG. 7 also shows the appearances of the components of each component type for reference. In addition, the component library 156b may include information such as the color and shape of the component.

  FIG. 8 is a diagram illustrating an example of the mounting condition data 156c.

  The mounting condition data 156c indicates the arrangement (component arrangement) of the component cassettes 114 in the component supply units 115a and 115b, the mounting order for each task of the heads 112a and 112b, and the like. For example, the mounting condition data 156c indicates that there is a component type c1 at the A1th and a component type c2 at the A2th from one side in the X-axis direction of the component supply unit 115a. Similarly, it shows that there is a component type c1 at B1 from the one side in the X-axis direction of the component supply unit 115b, and there is a component type c2 at B2.

  The mounting condition data 156c includes a task number Ta1 including the components of the component types c1 to c4 as the mounting order of the head 112a, and then a task of the task number Ta2 including the components of the component types c9 to c12. Is executed, and thereafter, the task of the task number Ta3 including the parts of the parts type c17 to c20 is executed. Similarly, in the mounting condition data 156c, as the mounting order of the head 112b, the task with the task number Tb1 including the components of the component types c5 to c8 is executed, and then the task number Tb2 including the components of the component types c13 to c16 is executed. This indicates that the task is executed, and then the task with the task number Tb3 including the parts of the part types c21 to c24 is executed. The mounting condition data 156c also indicates the mounting point of each component included in the task.

  The head control unit 153 controls the motor and the like based on the data stored in the storage unit 156, thereby moving the heads 112a and 112b, adsorbing components to the heads 112a and 112b, and adsorbing components. The heads 112a and 112b thus moved are moved to the component inspection units 116a and 116b, or the components are mounted on the mounting points on the substrate 20. The operation of the head controller 153 is controlled by a control program developed by a development support method described later.

  For example, the head control unit 153 reads the above-described mounting condition data 156c, specifies the task to be mounted by the heads 112a and 112b according to the task number, and specifies the location where the parts of the task are supplied based on the component arrangement To do. Then, the head controller 153 moves the heads 112a and 112b to the specified locations, causes the heads 112a and 112b to adsorb components, and attaches them to the mounting points corresponding to the components.

  The head controller 153 controls the head 112a according to the movement of the other head 112b. Similarly, the head 112b is controlled according to the movement of the other head 112a. That is, the head control unit 153 controls a head to be controlled (hereinafter referred to as a target head) according to the movement of the other head (hereinafter referred to as a counterpart head).

  When the target head reaches the entry point when the counterpart head is on the mounting area of the substrate 20, the head control unit 153 causes the target head to wait at the entry point. Then, when the counterpart head comes out of the interference area where the heads of the mounting area interfere with each other, the target head is caused to enter the mounting area. In addition, when the target head reaches the entry point when the counterpart head is not on the mounting area of the substrate 20, the head control unit 153 basically puts the target head on the mounting area without waiting at the entry point. Let it rush.

  However, the head control unit 153 in the present embodiment causes the target head to enter the mounting area of the substrate 20 at the timing when the target head reaches the entry point, and when non-alternate hitting is likely to be performed. Then, it is discriminated whether or not the non-alternating strike should be avoided and the alternate strike should be forcibly executed. If it is determined that non-alternate beating should be avoided, the head control unit 153 installs a part for one task after the partner head enters the mounting area even if the partner head is not on the mounting area. The target head is kept waiting at the entry point until exiting. As a result, forced alternating driving is realized.

  In addition, as described above, the alternate hitting is an operation in which mounting of a part for one task by the head 112a on the substrate 20 and mounting of a part for one task by the head 112b are alternately performed. In this order, the components are mounted on the board 20 in the order of “head 112a → head 112b → head 112a → head 112b →...”. Further, non-alternating is an operation in which mounting of parts for one task by the head 112a or the head 112b is repeatedly performed as described above. For example, “head 112a → head 112b → head 112b → This is an operation in which mounting of components by the same head is successively performed in the order of the head 112a →.

  Next, a development support method for supporting development of a program for controlling the operation of the head control unit 153 having the above configuration will be described. Note that the development support method of the present invention is typically provided in the form of a program (development support program) executed by a computer.

  FIG. 9 is a diagram illustrating a hardware configuration of the computer 10 that executes the development support program according to the present embodiment. As shown in FIG. 9, the computer 10 mainly includes a CPU (Central Processing Unit) 11, a ROM (Read Only Memory) 12, a RAM (Random Access Memory) 13, an input unit 14, and a display unit 15. Prepare for.

  The CPU 11 executes a program stored in the ROM 12 or the RAM 13. The ROM 12 stores, for example, a program (BIOS or the like) required when the computer 10 is started up. The RAM 13 stores, for example, various programs and is also used as a temporary storage area for calculation results by the CPU 11. The development support program according to the present embodiment is also stored in the RAM 13.

  The specific configuration of the RAM 13 is not particularly limited. For example, the RAM 13 is a means capable of recording data such as a DRAM (Dynamic Random Access Memory), an SDRAM (Synchronous Dynamic Random Access Memory), a flash memory, or a ferroelectric memory. You can use whatever you like.

  The input unit 14 is an interface that receives input from the user, and is, for example, a keyboard or a mouse. The display unit 15 is a display that displays various types of information to the user. Although the specific structure of a display is not specifically limited, For example, a liquid crystal display, a plasma display, or an organic EL (Electro Luminescence) display etc. are employable.

  The development support program according to the present embodiment supports the development of a program (hereinafter referred to as “control program”) for controlling the operation of the drive unit (the heads 112a and 112b in this example) of the component mounter 100. is there.

  An example of a program generated by the development support program according to the present embodiment will be described with reference to FIGS. FIG. 10 is a diagram illustrating an example of the state transition table. FIG. 11 is a diagram illustrating an example of the generated source code. However, in FIG. 11, description is made centering on the part taken up in the following description, and description of other parts is omitted.

  First, a state transition table as shown in FIG. 10 is designed by the user. Specifically, the development support program displays an input screen on the display unit 15 and accepts an input from the user via the input unit 14.

  Note that the state transition table is, for example, a matrix table composed of rows and columns as shown in FIG. In the first row (top row) of this state transition table, for example, the states of the heads 112a, 112b, etc. are defined. In the first column, events generated as a result of processing executed outside the control program are defined. The state may be defined in the first column and the event may be defined in the first row. Further, in each cell other than the first row and the first column, an operation to be executed by the heads 112a and 112b and a next state of the heads 112a and 112b are defined with respect to a combination of the state and the event.

  Here, “an event generated as a result of processing executed outside the control program” refers to, for example, an event generated as a result of a communication command from a host system, a GUI (Graphical User Interface), or a user operation such as an operation switch. As a result of the control program, a program that generates an event that occurs as a result, an event that occurs as a result of the operation of the drive unit (in this example, the heads 112a and 112b), or an event that occurs as a result of processing executed outside the control program. An event or the like that occurs when the program is installed in advance and the program is executed corresponds.

  For example, as shown in FIG. 10, the states of the heads 112a and 112b are “stopped”, “part feeder moving”, “part suction moving”, “part suction recognition position moving”, “part recognition”. “Medium”, “Moving component mounting position”, “Mounting component”, “Error occurring”, etc. Further, the events generated as a result of processing executed outside the control program are, for example, as shown in FIG. 12, “component suction start”, “component feeder position movement completion”, “component suction completion”, “component For example, “suction recognition position movement completion”, “component recognition completion”, “component mounting position movement completion”, “component mounting completion”, “error”, and “error return”.

  Further, the operations performed by the heads 112a and 112b corresponding to the states and events and the next state of the heads 112a and 112b are moved downward from any cell in the first row and rightward from any cell in the first column. Defined in the cell at the intersection.

  For example, the operation corresponding to “part feeder position moving” in the first row and “part feeder position movement completed” in the first column is “part suction ()”, and the next state is “part suction”. (“(Event ID, State ID) = (1, 1)” cell in FIG. 10). That is, in this state transition table, when the state of the heads 112a and 112b is “part feeder position moving” and the “part feeder position movement complete” event occurs, the heads 112a and 112b execute the part suction processing. As a result of the component suction processing, the state of the heads 112a and 112b transitions to “part suctioning”. Note that the heads 112a and 112b have different states and event timings between the heads 112a and 112b when the above-described alternating or non-alternating is selected.

  Next, the development support program generates the source code as shown in FIG. 11 of the target module from the state transition table shown in FIG. Further, the development support program compiles the generated source code to generate an object of the target module (hereinafter, “component mounting process object”).

  In FIG. 11, a state of a global variable (global variable) is a variable for setting a state ID (0 to 7) that specifies the state of the heads 112a and 112b. The global variable (global variable) event is a variable for setting an event ID (0 to 8) for specifying an event. The global variable (global variable) cnt is a variable for setting the number of components to be mounted in one task. Furthermore, the local variable result is a variable for setting a return value of an external function called in the component mounting process StmCall (), for example.

  In FIG. 11, the component feeder movement () is an external function for moving the heads 112 a and 112 b to predetermined positions of the component supply units (component feeders) 115 a and 115 b. The component adsorption () is an external function for causing the heads 112 a and 112 b to adsorb the mounted component on the component feeder. The component suction recognition () is an external function for causing the component inspection units 116 a and 116 b to inspect the state of the component sucked by the heads 112 a and 112 b. Log output () is an external function for outputting a log to a specified log file. Further, for example, stop (), error content display (), return to origin (), and the like are external functions that perform processing when an error occurs in component mounting processing.

  Further, in FIG. 11, the control program generated by the development support program calls the log output (), which is an external function, every time the state of the heads 112a and 112b changes. That is, each time the state of the heads 112a and 112b transitions, the control program outputs a log indicating the operation results of the heads 112a and 112b to the log file. The log file is arbitrarily designated by the user.

  Furthermore, the development support program has a function of creating a test scenario based on a log output by the control program generated by itself and performing a test execution of the control program along the created test scenario. The operation of the development support program will be described with reference to FIGS. FIG. 12 is a flowchart showing the operation of the development support program.

  First, the development support program acquires a log from the log file output by the control program generated by itself (S11). The log according to the present embodiment includes, for example, the state of the drive unit (heads 112a and 112b in this example) on the state transition table and the head 112a as the drive unit at the time of processing executed immediately before log output. , 112b operation result (corresponding to “result (normal end or abnormal end)” described later), information specifying the next state of the heads 112a, 112b (corresponding to “state ID” described later), The operation time (corresponding to “processing time” described later) of the heads 112a and 112b in the state is described.

  Specifically, the control program is incorporated into the head control unit 153, and the heads 112a and 112b of the component mounter 100 are operated. As a result, the control program outputs a log for each state of the heads 112a and 112b to a log file designated by the user. FIG. 13 is a diagram illustrating an example of a log written in the log file.

  The content of the log output by the control program is not particularly limited. For example, as illustrated in FIG. 13, “log No”, “log output time”, “state ID”, “event ID”, “processing”, “ What is necessary is just to output "result", "processing time", "power consumption", etc.

  Log No. is information (identifier) for identifying each log in the log file. The log output time is the time when the log is output. The state ID is state information that identifies a transition destination state that has undergone a state transition due to the operation of the heads 112a and 112b during log output. The event ID is information indicating an event that occurred immediately before log output. The process is information indicating the contents of the process executed immediately before the log output, and is the name of the called external function in this example. The result (result of the operation of the drive unit) indicates whether the processing of the called external function has ended normally (OK) or abnormally ends (NG).

  The processing time indicates the time required for processing by the called external function. That is, it indicates the time from when the component mounting process () calls an external function until the external function returns a return value (the time until control returns to the calling function). In the example of FIG. 13, the processing time is clearly shown. However, the present invention is not limited to this. For example, the result obtained by subtracting the “log output time” of two consecutive logs is the processing time (operation time). ).

  Next, with reference to FIG. 12, the development support program designs a test scenario using the log acquired in step S11 (S12). In step S12, a test scenario is created in which the states of the heads 112a and 112b are changed in the order described in the log. Further, in this test scenario, when the control program test is executed, each instruction of the control program corresponding to each operation of the heads 112a and 112b is executed in accordance with the operation time (processing time) described in the log. Created.

  This test scenario is a combination of a global variable setting value and the processing time and return value of an external function corresponding to the global variable setting value. Specifically, the test sequence No. 1 is that each external function called when the global variable cnt is set to “3” executes processing over the processing time (0.5 sec) in the left column, and the return value of the external function in the right column "0" is returned.

  Next, the development support program performs a test execution of the component mounting process object in accordance with the test scenario created in step S12 (S13). With reference to FIGS. 11, 14, and 15, a process for executing a test of a component mounting process object will be described.

  First, as shown in FIG. 14, “3” is set to the initial value of the global variable cnt when the component mounting process object is called.

  Next, when the component feeder position movement (), which is an external function, is called, the development support program acquires the return value “0” of the external function corresponding to the global variable cnt = 3 from the test scenario in FIG. After 0.5 (sec) of time, the variable result is set (S21). Similarly, the development support program calls the component adsorption () and component adsorption recognition (), which are external functions, and sets “0” as the return value of the external function in the variable result after the predetermined processing time has elapsed (S 22). , S23).

  Note that the processing time at the time of test execution is used as a delay time from when the external function is called until the return value of the external function is returned. That is, the development support program returns a return value after delaying the processing time after calling the external function.

  Next, when the mounting of the first mounting component is completed, that is, when the state is “component mounting complete” and the “component mounting complete” event occurs, the value of the global variable cnt is decremented (S24). Next, since the global variable cnt = 2 at this time (No in S24), the processing from step S21 to step S24 is repeated twice more. When the global variable cnt = 0 (Yes in S24), the heads 112a and 112b are returned to the origin (S25), and the test execution of the component mounting process object is completed.

  In this way, by setting the values defined in the test scenario created based on the log output from the component mounter 100 when executing the test of the component mounting process object, the component mounting process object A situation in which the heads 112a and 112b are actually operated by being incorporated in the head controller 153 can be reproduced.

  In addition, the development support program according to the present embodiment generates a source code from the state transition table, generates an object from the source code, and creates a test scenario from a log output from the object incorporated in the component mounter 100. The object can be tested again according to this test scenario. That is, it is possible to perform cooperation from development to testing on one tool.

  Note that the development support program causes the display unit 15 of the computer 10 to display the display screen shown in FIG. 16 when the component mounting process object is tested. FIG. 16 is a diagram illustrating a display example of the display unit during the test execution.

  The display screen of FIG. 16 is divided into a processing summary display area A, a state transition table display area B, an H / W simulator display area C, and a three-dimensional drawing display area D. In the process overview display area A, an overview of processes in the component mounter 100 (operating rate for each lane, number of mounted points, etc.) is displayed. In the state transition table display area B, the state transition table of the component mounting object is displayed. In the H / W simulator display area C, a button for switching a signal output from a hardware such as a sensor to the control program is displayed. In the three-dimensional drawing display area D, a three-dimensional drawing of the component mounter 100 created by 3D-CAD or the like is displayed.

  Then, each time each instruction of the component mounting process object is test-executed, the development support program displays the current state on the state transition table corresponding to the instruction on the state transition table displayed in the state transition table display area B. The position (in this example, cell (4)) and the trajectory on the state transition table up to the current position (in this example, cells (1) to (3)) are displayed.

  The display example of the current position and the trajectory is not particularly limited, but may be displayed on the state transition table, for example, by changing or highlighting the background color of the cell corresponding to the current position and the cell on the trajectory. Or you may display as a separate item from a state transition table. For example, as a display example of the current position, the component suction recognition () cell is highlighted (shaded) (see the ID position “(event ID, state ID) = (3, 3)” in FIG. 16). ) And “current position: 3, 3)” may be displayed below the state transition table. In addition, as an example of displaying the trajectory up to the current position, each cell of component feeder movement (), component suction (), and component suction recognition position movement () is highlighted (shaded differently from the current position). At the same time, as a display representing the trajectory up to the current ID position below the state transition table, the history of “(event ID, state ID)” is “trajectory up to the current position: (0, 0) → (1,1) → (2,2) ”may be displayed.

  In addition, as the trajectory on the state transition table, the state of the drive unit in the state transition table at the time of processing executed immediately before log output, the state of the transition destination after the state transition by the operation of the drive unit at the time of log output, etc. Two states before and after the transition may be displayed. Thereby, the locus of the state transition before and after the state transition at the time of log output can be clarified.

  That is, the user who has seen the state transition table display area B in FIG. 16 is performing a test execution of the process corresponding to the current cell (4) through the states corresponding to the cells (1) to (3). Can be grasped at a glance. This is effective even when each process ends normally, but is particularly effective for identifying the cause when the process ends abnormally.

  In addition, the development support program links the heads 112a and 112b of the component mounter 100 displayed in the three-dimensional drawing display area D in conjunction with the test execution of the component mounting process object. Move it as if it were operating in response to the command.

  Specifically, the development support program processes the heads 112a and 112b on the three-dimensional drawing display area D from the initial position to the position of the component feeder in accordance with the call of the component feeder position movement () that is an external function. Move over time 0.5 sec. Then, at the timing when the heads 112a and 112b on the three-dimensional drawing display area D reach the position of the component feeder, that is, at the timing when the processing time 0.5 (sec) has elapsed after calling the component feeder position movement (), A return value “0” defined in the test scenario is set in a variable “result”.

  Here, the actual heads 112a and 112b do not move at a constant speed from the initial position to the position of the component feeder, but accelerate from a state stopped at the initial position and move at a constant speed for a certain period of time. Then, it decelerates and stops at the position of the parts feeder. Therefore, the development support program moves the heads 112a and 112b on the three-dimensional drawing display area D while accelerating / decelerating according to the acceleration / deceleration curve of the motor that drives the heads 112a and 112b.

  Thereby, the movement of the heads 112a and 112b on the three-dimensional drawing display area D becomes very close to the movement of the actual heads 112a and 112b mounted on the component mounter 100. As a result, for example, it is possible to reproduce on the computer a trouble that occurs at a delicate timing in the operation between a plurality of driving units or the operation of the driving unit alone, such as two heads 112a and 112b colliding with each other. Become.

  In the above-described embodiment, examples of the heads 112a and 112b have been described as drive units. However, the present invention is not limited to this, and the present invention can be applied to other drive units of the component mounter 100.

  In the above embodiment, an example of the component mounting machine 100 has been described as a mounting board manufacturing apparatus. However, the present invention is not limited to this, and the present invention is used for manufacturing a mounting board such as a printing machine or a printing inspection machine. Can be applied to any device.

(Other embodiments)
Specifically, the computer 10 is a computer system including a microprocessor, a ROM, a RAM, a hard disk unit, a display unit, a keyboard, a mouse, and the like. A computer program is recorded in the RAM or hard disk unit. The computer 10 achieves its functions by the microprocessor operating according to the computer program.

  Here, the computer program is configured by combining a plurality of instruction codes indicating instructions for the computer in order to achieve a predetermined function. Each device is not limited to a computer system including all of a microprocessor, a ROM, a RAM, a hard disk unit, a display unit, a keyboard, a mouse, and the like, and may be a computer system including a part of them. .

  A part or all of the components constituting the computer 10 may be configured by one system LSI (Large Scale Integration). The system LSI is an ultra-multifunctional LSI manufactured by integrating a plurality of components on a single chip, and specifically, a computer system including a microprocessor, ROM, RAM, and the like. . A computer program is recorded in the RAM. The system LSI achieves its functions by the microprocessor operating according to the computer program. In addition, each part of the constituent elements constituting the computer 10 may be individually made into one chip, or may be made into one chip so as to include a part or all of them. Although the system LSI is used here, it may be called IC, LSI, super LSI, or ultra LSI depending on the degree of integration. Further, the method of circuit integration is not limited to LSI's, and implementation using dedicated circuitry or general purpose processors is also possible. An FPGA (Field Programmable Gate Array) that can be programmed after manufacturing the LSI or a reconfigurable processor that can reconfigure the connection and setting of circuit cells inside the LSI may be used. Further, if integrated circuit technology comes out to replace LSI's as a result of the advancement of semiconductor technology or a derivative other technology, it is naturally also possible to carry out function block integration using this technology. Biotechnology can be applied.

  The method shown above may be sufficient as this invention. Moreover, the computer program which implement | achieves these methods with a computer may be sufficient, and the digital signal which consists of a computer program may be sufficient. The present invention also relates to a computer-readable recording medium capable of reading a computer program or a digital signal, such as a flexible disk, hard disk, CD-ROM, MO, DVD, DVD-ROM, DVD-RAM, BD (Blu-ray Disc), It may be recorded on a semiconductor memory or the like. Moreover, the digital signal currently recorded on these recording media may be sufficient. Further, the present invention may transmit a computer program or a digital signal via an electric communication line, a wireless or wired communication line, a network represented by the Internet, a data broadcast, or the like. The present invention may also be a computer system including a microprocessor and a memory, in which the memory stores the above computer program, and the microprocessor operates according to the computer program. The program or digital signal may be recorded on a recording medium and transferred, or the program or digital signal may be transferred via a network or the like, and may be implemented by another independent computer system.

  As mentioned above, although embodiment of this invention was described with reference to drawings, this invention is not limited to the thing of embodiment shown in figure. Various modifications and variations can be made to the illustrated embodiment within the same range or equivalent range as the present invention.

  The present invention is advantageously used in a development support method for supporting the development of a control program for controlling the operation of the drive unit of the mounting board manufacturing apparatus.

10 Computer 11 CPU
12 ROM
13 RAM
DESCRIPTION OF SYMBOLS 14 Input part 15 Display part 20 Board | substrate 100 Component mounting machine 110a, 110b Mounting unit 112a, 112b Head 114 Component cassette 115a, 115b Component supply part 116a, 116b Component inspection part 121a, 121b Beam 122a, 122b Substrate conveyance rail 130 Carriage entrance 140 Beam drive robot 151 Input unit 152 Display unit 153 Head control unit 154,540 Control unit 155 Communication unit 156 Storage unit 156a NC data 156b Parts library 156c Mounting condition data 200 Controller 424 Carrier tape 424a Storage recess 425 Cover tape 426 Reel 1000 Parts Mounting system

Claims (5)

A development support method for supporting development of a control program for controlling the operation of a drive unit of a mounting board manufacturing apparatus by a computer,
The control program is executed by the drive unit for each of a state of the drive unit, an event generated as a result of processing executed outside the control program, and a combination of the state of the drive unit and the event. And the next state of the driving unit are generated based on a defined state transition table, and each time the state of the driving unit transitions, the result of the operation of the driving unit and the driving unit A log in which information specifying the next state is described is output to a log file.
The development support method is:
A log acquisition step of reading from the log file the log output by the control program incorporated in the mounting board manufacturing apparatus;
A test scenario creating step for creating a test scenario that causes the state of the driving unit to transition in the order described in the log obtained in the log obtaining step;
A test execution step of performing a test execution of the control program in accordance with the test scenario created in the test scenario creation step. The log further describes the operation time of the drive unit in each state on the state transition table,
In the test scenario creating step, the control program instruction corresponding to each operation of the drive unit is matched with the operation time of the drive unit described in the log at the time of the test execution of the control program in the test execution step. The test scenario is created so that
In the test execution step, the drive unit on the three-dimensional drawing of the mounting board manufacturing apparatus displayed on the display screen is moved so as to perform an operation corresponding to a command of the control program to be tested. The development support method according to Item 1. In the test execution step, the driving unit on the three-dimensional drawing displayed on the display screen is operated according to an acceleration / deceleration curve of the driving unit so that the operation is completed in the operation time of the driving unit described in the log. The development support method according to claim 2. In the development support method, each time each instruction of the control program is test-executed in the test execution step, the current position on the state transition table corresponding to the instruction and the current position until the current position are reached. The development support method according to claim 1, further comprising an output step of outputting a locus on the state transition table. The program which makes a computer perform the development assistance method of any one of Claims 1-4.