JP6578028B2 - Model editing unit, model editing method, program, and storage medium - Google Patents

Description

Embodiments described herein relate generally to a model editing unit, a model editing method , a program, and a storage medium.

  In order to improve productivity and quality in a processing system, a tool capable of adding production information to various data detected by the processing system has been developed. When such a tool is applied to an actual processing system, it is necessary to create a program according to the configuration of the processing system, production information to be added, and the like. In order to implement the tool in a shorter time, it is desirable that the time required for creating the program is short.

Japanese Patent No. 5110733

The problem to be solved by the present invention is to provide a model editing unit, a model editing method , a program, and a storage medium that enable creation of a program according to the configuration of a processing system and production information to be added in a shorter time. It is to be.

The model editing unit according to the embodiment includes a reading unit and an editing unit. The reading unit reads a definition file having software component information. The software component includes a plurality of first processors that collect data of different detection units provided in the processing system as events, and a first that holds the events collected by at least one of the plurality of first processors. A queue, and a plurality of second processors that add different production information to the event held in the first queue and output a processing event. One of the plurality of second processors has a plurality of states, a transition between the plurality of states, an action, when the event indicating the input of a work to the processing system is held in the first queue. , Generate an ID as the production information, and add it to the state machine. The editing unit displays the software part corresponding to the information in the definition file and an editing area. In the editing area, at least one of the plurality of first processors and the first queue are connected, and a model is constructed by connecting the first queue and at least one of the plurality of second processors. Make it possible.

It is a block diagram showing the structure of the assistance system which concerns on embodiment. It is a flowchart showing operation | movement of the assistance system which concerns on embodiment. It is a schematic diagram which illustrates GUI displayed by an edit part. It is a schematic diagram which illustrates GUI displayed by an edit part. It is a schematic diagram which illustrates GUI displayed by an edit part. It is a schematic diagram which illustrates GUI displayed by an edit part. It is a schematic diagram which illustrates GUI displayed by an edit part. It is a schematic diagram which illustrates GUI displayed by an edit part. It is a functional block diagram for demonstrating operation | movement of the model illustrated in FIG. It is a mimetic diagram showing processing of an actual work, and processing of a virtual work. It is a state machine diagram showing an example of a virtual work. It is a graph showing an example of operation | movement of a manufacturing apparatus, and the state of the virtual workpiece | work according to it.

Embodiments of the present invention will be described below with reference to the drawings.
In the present specification and each drawing, the same elements as those already described are denoted by the same reference numerals, and detailed description thereof will be omitted as appropriate.

FIG. 1 is a block diagram illustrating a configuration of a support system according to the embodiment.
The support system 1 according to the embodiment is used, for example, to construct a model (data collection flow) representing a data collection flow in the processing system PS. The support system 1 is also used to generate a program corresponding to the constructed data collection flow and collect data of the processing system PS.

  As illustrated in FIG. 1, the support system 1 according to the embodiment includes a model editing unit 10, a data collection unit 20, a first storage unit 31, a second storage unit 32, and a third storage unit 33.

  The model editing unit 10 is used when the user of the support system 1 constructs a data collection flow. The data collection unit 20 generates a program corresponding to the data collection flow constructed by the model editing unit 10. Then, the data collection unit 20 drives the program and collects data of the processing system PS.

  The first storage unit 31 stores plug-ins. The plug-in is an additional program for extending the software function of the data collection unit 20. The second storage unit 32 stores a definition file used when the model editing unit 10 edits a model. This definition file includes information corresponding to the plug-in setting items stored in the first storage unit 31.

More specifically, the model editing unit 10 includes a reading unit 11, an editing unit 12, and an output unit 13.
The reading unit 11 reads the definition file stored in the second storage unit 32.
The editing unit 12 displays a graphical user interface (GUI) on the display based on the read definition file. In the GUI, a list of icons representing software components corresponding to plug-ins, an editing area for arranging icons to build a model, a detailed setting screen for software components, and the like are displayed. The user can construct a model on the GUI displayed by the editing unit 12.
The output unit 13 outputs a setting file corresponding to the constructed model in a format readable by the data collection unit 20 and stores the setting file in the third storage unit 33.

The data collection unit 20 includes a generation unit 21 and a drive unit 22.
The generation unit 21 reads the setting file stored in the third storage unit 33 and the plug-in stored in the first storage unit 31. Then, the generation unit 21 generates a program corresponding to the setting file and the plug-in.
The drive unit 22 drives the program generated by the generation unit 21 and collects data of the processing system PS along the program.

In the example illustrated in FIG. 1, the data collection unit 20 further includes a determination unit 23 and a notification unit 24.
The determination unit 23 reads the setting file and the definition file stored in the second storage unit 32. The definition file in the second storage unit 32 includes the grammar definition of the setting file. The determination unit 23 determines whether the description of the text in the setting file is appropriate based on the grammar definition of the definition file.

