JPH1011115A - Distributed type control device - Google Patents

Abstract

PROBLEM TO BE SOLVED: To make it impossible to simultaneously edit the same data on the same screen from plural consoles. SOLUTION: In the distributed type control, device for controlling a plant 3 by plural operator's consoles 11 to 1n , each console uses a common registered picture through an information LAN 2 and has a table for presenting the existence of reading/writing and priority in each data to be used for each picture, and when reading/writing data to be edited have been already registered by another console, the edition of the succeeding console is inhibited.

Description

DETAILED DESCRIPTION OF THE INVENTION

[0001]

[0001] 1. Field of the Invention [0002] The present invention relates to a distributed control device for monitoring and controlling a plant via an operation console having two-dimensional display means such as a CRT display, and more particularly to a data registration screen thereof.

[0002]

2. Description of the Related Art Generally, when monitoring and controlling a plant,
In many cases, distributed control is performed via a communication path from a plurality of operator consoles having two-dimensional display means such as a CRT display.

[0003]

In a distributed control device of this type, when data is to be edited on a plurality of consoles, the operator cannot know which data is being edited on consoles other than his / her own. for that reason,
The same data could be edited from multiple consoles at the same time, which could cause confusion.

The present invention has been made in view of the above problem, and provides a distributed control device which cannot edit the same data at the same time based on the editing status of another console. It is intended to be.

[0005]

A distributed control device according to the present invention monitors and controls a plant via a plurality of operator consoles each having two-dimensional display means. Each of them creates data on what data is used and in what state, so that other console screens can refer to each other.

When the data editing screen is activated, it refers to the data of the use status, checks whether necessary data is in use on the screen, and if it is in use, it cannot be edited according to the situation.

[0007]

DESCRIPTION OF THE PREFERRED EMBODIMENTS Hereinafter, the present invention will be described in more detail with reference to embodiments. FIG. 1 is a schematic block diagram showing a system configuration of a distributed control device according to an embodiment of the present invention. Here, a plurality of consoles 1 _-1, 1 _-2,
.., The plant 3 can be monitored and controlled via the control LAN 4 from 1 _-N .

[0008] required for system data (data that is necessary for display, such as a screen or panel), each of the console 1 _-1, 1 _-2, ... are held at 1 _-N. In this system, data can be edited via the information LAN ₂ from any of the consoles _1-1 , 1-2, ..., 1- _N . Data to be edited on the edit screen are a, b, c,
It is assumed that there are d, e,. Editing screens are A, B, C,
... and there are several things.

[0009] Here, an editing screen A (hereinafter referred to as "screen A") is activated on the console _1-1 . It is assumed that the editing screen has not been started in another console yet. Screen A handles data of a, b, and c. Of these, reading and writing are performed simultaneously for a, and only reading is performed for b and c. Each console is provided with data (hereinafter, referred to as "usage data") representing the use situation of each data. The content of the usage data is represented as follows.

Neither read nor write: 0 Performs only read: 1 Performs read and write: 2 Priority: Indicates the order in which data editing rights are obtained when a plurality of screens for editing the same data are activated. Items that are 1 can be edited.

Screen A confirms usage data at the time of startup. As shown in FIG. 2, in the initial state, the use state data is all 0, so the apparatus is started in a state where the data a can be edited. When activated, the screen writes the usage status data to the priority order for the status data a using the data. In this state, the data of the usage status is represented as shown in FIG. If usage data in the console 1 _-1 is created, all other consoles 1 _-2 ,, as shown in FIG. 5
, 1- _N through the information LAN ₂ , and as a result, the usage status data of all the consoles _1-1 , 1-2, ..., 1- _N is updated.

[0012] Consider the case to start a new editing screen B (hereinafter referred to as "screen B") in the console 1 _-2 this state. On screen B, data a, c, and d are handled. Data a,
c is for reading only, and data d is for reading and writing. When the screen B is activated, the current usage data is checked. As a result of the check, as shown in FIG. 3, it can be seen that the data a and c have already been used. It can also be seen that the data d is not used. Therefore, the screen B is started in a state where the data a and c are not edited, and the data d is not used by others, so that the data d can be edited. However, although there is a possibility that the content of the data a is changed on the screen A, there is no particular problem because it is only referred to. Eventually, the screen B is activated in a normal state. It is added that the data a, c, and d on the screen B are handled as described above to the usage status data.

