JP2001092691A - Program execution history managing device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a program execution history managing device for efficiently operating trouble processing by easily specifying the cause of the failure of a control program. SOLUTION: At the time of controlling an object to be controlled by executing a control program constituted of plural functions, each module and the identification codes of the functions of the control program are stored in a data storing part 4, and when the control program is executed, each module and the identification codes of the functions are time-sequentially stored as execution history data in a history storing part 5 into the order of execution. Thus, the execution history data can be outputted by a display part 9 or a printing part 10 as necessary when any failure is generated, and trouble processing can be efficiently operated by easily specifying any cause when the failure is generated.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a program execution history management device for managing an execution history in the execution of a control program composed of a plurality of functions used in an FA device or the like.

[0002]

2. Description of the Related Art Factory Automation (FA)
In the device, the operation control is generally implemented by a computer, and the operation and processing of each unit of the device are performed by executing a control program of the computer. The control program is stored in a storage device in a form of a module for each function. When the control program is executed, necessary modules are sequentially called and executed according to an instruction of the program indicating a processing order.

[0003]

However, if a trouble occurs due to some trouble in the control program, such as an operation error, during the execution of the control program, the relationship between the trouble and the trouble in the control program in the past is considered. There was no clear way to specify, and in order to identify a defect in a control program that caused the trouble, the trouble had to be first reproduced as a phenomenon. And even when it is specified that a certain module has a defect, the common module is often called and executed in a plurality of control flows in the execution of the entire control program. It is difficult to check whether a program failure has occurred, and there is a problem that trouble handling requires time and effort.

SUMMARY OF THE INVENTION It is therefore an object of the present invention to provide a program execution history management device which makes it easy to identify the cause of a failure in a control program and can efficiently handle a trouble.

[0005]

A program execution history management device according to the present invention is a program execution history management device for managing an execution history in the execution of a control program composed of a plurality of functions. An identification data storage unit that stores identification data to be specified, a history storage unit that stores execution history data indicating the order in which the functions are executed in chronological order using the identification data, and a stored execution history data. Output means for outputting.

According to the present invention, the execution history data indicating the execution order of the functions constituting the control processing program is stored in time series using the identification data of the functions, and the execution history data is output as necessary. By doing so, when a failure occurs, the cause of the failure can be specified based on the execution history.

[0007]

Embodiments of the present invention will now be described with reference to the drawings. FIG. 1 is a functional block diagram showing processing functions of a program execution history management device according to an embodiment of the present invention, FIG. 2 is a functional block diagram showing processing functions of the program execution history output device, and FIG. It is a figure showing a hierarchical structure.

First, the function of the program execution history management device will be described. The program execution history management device is used by being incorporated in a control device that controls the operation of the FA device, such as an electronic component mounting device, and has a program execution history management function. Here, the program execution history refers to the execution history of the control program during the operation of the controlled device, that is, data indicating the order in which the functions constituting the control program are executed in chronological order. This means that the execution history data is stored in a storage device so that it can be output in a predetermined data format when necessary.

Next, the module configuration and functions of a control program to be managed in execution history will be described by taking a control program for controlling the operation of an electronic component mounting apparatus as an example. As shown in FIG. 3, the control program is composed of tasks indicated by layers A and B and modules of layers C and D for realizing these tasks.

A main task A1, which is one of the higher-level tasks belonging to the hierarchy A, is a task that plays a major role as an electronic component mounting apparatus. To perform the main task A1, a hierarchy B showing a more specific task operation is performed. , Such as a mounting task B1 for performing a mounting operation for mounting a chip on a substrate.

The execution of the mounting task B1 requires execution of a module of a control program for controlling an individual operation in the mounting operation, that is, a module belonging to the hierarchy C. The module of the layer C is a program for controlling the operation of each mechanism unit in the mounting apparatus, such as a substrate table module (a module for controlling the operation of a table for mounting and positioning a substrate) C1. is there.

The execution of the module of the hierarchy C
Further, execution of a module belonging to the hierarchy D is required. The module of the hierarchy D is an individual module for the purpose of controlling element devices such as actuators and sensors constituting the mechanism unit of the hierarchy C. For example, to execute the substrate table module C1, a motor or a table driving the substrate table is required. It is necessary to execute an individual module for controlling the position detecting sensor. Each individual module controls a control target such as each actuator or sensor via each control board interface.

Here, functions constituting the control program will be described. The function refers to a unit having a predetermined processing function in executing the control program. The functions exist in the modules of each layer of the above-described control program. Generally, one function is a functional element of another function, and a higher-level function is configured by a plurality of functions.
In some cases, the same function belongs to a plurality of higher-level functions. In this case, the same function is called and executed a plurality of times while the control program is sequentially executed.