When there is an error in the setting file, the determination unit 23 outputs the determination result to the notification unit 24. When the notification unit 24 receives the determination result from the determination unit 23, the notification unit 24 issues a notification to the user. For example, the notification is made by light emission from a light emitting unit provided in the support system 1 or generation of sound from a speaker. Alternatively, the notification unit 24 may notify by recording in a log or transmitting information to a previously registered terminal.
If there is no error in the setting file, the determination unit 23 outputs the setting file to the generation unit 21. The subsequent operation in the generation unit 21 is as described above.

  In the support system 1, for example, the model editing unit 10, the data collection unit 20, the first storage unit 31, the second storage unit 32, and the third storage unit 33 are connected to each other by wire or wirelessly. These may be connected to each other via a network. Alternatively, the first storage unit 31 may be incorporated in the data collection unit 20 and the second storage unit 32 may be incorporated in the model editing unit 10. Further, when the setting file is directly transmitted from the model editing unit 10 to the data collection unit 20, the support system 1 may not include the third storage unit.

  For example, when the format of the setting file is XML (eXtensible Markup Language), the format of the definition file is XSD (XML Schema Definition) or XML. Alternatively, the format of the setting file and the definition file may be JSON (JavaScript (registered trademark) Object Notation). The format of the plug-in can be changed as appropriate according to the data collection unit 20. As an example, the plug-in format is DLL (Dynamic Link Library).

The operation of the support system 1 described above will be described with reference to FIG.
FIG. 2 is a flowchart showing the operation of the support system according to the embodiment.

  First, the reading unit 11 reads a definition file (step S1). The editing unit 12 displays a GUI based on the definition file (step S2). When a model is constructed on the GUI by the user, the output unit 13 outputs a setting file corresponding to the model (step S3).

  The determination unit 23 reads the definition file and the setting file, and determines whether there is an error in the syntax of the setting file (step S4). If there is an error, the notification unit 24 issues a notification (step S5). If there is no error, the generation unit 21 reads the setting file and the plug-in and generates a program (step S6). The drive unit 22 drives the generated program (step S7).

Next, an example of a GUI displayed by the editing unit 12 will be described with reference to FIGS.
3 to 5 are schematic views illustrating GUIs displayed by the editing unit.

  For example, as shown in FIG. 3A, the user can open a list of software parts (“Parts pallet”) on the GUI. In the example of FIG. 3A, two queues 41a and 41b ("queue1" and "queue2") and nine processors 42a to 42i ("Processor1" to "Processor9") are displayed. These software components are based on plug-in setting items included in the definition file. In other words, software components corresponding to plug-ins are displayed as icons on the GUI.

  In the processing system PS, for example, a plurality of detection units are provided. The detection unit is a sensor that detects an object such as a proximity sensor or a photoelectric sensor, a camera that detects the movement of the robot, a reader that reads a barcode, and the like.

  In the support system 1, for example, all data of the detection unit in the processing system is handled in units of “events”. For example, the event includes the event occurrence time, the event ID, and other production information.

  For the software component displayed in FIG. 3A, the processor processes the event, and the queue holds the event.

More specifically, the processors are classified into a first processor, a second processor, and a third processor.
When the first processor receives data from a specific detection unit installed in the processing system, the first processor generates an event. For example, when it is detected by a sensor or a barcode reader that a workpiece has been input to the processing system, the first processor generates an event according to the detection data.
The second processor processes the generated event and outputs a processing event. For example, the second processor adds production information to the event and outputs it as a processing event. The production information includes, for example, at least one of a work ID, a lot ID, an ID of the processing system PS, an ID of an operator in charge of the processing system PS, an ID of a process performed in the processing system PS, and the like.
The third processor outputs an event to the outside such as an external database or an FTP server.

  The queue buffers events on memory (RAM) or a database. A queue is connected between the processors, and events are input / output through the queue. That is, the event output from the first processor or the second processor is held by the queue, and is pulled out by the third processor or another second processor.

  Queues may have other functions than simply holding events. For example, the queue may be provided with a function of sorting a plurality of events in the order of occurrence time of each event.

  These software component icons are arranged on the editing area 43 as shown in FIG. 3B, for example, by drag and drop. The arranged icons can be connected by a directed line 44. A directed line 44 represents the flow of events between the processor and the queue. A plurality of processors and one queue may be connected by a directed line 44, and one processor and a plurality of queues may be connected by a directed line 44.

  Further, by double-clicking a processor or queue arranged in the editing area 43, a detailed setting screen for the processor or queue can be opened as shown in FIG. In the example shown in FIG. 4, each of the items 45a to 45c can be set. When expanding more detailed setting items for each item, it is possible to set details by drilling down from that item, for example.

  FIG. 5 schematically shows a detailed setting screen for a processor or a queue. For example, as shown in FIG. 5A, a mark 45m indicating that drill down is possible is added to the item 45c. By clicking this mark 45m, the screen shown in FIG. 5B showing the items 45e to 45g in the lower hierarchy is displayed for the item 45c. For example, the mark 45m is attached to the item 45g. By clicking this mark 45m, the screen shown in FIG. 5C showing the data of the lower hierarchy is displayed for the item 45g. In order to display the data of the upper hierarchy after drilling down, for example, the mark 45n is clicked.

  In this way, a data collection flow can be constructed by repeating the arrangement of icons (processors and queues) in the editing area 43, connection between icons, and detailed setting of processors and queues.