[0013] In addition, consider the case where the editing screen C is launched from here in the console 1 _-3. Data to be handled are b, c,
d and e. Data b and c are read only, and data d and e are read and written.
When the usage status data is checked in the same manner as in the screens A and B, it is found that the data b, c, and d are already used, and the data e is not used. When comparing the way of using the data used here and the way of using the screen C, there is no problem since the data b and c are only read on the screen C. However, data d is read and written on both screen C and screen B. In such a case, if read / write is permitted on the screen C as it is, data is edited simultaneously on the two consoles. Therefore, on the screen C which is activated later and tries to read and write data which has already been used, it is necessary to perform a process of permitting only reference to the data d.
As shown in FIG. 4, the usage status data is written such that only the data d is read, and the priority order for the data d is written as 2. For the data e, readable and writable and the priority 1 are written. Therefore, the screen C can be performed only by the monitor for the data d. In this way, editing of the same data between consoles is prohibited at the same time, so that data discrepancies are eliminated.

The usage data in each console is updated every time the data editing screen is started or stopped when the data editing screen is started, and at regular intervals in addition to the above. The screen also periodically checks the usage data. If the usage data has not been updated, the data cannot be edited on the screen, even if there is a screen that can be edited.
In the above example, when the screen B is terminated when the screen C is activated, the data d is not read or written at that time.
As shown in FIG. 6, the screen B rewrites the usage data so that the data used by the user at the end is set to 0 and the priority is changed. This data is immediately distributed to all consoles. If the screen C does not confirm the usage data, the data d cannot be edited. However, if the screen C periodically checks the usage status data, it can be confirmed that the usage status and the priority are changing. The screen itself determines whether this change is related to the screen C, and d
By determining that is readable and writable,
The screen C changes to a state where d can be edited (see FIG. 7).
FIG. 8 is a flowchart showing an outline of the editing or monitoring process in each console described above.

As described above, the right to use data can be adjusted among the consoles, and the same data can be prohibited from being changed at the same time.

[0016]

According to the present invention, the data is prohibited from being edited depending on the situation, so that the same data is not edited at each console at the same time, so that it is not necessary to synchronize the data after editing. In addition, data becomes inconsistent for each console, and reediting to eliminate the inconsistency is eliminated.

Further, even when the consoles are arranged in isolation, it is not necessary for the operator to check the situation each time, and the editing work can be performed safely, so that unnecessary burdens other than operations can be reduced.

[Brief description of the drawings]

FIG. 1 is a schematic block diagram showing a system configuration of a distributed control device according to an embodiment of the present invention.

FIG. 2 is a diagram illustrating usage state data in an initial state in the distributed control device of the embodiment.

FIG. 3 is a diagram illustrating usage data after screen A is activated in the distributed control device of the embodiment.

FIG. 4 is a diagram illustrating usage status data after the screen C is activated in the distributed control device of the embodiment.

FIG. 5 is a diagram illustrating a flow of data of usage status when a screen is started on a console in the distributed control device of the embodiment.

FIG. 6 is a diagram illustrating usage data after the screen B ends in the distributed control device of the embodiment.

FIG. 7 is a diagram for explaining a change in an editing state after the end of the screen B;

FIG. 8 is a flowchart illustrating an operation of the distributed control device of the embodiment immediately after the console is started.

[Explanation of symbols]

_{1 -1, 1 -2, ...,} 1 -n operator console 2 information LAN 3 Plant 4 control LAN

Claims (1)

[Claims] 1. Engineering of a distributed control device for monitoring and controlling a plant through a plurality of operator consoles each having two-dimensional display means (signal and data registration).
Checks whether the same data is used in the registration screen of another console on the LAN based on the association between the screen to be registered and the data required for registration, and prohibits editing of the data if necessary A decentralized control device characterized by: