JPH11282515A - Programmable controller and recording medium - Google Patents

Abstract

(57) [Summary] [PROBLEMS] To enable debugging of an application program even when an unmounted module exists. SOLUTION: An application program developed in a loader 2 is sent to a program execution unit 10b via an interface 10a. The loader 2 also stores the configuration information indicating the modules supported by the program and the module mounting information indicating the current module mounting status in the programmable controller 10.
To supply. The program execution suspending unit 10c attempts to suspend the execution of the program because the module 5-2 is not mounted. However, the program execution suspending operation suspending unit 10e stores the module implementation information input from the module implementation information input unit 10d. Since it is indicated that this module has not been mounted, the operation of the program execution stopping means 10c is suspended. Input / output management means 1
0f manages data input / output from the interface 10g, and stops input / output of data to / from the unmounted module 5-2.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

BACKGROUND OF THE INVENTION 1. Field of the Invention The present invention relates to a programmable controller, and more particularly, to a programmable controller for controlling a module to be controlled in accordance with a program supplied from a loader, and showing a configuration of a module set in the loader. The present invention relates to a programmable controller having a program execution stopping means for stopping execution of a program when information does not match the mounting state of a module.

[0002]

2. Description of the Related Art A programmable controller (PC: Proglamable) characterized in that control specifications can be easily changed.
Controllers) have come to be used in numerous sites, driven by their lower prices and higher performance.

[0003] Generally, a programmable controller is, like a personal computer, a CPU, an RO, and the like.
It comprises an M, a RAM, an interface, and the like, and controls a group of modules to be controlled according to an application program supplied from a support tool called a loader.

FIG. 8 is a diagram showing a configuration example of a control system including a conventional programmable controller. In this figure, a programmable controller 1 includes a CPU,
It is configured by a ROM, a RAM, an interface, and the like, and controls the modules 5-1 to 5-n according to an application program supplied from the loader 2.

[0005] The loader 2 is constituted by, for example, a personal computer or the like, and supports development of an application program to be executed in the programmable controller 1 and debugging of the developed application program.

[0006] The bus 3 is, for example, a serial bus.
The application program created in the loader 2 is transmitted to the programmable controller 1, and the operation status of the programmable controller 1 is transmitted to the loader 2.

The bus 4 is connected to the programmable controller 1
And modules 5-1 to 5-n are interconnected, and data can be input / output between them. Module 5-1
Reference numeral 5-n denotes a device that directly controls the control target, and is configured by, for example, a digital input / output, an analog input / output, and a communication device.

[0008] Such a programmable controller 1
When executing the application program supplied from the loader 2 in the
Executes a process of checking whether all modules are normal.

FIG. 9 is a flowchart illustrating an example of such a check process. When this processing is started, the following processing is executed. [S1] The programmable controller acquires configuration information indicating the configuration of the module from the loader 2.

[0010] The configuration information is information as shown in FIG. 10, and includes the station number (address) of each IO port of the module group connected to the programmable controller 1 and the port size (number of bits). Stored.

For example, the first information 7-1 is related to the module 5-1 and its station number is "1" and its port size is 1 bit. [S2] The programmable controller accesses the module corresponding to the module information described in the configuration information to determine whether or not the module is mounted. As a result, if the module is mounted, the process proceeds to step S3; otherwise, the process proceeds to step S4. [S3] The programmable controller determines whether an unconfirmed module exists by referring to the configuration information. If an unconfirmed module exists, the process returns to step S2; otherwise, the programmable controller performs processing. finish. [S4] The programmable controller stops executing the application program.

With the above processing, for example, if any module has a problem, the operation of the application program can be stopped in advance.

[0013]

By the way, when debugging an application program, when not all the modules are available, sometimes it is necessary to confirm the operation of only the existing module.

In such a case, it is determined that the module does not exist by the processing in step S2, and the execution of the application program is stopped. Therefore, there is a problem that the application program cannot be debugged when all the modules are not prepared.

The present invention has been made in view of such a point, and an object of the present invention is to provide a programmable controller capable of checking an application program even when there is an unmounted module.

[0016]

According to the present invention, there is provided a programmable controller for controlling a group of modules to be controlled in accordance with a program supplied from a loader. When the configuration information indicating the configuration of the module group does not match the mounting status of the module group, in a programmable controller having a program execution stop unit for stopping the execution of the program, the program is set in the loader. A module mounting information input unit for inputting module mounting information indicating a module group mounting status from the loader; and a case where the configuration information and the mounting status do not match, and the module corresponding to the module mounting information is not mounted. If it is shown that Program execution suspension operation suspension means for suspending the operation of the ram execution suspension means, and input / output management means for managing the input and output of information to and from the module indicated by the module implementation information as being unmounted. A programmable controller is provided.