The effect of the embodiment will be described.
As described above, in the model editing unit 10 according to the embodiment, the editing unit 12 displays the software component and the editing area 43 on the GUI. In the editing area 43, the user can construct a model by connecting at least one of the plurality of first processors and a queue, and connecting the queue and at least one of the plurality of second processors. Therefore, a program model for adding production information to the data of the detection unit can be easily constructed.

  In addition, the first processor used for the model can be selected as appropriate according to the type and number of detection units provided in the applied processing system PS. The second processor used for the model can be appropriately selected according to the production information to be added. Thereby, a model corresponding to the configuration of the processing system and desired production information can be easily constructed. Further, it is not necessary to directly edit the program driven by the data collection unit 20 according to the configuration of the processing system and desired production information. Therefore, by using the constructed model, a program necessary for driving the data collection unit 20 can be easily obtained in a shorter time.

  In the editing area 43, a third processor and a second queue are further arranged, and the second processor and the third processor are connected via the second queue. At this time, a model can be constructed according to a desired data output method by selecting at least one from a plurality of third processors to be output to the outside by different methods.

When only the first processor and the second processor are used and the third processor is not used, the event data is not output to the outside. However, even in this case, for example, it is possible to control the operation of the processing system based on the event output from the second processor. For example, the second processor performs an input operation to the processing system PS in accordance with the event held in the first queue. That is, it is possible to substitute an event output from the second processor for an input using a keyboard, a mouse, a touch panel, a button, or the like performed by a person on the processing system PS. Thereby, at least a part of the operation of the processing system PS can be automated.

  Alternatively, only the first processor and the third processor may be used, and the second processor may not be used. In this case, production information is not added to the event, and the data is output to the outside as it is. Even in this case, since the event includes an occurrence time and an ID, information can be added to the data of the detection unit.

  In the support system 1, the data collection unit 20 reads a plug-in file and generates a program. By adding necessary functions by plug-ins, it is not necessary to reconstruct software according to the configuration of the processing system PS.

  Further, the definition file used in the model editing unit 10 has information corresponding to the setting items of the plug-in. Thereby, the setting file output from the model editing unit 10 can also correspond to the plug-in. In this way, it is not necessary to edit the contents of the setting file according to the plug-in, and the setting file can be directly read by the data collection unit 20 to generate a program. Further, by making the definition file correspond to the plug-in, it is not necessary to customize the model editing unit 10 according to the plug-in.

  Also, the software unit corresponding to the plug-in is displayed on the GUI by the editing unit 12, and the detailed setting of each software component can be edited, so that a model corresponding to the specific configuration of the processing system is constructed. it can.

  Preferably, in order to improve the usability of the model editing unit 10, an annotation 47 is displayed on the detailed setting screen as shown in FIG. The annotation 47 explains each setting item. By displaying the annotation 47, the user can easily understand the meaning of each setting item.

  Such information on the annotation 47 is included in the definition file. When the reading unit 11 reads the definition file, the reading unit 11 also reads information on the annotation 47, and the editing unit 12 displays the annotation 47 on the detailed setting screen.

  The format of the setting file output from the model editing unit 10 corresponds to the format of the definition file in the second storage unit 32, and the definition file includes a grammar definition of the format. In the support system 1 according to the embodiment, the data collection unit 20 is provided with a determination unit 23 that reads the setting file and the definition file and determines whether there is an error in the syntax of the setting file. By providing the determination unit 23, when there is an error in the setting file, it is possible to notify the user, and it is possible to cause the generation unit 21 to read only a normal setting file.

(Example)
Below, the construction method of the specific data collection flow using the support system 1 which concerns on embodiment is demonstrated.
FIG. 6 is a schematic view illustrating a GUI displayed by the editing unit.
In the example shown in FIG. 6, “MemoryEventQueue” (queue 41a), “OrderedMemoryEventQueue” (queue 41b), “SQLEventQueue” (queue 41c), “BarcodeReaderProcessor” (processor 42a), “SensorInputProcessor” (processor 42b) are used as software components. ”,“ FtpOutputProcessor ”(processor 42c),“ GridDbOutputProcessor ”(processor 42d),“ AnalogTrimProcessor ”(processor 42e), and“ BasicStateMachineProcessor ”(processor 42f).

  The queue 41a represents a queue for buffering events on a memory (RAM). The queue 41b represents a queue having a function of sorting events in time order. The queue 41c represents a queue for buffering events on the database.

  The processor 42a represents a processor that converts the input of the barcode reader into an event. The processor 42b represents a processor that converts the sensor input provided in the processing system into an event. The processor 42c represents a processor that transmits an event in a CSV file format to an FTP (File Transfer Protocol) server. The processor 42d represents a processor that outputs an event to the GridDB. The processor 42e represents a processor that associates an ID with an analog event in a range surrounded by start / end events. The processor 42f represents a processor that executes arbitrary logic defined by the user by driving the state transition model.

  In the example shown in FIG. 6, a plurality of queues 41 (queues 41a0 to 41a3), a processor 42a, a processor 42b, a plurality of processors 42c (processors 42c1 and 42c2), a processor 42e, and a processor 42f are arranged in the editing area 43. The model has been built.

  For example, in this model, when a work is input to the processing system, the processor 42a outputs an event when the ID of the work is read by a barcode reader. The output event is held in the queue 41a0.

  The processing system is provided with a plurality of sensors. For example, a sensor that detects the passage of a workpiece in the processing system, a sensor that detects the unloading of the workpiece from the processing system, a sensor that detects conditions (temperature, pressure, gas flow rate, etc.) during workpiece processing, and the like are provided. When there is an input from these sensors, the processor 42b outputs an event.

  As an example, the workpiece loading / unloading / passing detection signal is transmitted as digital data, and the conditions for processing the workpiece are transmitted as analog data. The processor 42b sends a digital data event to the queue 41a0 and sends an analog data event to the queue 41a2.

  When the processor 42f receives an event corresponding to the input of a work to the processing system, the processor 42f generates a state machine. At the same time, the processor 42f issues and assigns an ID to each state machine. Further, when the processor 42f receives an event indicating the passage of a work in the processing system, the processor 42f drives the state machine. When the processor 42f receives an event corresponding to the unloading of a work from the processing system, the processor 42f extinguishes the state machine and the history is held in the queue 41a1 as an event. The state machine has an action of transmitting an event toward the queue 41a1 in accordance with the state transition. This event includes an ID given to the state machine that issued the event.

  The timing of generation and disappearance of the state machine in the processor 42e and the behavior of the state machine are set based on the state machine model file and the definition file.

  When an event is transmitted from the state machine to the queue 41a2, the processor 42e cuts out a part of the waveform data being processed by the processor 42b. The processor 42e further associates a part of the extracted waveform data with the ID included in the event transmitted from the state machine. Those data are held in the queue 41a3.

  The processors 42c1 and 42c2 respectively transmit the event held in the queue 41a1 and the event held in the queue 41a3 to the FTP server in the CSV format.

  Note that, like the processor 42b in the above-described example, the model editing unit 10 according to the embodiment can specifically set events output from the processor to each queue. A method of setting an event output from the processor to the queue will be described with reference to FIGS.

7 and 8 are schematic views illustrating GUIs displayed by the editing unit.
In FIG. 7A, the processor 42b is arranged in the editing area 43, and the detailed setting screen of the processor 42b is opened. For example, in this detailed setting screen, an item 45h for setting an event drain is displayed. Here, the event drain means an output terminal from which an event is output.

  By clicking on the mark 45m for drilling down the item 45h, as shown in FIG. 7B, a detailed screen for adding an event drain is opened. In the screen shown in FIG. 7B, the event drain of the processor 42b can be added by clicking the mark 45o. Thereby, for example, as shown in FIG. 8A, a plurality of event drains can be added. For example, all the events are set to be output from the default event drain existing when the processor is arranged on the editing area 43.

  When an event drain is added, as shown in FIG. 8A, items 45i1 and 45i2 for setting an event output from each event drain are displayed. For example, when the mark 45m of the item 45i1 is clicked and drilled down, as shown in FIG. 8B, an item 45j for inputting an event output from the event drain is displayed.

  By inputting the event ID in the item 45j, the event output from the added first event drain is specified. When a plurality of event IDs are set for one event drain, the item 45j can be increased by clicking the mark 45о. Further, the ID input to the item 45j may be described using a regular expression as shown in FIG. Thereby, a plurality of event IDs can be specified by setting one item. Similarly, an event to be output can be designated for the second event drain.

  After setting the event drain, by connecting the event drain and the queue in the editing area 43, it can be set to output only the specific event to the specific queue.

FIG. 9 is a functional block diagram for explaining the operation of the model illustrated in FIG.
As shown in FIG. 9, the model constructed on the GUI of FIG. 6 includes a BCR data receiving unit 61, a serial data receiving unit 62, an input event data list 63, an input process data list 64, and a state machine driving unit. 65, a data collection flow 2 including a state machine list 66, a setting file reading unit 67, a linking unit 68, an output event data list 69, an output process data list 70, an event data output unit 71, and a process data output unit 72 Corresponding to

  For example, the processing units PS that collect data include detection units A to C. As an example, the detection unit A is a barcode reader. The detection unit B is a sensor that detects the loading and unloading of the workpiece into the processing system and the passage of the workpiece in the processing system. The detection unit C is a sensor that detects conditions (temperature, pressure, gas flow rate, etc.) in a processing chamber provided in the processing system.

  The BCR data receiving unit 61 corresponds to the processor 42a. The BCR data receiving unit 61 collects data transmitted from the detecting unit A as an event and stores it in the input event data list 63. The serial data receiving unit 62 corresponds to the processor 42b. The serial data receiving unit 62 receives data transmitted from the detection units B and C by serial communication.

  The input event data list 63 corresponds to the queue 41a0. The input process data list 64 corresponds to the queue 41a2. The serial data receiving unit 62 analyzes the received data, stores events in the input event data list 63, and stores waveform data (analog events) in the input process data list 64.

  The state machine driving unit 65, the state machine list 66, and the setting file reading unit 67 correspond to the processor 42f.

  The state machine list 66 holds the state machine when the state machine is generated. The state machine is generated as a model corresponding to a work when an event indicating the input of the work to the processing system is stored in the input event data list 63. A state machine includes multiple states, transitions between multiple states, and actions. These states, transitions, and actions are set according to the actual work movement in the processing system. In addition, an ID is issued and assigned to the state machine. The generated state machine behaves as a virtual work. That is, in accordance with the input of work to the processing system, a state machine is generated as a virtual work to which an ID is assigned corresponding to each work. The state machine list 66 keeps holding each state machine until the state machine disappears.

  The state machine drive unit 65 drives the state machines held in the state machine list 66 in accordance with the input event data list 63. For example, when the workpiece loaded into the processing chamber is detected by the detection unit B of the processing system, the state machine driving unit 65 drives the state machine corresponding to the workpiece, so that the state machine is in the loader. Transition to a state in the processing chamber.

  In the example shown in FIG. 9, the state machine list 66 holds another state machine that functions as the virtual loader 66a. When an event indicating input of a workpiece is stored in the input event data list 63, the state machine driving unit 65 drives the virtual loader 66a. Thereby, a state machine as a virtual work is generated in accordance with the input of the work to the processing system.

  The setting file reading unit 67 reads a model file of the state machine from an external storage unit. The model file includes a state machine reception event list and a state list for the state machine as the virtual loader 66a and the state machine as the virtual work. The state list includes states that can be taken by the state machine. The received event list includes an event that causes a transition between the states included in the state list. In addition to this, the model file also includes an action such as transmission of a secondary event and a guard condition for performing a transition condition determination.

  For example, the state machine driving unit 65 executes actions for writing the input history, writing the OK payout history, writing the NG payout history, starting the waveform cutout, and ending the waveform cutout according to the event stored in the input event data list 63. To do.

  The input history includes a record indicating that the work has been input to the processing system. The OK payout history includes a record indicating that the work has been normally discharged from the processing system. The NG payout history includes a record indicating that the work has been paid out as an abnormality from the processing system. For example, when an abnormality is found in the workpiece in the inspection of the workpiece in the processing system, the workpiece is paid out as an abnormality.

  Cutout start and cutout are actions for transmitting an event for cutting out waveform data. When these actions are executed, an event is transmitted to the input process data list 64. Hereinafter, an event transmitted by an action of a state machine is referred to as a “secondary event”. The secondary event is accompanied by the ID of the state machine that transmitted the secondary event.

  The output event data list 69 corresponds to the queue 42a1. When the input history writing, OK history writing, or NG history writing action is executed, the history is written to the output event data list 69.

  When the secondary event is held in the input process data list 64, the associating unit 68 cuts out a part of the waveform data held in the input process data list 64. The associating unit 68 associates the extracted waveform data with the ID attached to the secondary event. Thereby, the state machine and the waveform data are associated with a common ID.

  As a specific example, when a workpiece is put into a certain processing chamber, the state machine enters a corresponding state accordingly. At this time, the action “start cutting” is executed by the state machine, and a secondary event is transmitted.

  For example, in the processing chamber, the pressure is detected every predetermined time. That is, waveform data representing a change in pressure with respect to time is held in the input process data list 64. When the secondary event is transmitted by the action of “start cutting”, the linking unit 68 starts cutting the waveform data.

  When the processing of the workpiece is completed and the workpiece is paid out from the processing chamber, the state machine exits from the corresponding state accordingly. At this time, the state machine executes an action of “end cutting” and transmits a secondary event. When this secondary event is transmitted, the associating unit 68 ends the clipping of the waveform data.

  The output process data list 70 corresponds to the queue 42a3. The associating unit 68 associates the ID of the state machine with the extracted waveform data, and transmits it to the output process data list 70.

  The event data output unit 71 and the process data output unit 72 correspond to the processors 42c1 and 42c2, respectively. The event data output unit 71 and the process data output unit 72 refer to the output event data list 69 and the output process data list 70, respectively, and transmit the stored data to the FTP server in the CSV format.

