JPS6380337A - Maintenance device for decentralized process controlling device - Google Patents

Abstract

PURPOSE:To monitor a controller connected to a different network by one set of maintenance device by using a host controller to link plural subsequent networks to a common host network having the maintenance device. CONSTITUTION:The data transmission between the maintenance device 300 and the host controller UCTL 100 is executed through the device 300, UNW 200, UTCL 100, UNW 200, device 300 via the host network UNW 200 and the data transmission between the device 300 and the subsequent LCTL 101 is executed through the device 300, UNW 200, UCTL 100, LUW 201, LCTL 101, LUW 201, UCTL 100, UNW 200, device 300 via the UNW 200, the UCTL 100 and the LCTL 201. The device main body 301 receives the transmission signal from the UCTL 100 to the UNW 200, compares the content of the UCTL node No. table and the received node No., fetches the data in the reception data area specified by each node to carry out editing processing and displays a prescribed data on a CRT 302.

Description

[Detailed description of the invention] [Industrial field] The present invention relates to a maintenance device for a distributed process control device,
In particular, the present invention relates to a maintenance device suitable for a distributed process control device that is connected to a large number of controllers and requires intensive high-speed online maintenance from one location.More specifically, the present invention , a plurality of lower-level networks each connected to the upper-level network by at least one higher-level controller;
Relating to a maintenance device for a distributed process control device including a lower-level controller connected to the lower-level network.
Conventional technology] Conventionally, in distributed process control devices that use microcomputers as process control controllers (hereinafter referred to as controllers), each type of The controllers are connected via a network for data transmission of control signals.

There are primary types of maintenance devices for these distributed process control devices.

(Person) Connect the maintenance device to each controller via an interface different from the interface of the network concerned:
(B) A method in which each network is connected and maintained by connecting each maintenance device individually. (CC) An interface is placed in each network and the signal lines are connected in a star pattern. A system where all systems are gathered in one location and maintained using a single maintenance device using a common signal switch.

[Problem that the invention seeks to solve]

In the Joki Jumei technology, there were the following problems when monitoring the calculation results of multiple controllers. First, with method (A), the condition B of two or more controllers was monitored at the same time. In order to monitor the controllers, maintenance devices for the number of controllers that are desired to be monitored simultaneously are required, which complicates the configuration and increases costs.

Furthermore, as the number of controllers increases, the space required to install maintenance equipment in one place becomes a problem.Next, regarding method (B), in order to monitor the status of controllers on different networks at the same time,
Since maintenance devices are required for the number of networks, the structure becomes complicated and costs increase, and the method described above (A
), when the number of networks is large, the installation space for maintenance equipment becomes an issue.

Regarding method (C), the status of the controller of the specified network is 8. - It is possible to monitor the status of controllers on different networks at the same time by changing the switch of a changeover device by one maintenance device at a location, but it is not possible to monitor the status of controllers on different networks at the same time.

In addition, when ending the monitoring process of a controller that has started - degree monitoring, in method (λ), method (B)
However, in method (C), there is the hassle of having to perform switching for each network.

An object of the present invention is to enable one maintenance device to simultaneously monitor the states of controllers connected to different networks at the same time without switching delays and transmission delays.

[Means for solving problems]

The above problem is solved by the following means.

(1) Each of the multiple upper networks 8. At least one upper controller is connected to a common upper network, and a maintenance device is connected to the upper network.

(2) Each controller should be unique (no duplicates) throughout the system and have the same number of digits, and a specific digit number (or symbol) should be assigned to each controller connected to the same lower level network. The controller and lower controllers are the same, and are stored in each controller.

Further, the upper controller stores a correspondence table (node correspondence table) between the controller positions of the lower controllers and the node positions.

(3) The maintenance device and the upper controller are assigned 1m% of unique nodes on the upper network and are stored therein, and the upper controller is also stored with the node FkL on the lower network.