Next, the processing function of the program execution history management device will be described with reference to FIG. In FIG.
The control target 1 is an element device constituting hardware of the electronic component mounting apparatus, that is, an actuator such as a motor, a sensor, or the like, and is controlled by an individual module of the hierarchy D via an interface. The control processing execution unit 2 uses C
It is a PU and controls the operation of the control target 1.

A control program storage unit 3 and a data storage unit 4 are connected to the control processing execution unit 2. The control processing program storage unit 3 stores a control program for controlling the operation of the electronic component mounting apparatus, and the data storage unit 4 stores various data necessary for control. The control processing execution unit 2
In accordance with the control program stored in the control program storage unit 3, the control target is controlled using various data stored in the data storage unit 4, and the execution history of each function constituting the control program is stored in the history storage unit 5. Output. Further, an input for operation is performed from the operation unit 8 to the control processing execution unit 2.

The history storage unit 5 stores the execution history data output by the control processing execution unit 2. Here, each function is provided with an identification code as identification data for individually specifying the number of each building, that is, a unique number for each function using a machine language, and these identification codes are stored in the data storage unit 4. Is stored in Therefore, the data storage unit 4 is an identification data storage unit that stores identification data for individually specifying functions.

When this identification code is stored as execution history data, it is stored in the history storage unit 5 in the form of a combination of the identification code indicating the module that called this function and the identification code of this function. Therefore, even when a common function is called and executed by a plurality of modules by referring to the execution history data,
The execution history of each function in the execution of the control program can be specified.

A storage area of a predetermined capacity is set in the history storage unit 5, and when execution history data is stored, data is stored in the order of addresses. Then, when the storage area is filled, data is stored again by overwriting from the first address. That is, the history storage unit 5
Always stores a certain amount of execution history data retroactively from the latest data, and when outputting the stored data to the outside, it similarly outputs retroactively from the latest data.
By using such a storage mode, the limited memory capacity can be effectively used. The execution history data stored in the history storage unit 5 is stored in a non-volatile memory. As a result, even when the power of the mounting apparatus is turned off for some reason, the execution history data is stored without disappearing.

The program name conversion processing unit 6 performs a process of converting an identification code in the execution history data stored in the history storage unit 5 into a program name. Here, the identification code of each module or function expressed in a machine language is converted into a program name using a general character which can be read by an operator. The output processing unit 7 performs data processing for outputting the execution history data stored in the history storage unit 5. This output is performed by sending a command to the output processing unit 7 by the control processing execution unit 2 or by direct operation input from the operation unit 8 to the output processing unit 7.

The output processing unit 7 is connected to a display unit 9, a printing unit 10, and an electronic mail unit 11. The display unit 9 is a display device, and displays an operation display screen and execution history data stored in the history storage unit 5 and output-processed by the output processing unit 7. The printing unit 10 is a printer device, and prints out execution history data. The e-mail unit 11 outputs the execution history data similarly output-processed via the communication network. The display unit 9, the printing unit 10, and the e-mail unit 11 are output units that output the stored execution history data.

Here, the output form of the execution history data includes:
Two types are set depending on the application. One is a form (data format a) in which the identification code in the machine language stored in the history storage unit 5 is output as it is. Another form is a form (data format b) in which the program name is converted to a readable general character and converted by the program name conversion processing unit 6.

The output format in the data format a is an output format in a case where it is not necessary for the operator to directly determine the data format. For example, when the data is transferred to another device via the communication network by the electronic mail means 11 or when the external storage medium Floppy (registered trademark) disk 13
It is used when recording on a storage medium such as.

The output format of the data format b is an output format for the direct purpose of visual interpretation by an operator.
For example, it is used when displayed on a display by the display unit 9 or when printed out by the printing unit 10. In the case of direct display or printout on a display device of another device, the data may be recorded in a data format b on a floppy disk 13 or the like via the external storage medium recording means 12, or the electronic mail means 11 may be used. The data may be transmitted in the data format b.

This program history management device is configured as described above, and the process of storing execution history data will be described below. When the mounting operation is started by activating the electronic component mounting apparatus, the control processing execution unit 2 performs electronic control based on the control program stored in the control program storage unit 3 and the data stored in the data storage unit 4. The control target 1 of the component mounting apparatus is controlled. During the execution of the control program, the execution history in which each function constituting the control program is called and executed is stored in the history storage unit 5.

The storage processing of the execution history data is performed full-time during the operation of the control target device. If the data storage is performed by a normal method, a huge data capacity is required. Therefore, when storing data, the memory capacity for storing execution history data is limited to a predetermined amount as described above, and the following handling is performed.

In executing a program, the same function may be called and executed successively. In such a case, the function names after the second time are excluded from the stored data or are not stored. This is because, in execution history management, it is not necessary to leave duplicate data when execution is performed continuously.