A specific example of the operation of the data collection flow 2 will be described with reference to FIGS. 10 and 11.
FIG. 10A is a schematic diagram illustrating an example of actual workpiece processing. FIG. 10B is a schematic diagram showing processing of a virtual work corresponding to FIG.
FIG. 11 is a state machine diagram illustrating an example of a virtual work.
Note that the state machine diagram of FIG. 11 is created by the Unified Modeling Language (UML).

  The state machine diagram shown in FIG. 11 includes six states S10 to S15. State S10 is an initial state, and state S15 is a terminal state. A state name is described in the upper part of each of the states S11 to S14. Arrows between states represent transitions and their directions. An arrow may be attached with “event / [guard condition] / action”. Any of the event, the guard condition, and the action can be omitted as appropriate. In the example illustrated in FIG. 11, characters attached to the arrows represent events. In the lower part of states S11 and S12, action execution conditions are described. For example, “entry / ID numbering” in the state S11 indicates that an action for issuing an ID is set when entering the state S11.

  Hereinafter, as shown in FIG. 10A, a workpiece processed in an actual manufacturing apparatus is referred to as “real workpiece”, and a state machine illustrated in FIG. 10B is referred to as “virtual workpiece”.

  The detection unit B1 detects an actual work put into the loader. This detection signal is collected as a work input event by the BCR data receiving unit 61 (processor 42a). The virtual loader 66a in the state machine list 66 generates a virtual work when a work input event is generated.

  As illustrated in FIG. 11, when the work input event is generated, the virtual work changes from the initial state S10 to the state S11 arranged in the loader. When entering the state S11, an action for issuing an ID is executed. Thereby, ID is provided to the virtual work.

  The actual workpiece paid out from the loader is put into the processing chamber. The detection part B2 detects the actual workpiece put into the processing chamber. The BCR data receiving unit 61 (processor 42a) collects this detection signal as an input event to the processing chamber. In response to the processing chamber input event, the state machine driving unit 65 causes the virtual workpiece to transition from the state S11 disposed in the loader to the state S12 disposed in the processing chamber.

  When entering the state S12, a secondary event for starting to cut out the waveform is transmitted by the action of the virtual work. In response to this secondary event, the associating unit 68 starts to cut out the detection result (waveform data) by the detecting unit C provided in the processing chamber.

  The actual work is paid out from the processing chamber when the processing is completed. The detection unit B3 detects an actual workpiece that is paid out from the processing chamber. For example, the BCR data receiving unit 61 collects this detection signal as a payout event from the processing chamber. In response to the processing chamber payout event, the state machine driving unit 65 changes the virtual workpiece from the state S12 arranged in the processing chamber to the state S13 arranged in the inspection chamber. At this time, a secondary event for ending the clipping of the waveform is transmitted by the action of the virtual work. In response to this secondary event, the associating unit 68 ends the clipping of the waveform data.

  These secondary events are accompanied by virtual work IDs. The associating unit 68 associates the ID of the virtual work with the extracted waveform data.

  The work determined as non-defective in the inspection room is transferred to the unloader. The work determined as defective is transported to a container for collecting the defective. At this time, the detection unit B4 detects the workpiece on the path along which the non-defective product is conveyed. The detection unit B5 detects a workpiece on a path along which a defective product is conveyed.

  When the detection unit B4 detects an actual work, the serial data reception unit 62 (processor 42b) collects this detection signal as an inspection OK event. In response to the inspection OK event, the state machine driving unit 65 changes the virtual work from the state S13 arranged in the inspection room to the state S14 arranged in the unloader.

  On the other hand, when the detection unit B6 detects an actual workpiece, the serial data reception unit 62 collects this detection signal as an inspection NG event. In response to the inspection NG event, the state machine driving unit 65 causes the virtual work to transition from the state S13 arranged in the inspection room to the terminal state S15.

  The detection unit B5 detects a workpiece paid out from the unloader. The serial data receiving unit 622 collects this detection signal as a work payout event from the manufacturing apparatus. In response to the work payout event, the state machine drive unit 65 causes the virtual work to transition from the state S14 arranged in the unloader to the terminal state S15.

  The state machine that has transitioned to the terminal state S15 disappears. The disappeared state machine is deleted from the state machine list 66. At this time, information such as the process from the initial state S10 to the terminal state S15, the ID assigned to the state machine, and the waveform data associated with the ID is output to the outside.