(4) The maintenance device includes a monitor start or end command, a controller number to be monitored. , a device for inputting a monitor request signal point number, and a controller No. A correspondence table (node table) between the specific digit number (or symbol) of the controller and the node number in the upper network of the upper controller is provided. ), the node number is calculated based on the above node table, and the request signal 1! corresponding to the node is calculated for each node floor. An embedded table (node-specific request signal management table) 8 is created and stored.

(5) When the above-mentioned monitor start command is input to the maintenance device, this maintenance device receives its own node number. , and sends the monitor start command, the controller number to be monitored, and the signal point number to the upper network, and also sends the node number calculated in (4) above. When the monitor start command, the number of data words, and the signal data are received from all the upper level controllers of The maintenance device 8 is configured to edit and display on a data display device.

(6) When the above-mentioned monitor end command is input to the maintenance device, this maintenance device transmits its own node 3 and monitor end command together with the same controller and signal point number as at the time of the above-mentioned monitor start command, and ), after sending, the device monitors the received data received from the higher-level controller, and when the sending command (end command) is confirmed to have been received by all controllers, the device sends a message indicating that monitoring has ended. The maintenance device is configured so as to display the following information.

(The upper controller receives the transmission data from the above maintenance device, checks the node number with the number in its own memory, and if it matches, the received command and the controller number
o. , the signal point number is kept in its own memory as 0, while the same content is stored in its own node number in the lower network. and send it on the lower network.

At this time, if the command is a start command and the data includes its own controller, monitor processing is started, the signal data corresponding to the designated signal point is extracted, and the transmission data buffer ( (upper), temporarily store it in the same l1lij order as when it was received.

After transmission to the lower network, the received data from the lower controller is sent to the controller N that received it from the maintenance device.
o. If it matches the sent command, the following processing is performed depending on the type number of the command.

If the command is a start command, the received signal data is temporarily stored in the transmission data buffer (upper) 1 in the same order as when it was received. Then, at the time when data is received from all the lower controllers of the lower network, the own node No. on the upper network is received. and the contents of the above send data buffer (upper) (start command,
The number of data words and signal data) are transmitted over the upper network.

If the command is a termination command, only the termination command is sent to the upper network in the same manner as described above when it is received from all lower controllers.

(8) The lower controller receives the transmission data from the upper controller, checks the 7th floor of the upper controller with the number in its own memory, and if they match, the lower controller transmits the data according to the type of command. Each is processed as follows.

If the received command is a start command and the received data includes its own controller, monitor processing is started, the signal data corresponding to the specified signal point number is extracted, arranged in the order in which it was received, and the corresponding Attach the self-node FkL on the lower network and send the start command, number of data words, and signal data to the lower network.e If the above command is an end command, end the monitoring process and send the self-node Sends a termination command to the lower network.

[Effect]

From the maintenance device to its own node number. , monitor start command, controller No. When the signal point number is sent to the upper network, the upper controller receives the node number of the maintenance device on the upper network. Since the data is stored in advance, the host controller can recognize without delay that the received data is from the maintenance device.

Next, the higher-level controller, which learns from the monitor command that a monitor start command has been issued and whose unit matches the controller data in the received data, can immediately move on to monitor processing.

At the same time, the data after the above-mentioned monitor start request is transmitted from the upper controller Gζ to the lower network along with the note 7 on the lower network of the upper controller.Thus, the lower controller Whether the node number of the upper controller matches what it remembers, and also whether the h4 of the command
The process of determining whether the controller group in the received data matches the own controller group can be executed in parallel with other controllers.

That is, the above-mentioned monitor start command, controller number, and signal point number can be quickly transmitted to all upper and lower controllers of the process control device.

Next, since the upper controller receives the node number and data together from the lower controller, the controller number is determined using the node-to-node correspondence table of the controllers belonging to the lower network. can be easily recognized.

Then, the upper controller receives the upper controller number from the maintenance device. If it is determined that monitor start commands have been received from all controllers that match, if the controller also has a start command as described above, its edited data is also collected and the requested In the data order format, the node number on the upper network of the upper controller. monitor start command,
The number of data words and signal data are collectively transmitted to the upper network as monitor data of the upper controller of the lower network.

Therefore, the maintenance device can receive the request with a time difference equivalent to the delay in the transmission cycle between each upper controller, and can easily receive the request input from the input device based on the node-specific request signal management table. Data can be edited in order and displayed on a display device.

In other words, the maintenance device does not need to edit data received from lower-level controllers (and the time difference in signal and data reception between higher-level controllers can be reduced, so data from controllers on different networks can be edited). Both monitors can be displayed at the same time by reducing the mutual time delay.

〔Example〕

An embodiment of the present invention will be described below. FIG. 1 shows an example in which the present invention is applied to a distributed process control device. The process control device includes an upper controller 100, a lower controller 101. It is composed of an upper network 2001 that connects the respective upper controllers, and a lower network 201 that connects one upper controller 100 and a plurality of lower controllers 101 belonging thereto.

Process control is performed by performing control calculations in the lower controller 101 and the upper controller 100 based on the process signal 11 from the transmitter 10, and applying the result to the operating end 20 as an operating signal 21.

Within the same lower network, information exchange between the upper controller 100 and the lower network 101 of the cough network is performed via the lower network.On the other hand, data transmission between different lower networks is performed between the upper controller 100 and the lower network. Data transmission between upper controllers 100 is performed via the upper network 200.

The maintenance equipment ft300 includes a maintenance equipment main body 301. It is composed of a CRT display fit 302 and a keyboard 303.

Data transmission between the maintenance device 300 and the host controller 100 is performed via the host network 2008 in the following order: maintenance device 300 → host network 200 → host controller 100 → host network 200 → maintenance equipment 30
0 route.

On the other hand, data transmission between the maintenance device 300 and the lower controller 101 is performed by the upper network 200, the upper controller 100. Maintenance equipment via the lower network 201! 300 → Upper network 200 → Upper controller 100 → Lower network 201 → Lower controller 101 → Lower network 201 → Upper controller 100 → Upper network 200 → Maintenance device 30
0 route.

FIG. 2 shows a detailed block diagram of the maintenance device 300, FIG. 3 shows a detailed block diagram of the upper controller 100, and FIG. 4 shows a detailed block diagram of the lower controller 101. The operation of the embodiment will be explained below using these drawings.

First, input a monitor command and controller number from the keyboard 303 shown in FIG. Enter the signal point number.

The key human processing unit 3011 inputs these data to the input data buffer 301. This is sent to the transmission editing processing section 301 in the format shown in FIG. 12. is set in the transmission buffer 30l, and the transmission processing unit 301.
adds the maintenance device node m301s to the beginning of this data and transmits it to the upper network 200 at the timing of the transmission cycle.

Editing table creation process 301. Refers to the node positive table 3o18, an example of which is shown in FIG. 13, and creates the node level corresponding request signal data management table 301. as shown in FIG. 14. %create.

FIG. 12 shows a format H in the system configuration shown in FIG. 1 when the maintenance device makes a request to monitor data as shown in FIG. 7 (this will be described in detail later).

In Figure 1, the upper and lower controller floors are composed of two digits, and the upper digit number is the node F of the upper controller.
kL, and the second digit (higher digit) signal of the lower controller is matched with that of the upper controller.

FIG. 13 shows the above-mentioned controller No. A node number table 301 showing the correspondence between the upper digits (ASCII code) and node numbers. It is.

When the data shown in Fig. 12 is input, the maintenance device main body 30
The editing processing table creation processing unit 30 l of No. 1 is
For the controller number 111”, the upper digit is 11.
” Therefore, from the node table in Figure 13.” 3
1'! It is determined that this is the corresponding node -Of'', and the first
4. Register the first i node @01” in Figure 4. Also, register the first
Since there is only one signal point in FIG. 2, "1" is set in the corresponding section in FIG. 14.

Next, regarding the upper controller 21 in FIG. 1, since it is node 2-2, "2" is set in FIG. 14, and l" is set in the corresponding section to indicate the first data.

Similarly, for the lower controller 22, the node seal 2
Therefore, set node--2 in the same way as above, and since this is the second data of the same node, set @2' in the corresponding section in FIG. 14. The reception processing unit Zoo shown in FIG. 3 receives the signal (see FIG. 12) sent to the node table 100. of the maintenance equipment and other upper controllers. contents and receiving node No. @As a result, when it is recognized that the maintenance device node is missing, the reception management table (upper)
ioo.

Receive data area specified for each node (upper)
The above received data is taken in at 10 o4.

Next, reception editing processing B (upper) 100. is the reception specification table (upper) 100. Refer to , and read the contents of the maintenance device reception data area (upper) l 003 to the reception data buffer (upper) 100. Transfer the data from other upper controllers to the reception data area (upper) l OO4 to the reception specification table (upper) l OO
, and moves to the calculation result area 100 designated by .

Calculation result area 100. The contents of the control calculation processing section 10
0. , the control calculation cycle is updated accordingly.

The missing number command decoder data transcription processing section 100 decodes the command of the data (FIG. 12 is an example) of the received data buffer (upper) l Ooy, and outputs the command to the data editing processing section i o o. At the same time, it is determined whether or not its own controller m l OO, is included in the above data.

If included, the data editing processing unit 100. The specified point number data is calculated in the calculation result area l OOa
Transmit data buffer (upper) l O
tic is set at a predetermined position of 012. Next, the data in the receive data buffer (upper) ioo is transferred to the transmit data buffer (upper) L00. ! Posted to.

Transmission editing processing section (lower) l 0014 is transmission data buffer (lower) l OO+s and calculation result area i
The contents of oo are edited based on the transmission specification table (lower) 100□, and the contents of the transmission buffer (lower) l00.
, write to.

The transmission processing unit (lower>lOOl) writes its own node 1001 on the lower network at the beginning of this data.
lower network 2 at the timing of the transmission cycle.
The lower controller 101 receives the signal sent out onto the lower network 201 as described above with the reception processing unit lO1 shown in FIG. Compare and contrast with the contents of the node positive table 101□.

As a result, the received signal contains node N of the upper controller.
o. When the received data is recognized, the above received data is taken into the designated position number of the received data area i o i defined for each node in the reception management table 101 .

Reception editing processing unit 101. is the reception specification table 101,
Refer to the receive data area 101 for upper controller.
．． The contents of receive data buffer 101? Move to
Also, the reception data area 1014 from the lower controller
The data in the reception specification table 101. The calculation result area 101. Posted to.

Next, the command decoding/data editing processing unit 101° receives the received data buffer 101. (Fig. 12 is an example) command is decoded. Figure 12'POO
Since "O" is a monitor start command, monitor processing is started in accordance with this command.

That is, the command decoding/data editing processing unit 101 executes the self-controller m101. . is in the data, and if so, the data of the specified point number is read from the operation result area lot, and is sent to the transmission data buffer 101. .

Set it to the specified position. The contents of the calculation result area 101a are stored in the control calculation processing section 101. ! The transmission editing processing unit 10 is updated according to the control calculation cycle by the transmission specification table 10.
1, based on the transmission data buffer 1of1 and the calculation result area l01. The contents are edited and written to the transmission buffer 101□. The transmission processing unit 101,...
This data is appended with % at the beginning of the self-node 101 and sent to the lower network 201 at the timing of the transmission cycle. In this case, the format of the sent data is as shown in FIG. 15: command, data word count, signal data. Consists of. As you can see if you compare it with Figure 12, the data in Figure 15 is “9”.
2” and 195” are point code person 005 and person 010
This is the data.

Next, as described above, the upper controller 100 transmits the signal transmitted from the lower controller 101 to the lower network 201 to the reception processing unit (lower) 10 shown in FIG.
0. . , compares the received node floor with the contents of the node floor table lOOl of the lower controller, and stores the above information in the reception data area i o o, defined for each node in the reception management table (lower) IQO, . Import received data.

Reception editing processing section (lower) 100!4 is reception specification table (lower) 100. , and extract only the above command, number of data words, and signal data from the reception data area 1000 and store them in the reception data buffer (lower) l 00
! , and the control data is transferred to the calculation result area 100.
．． Move to.

The data editing process @ 100Io checks the contents of the received data buffer (lower) 100□6 for each node.Then, the node where the command is received (in this case, the correspondence between the controller block of the lower controller and the node block) Based on the stored node correspondence fiioO!, convert the node into the controller and check against the controller stored in the receive data buffer (upper) 100 degrees. ・Both controllers match. Furthermore, the received signal data and the total number of words are arranged in the order of the contents of the received data buffer (upper) l OO, and all responses have been received from the corresponding controllers (all the When the controller confirms that the requested monitor data has been sent, the receive data buffer (upper)
The command stored in 1007 is sent to the data buffer (
Top) l 00. , transmission editing processing unit (upper) 100. , is the transmission specification table (upper) l
Based on Oowe, send data buffer (upper) l
Edit the contents of the calculation result area ioall with OO,2, and send it to the buffer for i1 (upper)L OO,.・ Transmission processing unit (Royal) l OOss appends its own node rkloos□ on the upper network to the beginning of this data, and sends it to the upper network 200 at the timing of the transmission cycle.
I'll send it to you.

Next, the maintenance device main body 301 receives the signal transmitted from the upper level controller 100 to the upper level network 200 as described above to the reception processing unit 301 shown in FIG. and the upper controller node floor table 301. The contents of l and the receiving node No. Compare and contrast the reception data area 30 defined for each node in the reception management table 301□.
1. , takes in the above received data.

The reception editing processing unit 301.4 stores the reception specification table 301,
, and transfer the contents of the receive data area 301.3 to the receive data buffer 301.3. .・Data editing processing section 3
01. , refers to the previously created node-related request signal data management table 301° (FIG. 14 is an example) and stores the received data buffer 301. . (Fig. 5 is an example for Fig. 12) and edit the contents of the display buffer 301.
．． Set to s.

Data display processing section 30 l. is 1 display bakhwa 301
, , based on the contents of controller No. Signal point numbers and signal data, etc., are input in the order in which they are input during the monitor request.
It is displayed on the RT display device 302.

Regarding the processing of the monitor M completion command, the controller No. that issued the end command and start command from the maintenance equipment.
and signal point number, the data is transmitted through the same route and processing as described above.

When the relevant controller receives the above-mentioned data, it ends the monitoring process and sends an end command back to the maintenance device. All applicable controllers return a termination command, and when the maintenance equipment receives it, it displays a monitor termination message) on the CRT display device.

6 to 9 show the case where the present invention is applied to the online trend graph display function of the maintenance device 300. and (b) an operating procedure for displaying a trend graph of a specified signal on a CRT and an example of a CRT display screen. This content will be explained below.

In general, when trend graphs are displayed simultaneously, displaying a large amount of data on one CRT screen can cause the screen to become congested, impairing visibility. In view of the fact that black is excluded (), data of about 6 pieces per screen is displayed at the same time,
By switching to another screen, it is possible to monitor the data of other signals at the same time. In other words, since only about 6 points can be displayed on one screen, data must be captured on the required number of screens. However, only the data corresponding to the screen requested to be displayed is displayed on the screen.

In the following, this screen will be identified by page number.

Figure 6 shows the procedure for setting tread display items.In step 61, manually specify the display screen (for example, page ugliness), and then in step 62, the time axis scale (for example, l) of the trend graph For example, select 6 minutes).

In step 63, the individual (point 1 is selected and the display scale and unit are entered. In other words, first, in order to specify which controller the signal belongs to, the controller (for example, 11) is entered, and then the point number (e.g. AOO2
＞Enter %.

Furthermore, the calculation range lower limit value MIN (for example, -1
00) and an upper limit value MAX (for example, -200).

Calculated value center value C, (for example, O), display data center value C
, (for example, 5 O%), display gain G (for example, 1
．． 0), display item name (for example, MWB), engineering unit range lower limit (for example, O) and upper limit (for example, 100
0) and engineering units (for example, MW).

One page of display items and parameter settings are completed.
In step 64, it is determined whether settings for other pages are necessary. If necessary, steps 61 to 63 are repeated, and if unnecessary, the process is terminated. In addition, in the above,
The numbers in parentheses are channel (CH)l in Figure 7.
This applies to IC.

Using the numerical values entered as above, the value Y of the graph display
is calculated by the following formula, where X is the value of the data transmitted from the controller.

In the case of the setting values listed in parentheses above, the value Y of the graph display is as follows @ Figure 7 shows a display example of a CRT screen with display items set according to the procedure explained in Figure 6.・This example is page N
This shows the setting contents of ll, and up to 6 trend points can be registered on one page. A total of four digital signals of the signal point D101 are set.

The details of each item in Figure 7 are as follows: CH: channel (display graph number) CTL, 闘: controller team PT, UG: point number COMP, RANGE (LO■几): calculation range Lower limit COMP, RANGE (UPPER): Upper limit of calculation range CENTER (VALUE): Calculation center direct CENTER (%): Center value of display data G Artificial N: Disaster gain NAME: Display item name EiNG, RAMGE (Lω conversion R): Engineering unit range lower limit BNG, RANGE (UPPRR) : Engineering unit range upper limit UNIT : Engineering unit Figure 8 shows the procedure from starting to ending the trend graph display for the page where display items are set according to Figure 6. This is what is shown: First, step 81
Page lI&! (for example, page 1m1) and
Next, when a monitor start command is input in step 82, the monitor command, controller No. The signal point number is transmitted from the maintenance device 300 to the controller, and the controller sends the corresponding data onto the network at a predetermined period (see Figure 5).In step 83, the maintenance device 300 receives this and updates the trend Display as a graph. The details of the display number will be explained later with reference to FIG.

In step 84, it is determined whether or not to end the display. If the display is to be ended, the process advances to the next step 85.

When the operator inputs a termination command, it is determined in step 84 that the process has ended, and in step 85 the termination command is transmitted to the corresponding controller. The relevant controller ends the monitoring process and returns the termination command to the maintenance bag [1]. The maintenance device ends the trend graph display process when it receives this end command from all applicable controllers. ・Figure 9 shows the trend graph CRT when the display process is performed according to the procedure shown in Figure 8. An example of screen display is shown.

This example displays a trend graph of signals corresponding to the setting items in Figure 7. Analog signals are displayed on channels 1, 2.3, and digital signals are displayed on channel 4. The numbers near the graph are channel numbers. impersonating. The engineering unit scale of each analog signal is shown in order from the left end of the graph display frame to the right end, starting from channel 1, with the upper limit and unit at the top of the display frame, and the lower limit at the bottom. In Figure 9, )(1, H2, H3,...).

Bl, B2, 83. ...... are respectively channel 1,
Indicates the engineering unit range of 2゜3,... Also,
r_VALUEJ in the figure represents the current value of the data of the valley channel.

FIG. 10 shows the internal processing 70- of the host controller 100.
shows. The processes of steps 101 to 107 are repeatedly executed in order at a predetermined period.

In step 101, the reception editing processing unit (upper) ioo,
tThus, the received data from the upper network 200 is edited, and in step 102, the received data from the lower network is edited by the reception editing processing section (lower) lOO,.

In step 103, based on the data received above and the control calculation processing results of the previous cycle, the control calculation processing section 100. ,
Control calculations are executed by.

In step 104, the command decoding/data transcription processing unit 1 decodes the command from the maintenance device 300 and transfers the received data to the lower network transmission data buffer.
00. In step 105, the data editing processing unit 1001° performs a process of transferring the received 1g data from the lower controller and the calculation result of its own controller to the transmission data buffer (upper) 100.2.

In step 106, the transmission editing processing unit (lower) i o
ol, transmit data buffer (lower) 100,
, and the calculation result area 100. The contents of are edited and transferred to the transmission buffer (lower) 100□.゛In step 107, the transmission editing processing unit (upper) 100,
The contents of the transmission data buffer (upper) 100, and the calculation result area lOO are edited and transferred to the upper network transmission buffer (upper) lO03o. Figure 11 shows the internal processing of the lower controller 101. Show flow. The processes of steps ill to 114 are repeatedly executed in order at a predetermined period.

In step 111, the reception editing processing unit 1015 of the lower network edits the received data from the lower network 201, and in step 112, control calculation processing is performed based on the data received above and the control calculation processing result of the previous cycle. Part 10 l,! Control calculations are executed by.

In step l13, in response to the command and received data from the maintenance device 300, the calculation result area 101. Data editing from the command resolution dispute data editing processing unit 101
．． and the result is sent data buffer lOl
, 1 is transferred to @step 114, the transmission data buffer l 01. is transferred to the transmission data buffer l 01.
, and the calculation result area 101. The contents of 01. are edited and sent to the buffer for transmission to the lower network 201. In the above explanation, in order to clarify the mutual relationship between the controller nodes and the controller floors on each network, each controller has the same number of digits and is not duplicated. A unique controller field and a /- do positive on each network were assigned, and the value or symbol of a specific digit of the controller group was the same for those connected to the same lower network, but instead It will be easily understood that even if a table representing the relationships is provided in the host controller and/or the maintenance device, the same monitoring function as described above is possible.

〔Effect of the invention〕

According to the present invention, arbitrary data of arbitrary controllers on different networks can be quickly and simultaneously monitored with one maintenance device, and termination operations can be easily performed.

[Brief explanation of the drawing]

FIG. 1 is a schematic block diagram of an embodiment of the present invention. Figure 2 is a detailed block diagram of the main body of the maintenance device shown in Figure 1, Figure 3 is a detailed block diagram of the lower controller shown in Figure 1, and Figure 4 is a detailed block diagram of the lower controller shown in Figure 1. Figure 5 is a diagram showing an example of the format of data from the host controller that is most important in maintenance equipment, Figure 6 is a flowchart showing the procedure for setting items to be displayed on the trend graph, and the seventh factor is the A diagram showing a specific example of the display items of the trend graph, FIG. 8 is a flowchart showing the procedure for displaying the trend graph in the maintenance equipment, FIG. 9 is a diagram showing an example of the display of the trend graph, and FIG. 10 is the upper controller. Flowchart showing the internal processing steps of &! Fig. 11 is a 70-chart showing the internal processing procedure of the lower controller, Fig. 12 is a diagram showing the format of data transmitted from the maintenance equipment to the upper controller using the monitor start special number, and Fig. 13 is a diagram showing the node floor provided in the maintenance equipment. Figure 14 shows a concrete example of a node-specific request data management table provided in the maintenance device, and Figure 15 shows an example of the format of data transmitted from a lower controller to an upper controller. It is a diagram. DESCRIPTION OF SYMBOLS 10... Transmitter, 20... Control end, 100... Upper controller, 101... Lower controller, 20
0... Upper network, 201... Lower network, 300... Maintenance device, 301... Maintenance device body, 302... CRT display device, 303... Keyboard. 100, . . . Node block table for maintenance equipment and other upper controllers, 100. ... Reception editing processing Wi5 (a), L Q Os ... Command decoding/data Ele processing [i, l OO,, ... sending (
Jim collection processing S (lower). 1OO14... Reception editing processing unit (lower), l OO,
. . . . Node hidden correspondence table, 100□8 . . . Transmission editing processing unit (upper), 10ft . . . Node hidden table of other controllers on the lower network, 101.・・・
- Reception editing processing unit, 101.・・・Command deciphering・
Data editing processing section, 1olss... transmission editing processing section. 301... Transmission editing processing unit, 30th... Editing table creation processing unit, 301*... Node-specific request signal data management table, 301. , . . . Node m of the upper controller, 301. , . . . reception editing processing unit, 301. ,...data editing processing section, 301s
s...display buffer, 301. ,... Data Display Processing Department Agent Patent Attorney Michihito Hiraki +0021 Figure 4 Figure 5 (a) Received data from node 1 (b) Received data from node 2 (c) Received data from node 3 Figure 6 Figure 8 Figure 9 BI BZ B3 Figure 10 Figure 11 Figure 12 Figure 15 Figure 13

Claims (6)

[Claims] (1) Maintenance of a distributed process control device that includes a common upper network, a plurality of lower networks each connected to the upper network by at least one upper controller, and a lower controller connected to the lower network. The device includes a maintenance device main body, a display device connected to the maintenance device, and an input device, and is provided in either the maintenance device connected to the upper network, and the maintenance device and the upper controller, and is connected to each network. The node numbers of the upper and lower controllers above. and controller no. The maintenance device further includes a table representing the mutual relationship between the maintenance device and its own node N in the upper network.
o. , the node number of the upper controller. and the value or symbol of the specific digit, as well as the controller number of the input controller to be monitored. and the node number created based on the signal point number. Means for storing a corresponding request signal data management table, input monitor start command, controller No. , and the signal point number, or the own node number in the monitor end command. The upper controller is equipped with means for transmitting these data onto the upper network by adding the node numbers of the lower controllers connected to itself and the lower controllers connected to the upper controller. Controller No. , the controller No. and node no. Means for storing the correspondence table of self-related data on the upper network, and means for storing the correspondence table of own node No. on the lower network. means to add the self-related data and transfer the self-related data onto the lower network, and include the self-controller No. in the imported self-related data. The lower controller includes means for determining whether or not there is its own controller No. in the data transferred from the upper controller to the lower network. means for determining whether or not there is a controller No. of the self. If there is, data of the requested signal point number and own node number. the higher-level controller further comprises means for receiving data transmitted from the lower-level controllers onto the lower-level network; and means for receiving the data transmitted from the lower-level controllers onto the lower-level network; When data from all the requested lower-level controllers has been retrieved according to the above-mentioned determination result, the data retrieved from the lower-level controllers is also monitored if there is a request for self-monitoring. If so, edit it together with your own data, and edit it with your own node No. on the upper network. The maintenance device further includes means for acquiring data transmitted from the upper level controller onto the upper level network, and means for capturing data from all the requested upper level controllers. and a means for determining whether data has been received, and when data from all requested controllers has been taken in, according to the above-mentioned determination result, displaying the data taken in from the upper controller on a display device in a predetermined format. 1. A maintenance device for a distributed process control device, characterized by comprising means. (2) When the maintenance device displays the monitor data on the display device, the maintenance device transfers the captured data to the node number. Based on the corresponding request signal data management table, the controller number input from the input device is determined. 2. The maintenance device for a distributed process control device according to claim 1, wherein the maintenance device is configured to perform editing in advance in order. (3) The upper controller is characterized in that, when transmitting the data imported from the lower controller via the lower network and its own data to the upper network, the upper controller edits these data in advance in the order requested by the maintenance device. A maintenance device for a distributed process control device according to claim 1 or 2. (4) If the command received from the maintenance device is a monitor termination command, the higher-level controller shall send only the termination command back to the upper-level network when the requested data from all lower-level controllers has been captured. A maintenance device for a dispersion amount process control device according to claim 1, characterized in that: (5) When the command received from the upper controller is a monitor start command, the lower controller arranges the data of the specified signal number in the specified order in advance and transmits it to the lower network. A maintenance device for a distributed process control device according to claim 1. (6) Node numbers of upper and lower controllers on each network. and controller no. Instead of having a table representing the mutual relationship between upper and lower controllers, each upper and lower controller number has the same number of digits and is assigned a controller number that does not overlap with each other. and node numbers on the upper and lower networks. and means for storing the controller No. The distributed process control device according to any one of claims 1 to 5, wherein the value or symbol of a specific digit is the same for controllers connected to the same lower-level network. Maintenance equipment.