Here, the module mounting information input means includes:
Module mounting information indicating the mounting status of the module group set in the loader is input from the loader. The program execution suspending operation suspending unit is configured to execute the program execution suspending unit when the configuration information does not match the implementation status and the module implementation information indicates that the corresponding module is not implemented. Suspend the operation. The input / output management unit manages input / output of information with respect to a module that is indicated as not mounted by the module mounting information.

[0018]

Embodiments of the present invention will be described below with reference to the drawings. FIG. 1 is a principle diagram for explaining the principle of the present invention. As shown in FIG. 1, the programmable controller 10 includes an interface 10a, a program execution unit 10b, a program execution suspension unit 10c, a module mounting information input unit 10d, a program execution suspension operation suspension unit 10e, an input / output management unit 10f, and an interface 10g.

The interface 10a inputs an application program created in the loader 2, module mounting information indicating a module mounting status, and the like, and outputs information indicating an internal state of the programmable controller 10 to the loader 2.

The program execution unit 10b executes the application program supplied from the loader 2 and controls the modules 5-1 to 5-n. The program execution stopping means 10c stops the operation of the program execution unit 10b when the configuration information supplied from the loader 2 does not match the module mounting status.

The module mounting information input means 10d is connected to the modules 5-1 to 5 through the interface 10a.
Input module mounting information indicating the mounting status of -n.
The module mounting information indicates the mounting status of each module by 1-bit information, and is input by a user from an input unit (not shown) of the loader 2 with reference to the mounting status of the module. When a certain module is mounted, the corresponding bit is set to “1”, and when not mounted, it is set to “0”.
Such information is added to the configuration information as shown in FIG. In this example, the module mounting information 2 is set as the least significant bit of the configuration information of each of the modules 20-1 to 20-n.
0-1a to 20-na are added.

Program execution suspension operation suspension means 10e
If the configuration information does not match the module mounting status, and if the module mounting information corresponding to the module that is not mounted is “0”, the operation of the program execution suspending unit 10 c On hold.

The input / output management means 10f manages data to be transmitted by the program execution unit 10b via the interface 10g. That is, the input / output management unit 10f
Stops input / output of data to / from a module not mounted in the program execution unit 10b.

Next, the operation of the above principle diagram will be described. Now, it is assumed that the module 5-2 has not been mounted. In this case, when the user inputs from the input unit (not shown) of the loader 2 that the module 5-2 is not mounted, the loader 2 sets the module mounting information 20-2a to "0" (see FIG. ) To the programmable controller 10.

Next, when the loader 2 supplies the application program to be executed (or debugged) to the programmable controller 10 and starts the program, the program execution stopping means 10c sets the interface 10g.
Is checked by checking the mounted module, and is compared with the configuration information supplied from the loader 2.

In the present example, since the module 5-2 has not been mounted, the configuration information does not match the mounting state, and the program execution stopping means 10c starts processing for stopping the execution of the application program. .

By the way, the program execution suspending operation suspending means 10e refers to the module mounting information input from the module mounting information input means 10d, and refers to the module 5-
Since the mounting information of No. 2 is "0", the operation of the program execution stopping means 10c is suspended. As a result, the application program is executed as usual.

When the application program is executed, the input / output management means 10f connects to the interface 10g.
Manages data input and output from the
The input / output of data to the unmounted module 0b is stopped. That is, when the program execution means 10b attempts to output predetermined data to the unmounted module 5-2, the output of data from the interface 10g to the module 5-2 is stopped. When data is to be input from the module 5-2, preset data is supplied to the program execution unit 10b.

As a result, even when the module 5-2 is not mounted, it is possible to debug other modules. When the module mounting information is not set to “0” and a failure occurs in the module, the program execution stopping unit 10c stops the operation of the program execution unit 10b.

Next, a configuration example of the embodiment of the present invention will be described with reference to FIG. In this figure, a programmable controller 30 includes a CPU 30a, a ROM 3
0b, a RAM 30c, an interface 30d, a buffer 30e, and an interface 30f.

The CPU 30a responds to the application program supplied from the loader 2 by
1 to 5-n are controlled. The ROM 30b stores a system program and the like. The RAM 30c is a CPU 3
When Oa performs various controls and arithmetic processing, it temporarily stores a program being executed, data being calculated, and the like.

The interface 30d mutually converts data formats when exchanging application programs with the loader 2. Buffer 30e
When the CPU 30a and the modules 5-1 to 5-n exchange data, the CPU 30a temporarily stores the data to absorb the difference in transmission speed, and stops input / output to an unmounted module. Used when performing processing.

The interface 30f converts data formats between the CPU 30a and the modules 5-1 to 5-n when exchanging data. The loader 2 is composed of, for example, a personal computer, and supports developing an application program to be executed in the programmable controller 1 and debugging the developed application program.