Here, the above-described example will be described more specifically with reference to FIG.
FIG. 12 is a graph showing an example of the operation of the manufacturing apparatus and the state of the virtual work corresponding thereto.

In FIG. 12, mainly from the upper stage, the workpiece passing event collected by the serial data receiving unit 62, the waveform data of the process in the processing room, the history of the state transition of the virtual workpiece, the waveform of the process after the ID is linked. Data.
In addition, regarding the waveform data after the ID association, the portion where the association is performed is represented by a solid line, and the portion which is not associated is represented by a broken line.

At time t _1, work on event has been generated. At this time, the first virtual work is generated, and the virtual work changes to the state S11.
In time t _2, the the processing chamber on event is generated, the virtual workpiece is shifted to a state S12. At this time, extraction of pressure data in the processing chamber is started.
At time t _3, when the processing chamber payout event is generated, the virtual workpiece is shifted to a state S13. At this time, extraction of the pressure data in the processing chamber is completed.
Waveform data between the time t ₂ to time t ₃ is cut out, attached ID and string of the first workpiece.

At time _{t 4,} the inspection OK event is generated, the virtual workpiece is shifted to a state S14.
At time t _5, when the workpiece payout event is generated, the virtual work transitions to state S15 (terminal state), disappears.

  Similarly for the second and subsequent workpieces, the state transitions according to the generation of each event. Along with the state transition, a part of the waveform data is cut out and associated with the ID of each virtual work.

  In the example shown in FIG. 12, an inspection NG event is generated for the third work, and the state transitions from the state S13 to the terminal state S15. For this reason, the state S14 is not included in the history of the third virtual work.

  In this way, by generating a virtual work with production information (ID) added and changing the state in accordance with the movement of the real work, the production process data is added to the actual work process data. It becomes possible to collect.

For example, in the above-described example, when the detection units A to C are replaced with different ones or the data acquired by the detection units A to C is changed, the BCR data reception unit 61 to which they are input Also, the function of the serial data receiving unit 62 needs to be changed. However, according to the support system 1 according to the embodiment, a data collection flow applicable to the processing system PS after the change can be constructed by rearranging the first processor in response to those changes on the editing area 43. .
Further, even when the production information to be added to the data of the detection unit changes, a data collection flow capable of adding desired production information can be constructed by rearranging the second processor in response to the change.
In addition, if you want to change the data output method or the format of the data to be output, the data collection flow that can output the desired output method and data format is constructed by reconfiguring the third processor in response to the change. it can.

  The operation logic of the second processor can be defined by an arbitrary method such as a flowchart. More preferably, the logic of the second processor is defined using a state machine as in the above-described embodiment. By using the state machine, the operation of the second processor can be more easily modeled.

  The state machine can also be applied to cases other than the case where production information is added to an event by the second processor as in the embodiment. For example, the action of the state machine can be set to transmit an input operation (control signal) to the processing system PS in accordance with the state transition.

In the support system 1 described above, the model editing unit 10 is configured by, for example, a computer including a CPU and a memory. The program storage unit of the computer stores a program for causing the computer to function as the reading unit 11, the editing unit 12, the output unit 13, and the like.
The data collection unit 20 is constituted by a monitoring control unit. A program for causing the unit to function as the generation unit 21, the drive unit 22, the determination unit 23, the notification unit 24, and the like is stored in the program storage unit of this unit.

  By using the model editing unit, the model editing method, and the support system according to the embodiment described above, various data collection flows can be easily constructed. Similarly, it is possible to easily construct various data collection flows by using a program for operating a computer as a model editing unit or a support system.

  As mentioned above, although several embodiment of this invention was illustrated, these embodiment is shown as an example and is not intending limiting the range of invention. These novel embodiments can be implemented in various other forms, and various omissions, replacements, changes, and the like can be made without departing from the spirit of the invention. These embodiments and modifications thereof are included in the scope and gist of the invention, and are included in the invention described in the claims and equivalents thereof. Further, the above-described embodiments can be implemented in combination with each other.

  DESCRIPTION OF SYMBOLS 1 Support system, 2 Data collection flow, 10 Model editing unit, 11 Reading part, 12 Editing part, 13 Output part, 20 Data collection unit, 21 Generation part, 22 Drive part, 23 Determination part, 24 Notification part, 31 1st Storage unit, 32 second storage unit, 33 third storage unit, 41a-41c, 41a1-41a4 queue, 42a-42f processor, 43 editing area, 44 directed line, 45a-45c, 45e-45g item, 45m, 45n Mark, 47 Annotation, 61 BCR data receiver, 62 Serial data receiver, 63 Event data list for input, 64 Process data list for input, 65 State machine driver, 66 State machine list, 66a Virtual loader, 67 Load configuration file Part, 68 tying part, 69 out Event data list for power, 70 process data list for output, 71 event data output unit, 72 process data output unit, A, B, B1-B6, C detection unit