Since the storage of the execution history data is performed mainly for the purpose of processing when a trouble occurs in the control program, the following functions are provided so that appropriate execution history data can be stored. It has become.

When a trouble occurs, it is often necessary to first reset the program and then restart it as a measure. Even when the program is reset and restarted, the execution history data at the time of occurrence of the trouble remains unchanged. Must be saved. For this reason, a storage necessity selection unit 14 is provided for setting whether to capture execution history data even at the time of starting the program, that is, whether to store the name of the executed function. By this selection, when a trouble occurs, new acquisition of the execution history data is not performed until the restart is completed, that is, the execution history data already stored in the history storage unit 5 is not overwritten with the execution history data at the time of occurrence of the trouble. I do. Thus, it is possible to prevent the execution history data at the time of occurrence of the trouble from being erased by the program reset.

Further, the following functions are provided to make it easier to determine the cause of the trouble. That is, a timing identification mark can be added to the execution history data so that the function executed at a certain timing can be specified. Usually, in the work of investigating the cause at the time of occurrence of a trouble, phenomena such as abnormal operation of each part of the electronic component mounting apparatus are observed from the outside. At this time, a program executed at a specific timing at the time of observation is performed. Module and function can be specified.

That is, by inputting a predetermined signal from the operation unit 8, the control processing execution unit 2 adds a timing identification mark when outputting the execution history data, and outputs the execution history data to the history storage unit 5. This makes it possible to directly associate the phenomenon that occurred at a specific timing during observation with the module or function that was being executed at that timing, making it easy to find the cause at the time of trouble.

The execution history data stored in this way is output as needed. In other words, if there is any problem in the control program and it is necessary to specify the cause of the problem, the operation input from the operation unit 8 causes the execution history data stored in the history storage unit 5 to be output. At this time, by instructing the program name conversion, the function name or module name is converted into a program name using general characters that can be read by an operator and displayed on the display of the display unit 9 or printed out by the printing unit 10. Can be done. Then, by analyzing the execution history data, it is possible to compare the state of the occurrence of the failure with the module or function that was being executed at that time, so that the cause of the failure can be easily specified. The execution history data is transferred by the electronic mail means 11 via a communication network as needed.

Next, a program execution history output device will be described with reference to FIG. This output device is used when it is necessary to output execution history data at a location remote from the device from which the execution history is collected. In FIG. 2, the external storage medium reading unit 20 is a disk drive device that reads data from an external storage medium such as the floppy disk 13,
In FIG. 1, the execution history data written on the floppy disk 13 by the external storage medium storage means 12 is read.

The read execution history data is converted by the program name conversion processing section 21 into a program name that can be read by an operator. The converted data is displayed on the display of the display unit 23 or printed out by the printing unit 24. The execution history data received by the e-mail unit 22 via the communication network is similarly stored in the program name conversion processing unit 2.
1 and processed similarly.

As described above, by outputting the execution history data at a remote location, even if a specialized engineer who is familiar with the contents of the control program is not resident near a device to be controlled such as an electronic component mounting device. , It is possible to cope in various forms. For example, by transferring only the execution history data to the manufacturer of the apparatus and requesting a specialist to analyze the data contents, it is possible to easily clarify the cause of the trouble.

As described above, according to the present invention, the execution history data indicating the execution order at the time of execution of the control program is stored using the identification data for individually specifying the functions constituting the control program. Sometimes, the data is output in a predetermined data format. With this, when a trouble occurs, it is possible to clearly identify which function of the control program is executed in which control flow and the trouble occurs,
Investigation of the cause at the time of trouble is facilitated, and trouble processing can be efficiently performed.

[0036]

According to the present invention, the execution history data indicating the order in which the functions constituting the control processing program are actually executed are stored in time series using the identification data of the functions.
Since execution history data is output as needed, when a problem occurs, the function related to the occurrence of the problem can be specified based on the execution history. It can be carried out.

[Brief description of the drawings]

FIG. 1 is a functional block diagram showing processing functions of a program execution history management device according to an embodiment of the present invention.

FIG. 2 is a functional block diagram showing processing functions of the program execution history output device according to the embodiment of the present invention;

FIG. 3 is a diagram showing a hierarchical structure of a control program according to the embodiment of the present invention;

[Explanation of symbols]

 DESCRIPTION OF SYMBOLS 1 Control object 2 Control processing execution part 3 Control program storage part 4 Data storage part 5 History storage part 6 Program name conversion processing part 7 Output processing part 9 Display part 10 Printing part 11 E-mail means

Claims (1)

[Claims] 1. A program execution history management device for managing an execution history in execution of a control program composed of a plurality of functions, comprising: an identification data storage unit for storing identification data for individually specifying the functions; A program comprising: a history storage unit that stores execution history data indicating the order in which functions are executed in time series using the identification data; and an output unit that outputs the stored execution history data. Execution history management device.