The bus 3 is, for example, a serial bus.
The application program created by the loader 2 is transmitted to the programmable controller 1, and the setting status and operation status of the programmable controller 1 are transmitted to the loader 2.

The bus 4 is connected to the programmable controller 1
And the modules 5-1 to 5-n are mutually connected, and data can be input / output between them. Module 5-1
Reference numeral 5-n denotes a device to be controlled, which includes, for example, a relay, a motor, an electromagnetic relay, an indicator, or a detector.

Next, the operation of the above embodiment will be described with reference to FIG. The flowchart shown in this figure is started when the application program is supplied to the programmable controller 30 and executed after the module mounting information is input to the loader 2.

When this flowchart is started, the following processing is executed. [S21] The CPU 30a acquires the configuration information shown in FIG. [S22] The CPU 30a extracts and inputs the module mounting information 20-1a to 20-na added to the configuration information. [S23] The CPU 30a refers to the information on the predetermined module included in the configuration information, checks the corresponding module via the interface 30f, and determines whether the module is mounted. As a result, when the module is mounted, the process proceeds to step S24, and otherwise, the process proceeds to step S25. [S24] The CPU 30a determines whether or not an unconfirmed module exists by referring to the configuration information. If an unconfirmed module exists, the process returns to step S23; otherwise, the process ends. I do. [S25] The CPU 30a refers to the module mounting information input in step S22, and determines whether or not the module determined not to be mounted in step S23 is set as an unmounted module (when the bit corresponding to the module is It is determined whether the state is “0” or not. If the state is “0”, S
The process proceeds to step S24, and otherwise proceeds to step S26. [S26] The CPU 30a stops execution of the application program and ends the processing.

According to the above processing, for example, even if the module 5-2 is not mounted, the module mounting information 2
By setting 0-2a to "0", the application program can be started.

Incidentally, since the application program input from the loader 2 also includes control for the module 5-2, when this application program is started, data is also input to the unmounted module 5-2. In this embodiment, the data is supplied to the interface 30f via the buffer 30e, and the input / output management application program manages the input / output data. Data is input / output to / from the module, and as a result, malfunction of the application program can be prevented.

That is, as shown in FIG. 5, in this embodiment, the application program 50 supplied from the loader 2 is a basic input output system (BIOS) 51.
Is temporarily stored in the buffer 30e.

FIG. 6 shows one mode of the division of the buffer 30e. As shown in this figure, the buffer 30e is divided into areas 60-1 to 60-n corresponding to each module, and each area is further subdivided into areas for storing input data and output data. (For example, area 6
0-1 is subdivided into an area 60-1a and an area 60-1b for storing input data). In addition, an area for storing input data of a module not mounted (in this example, an area 60-2a corresponding to the module 5-2).
, A value that does not hinder execution of the application program is set in advance by the loader 2.

The input / output management program 53 is stored in the ROM 30
b, the firmware stored in buffer 3
0e is supplied to the interface 30f, and the output data is stored in the interface 3f.
The input data input from 0f is written to a predetermined area of the buffer 30e.

The BIOS 51 reads input data from the buffer 30e and writes output data. The interface 30f outputs the data written by the input / output management program 53 to the corresponding module, and stores the data output from the module.

At this time, the input / output management program 5
Reference numeral 3 refers to the module mounting information, and if there is a module that is not mounted, stops writing output data corresponding to the module to the interface 30f. Also, writing of input data input from the interface 30f to the buffer 30e is stopped.

Therefore, when the module 5-2 is not mounted, the data written in the area 60-2b is not output to the interface 30f.
As described above, the predetermined value is written in the area 60-2a in advance, and the input / output management program 53 does not write the data input to the interface 30f in this area. The written data is read as data input from the module 5-2. As a result, it is possible to prevent data from being transmitted to the unmounted module 5-2 and to prevent indefinite data from being input as data from the module.

FIG. 7 is a view for explaining an example of a flowchart for realizing such processing. When this flowchart is started, the following processing is executed. [S41] The CPU 30a initializes a variable i to “1”. [S42] The CPU 30a acquires the ith module mounting information. [S43] The CPU 30a determines whether or not the i-th module mounting information is “0”, and as a result, “0”
If so, the process proceeds to step S46; otherwise, the process proceeds to step S44. [S44] The CPU 30a acquires the output data of the i-th module from the buffer 30e and supplies it to the interface 30f.

As a result, predetermined data is output to the i-th module. [S45] The CPU 30a acquires input data of the i-th module from the interface 30f, and writes the input data to the buffer 30e. [S46] The CPU 30a increments the value of the variable i by one. [S47] The CPU 30a determines whether or not there is an unprocessed module. As a result, if it is determined that there is no unprocessed module, the processing is terminated. Otherwise, the processing is performed. To end.

According to the above processing, the output of the data to the module not yet mounted is stopped, and the preset data is used as the input data from the module not mounted. . For example, if an unmounted module is a temperature detection module, and if a process that causes an emergency stop when the detected temperature exceeds a predetermined temperature (for example, 45 ° C.) is described in the application program, By setting a predetermined value (for example, 30 ° C.) lower than the detected temperature in the buffer 30e in advance, a malfunction occurs due to indefinite data read from an unmounted module, and the application program is stopped immediately. Can be prevented.

In the above embodiment, the data input / output from the interface 30f is stored in the buffer 30e.
And temporarily stops data input / output from unmounted modules by managing data input / output by the input / output management program 53. However, the present invention is not limited to this. is not.

For example, when the CPU 30a has a debugging function (for example, when an access is made to a designated input / output port, an interrupt process can be generated), for example, When an access is made to the input / output port, an interrupt process may be generated to stop input / output of data.

According to the above-described embodiment, even when there is an unmounted module, it is possible to verify the operation of the application program with respect to another mounted module.

When a failure occurs in a predetermined module, the execution of the application program is stopped as usual since the module mounting information is not set to "0".

The above processing functions can be realized by causing a programmable controller to execute a predetermined application program. In this case, the processing contents of the functions that the programmable controller should have are described in an application program recorded on a recording medium readable by the programmable controller, and the above processing is executed by executing the application program on the programmable controller. Is achieved. Recording media readable by the programmable controller include a magnetic recording device and a semiconductor memory.

For distribution to the market, a CD-ROM
(Compact Disk Read Only Memory) or an application program stored in a portable recording medium such as a floppy disk and distributed, or stored in a storage device of a computer connected via a network, and another programmable controller is connected through the network. Can also be forwarded to When the program is executed by the programmable controller, the application program may be stored in a hard disk device or the like in the programmable controller, loaded into the main memory, and executed.

[0055]

As described above, according to the present invention, by describing predetermined information in module mounting information, an application program can be started even when there is a module that is not mounted.

Since the input / output of data is stopped for a module that is not mounted, the operation of another module that is mounted can be confirmed.

[Brief description of the drawings]

FIG. 1 is a principle diagram illustrating the principle of the present invention.

FIG. 2 is a diagram showing configuration information and module mounting information.

FIG. 3 is a block diagram illustrating a configuration example of an embodiment of the present invention.

FIG. 4 is a flowchart illustrating an example of a process performed in the embodiment illustrated in FIG. 3;

FIG. 5 is a diagram showing a correspondence relationship among an application program, a BIOS, a buffer, an interface, and an input / output management program in the embodiment shown in FIG. 3;

FIG. 6 is a diagram showing one mode of division of a buffer area shown in FIG. 3;

FIG. 7 is a flowchart illustrating an example of a process performed in FIG. 3;

FIG. 8 is a block diagram illustrating a configuration example of a control system including a conventional programmable controller.

FIG. 9 is a flowchart illustrating an example of a process performed in the programmable controller illustrated in FIG. 8;

FIG. 10 is a diagram showing an example of configuration information used in the conventional example shown in FIG.

[Explanation of symbols]

 2 Loader 5-1 to 5-n Module 10 Programmable controller 10a Interface 10b Program execution unit 10c Program stop / stop unit 10d Module mounting information input unit 10e Program execution stop operation suspension unit 10f Input / output management unit 10g Interface

Claims (3)

[Claims] 1. A programmable controller for controlling a module group to be controlled according to a program supplied from a loader, comprising: configuration information indicating a configuration of the module group set in the loader; When the mounting status does not match, in a programmable controller having a program execution stopping means for stopping the execution of the program, module mounting information indicating the mounting status of the module group set in the loader is input from the loader. Module mounting information input means, and when the configuration information and the mounting status do not match,
In the case where the module mounting information indicates that the corresponding module is not mounted, a program execution suspending operation suspending unit that suspends the operation of the program execution suspending unit; Input / output management means for managing input / output of information to / from a module indicated to be present. 2. The method according to claim 1, wherein the input / output management unit stops outputting to the unmounted module and fixes data input from the unmounted module to a predetermined value. Item 4. The programmable controller according to Item 1. 3. A programmable controller for controlling a group of modules to be controlled in accordance with a program supplied from a loader, comprising: configuration information indicating a configuration of the module group set in the loader; If the mounting status does not match, on a recording medium recording a program to be executed by a programmable controller having a program execution stopping means for stopping the execution of the program, the mounting status of the module group set in the loader Module mounting information input means for inputting module mounting information from the loader, indicating that the configuration information does not match the mounting status,
When the module mounting information indicates that the corresponding module is not mounted, a program execution suspension operation suspending unit that suspends the operation of the program execution suspension unit; A recording medium that records a program that causes a programmable controller to function as an input / output management unit that manages input / output of information with respect to a module indicated to be.