Claims (13)

A plurality of first processors each collecting data of different detection units provided in the processing system as events;
A first queue for holding at least one said event which is collected by the plurality of first processors,
A plurality of second processors that add different production information to the event held in the first queue and output a processing event, wherein one of the plurality of second processors is sent to the processing system. When the event indicating the input of the workpiece is held in the first queue , a state machine including a plurality of states, transitions between the plurality of states, and an action is generated, and an ID is used as the production information. A plurality of second processors that issue and add to the state machine;
A reading unit for reading a definition file having information on software parts including
The software component corresponding to the information of the definition file and an editing area are displayed, and in the editing area, at least one of the plurality of first processors and the first queue are connected, and the first queue and the An editing unit that allows a model to be constructed by being connected to at least one of a plurality of second processors;
Model editing unit with In the definition file, the software component includes a second queue and a plurality of third processors,
The second queue holds the processing event output from at least one of the plurality of second processors,
2. The model editing unit according to claim 1, wherein the plurality of third processors output the processing events held in the second queue to the outside in different ways. An output unit;
The model editing unit according to claim 1, wherein the output unit outputs the constructed model as a setting file that can be read by a data collection unit that collects data of the processing system. One of the plurality of first processors collects waveform data in a processing system as the event;
2. The model editing unit according to claim 1, wherein another one of the plurality of second processors cuts out a part of the waveform data and associates it with the ID. A plurality of first processors each collecting data of different detection units provided in the processing system as events;
A first queue holding the events collected by at least one of the plurality of first processors;
A plurality of second processors that add different production information to the event held in the first queue and output a processing event, wherein one of the plurality of second processors is sent to the processing system. When the event indicating the input of the workpiece is held in the first queue , a state machine including a plurality of states, transitions between the plurality of states, and an action is generated, and an ID is used as the production information. A plurality of second processors that issue and add to the state machine;
The definition file with the information of software components, including, Mase write reading the reading portion of the model editing unit,
The software component corresponding to the information in the definition file and an editing area are displayed on the editing unit of the model editing unit, and in the editing area, the user can select at least one of the plurality of first processors and the first area. A model editing method, wherein a model is constructed by connecting one queue and connecting the first queue and at least one of the plurality of second processors. In the definition file, the software component includes a second queue and a plurality of third processors,
The second queue holds the processing event output from at least one of the plurality of second processors,
6. The model editing method according to claim 5, wherein the plurality of third processors output the processing events held in the second queue to the outside in different ways. The constructed the model, as readable configuration file in the data collection unit for collecting data of the processing system, the model editing method according to claim 5 or 6 Ru is output to the output portion of the model editing unit. One of the plurality of first processors collects waveform data in a processing system as the event;
The model editing method according to claim 5, wherein another one of the plurality of second processors cuts out a part of the waveform data and associates it with the ID. On the computer,
A plurality of first processors each collecting data of different detection units provided in the processing system as events;
A first queue holding the events collected by at least one of the plurality of first processors;
A plurality of second processors that add different production information to the event held in the first queue and output a processing event, wherein one of the plurality of second processors is sent to the processing system. When the event indicating the input of the workpiece is held in the first queue , a state machine including a plurality of states, transitions between the plurality of states, and an action is generated, and an ID is used as the production information. A plurality of second processors that issue and add to the state machine;
Read the definition file that contains the software component information including
The software component corresponding to the information of the definition file and an editing area are displayed, and in the editing area, at least one of the plurality of first processors and the first queue are connected, and the first queue And at least one of the plurality of second processors are connected to each other so that a model can be constructed. In the definition file, the software component includes a second queue and a plurality of third processors,
The second queue holds the processing event output from at least one of the plurality of second processors,
The program according to claim 9, wherein the plurality of third processors output the processing events held in the second queue to the outside in different ways.   The program according to claim 9 or 10, which causes the computer to output the constructed model as a setting file that can be read by a data collection unit that collects data of the processing system. One of the plurality of first processors collects waveform data in a processing system as the event;
The program according to claim 9, wherein another one of the plurality of second processors cuts out a part of the waveform data and associates it with the ID.   The storage medium which memorize | stored the program as described in any one of Claims 9-12.

Images